MercuryGate vs Descartes TMS: Which Fits in Small Teams 2027

Pick by business model before you compare brands

A transportation management system (TMS) is software that plans shipments, rates and tenders them to carriers, tracks them, and passes freight costs to accounting. For a small logistics business, the first decision is the business model, not the brand. A freight brokerage, a shipper running its own moves, and a 3PL need different workflows, and the vendors in this comparison sell to different buyers.

Two naming problems come first. MercuryGate TMS is no longer sold under that name. Körber announced a signed agreement to acquire MercuryGate on August 6, 2024, according to Körber (2024), and the Infios product page now states that "MercuryGate's TMS is now Infios Transportation Management (TM)," according to Infios (2026). Older directories and review sites still use the MercuryGate name, so match on the product description rather than the label.

"Descartes TMS" is not one product either. Descartes bought 3GTMS, a platform for shippers, third-party logistics providers and freight brokers, in March 2025. 3G deal price: $115 million according to SEC (2025). Its Aljex brand, which the Aljex pricing page calls the Descartes Aljex cloud-based TMS, is aimed at freight brokerages. A brokerage therefore has to choose between Aljex and 3G TMS, and that choice mostly comes down to price transparency and scope.

The short version: pick Aljex if you broker freight and want published tiers. Pick Infios or 3G TMS if you run multimodal freight and can handle a quote-based process with an owner for integrations.

Key Takeaways

• TL;DR: Aljex is the only option in this comparison that publishes monthly prices. Infios Transportation Management and Descartes 3G TMS are quote-based.

• MercuryGate TMS is now sold as Infios Transportation Management, and Descartes' TMS offer is split across 3G TMS and Aljex.

• Infios targets shippers and 3PLs across every mode. Descartes 3G TMS targets shippers, 3PLs and brokers. Aljex targets freight brokerages.

• Quote-based pricing hides scope. Ask every quote-based vendor for migration, connector and go-live tasks in writing before you compare totals.

• Descartes announced in August 2026 that it is buying Tai, an AI TMS for freight brokers, so brokers should ask how that changes the roadmap.

• Choose by business model first, then compare written scope and fees rather than which name looks familiar.

How we evaluated these tools

This guide is built from public pages only: vendor sites, a regulatory filing, trade press and a review comparison. It includes no demo, trial or customer interview. The table below weights six criteria for a small team. The weights are our judgment, not vendor scores. We did not use star ratings, because the G2 and Capterra pages we tried to open returned access errors.

Business-model fit carries the most weight because a tool built for the wrong buyer generates workarounds that no price comparison will show.

Feature matrix: what each vendor publishes

The facts in this table come from vendor pages and the sources cited elsewhere in this guide. The fit judgments in later sections are ours.

The Infios and 3G columns describe marketing-level pages, so verify each row against your own lanes, carriers and ERP before you rely on it. The Aljex column is the most specific of the three, because its pricing page itemizes integrations by tier.

Pricing and first-year cost

Only Aljex publishes prices among these three options. The table below lists its tiers as its pricing page shows them.

Essential plan price: $699 per month according to Aljex (2026). Two cost items sit outside that line. The Aljex page says "Customers must still purchase subscriptions with third parties when required," and it lists setup and integration fees as one-time charges, so the monthly figure is not a full first-year cost. The Professional and Enterprise prices are "from" figures, so ask for the full tier before you treat the starting number as your cost.

Pricing checked October 25, 2026. Infios and Descartes' 3G TMS publish no prices, so their rows below read Quote-based.

