What Is a TMS System? Transport Management Explained

Someone in the office says the new TMS goes live in March, and everyone nods. Ask afterwards what a TMS actually is and the answers diverge fast: the planning screen, the thing that makes invoices, the app the drivers complain about. All three are partly right, which is the problem.

This is a plain description of what a transport management system is, what it owns, and — more usefully — what it does not, so you can tell which system in your own company is responsible when something goes wrong.

What TMS stands for

TMS stands for Transport Management System. In Dutch it is used untranslated as often as transportmanagementsysteem, and both refer to the same thing: the system that manages freight from the moment an order is accepted until it can be invoiced.

One warning if you are searching, because it wastes a lot of people's time: TMS is also a common abbreviation in medicine, for transcranial magnetic stimulation, and separately for tension myositis syndrome. Search for the bare acronym and you will land in clinical results. Add "systeem" or "transport" and the results become the ones you wanted.

The four things a TMS owns

A transport management system is defined by the decisions it is responsible for, not by its screens. Four of them belong to the TMS and nowhere else.

1. The shipment as a record

The TMS holds the shipment: what was collected, from where, to where, under which agreement, with which requirements. This sounds administrative until a load moves across two vehicles, or gets transferred to a partner halfway. The shipment stays one record while the execution splits. Systems that model the vehicle as the core record cannot do this, and it is the single clearest test of whether you are looking at a TMS at all.

2. What may be charged

The TMS carries the tariff agreed with each customer and applies it to what actually happened. Not what was planned — what happened. Waiting time, an extra stop added by phone, a fuel surcharge for the right period. If the system that knows the price and the system that knows the events are different systems, someone reconciles them by hand every month, and that person is quietly the most important employee in the company.

3. Who does the work

Own fleet or subcontracted. Where charters are used, the TMS holds both the purchase and the sale on the same shipment, which is the only way to see whether a subcontracted trip made money before the month closes.

4. The paper trail

Consignment notes, proof of delivery, customs documents where relevant. Increasingly this is digital, and increasingly it must be produced in a structured form on request rather than as a scan someone finds in a folder.

What a TMS is not

Most confusion in practice comes from four neighbouring systems that overlap at the edges.

Not telematics

The board computer records what happened: positions, times, driving hours, fuel. It is a superb source of truth about reality and has no opinion about what should happen. It cannot price a shipment, and it does not know about work you have not accepted yet. Many telematics suppliers now sell order screens, which makes the boundary genuinely hard to see from outside.

Not planning software

Planning decides which vehicle takes which load in what sequence. It may be a module inside the TMS or a separate optimiser sitting beside it. A TMS without planning is perfectly coherent — plenty of operations plan on a board and use the TMS for everything downstream.

Not a WMS

A WMS manages goods inside one building: locations, picking, stock condition. A TMS moves goods between buildings. They meet at the dock and are otherwise unrelated. Running warehouse work on transport software is the most common cause of a stock position nobody trusts.

Not your accounting package

The financial system receives what the TMS says is billable and books it. It has no way of knowing whether that was right, which is why an error in the tariff engine is silent all the way to the customer.

How the chain actually runs

Following one shipment through makes the division of labour concrete. An order arrives — by phone, email, portal or EDI — and is entered or received into the TMS, where it becomes a shipment with a customer, a tariff and requirements. Planning assigns it to a vehicle within driving hours and time windows. The board computer carries it to the driver and reports back what actually happened, including the forty minutes spent waiting at a closed dock.

Those events flow back into the TMS, which prices the shipment against the agreed tariff — including the waiting time — and marks it billable. The financial system produces the invoice. If any link in that chain is manual, the cost is not the labour; it is that the manual step is where chargeable events quietly disappear.

What people expect a TMS to do and it does not

Three expectations come up repeatedly and all three are worth resetting early.

It will not tell you which customers are unprofitable unless you feed it costs as well as revenue. Out of the box it knows what you charge, not what you spend.

It will not fix disagreements about what was agreed. It records agreements faithfully; it does not make a vague commercial arrangement precise.

It will not plan better than the data you give it. Vehicle capacities, loading times and realistic time windows are the actual input, and most planning disappointment traces back to that rather than to the algorithm.

When you actually need one

There is no fleet size that triggers it. The threshold is complexity of tariffs and exceptions. Two signals show up reliably:

Someone maintains a spreadsheet to work out what may be invoiced. That is a revenue risk with a person standing in front of it.

One planner is the only person who understands why yesterday looked the way it did. That is a continuity risk, and it does not resolve on its own.

Below that, a good invoicing package and a shared planning board genuinely cover it, and adding a TMS adds administration rather than control.

Where to go next

We wrote a practical guide to testing a TMS before you sign, built around replaying one real week of your own orders against what you actually invoiced and drove.

wider transport software stack — TMS, planning, telematics, invoicing and WMS — maps which system owns which problem and which to buy first.

Frequently asked questions