Per-Unit Liability Limit vs. Aggregate And Per-Occurrence Caps

Per-Unit Liability Limit A liability cap calculated for each item, carton, pallet, or other defined unit of stored goods. That per-unit construct contrasts with other liability models such as aggregate limits (a single cap on all losses) and per-occurrence limits (a cap per incident).

Understanding the differences between these approaches matters for contract negotiation, insurance placement, and operational risk planning. Each model shifts risk between warehouse operators and customers in different ways, and they interact with deductibles, declared values, and indemnity language.

Key Differences

• Per-Unit Limit: Caps recovery by the defined unit — for example, $100 per carton or $600 per pallet — and multiplies by the number of affected units in a claim.
• Per-Occurrence Limit: Caps the insurer’s or operator’s liability per event, regardless of how many units were lost in that event (e.g., $10,000 per fire).
• Aggregate Limit: Sets a cap on total liability across the policy period or contract term (e.g., $100,000 annual limit), which can be exhausted by multiple claims.

How The Models Affect Claims Outcomes

Per-unit limits produce predictable per-item payouts but can dramatically undercompensate for high-value SKUs or mass-loss incidents. Per-occurrence limits protect against large single events but can be severely limiting if an occurrence destroys many units. Aggregate limits cap overall exposure but may leave merchants without recovery late in the policy year after prior claims consume the limit.

Example: A warehouse stores 200 cartons at $150 replacement each. A sprinkler failure destroys all cartons. With a $50 per-carton limit, recovery = 200 × $50 = $10,000. With a $20,000 per-occurrence limit, recovery = $20,000. With a $100,000 aggregate limit, recovery could be the full $30,000 replacement cost (200 × $150) if the aggregate is unused; otherwise limited by remaining aggregate.

When Each Model Is Preferable

• Per-Unit: Favored when inventory contains many low-value units, enabling lower premiums and simpler claims calculation.
• Per-Occurrence: Useful when the main concern is single large events (fire, flood) that could affect many units simultaneously.
• Aggregate: Appropriate for long-term contracts where total exposure over time — not single events — is the main concern.

Contract Language To Watch

Precise drafting determines how these caps operate. Merchants and warehousing operators should watch for terms that combine models (for example, a per-unit limit subject to an overall per-occurrence or aggregate cap) and for phrases like "per package," "per pallet," "per SKU," or "per claim." Clear definitions of what constitutes a "unit" and an "occurrence" prevent disputes.

• Label:Define Unit: Specify whether a unit is a single item, carton, case, pallet, or other packaging configuration.
• Label:Stacking Limits: Consider how mixed pallet builds are handled — is each SKU treated separately or is the pallet the unit?
• Label:Interaction Clauses: Note any clause that says per-unit payouts are subject to per-occurrence or aggregate ceilings.

Practical Negotiation Strategy

Assess mission-critical SKUs and volume. If you handle high-value pallets, negotiate declared-value per unit or a higher per-occurrence cap. If you handle many SKUs with low unit values, a per-unit cap might be cost-effective. Use loss-history data from your WMS or insurance carrier to justify changes in limits.

In short, the Per-Unit Liability Limit must be evaluated against per-occurrence and aggregate caps to understand total recoverable exposure. The right model — or combination of models — depends on SKU values, loss scenarios you most want protection against, and the commercial balance you need with your warehousing or insurance partners.