TMS Support Tiers: Which Level Do You Need
A buyer's guide to TMS support tiers: the SLA criteria that matter, what's overweighted, and how to size the right level for your operation.
The decision: pick a support tier before you negotiate price
Decide your TMS support tier before you get deep into commercial negotiation, not after. Tier selection happens once, during contracting, and it is far easier to negotiate up front than to upgrade mid-term once you are locked into a multi-year agreement. Most vendors treat a mid-contract tier upgrade as a new sale, which means a fresh price conversation on terms that favour them, not you.
The core tension is simple: buy too much tier and you are paying for named contacts and after-hours phone lines nobody calls. Buy too little and you have no enforceable remedy the day a carrier integration silently stops sending tracking updates during peak season. Both mistakes are common, and both trace back to buyers scoring the wrong line items in the RFP.
Seven criteria, ranked by how much they actually predict outcomes
Here is the order that matters, based on what actually breaks TMS operations versus what sounds good in a sales deck.
- Response time attached to an enforceable remedy. A published target is not a commitment. An uptime figure is a measured statement about the past; an SLA is a contractual commitment with service credits, a claims process, and ideally a termination right if misses repeat. Locus's framework on uptime SLAs draws this line clearly: a measurement method you can audit matters, remedies that matter mean looking for service credits, a claims process and a termination right for repeated or severe misses, and a written definition of downtime should cover degraded performance, API availability and field app availability. If the remedy clause is missing, the response-time number is marketing copy.
- SLA coverage for carrier-integration breaks specifically, separate from platform uptime. Your TMS can show 99.9% platform availability while a single carrier EDI feed goes dark for six hours and nobody is contractually on the hook for it. Ask vendors to define "carrier integration break" as its own failure mode with its own response clock, not something that falls under general uptime language.
- Coverage hours mapped to where you actually operate, not where the vendor is headquartered. A support desk open 9-to-5 US Eastern is functionally useless to a back-office team in Rotterdam dealing with a 6am cutoff. Ask for the support calendar in local time zones before you sign, not the marketing claim of global coverage.
- Escalation path and a named contact versus a ticket queue. This is where tier gaps show up hardest in practice. One Capterra reviewer of Infios's Transportation Management system (formerly MercuryGate) described submitting a support ticket and getting back a request for 8 hours of "Discovery," followed by a 50 hour billable quote, which is a very different experience from a dedicated account contact. LogiCatalog's review flags the same pattern at a market level, noting support response times inconsistent as a recurring weakness, while vendor-listed enterprise packages add dedicated support as a named line item on top.
- Hypercare length and the support hours bundled at go-live. This is the single most concrete, comparable data point across vendors, and almost nobody asks for it directly. Descartes Aljex's own published tiers show the gap plainly: a comparison of MercuryGate and Descartes for small teams lays out that Professional includes 10 hours of support and training and a 30-day hypercare period, while Enterprise includes 15 hours and 90 days, plus two customer EDI connections against one on Professional. The Essential plan includes neither hypercare nor listed support hours at all. That is a real, priced difference between tiers, not a rounding error.
- The price delta between tiers and how it is structured. Flat per-tier pricing is easier to budget than per-user or per-carrier-connection pricing that scales support cost with growth you cannot fully predict at signing. Get the delta in writing before you assume "Enterprise" is a modest step up from "Professional."
- Roadmap and beta access. This is the most commonly overweighted line item on the list, and it sits last for a reason covered below.
Mapping your situation to a tier
The right tier depends on carrier count, geography, and how much operational pain a four-hour outage actually causes you, not on what the vendor calls its top package.
| Shipper profile | Recommended tier | Why |
|---|---|---|
| Single-country, under 10 carriers, back-office hours only | Standard / mid-tier | Cargoson bundles Standard SLA customer support into its mid-tier Standard plan rather than reserving SLA-backed support for the top package, which suits a single-market operation that doesn't need 24/7 phone coverage. |
| Multi-country B2B/pallet network with cross-dock cutoffs | Premium, named contact | Enterprise-tier packages that pair a dedicated contact with hypercare matter most where a missed cutoff cascades across a network. Descartes Aljex's Enterprise plan adds a dedicated customer success manager alongside the longer hypercare window. |
| Fast-growing parcel/multi-carrier mix, adding carriers quarterly | Tier prioritising onboarding speed over phone hours | What you need is fast carrier onboarding, not a 24/7 call centre. Cargoson's model of free, on-demand new carrier integrations matters more here than headline support hours. |
| Regulated or hazmat flows | Premium plus compliance add-on | SAP TM and Oracle TM sell compliance and customer-success support as separate, priced add-ons rather than bundling them, so budget for that line before assuming it's included. |
| 3PL managing multiple client accounts | Tier allowing per-client SLA configuration | A single blanket SLA doesn't fit a 3PL serving clients with different cutoffs. MercuryGate's architecture is built around this: it allows 3PLs to manage separate rating, billing, and reporting environments for each customer under one login, and support tiering should follow the same logic. |
Naming real options against the criteria
No major vendor publishes a single, clean, comparable SLA table across tiers. You have to request every line below in writing during the RFP; none of it should be inferred from a pricing page.
| Vendor | Pricing model | Hypercare / onboarding | Named contact | Published uptime % |
|---|---|---|---|---|
| Infios (formerly MercuryGate) | Quote-only, no published tiers | Not published; dedicated project manager assignment recommended by reviewers | Enterprise tier lists dedicated support; lower tiers report inconsistent response times | Not published |
| Descartes Aljex | Published tiers: $699 / $999 / $2,375 per month | 30 days (Professional) vs 90 days (Enterprise) | Dedicated customer success manager on Enterprise only | Not published |
| SAP TM / Oracle TM | Quote-based, tied to ERP licensing | Sold via implementation partners as a priced optimization period | Premium support and customer success sold as add-ons, not bundled | Not published on vendor pricing pages |
| Cargoson | Published tiers from roughly €199-€599/month plus custom Enterprise | Structured onboarding with go-live support on Advanced tier and above | Priority support line on Advanced tier; Standard SLA support from mid-tier | Not publicly disclosed; ask directly in the RFP |
What's commonly overweighted, and why
"24/7" as a headline looks reassuring and predicts almost nothing. Coverage hours matter far less than whether the first response actually resolves anything or just acknowledges the ticket. A generic scoring checklist, like GoFreight's TMS evaluation checklist, treats an average response under four hours as a top score, but a four-hour acknowledgment that kicks off a billable discovery process is not the same outcome as a four-hour fix.
Generic platform uptime percentage is the second most overweighted number. It is largely decoupled from the support experience you actually feel day to day, because carrier and partner outages affect perceived reliability far more than core application uptime does. Spedity's buyer checklist makes the same point when it recommends checking historical uptime: declared SLA vs actual uptime over the past 12 months rather than taking the headline number at face value.
Roadmap and beta access feels valuable in a demo and rarely changes outcomes for mid-market buyers. Spedity even lists access to product roadmap as part of the support evaluation, but most mid-market teams don't have the internal bandwidth to pilot betas anyway, so this line item is worth almost nothing in the scorecard relative to how often vendors lead with it.
How to write this into the RFP and contract
Ask vendors to define "carrier integration break" explicitly, in writing, and attach a response time and remedy to that specific failure mode rather than letting it hide inside general uptime language. Request hypercare length and included support hours as a written line item, not a verbal promise from the account executive in a demo. A good RFP borrows directly from the framing in a practical buyer's guide that asks, plainly, what tier, what SLA, what channel, and what support exists during the first 90 days of production.
Also treat support location and language as a contract tripwire, not an afterthought. One buying guide frames the question to ask vendors directly: where is support based, what hours do you cover, and what response/resolution SLAs are you putting in the contract. Finally, cap any support-tier upgrade fee in the base contract, so a mid-contract "recommended upgrade" from your account manager doesn't become unbudgeted spend a year into the deal.
Size the tier to the operation, not the sales tier name
Match your support tier to carrier count, operating geography, and how much a broken integration actually costs you in a bad week, not to whatever label the vendor has put on its top package. "Enterprise" on one vendor's pricing page can mean a dedicated customer success manager and a 90-day hypercare window; on another it can mean the same ticket queue with a nicer badge. Get the specific response times, the carrier-integration remedy, and the hypercare hours in writing before you sign, and you will spend less time arguing about a support bill and more time actually running freight.