Trip planning and dispatch board
Build a trip with vehicle, driver, stops, and load lines. Move it from planned to dispatched to in transit from one board.
Plan trips, dispatch trucks, bill freight, and let customers track deliveries in one Odoo desk.

Trusted by clients worldwide



















Carriers still run dispatch in spreadsheets, GPS in a separate login, and billing in Accounting after the truck is back. That split is what leaks margin: missed accessorials, late POD, and no shared view of which trip is late. PySquad TMS is an Odoo app plus implementation. It sits on Fleet, Sales, Inventory, and Accounting so a trip, a shipment, a tariff, and an invoice are the same record trail. English and Arabic. GPS is optional and uses a configured provider, not a promised live map on day one.
Dispatch, tracking, and freight billing do not share one trip record
Dispatchers assign work by phone. Drivers send status on WhatsApp. Finance rebuilds freight from trip sheets, then argues over waiting time and extra stops. LTL work (several customers on one truck) makes that worse: one missing POD blocks several invoices. Standalone GPS does not create a bill. Spreadsheets do not know vehicle capacity or contract tariffs. Customers get a tracking link that is already stale. The cost is not one bad trip. It is every week of trips you cannot price or prove.
Common approaches
Where it falls short
Does this match your constraints?
Talk to us before you commit to another generic build.
See how the system looks and moves before you decide scope.
Product walkthrough
How the system is structured and how teams move through the main workflows.
Building blocks that keep delivery predictable under real operating load.
Build a trip with vehicle, driver, stops, and load lines. Move it from planned to dispatched to in transit from one board.
Take a customer shipment onto a trip. Several customers can share one truck. Print bill of lading and delivery receipt.
Price from contracts, tariffs, and accessorials, then post customer invoices in Accounting from the trip.
Drivers open assigned trips on a phone browser, update stops, and capture proof of delivery. This is the Odoo portal, not a separate mobile store app.
A tracking number for guests, plus a logged-in portal so customers can follow shipments and request a move.
Optional GPS providers, positions, and ETA snapshots on the trip. Live map data needs a configured source. It is not automatic at install.
Vehicle readiness, maintenance requests, and driver costs sit next to the trip, on Odoo Fleet.
An operations dashboard for open trips and exceptions. Hand a job to an outside carrier when your own fleet cannot take it.
Drivers get a mobile app for assigned trips, stop updates, and proof of delivery on the road, so dispatch is not waiting on calls or chat screenshots.
Step 1
Map dispatch, LTL vs FTL, subcontracting, and how you invoice freight today
Step 2
Install and configure PySquad TMS on your Odoo (zones, vehicles, tariffs, roles)
Step 3
Turn on driver portal POD and customer tracking before any GPS work
Step 4
Connect a GPS or telematics provider only if you already use one
Step 5
Train dispatch, billing, and a pilot set of drivers on the real trip flow
Step 6
Go live with reports for trip cost, freight, and on-time delivery
We start from how you dispatch today: own fleet vs subcontract, FTL vs LTL, and how you price freight. Then we configure PySquad TMS on Odoo: zones, route templates, tariffs, accessorials, driver portal POD, and customer tracking. GPS and telematics are wired only when you have a provider. You get one operations desk, not a slide deck.
What teams plan for when scope, integrations, and release are handled as one program.
Same-day dispatch from one board instead of chat and spreadsheets
Fewer missed accessorials because extra stops and waiting time sit on the trip
POD and tracking attached to the shipment, not lost in a phone thread
Finance invoices from trip data in Odoo Accounting
PySquad TMS is the operations layer for carriers who already run (or will run) Odoo. It is not a generic GPS login and it is not only a freight invoice screen. Dispatch plans the trip. The driver updates stops and proof of delivery. Billing uses the same trip. The customer tracks a number you already issued.
The product is the Odoo module Transport Management System on Community or Enterprise, with Multi Language support. We implement it against your zones, tariffs, and roles. Optional GPS needs a provider you name. Optional work includes extra rate logic, carrier EDI, or a branded tracking page.
Product page: TMS on the PySquad app store.
Straight answers procurement and engineering teams ask before a build kicks off.
Yes. Odoo TMS can integrate with GPS fleet tracking platforms, telematics devices, and vehicle monitoring systems. This allows dispatchers and operations managers to view vehicle locations, monitor trip progress, calculate estimated arrival times, and improve fleet visibility without switching between multiple applications.
Yes. Odoo Transport Management System is well suited for transportation businesses expanding their fleet size, service areas, or shipment volumes. The platform supports additional vehicles, drivers, routes, and locations while maintaining centralized operational visibility and consistent transport management software processes.
It is an Odoo module plus our implementation. You plan trips, dispatch vehicles and drivers, carry one or many customer shipments on a trip, price freight, capture proof of delivery, and invoice from Accounting. Tracking and GPS are part of that trip record when you switch them on.
Yes, Drivers get a mobile app for assigned trips, stop updates, and proof of delivery on the road, so dispatch is not waiting on calls or chat screenshots.
A software engineering team for complex operations. We build tools that fit how you work, not software that forces you to change everything overnight.
Discovery, build, integrations, testing, release, and follow-up once real users are in the product. You talk to engineers and leads who own the outcome.
Share scope, constraints, and timelines. We respond with a clear delivery approach, not a generic pitch deck.
Start the conversationReady modules from the same team. Pick the Odoo version you run, then download that zip.
Other areas you may want to compare.
Tell us what you are building, which systems matter, and the outcome you need. We reply within 24 hours with a clear next step.
50+ teams · Production-ready delivery · Reply within 24h
Prefer a structured brief?