Purchase Stock Line Sequence
Glue module that propagates the purchase order line sequence to the related stock moves and prevents editing the sequence of those moves from the picking view.
It is automatically installed when both purchase_order_line_sequence and stock_picking_line_sequence are installed.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Keeps the order of purchase order lines and their stock moves in sync, and blocks changing the move order from the transfer screen.
This module links the line order you set on a purchase order with the order of the corresponding stock moves created for the receipt.
- When a purchase order is created, saved with changed lines, or when its receipt (picking) is generated, the sequence of each stock move is updated to match the visible sequence of its purchase order line.
- The update only applies to orders that contain at least one consumable product, and only to moves that are linked to a purchase order line.
- If someone tries to change the sequence of a stock move directly from the transfer/picking screen, Odoo raises an error telling the user that the order cannot be changed there and must be changed on the purchase order instead.
It works together with the purchase order line sequence and stock picking line sequence modules, and is installed automatically when both are present. It affects purchase.order and stock.move records.
Models and fields (2)
- stock.move · extends an existing model
- purchase.order · 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: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 18.0
Confirmed on 2026-11-03 in branch 18.0 of OCA/purchase-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.