Route Planning
Project description
Route Planning
This module allows to manage delivery routes, checkpoints, and visit windows.
Before using this module, you must configure the required master data: Route Areas, Checkpoints, and Routes. Without this data, the route planning functionality will not be operational.
Models
Route Area
Defines a geographic or logical zone used to group routes. Each area helps organize delivery operations by region or territory.
Checkpoint
Represents a specific stop or delivery point within a route. Checkpoints define the locations that must be visited, along with any time window constraints for the visit.
Route
A route is an ordered sequence of checkpoints assigned to a specific area. It defines the order in which checkpoints must be visited, making it possible to optimize daily or weekly operations for any kind of service or delivery workflow.
Visit Windows
A visit window defines the time interval during which a checkpoint must be reached. Windows are configured on the contact (partner), where one or more slots can be defined specifying the earliest arrival time (time from) and the latest allowed arrival time (time to). This allows the same availability constraints to be reused across different routes and checkpoints.
Table of contents
Configuration
Ensure that partners and your company have latitude and longitude set before using this feature.
Usage
Follow these steps before creating routes and checkpoints.
Create Areas
Go to Route Planning > Configuration > Areas and create the areas that represent the geographic or logical zones where routes will operate. At least one area is required. Each area must have a responsible user assigned.
Configure Visit Window Templates (optional)
Go to Route Planning > Configuration > Visit Window Templates to define reusable sets of time windows. Templates can later be applied to contacts to populate their visit windows quickly.
Configure Contacts
Open any contact form (Contacts app) and go to the Route Planning tab. There you can:
Assign the contact to an Area.
Define the contact’s Latitude and Longitude.
Set one or more Visit Windows, either manually or by selecting a Visit Window Template.
At least the contacts that will be used as checkpoint destinations should be configured.
Create Routes
Go to Route Planning > Operations > Routes and create a route. Assign it to an area and add the checkpoints directly from the route form. Only the areas where the current user is the responsible user are available when creating the route. A checkpoint can be linked to a contact or defined only with its own latitude and longitude. When the route is planned, the checkpoints are reordered automatically using OR-Tools, which suggests the best route based on the available coordinates and time windows.
A map button is available on the route form to visualize all checkpoints on a map.
Day-to-day operations
Users can go to Route Planning > Operations > Checkpoints to see the checkpoints assigned to them and manage the status and details of each stop. Each checkpoint also includes a map view to locate the stop geographically.
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.
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distributions
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file odoo_addon_route_planning-18.0.1.0.0.2-py3-none-any.whl.
File metadata
- Download URL: odoo_addon_route_planning-18.0.1.0.0.2-py3-none-any.whl
- Upload date:
- Size: 67.3 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.2.0 CPython/3.12.3
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
f91fea6742a4d527e7f0c71b8b0600ed8769ac0c0e41f739c00a6aea50e0efcb
|
|
| MD5 |
ce6cb1a3fcf597f6190121685c5eb489
|
|
| BLAKE2b-256 |
9b8453ad9f6a409310c69c9c0a441b386079eab64d2a9cf8d9a5958cb0caa6f1
|