The TMS Vendor Landscape
A market map for retail enterprise readers evaluating agentic TMS software.
Why a map, not a list
The TMS market is fragmented and getting more so. A long list ranks vendors. A map separates them by what they actually are.
Build era, deployment model, decisioning depth, and how each candidate clears the rubric set out in The Seven Tenets of an Agentic TMS — the prior piece in this series. Four archetypes emerge. Knowing which archetype your incumbent sits in, and which your shortlist is sampling from, matters more than rank within a single bucket.
Two axes, four positions.
The horizontal axis is architecture: monolithic systems whose modules share state and ship as one product, versus composable systems whose components can be swapped, configured, or extended independently.
The vertical axis is decisioning: rules-driven systems that surface recommendations for a planner to action, versus agentic systems that execute decisions autonomously inside operator-set guardrails.
Most vendors do not sit cleanly in a corner. The four archetypes mark the centres of mass.
The four archetypes.
- Archetype 01
Legacy Enterprise TMS
Built between roughly 2000 and 2012 for a world of perpetual licences, on-premises servers, and EDI-based carrier integrations. These systems digitised manual workflows: static routing guides, batch freight audits, contract compliance reporting. They were engineered to map precisely to a specific shipper's idiosyncrasies, and many enterprise IT teams modified the application logic itself to fit local needs.
The trade-off is well documented. Deloitte's 2024 work on cloud-native development calls legacy monolithic applications the primary obstacle to "the speed of delivery" required in modern operations. Tight coupling means vendor upgrades risk breaking custom integrations, which drives version-lock. Many shippers in this archetype are running software two or three major versions behind, accumulating technical debt while the freight market evolves around them.
ExamplesOlder on-premises deployments of Oracle Transportation Management, SAP TM, and Manhattan Associates' WMos-era TMS. Often still running on hardware procured in the early 2010s.
Where it winsHighly regulated, asset-heavy operations with stable freight patterns, deep ERP entanglement, and data-residency requirements that preclude public cloud. Defence, heavy industry, and a handful of regulated CPG verticals still defensibly run these systems.Where it losesAnywhere real-time decisioning matters. Anywhere the carrier base churns. Anywhere the planning team is shrinking. The maintenance cost grows; the optionality shrinks.Tenets cleared0 of 7 fully. Partial credit on Governance (audit trails) and Network-aware (some multi-leg planning, but lane-by-lane in practice). - Archetype 02
Modern Monolithic SaaS
Emerged between roughly 2014 and 2020 as the cloud transition reset enterprise TMS. The functional modules (procurement, planning, execution, settlement) ship as one product on a single data schema, but the deployment is multi-tenant SaaS. Version-lock is gone. The vendor handles upgrades. The buyer gets a single pane of glass across modes. The IDC MarketScape: Worldwide TMS 2024 places most of the named Leaders in this category, validating the architecture as the current dominant form.
The architectural ceiling is the monolith itself. Modules cannot be swapped without leaving the suite. AI is layered on top of the same rule-based decisioning core, which is why most "agentic" claims at this layer surface as copilots and recommendations rather than autonomous execution. The data model is unified, which helps with reporting and trade-offs across modes, but the buyer adapts to the vendor's workflow logic, not the other way around.
ExamplesOracle Transportation Management Cloud, Blue Yonder, SAP Transportation Management, Manhattan Active Transportation, e2open, C.H. Robinson Navisphere. Gartner MQ 2025 Leaders.
Where it winsGlobal, multi-modal enterprises with stable processes and a strong preference for one accountable vendor. Mature deployments deliver real freight savings and reliable execution across regions.Where it losesAnywhere the operational shape shifts faster than the vendor's release cadence. Anywhere a buyer wants to replace one component (pricing, optimisation, settlement) without replacing the platform.Tenets cleared2 to 3 of 7. Partial on Decisions (recommendations layered on rules), partial on Learning (some ML in routing), partial on Events (cloud APIs + real-time visibility), empty on Composable by definition. - Archetype 03
Modular Suite (MACH)
Built on the MACH principles (Microservices, API-first, Cloud-native, Headless) that Accenture describes as the shift from "static, standalone parts" to "composable pieces." The buyer assembles a TMS from best-of-breed components rather than buying a suite. The benefit is real: a visibility component can be swapped without rebuilding the planning component; a procurement workflow can be extended without touching settlement.
The cost lands on the buyer's IT team. The "connective tissue" between components, the API gateways, the master-data management, the event mesh that synchronises state across services, is the buyer's problem. Done well, this archetype is the only one that delivers genuine composability today. Done badly, it produces a fragile web of brittle integrations and silent failure modes that no single vendor will own.
ExamplesAlpega (Gartner MQ 2025 Challenger). Customer-assembled stacks built around project44 (visibility), FourKites (real-time tracking), Uber Freight (capacity), and specialist point solutions on iPaaS.
Where it winsDigital-native retailers, advanced 3PLs, and high-growth omnichannel brands with elite internal engineering. Organisations whose operating model changes faster than any single vendor's release cadence.Where it losesEnterprises that lack the engineering depth to govern an API-centric stack. Without strong master-data discipline, the modular suite devolves into the worst of both worlds: monolithic dependency on a tangle of vendors.Tenets cleared3 to 4 of 7. Clears Composable by definition. Partial credit on Events (depending on components) and Ground-truth (best-of-breed feeds, but stitched). Decisioning depth depends entirely on the components selected. - Archetype 04
Agentic-Native
Built from inception around multi-agent architectures, real-time event streaming, and policy-as-code governance. The decisioning engine is the operating system; the UI is a supervisory surface for human-in-the-loop validation. Gartner's May 2026 framing names this shift as the move from "automated, siloed tasks" to "a network of outcome-based decisions autonomously made or augmented by AI." The architecture is what makes Tenets 01 through 06 reachable simultaneously, not as feature claims but as system properties.
The honest reads. The installed base is smaller than the Leader quadrant. The integration burden in heavy-ERP shops is real. And not every vendor claiming "agentic" actually has the multi-agent infrastructure, the governance stack, or the years of architectural investment to back it. The category is also where the most marketing theatre lives. Read the trajectory, not the label: vendors who have been building autonomous decisioning for years are visibly ahead of those who painted it on last quarter.
ExamplesLocus, Pando and a few others. The smallest, newest, and fastest-moving group on the map.
Where it winsHigh-velocity retail, omnichannel grocery, last-mile-heavy operations, and any network where the latency cost of human-in-the-loop on every decision compounds into real margin loss. Buyers willing to set strategic guardrails and let the system execute inside them.Where it losesBuyers without clean, structured operational data, or without the executive appetite to shift planners from execution to oversight. The architecture is ready before some buyers' organisations are.Tenets cleared5 to 7 of 7, depending on vendor maturity. The leaders in this archetype clear 1, 2, 3, 4, 6 cleanly; 5 (Governance) and 7 (Network-aware) vary by deployment depth.
The rubric, applied.
The Seven Tenets translate cleanly into a score grid. Filled dots are tenets the archetype clears as a structural property of the architecture, not as a feature claim. Half-dots are partial. Empty cells are tenets the architecture cannot clear without breaking.
| Archetype | T01Decisions | T02Learning | T03Events | T04Composable | T05Governance | T06Ground-truth | T07Network |
|---|---|---|---|---|---|---|---|
| 01 Legacy Enterprise TMS | |||||||
| 02 Modern Monolithic SaaS | |||||||
| 03 Modular Suite (MACH) | |||||||
| 04 Agentic-Native |
A counterpoint.
The map is not the territory.
Three constraints legitimately override the rubric: regional concentration (a Niche Player with deep local carrier coverage can outperform a Leader with a thin regional footprint), data residency (sovereignty rules can rule out vendors whose cloud forces data into the wrong region), and ERP entanglement (deep coupling to one vendor's stack can make their TMS the cheaper integration). None invalidate the map. They tell the reader where to apply judgment on top of it.
This map combines third-party analyst research with Locus's own field research on operating retail logistics networks at scale. Vendor placements plot each archetype's centre of mass, not the precise position of every named vendor.
Analyst sources. Gartner Magic Quadrant for TMS 2025 (Leaders, Challengers, Visionaries, Niche Players). IDC MarketScape: Worldwide TMS 2024. Forrester, "New Technologies Transform Transportation Management" (2024). Gartner, "Three Building Blocks for Autonomous Supply Chain Future" (May 2026). IDC Innovators: Retail Last-Mile Platforms, 2025-2026 names Locus an innovator.
Architecture anchors. Deloitte on cloud-native vs. legacy monoliths and Accenture on MACH composability.
If a vendor placement looks wrong from where you sit, write to us. The map gets sharper with that feedback.
