Nobody in warehousing buys an umbrella because they woke up wanting more limit.
They buy it because an agreement landed on the desk with an insurance-requirements exhibit stapled to the back of it, and somebody has to sign that agreement by Friday. This is the coverage that is bought almost entirely by contract demand — which makes it worth understanding what the contracts are actually demanding, because it is usually two things at once, and they are frequently confused with each other.
The three contracts that ask for things
Three agreements show up in nearly every warehousing or distribution business, and each one arrives with requirements.
The lease. The building owner wants a tenant that carries real liability limits, and they want to be an additional insured on the tenant’s policy for the premises. This is not unusual and it is not adversarial; a landlord who has leased a large industrial building to a business running powered trucks and dense storage is managing an obvious exposure of their own.
The 3PL or distribution agreement. The contract that defines the actual work — storing, handling, and shipping a customer’s freight — routinely sets its own liability-limit requirements, and asks that the customer be added as an additional insured for the work you do on their behalf. For a bailee operation this is the agreement that matters most, because the customer whose goods sit on your racking has the most direct stake in what your program looks like.
The national customer. A large retailer or a national account applies one insurance standard across every supplier and every logistics partner it uses, and it does not adjust that standard for a small vendor. The requirement is a threshold, not an opening offer. You either meet it and get onboarded, or you do not.
Read those three side by side and the same two requests appear over and over: limits you may not currently reach, and status for a party who is not currently on your policy. They are separate problems and they have separate answers.
Request one: height. That is what the umbrella is.
When a contract demands a total liability limit above what your primary policies carry, it is not asking you to insure anything new. It is asking you to be able to reach further on what you already insure.
That is precisely, and only, what an umbrella does. It sits above the underlying liability policies — typically your general liability, your commercial auto, and the employers liability inside your workers compensation — and adds limit above them, responding after an underlying limit is used up on a covered claim. More of the coverage you have, not different coverage.
Which is why the most common misreading of a contract demand leads owners in the wrong direction. A requirement for a high total limit is a height problem. It is not solved by rewriting the general liability, and it is certainly not solved by adding coverages the contract never asked about. The umbrella page walks through how the layer sits over the lines beneath it; the point here is narrower: when a certificate comes back short, the shortfall is nearly always height, and this is the layer that supplies it.
Request two: status. That is the additional-insured question.
The second request is a different animal entirely, and confusing it with the first is how businesses end up with the right limit and the wrong policy.
Adding someone as an additional insured means extending your liability coverage so that they are also an insured under your policy — typically for liability arising out of your operations, or out of the premises you lease from them. It is a change in who the policy protects, and it happens through an endorsement to the policy itself. Your insurer has to grant it, on terms the insurer has written.
There are two ways it commonly attaches, and the difference is entirely practical:
- Scheduled. The parties added are named on the policy, one at a time. Every new customer or landlord means a new request to your insurance carrier and a new endorsement.
- Blanket. The policy extends additional-insured status to a party you have agreed in a written contract to add, without each one being individually named.
For a bailee warehouse signing a handful of long-term accounts, scheduled status may be perfectly workable. For a distributor onboarding customers continuously, or a 3PL adding accounts through a peak season, the blanket approach is usually the only one that keeps up with the business. Which one your policy operates on is not something to infer from the coverage type — it is set by the endorsements actually attached to your policy, and reading them against the contracts you are about to sign is the whole discipline.
Your general liability is where this normally lives, since it is the policy the lease and the customer contract are almost always pointing at.
<text x="110" y="34" text-anchor="middle" font-family="Inter, sans-serif" font-size="14" font-weight="600" fill="#0F4C5C">What demands it</text>
<rect x="20" y="50" width="180" height="52" rx="9" fill="#ffffff" stroke="#C3DEDE"/>
<text x="110" y="72" text-anchor="middle" font-family="Inter, sans-serif" font-size="13" font-weight="600" fill="#0F4C5C">The lease</text>
<text x="110" y="91" text-anchor="middle" font-family="Inter, sans-serif" font-size="12" fill="#3F5B64">The landlord</text>
<rect x="20" y="116" width="180" height="52" rx="9" fill="#ffffff" stroke="#C3DEDE"/>
<text x="110" y="138" text-anchor="middle" font-family="Inter, sans-serif" font-size="13" font-weight="600" fill="#0F4C5C">The storage agreement</text>
<text x="110" y="157" text-anchor="middle" font-family="Inter, sans-serif" font-size="12" fill="#3F5B64">The customer</text>
<rect x="20" y="182" width="180" height="52" rx="9" fill="#ffffff" stroke="#C3DEDE"/>
<text x="110" y="204" text-anchor="middle" font-family="Inter, sans-serif" font-size="13" font-weight="600" fill="#0F4C5C">The national account</text>
<text x="110" y="223" text-anchor="middle" font-family="Inter, sans-serif" font-size="12" fill="#3F5B64">The onboarding threshold</text>
<path d="M200 142 L246 142" stroke="#0F4C5C" stroke-width="2" fill="none" marker-end="url(#coi-arrow)"/>
<text x="360" y="34" text-anchor="middle" font-family="Inter, sans-serif" font-size="14" font-weight="600" fill="#0F4C5C">What actually answers it</text>
<rect x="250" y="50" width="220" height="88" rx="9" fill="#ffffff" stroke="#C3DEDE"/>
<text x="360" y="74" text-anchor="middle" font-family="Inter, sans-serif" font-size="13" font-weight="600" fill="#0F4C5C">More total limit</text>
<text x="360" y="97" text-anchor="middle" font-family="Inter, sans-serif" font-size="12" fill="#3F5B64">The umbrella adds height</text>
<text x="360" y="115" text-anchor="middle" font-family="Inter, sans-serif" font-size="12" fill="#3F5B64">above the primary policies.</text>
<rect x="250" y="150" width="220" height="118" rx="9" fill="#ffffff" stroke="#C3DEDE"/>
<text x="360" y="176" text-anchor="middle" font-family="Inter, sans-serif" font-size="13" font-weight="600" fill="#0F4C5C">Additional-insured status</text>
<text x="360" y="199" text-anchor="middle" font-family="Inter, sans-serif" font-size="12" fill="#3F5B64">An endorsement to the policy.</text>
<text x="360" y="222" text-anchor="middle" font-family="Inter, sans-serif" font-size="12" fill="#3F5B64">Blanket, where a written</text>
<text x="360" y="240" text-anchor="middle" font-family="Inter, sans-serif" font-size="12" fill="#3F5B64">contract requires it — or</text>
<text x="360" y="258" text-anchor="middle" font-family="Inter, sans-serif" font-size="12" fill="#3F5B64">scheduled, named parties only.</text>
<path d="M470 94 L516 130" stroke="#0F4C5C" stroke-width="2" fill="none" marker-end="url(#coi-arrow)"/>
<path d="M470 208 L516 172" stroke="#0F4C5C" stroke-width="2" fill="none" marker-end="url(#coi-arrow)"/>
<rect x="520" y="122" width="160" height="90" rx="9" fill="#ffffff" stroke="#C3DEDE"/>
<text x="600" y="152" text-anchor="middle" font-family="Inter, sans-serif" font-size="13" font-weight="600" fill="#0F4C5C">The policy</text>
<text x="600" y="175" text-anchor="middle" font-family="Inter, sans-serif" font-size="12" fill="#3F5B64">This is the part</text>
<text x="600" y="193" text-anchor="middle" font-family="Inter, sans-serif" font-size="12" fill="#3F5B64">that answers a claim.</text>
<path d="M600 212 L600 264" stroke="#0F4C5C" stroke-width="2" fill="none" marker-end="url(#coi-arrow)"/>
<rect x="40" y="288" width="620" height="112" rx="10" fill="#C8935A" stroke="#0F4C5C"/>
<text x="350" y="320" text-anchor="middle" font-family="Inter, sans-serif" font-size="15" font-weight="600" fill="#1A1A1A">The certificate of insurance reports what the policy says</text>
<text x="350" y="348" text-anchor="middle" font-family="Inter, sans-serif" font-size="13" fill="#1A1A1A">It is evidence that coverage exists. It is not coverage,</text>
<text x="350" y="368" text-anchor="middle" font-family="Inter, sans-serif" font-size="13" font-weight="600" fill="#1A1A1A">and it does not amend the policy it describes.</text>
<text x="350" y="390" text-anchor="middle" font-family="Inter, sans-serif" font-size="13" fill="#1A1A1A">If the two disagree, the policy governs.</text>
<text x="350" y="424" text-anchor="middle" font-family="Inter, sans-serif" font-size="13" fill="#3F5B64">Fix the policy first. The certificate can only ever describe it.</text>
The certificate is evidence. It is not coverage.
Here is the sentence to take away from this post, because it is the one that costs businesses the most when it is misunderstood.
A certificate of insurance is evidence that coverage exists. It is not coverage, and it does not amend the policy.
A certificate is an informational summary, issued to somebody who is not a party to the policy, describing what the policy is understood to say. That is all it is. It confers nothing. It grants nothing. It cannot add a party to a policy that has not been endorsed to include them, it cannot raise a limit that is not there, and it cannot make a contract requirement come true by stating that it is.
Which produces the failure that is worth naming plainly. A certificate reports that a landlord or a customer holds additional-insured status. No endorsement on the policy actually provides it. Everyone files the certificate and moves on. Nothing is wrong for two years — and then there is a loss, the other party tenders the claim under your policy, and the policy is read. The policy governs. The certificate was never anything more than a description, and it turns out to have been describing something that was not there.
The lesson runs one direction only: fix the policy first. A certificate that accurately reports a program that genuinely meets the contract is a fine and useful document. A certificate produced to satisfy a requirement the underlying policy does not actually meet is not a shortcut — it is a problem with a delay built into it.
The other two phrases in the exhibit
Once you start reading insurance-requirements exhibits closely, two more phrases turn up beside the limit and the additional-insured demand. Both are worth knowing by function.
Primary and non-contributory. The party you have added wants your policy to respond first for a claim connected to you, without your insurer seeking a contribution from that party’s own insurance. In plain terms: they do not want their program pulled into a loss that belongs to yours.
Waiver of subrogation. The party wants your insurer to give up its right to pursue them after paying a claim connected to them. Ordinarily, an insurer that pays a loss can step into your shoes and go after whoever was responsible; a waiver gives that right up in advance, in favor of the party named.
Neither of these is exotic and neither is unreasonable. But both are changes to your policy, both require your insurance carrier to agree, and both depend on endorsements actually granting them. Signing a contract that demands them without confirming your program delivers them is making a promise on your policy’s behalf that your policy has not made — and that is a promise nobody discovers is empty until it is being relied on.
How to read a requirements exhibit before you sign it
The order matters, and it is not the order most businesses use.
- First, read what the contract asks for — the total limits, the additional-insured status, and any primary-and-non-contributory or waiver language.
- Then read what your policies actually do — the limits in place with the umbrella stacked on top, and the endorsements attached, not the coverages assumed.
- Close the difference on the policy, with your insurance carrier, in writing.
- Only then issue the certificate, which will now be describing something that is true.
Most businesses run that list backwards: the certificate request arrives, somebody produces a certificate, and nobody looks at the policy at all. That works right up until it is tested, and it is tested exactly once.
The short version
Your contracts want two things: enough total limit, and a seat on your policy for the party you are doing business with. The umbrella supplies the first. An endorsement supplies the second, on a blanket basis or a scheduled one depending on what is attached to your policy. Neither of them is supplied by a certificate — the certificate merely reports on what the policy already did or did not do.
When an insurance-requirements exhibit lands on your desk and you are not certain whether your program meets it, that is the moment to find out, and it takes one conversation. The warehouse insurance program is built to sit under those contracts rather than trail behind them. Send us the exhibit and the policies together and we will read them side by side — before the signature, not after the loss.