According to a FreightWaves analysis published on June 23, 2026, the logistics industry faces a seismic shift in compliance obligations following two landmark government actions. On May 22, 2026, the U.S. Supreme Court issued a unanimous decision in Montgomery v. Caribe Transport II that removed a legal shield freight brokers had relied on for decades. Eleven days later, a White House Executive Order extended compliance obligations across the entire logistics chain, targeting forced labor, misclassification, undervaluation, and illegal transshipment with criminal enforcement authority.
Supreme Court Ruling Removes Preemption Shield
The Court's holding in Montgomery v. Caribe Transport II is precise, according to FreightWaves: state negligent carrier selection claims against freight brokers are not preempted by federal law. This means a plaintiff whose cargo was damaged, lost, or involved in an accident can now sue the freight broker directly for failing to exercise reasonable care in selecting the carrier. The Court did not define "reasonable," but the article states that the definition will be written in discovery, deposition, and verdict over the next five years. The direction is clear: reasonable care is moving toward a documentation standard, not an intention standard.
Executive Order Expands Enforcement
The White House Executive Order, issued eleven days after the Supreme Court decision, extends compliance obligations across the entire logistics chain. The order targets forced labor, misclassification, undervaluation, and illegal transshipment, and comes with criminal enforcement authority, according to FreightWaves.
New Documentation Standard for Brokers
The article spells out what reasonable care now requires for freight brokers:
- Live carrier screening at every load assignment — not cached, not periodic, not at onboarding only
- OFAC SDN and BIS Entity List verification at every handoff — not just at initial carrier setup
- ELD transit monitoring that is tamper-evident and cryptographically sealed
- A court-ready compliance certificate that documents every verification event with a forensic timestamp
| Requirement | Description |
|---|---|
| Carrier screening | Live check at every load assignment, not just at onboarding |
| OFAC/BIS verification | At every handoff, not just initial setup |
| ELD monitoring | Tamper-evident and cryptographically sealed transit monitoring |
| Compliance certificate | Court-ready document with forensic timestamps for every verification event |
According to FreightWaves, a freight broker who can produce that documentation when a plaintiff's attorney requests discovery is in a fundamentally different legal position than one who cannot. The documentation does not eliminate liability; it defines the battlefield.
NVOCCs Face Carrier-Grade Liability
Non-Vessel Operating Common Carriers (NVOCCs) occupy a uniquely exposed position in the post-Montgomery landscape, the article reports. Unlike freight brokers who arrange transportation, NVOCCs issue their own House Bills of Lading. They are carriers in the eyes of the law, meaning they owe carrier-grade duties to shippers even though they do not operate the vessels. This creates a compliance obligation that freight brokers do not face: the NVOCC is responsible for every party in the chain they assemble — the ocean carrier they book, the drayage operator at origin, and the warehouse handling the cargo at the foreign port. If any one of those parties appears on OFAC's Specially Designated Nationals list — before, during, or after the shipment — the NVOCC is exposed.
Implications for Operators
The FreightWaves article emphasizes that these two events did not create new problems; they exposed problems that already existed and handed plaintiffs' attorneys and federal prosecutors the tools to act on them. The question every logistics operator should be asking is not whether they are compliant, but whether they can prove it — cryptographically, at every handoff, in real time, in a format that holds up in federal court. For most of the industry, the answer is no.
Sources:
