Coverage Explained

Warehouse Receipts: What Your Liability Limit Actually Does

A long aisle between tall pallet racking stacked on both sides with shrink-wrapped pallets

This post explains what contract terms commonly do in a warehousing operation. It is general information, not legal advice, and it is not an opinion about your agreement. What your specific warehouse receipt or storage contract means — and whether a given clause is enforceable in your situation — is a question for your own counsel.

There is a sentence owners say with real confidence, usually right after they hear that general liability will not pay for a customer’s goods, and it goes like this: “It is fine — my warehouse receipt limits what I owe.”

That sentence is not wrong. It is just doing far less work than the person saying it believes.

A limitation-of-liability clause is a genuine and valuable layer. It is also the most over-trusted document in a warehouse office, and the reason is simple: it is quietly answering a different question than the one the owner thinks they asked.

The document itself, and when it attaches

Start with what a warehouse receipt actually is, because plenty of operators have issued thousands of them and never read one closely.

A warehouse receipt is the document you issue when you take custody of a customer’s goods. It does three things at once, and only the first is obvious.

It identifies the goods and records that you have them — the acknowledgment that the freight came off the truck, crossed your dock, and is now sitting in your building under your control.

It functions as a document of title, which is a larger idea than it sounds. The receipt is not just a note between you and your customer; it can matter to parties who never set foot in your building — a lender financing the inventory, a buyer taking the goods on paper, a party with a claim to the freight itself. Warehouse receipts operate inside the commercial-code framework that governs documents of title and the duties of a warehouse holding goods as a bailee. We reference that framework by function rather than reciting provisions at you, because the specifics belong with your counsel and with the wording of your own forms.

And it carries the terms on which you are holding the goods — which is the part that gets skimmed, and the part this post is about.

The receipt is also the practical marker for when the goods became your responsibility. The bailment does not begin with a handshake and it does not begin when the truck pulls into the yard; it begins when you accept custody, and the receipt is normally the record of that moment. That matters more than it seems, because the exposure it opens is the one your bailee coverage is sized against.

Declared value and released value: the bargain inside the clause

Inside the terms is a trade, and it is a fair one once you see it from both sides.

A warehouse cannot price the risk of contents it did not buy, did not choose, and often cannot inspect. The same pallet footprint can hold packaging foam or medical devices. So the default in most storage terms is a released value — the goods are treated, for purposes of what you owe on a loss, as carrying a limited value. That limit is the cap your terms rely on, and it is the reason a storage rate can be quoted at all without an appraisal of every skid in the building.

The customer’s way out of that default is declared value: they tell you the goods are worth more, and they pay for the larger exposure you are agreeing to carry.

Those are concepts, not numbers, and we are not going to hand you a figure. The actual caps and the mechanics of declaring live in your contracts and your rate structure — not in a rule of thumb, and not in a blog post. What you should take from the concept is the direction it points: a declared value is not a formality. It is a customer telling you the exposure just went up, and it is information your insurance carrier expects you to have passed along.

Caution one: a contractual limit is not insurance

Here is the first of the two things that catch people, and it is the more important one.

A limitation clause reduces what you owe. It pays nothing.

Read that again slowly, because the whole confusion lives in the gap between those two verbs. If a customer’s inventory is destroyed and your terms cap your exposure, you have not been paid. You have been invoiced less. The remaining amount is still a real obligation to a real customer who is standing in your building with an empty rack aisle, and it comes from one of exactly two places: a policy, or your own bank account.

That is the entire relationship between the two layers, and it is worth being blunt about it:

  • The contract sizes the loss.
  • The coverage funds it.

Warehouse legal liability is the line written to answer for the goods in your care — the freight that is not yours but is your responsibility while it sits under your roof. It exists because general liability carves those goods out under its care, custody, or control exclusion, which is a story we told in full in an earlier post. The contract layer sits on top of that structure. It never replaces it.

An owner who treats a limitation clause as a substitute for bailee coverage has made a category error: they have confused a smaller bill with a paid one.

