Your Legacy TMS Renewal is Not a Selection Decision: A 2026 Framework for North American Shippers

Renewal is a different decision from selection

Almost all published TMS guidance addresses selection: define requirements, shortlist vendors, score responses, choose. That guidance assumes the buyer controls the timeline.

A renewal inverts that. The date is fixed by a contract signed years ago, the incumbent has your configuration and your historical data, switching carries a cost that a greenfield buyer never pays, and the alternative to deciding is not “keep looking” but “renew by default.” Every one of those changes the analysis.

The specific consequence is that a renewal evaluation is planned backwards from a date rather than forwards from a requirement. Teams that run a renewal like a selection typically arrive at the notice deadline mid-evaluation, at which point the only available action is to renew for another term and resolve to look properly next time. That happens frequently enough to be the default outcome rather than the exception.

The status quo has a cost that rarely appears in the renewal paper. McKinsey estimates that inefficient logistics handovers account for 13 to 19 percent of logistics costs, as much as 95 billion dollars annually in the US alone, and much of that sits in the seams a legacy platform leaves unaddressed. Renewal is not a zero-cost option; it is a decision to keep paying that.

The clock you are actually running against

Find your notice deadline before you do anything else.

Most enterprise TMS agreements auto-renew unless notice is given within a defined window, commonly 90 to 180 days before term end. That window, not the renewal date, is the decision deadline, and every planning date should be derived backwards from it.

The second date to establish is your incumbent’s support horizon for the version you are running. A platform still supported does not mean the version you deployed and configured is on the same footing, and a required upgrade during the next term is a project with a cost and a risk profile that belongs in the renewal comparison rather than surfacing eighteen months later.

The third is your own operational calendar. Nobody should be cutting over during peak, which for most North American shippers removes a quarter from the available window and frequently more.

Those three dates define what is actually possible. If the notice deadline is four months out, replacement inside this term is not realistic, and the honest options narrow to renewing short or renewing and layering. Knowing that early is more valuable than discovering it after a three-month evaluation.

Three options, not two

Renewal evaluations are usually framed as renew or replace. There is a third, and it is frequently the best fit for a fixed deadline.

Renew as-is. Correct when the platform still matches the operating model, the configuration is sound, and the constraint you feel is capability you do not actually need. Also correct as a deliberate short renewal to create runway, which is a legitimate strategy rather than a failure.

Renew and layer. Keep the incumbent for what it does well, typically freight procurement, rate management, tendering, and settlement, and deploy an execution platform above it for dispatch and last-mile decisions. This is not a compromise architecture. Freight procurement and delivery execution optimise different objectives, and forcing one system to do both is a common source of the dissatisfaction driving the renewal review in the first place.

The evidence for this path is direct. A Fortune 50 parcel and logistics provider had implemented a replacement freight platform intended to handle routing in its own stack, and it could not run dispatch. Rather than replace again, the operation deployed Locus as the all-mile decisioning layer alongside it, governing 4,500+ drivers, 1,500+ captive and 3,000+ third-party, under one policy. Weekly execution moved from 75 percent to 92 percent across 51 service-center locations, and a single-site analysis surfaced 565,000 dollars in unused capacity that scaled to 14 million dollars-plus annualized across 25 sites.

Replace. Correct when the mismatch is structural rather than functional, most often when the platform’s data model does not fit how the operation runs. A leading North American retailer supplying a multi-hundred-store network across ocean, rail, and road was running six disconnected systems where planning ran leg by leg and more volume simply meant more people. Consolidation onto one decision layer, with ERP and WMS retained as systems of record, produced 99 percent-plus on-time store delivery, exceptions resolved in under two hours, an 80 percent-plus reduction in manual dispatch, and 1 million dollars-plus in savings with break-even inside the first year, from kick-off to go-live in six to nine months.

Note that timeline against a notice deadline. Six to nine months is achievable and it is not four.

Five factors that actually decide it

1. Sunk configuration, honestly assessed. The most cited reason to renew and the weakest one. Configuration has value only if the underlying model still fits the operation. Where teams configured extensively to work around a mismatch, that configuration is a record of the problem rather than an asset, and preserving it preserves the problem. Ask what share encodes genuine business rules versus what compensates for something the platform does not do.

2. Support horizon and forced upgrades. Any required version upgrade inside the next term is a project. Price it onto the renewal side, because it is a cost of renewing the renewal quote does not contain.

3. Lock-in terms. Term length, auto-renewal mechanics, egress rights, and exit cost. Egress terms negotiated during a renewal, while you have leverage, are considerably better than those discovered during an exit.

