Stock Picking Backorder Policy
When a transfer is only partially done, Odoo decides whether to create a backorder for the remaining quantity based on the backorder policy of the operation type (Ask, Always or Never).
That default fits the warehouse, but the right answer is often driven by the document the transfer comes from: some customers always want the rest shipped later, others never do.
This module lets you optionally override that operation type default on the transfer itself:
Ask: the user is prompted (standard behaviour).
Always: a backorder is created automatically for the remaining quantity.
Never: the remaining quantity is cancelled and no backorder is created.
When left empty, the operation type’s own policy applies, exactly like standard Odoo.
The policy is carried by the operations, so it survives multi-step routes and make-to-order chains. Modules building on top of this one seed it from their own documents: sale_stock_picking_backorder_policy for deliveries generated from a sale order, purchase_stock_picking_backorder_policy for receipts generated from a purchase order.
Table of contents
Usage
On a transfer, set the Backorder Policy (Ask, Always or Never). The value set here takes precedence over the value set on the operation type; if left empty, the operation type’s value is used.
When the transfer is validated with a missing quantity:
Ask: the usual backorder prompt is shown.
Always: a backorder is created automatically.
Never: the remaining quantity is cancelled.
Returns and exchanges are never subject to the transfer’s backorder policy: they always follow the operation type’s own Create Backorder setting, since the policy of the original transfer is not relevant to goods coming back in.
Bug Tracker
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
Contributors
-
Alex Pfändler <alex.pfandler@camptocamp.com>
Iván Todorovich <ivan.todorovich@camptocamp.com>
Italo Lopes <italo.lopes@camptocamp.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.
Current maintainer:
This module is part of the OCA/stock-logistics-workflow project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
Metadata
Release files for odoo-addon-stock-picking-backorder-policy 19.0.1.1.0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo_addon_stock_picking_backorder_policy-19.0.1.1.0.4-py3-none-any.whl | Python 3 | none | any | Details for odoo_addon_stock_picking_backorder_policy-19.0.1.1.0.4-py3-none-any.whl |
Release files / odoo_addon_stock_picking_backorder_policy-19.0.1.1.0.4-py3-none-any.whl
| Download URL | odoo_addon_stock_picking_backorder_policy-19.0.1.1.0.4-py3-none-any.whl |
|---|---|
| Size | 35.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1882626bff68e21acb839a97c24c59a5e893172de5c58c58e2059098e823c1f6
|
|
BLAKE2b-256 checksum How to use checksums |
bd989fe7eaf28d9e4e574cb97532d9bd43850360f80b21129301f652b22e5849
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Security for odoo-addon-stock-picking-backorder-policy 19.0.1.1.0.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.