Trips and planning
One list of all trips, colour-coded statuses, saved filters per dispatcher.
An international road haulier ran trips, invoices and drivers on Google Sheets and WhatsApp. In 8 weeks I moved everything into one system with GPS tracking, AI checks and automated invoicing.
TMS = Transport Management System. The system where a transport company runs its orders, trips, fleet, documents, invoicing and payments, all in one place.
An international road haulier with its own fleet and subcontractors. Until September 2026 this is how operations ran:
I built a dedicated TMS starting from their own spreadsheets: imported the whole trip history, kept the words and the order they worked in, then rolled it out module by module while the team kept working. Today a trip is entered once and flows from there: the subcontractor order, GPS tracking, document checks, the invoice and the margin.
Click a screenshot to enlarge it. Client data, amounts, addresses and registration numbers are hidden.
One list of all trips, colour-coded statuses, saved filters per dispatcher.
A client order becomes a trip in minutes, with a code, stops and a PDF order for the subcontractor.
Statuses update themselves from GPS; alerts when a truck runs late or leaves its route.
AI reads the client order and the CMR, compares them with the trip and proposes fixes in one click.
Invoices issued from the TMS into the accounting software, emailed with the documents attached.
Real km from the truck's CAN / GPS computed after each delivery and compared with planned km.
Subcontractor invoices, bank statements matched automatically, margin on every trip.
3D load planner, tachograph simulator, live fleet map.
Aggregated figures from the system on 17 Nov 2026. The system has been live since 23 Sep 2026.
The team works in one place, with the full trip history imported from the sheets. Loadings and deliveries are confirmed straight from GPS, and client orders and CMRs are read and checked by AI before invoicing.
Every change has an author and a timestamp. Real km from the truck computer are calculated after each delivery and compared with the planned km: a difference nobody could see before.
Started from the existing sheets and how each person works.
The sheet history moves in, cleaned and checked.
One module at a time, in parallel with the sheets, until they are no longer needed.
Team requests ship the same or next day: 380+ updates in 8 weeks.
Every module below already runs in production at the client in this case study.
Best for: Any company that receives orders by email or WhatsApp
Best for: Own fleets with GPS (WebEye / Eurowag or any provider with an API)
Best for: Companies with lots of paper or PDF documents
Best for: Companies invoicing in several countries or currencies
Best for: Companies with own drivers and subcontractors
You are not buying boxed software: I build on your process, starting from the very spreadsheets you use today.
Tell me what you use today and in 30 minutes I'll show you what can be automated.
TMS stands for Transport Management System: the application where a transport company manages its orders, trips, fleet, documents, invoicing and payments. I do not sell a boxed TMS: I build it to measure (tailored, custom made), starting from each client's process.
No. Both run in parallel until the system covers them.
Yes, if the provider has an API (e.g. WebEye / Eurowag, FGO, SmartBill, Xero).
First modules in 2–4 weeks; this project, everything in 8.
Yours: it runs on your server, with your data.
No: the same approach fits any company that has outgrown its spreadsheets.
Case study by Codrin Chicuș · published 17 November 2026