MercuryGate

MercuryGate, now part of Infios, is the enterprise TMS many shippers and 3PLs use for rating, tendering and freight settlement. Shipments, tenders, tracking events and audit records from MercuryGate appear in Cargofy, and digital workers handle the carrier follow-up that otherwise runs through email and tracking portals. The transport manager who owns tendering usually switches it on, with IT and the MercuryGate integration team handling access.

What teams use it for

Tender a shipment from Load Hub

A planner builds the shipment in MercuryGate, and it lands in Load Hub with the lane, equipment and dates. A digital worker tenders it to your contracted carriers in Carrier Network, watches for the reply and writes accept or decline back to MercuryGate. The planner sees a covered load in Load Hub and a closed tender in the TMS, with no re-keying in either.

Check a carrier rate against TMS rating

Rates and carrier selection from MercuryGate are read into Sales and Freight Procurement, so a carrier's quote sits next to the TMS rate for that lane. The digital worker flags any carrier priced above the contracted rate. The planner decides in one view, and the decision is recorded in Cargofy.

One timeline for EDI, GPS and check calls

One carrier sends an EDI 214 status, another truck reports a GPS ping, a third driver phones in a check call. Each lands in MercuryGate in its own format. Cargofy reads every event from your instance, and a digital worker normalizes them onto one timeline per shipment in Tracking. When a customer asks where the load is, the customer service rep reads position and status there without touching raw EDI. When a pickup runs late, the worker opens an exception and routes it to the lane's planner.

Catch detention while the truck is at the dock

A driver waits past free time at a Dallas receiver. The check call is in MercuryGate, but often nobody looks at it until the carrier invoices detention two weeks later. The digital worker sees the dwell on the timeline, opens a detention exception in Tracking and attaches the check-call log to the shipment. The planner can call the receiver while the truck is still there, and Finance has the evidence when the invoice arrives.

Match the carrier invoice to the shipment

Freight audit and settlement records (EDI 210, 810, 820) are read from MercuryGate into Finance. The AP clerk sees each carrier invoice matched against the tendered rate, the accessorials on the timeline and the BOL from Documents. The digital worker marks clean matches for approval and holds mismatches with a reason, such as a rate above the tender or an accessorial with no exception on record. The clerk works only the held invoices.

How it fits your stack

MercuryGate stays the system of record for shipments, carriers, contracts and settlement. Cargofy reads shipments, orders, rates, carrier profiles, tracking events, documents and settlement records, and writes shipment updates and tender accept and decline decisions back. The connection is set up per installation: your MercuryGate admin obtains IP-bound credentials through the Infios integration team, and Cargofy maps your instance schemas and EDI flows. Cargofy does not change carrier master data or rate contracts inside MercuryGate, and there is no self-serve activation.

Who it is for

Shippers and 3PLs running MercuryGate for multimodal freight, with a transport planner who tenders, a customer service desk that watches shipments and an AP team that audits carrier invoices. 3PLs with several client environments connect each one as its own connection.