Stock Picking Propagate Scheduled Date
Allows changes on the scheduled date of the pickings to be propagated when picking moves are chained.
Propagate the date delta between the new date and the old date to the move_dest_ids of the stock move being updated.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0When you change the scheduled date of a stock transfer, Odoo automatically shifts the scheduled dates of the downstream transfers that depend on it by the same time difference.
This module keeps chained warehouse operations in sync when you reschedule one of them.
- If you edit the scheduled date of a stock transfer (or of a stock move), the same time difference is applied to the next moves in the chain, so the whole sequence moves together instead of leaving later steps at their old dates.
- Moves that are already done or cancelled are left untouched, and a move is never shifted twice in the same operation, which avoids double adjustments when several moves share the same successor.
- The propagation also runs when a transfer is validated, so the dates of the following steps stay consistent with what was actually executed.
It works on the stock.move and stock.picking models and only changes scheduled dates; quantities, products, locations and statuses are not modified. There are no new menus, screens, buttons or reports: the behaviour is automatic and appears directly in the existing transfer and move date fields.
Depends on
Models and fields (1)
- stock.move · 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: 2 confirmed, 7 with no information of 9 versions.
Sources · Odoo 15.0
Confirmed on 2026-11-03 in branch 15.0 of OCA/stock-logistics-workflow.
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.