Two carriers can both tell you they have a TMS and mean nothing alike. One means a map with trucks on it. The other means the system their whole business runs through.

That is not anyone being dishonest. The term covers three genuinely different kinds of software, and the gap between them is where a lot of money gets spent on the wrong thing.

Three systems, three questions

Which system answers which question
The systemThe question it answersThe question it does not
Telematics · GPS Where is the truck, how fast, how much fuelWhat was agreed, and what this trip earns
TMS What was promised, who is driving it, what it earnsPayroll, the ledger, the tax return
ERP What the company owns, owes and earnsWhich truck goes where this morning

Most carriers already own the first one. Owning it is often mistaken for owning the second.

Telematics is a sensor feed. It is genuinely useful and it is not a management system: it can tell you a truck has been standing still for two hours, but not whether anyone can be invoiced for that.

An ERP is the company’s books. It knows what a customer owes. It does not know that the customer owes it because of a load collected on Tuesday that is still sitting at the border.

A TMS is the thing in between, and it is the one most carriers are actually missing.

What a TMS actually holds

Strip away the feature lists and a TMS does one job: it carries the trip from the first phone call to the money arriving, without it being written down again at each hand-off.

That journey has a fixed shape, and every stop on it is somewhere a trip currently gets retyped:

  • The request and the price. What was quoted, against which tariff, and what the contract already says about this customer.
  • The order and its checks. Credit limit, cargo type, whether this truck may carry it at all.
  • Planning. Which truck, which driver, which trailer, and what each of them is already committed to.
  • The task on the driver’s phone. Not a message in a chat that scrolls away by lunchtime.
  • The documents. CMR, delivery note, e-qaimə, built from the trip rather than typed beside it.
  • The road. Loading, waiting, border hours, delivery confirmed where it happens.
  • The money. Act and invoice from the same trip, and the payment finding its own invoice.

Signs you need one

  1. Nobody can tell you today’s margin on a trip. The revenue is in one place, the fuel in another, the driver’s pay in a third. Profit per trip is something you work out later, if at all.

  2. Dispatch lives in one person’s head. When that person is on holiday the week runs worse, and everyone knows it. That is not a staffing problem, it is a missing system.

  3. The same trip exists in four places. A call, a spreadsheet row, a chat message and an accounting entry — none of which knows about the others when something changes.

  4. Documents are typed after the fact. CMR, acts and e-invoices are produced separately from the trip they describe, usually at month end, usually in a hurry.

  5. Customers know things before you do. A customer calls to say their load has not arrived, and that call is how you find out. The information existed; it just was not anywhere you could see it.

Two or three of these and a TMS will pay for itself. One, and the honest answer is to fix that one thing.

Who does not need a TMS

This is the part that rarely gets said by anyone selling one.

  • An own-account fleet. If your trucks move your own goods, there is no customer to invoice for a trip, no tariff and no demurrage. Half a TMS has nothing to do. What that operation needs is maintenance, fuel control and a delivery app — a much smaller thing.
  • A very small operation that is working. If one dispatcher holds the day in their head and the month closes cleanly, a TMS will add administration before it removes any. Wait until it stops working, which it will, and you will know the week it happens.
  • A company whose trucks are half empty. Software that runs trips better does not create trips. If the problem is finding loads, a TMS is an expensive way to avoid a sales conversation.

If both the sales problem and the operations problem are real, fix whichever is cheaper first — and it is almost never the software. A tariff written down properly, or a free-time clause added to five contracts, can recover more in a quarter than a system does in its first year.

TMS or ERP first?

Carriers ask this as though there is a correct order. There is, and it is not the one the org chart suggests.

Start where the money leaks. For most carriers that is the trip: unbilled waiting, documents retyped, margin nobody can see per load. Accounting is usually not leaking — it is slow and annoying, which is a different complaint.

So the usual answer is the trip first, with the accounting system staying exactly where it is and receiving finished documents from the new system. That is a smaller project, it pays back sooner, and it does not put your tax reporting at risk in its first year.

Where to start

Write down one trip. A real one, from last week, with every place it was recorded and every person who touched it.

Most carriers who do this find five or six recordings and three or four people. Then ask which of those are reading and which are typing. The typing is the part a TMS removes, and the count tells you what it is worth.

If that exercise shows a trip already written once, you have saved yourself a project. If it shows five, we can tell you after one conversation which stop to start with — and it is rarely the one people expect.

Projects behind this article

What we build in this area

  • Logistics software & TMS

    Transport management, fleet telematics, logistics ERP and driver apps — with CMR, e-qaimə and AYNA documents built in.

  • ERP & business management systems

    ERP for trade, distribution and service businesses — sales, stock, finance, payroll and approvals, connected to 1C and e-qaimə.

All articles