Signs your freight was re-brokered without your consent, why it happens, and what to check before you dispatch the next load.
You booked the load with one carrier. Now the truck that shows up has a different company name on the door, the driver doesn't know the broker you dealt with, and nobody will confirm who actually has your freight. This is the moment most shippers and brokers first realize a load has been double brokered — and by then, it's already in motion.
Double brokering happens when a carrier that was awarded a load turns around and re-assigns it to another carrier, without permission, often to a company with no vetting history or insurance you can verify. Sometimes it's a legitimate capacity crunch handled sloppily. Sometimes it's fraud, where the original "carrier" never intended to haul the load at all and disappears once payment is collected — leaving the real carrier unpaid and the freight's location in question.
No single flag proves a load has been double brokered, but a cluster of them should stop you before pickup or during transit.
Carrier vetting practices vary a lot across the industry. Some brokers check authority status and insurance once, at onboarding, and never look again. Others check FMCSA records every time a load is tendered. Because a carrier's authority, insurance, and safety status can change between loads — or because a legitimate carrier can subcontract a load to a broker-carrier hybrid without telling you — a single point-in-time check often isn't enough to catch a re-brokered load before it happens.
A few habits reduce the risk significantly:
Stop further payment until you can confirm who physically has the freight. Contact the carrier of record directly through their FMCSA-listed phone number. Document everything — rate confirmations, texts, driver and truck information — because this paper trail matters if you need to involve law enforcement, FMCSA, or your insurer. Ellys International Logistics vets every carrier in its network against live FMCSA data before dispatch and continues monitoring status afterward, which is one way this kind of surprise gets caught before it becomes a bigger problem.
If you want a carrier or a load checked before you commit to it, start at /vet.