The contract sizes the loss; the coverage funds it — two layers, two different jobs A side-by-side comparison. A loss to a customer’s goods sits at the top. Beneath it, two columns: on the left, the contract layer — the warehouse receipt and storage terms — which can limit the amount you owe, and only where the customer actually agreed to the limit; on the right, the coverage layer — warehouse legal liability — which can fund what you still owe, within the terms of the policy. An emphasized band across the middle states that a limit reduces the bill and never writes the check. A closing line notes that the two layers are read together, because the place they disagree is where a claim gets argued. No numbers, form numbers, or clause citations appear anywhere in the diagram.
<rect x="205" y="20" width="290" height="52" rx="9" fill="#ffffff" stroke="#C3DEDE"/>
<text x="350" y="42" text-anchor="middle" font-family="Inter, sans-serif" font-size="14" font-weight="600" fill="#0F4C5C">A loss to a customer’s goods</text>
<text x="350" y="62" text-anchor="middle" font-family="Inter, sans-serif" font-size="12" fill="#3F5B64">Fire · water · theft · handling damage</text>

<path d="M300 72 L215 104" stroke="#0F4C5C" stroke-width="2" fill="none" marker-end="url(#wr-arrow)"/>
<path d="M400 72 L485 104" stroke="#0F4C5C" stroke-width="2" fill="none" marker-end="url(#wr-arrow)"/>

<rect x="26" y="110" width="300" height="130" rx="10" fill="#ffffff" stroke="#C3DEDE"/>
<text x="176" y="136" text-anchor="middle" font-family="Inter, sans-serif" font-size="14" font-weight="600" fill="#0F4C5C">The contract layer</text>
<text x="176" y="160" text-anchor="middle" font-family="Inter, sans-serif" font-size="12" fill="#3F5B64">Your warehouse receipt and</text>
<text x="176" y="178" text-anchor="middle" font-family="Inter, sans-serif" font-size="12" fill="#3F5B64">storage terms</text>
<text x="176" y="204" text-anchor="middle" font-family="Inter, sans-serif" font-size="13" font-weight="600" fill="#0F4C5C">Can limit what you owe —</text>
<text x="176" y="222" text-anchor="middle" font-family="Inter, sans-serif" font-size="13" font-weight="600" fill="#0F4C5C">if the customer agreed to it.</text>

<rect x="374" y="110" width="300" height="130" rx="10" fill="#ffffff" stroke="#C3DEDE"/>
<text x="524" y="136" text-anchor="middle" font-family="Inter, sans-serif" font-size="14" font-weight="600" fill="#0F4C5C">The coverage layer</text>
<text x="524" y="160" text-anchor="middle" font-family="Inter, sans-serif" font-size="12" fill="#3F5B64">Warehouse legal liability —</text>
<text x="524" y="178" text-anchor="middle" font-family="Inter, sans-serif" font-size="12" fill="#3F5B64">the bailee line</text>
<text x="524" y="204" text-anchor="middle" font-family="Inter, sans-serif" font-size="13" font-weight="600" fill="#0F4C5C">Can fund what you still owe —</text>
<text x="524" y="222" text-anchor="middle" font-family="Inter, sans-serif" font-size="13" font-weight="600" fill="#0F4C5C">within the terms of the policy.</text>

<path d="M176 240 L176 272" stroke="#0F4C5C" stroke-width="2" fill="none" marker-end="url(#wr-arrow)"/>
<path d="M524 240 L524 272" stroke="#0F4C5C" stroke-width="2" fill="none" marker-end="url(#wr-arrow)"/>

<rect x="40" y="278" width="620" height="72" rx="10" fill="#C8935A" stroke="#0F4C5C"/>
<text x="350" y="306" text-anchor="middle" font-family="Inter, sans-serif" font-size="15" font-weight="600" fill="#1A1A1A">A limit reduces the bill. It never writes the check.</text>
<text x="350" y="332" text-anchor="middle" font-family="Inter, sans-serif" font-size="13" font-weight="600" fill="#1A1A1A">The contract sizes the loss; the coverage funds it.</text>

<text x="350" y="382" text-anchor="middle" font-family="Inter, sans-serif" font-size="13" fill="#3F5B64">Read them together, before a loss —</text>
<text x="350" y="402" text-anchor="middle" font-family="Inter, sans-serif" font-size="13" fill="#3F5B64">because the place they disagree is where a claim gets argued.</text>
Two layers, two different jobs. Your storage terms can limit what you owe; your bailee coverage is what actually funds the amount that remains.

Caution two: the clause is only as good as the agreement you actually signed

The second thing that catches people is subtler, and it is the one that tends to be invisible right up until it is expensive.

