TMS vs Fleet Management Software: Different Jobs, Shared Data

A planner books a load on the transport system, the tractor breaks down at midnight, and the fleet controller moves the trailer to another truck. By morning the fleet app shows the right vehicle, the transport system still shows the old one, the freight bill is matched to a truck that never finished the trip, and in India the e-way bill carries a vehicle number that no longer matches the road. Both systems worked. Nobody decided which one owned the truck.

A transportation management system (TMS) and fleet management software answer different questions, and most confusion comes from buying one and expecting it to answer the other's. Once each record has one owner and a handful of shared fields flow both ways, a company running its own trucks can plan in one, execute in the other, and compare an own-truck trip with a carrier quote in the same currency unit.

• What this covers: the shipper and asset views, the records each system owns, US hours-of-service and inspection rules, Indian e-way bill and tracking-device rules, an integration payload, a vehicle-swap incident and a dollar and rupee cost comparison.
• Who it is for: supply chain managers and founders deciding whether they need a TMS, fleet software, both, or a carrier-side system.

A TMS buys and plans freight while fleet software runs the trucks

A TMS is organised around shipments and what they cost to move; fleet management software is organised around vehicles and drivers and what they cost to keep running. If you do not own or lease trucks, you rarely need fleet software. If you own trucks but never buy outside freight, you may not need a full TMS.

Our explainer on TMS architecture covers what sits inside a transport system: load building, carrier tendering and freight settlement. The companion page on fleet management software covers telematics, fuel and tyre control. This article is about the boundary between the two, which neither page addresses directly.

The shipper's question set against the asset owner's question set

The shipper view starts from demand and treats trucks as interchangeable capacity. The asset view starts from a fixed fleet and asks how to keep it full, legal and maintained. A company with a private fleet holds both views at once, which is why it feels the gap most.

• Shipper asks first: what has to move, by when, and what will it cost with each carrier or mode? The answer is a tender, a booking and later an audited invoice.
• Asset owner asks first: which truck and which driver are free, with enough legal driving time and no open defects? The answer is an assignment, a trip and later a settlement.
• Private fleet asks both: should this load go on our own truck or a carrier's, and if ours, which one? Only the combination of TMS quotes and fleet cost data answers that.
• Carrier asks differently: a trucking company sells capacity, so its "TMS" is usually a dispatch and billing system built around its own fleet, closer to fleet software than to a shipper's TMS.

Records each product owns and five fields they must exchange

Each record should have one owning product, and the other product should only read it. Five shared fields carry almost all the integration: trip or load identifier, vehicle identifier, driver identifier, stop sequence with planned times, and actual event timestamps with location.

The vehicle identifier is the field that breaks most often. The TMS records which truck was planned; the fleet software records which truck actually ran. When they differ, the fleet software is right about the past and the TMS must accept a change event rather than overwrite it, or the freight cost, proof of delivery and tax documents will each describe a different vehicle.

US hours-of-service and inspection records sit on the fleet side

In the US, driver logs and vehicle inspection reports are fleet records with their own retention rules. A TMS should read available driving hours and open defects from the fleet side before it assigns a load, rather than keeping a second copy.

Under 49 CFR 395.8(a)(1)(i), a motor carrier operating commercial motor vehicles must install and require each driver to use an electronic logging device. Paragraph (a)(1)(ii)(A) allows paper records for drivers who need a record of duty status on no more than 8 days in any 30-day period, for certain driveaway-towaway operations, and for vehicles made before model year 2000. Section 395.8(k)(1) requires carriers to keep records of duty status and supporting documents for at least 6 months.

• Daily inspection report: 49 CFR 396.11(a)(1) requires a written driver vehicle inspection report at the end of each day's work on each vehicle, covering at least the listed parts such as service brakes, steering, lights, tyres and coupling devices.
• No-defect exception: under 396.11(a)(2)(i), no report is needed if no defect is discovered by or reported to the driver.
• Repair before use: under 396.11(a)(3), the carrier must repair a listed defect likely to affect safety, or certify that repair is unnecessary, before the vehicle operates again.
• Retention: the report and certifications are kept for three months under 396.11(a)(4).

