Shipper of record: who is actually liable when something goes wrong

A pallet shows up damaged. Or it doesn't show up at all. The claim gets filed, and then the real fight starts: not about the damage itself, but about who is actually responsible for it. The shipper, the broker, the carrier, and the insurance company all point in different directions, and the term that keeps coming up is "shipper of record." Most people in that argument don't actually know what it means.

What shipper of record means

The shipper of record is the party legally named as the origin of the shipment on the bill of lading and other transport documents. It's not necessarily the company that owns the goods, and it's not automatically the company that booked the load. It's whoever is documented as the shipper at the point of tender. That distinction matters because liability tends to follow the paperwork, not the business relationship people assumed they had.

If a manufacturer sells goods to a buyer but a third party books and tenders the freight, the shipper of record on the BOL may be the third party, not the manufacturer. If something goes wrong, the carrier's liability obligations run to whoever is named there, and that party then has to sort out responsibility with everyone else in the chain separately.

Carrier liability vs. broker liability

These are not the same thing, and conflating them is where most disputes start.

• The carrier that physically transports the freight generally carries liability for loss or damage while the goods are in its possession, subject to the terms of the bill of lading, the carrier's tariff, and any limitations of liability stated there.
• The broker that arranged the transportation typically does not take on cargo liability in the same way. A broker's job is to arrange and manage the move, not to physically handle the freight, and most broker-carrier agreements are written to keep that line clear.
• The shipper can carry exposure too, particularly around packaging, accurate weight and commodity declarations, and hazardous materials disclosure. Freight damaged because it was packaged or labeled incorrectly is a different claim than freight damaged in transit.

Where responsibility actually lands often comes down to what the contract and the BOL say, not what seems fair after the fact. This is one area where practice varies a lot by lane, mode, and the specific agreements in place, so it's worth reading the actual documents rather than assuming a standard answer applies.

Why cross-border shipments add a layer

Add a border crossing and the shipper-of-record question gets more complicated, because customs paperwork introduces its own version of the same concept. The importer of record, the exporter of record, and the shipper of record on the transport documents don't have to be the same entity, and in cross-border freight they frequently aren't. A claim involving a US-Mexico shipment can touch customs liability, carrier liability, and brokerage liability at the same time, each governed by different rules.

This is part of why vetting on the carrier side matters so much in cross-border work. Ellys checks carriers against live FMCSA data before dispatch and keeps monitoring them afterward, specifically because the carrier named on the BOL is the one holding operational liability for that leg of the move, and that status can change.

What actually protects a shipper

Clear, accurate paperwork is the first line of defense, since claims get resolved against what's documented, not what was intended. Knowing who is named as shipper of record on every load, understanding the limitation of liability language in the carrier agreement, and confirming insurance and bonding are in place before freight moves all reduce the odds of a dispute turning into a loss. Ellys is bonded under a BMC-84 surety bond and carries contingent cargo and liability coverage, which is the kind of baseline a shipper should be asking about from any broker it works with.

If you want to see how a specific lane is set up, including the carriers and documentation involved, start at /lanes.