Stock Orderpoint Procure Location
Allows to create procurement orders in a different locationthe orderpoint
auto_awesome What this module does
AI-generated from the code · Odoo 12.0Adds a 'Procurement Location' field to reordering rules so replenishment orders can be created in a different location than the one being replenished.
This module extends reordering rules (orderpoints) with an extra field called Procurement Location. When you set it, the automatic replenishment triggered by that rule is created in the chosen location instead of the rule's own location.
Where it appears: - On the reordering rules list and form, a new 'Procurement Location' field is shown right after the existing Location field. It is only visible to users who have the multi-locations setting enabled. - The field only accepts internal or transit locations.
What it changes: - When a reordering rule runs and generates a procurement, the module passes the chosen procurement location along with the request. - The procurement engine then uses that location as the destination for the generated order, so the replenishment lands where you asked for it. - If no procurement location is set on the rule, behaviour stays exactly as standard Odoo.
It touches the reordering rule model stock.warehouse.orderpoint and the procurement engine procurement.group, and depends on the Purchase and Inventory apps.
Depends on
Models and fields (2)
- procurement.group · extends an existing model
- stock.warehouse.orderpoint · extends an existing modelprocure_location_id (Procurement Location)
Text generated by AI (DeepSeek) from reading the Odoo 12.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 12.0
Confirmed on 2026-11-03 in branch 12.0 of OCA/stock-logistics-warehouse.
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.