Transportation Management Systems

A TMS is the software platform that plans, executes, and optimizes freight movements from shipper to receiver. It sits at the boundary between the warehouse (WMS/WCS) and the carrier network, managing everything from rate shopping to freight invoice audit.

Core TMS Modules

Module	Function
Rate management	Maintains carrier rate contracts; runs real-time rate shopping across carriers and modes
Load planning & tendering	Consolidates shipments into loads; tenders to carriers via EDI or portal
Carrier management	Onboards carriers, manages compliance, scorecards, and capacity commitments
Shipment execution	Generates BOLs, labels, manifests; transmits EDI to carriers
Visibility & tracking	Real-time shipment status via carrier EDI 214, tracking APIs, or IoT
Freight audit & pay	Matches invoices to contracted rates; identifies billing errors; automates payment
Analytics & reporting	Lane-level cost analysis, carrier performance, service failure root cause

TMS vs. WMS Boundary

The TMS/WMS handoff occurs at the dock door:

• WMS owns: inbound receiving, putaway, pick/pack, outbound staging up to the dock
• TMS owns: outbound shipment from dock-out through carrier delivery confirmation and invoice payment
• Overlap zone: yard management, dock scheduling, carrier appointment booking (handled by either, or by a standalone YMS)

Integration is typically via REST API or EDI. The WMS generates the ship confirmation (ASN/856); the TMS receives it and triggers tendering.

Carrier EDI Standards

EDI Transaction	Direction	Content
204	Shipper → Carrier	Load tender
990	Carrier → Shipper	Tender acceptance/rejection
214	Carrier → Shipper	Shipment status update
210	Carrier → Shipper	Freight invoice
856	Shipper → Receiver	Advance ship notice (ASN)

EDI 210/214 are the backbone of freight audit and real-time visibility. Carriers without EDI 214 capability require manual tracking or third-party visibility overlays.

Vendor Landscape

Vendor	Strength	Deployment
Oracle TMS (OTM)	Complex multi-modal, global, large enterprise	On-premise / cloud
SAP TM	Deep ERP integration for SAP shops	Cloud (BTP)
MercuryGate	Mid-market, strong LTL/parcel	Cloud SaaS
Uber Freight / Transplace	Network-based, carrier connectivity	Cloud SaaS
Project44	Visibility layer, not full TMS	Cloud SaaS
Blue Yonder TMS	Strong optimization engine	Cloud / on-premise

Most mid-market shippers ($50M–$500M freight spend) run cloud SaaS TMS. Enterprise with complex global/intermodal requirements tend toward Oracle OTM or SAP TM.

Freight Audit & Pay

Carrier invoicing error rates average 2–5% of freight spend, mostly from incorrect accessorials, duplicate invoices, and rate misapplication. A TMS with automated audit logic:

• Matches each invoice line to contracted rates
• Flags discrepancies above a configurable threshold
• Automates dispute filing for overbills
• Consolidates payment to carriers on net-30 or net-45 terms

Standalone freight audit & pay providers (Cass Information Systems, nVision, CT Logistics) handle this for shippers without a TMS-native audit module.

ROI

Typical TMS ROI drivers:

Lever	Typical Savings
Rate shopping / mode optimization	4–8% of freight spend
Load consolidation	2–5% of freight spend
Freight audit recovery	2–4% of freight spend
Carrier compliance (reducing exceptions and redelivery)	1–2% of freight spend
Total	8–15% of freight spend

Implementation cost ranges from $150K–$500K (mid-market SaaS) to $1M–$5M+ (enterprise on-premise). Payback is typically 12–24 months for freight spend >$20M/year.

Integration Architecture

ERP / Order Management
       ↓
     WMS (pick, pack, stage)
       ↓
     TMS (rate shop, tender, execute, audit)
       ↓
   Carrier Network (EDI 204/214/210)
       ↓
   Visibility Layer (Project44, FourKites)

TMS integrates with ERP for purchase orders and invoices, WMS for ship confirmations, and carrier portals/EDI for execution and tracking.