Worked example, with illustrative volumes: take a brokerage team on five seats, the number the Essential plan includes, that handles 300 loads a month and spends four minutes per load matching carrier invoices to rate confirmations. That is 300 × 4 = 1,200 minutes, or 20 hours of AP and planner time every month before any exception work. A proposed US Tech Automations flow would take over the matching step. The trigger is a new carrier invoice in the AP mailbox or a freight audit export. The action compares load ID, rate and accessorials against the rate confirmation and creates a draft bill in QuickBooks, with Bills.DueDate set from the agreed terms, the field described in CData's QuickBooks Online Bills reference. The output is a draft for each clean invoice plus a mismatch list for the planner. Prerequisites are QuickBooks API access, a carrier invoice export or audit output, and an agreed tolerance for each accessorial. Human review points are an AP clerk who approves each draft before posting, and a planner who resolves every mismatch rather than letting the flow correct it. The 20 hours is a number to test, not a promised saving, because the flow only returns that time if your invoices arrive in a consistent format.

Vendor profiles: best fit, limits and evidence

Infios Transportation Management (formerly MercuryGate TMS)

Best fit: shippers and 3PLs that move freight across several modes and regions, with an internal or partner owner for ERP and EDI work. The Infios transportation management page says its product connects moves "across every mode, geography and industry," and it lists a Freight Audit and Payment module and a Claims Management module as separate pieces. The same page cites 70-plus pre-built integrations and Infios load tendering claim: 80% faster according to Infios (2026). Both are vendor-published claims, so ask for the measurement method and a customer reference you can call.

Limits: no price is published, so a small team cannot compare it on cost until a quote arrives. A comparison page that says it drew on 1,821 reviews from six review sites, according to RFP.wiki, lists a steep learning curve and admin-heavy daily workflows as recurring complaints about MercuryGate. That page does not label every bullet by vendor, so treat those complaints as directional and test them against your own workflows.

Implementation: the Infios pages reviewed here publish no implementation timeline and no fee schedule. Ask for a written plan that names data migration, EDI partners, ERP mappings and the admin roles your team will need after go-live.

Descartes 3G TMS

Best fit: mid-market shippers, 3PLs and freight brokers that need LTL and drayage coverage. Descartes' acquisition release names the customer segments as "shippers, third-party logistics providers and freight brokers" and says the deal adds "a network of API-integrated LTL carriers." The release puts the purchase at $115 million, according to Descartes (2025).

Limits: Descartes publishes no price for its TMS. The 3G shipper page lists Rating and Optimization, Carrier Management, Visibility, Settlement and Invoicing, and AI and Automation, but it names no ERP connectors. Roadmap is the other open question. Tai deal price: $100 million according to Transport Topics (2026). That article describes Tai as an AI-powered TMS for freight brokers, so a brokerage choosing 3G should ask how the two products will relate.

Implementation: the 3G shipper page says "weeks to go-live" but gives no number. Ask for a dated plan before you sign.

Descartes Aljex

Best fit: freight brokerages. The Aljex pricing page says its platform is "built to scale and support freight brokerages regardless of size," and it lists five users on Essential and 15 on Professional, according to Aljex (2026).

Limits: the Essential plan lists no support hours, hypercare period or customer EDI connections, which appear on Professional and Enterprise. Third-party subscriptions can sit outside the platform fee, as noted above. Aljex is built for brokerages, so a private fleet or shipper-only team is outside its stated fit.

Implementation: Essential carries a one-time setup fee, and Professional and Enterprise carry one-time implementation fees. Professional includes 10 hours of support and training and a 30-day hypercare period. Enterprise includes 15 hours and 90 days, plus two customer EDI connections against one on Professional.

Who this is for, vendor by vendor

Infios Transportation Management fits multimodal shippers and 3PLs that have someone to own ERP and EDI work.

Red flags: you need a published price before you shortlist, nobody internal will own data mapping, or your freight is a single mode on a narrow set of lanes.

Descartes 3G TMS fits mid-market shippers, 3PLs and brokers that want LTL and drayage coverage and can run a negotiated process.

Red flags: you need a fixed monthly price before any sales conversation, you want a shipper-only tool with no brokerage features, or you have no need for LTL or drayage.

Aljex fits freight brokerages that want a published starting price and a five-seat start.

Red flags: you are a shipper or private fleet without brokerage operations, you expect every third-party subscription to be included in the platform fee, or you need multimodal planning beyond brokerage workflows.

