What does a TMS integration do?

A TMS integration connects your transportation management system to Cargado. Loads sync from your TMS into Cargado, and your posting rules decide which ones reach carriers. Carrier bids come back to the load in your TMS, and when you book a carrier, the booking syncs back too.

Step 1: Save the load in your TMS

The load comes into Cargado through the integration, with its details carried over. Depending on your TMS, that happens when you save the load or on the next scheduled sync. Syncing itself does not publish the load; carriers see it once it is posted.

Step 2: Let your posting rules decide what posts

Nothing reaches carriers until you or your rules post it. Rules can match loads by lane and equipment type, so dry van and flatbed on the same lane can follow different rules, and a rule can post a load as soon as it syncs. Loads that are available, eligible to post, not expired and not yet posted or matched wait in Review to Post. To set up the rules, see Set up auto-posting rules.

Example: the company, loads and counts are fictional.

1. Review to Post: available, posting-eligible, unexpired loads that are not posted or matched yet.
2. Posted: the loads you have posted.

Step 3: Watch carriers bid on the posting

A posting that came in through your integration shows a TMS synced tag, and carriers see your company name on it. On a load that crosses the border, a bid can be itemized into the Mexico portion, the border crossing and the U.S. portion, or given all-in.

Example: Pied Piper Logistics and the posting are fictional.

1. TMS synced: the load came in through your integration.
2. Your company name, as carriers see the posting.

Step 4: Follow the bids

Bids arrive in Cargado under Pending Bids, and each bid also comes back to the load in your TMS. When you book the carrier, the booking syncs back to your TMS too.

Step 5: Confirm the truck in Cargado Chat

Once the load is matched, you and the carrier can talk in the freight chat about the truck, trailer, crossing partner and pickup time. Carriers are notified by email, and by WhatsApp where that is set up, and Chat can show messages translated between English, Spanish and French.

During setup, we confirm which status in your TMS means a load is no longer available. When that status syncs, Cargado takes the posting down, so carriers stop chasing freight that is already gone.

Tip: The rate confirmation to the carrier still comes from your team. The integration brings loads in, lets your rules post them and sends bids and the booking back to your TMS; it does not replace your confirmation.

Good to know

• Which TMSs connect: Cargado has integrations for Tai (Tai + Descartes), McLeod, Turvo and Revenova. Ask your Cargado contact which one is available for your account. If your team is on another system, you can connect through the Cargado API.
• On Revenova today: Revenova loads sync into Cargado and post under your rules. If your team wants to decide load by load what posts, your Salesforce admin can create a Post to Cargado checkbox that your Cargado contact maps; unchecking it takes the posting down. When the load changes in Revenova, Cargado updates the posting or takes it down. Carrier bids come back to the load in Revenova, and when you book a carrier, the booking syncs back too. Carrier Sync is not connected to Revenova yet.
• What setup takes: access that your team supplies:
  • Tai: a Tai staff user you create for Cargado, with the permissions we list, and its API key; the five Cargado webhook URLs and bearer token registered in Tai; and the JSON report codes for two custom reports, shipments and carriers, covering the last 12 months. See Set up your Tai integration.
  • McLeod: the URL of your McLeod instance and a McLeod API token for Cargado. You need McLeod API access; if you only have the DFM module, tell us before setup. See Set up your McLeod integration.
  • Turvo: an API user in Turvo set up for Cargado, with its password, plus your Turvo API key, client name and client secret, plus a webhook so Turvo tells Cargado about shipment, carrier and user changes. See Set up your Turvo integration.
  • Revenova: your Salesforce admin sets up the connection with your Cargado contact. See Set up your Revenova integration.
  During setup we also map your TMS users and teams to the right people in Cargado, so synced loads reach the right owner; where a mapping is missing, Cargado uses the fallback owner if one is configured. Then you set your posting rules and freight starts reaching carriers. Send credentials directly to your Cargado contact, never in a shared chat.
• Carrier Sync, your compliance statuses in Cargado: On McLeod, Tai and Turvo, Carrier Sync brings each carrier's compliance status from your TMS into Cargado. On your freight a carrier shows as Onboarded, Needs to onboard or Do not dispatch. A carrier who needs to onboard is shown your onboarding requirements and, if you provide one, your onboarding link. A carrier you've marked Do not dispatch never sees your freight in the marketplace.
• Postings and your plan: each shipment posted from your TMS counts as a posting on your plan, the same as one you post by hand. See Plan limits, and what the usage warning emails mean.
• To start an integration, ask your Cargado contact or email success@cargado.com. For more, see Cargado integrations and Cargado for Tai.