Stock Picking Origin State

This module adds two computed fields on stock.picking that summarize the state of the most upstream not-done origin pickings:

origin_state: aggregated state across the origin pickings at the deepest level still active (waiting, partially_available, assigned or done).
origin_state_label: a display string combining the origin operation type name and the translated state label

Table of contents

Use Cases / Context
Bug Tracker
Credits

Use Cases / Context

This module is useful whenever a transfer has upstream pickings that must be completed before it can proceed. The two most common scenarios are:

Multi-step outbound / inbound configured on the warehouse (e.g. a 3-step delivery: PICK → PACK → OUT). The final OUT picking benefits from showing the state of the PICK and PACK operations without navigating to them.
Linked moves via route / rules logic: push or pull rules can chain pickings across locations. Any downstream picking whose moves are fed by upstream moves will have an origin state computed.

When several origin pickings exist at the same chain level, the least favorable state is reported.

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.

Do not contact contributors directly about support or help with technical issues.

Credits

Authors

ForgeFlow

Contributors

Andreu Orensanz <andreu.orensanz@forgeflow.com>

Maintainers

This module is maintained by the OCA.

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

This module is part of the OCA/stock-logistics-workflow project on GitHub.