Owners talk about “our terms” as if there is one set of them, printed once, applied to everybody. In a real warehouse there are as many sets of terms as there are customers who had a legal team.

Three versions of that, and every operator will recognize at least one:

  • The customer who negotiated the limitation away. A large national account with leverage says the cap is unacceptable, their legal department strikes it, and someone in your business signs — because the account is worth having and the change looked like a paperwork concession. It was not. It was the removal of the ceiling on what that customer can recover from you.
  • The contract that assumes coverage you do not carry. A storage or distribution agreement commits you to a standard of care, an indemnity, or an insurance requirement that reads broader than what your policy actually does. Nobody underwrites a contract before it is signed. The mismatch does not surface at signing; it surfaces at the claim.
  • The terms nobody can find. The receipt language has not been reviewed in years, the storage agreement for your third-largest account is in an email attachment from a departed employee, and the version you are relying on may not be the version in force.

None of that is exotic. It is Tuesday in a growing warehouse. And all three have the same effect: the protection you believe is sitting behind you is not the protection you actually signed.

Where the contract and the policy disagree — and why that is always a claim

This is the part neither the contract nor the policy will tell you about, because neither one knows the other exists.

Your storage terms were written to manage what you owe a customer. Your policy was written to answer for a defined set of losses on defined terms. They were drafted by different people, at different times, for different purposes, and nobody sat them down at the same table. So they can drift apart in either direction, and both directions cost you.

When the contract promises more than the policy answers, you are self-insuring the difference without knowing it. The agreement says one thing to your customer; the policy says another to you; the gap is yours.

When the policy is sized for a limit the contract no longer has, you are underinsured on the exact account you most wanted to win. The limitation you priced the coverage around was negotiated out two years ago, and the file still assumes it.

And there is a third, quieter version worth naming, because it is where this post meets the fault question: the standard your policy is written to may not be the standard your contract implies. A storage agreement can leave a customer with the impression that their goods are protected against loss, full stop — while the coverage behind it may answer only for loss you are legally liable for. That distinction between a legal-liability form and a broader all-risk bailee form is a decision, not a detail, and the warehouse legal liability page walks it properly. The point here is narrower and it is about paper: what you promised and what you bought have to be read as one document.

What to actually do about it

Not much, and it does not take long. That is the good news buried in all of this.

Put the two stacks on the same desk. The warehouse receipts and storage agreements in one pile, the policy in the other. They should be read against each other before anything binds, and again whenever a major customer contract changes. That is a working session, not a project.

Ask your counsel the legal questions. What your terms mean, whether a limitation holds up in your circumstances, how to revise an agreement — those are theirs, and this post is not a substitute for that conversation.

Ask your broker the insurance question. Given the agreements you have actually signed — including the one where the cap was struck — does the coverage stand behind them? That is ours.

And tell somebody when a contract changes. The single most common way this goes wrong is not a bad clause. It is a good clause that a customer removed, in an agreement nobody circulated, on an account that has since become your largest.

The short version

Your warehouse receipt is doing real work. It is recording custody, it is functioning as a document of title, and it is carrying the terms that size what you owe when something goes wrong. Keep it, read it, and take it seriously.

Just do not ask it to be an insurance policy, because it will not be one. A limit reduces the bill; it never writes the check. The check comes from warehouse legal liability, the bailee line that the whole warehouse insurance program is built around — and it should be sized against the agreements you actually signed, not the ones you remember signing.

If you are not certain those two things match, that is worth an afternoon. Send us the contracts and the policy, and we will read them side by side.

The bottom line

A warehouse receipt is the document that records custody of a customer’s goods and carries the terms you hold them on — and those terms commonly include limitation-of-liability or released-value language that caps what you owe for a loss unless the customer declares a higher value and pays for it. That layer is real and it matters. But two things about it are misunderstood often enough to be dangerous. First, a contractual limit is not insurance: it may reduce the amount you owe, and it pays nothing at all toward what you still owe — the check comes from a policy or it comes from you. Second, a limitation is only as good as the agreement you actually signed; a customer who negotiated it away, or a storage contract that quietly assumes you carry broader cover than you do, changes the exposure entirely. Warehouse receipts operate inside the commercial-code framework that governs documents of title, and the specifics of your own terms are a question for your counsel. What we can say plainly is that your contract layer and your coverage layer are one decision, read together — because the moment they disagree, that disagreement is a claim.

