Transport Management System (TMS) for Odoo

This is a build-to-order module, not an instant apps.odoo.com download. ECOSIRE builds it to your fleet's actual workflow, tests it on your target Odoo version, and installs it on your database. Typical delivery is 2 to 4 weeks depending on scope — simpler dispatch-only builds land sooner, and heavier freight-rate logic or telematics/portal integrations take longer. You get a scoped timeline before work starts.

Every build includes a defined post-go-live support window for bug fixes, questions and minor adjustments. Because the module is standard Odoo and you own the full source, it is not a locked black box — you can maintain it in-house or contract ECOSIRE for enhancements. We also validate compatibility across Odoo 17, 18 and 19 so a future core upgrade has a clear path. Extended support and version-upgrade retainers are available on request.

Odoo 17, 18 and 19, on both Community and Enterprise. The module is built to work with Odoo core objects you already have — `fleet.vehicle`, `res.partner`, `stock.picking`, `sale.order` and `account.move` — so it fits whichever edition you run. If you use Enterprise-only apps, we wire the trip flow to them where it helps; if you are on Community, the module stands on its own without paid dependencies.

Yes. All trip and stop data is available over Odoo's XML-RPC and JSON-RPC API, so an external driver app, a telematics/GPS feed or a customer tracking portal can read and update trips, capture proof of delivery, and post arrival times. ECOSIRE can build or connect those integrations as part of the scope, or leave clean API endpoints for your own team to consume.

Freight is priced on trip lines using rules you define (by distance, weight, pallet, container, zone or flat rate, including customer-specific rates). A 'Create Invoice' action generates a standard `account.move` in Odoo Accounting, so freight revenue lands in the same ledger as the rest of your business — no separate billing tool, no re-keying. Trip costs like fuel, tolls and driver settlements are captured too, so you get margin per run.

Yes. Access is enforced with Odoo's native model — `ir.model.access.csv` grants define what Dispatcher, Driver and Manager groups can read or write, and record rules scope each driver to only their own assigned trips (and to their own company in multi-company setups). Nothing bypasses Odoo's permission system, so your existing user and company security carries through.

Yes. The module respects Odoo's multi-company rules — trips, vehicles, drivers and freight invoices are scoped per company, and record rules keep each branch's dispatchers seeing only their own operation. If you run one shared fleet across branches, ECOSIRE configures the sharing rules during the build so assignment and billing land in the right company.