General liability does not carry one single limit. It carries several, and for a machine shop or manufacturer the one that matters most is the one most owners have never looked at: the products-completed operations aggregate. It is a separate bucket from the limit that handles the slip-and-falls and on-site mishaps, it is the cap that serious products claims actually erode, and because making or machining a product is the defining exposure of this class, it is the number worth watching above all the others. This post explains what the aggregate is, why it sits apart from the general aggregate, and how an umbrella relates to it when a products claim threatens to exhaust it.
The short version: the products-completed operations aggregate is a separate limit bucket inside your general liability policy, distinct from the general aggregate. It caps what the policy pays across the term for products-liability claims — the harm a product you made causes after it leaves your control — and when that bucket is at risk, an umbrella sits above the primary policy to add limit over it.
Two buckets, not one
A standard general liability policy carries more than a single ceiling. Underneath the per-occurrence limit that caps any one claim, there are separate annual aggregates that cap total payouts for the policy term — and the two that matter here are the general aggregate and the products-completed operations aggregate.
The general aggregate is the cap for premises and operations claims: the visitor hurt at your facility, the forklift that backs into a customer’s trailer at the dock, the everyday third-party exposure of running a place where outsiders come and go. The products-completed operations aggregate is the cap for the products side: the harm a part or product you made causes once it is out in the field, after it has left your control. They are two separate buckets, and they are eroded by different claims. A year of on-site incidents draws against the general aggregate; a serious products claim draws against the products one. Because they are separate, draining one does not automatically drain the other — which is exactly why knowing which bucket a claim hits matters.
Why the products bucket is the one to watch
Most businesses rarely touch their products-completed operations aggregate. A machine shop or manufacturer can, and that single fact is why this number deserves an owner’s attention more than any other limit on the policy.
The reason is the exposure. The defining risk of this class is a product that fails downstream — a part that lets go in a customer’s machine, a component that fails in the field, a finished good that injures an end user far down the chain — and every one of those claims draws against the products bucket, not the general one. A serious products claim, or several in a single term, erodes that specific aggregate. And once it is exhausted, the policy stops paying products-completed operations claims for the rest of the year, even if the general aggregate sits entirely untouched. The premises limit being full does you no good when the bill is a products claim. That is the asymmetry a manufacturer has to plan around: the bucket most likely to be tested is the one specific to the products you ship.
It also ties back to how the policy is triggered. Because a product can surface a claim long after it ships, which policy year answers depends on the occurrence-versus-claims-made trigger — and the trigger decides which year’s products aggregate a late claim draws against. The two ideas work together: the trigger picks the year, and the products aggregate sets how much is left in that year to pay.
Where the umbrella comes in
When a manufacturer’s products exposure is large enough that a single serious claim could approach or exhaust the primary products aggregate, that is where an umbrella earns its place. An umbrella, or excess liability, sits above the primary general liability policy and adds limit over its aggregates — including the products-completed operations aggregate. It does not replace the products bucket; it extends the height of coverage over it, so a claim that would have blown through the primary limit has somewhere to go.
Real-World Scenario: A manufacturer has a strong year of on-site safety and an unremarkable general aggregate — and then one shipped product fails downstream and causes a serious third-party injury. The claim does not touch the general aggregate at all; it draws entirely against the products-completed operations aggregate. If that bucket is thin, the primary policy pays up to its products cap and stops, even though the general aggregate is fully intact. An umbrella sitting above the primary policy is what answers above that products cap. Same operation, and the only limit that mattered was the products one.
For a manufacturer with real products exposure, the umbrella is often there specifically because the products bucket is the one most likely to be tested — and reading the products aggregate, the umbrella above it, and how the three products coverages fit together is part of structuring the program to the exposure rather than to a generic limit. The umbrella coverage page goes deeper on how excess limit stacks above the primary layer.
Reading the products aggregate on your policy
Because the products-completed operations aggregate is the limit that matters most for this class, it is worth knowing where to find it and what can quietly undercut it. The aggregate is shown on the declarations page, listed separately from the general aggregate — and seeing the two as distinct numbers is the first thing to confirm, because an owner who assumes a single shared limit is reading the policy wrong. The second thing to check is whether the products-completed operations hazard is even present: some policies carve it out entirely with an exclusion endorsement, which would strip away the exposure this aggregate is meant to cap and leave the number on the page meaningless. The third is the relationship between the products aggregate and the per-occurrence limit, since a single large products claim is capped first by the per-occurrence limit and then counts against the aggregate for the rest of the term.
None of those three reads is complicated, but they are easy to skip, and a manufacturer who skips them can carry a products aggregate that is thinner than the exposure, carved out without realizing it, or assumed to be shared with the general aggregate when it is not. Reading the declarations against the products you actually ship — before a loss, not during one — is how the number on the page turns into coverage you can count on rather than a figure nobody checked until it was tested.
Why it matters for your operation
If you make or machine a product, the products-completed operations aggregate is the limit your program should be built around — not the general aggregate, and not a single shared number an owner assumes covers everything. It is the bucket your defining exposure actually erodes, it can be exhausted in a bad year while the rest of the policy sits untouched, and it is the limit an umbrella is most often there to extend. We read this number against the products you actually ship, check whether an umbrella sits above it at the right height, and confirm the hazard the aggregate is meant to cap has not been quietly carved out. When you are ready, start a quote and tell us what you make or machine, or read the full general liability and umbrella liability pages. Limits, forms, and editions vary by carrier, so the right move is always to confirm how your policy is structured rather than assume.