| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Inventory (stock)
• Discuss (mail) |
| Lines of code | 421 |
| Technical Name |
stock_auto_reorder_transfer |
| License | OPL-1 |
| Website | https://www.nexterp.ro |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Inventory (stock)
• Discuss (mail) |
| Lines of code | 421 |
| Technical Name |
stock_auto_reorder_transfer |
| License | OPL-1 |
| Website | https://www.nexterp.ro |
Stock Auto Reorder Transfer
Automatic reordering rules for internal transfers between warehouses.
Overview
This module extends Odoo's reordering engine with warehouse-to-warehouse auto-replenishment. The standard reordering rules cover supplier purchases and manufacturing, but leave internal transfers between warehouses to be configured product by product — this module fills that gap by driving the flow from a single category-based configuration.
A configuration binds one source warehouse to a list of destination warehouses, each tied to a set of product categories. On save, the module auto-creates the matching stock route, picking type(s) and orderpoints for every storable product in those categories. A direct one-step transfer is generated by default, and a two-step flow through a transit location is available for inter-company or cross-site moves.
Whenever a product changes category, the orderpoints follow automatically, so the replenishment perimeter stays in sync with the catalog without any manual maintenance.
Built & supported by NextERP Romania
Romanian Odoo specialists, here for the long run — from implementation to localization and day-to-day production support.
What we do
Odoo Solutions
From quick-start rollouts to multi-company deployments and custom modules built for your processes.
Romanian Localization
SAF-T (D406), e-Factura, e-Transport, D300 / D390 / D394, ANAF integration, full chart of accounts and fiscal positions.
Our Services
Implementation, customization, migration, integration, support and consultancy — Romanian-speaking, SLA-backed.
Features
- Category-driven replenishment — a single rule covers every storable product in one or more product categories, instead of declaring orderpoints product by product.
- Source/destination pairs — each configuration ties one source warehouse to multiple destination warehouses, with their own categories and trigger type.
- Automatic route and picking type creation — saving a rule
generates the matching
stock.route, picking type and pull rules on the fly; the user only picks warehouses and categories. - One-step or two-step transfers — direct internal transfer by default, or via an auto-created transit location when inter-site flows must be tracked separately.
- Self-maintaining orderpoints — moving a product into or out of a tracked category adds or removes its orderpoint automatically.
- Manual or automatic trigger — choose per rule whether replenishment fires immediately when stock is needed or waits for a scheduled run of the orderpoints.
- Recreate Orderpoints action — a button on each rule line forces a full rebuild of the orderpoints, useful after bulk catalog changes.
Configuration
All setup happens under the Inventory configuration menu. The user must belong to the Inventory: Administrator group.
1. Open the configuration menu
Go to Inventory → Configuration → Auto Reorder Transfer → Reorder Transfer Configs.

2. Create a transfer config
- Click New and fill in:
- Configuration Name — a descriptive label
(e.g.
Central → Hubs). - Source Warehouse — the warehouse from which stock will be pulled.
- Configuration Name — a descriptive label
(e.g.
- Save the record. The list view groups all configs by source warehouse for quick review.

3. Add reorder rules
In the Reorder Rules tab, add one row per destination warehouse:
| Field | Description |
|---|---|
| Destination Warehouse | Target warehouse that should be replenished |
| Product Categories | One or more categories; all storable products in them get an orderpoint |
| Trigger Type | Automatic runs as soon as a need is detected, Manual waits for the scheduler |
| Use Transit Location | Tick to route through a transit location (created automatically if missing) |
| Transit Location | Auto-filled when Use Transit is ticked |
| Picking Type / Stock Route | Read-only; populated by the module on save |

4. What the module creates
On save, the module generates the following objects per rule line:
| Object | Where to find it |
|---|---|
| Stock route | Inventory → Configuration → Routes |
| Picking type(s) | Inventory → Configuration → Operations Types |
| Orderpoints | Inventory → Operations → Replenishment |
A duplicate destination warehouse across rules is rejected to avoid conflicting routes.
5. Keep orderpoints in sync
- Adding or removing a product from a tracked category updates the orderpoints automatically.
- Click Recreate Orderpoints on a rule line to force a full rebuild after large catalog changes.
How it works
Once the configurations are saved, replenishment happens through the standard Odoo orderpoints engine — no extra wizard is required.
Automatic flow (Trigger Type = Automatic)
- A stock move or sale creates a need on a product whose category is covered by a rule.
- The orderpoint fires and, through the auto-created stock route, generates an internal transfer from the source warehouse to the destination warehouse.
- If Use Transit Location is ticked, two chained pickings are created: source → transit, then transit → destination.
- The internal transfer follows the normal lifecycle (draft → confirmed → done) and can be processed by the warehouse team like any other picking.
Manual flow (Trigger Type = Manual)
- The orderpoint still computes the replenishment need but waits for the scheduled Run Scheduler action (or a manual run).
- Open Inventory → Operations → Replenishment to review proposed quantities and confirm them.
- The transfer is then created with the same picking type as the automatic flow.
Keeping the catalog in sync
- Move a product into a tracked category — an orderpoint is added for it on the matching rule.
- Move a product out of a tracked category — its orderpoint is removed from the rule.
- For ad-hoc reconciliations, use the Recreate Orderpoints button on a rule line.
Where to look
| What to check | Menu |
|---|---|
| Internal transfers generated | Inventory → Operations → Transfers |
| Pending replenishments | Inventory → Operations → Replenishment |
| Routes used by the module | Inventory → Configuration → Routes |
Screenshots
Captured from a running Odoo instance.
Action stock auto reorder transfer config
Versions
19.0.1.0.0 (2026-05-25)
- Changelog tracking starts at this release.
Discover the NextERP suite
Other modules from the same publisher, built to work together.
NextERP Romania
Odoo implementation, customization, Romanian localization and long-term support since 2018.
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module