Transport Management System (TMS) for Odoo is a build-to-order module that ECOSIRE designs, builds, installs and supports on your own Odoo 17, 18 or 19 database — not an off-the-shelf apps.odoo.com download. If you run your own delivery fleet, your operation lives in three disconnected places today: a spreadsheet for the daily dispatch board, WhatsApp for driver instructions, and Odoo Sales/Accounting for the money. Trips get double-booked, drivers show up without a manifest, and freight charges get invoiced late (or forgotten). This module closes that gap by making the trip a first-class object inside Odoo, wired directly to the customers, products, deliveries and invoices you already manage.

At the core is a new tms.trip model (extending models.Model) that represents a single load or run: origin, destination, an ordered set of stops, the assigned driver and vehicle, scheduled and actual departure/arrival, and the freight lines to be billed. Stops are child records (tms.trip.stop) with sequence, contact, pickup-or-delivery type, planned window and captured proof of delivery. Computed fields with @api.depends roll up total distance, estimated duration, load weight/volume and total freight cost so planners see feasibility before they commit a truck. A Kanban dispatch board and a Gantt-style planning view (OWL/XML) let dispatchers drag trips onto drivers and vehicles, while a status flow (draft → planned → dispatched → in transit → delivered → invoiced) drives what everyone sees.

Because it is native Odoo, the module reuses fleet.vehicle for your trucks and vans, hr.employee or a dedicated driver profile for drivers, res.partner for shippers/consignees, and links each trip back to stock.picking deliveries and sale.order lines where relevant. Freight is priced per trip line — by distance, weight, pallet, container or flat rate — and a "Create Invoice" action generates a standard account.move so billing stays in one ledger with the rest of your accounting. Driver settlements, fuel and toll costs are captured as trip expenses so you can see true margin per run.

Security is enforced the Odoo way: ir.model.access.csv grants define what Dispatcher, Driver and Manager groups can read or write, and record rules keep a driver scoped to only their own assigned trips (and, in multi-company setups, to their own company). QWeb reports produce a printable trip sheet / manifest and a delivery note the driver carries, plus a proof-of-delivery PDF. Automated actions and scheduled crons handle the repetitive work — auto-flagging overdue trips, notifying the next stop's contact, and escalating a trip that has been sitting in "dispatched" too long. Everything is reachable over Odoo's XML-RPC / JSON-RPC API, so a driver mobile app, a telematics feed or a customer portal can push and pull trip data without a separate integration layer.

ECOSIRE builds the module to your fleet's real workflow — your stop types, your freight rate rules, your document layouts — tests it against Odoo 17, 18 and 19 (Community or Enterprise), and installs it on your server or hosting with your data. Typical delivery is one working week depending on scope. You receive the full source, a configured working system, documentation, admin and dispatcher training, and a support window. Nothing is a black box: the code is yours, standard Odoo, and upgradeable.