Where the work piles up after you pick a TMS

Most small-team pain shows up after go-live, in exceptions the TMS does not close on its own: a load that stops reporting, a carrier that never returned paperwork, or an invoice that does not match the rate confirmation. A proposed US Tech Automations exception check could run each morning. The trigger is a load with no status update for a window the planner sets. The action opens an exception record with the load ID, carrier, lane and last check-call time. The output is a list sorted by customer deadline for the planner. The prerequisite is a status export or read access from the TMS; Infios lists APIs, EDI, SFTP and webhooks among its integration options, and Aljex lists API Export and CSV Export. The human review point is the planner, who decides whether to call the carrier, and the flow sends no carrier or customer message on its own.

Zapier, Make and n8n are a fair alternative for this kind of work. Configured well, they keep run histories, retries, error branches and audit evidence. The buyer still designs and owns idempotency, so a retry never posts the same bill twice, along with escalation paths, access controls, and upkeep whenever a connected API changes. A proposed US Tech Automations design could configure run logs, retry limits and approval gates as part of the build, but it needs the same API prerequisites, and someone on your team still owns each exception type.

Mistakes and a checklist before you sign

Common mistakes:

• Treating "Descartes TMS" as one product, then comparing a brokerage plan with a shipper platform.

• Comparing Aljex's monthly starting price with a quote-based total that leaves out setup, integration and third-party subscription costs.

• Searching for MercuryGate and assuming the current product sheet still uses that name.

• Accepting a go-live date without a written list of connectors, EDI connections and data to migrate.

Decision checklist:

• Am I a brokerage, a shipper, or a 3PL?

• Which accounting system and ERP must connect on day one?

• Which load boards and visibility providers do I use today?

• Who on my team owns exports, EDI and carrier setup after go-live?

• Can the vendor put migration tasks, fees and go-live dates in one written document?

Verdict by business model

For a brokerage that wants a published starting point, Aljex is the closest fit in this set. For a multimodal shipper or 3PL with an IT owner, Infios is the broader platform, though expect a quote-based process. For a mid-market shipper, 3PL or broker that needs LTL and drayage coverage, Descartes 3G TMS belongs on the shortlist, with the Tai roadmap question added.

When NOT to use US Tech Automations: skip an automation layer in any of these three cases. First, the built-in invoicing or load board in the TMS you pick already covers your exception volume, and a person can handle the rest by hand. Second, a native connector such as Aljex's QuickBooks integration already moves the data you need, and no process change is required. Third, you have not chosen a TMS or defined your exception rules yet, because automating an undefined process only makes the confusion faster.

Questions buyers ask before shortlisting

Is Descartes TMS a single product?

No. Descartes sells 3G TMS for shippers, 3PLs and brokers, and Aljex for freight brokerages, and each has its own pricing path.

Is MercuryGate TMS still sold?

Not under that name. The product is now sold as Infios Transportation Management, so search for that name when you request a quote.

Which option shows a price before a sales call?

Aljex is the only option in this comparison that publishes monthly prices, and its tiers appear in the pricing section above.

Can a shipper use Aljex?

Aljex describes its platform as built for freight brokerages, so a shipper or private fleet should look at 3G TMS or Infios first.

Does a small team need an ERP connector on day one?

Not always. Aljex lists QuickBooks, NetSuite, Sage and GreatPlains among its accounting integrations, while Infios names SAP, NetSuite, Oracle and Dynamics as examples of the ERP platforms it supports.

Should I skip a TMS and use Zapier, Make or n8n?

Only if your freight is simple enough that you will own the run logs, retries, idempotency and access controls yourself. A TMS holds the load and carrier records those tools would otherwise have to reconstruct.

What to do this week

Start with the business-model question, then send each vendor the same written request covering migration tasks, connections, fees and a dated go-live plan. Compare Aljex's published tiers against the third-party subscriptions it says may still be required, and compare the quote-based proposals from Infios and Descartes against that same list. To see how the exception and invoice flows above would be configured, see how US Tech Automations configures this.