IMPARGO's transportation and logistics glossary

Find the definitions of the most important terms used in transportation and logistics industry

IMPARGO's logistics glossary/T/

TMS – Transport Management System

TMS Meaning: What a Transport Management System Does

A transport management system (TMS) is the software a transport business runs its shipments on. It holds the orders, plans the tours, assigns vehicles and carriers, tracks what is happening while the goods move and records what each job cost and what it earned. The category is not tied to one mode: transport by road, rail, sea and air is managed under the same name, and this entry looks at what road freight in particular asks of one.

Put the way a dispatcher would put it: a TMS is the single place a transport order lives from the moment a customer books it to the moment it is invoiced, instead of sitting in a spreadsheet, an inbox and somebody’s memory. The same software is also sold as a transport management platform, where that label is compared in detail.

Prefer IMPARGO in your Google results

Add us as a preferred source and our pages are more likely to appear in your Search, AI Mode and Discover results.

Add IMPARGO as a preferred source

What a TMS covers, from intake to invoice

The sequence runs from a customer request, through a structured transport order, to a tour on a vehicle or a subcontractor, to a cost known before the job is confirmed, to whatever comes back off the road, and out into the invoice. What makes software a TMS rather than a mapping tab or an address book is that one record carries the whole way through.

The capability list behind each step is broken down on the platform entry linked above. The more useful question here is where the category ends.

Where a TMS stops and the neighbouring systems start

Buyers lose time here: these systems overlap at the edges, and each vendor paints its own box as the centre.

  • ERP owns the commercial side: customers, contracts, accounting and master data. A TMS usually takes orders from it and hands settlement data back.
  • Warehouse management owns what happens inside the building: stock, put-away, picking and loading. What the warehouse system itself governs is set out under warehouse management. The TMS takes over when the goods leave the ramp.
  • Telematics owns the vehicle: position, driving data and often tachograph files. A TMS reads that feed so positions land on the planning screen.

The practical test: goods at rest belong to the warehouse system, money and contracts to the ERP, and a shipment in motion plus whoever is moving it to the TMS.

That boundary is what you are actually shortlisting. The transport layer stands or falls on one screen: in the Planner Module a trip is worked out from the tractor and trailer you enter rather than a car profile, which is the difference a prepared demo route tends to hide. try it on a lane you already run

What road freight asks of a system like this

A general purpose TMS can tick every box on paper and still fall over on the first tour, because a truck is not a car. Road freight planning means the trip is calculated against the combination you are actually sending: dimensions, gross weight, axle count, dangerous goods. A planner correcting a car route from memory is doing that by hand.

The second thing road freight adds is cost before departure. Toll is a real line in the price of a European tour and it varies by country, vehicle class and road, so a quote made without it is a guess. A European truck toll calculator belongs next to the planning screen, not in a separate tab.

Who ends up working in it

A system only the planner ever opens has not replaced much. Several people touch the same shipment record from different angles, and the fiddly part of any rollout is deciding who gets to see what.

The dispatcher builds and rebuilds the plan and needs the whole picture. Customer service needs to answer where a load is without interrupting the planner. The driver needs the job in hand and nothing else. A subcontracted carrier needs its own leg and its own paperwork, with your rates and your other customers out of view.

Ask how those views are separated before you ask about features. A pilot account, where everyone is an administrator, skips the question.

What to check before you commit

Shortlists get decided on a feature grid, the one artefact every vendor has already polished. The questions that separate two products are duller, and nearly all of them sit on the boundaries above.

  • Which of your systems has it got to exchange data with, who builds that link, and who fixes it when a field changes?
  • When an order arrives as a mail or an attachment, the way your customers really send it, what happens to it?
  • Do the vehicle and the cost live on the planning screen, or is that screen a line on a map?
  • Where does position data come from once the truck has gone, and who pays for it?

Those edges are where the work leaks back out. Software that plans well but cannot take an order from the system it already sits beside has only moved the retyping one desk along. The line between the transport layer, the warehouse and the commercial system is most of what you are buying.

Related Topics:


Impargo-logo

Digitalize your transport business overnight.

© IMPARGO 2026, All rights reserved.