Product Liability: The Threshold Is Not A Risk Threshold

What The Coverage Actually Does

Terminology first, because two terms get used interchangeably and describe different things.

Commercial general liability covers third-party bodily injury, property damage, and associated legal costs arising from your operations. Product liability is not usually a separate policy; it is a component of a general liability policy, generally appearing as products and completed operations coverage.

The practical consequence is that asking a broker for general liability is not sufficient. The requirement is general liability that specifically includes product liability covering all products you list, and the certificate has to evidence that.

What triggers it is a claim that something you sold caused harm. Not that you were negligent, necessarily, and not that you manufactured it. That distinction is section three and it is the part that surprises people.

Why The Threshold Misleads

Here is the reframe that matters more than any requirement detail.

A marketplace threshold is a decision by the marketplace about when a seller's volume makes the platform's own exposure worth documenting. It is a risk management decision about the platform, made by the platform, for the platform.

The clearest demonstration is channel comparison. Reporting indicates Shopify, Etsy and eBay impose no insurance requirement. A brand selling identical products through its own Shopify store carries the same legal exposure as one selling on Amazon, and nobody will ever send it a notification.

That produces a predictable failure. Direct-to-consumer brands with no marketplace presence frequently carry no product liability coverage at all, not through any considered decision, but because no external party ever prompted them and the topic never reached an agenda.

The useful question is therefore not what your marketplace requires. It is what a claim would cost you and whether your business could absorb it. For nearly every brand selling physical goods, the answer makes the premium look small.

Strict Liability And Your Supplier

The legal principle that makes this unavoidable for resellers and private label brands alike.

Under strict liability principles, entities across the supply chain can be held responsible for a defective product regardless of fault. Reporting notes sellers can be held liable even when sourcing from third-party manufacturers, which is precisely the situation most ecommerce brands are in.

Two comfortable assumptions collapse here. The first is that a manufacturer's defect is a manufacturer's problem. It may be theirs as well, and that does not remove you from a claim brought against the party the customer bought from.

The second is that an overseas supplier relationship provides recourse. In practice, suing a factory in another jurisdiction is slow, expensive, and often not worth attempting, so a supplier indemnity clause is worth considerably less than it reads.

This is also why sourcing decisions carry insurance consequences. A supplier who can produce their own liability coverage and safety testing documentation is a lower-risk relationship, and that belongs in supplier evaluation alongside price. Our product research guide covers where those checks fit.

What Amazon Requires

The requirements below are widely reported and, in several places, reported inconsistently. Treat this as a map of what to check rather than as the specification.

The additional insured wording deserves particular care, because it is a text string that either matches or does not. Sources give at least two different entity formulations, and a certificate naming the wrong Amazon entity is a rejected certificate even though the underlying coverage is fine.

Why Valid Policies Get Rejected

The operational trap, and the reason a thirty-day window can expire while you are technically insured.

A policy can be genuinely active, adequate, and in force, and still fail a marketplace review. The review is not asking whether you are insured. It is checking specific fields on a certificate against a specification.

Every one of these is avoidable by giving your broker the platform's requirement text at the outset rather than describing it. Brokers produce certificates to specification routinely; they cannot meet a specification they have not seen.

The other habit worth building is checking the certificate yourself against the requirement, field by field, before uploading. It takes ten minutes and it is the difference between one submission and three.

Occurrence Versus Claims-Made

A technical distinction with a trap inside it that catches multi-category sellers.

An occurrence policy responds to incidents that happened during the policy period, whenever the claim arrives, including years after you cancel. A claims-made policy responds to claims made during the policy period, which means coverage stops when the policy does unless you buy extended reporting.

Occurrence is better for product sellers, because product injury claims frequently surface long after the sale. Reporting indicates Amazon requires occurrence-basis policies for this reason.

The exception list matters. Reporting indicates Amazon permits claims-made policies for pharmaceuticals, nutraceuticals and dietary supplements, ingestible products, chemicals, critical automotive parts, and children's consumable products, on the basis that these are frequently not insurable on an occurrence form.

Brands in the exception categories should also understand what claims-made means for exit. If you sell the business or stop trading, claims can still arrive, and coverage ends with the policy unless extended reporting is purchased. That belongs in exit planning, which our guide to preparing a brand for sale covers.

Walmart And Other Channels

Requirements differ by platform, and the differences are not trivial.

Walmart. Reporting indicates a certificate is required once a seller exceeds $100,000 in gross merchandise value over any twelve-month period, or on direct notification, with limits of $1,000,000 per occurrence and $2,000,000 aggregate, and Walmart Inc. together with its subsidiaries and affiliates named as additional insured. Note both the different threshold basis, annual rather than monthly, and the higher aggregate.

Shopify, Etsy, eBay. Reporting indicates no platform insurance requirement at all. Your legal exposure is unchanged.

Wholesale and retail partners. Certificates are commonly requested by fulfillment providers, suppliers, wholesale buyers, and retail partners, often with their own limit requirements and their own additional insured wording.

The practical consequence for a multi-channel brand is that one policy must satisfy several specifications simultaneously. Build to the strictest one you face rather than the one that arrived first, because a policy meeting Amazon's structure may not meet Walmart's aggregate, and discovering that during a Walmart onboarding is an avoidable delay.

What The Policy Does Not Cover

Worth knowing before you assume a general liability policy is a general safety net. It is not.

