A TMS is the software brokers and shippers use to plan, execute, and settle freight: quoting, tendering, tracking, documents, and billing. Most U.S. TMS platforms were built for domestic freight and lack native fields for cross-border data like Mexican postal codes and crossings.
A TMS, transportation management system, is the operating software of freight: the system where loads are built, quoted, tendered to carriers, tracked, documented, and settled. Brokers run their businesses inside one; shippers use theirs to manage carriers and freight spend; and integrations (EDI, APIs) stitch TMS platforms to carriers, marketplaces, and visibility tools.
The cross-border catch: most U.S. TMS platforms grew up on domestic truckload, and their data models show it. Common gaps include Mexican postal codes and addresses that fail validation, no native concept of a border crossing or transfer leg, nowhere to store CTPAT status, CAAT codes, or dual-entity carrier structures, and single-currency assumptions that mangle peso-dollar moves.
If you run cross-border freight through a domestic-first TMS, design your workarounds deliberately instead of accumulating them accidentally: decide where crossing data, Mexican references, and second-currency amounts live, and standardize so reporting stays usable. When evaluating cross-border tools and marketplaces, integration questions belong early in the conversation: what flows into the TMS automatically, which documents (PODs, customs docs) attach to the load record, and whether the integration costs extra. A cross-border operation whose systems reflect how the freight actually moves, three legs, two countries, two currencies, scales; one running on spreadsheet sidecars does not.
Cargado connects 250+ brokers with 2,000+ vetted carriers moving Mexico and Canada freight every day.