Product Liability vs Completed Operations (within GL) for Warehouses

When do Warehouses need Product Liability vs Completed Operations (within GL)?

For Warehouses, the question of whether to carry Product Liability or Completed Operations (within GL) (or both) maps to operational exposure. Operations with exposure on both sides of the boundary need both coverages; operations clearly on one side may only need one.

In practice, most Warehouses carry both coverages because the operational profile spans both. The premium for both lines is often less than the financial exposure on either side — buying both is the conservative answer for most operators.

Where Product Liability and Completed Operations (within GL) overlap and where they don't

Product Liability and Completed Operations (within GL) have minimal coverage overlap by design — carriers structure the lines to handle distinct exposures. The gap between them is the area neither covers: typically the boundary scenarios where a claim has elements of both but the specific facts trigger neither policy's response.

For Warehouses, the gap is mostly theoretical for well-structured policy stacks. Properly drafted policies on both lines cover the realistic exposure space without significant gaps. Where gaps do emerge, they usually arise from policy-form choices or specific exclusion language.

Real-world claim allocation between Product Liability and Completed Operations (within GL)

Most Warehouses claims clearly belong to one policy or the other. The exceptions — claims that genuinely span both — are usually handled through carrier-to-carrier coordination rather than the warehouse having to choose.

The key is reporting promptly to both carriers when a claim might involve either policy. Late reporting to one carrier can produce coverage issues; reporting to both preserves both policies' ability to respond if facts develop.

Coordinating limits between Product Liability and Completed Operations (within GL) on Warehouses

For Warehouses carrying both Product Liability and Completed Operations (within GL), limit coordination matters. Both policies should have limits sized to the realistic exposure on their respective sides, with umbrella coverage stacking above both for catastrophic-scenario protection.

Common mistake: sizing limits based on contract minimums alone rather than realistic loss exposure. Contract minimums are floors; the realistic limit should reflect actual claim potential, which often exceeds the contract minimum.

Is there ever a case to skip Product Liability or Completed Operations (within GL)?

The case for buying only one of Product Liability or Completed Operations (within GL) on Warehouses is narrow. It generally requires the warehouse to demonstrate that the operational exposure is genuinely one-sided — either no operational exposure (where Completed Operations (within GL) would cover everything that matters) or no advisory/financial exposure (where Product Liability would cover everything that matters).

This determination should be made with a broker who can review the operations and contractual obligations. Self-assessment often misses subtle exposures that warrant both coverages.

How Warehouses efficiently buy both coverages together

For Warehouses carrying both Product Liability and Completed Operations (within GL), placing both with the same carrier typically captures 5-12% multi-line credit and simplifies renewal. The premium savings often exceed the modest convenience of separate placements.

The exception: when specialty knowledge in one line favors a different carrier. If one carrier writes the best Product Liability for retail or hospitality but another writes the best Completed Operations (within GL), splitting may produce better total coverage even without the multi-line credit. Most Warehouses, however, find one carrier that writes both lines competitively.

How Warehouses should evaluate the Product Liability-Completed Operations (within GL) stack

Warehouses that perform annual reviews of the Product Liability/Completed Operations (within GL) stack typically maintain better-aligned coverage than Warehouses that set up policies once and never revisit. Operations evolve; contracts change; coverage needs shift. The annual review keeps the coverage current with the operation.

The questions to ask: do we still need both coverages at current limits? Are there new exposures that require endorsements? Have we taken on contracts requiring different limits or AI structures? Catching these at the annual review prevents problems at claim time.