By Luis Lopez, AI transportation consultant, CEO of Go Hub.io Holdings Corp and subsidiaries, and host of the Freight Guru Podcast
Few notations on a bill of lading cause as much argument after a loss as “shipper’s load and count.” You will see it abbreviated as SLC or SL&C, usually stamped or typed near the description of goods. Carriers like it. Shippers and consignees often do not know what it means until a claim lands on their desk.
This article explains what shipper’s load and count means, what it does and does not protect, and what practical steps help everyone involved. It is general information, and the details of any dispute depend on facts and contract language, so involve a transportation attorney when real money is at stake.
What the notation says
The phrase is shorthand for “shipper’s weight, load and count.” It tells the reader that the shipper, not the carrier, loaded the freight and determined the quantity and weight. The carrier is saying, in effect, that it did not personally verify what went into the trailer or container.
The federal bills of lading law, 49 U.S.C. 80113, allows a carrier to note “shipper’s weight, load, and count” on a bill of lading when the shipper loaded the goods. When that statement is true, the carrier is not liable for damage caused by improper loading. The practical idea is simple: if you packed and loaded it, the carrier should not be blamed for problems that came from how you did it.
Where it helps the carrier
Consider damage that results from how the freight was loaded. Shifted pallets, poor blocking and bracing, uneven weight distribution, or product packed in a way that could not travel safely are loading issues. If the shipper loaded the trailer and the notation is accurate, the carrier has a basis to say those problems are not its responsibility.
It can also matter for quantity. If the shipper counted the pieces and sealed the unit and the carrier never opened it, the carrier did not verify the count.
Where it does not protect the carrier
The notation is not magic words that erase liability.
The notation must be true
The protection rests on the shipper actually having loaded the goods. If the carrier’s people loaded, helped load, or controlled the loading, stamping SLC on the paperwork does not change the facts.
It does not excuse the carrier’s own negligence
Even with the notation, a carrier remains responsible for what happens during transit that is its own fault. Poor driving, an accident, mishandling at a transfer point, or failing to protect the load are not loading issues. If damage came from something the carrier did, the notation is beside the point.
Apparent defects
Courts generally still hold the carrier responsible for loading defects that were apparent on ordinary observation. A driver who accepts a trailer with obviously unsecured freight and hauls it away cannot easily claim surprise later. If the problem would be visible on ordinary observation, the carrier may be expected to notice it and note it on the paperwork.
How this fits with the broader cargo liability rules
Interstate cargo claims against motor carriers generally fall under the Carmack Amendment, 49 U.S.C. 14706. That statute sets up the framework for carrier responsibility for loss and damage. The load and count notation is a piece of evidence and a defense that works inside that framework, not a replacement for it. For the bigger picture, see our explainer on the Carmack Amendment and cargo liability.
Why seals and records matter
When a unit is loaded by the shipper, sealed, and handed to the carrier, the seal tells a story. A sealed trailer with recorded seal numbers helps show who had control of the load and whether anyone opened it along the way. If the seal number on delivery matches the seal number on the paperwork, it supports the position that nobody tampered with the contents in transit. If the seals do not match, or were broken, the carrier will have more explaining to do.
Good records on both sides make disputes easier to resolve:
- Seal numbers written on the bill of lading and confirmed at pickup and delivery.
- Photos of the freight as loaded, the seal, and the condition at delivery.
- Notes on any visible problems at pickup, signed by the driver.
Practical advice by role
If you are a shipper
Load carefully and document it. Photograph the load, block and brace properly, and make sure the paperwork matches the trailer. If you load it, you own how it was loaded.
If you are a carrier or driver
Look at the load before you accept it. If you see something wrong, write it on the bill of lading, and record the seal number correctly. Do not rely on the notation to cover freight that looks poorly loaded.
If you are a consignee
Inspect at delivery, note exceptions on the receipt, and check the seal before it is cut. Our guide to freight damage at delivery and claims walks through that process.
If you carry the cargo risk
A shipper’s load and count defense can leave a gap that insurance has to fill. See cargo insurance vs carrier liability, and review how your bill of lading is completed, since the notation sits right in that document.
The bottom line
Shipper’s load and count is a real and useful notation, but it is narrow. It can protect a carrier from damage caused by the shipper’s loading, provided the shipper truly loaded the goods and the defect was not apparent. It does not cover the carrier’s own negligence, and it does not turn a blind eye into a defense. Accurate paperwork, recorded seal numbers and good photos do more to settle these disputes than any stamp. When a claim is large or the facts are contested, get advice from a transportation attorney before you decide who is responsible.
For more on freight and technology, subscribe to the Freight Guru Podcast.
About the author: Luis Lopez is a Miami-based AI transportation consultant and logistics entrepreneur, the CEO of Go Hub.io Holdings Corp and subsidiaries, and host of the Freight Guru Podcast.
This article is general information for the freight community, not legal advice. Talk to a transportation attorney about your specific situation.