Frequently asked questions

Does a limitation-of-liability clause in my warehouse receipt mean I do not need bailee coverage?

No, and this is the most consequential misreading of the contract layer there is. A limitation clause and an insurance policy do two different jobs. The clause may cap the amount a customer can recover from you for a loss to their goods. It does not put a single dollar toward that capped amount — it reduces the size of the bill, it does not pay the bill. If a customer’s freight is destroyed in your building and your terms limit what you owe, you still owe what remains, and it comes out of a policy or it comes out of your business. Warehouse legal liability is the line written to answer for the goods in your care. The contract limits the exposure; the coverage funds it. You want both, and they are read together, not traded against each other.

What is a warehouse receipt, exactly?

It is the document a warehouse issues when it takes custody of a customer’s goods. It identifies the goods, records that you have them, and — this is the part owners skim — carries the terms on which you are holding them. Those terms typically include the limitation-of-liability or released-value language, the customer’s option to declare a higher value, storage and handling provisions, and what happens if goods are not collected. It functions as a document of title, which means it can matter to parties beyond you and your customer, including a lender who is financing the goods. Warehouse receipts sit inside the commercial-code framework that governs documents of title; the exact provisions and how they apply to your operation are a question for your own counsel.

What is the difference between declared value and released value?

They are two sides of one bargain. Released value is the default: unless the customer says otherwise, the goods are treated as having a limited value for purposes of what you owe if they are lost or damaged, which is the basis for the cap in your terms. Declared value is the opt-out: the customer states a higher value for the goods and pays more for the higher exposure you are taking on. The reason the bargain exists is that a warehouse cannot price the risk of contents it did not buy and cannot inspect. The reason it matters to your insurance is that a customer who declares a higher value has raised the exposure your policy is standing behind, and your insurance carrier expects that to be reflected in what you told them.

My customer struck the limitation clause out of our storage agreement. What now?

Then you are holding that customer’s goods without the cap you assumed you had, and the exposure your policy is being asked to answer just got larger. This is not unusual — a large national customer with negotiating leverage will often insist on it, and the change is made by a legal team long before it reaches the operations side of your business. What matters is that somebody tells your broker. A limitation you no longer have is not a paperwork detail; it changes the size of the loss that can land on you for that account. Whether the terms of a specific agreement are enforceable, and what your options are, is a question for your own counsel. Whether your coverage is sized for the agreement you actually signed is a question for us, and we would rather answer it now.

Can my storage contract promise a customer more protection than my policy provides?

It can, and that mismatch is one of the quietest exposures in this class. A storage or distribution agreement can commit you to a standard of protection, an indemnity, or an insurance requirement that reads broader than the policy sitting in your file. Nothing prevents an owner from signing it — contracts are not underwritten by an insurance carrier before a signature goes on them. The gap does not announce itself; it surfaces at a claim, when the customer points at what you promised and the policy answers only for what it covers. The fix is unglamorous and it works: read the insurance requirements in a customer contract against the coverage you actually have, before it is signed rather than after.

Do I need a lawyer for this, or a broker?

Both, and for different questions. What your specific terms mean, whether a limitation is enforceable in your situation, and how to draft or revise a storage agreement are legal questions and belong with your own counsel — this post explains what a clause does in general, and is not legal advice about your contract. What your policy answers for, whether the coverage is written to the standard your contracts assume, and how to size a limit against the goods you are actually holding are insurance questions, and that is our side of the table. The best version of this is the two working from the same set of documents, because a contract and a policy that were never read against each other are a claim waiting for a date.

About the author

Nate Jones, CPCU

Nate Jones, CPCU, is the founder of Wexford Insurance and Warehouse Guard Insurance, a specialty insurance agency placing warehousing, distribution, and wholesaling coverage in 48 states through a 25-market specialty panel. He places the bailee line for operations that store other companies’ freight, and on a submission the document he asks for before the loss runs is the warehouse receipt — because the limitation-of-liability language a customer actually agreed to, and the language a customer negotiated away, size the exposure the policy is being asked to stand behind. Reach him via the Warehouse Guard Insurance quote form or call 317-942-0549.

Let a CPCU-led agency read your program

Tell us what you store or sell and who owns it — the customers’ goods in your care, or your own inventory on the move — and we will market it to the markets that write this class.