Transportation management systems earn their keep before the wheels turn. Load consolidation, mode selection, carrier procurement, stop sequencing: real math, real savings, computed at the dock. Manhattan Associates, the reference vendor in the category, states that more than half of the Top 100 motor carriers in North America run its transportation solutions. When a TMS vendor says it routes freight to the lowest cost, that is the layer it means: the plan.
Then the load leaves the dock, and the plan stops deciding. Diesel moves during the run, and it varies up to 50 cents within the same city. Parking fills by early evening. A lane closes. The driver's clock burns down. Every one of those is a money decision, and in the TMS model every one of them lands on the driver or the fuel desk, hours after the optimizer last looked.
The rented engine pattern
Here is the detail most fleet buyers never see: enterprise TMS products do not build road level truck routing. They license it. Manhattan lists Trimble MAPS as its routing and mapping partner, and its Fuel&Route product integrates PC*Miler RouteSync for turn by turn navigation, per both companies' published partner pages. The pattern repeats across the category: the TMS owns the planning math, and the road model underneath is rented from the same decided once engine the industry has used since the 1980s.
That architecture has a consequence. When the routing engine is a licensed component that answers one question, what is the path, the platform built on top can only optimize what it can see at planning time. Fuel, tolls, tax, parking, and hours become separate lookups for separate teams instead of inputs to one live decision.
What the published numbers say
Manhattan's flagship Fuel&Route case study, an enterprise refrigerated carrier, reports a roughly 1% annual fuel expense reduction, about $500,000 a year at that fleet's scale. That is a real result, and it took an enterprise implementation to get it. It is also the ceiling of what plan level fueling recommendations can reach, because the plan cannot see the pump price at the exit the truck is actually approaching.
Deciding at the pump level inverts the number. The Argus Agent scans live prices along the route, times the fill against the tank, models burn over the terrain, and weighs state fuel tax before handing the driver one answer per fill. That decision layer averages about $334 a month back per truck, on any fleet size, from the first day, with no implementation project.
What agentic routing means
Agentic routing is routing where the decision survives dispatch. One agent holds the whole trip: route, fuel, tolls by axle and time of day, tax, parking, and the HOS clock, and re decides it continuously as conditions change, inside guardrails the fleet sets. Approved fuel networks, out of route limits, parking rules: the fleet draws the box, the Agent decides inside it, and every decision is explainable after the fact.
The 2026 agent announcements from the enterprise vendors do not change this boundary. Manhattan's commercially available AI agents review planned shipments for missed consolidations, monitor shipments, and process carrier invoices. Useful back office work, all of it before or after the trip. None of it rides with the driver, where the fuel is bought and the clock burns.
The honest split
The two layers are complements, not substitutes. If you plan thousands of loads a day across a national network, TMS planning is worth every dollar. But the plan ends at the dock, and the spending does not. The fleets that win this decade run both: the TMS plans freight, and an agent runs the trip. For the full side by side, read the Argus vs Manhattan comparison and the Argus vs Trimble comparison, or start with what agentic routing is.
The boundary, in one table
| Decision | TMS (at the dock) | Agent (on the road) |
|---|---|---|
| Load, mode, carrier | Decided | Inherited from dispatch |
| Road level route | Licensed engine, computed once | Own engine, re decided live |
| Where to fuel | Pattern in the plan | Live pump price + tank + state tax, per fill |
| Where to park | Not in the plan | Real time, decided against the clock |
| The HOS clock | A constraint at dispatch | A routing input, all trip |
Questions, answered
What does TMS route optimization actually optimize?+
Pre dispatch decisions: load consolidation, mode and carrier selection, stop sequencing, and plan level fueling patterns. Manhattan Active Transportation Management, the reference enterprise product, describes a lowest cost path optimization across those variables. All of it is computed before the truck moves.
Do TMS platforms build their own truck routing engines?+
Generally no. Road level truck routing is licensed. Manhattan Associates lists Trimble MAPS as its mapping and routing partner, and its Fuel&Route product integrates PC*Miler RouteSync for turn by turn navigation, per both companies’ published partner pages. The TMS owns the planning math; the road model is rented.
What is agentic routing?+
Routing where the decision does not end at dispatch. An agent re prices the trip continuously while it runs: live pump prices, tank level, tolls by axle and time of day, parking availability, the driver’s remaining HOS clock, and state fuel tax, re decided every mile inside guardrails the fleet sets. The plan is a starting point, not the answer.
How big is the gap in fuel results?+
Manhattan’s published flagship Fuel&Route case study reports a roughly 1% annual fuel expense reduction at an enterprise refrigerated carrier. Argus, deciding at the pump level per truck, averages about $334 a month back per truck on fuel. Different layers produce different numbers: one optimizes the fueling pattern in the plan, the other decides each actual fill.
Vendor capability descriptions and results in this article come from Manhattan Associates' and Trimble's published product pages, partner pages, press releases, and case studies as of July 2026.