Transport
The Transport Management Systems (TMS) module manages the workflow of creating transport operations within Odoo. This module provides features such as creating teams, stages, crews, routes, and vehicles, allowing businesses to efficiently handle various aspects of their transport operations.
Table of contents
Configuration
TMS module can be used with advanced configuration that enable extra features complementing the base module.
Units of Measure
In the base module units of measure (UoM) aren’t considered. They have to be manually enabled in the settings.
Go to TMS > Configuration > Settings > Units
Activate the “Units of measure” checkbox and save the changes
Now UoM appear in the module in the distance, length, weight and time fields with a default unit that is computed.
To change the default UoM of an specific magnitude, select the default UoM in its corresponding measurement in the settings.
Manage teams and crews
Team management is an advanced feature that can be configured in the TMS module. They are a predefined group of employees that have predefined drivers and vehicles. “Mexican Transportation Company”, i.e., has the “Mexico City Team” and “Querétaro Team” with their own vehicles and drivers.
Go to TMS > Configuration > Settings > Drivers
Activate the “Manage Teams” checkbox and save the changes
Go to TMS > Configuration > Drivers > Teams
A default team is created. Edit this team or create a new one
Write the team’s name, select the drivers and the vehicles
If it’s configured, you can also select crews for this team
When a trip is created, you can assign the trip to an specific team.
Crew management is an advanced feature that can be configured in the TMS module. They are a predefined group of drivers and employees in a vehicle. An airplane, i.e., has its pilots and crew members that attend the passengers.
Go to TMS > Configuration > Settings > Drivers
Activate the “Manage Crews” checkbox and save the changes
Go to TMS > Configuration > Drivers > Crews
Create a new crew and assign it a name
Select the drivers, the personnel, and a default vehicle that the crew uses
When a trip is created, you can assign the trip to an specific crew
Routes and stop locations
Routes can be used to establish predetermined trips from one location to another.
Go to TMS > Configuration > Settings > Trips
Activate the “Routes” checkbox and save the changes
Go to Master Data > Routes and create a new route
Write the route’s name, select the origin location and select the origin destination
Create a new trip and enable the “Use a predefined route” checkbox
Select the route you have created for the trip
When activating routes in the settings, the option for creating stop locations in routes is enabled.
Go to TMS > Configuration > Settings > Trips
Activate the “Stops” checkbox and save the changes
Go to Master Data > Routes and create a new route or select and existing one
Enable the “Stop locations” checkbox
Write the locations in the “Stop locations” page
Usage
Vehicles
Go to TMS application.
Go to Master Data > Vehicles in the menu.
Create a new vehicle with the desired model (required).
In the TMS page select the operation type (Cargo/Passenger).
Type the capacity of the vehicle.
Drivers
Go to TMS application.
Go to Master Data > Drivers in the menu.
Create a new driver.
Locations
Go to TMS application.
Go to Master Data > Locations in the menu.
Create a new location.
Orders
Go to TMS application.
Create a new trip from the dashboard.
Select a driver, a vehicle, an origin location and a destination location.
In the planning page select the start date, the duration and the scheduled end.
Once confirmed, click ‘START’ button to start the trip.
Once the trip is completed, click ‘END’ button to end the trip.
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
Santiago Rodriguez srodriguez@opensourceintegrators.com
Edgar Martinez emartinez@opensourceintegrators.com
-
Maxime Chambreuil <maxime.chambreuil@graymatterlogic.com>
Israel Cruz israel.cruz@argil.mx
Alan Ramos alan.ramos@jarsa.com.mx
Luis Triana luis.triana@jarsa.com.mx
Sarai Osorio sarai.osorio@jarsa.com.mx
Oscar Garza oscar.garza@jarsa.com.mx
Hector Camacho hector.camacho@jarsa.com.mx
Luis Miguel Guzmán miguel.ruiz@jarsa.com.mx
Isabel Ávila isabel.esparza@jarsa.com.mx
Erick Reza alexis.reza.s@gmail.com
Tecnativa: * Sergio Teruel * Carlos Dauden
Other credits
Open Source Integrators https://opensourceintegrators.com
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 maintainers:
This module is part of the OCA/stock-logistics-transport 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-tms 19.0.1.2.0.2
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 | Actions Reset |
|---|---|---|---|---|
| odoo_addon_tms-19.0.1.2.0.2-py3-none-any.whl | Python 3 | none | any | Details for odoo_addon_tms-19.0.1.2.0.2-py3-none-any.whl |
Release files / odoo_addon_tms-19.0.1.2.0.2-py3-none-any.whl
| Download URL | odoo_addon_tms-19.0.1.2.0.2-py3-none-any.whl |
|---|---|
| Size | 124.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ec294460313ccb72d64efd3555d73926c78cbcdcc66bc811ce91e4c82d99174b
|
|
BLAKE2b-256 checksum How to use checksums |
db317e387e806ec4353559e0754eb184ea9105904e162fa374abe5da5fec6d72
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for odoo-addon-tms 19.0.1.2.0.2
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.