US load assignment in a TMS should read remaining driving time from the ELD records a fleet system keeps under 49 CFR 395.8(a)(1)(i), retained for at least 6 months under 395.8(k)(1). A vehicle with an unrepaired defect from a 49 CFR 396.11 inspection report should be ineligible for assignment until certified.

Unassigned driving segments are a common source of disagreement between the two products, because the TMS trip shows one driver while the logging device records movement with nobody logged in. Our guide to unassigned driving time on ELDs explains how those segments are reviewed and annotated.

India: e-way bill vehicle changes and tracking-device rules

In India the sharpest TMS and fleet boundary is the e-way bill. The consignment is generated from the shipper's side, but the vehicle number in Part B must match the truck actually carrying the goods, and the fleet controller is usually the first person to know when that truck changes.

CGST Rule 138(5) says that where goods are transferred from one conveyance to another, the consignor, recipient or transporter must update the conveyance details in Part B before the transfer and further movement. A proviso relieves this where the goods move up to 50 km within the same State or Union territory to the consignee's place of business. A truck swap after a breakdown therefore has to reach the e-way bill before the replacement truck leaves.

Vehicle changes during an Indian road movement must reach the e-way bill before the goods move again: CGST Rule 138(5) requires the Part B conveyance update before transfer, except final deliveries within 50 km in the same State. The fleet record of the swap should trigger that Part B update through the TMS automatically.

Tracking devices add a second India-specific link. Rule 125H of the Central Motor Vehicles Rules, inserted by notification G.S.R. 1095(E) of 28 November 2016, requires vehicle location tracking devices meeting AIS-140 in public service vehicles. State notifications, such as Tripura's of February 2025, also apply it to national permit goods carriages, and G.S.R. 617(E) of 3 August 2022 requires it on N2 and N3 vehicles carrying dangerous goods, from 1 September 2022 for new models and 1 January 2023 for existing ones.

The practical consequence for Indian private fleets is that the fleet product holds the device and route data, while the TMS or ERP holds the e-way bill. Our article on e-way bill penalties under section 129 explains what happens at a roadside check when the two disagree.

Plan in the TMS, execute and measure in the fleet product

The integration that works is a small, versioned message set: the TMS sends a trip plan, the fleet product returns events, and a vehicle or driver change is an event the TMS must accept, not a field it silently overwrites. Telematics pings stay in the fleet product; the TMS receives only milestones.

// TMS to fleet product: trip plan (illustrative)
{
  "messageType": "trip.plan",
  "messageId": "TMS-TRP-77215-v3",
  "tripId": "TRP-77215",
  "version": 3,
  "loadIds": ["LD-55102", "LD-55107"],
  "vehicleRegistration": "MH04AB1234",
  "driverId": "DRV-0912",
  "plannedDriveMinutes": 610,
  "stops": [
    { "seq": 1, "site": "BHW-DC", "type": "pickup",   "plannedAt": "2026-11-12T21:00:00+05:30" },
    { "seq": 2, "site": "NSK-C14", "type": "delivery", "plannedAt": "2026-11-13T05:30:00+05:30" }
  ],
  "ewayBills": [{ "ewbNo": "391002345678", "partBVehicle": "MH04AB1234" }]
}

// Fleet product to TMS: vehicle change event (must be consumed, never ignored)
{
  "messageType": "trip.vehicleChanged",
  "messageId": "FMS-EVT-77215-0042",
  "tripId": "TRP-77215",
  "basedOnVersion": 3,
  "fromVehicle": "MH04AB1234",
  "toVehicle": "MH04CD5678",
  "changedAt": "2026-11-12T23:40:00+05:30",
  "reasonCode": "BREAKDOWN",
  "odometerKm": 214
}

