TMC made freight someone’s full-time problem

At Tetra Pak’s Indian operation, the truck could leave the factory and take the information with it. An industry analyst’s 2012 visit described manual bookings, little visibility after dispatch and duplicate freight invoices getting paid. The cartons were moving. The management system was struggling to keep up.

That gap helps explain TMC, a division of C.H. Robinson. Its business occupied the space between buying transportation software and finding enough experienced people to use it every day. A control tower, in this version of logistics, meant a team with a shared system and a practical assignment: make the network behave.

The map needed people

Jordan Kass founded the TMC division in 1999, during the dot-com boom. The proposition was unusually concrete for an internet-era business: connect shipment information, use it to organize transportation, and supply the expertise needed to keep improving the result. The offering became Managed TMS, short for transportation management system.

TMC combined process engineers, account teams and software power users. Its Control Tower locations connected regional operations through common technology. Chicago, Amsterdam and Shanghai were among the hubs; São Paulo joined the network in 2015. The arrangement made local knowledge available inside a coordinated international operation.

For Tetra Pak, the changes included automated carrier tendering, confirmations and freight-bill processes. Planning could consider fuller loads and different transport modes. The analyst’s account also described better reporting and less reliance on urgent shipments. What failed first was the flow of information between people and systems. Adding another truck would have left that problem intact.

John Deere kept the wheel

The John Deere case reveals the organizational bargain. Several thousand suppliers were involved in its inbound network, with suppliers managing much of the freight. That produced higher costs and inconsistent processes. TMC and Deere developed a coordinated inbound program rather than treating each shipment as an isolated purchase.

The work began with data collection and network analysis. Recommendations included cross-docking, dedicated fleets, multi-stop truckloads and consolidation of smaller shipments. Suppliers entered shipment information into an online system; TMC optimized the movements and tendered them to Deere’s inbound carriers. Reporting tracked the results.

A five-year North American agreement reported in 2008 made the division of authority explicit: Deere retained carrier selection and rate negotiation. TMC supplied technology and transportation expertise. Outsourcing could be selective. A manufacturer could delegate coordination without surrendering every commercial relationship.

The price of getting it done

The business model was fee-based managed services. Historical TMC materials described pay-as-you-go arrangements and limited upfront technology investment. That appealed to companies reluctant to buy, maintain and staff a conventional software installation. The customer was purchasing an operating capability as well as access to a platform.

For a buyer, the useful calculation is broader than the software bill. Compare the contracted service fee, implementation effort and retained internal staff against the costs the program can actually influence. A lower carrier rate, a fuller trailer and fewer emergency shipments affect different parts of the budget. Counting each honestly matters.

C.H. Robinson promotes delivered savings of up to 25% on addressable supply chain costs. That is a company claim with a defined denominator, not a promise about every freight dollar. It is also different from profit after service fees. Buyers should make that distinction before falling in love with a percentage.

Boise came for punctuality

Paper and packaging company Boise selected TMC in 2005 to improve delivery performance. Its published customer case reports on-time deliveries rising from about 88% to 97-98%. TMC handled planning, scheduling, execution and reporting; Boise kept carrier negotiations and relationships.

Logistics planning manager Howard Lortz initially wanted more punctual deliveries. The experience broadened his view of the project: clearer cost information helped Boise reconsider service offerings, including rush orders. The interesting change was managerial. A team chasing late deliveries gained a way to examine which promises were expensive to keep.

Microsoft became part of the product

Microsoft added another dimension. It was an early customer for Navisphere Vision, the visibility product first released in late 2016, and contributed supply chain data and feedback to its development. The software brought shipment information together with signals about possible disruption.

The relationship subsequently expanded into a 2020 technology alliance involving Microsoft Azure and Azure IoT. Inventory at rest and in motion could be viewed together, while connected devices added information about shipment conditions. A customer helping shape the product also became part of its underlying technology ecosystem.

“Our mission is to develop innovative technology platforms paired with managed services”Jordan Kass · prepared U.S. Senate testimony, 2016

The name changed. The buying question remains.

In November 2024, C.H. Robinson announced Managed Solutions, combining TMS technology, managed transportation and fourth-party logistics services. The TMC name would be phased out. The company’s stated reasoning was that shippers wanted easier movement between those services, with fewer provider boundaries. Its 2025 annual report confirms where the former division’s work now lives.

TMC therefore belongs in the market for managed transportation and supply chain coordination. Buyers can also consider Uber Freight for transportation software and managed services, DHL for 4PL coordination, or an internally operated platform such as Oracle Transportation Management. Its distinctive proposition was the combination of software, engineering and daily execution, with room for customers to keep strategic authority.

The lesson readers can copy is operational: establish a baseline, agree who owns each decision, and connect reporting to action. The model depends on suppliers providing usable data and teams accepting common rules. If nobody can change a booking when the system spots trouble, a better view simply gives everyone a clearer picture of the delay.