4. Parallel-run cost. Any replacement means paying for two platforms for a period. That is a real number and it belongs in the business case rather than being treated as an implementation detail. It is also the number that makes a short renewal look attractive, since a six-month extension is frequently cheaper than a compressed cutover.

5. What the platform needs to do in year three. A renewal is a commitment across a period of category change. Gartner projects that 60 percent of enterprises using supply chain management software will have adopted agentic AI features by 2030, up from 5 percent in 2025. Whether your incumbent can absorb that shift, and whether absorbing it is a configuration change or a replatform on their side, is a fair question to put to them directly.

Building the case your CFO will accept

Three components, in the order finance will want them.

The cost of the status quo, quantified. Not the licence fee, which finance already knows, but the operational cost of what the platform does not do: manual dispatch hours, exception handling headcount, expedited freight caused by late replanning, and cost visibility gaps. Most of these are recoverable from your own data in a fortnight.

The realistic upside, sourced. A Gartner-commissioned analysis indicates the average TMS user can expect to save 5 to 15 percent of annual freight costs, with more than 40 percent of adopters breaking even within 6 to 12 months and a further 25 percent within 18. Use category-level figures for the range and your own operational data for the specifics, and be explicit about which is which. A business case built entirely on vendor numbers gets discounted entirely.

The risk case, addressed rather than avoided. Gartner predicts that more than 40 percent of agentic AI projects will be cancelled by the end of 2027, attributing this to escalating costs, unclear business value, and inadequate risk controls rather than to capability. Naming that in your own paper, with your mitigations against each of the three, is more persuasive than omitting it and being asked.

Capability is worth costing honestly too. Gartner found that 56 percent of chief supply chain officers cite integrating AI with legacy systems as a major challenge, and 50 percent report limited internal expertise. If the second applies to you, the plan needs to name who does the integration work.

Planning backwards from the notice deadline

Work from your notice date, not your renewal date. The months below are indicative and should compress or extend against your own operational calendar.

The row most teams skip is the third. Deciding direction before evaluating vendors saves months, because renew, layer, and replace produce entirely different shortlists, and running one process across all three produces a comparison nobody can score.

What to ask, on both sides

Of your incumbent: the support horizon for our current version and any upgrade required inside the next term. Renewal cost at current volume versus projected volume. Our data egress rights, in what format and over what period after termination. The roadmap for autonomous decisioning, and whether adopting it would be a configuration change or an upgrade project for us. What a two-year renewal costs against a five-year one.

Of an alternative: whether you can coexist with our incumbent rather than replacing it, and what that architecture looks like. Realistic kick-off to go-live for an operation of our size. What the parallel-run period costs and how long it runs. Which of our systems have pre-built connectors, which require a build, and who maintains them. What implementation support covers on the operating model side, not the technical side.

The coexistence question is the one that most changes the shape of a renewal decision, because it converts a binary into a sequence: layer now, replace at the next renewal with the execution layer already proven.

Where Locus fits

Architecturally, Locus’ DiSCO (Digital Supply Chain Officer) runs eight named agents on a continuous Sense, Decide, Execute, Learn cycle, with the Dispatch agent planning and re-sequencing against 250+ real-world constraints per computation, the Carrier agent allocating across owned and contracted capacity, and six governance mechanisms bounding autonomous action including autonomy levels and human-in-the-loop override. Autonomy levels matter in a renewal context specifically, because they let an operation start narrow and widen on evidence rather than committing to a step change at go-live.

Locus has been recognized by Gartner for seven consecutive years, featured in the 2026 Hype Cycle for Supply Chain Execution and Logistics Technologies, named a Leader in TMS by QKS Group (SPARK Matrix), and ranked #1 in Route Planning on G2’s 2026 Best Software Awards. In October 2025, Ingka Investments, the investment arm of Ingka Group, the world’s largest IKEA retailer, acquired Locus. Locus continues to operate independently. It has optimized 1.5B+ deliveries across 360+ enterprise customers in 30+ countries.

The question to settle first

Before any vendor conversation, answer one question internally: is the problem with our TMS functional or structural?

Functional means the platform does the right things and does some of them poorly, which configuration, training, and pressure on the incumbent can address. Structural means the platform’s data model does not match how the operation runs, most often a shipment-centric system being asked to manage stop-centric work, and no amount of configuration resolves that.

If the answer is functional, renew and negotiate hard. If it is structural, the only question left is whether you layer or replace, and your notice deadline decides which is available to you this term.