It is 6.30 on a Monday morning. The plan is on a whiteboard, half of it is in the MD’s head, and one driver has just texted to say he is off sick. Friday’s PODs are still in a tray somewhere, and a customer has already rung to ask where their load is. If you have typed “what is a TMS” into Google, it is probably because somebody told you a transport management system fixes mornings like this. You want to know whether that is true before you sit through a sales demo. This guide explains what a TMS is in plain English, what it does from order to invoice, what it is not, and how to tell when a spreadsheet has stopped being enough.
What is a TMS?
A TMS, or transport management system, is software that runs the day-to-day work of moving goods by road: taking orders, planning which driver and vehicle does which job, sending the work to the driver, capturing proof of delivery, and turning finished jobs into invoices. It gives the office and the drivers one shared record of every job, in place of the spreadsheet, the message thread and the paper trail that usually carry it.
That is the short version. In UK haulage the term covers everything from a basic job-booking tool to a full platform, so two operators saying “we have a TMS” can mean very different things. It helps to separate the core from the extensions.
- Core TMS: a practical core TMS covers job capture, planning and allocation, dispatch and execution, delivery status and proof, and billing preparation or handoff.
- Common extensions: telematics and live tracking, route optimisation, driver walkaround checks, customer portals, automated invoicing, HGV-safe navigation, compliance records and accounts integrations. Not every TMS includes them; a more complete platform bundles several.
The rest of this guide walks the core flow first, then the extensions, so you can judge any TMS software against both.
What a transport management system does, from order to invoice
Every haulage job follows the same path: a customer asks you to move something, you plan it, a driver does it, proof comes back, and you get paid. A TMS is built around that path. When each step feeds the next, nothing is rekeyed and nothing is lost between the office and the truck.
1. Order capture
The job comes in by phone, email, a customer portal or a file upload, and it is recorded once: who the customer is, what is moving, where from, where to, and the agreed rate or tariff. On a spreadsheet the same job gets typed three times, into the plan, into the driver’s message and into the invoice. Here it is typed once.
2. Planning
The planner drags each job onto a driver and vehicle for the day, with trailers and subcontracted legs handled on the same screen as your own fleet. The system flags what the whiteboard cannot: a driver whose licence check is overdue, a vehicle off the road, a trailer already assigned. Some systems add algorithmic planning that suggests multi-stop runs; useful on complex work, less so if every truck does the same route every day.
3. Driver execution
At its simplest, dispatch means the job reaches the driver from the plan rather than being retyped. In many modern systems that is a driver app: the driver sees the day’s jobs in order, with addresses, contacts and any instructions. Two common extensions live in the same app. Where a system includes walkaround checks, the inspection is recorded against the vehicle with its date and time as part of the operational record. Where it includes HGV-safe navigation, the driver is routed for a vehicle of that height and weight rather than a car.
4. Proof of delivery
At its core, a TMS records the delivery status. The extension operators ask for first is often electronic proof of delivery (ePOD): the driver captures a signature and photos on the app, stamped with time and location. A good driver app works offline, so the POD is captured on site and synced when the signal returns, reaching the office the same day instead of travelling back in the truck. What a POD must contain and how long you have to keep it is covered in our guide to proof of delivery for UK hauliers.
5. Invoicing
Once the POD is in, the job is ready to invoice. If your rate cards are set up in the system, the price was applied at booking, so nobody looks anything up. The invoice is raised from the job, with the POD attached, and sent. We model the cash-flow impact of a seven-day invoicing delay in The Real Cost of Delayed Haulage Invoicing.
6. Accounts handoff
The system does not replace your accounts package. It hands off to it. At minimum that is an export; with a supported integration, approved invoices, credit notes and payments flow into Xero, Sage or whichever package your accountant uses, so month end stops being a rekeying exercise.
The extensions that sit alongside the spine
Because the system knows where every job is in that sequence, extensions build on it. Live tracking and an arrivals board show the traffic office what is on the road and the current ETA for each drop. A customer portal lets customers check their own loads instead of ringing you. Where checks, licences and defects are recorded in the same place as the work, the compliance evidence a Transport Manager needs for a DVSA visit is assembled as you go rather than reconstructed the night before. None of these makes something a TMS; all of them are why operators buy a fuller one.
The table below sorts the two. Core is the typical foundation of a transport management system; an extension is common and valuable, but not universal, so it is worth confirming rather than assuming.
| Capability | Status | What it does for the operation |
|---|---|---|
| Job capture | Core | One record per job: customer, goods, addresses, rate |
| Planning and allocation | Core | Driver, vehicle, trailer and subcontractor assigned to each leg |
| Dispatch and execution | Core | Work reaches the driver from the plan; status comes back |
| Delivery status and proof | Core | Delivered, claused or failed, with proof attached where captured |
| Billing preparation | Core | Finished jobs priced and ready to invoice or hand off |
| Live tracking and ETAs | Extension | Tracker positions feed a fleet view and current ETAs |
| Route optimisation | Extension | Suggests multi-stop runs; matters on complex work |
| Walkaround checks | Extension | Inspection recorded against the vehicle with date and time |
| HGV-safe navigation | Extension | Routes for the vehicle’s height and weight, in the driver app or a separate device |
| Customer portal | Extension | Customers check loads and PODs themselves |
| Accounts integration | Extension | Approved invoices, credit notes and payments flow to the accounts package |
What a TMS is not
Half the confusion around TMS software comes from neighbouring products that look similar on a logo strip. They are not the same thing, and a good one connects to them rather than pretending to be them.
- Telematics is not a TMS. A tracker’s primary role is vehicle and location data: where it is, how it is being driven. Some telematics suites add dispatch features, but they do not normally own the end-to-end transport job from order to invoice. Transport management software consumes tracker positions to show the fleet and support ETAs; it does not replace the tracker.
- A sat-nav is not a TMS. Navigation gets the driver to the postcode. It is one step of one job. Some systems build HGV-safe navigation into their driver app; many rely on whatever device the driver already has.
- An accounts package is not a TMS. Xero and Sage can raise and send invoices, and they own the ledger and VAT. What they do not do is plan, dispatch or prove delivery. In a TMS the invoice is created from the job and its POD; the accounts package books it.
- A warehouse management system is not a TMS. A WMS runs stock, locations and picking inside the building. A TMS runs the movement between buildings. Operators who do both usually run both.
One label to be careful with: “fleet management software” is often the label for telematics and vehicle-maintenance tools, not for the system that runs jobs. If a product page leads with fuel economy and driver behaviour scores, it is probably a fleet tool, not transport management software.
Do you actually need a TMS?
Plenty of UK hauliers run well on a spreadsheet, and if you have three trucks on regular work it may be the right tool. The case for a transport management system is not that spreadsheets are wrong. It is that they stop scaling at a point many operators recognise in hindsight.
The economics make the point. The RHA’s Haulage Cost Movement 2025 report puts the annual operating cost of its 44-tonne artic model at £211,180 including fuel and additive. The same report cites Motor Transport Top 100 pre-tax profit at just 2.17%. They are different benchmarks, but together they show how little room operators have for avoidable cost, wasted mileage and delayed cash collection.
Road remains central to UK freight: Department for Transport figures show that 82% of domestic freight tonne-kilometres in 2024 were moved by road. The question for any operator is not whether the work exists, but how much of the margin on it the process is quietly spending.
The practical test is whether the job record survives without one person. If the plan, the driver messages and the invoices all depend on someone re-typing them, the spreadsheet is already a TMS with a human as the database. We list the specific triggers in Warning Signs Your Haulage Business Has Outgrown Its Current Setup, and the TMS for growing hauliers page shows what the switch looks like for a 6 to 20 truck operation.
Larger operators have the opposite problem: not too little software, but too much. A TMS from one vendor, telematics from a second, an ePOD app, a checks app, a route optimiser and an accounts package can add up to six logins before the morning is out, with the data disagreeing between them. For that operator the question is not “what is a TMS” but which parts of the stack a single transport management system can absorb, and which, like the tracker, it should keep and connect to. We work that arithmetic through in The Real TMS Total Cost of Ownership.
What to look for in TMS software, if you run UK haulage
Many haulage software vendors will tick the boxes above on a feature list. The differences show up in the details that matter on a UK planning desk.
- Built for UK haulage, not adapted to it. DVSA walkaround and defect recording, pallet-network work, UK postcodes and tariff structures, and integration with the accounts packages UK accountants actually use. A platform designed for another market and configured for the UK tends to show it in the compliance and invoicing corners.
- A driver app that works offline. The M6 does not have signal everywhere. If the app cannot capture a POD without a connection, drivers can easily drift back to paper.
- Checks you can prove, not just forms you have digitised. The walkaround record should be tied to the vehicle, the driver and the time, so it stands up when DVSA asks. A regulator does not approve or certify this software; what you want is a record kept in line with DVSA guidance.
- Keep what works. Ask, in writing, which telematics providers and accounts packages the vendor supports today, and what each connection costs. In many cases a good TMS can let you keep compatible systems where they are supported; confirm your exact tracker and accounts version during evaluation rather than at go-live. HaulierMagic’s TMS integrations page lists what it connects to and the published starting prices, and we set out what to hold a vendor to in what TMS integration should actually mean.
- Pricing you can read without a quote. Some TMS pricing is per office user, some per vehicle, some by concurrent user with a tailored quote. HaulierMagic publishes its per-user TMS pricing: £99 per office user per month for teams up to 12 users and vehicles, and £79 per office user for fleets above that threshold. Driver devices are £15 per month, with NavigateMagic HGV-safe navigation available at £5 or £2 per device depending on tier. Prices exclude VAT.
- Simple to start. For many owner-operators the biggest worry is not price but complexity: too many buttons, drivers ringing the office to ask what to press. Look for role-limited screens that show each person only what they need, and ask to see the driver side on a phone, not a projector.
Moving to a TMS is not just a software purchase. It is the decision to run the business from one record of every job instead of five copies of it. The spreadsheet got you to where you are; the question is whether it can get you to where the fleet is going.
