What does a TMS integration do?

A TMS integration syncs loads, rates and carrier status into Cargado automatically; Cargado sets it up with your team.

Broker
Updated
September 21, 2026

A TMS integration connects your transportation management system to Cargado so eligible freight, rates and carrier status flow in automatically, without anyone re-typing a load. Cargado sets it up with your team; your McLeod, Turvo, Tai or Revenova instance stays the system of record, and Cargado mirrors it.

What syncs, and in which direction

Everything flows one way: from your TMS into Cargado.

A matched load's action bar: Matched USD $2,700, a dimmed Mark TMS assigned button outlined in blue with the tooltip "Bookings are automatically synced via TMS integration," and Cancel match.
With a TMS connected, the booking goes back to your TMS on its own.
  • Load sync. Shipments in your TMS are created or updated in Cargado as loads. The load's status and carrier assignment in your TMS decide whether Cargado treats it as open, booked or canceled.
  • Rate sync. Your TMS's target rate and max buy rate come across with the load and drive your auto-posting rules, including whether a load posts as bid-only when the TMS rate is missing.
  • Carrier sync. Carrier assignment and status reported by your TMS keep the matching booking in Cargado in sync: a load your TMS shows as assigned or canceled is reflected the same way here.

Important: Bids and matches are not written back to your TMS today. When a load came in through the integration, Mark TMS assigned is disabled in Cargado because your TMS is expected to be the source of truth for that assignment; carrier booking still happens in your TMS. See Work your bids for how to manage bids on a synced load.

Which TMSs are supported

Cargado has built integrations for McLeod LoadMaster, Turvo, Tai and Revenova (a Salesforce-native TMS). A custom integration path also exists for other systems; ask your Cargado contact.

What your IT or ops team provides

Cargado staff configure the integration; your team supplies the access. What that looks like varies by TMS:

The freight sidebar with Review to Post outlined in blue, between Posted and Pending Bids.
Loads your TMS sends to Cargado wait in Review to Post.
  • McLeod: API access to your McLeod instance (contact Cargado if you only have DFM module access), your McLeod API URL and Company ID, and either an API authentication token or a McLeod username and password.
  • Turvo: An API user created in Turvo, plus the resulting client ID, client secret, API key and default group ID. You'll also set up a webhook in Turvo so it notifies Cargado of shipment, carrier and user changes.
  • Tai: A new LSP staff member and a Public Authentication Key created in Tai's LSP menu, plus a Shipment Report and a Carrier Report (each identified by a report GUID) built in Tai. After Cargado saves your credentials, your team pastes Cargado's webhook URLs into the Tai portal to complete the sync.
  • Revenova: Credentials from a Salesforce Connected App configured for Revenova, since Cargado authenticates using the Salesforce JWT Bearer flow.

During setup, Cargado also maps your TMS teams, users and workspaces to the right people in Cargado, so synced loads and notifications reach the right person. Synced loads land on your board and wait under Review to Post until someone posts them, unless your auto-posting rules post them for you.

To start, or to check on an integration in progress, email success@cargado.com or ask your success manager.

Still stuck?

Email us and a person on our team will answer. Send the posting link or a screenshot if you have one.