sale_stock_prebook_stock_available_to_promise_release
Extends the previous available qty to promised with moves of a reservation
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Links prebooked stock reservations with the available-to-promise release process, so that when a sales order is confirmed, the reservation's priority date is passed to the delivery moves.
This module is an automatic bridge between two other modules: one that lets you prebook stock for a sales order, and one that manages available-to-promise (ATP) release dates. It does not add any new menu or screen; it changes how existing confirmations behave.
When a user confirms a sales order that has a reservation, the system looks at the reservation's delivery moves and takes the priority date of the first move. That date is then used when creating the stock moves for the order lines, so the new moves inherit the same priority as the reservation.
It also adjusts how the system counts previously promised quantities. Moves that are used for a sale reservation are now matched with moves that need release, and moves that are not used for a sale reservation are excluded from the 'no release' calculation. This helps keep the promised quantities accurate when both prebooking and ATP release are used together.
The module touches the sales order, sales order line, and stock move models. It is installed automatically when both dependency modules are present.
Models and fields (2)
- sale.order · extends an existing model
- sale.order.line · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 18.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 3 confirmed, 6 with no information of 9 versions.
Sources · Odoo 16.0
Confirmed on 2026-11-03 in branch 16.0 of OCA/sale-prebook.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.