Stock Location Orderpoint
Declare orderpoint on a location allowing to replenish any product with the same criteria. This is for an internal warehouse replenishment currently not compatible with the purchase buy route.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Lets you set up replenishment rules directly on a warehouse location, so any product stored there is automatically refilled from a source location when demand appears. Rules can run in real time, manually, or on a schedule.
This module adds a new concept called a location orderpoint: a rule attached to a specific internal location that says "keep this location filled up". You create these rules from a new menu under Inventory > Configuration > Warehouse Management.
- Each rule targets one location and one preferred route, and can be limited to certain products with a product filter.
- You choose when it runs: automatically when new stock moves happen, manually from the orderpoint list, or on a schedule via a background job.
- The replenishment quantity is calculated to bring the forecasted stock at the location back to zero, and it can be capped by what is actually free at the source location.
- A time horizon (in days) limits which future demand is taken into account.
- Rules are unique per company, location, route and replenishment method, and names are generated automatically.
On the location form you get a smart button showing how many orderpoints exist for that location. Generated replenishment moves are created through the normal procurement engine, get assigned automatically, and inherit the rule's priority. A scheduled action processes the rules marked as scheduled.
Required by other modules
Menus it adds
Models and fields (7)
- stock.move · extends an existing modellocation_orderpoint_id
- stock.rule · extends an existing model
- stock.location · extends an existing modellocation_orderpoint_ids (Location Orderpoints), location_orderpoint_count
- stock.location.orderpoint · new modelname, active, trigger, group_id, priority, route_id (Preferred Route), sequence, company_id, location_id, proc_run_async (Delay procurement execution), location_src_id, replenish_method, replenish_horizon (Replenishment horizon (in days)), last_cron_execution, product_domain_char (Product domain), replenish_limit_to_free_qty (Limit replenishment to free quantity at source location)
- stock.location.orderpoint.strategy · new model
- stock.location.replenishment.computer · new modelhorizon (Horizon Datetime), location_id (Destination Location), product_domain, location_src_id (Source Location), excluded_location_domain, replenish_limit_to_free_qty
- stock.location.orderpoint.strategy.fill_up · new 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. The module is very large and only part of the code was read. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 3 confirmed, 6 with no information of 9 versions.
Sources · Odoo 18.0
Confirmed on 2026-11-03 in branch 18.0 of OCA/stock-logistics-orderpoint.
terminal Installation and usage
OCA documentation · Odoo 18.0Configuration
Source · Odoo 18.0First configuration
- In order to replenish your stock location from another one, you first need to set the multi locations configuration.
- So, go to Inventory \> Configuration \> Settings \> Warehouse
- Check the 'Storage Locations' box.
- As you should be able to configure a dedicated route to replenishment, you should also activate, in the same menu, the 'Multi-Step Routes' box.
Locations configuration
- Identify the location you want to apply a replenishment rule (e.g.: WH/Stock)
- Create (if not exists) a new location for replenishment under Warehouse view (e.g.: WH) location as we want to get the stock in replenishment taken into account of our product stock total quantity.
Route Configuration
- You should configure at least a route with a rule that: > - Pull from the Replenishment stock location. > - For the stock location you want to (e.g.: WH/Stock)
Location Orderpoint configuration
- Go either by the stock location you want to replenish and click on 'Orderpoints' or go to Inventory \> Configuration \> Warehouse \> Stock Location Orderpoint
- Click on 'Create'
- Set a sequence
- Choose if the rule will be applied: > - Automatically (Auto/realtime): at each stock movement on the > stock location, the rule will be evaluated. > - Manually (Manual): If set, an action 'Run Replenishment' will be > displayed on the rule and allow to run it manually. > - by cron (Scheduled): A cron job will trigger the replenishment > rules of this kind.
- Choose a replenish method: > - Fill up: The replenishment will be triggered when a move is > waiting availability and forecast quantity is negative at the > location (i.e. min=0). The replenished quantity will bring back > the forecast quantity to 0 (i.e. max=0) but will be limited to > what is available at the source location to plan only reservable > replenishment moves.
- Choose the location to replenish
- Choose the route to use to replenish. The source location will be computed automatically based on the route value.
- Define a procurement group if you want to group some movements together.
- Define a priority for the created moves.
- If you want to filter the stock locations that should be taken in consideration for product available quantities when triggering a replenishment (e.g.: Supplier locations - to avoid confirmed receptions taken into account), fill in the 'Domain to filter locations' field.
When different orderpoints are defined on the same location, it could result in the creation of several replenishment moves for the same product. When this happens, if the moves are merged together, the resulting move will be linked to the orderpoint with the highest priority, ensuring that the move inherits the correct priority and is processed accordingly.
No verified information in OCA: Installation, Usage.
Installation 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.