Nearshoring did not just add lanes. It added a second working language to the operating day. The US-Mexico cross-border freight transport market is projected to grow from $91.12 billion in 2025 to $95.65 billion in 2026. Truck crossings at Laredo rose 28% between 2019 and 2024, and trade volume has expanded roughly 80% over five years.

The concentration is remarkable. Roughly 12,000 trailers circulate through Laredo's crossings on an average day, with peak-day inspections handling up to 21,000 trucks. Laredo handled more than $33.4 billion in a single month in 2026 — over 40% of US-Mexico trade, with Detroit a distant second at about $12.44 billion.

Behind that volume is a communication reality most US brokerages have not staffed for: a meaningful share of carrier dispatch, driver contact and customs coordination happens in Spanish, and it happens at the same hours as everything else.

The gap is response quality, not translation

Machine translation solved the comprehension problem years ago. Anyone can read an inbound Spanish message.

The gap is on the response side, and it is about quality and speed rather than meaning. A brokerage with two Spanish-speaking coordinators can respond well in Spanish — during those coordinators' shifts, at their throughput, on the accounts they cover. Everything else gets a slower reply, a stiffer machine-translated one, or a reply in English that shifts the translation burden onto the carrier.

None of those is fatal on any single message. In aggregate, they are the reason a carrier chooses a different broker — and with 86% of brokers reporting that capacity is harder to find, giving Mexican carriers a reason to prefer someone else is expensive.

What actually needs to work in both languages

• Carrier capacity outreach — Language reality: Spanish-first for many carriers · Cost of a slow or awkward reply: Lost coverage on the lane
• Dispatch and driver coordination — Language reality: Predominantly Spanish · Cost of a slow or awkward reply: Delays at the crossing
• Customs broker exchange — Language reality: Mixed, document-heavy · Cost of a slow or awkward reply: Detention at the border
• Facility appointment booking — Language reality: Depends on side of the border · Cost of a slow or awkward reply: Missed windows
• Customer status updates — Language reality: Usually English · Cost of a slow or awkward reply: —
• Exception notification — Language reality: Whoever is affected · Cost of a slow or awkward reply: Compounds fast

The rows that matter most are the ones where the counterparty is choosing whether to work with you: carrier outreach and dispatch coordination. Those are also the highest-volume, most repetitive ones — which makes them the natural place to remove the language constraint entirely.

Should freight communication be automated in Spanish?

Yes, for the high-volume operational exchanges — capacity outreach, dispatch coordination, status updates and document requests — where the content is factual and the value is in responding immediately and correctly rather than in nuance. Commercial negotiation and relationship-sensitive conversations should stay with a bilingual human.

That split follows the same logic as any autonomy boundary: automate where the content is determinate and the error is recoverable, escalate where judgement or relationship is involved. Language does not change the principle. It changes who is available to execute it, and when.

The practical effect is that Spanish-language response quality stops depending on which two people are at their desks. A carrier emailing at 8pm gets the same answer they would have gotten at 10am.

The document layer is where the real time goes

Cross-border freight is document-dense in a way domestic freight is not: commercial invoices, packing lists, certificates of origin, customs entries, the pedimento. Errors and omissions are the leading cause of delay at the crossing, and average peak wait times already run 45 minutes at Laredo and over 55 minutes at Otay Mesa before any paperwork problem is added.

The high-value automation here is validation before arrival rather than translation. Checking that a document set is complete and internally consistent — quantities matching across the invoice and packing list, classifications present, parties named consistently — is mechanical work that prevents a truck sitting at the border.

This is the same document validation pattern that applies to customs work generally, and it compounds with the language question: a document exchange that requires both translation and completeness checking is exactly where manual processes add hours.

Where the language constraint becomes a capacity constraint

Nearshoring freight growth has outpaced warehouse and drayage capacity at the border. That means the operational bottleneck is not finding freight, it is executing it — and execution is coordination across carriers, facilities, customs brokers and drivers, in two languages, under time pressure.

A brokerage whose Spanish-language throughput is capped by headcount has a hard ceiling on how much cross-border business it can take on, no matter how much freight is available. Removing that cap is a growth question rather than an efficiency one, which is a different and better argument for automation.

It also connects to sourcing. When coverage depends on how many carriers you can reach quickly, a network where a portion of carriers can only be worked by two people is a network you are only partially able to use.

What to check in your own operation

1. Median response time to Spanish-language inbound, compared against English. If there is a meaningful gap, that gap is visible to carriers.
2. After-hours Spanish coverage. Usually zero, and border operations do not run on office hours.
3. Share of your carrier network you can actively work. Not the list size — the portion your team can realistically reach in a language they operate in.
4. Border delays attributable to documentation. Separated from delays attributable to inspection volume, because only one of them is yours to fix.

Frequently asked questions

Is machine translation good enough for freight operations? For comprehension, yes. The gap is generating responses that are accurate about freight specifics and fast enough to matter — a status reply in twenty minutes in correct Spanish beats a carefully composed one tomorrow.

Which cross-border workflows should stay human? Rate negotiation, claims and relationship-sensitive conversations, same as in domestic freight. The operational exchanges — capacity, dispatch, status, documents — are where automation belongs.

How large is US-Mexico cross-border freight? The market is projected at roughly $95.65 billion in 2026, up from $91.12 billion in 2025. Laredo alone handles over 40% of US-Mexico trade, exceeding $33.4 billion in a single month.

Does this apply to Canadian cross-border too? The document validation and appointment coordination benefits apply directly. The language dimension is narrower, which makes the Mexico corridor the one where multilingual capability changes throughput most.

The bottom line

Cross-border volume is growing into infrastructure that is already congested, and a large share of the coordination happens in Spanish at all hours.

Automate the operational exchanges in both languages so response quality stops depending on who is at their desk, validate document sets before the truck reaches the crossing, and keep negotiation with bilingual humans. The language cap is a capacity cap.

Debales deploys AI agents for freight quoting, order processing, ETA updates, and multi-channel customer communication — operating across languages and channels so carrier and customer response times don't depend on shift coverage. Book a demo.