Home / Integrations / MercuryGate
AI for MercuryGate
Last updated October 11, 2026.
AI for MercuryGate follows the rename: on October 11, 2026, mercurygate.com redirected to Infios, and Infios's transportation management page says MercuryGate's TMS is now Infios Transportation Management.
MercuryGate isn't connected today. FreightScout works the carrier replies after Infios AI's recommendation, calls in the stretch after an appointment update goes quiet, and follows the customer bill the freight audit hasn't closed. Your team keeps Infios Transportation Management current. By API where the TMS offers one, and by reading it in place where it doesn't, set up during implementation. Connor walks through your TMS on the demo.
Sources, read on October 11, 2026: Infios's transportation management page. mercurygate.com redirected to Infios that day.
What the old domain does now
A team that learned this TMS as MercuryGate opens a product Infios now calls Infios Transportation Management. On October 11, 2026 the old domain redirected to Infios's homepage. The transportation management page is a separate address, and that's where the rename is written down.
A document still has to become an order
Infios's page says generative AI accelerates document processing and order creation. That's Infios's step, on Infios's product. A tender can leave that step and still be short of something a carrier can price: a second stop buried in the PDF, a date in the email and a different date on the attachment, a weight nobody confirmed. FreightScout isn't Infios's document tool, and it doesn't take that tool's place.
Tendering that stops at a recommendation
The page says the TMS automates carrier onboarding and load tendering. Infios AI, described there, can recommend or automate carrier selection, rerouting, and appointment updates inside guardrails the business sets. A recommendation inside those guardrails still isn't a truck booked at your max pay. Someone still has to work the replies. Working those replies is supervised by default, switch to autopilot per team and per action. Every action is logged and reversible.
Not a TMS, not a load board, and the TMS stays the system of record.
The quiet stretch after an appointment update
The page describes status updates and end-to-end shipment visibility. An appointment update can post, and the following status can sit while the driver misses a window that opened after that update. The visibility is real. The hole is the time between one update and the next, when the record looks current and the dock doesn't.
FreightScout places the check call in that stretch, once the status has gone stale and nobody has said why. The call asks what happened after the last update.
Freight audit is on the page. The chase often isn't finished.
Infios's page says the TMS handles freight audit and payment. That audit stays Infios's. The audit can already have the POD on the file while the brokerage is still the one the customer hasn't paid. FreightScout follows that unpaid bill on the brokerage side until it closes.
The same page says Infios Transportation Management connects to warehouse, order, and ERP systems, and it names SAP, NetSuite, Oracle, and Dynamics, by EDI and APIs. Those connections are Infios's. FreightScout doesn't book freight inside the warehouse system or the ERP. Plans are on pricing.
Questions buyers ask
Does Infios AI book the truck at my max pay?
No. Infios's page says its AI can recommend or automate carrier selection inside guardrails you set. A recommendation still isn't a truck booked at your max pay. FreightScout works those replies.
Does the freight audit send the customer's invoice?
No. Infios's page says the TMS handles freight audit and payment. A POD can match inside that audit while the customer is still unpaid on your side of the file. FreightScout chases that bill.