• Idempotent messages: each message carries an ID, so a retry after a network drop does not create a second trip or a second vehicle change.
• Version check: the fleet event names the plan version it applies to, so a late event against an old plan is queued for review rather than applied.
• Milestones only: arrival, departure, proof of delivery and exceptions go to the TMS; raw GPS points stay in the fleet product to avoid flooding the planning database.
• Hold on change: a vehicle change sets the trip to a held state in the TMS until linked documents, such as the e-way bill Part B, are updated.

A breakdown swap that split the truck, the bill and the e-way bill

The illustrative trace below shows how a sound breakdown response in the fleet product became a tax exposure and a billing error because the TMS never consumed the vehicle change.

1. 12 Nov, 21:10: The TMS releases trip TRP-77215 on MH04AB1234 with e-way bill 391002345678, Part B showing that vehicle. The fleet product receives the plan and starts tracking.
2. 12 Nov, 23:40: The tractor stops with a coolant fault 214 km out. The fleet controller sends replacement MH04CD5678 and records the swap. The interface carries GPS pings to the TMS but has no vehicle-change message.
3. 13 Nov, 02:15: The load leaves on MH04CD5678. Nobody updates Part B, although Rule 138(5) requires it before further movement and the remaining distance is well over 50 km.
4. 13 Nov, 06:30: A roadside check finds the vehicle number differs from the e-way bill. The vehicle and goods are held while the shipper's tax team responds, and delivery misses its 05:30 window.
5. 15 Nov, 14:00: Freight audit matches the transporter's bill to MH04AB1234, while fuel and toll costs post against MH04CD5678. Settlement is corrected by hand, and a vehicle-change message that holds the trip is added to the interface.

Own truck or carrier: one load costed in dollars and rupees

The private-fleet versus carrier decision needs fleet cost per distance unit and TMS carrier quotes in the same calculation. The deciding variable is usually empty running, which only the fleet product measures and which the TMS can reduce by finding a backhaul.

The table uses illustrative figures: a 500-mile US lane and an 800 km Indian lane, each costed first with the truck returning empty for most of the distance and then with a backhaul that cuts empty running. Indian figures exclude GST, and every unit cost is an example to be replaced with your own fleet data.

Own-truck versus carrier decisions combine fleet-product cost per kilometre with TMS carrier quotes. In the illustrative 800 km Indian lane, ₹50.50 per km makes the own truck dearer than a ₹55,000 quote when 400 km run empty, but ₹9,550 cheaper once a backhaul cuts empty running to 100 km.

The same arithmetic explains why many private fleets buy a TMS later than they should. Without carrier quotes stored next to fleet costs, the planner defaults to the company truck because it feels free once it is on the books, and the empty miles never appear as a cost against the load that caused them.

Checks that should be hard rules and where software only advises

Anything that would put an illegal driver, an unsafe truck or a mismatched tax document on the road should be a fixed rule that blocks the assignment. Predictions such as arrival times, carrier choice and fuel anomalies are advice for a person to accept or reject.

Keep the block lists short and written down. A rule that fires on every third trip gets bypassed with a shared override login, while a rule that fires only for illegal hours, open defects and a wrong vehicle on a tax document keeps its authority because everyone agrees those trips must not leave.

One platform, two products or a carrier dispatch system

Pick the operating model before the product. Shippers with no trucks need a TMS and carrier tracking; carriers need dispatch built around their own fleet; shippers with a private fleet usually need both products joined by the message set above, unless one vendor can prove both sides on your own data.

• Data ownership clause: state that trip, log and location data belong to the operator and can be exported in a documented format at any time and on termination.
• Message change clause: require notice before either vendor changes a message field the other product consumes.
• Exit test: run one export during implementation, not at the end of the contract.

More transport planning and fleet guides are on our Logistics and Supply Chain hub. If you are choosing between a TMS, fleet software or a combined platform and want the record ownership and message set written into the tender, share your requirements with us and we will scope the work.