Currently the reservation is performed by adding reserved quantities on quants, which is fine as long as the reservation is made right after the order confirmation. This way, the first arrived, first served principle is always applied. But if you release warehouse operations in a chosen order (through deliver round for example), then you need to be sure the reservations are made in respect to the first arrived first served principle and not driven by the order you choose to release your operations.
Allow each delivery move to mark a quantity as virtually reserved. Simple rule would be first ordered, first served. More complex rules could be implemented.
When the reservation of a picking move occurs, the quantity that is reserved is then based on the quantity that was promised to the customer (available to promise):
- The moves can be reserved in any order, the right quantity is always reserved
- The removal strategy is computed only when the reservation occurs. If you
reserve order 2 before order 1 (because you have/want to deliver order 2) you
can apply correctly fifo/fefo.
- For instance order 1 must be delivered in 1 month, order 2 must be delivered now.
- Virtually lock quantities to be able to serve order 1
- Reserve remaining quantity for order 2 and apply fefo
- Allow to limit the promised quantity in time. If a customer orders now for a planned delivery in 2 months, then allow to not lock this quantity as virtually reserved
- Allow to perform reservations jointly with your delivery rounds planning. Reserve only the quants you planned to deliver.
When move qty is not completely satisfied on release, the remaining qty is split and attached to a new picking that can be released later.
Important: if the "Stock reservation horizon" is set, the qty is calculated on moves which have an expected date not beyond $today + $horizon (in days).
Important: Moves without a warehouse set are not supported. If the warehouse is not set on the move, the "Ordered Available to Promise" Quantity will always be 0. It will also not be considered as consuming existing stock. The warehouse gets set by the Stock rule, if the Rule is not assigned to a warehouse, also the move will not end up with a warehouse.
Table of contents
In Inventory > Configuration > Routes, activate the option "Release based on Available to Promise" on the routes where you want to use the feature.
To modify the horizon go to "Inventory > Settings" and change "Stock reservation horizon".
When an outgoing transfer would generate chained moves, it will not. The chained moves need to be released manually. To do so, open "Inventory > Operations > Stock Allocation", select the moves to release and use "action > Release Stock Move". A move can be released only if the available to promise quantity is greater than zero. This quantity is computed as the product's virtual quantity minus the previous moves in the list (previous being defined by the field "Priority Date").
This behaviour is activated by stock route by setting the option "Release based on Available to Promise".
By default, when an outgoing transfer is released, a backorder is created for the remaining quantities for products not available at release time. This behaviour can also be changed by stock route by setting the option "No backorder at release". In such a case, moves created for unavailable products will remain in the original outgoing picking and no backorder will be created.
One a picking is released, you can also ensure that new move will no more be assigned to a released picking by setting the option "Prevent new move after release". on the stock picking type.
At the end of the picking process (when the picking is validated) of an outgoing transfer, if a backorder is created, the chained moves can be automatically unreleased. This behaviour is activated by setting the option "Unrelease on backorder" on the stock picking type.
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.
- Camptocamp
- BCIM
- Guewen Baconnier <[email protected]>
- Simone Orsi <[email protected]>
- Jacques-Etienne Baudoux <[email protected]>
- Dung Tran <[email protected]>
- Laurent Mignon <[email protected]>
- Michael Tietz (MT Software) <[email protected]>
The development of this module has been financially supported by:
- Camptocamp
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/wms project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.