| 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
NextERP Romania
NextERP Romania is a leading provider of integrated business management solutions, specializing in Odoo ERP implementations and customizations. With a strong focus on innovation and customer satisfaction, NextERP delivers scalable and efficient solutions tailored to the needs of Romanian businesses.
About Us
- Expertise: Over 10 years of experience in ERP, CRM, and business process automation.
- Services: Odoo implementation, customization, support, and training.
- Clients: Serving a wide range of industries including retail, manufacturing, and services.
Contact Us
For more information or to request a demo, contact us using the options below:
Visit our website: https://nexterp.ro
Table of contents
Use Cases / Context
Stock Auto Reorder Transfer
Context
stock_auto_reorder_transfer automates internal stock replenishment between warehouses based on product categories. Instead of maintaining orderpoints per product manually, a single rule covering an entire product category automatically creates and keeps orderpoints in sync as products are added or removed from that category.
Typical use-cases:
- Central warehouse → regional hub replenishment where all SKUs within a category should flow through the same route
- Multi-company or multi-warehouse setups where transit locations are required for inter-company compliance
- Operations teams that want zero-config replenishment as the product catalog grows
Key Concepts
| Concept | Description |
|---|---|
| Config | Top-level record binding the source warehouse and one or more transfer rules |
| Rule Line | Defines a destination warehouse, category set, trigger type, and optional transit location |
| Trigger Type | auto (triggered immediately) or manual (requires manual action) |
| Use Transit Location | Routes stock through an intermediary location (auto-created per rule if missing) |
| Orderpoint | Odoo stock.warehouse.orderpoint created/updated per product per rule; keeps min/max at 0 so replenishment fires whenever stock is needed |
How Automation Works
- Create a config with source warehouse and add rule lines.
- The module auto-creates picking types, routes, and orderpoints for every product in the selected categories.
- When the product catalog changes (product added or removed from a category), a compute hook updates the orderpoints automatically.
- Pressing Recreate Orderpoints forces a full rebuild for a rule.
Configuration
Configuration Guide
Navigation
Go to Inventory → Configuration to find the Auto Reorder Transfer section.
1. Create a Transfer Config
- Go to Inventory → Configuration → Auto Reorder Transfer → Reorder Transfer Configs.
- Click New and set:
- Configuration Name — descriptive label (e.g. Central → Hubs).
- Source Warehouse — the warehouse from which stock will be pushed.
2. Add Rule Lines
In the Reorder Rules tab, add one row per destination:
| Field | Required | Description |
|---|---|---|
| Destination Warehouse | Yes | Where stock should be sent |
| Product Categories | Yes | One or more categories; all storable products in these categories get an orderpoint |
| Trigger Type | Yes | Automatic — fires immediately on replenishment need; Manual — needs manual action |
| Use Transit Location | No | Tick to route through an auto-created transit location (needed for inter-company flows) |
| Transit Location | No | Auto-filled when “Use Transit” is ticked |
3. Save and Verify
On save the module automatically creates:
- A picking type per rule (e.g. INT: Demo Central Warehouse -> Demo North Hub)
- A route linking source to destination
- An orderpoint (stock.warehouse.orderpoint) for every storable product in each selected category
Verify the auto-created objects:
| Object | Where to find |
|---|---|
| Picking types | Inventory → Configuration → Operations Types |
| Routes | Inventory → Configuration → Routes |
| Orderpoints | Inventory → Operations → Replenishment |
4. Maintaining Orderpoints
- Add/remove products from a tracked category — orderpoints are refreshed automatically.
- Use the Recreate Orderpoints button on a rule line to force a full rebuild if something looks out of sync.
Security
Only users with the Inventory: Manager group can create or modify configs and rules.
Usage
Usage Guide
Day-to-Day Operation
Once configured, the module runs without manual intervention:
- Every time a replenishment need is detected for a product whose category is covered by a rule, Odoo creates an internal transfer picking from the source warehouse to the destination warehouse (directly or via transit location).
- The picking follows the standard Odoo transfer lifecycle: draft → confirmed → done.
Config List View
All configurations are listed at Inventory → Configuration → Auto Reorder Transfer → Reorder Transfer Configs.
Config Form — Rule Lines
The form shows the source warehouse at the top, and the Reorder Rules tab lists all destination rules. The Picking Type and Stock Route columns show the objects the module auto-created.
Manual Flow (Trigger Type = Manual)
- Go to Inventory → Operations → Internal.
- Filter by the relevant picking type (e.g. INT: Demo Central Warehouse -> Demo North Hub).
- Validate the transfer when the physical goods have been dispatched.
Recreating Orderpoints
If the product catalog or categories change and you want to ensure all orderpoints are up-to-date:
- Open the config form.
- Click Recreate Orderpoints on the relevant rule line row.
Checking Auto-Created Objects
| Object | Where to find |
|---|---|
| Picking types | Inventory → Configuration → Operations Types |
| Routes | Inventory → Configuration → Routes |
| Orderpoints | Inventory → Operations → Replenishment |
Development
🇷🇴 NextERP Romania
Romanian Localization 🇷🇴
Note: For each Odoo version, NextERP provides and maintains over 80% of the Romanian Localization modules and translations, ensuring comprehensive coverage and up-to-date compliance.
Everything you need for Odoo in Romania:
- 🧾 SAF-T & e-Factura & e-Transport compliance
- 💸 ANAF integration for tax & invoice reporting
- 📄 Romanian chart of accounts & fiscal positions
- 📝 Localized reports
Declaration Modules:
| 
Other Services
- ⚙️ Odoo Customization
- 🛠️ Odoo Implementation
- 🛟 Odoo Support
- 🔄 Odoo Migration
- 🧩 Odoo Integration
- 💬 Odoo Consultancy
📞 Contact Us
- 🌍 Website: nexterp.ro
- ✉️ Email: contact@nexterp.ro
- 🏢 Phone: +4 0770 816455
For tailored Odoo solutions and expert advice, reach out to NextERP Romania today!
Bug Tracker
Bugs are tracked on NextERP Issues. In case of trouble, please check there if your issue has already been reported.
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