Stock Orderpoint Move Link
This module adds to stock moves a direct link to the reordering rules that created them. In chained moves, the reordering rule is propagated.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0This module links reordering rules to the stock moves they generate, so you can see which rule created a transfer and open all transfers linked to a rule.
When Odoo automatically creates a stock move because a reordering rule (orderpoint) was triggered, this module records that link on the move. On the stock move form you now see a field called "Linked Reordering Rules" showing the reordering rules behind that move.
On the reordering rule form a new "Transfers" button appears in the button box. Clicking it opens the list of transfers whose moves are linked to that rule, so you can trace replenishment activity from the rule itself.
The link is also carried through chained moves: when a move creates a follow-up move, the reordering rules are passed along, and when moves are merged the linked rules are combined. This means the link is not lost in multi-step routes.
The module touches stock.move, stock.rule and stock.warehouse.orderpoint. It does not add new menus; it adds a field on the move form and a button on the reordering rule form.
Depends on
Required by other modules
Models and fields (3)
- stock.move · extends an existing modelorderpoint_ids (Linked Reordering Rules)
- stock.rule · extends an existing model
- stock.warehouse.orderpoint · 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: 6 confirmed, 3 with no information of 9 versions.
Sources · Odoo 16.0
Confirmed on 2026-11-03 in branch 16.0 of OCA/stock-logistics-orderpoint.
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.