• Data breaches and cyber incidents. Excluded from general liability and from most packaged small business policies. Separate cyber coverage handles this.
• Product recall costs. Notifying customers, retrieving stock, and destroying inventory are usually not covered by liability insurance, which responds to injury claims rather than to the cost of pulling a product.
• Your own damaged inventory. Property coverage, not liability.
• Employee injury. Workers' compensation, which is separately mandated by state law once you have employees.
• Intentional acts and known defects. Continuing to sell something you knew was dangerous is not an insurable event.

The recall exclusion is the one that surprises brands most, because recall is precisely the scenario people imagine insurance covering. Recall costs are typically a separate product recall policy, and the wider set of gaps between standard policies is worth reviewing alongside it, commonly recommended for food, supplement, cosmetic, and electronics sellers.

The last item deserves emphasis for a reason that is not really about insurance. Knowing about a defect and continuing to sell converts an insurable accident into an uninsurable decision, which means your safety complaint process is part of your risk management whether you thought of it that way or not.

Recall Exposure Is Separate

Insurance sits alongside a legal reporting duty that exists independently of any policy you hold.

US regulation at 16 CFR Part 1115 establishes obligations to report substantial product hazards to the Consumer Product Safety Commission. That duty attaches to information you receive about your products, and it does not wait for you to decide whether a claim is likely.

The connection to insurance runs in both directions. Meeting the reporting duty promptly is part of acting reasonably, which matters if a claim follows. And ignoring information about a hazard risks moving an incident from insurable accident toward known defect, per section eight.

Practically that means somebody owns safety complaints, a written threshold exists for escalating a complaint into a formal assessment, and the assessment gets documented. Most brands have a returns process and no safety process, and the difference between the two is whether anyone is reading complaints for hazard signals rather than for refund eligibility.

Our guide to reducing return rate covers the measurement side of complaint data, and the relevant discipline here is separating quality complaints from safety complaints rather than treating all negative feedback as one pool.

Sizing Your Limits

Marketplace minimums are a floor set by someone else's risk appetite. Whether they are adequate for you is a separate question.

The sensible starting point is to begin with partner and marketplace requirements and then adjust based on your total exposure and contractual expectations. Factors that argue for more than the minimum:

• Product risk profile. Ingestibles, electricals, children's products, and anything with heating, cutting, or chemical properties carry higher severity potential than apparel.
• Volume. More units in circulation means more opportunities for a claim, and a defect affects a population rather than an individual.
• Multiple channels. Aggregate limits are consumed across all claims in a period regardless of where the sale occurred.
• Partner requirements. Retail buyers frequently expect more than marketplaces do.
• Business value. If a claim exceeding your limit would end the business, the limit is doing less work than you think.

Umbrella or excess liability sits above your primary policy and is usually inexpensive relative to the additional limit purchased, which makes it the efficient way to buy meaningful headroom. It is worth pricing rather than assuming it is out of reach.

Whatever you land on, the premium belongs in your unit economics rather than sitting in overheads unexamined. Our guide to reading an Amazon P&L covers where it fits, and for regulated categories our supplements brand playbook covers the wider risk picture.

The Thirty-Day Scramble

What actually goes wrong, and it is a timing problem rather than a cost problem.

A notification arrives giving thirty days. That sounds generous until you sequence what has to happen: find a broker, complete an application, receive quotes, bind coverage, request a certificate with the correct additional insured wording, upload it, and have it reviewed. A rejection on any field restarts part of that.

Reporting includes an account of a seller who crossed the threshold, had no coverage, spent three days arranging it, and had listings frozen during the gap, losing sales and paying a rush premium. Take the specific figures as illustrative, since the source sells policies, and the shape of the failure is entirely plausible.

The avoidance is trivial. Arrange coverage before you approach the threshold rather than after crossing it, at which point you are buying calmly, comparing quotes, and getting the certificate right without a clock running.

Renewals deserve the same treatment. A lapsed certificate produces the same account problem as never having one, and renewal dates are exactly the sort of thing that gets missed. Diarise it with a month's warning.

A Sensible Sequence

In order, for a brand that does not currently have coverage.

1. Decide on exposure, not on thresholds. If a claim would end the business, you need coverage now regardless of what any platform asks.
2. Collect every requirement you face across marketplaces, fulfillment partners, and wholesale buyers, and build to the strictest.
3. Confirm your legal entity name exactly as it appears on each account, since mismatches are the leading rejection cause.
4. Give your broker the requirement text verbatim. Not a description of it.
5. Check the certificate field by field before uploading. Limits, insured name, additional insured wording, deductible, carrier rating, and evidence of products and completed operations.
6. Ask about the categories you sell if any fall in the claims-made exception list, and confirm whether you need a second policy.
7. Price umbrella coverage for headroom above the minimum.
8. Diarise renewal with a month's notice, and re-check requirements at renewal since they change.

If You Sell Only On Your Own Site

Nothing above will ever be prompted by anyone. No notification arrives, no listing gets frozen, and no threshold triggers. Your exposure is identical to a marketplace seller's and your prompt to act does not exist, which is why direct-to-consumer brands are disproportionately uninsured.

The decision is simply whether the premium is worth transferring a risk that could otherwise end the business. For most brands selling physical products it plainly is, and the reason it does not happen is not analysis but absence of a trigger. If that describes you, treat this article as the trigger, and speak to a broker rather than to us, because we genuinely have nothing to sell you here.