Route Planning Stock Integration
Integration between Route Planning and Stock to automatically generate routes and checkpoints from pickings.
This module automates route and checkpoint creation directly from stock pickings and integrates inventory transit locations and stock rules into Route Planning workflows.
Key Features:
Automatic generation of a Transit Location per Route Area and corresponding stock rules.
Automatic route and checkpoint generation upon picking validation.
Automated validation of pickings when route checkpoints are marked as completed.
When you use the transit location created for the Route Area, the delivery is performed in two steps:
The first step moves the stock from the internal location where it is stored to the transit location. This movement represents the physical transfer from your warehouse to the transport vehicle that will perform the delivery. A second picking is created when you validate the first picking. This picking waits for the corresponding checkpoint to be completed when the delivery is completed at the customer. Once the checkpoint is completed, the picking is automatically validated.
Note: For better integration and simplicity, we recommend using this module with the route_planning_delivery module installed.
Table of contents
Configuration
Go to Inventory / Configuration / Settings.
Enable Storage Locations and save.
Configuring Route Areas
Go to Route Planning / Configuration / Areas.
Create or edit a Route Area.
Set the Warehouse if you have more than one warehouse. Otherwise, the system will use the default warehouse for your company.
Upon saving, the system will automatically:
Create or update a Transit Location under the warehouse view location.
Create or update stock rules linking the warehouse stock location, the route area transit location, and the customer location.
Creating or Editing an Operation Type
Go to Inventory / Configuration / Operation Types.
Create or edit an operation type.
Set the Destination Location field to the transit location created automatically by the Route Area.
Usage
Create a Delivery Order using an operation type whose Destination Location is the transit location created automatically by the Route Area.
Assign the Route Area to the picking.
Confirm / Validate the picking.
The system will automatically search for an existing draft route for that area and scheduled date, or create a new Route.
A Route Checkpoint is created and linked to the picking and its partner.
Go to the Route and plan it.
When the visit to the customer is completed, validate the checkpoint. This will automatically validate the picking.
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
Pedro M. Baeza
Víctor Martínez
Carlos Lopez
Maintainers
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
Current maintainer:
This module is part of the OCA/route-planning project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
Metadata
Release files for odoo-addon-route-planning-stock 18.0.1.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| odoo_addon_route_planning_stock-18.0.1.1.4-py3-none-any.whl | Python 3 | none | any | Details |
Release files / odoo_addon_route_planning_stock-18.0.1.1.4-py3-none-any.whl
| Download URL | odoo_addon_route_planning_stock-18.0.1.1.4-py3-none-any.whl |
|---|---|
| Size | 45.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
446a43da093b3fbe31f8111590102aaab7d008a7040354c69ec6f583724ebfe2
|
|
BLAKE2b-256 checksum How to use checksums |
7de1f61b9b4047f7660bd46fff86551913f1ac7dba5e8fcd23d3b7e7e5d7e951
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Security for odoo-addon-route-planning-stock 18.0.1.1.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.