IMPARGO's transportation and logistics glossary
Find the definitions of the most important terms used in transportation and logistics industry
A Transport Management Platform (TMP), usually called a Transport Management System (TMS), is software that plans, executes, tracks and costs road freight in one place. It holds the transport orders, builds the routes, coordinates the carriers, shows where the shipments are and reports what each one earned.
The honest description of what it replaces is narrower than the category name suggests. In most small and mid-size fleets a TMP takes over a spreadsheet of tours, a messaging thread with drivers, a mapping tab open in the browser and a folder of scanned paperwork, and puts those four things into one record per shipment.
The pain a TMP addresses is rarely a missing feature. It is the same information being retyped into four places, and nobody being able to answer "where is this load and what will it earn" without asking two people. A platform earns its keep when it removes:
In practice the two terms are used interchangeably and no buyer should be pushed on the distinction. The classic label for this software category is TMS, and it is still the more common one in tenders and job adverts. TMP tends to be used for newer systems built as connected modules with integrations and automation rather than one monolithic install.
What matters when comparing two products is not the acronym on the box but whether the modules you need work independently, and whether the data entered once is available everywhere else.
Three groups, with different reasons. Carriers running their own fleet plus subcontractors use it to keep both under one plan. Companies that arrange transport without owning the trucks use it to coordinate execution across partners. Shippers with outbound, inbound or multi-site flows use it to stop managing haulage by email.
Inside those companies the daily user is the person assigning loads and vehicles each morning, which is why the planning screen, not the reporting screen, decides whether a platform gets adopted.
Almost nobody implements everything at once. Most teams begin with the workflow that hurts most, usually route planning or the intake and tracking of the transport order itself, and add modules as volume grows. IMPARGO is built that way on purpose: the modules work on their own and share one set of master data.
The useful test when comparing products is not the feature list but a single real tour: plan one you ran last month, then compare the predicted toll and cost against what it actually came to. A system that cannot get that number close will not be trusted for the tours you have not run yet, whatever else it does.
© IMPARGO 2026, All rights reserved.