Amazon Product Liability Insurance: The $10,000 Rule Most Sellers Learn About Too Late

What Amazon actually requires

The obligation sits in section 9 of the Amazon Services Business Solutions Agreement, which almost everybody accepts without reading. In plain terms, it says that once your sales reach a certain level, you will carry commercial general liability insurance and name Amazon on it. The clause is there from the day you register.

The details matter more than the summary. Amazon asks for commercial general liability cover of at least $1,000,000 per occurrence and $1,000,000 in the aggregate, and that cover has to include products liability and bodily injury. The policy has to come from an insurer with a solid financial strength rating, commonly expressed as A- or better from AM Best or an equivalent agency. And Amazon.com Services LLC, with its affiliates and assignees, has to be named as an additional insured on the policy itself. A mention on a piece of paper is not enough.

That last point trips people up constantly. A certificate of insurance is a summary document. Being named as an additional insured is an actual change to the policy, usually made through an endorsement. Some brokers will happily type Amazon's name into the certificate box without touching the underlying policy, which produces a document that looks right and is wrong in substance.

How the $10,000 threshold works

The trigger is $10,000 in gross proceeds in any single month. Annual revenue, profit and rolling averages don't come into it. One month above the line puts you inside the requirement, and once you are in, you are expected to stay insured through slow months as well.

Gross proceeds means the money that flows through the account before Amazon takes anything out. Sellers often misjudge this because they think in terms of what lands in the bank. A seller doing $14,000 in sales with a $9,000 payout after fees and ad spend is well past the threshold, even though the deposit looks modest. Refunds complicate it further. Realistically, if you are anywhere near $10,000, you are close enough that waiting for certainty is a bad trade against the cost of a policy.

Here is an illustrative example of how the threshold catches seasonal sellers. A brand averages $6,000 a month for most of the year, then sells $11,500 in November and $13,000 in December. Its annual average is nowhere near $10,000 a month, but November alone crosses the line, and from then on the requirement applies, including in the quiet months that follow.

There is a second reason not to wait. Insurance responds to when an incident happened, and the date you bought the policy doesn't change that. A product that shipped in March and caused an injury in April is not covered by a policy you bought in June. Cover bought after a problem surfaces is the one purchase that definitely won't help.

Why valid policies get rejected

Most of the real pain is here. Sellers buy a genuine policy from a real insurer for a real premium, upload the certificate, and get a rejection with a generic message that doesn't say what was wrong. The policy is usually fine. The paperwork is not.

• The additional insured wording is incomplete. Amazon wants "Amazon.com Services LLC and its affiliates and assignees" as a single phrase. Certificates that say "Amazon", "Amazon.com", "Amazon Inc" or "Amazon FBA" get bounced. The phrase "and its affiliates and assignees" is required, and leaving it off is probably the most common failure of all.
• The named insured does not match Seller Central. The legal entity on the certificate has to be the legal entity on the account. If you registered as a limited company and the policy is in your personal name, or the company changed its name and the policy never followed, a reviewer sees two documents describing different businesses.
• The policy is claims-made. Occurrence policies respond to incidents that happen during the policy period, whenever the claim arrives. Claims-made policies respond only if the claim is also reported during the period. Amazon expects occurrence cover, and general liability is normally written that way, though not always.
• Products liability is excluded. Some cheap general liability policies carve out products and completed operations, which is precisely the risk Amazon cares about. A policy that covers someone slipping in your warehouse but not your product causing harm doesn't meet the requirement.
• The certificate is expired or about to be. Reviewers check dates. A certificate with three weeks left on it invites a second request almost immediately.

The practical fix is to give your broker Amazon's exact requirement text instead of describing it. Brokers who write for ecommerce sellers see this every week and will produce the right endorsement without discussion. Brokers who mostly insure local trades may never have been asked to name a marketplace as an additional insured, and will fall back on their standard template.

When a rejection comes back, compare the certificate against each condition in the next section before you call the broker. Tell them which line failed. "Amazon rejected it" sends a broker back to the template that caused the problem; "the additional insured line is missing 'and its affiliates and assignees'" gets fixed the same day.

Reading the requirement line by line

Treat the requirement as a checklist of separate conditions, because a certificate can satisfy four out of five and still be rejected.

1. Type of cover. Commercial general liability, including products liability and bodily injury. Some sellers buy professional indemnity or product recall cover instead. Those are different products and don't substitute.
2. Limits. $1,000,000 per occurrence and $1,000,000 aggregate at minimum. Per occurrence caps a single incident, and aggregate caps the whole policy year. Both have to clear the bar.
3. Insurer quality. Rated A- or better by AM Best, or the local equivalent for non-US insurers. This rules out some very cheap unrated markets.
4. Additional insured. The exact Amazon entity phrase, added to the policy by endorsement.
5. Entity match. The named insured identical to the Seller Central legal entity, including suffixes like LLC or Ltd.

Stacking is allowed and is often the cheapest way to reach $1,000,000. A $500,000 general liability policy plus a $1,000,000 umbrella above it gets you comfortably past the limit, usually for less than a single policy at the higher limit. Upload both documents together.

Uploading the certificate and checking it was accepted

The certificate is uploaded in Seller Central, in the business insurance section of Account Info under Settings. Upload the certificate and, if your broker issued it separately, the endorsement, and for a stacked arrangement upload both policies. Fill in the policy details exactly as they appear on the documents; a typed expiry date that differs from the certificate is an avoidable reason for a second review.

Then check back. The same page shows whether the certificate is pending, accepted or rejected. Don't assume no news is good news: a rejection notice can get lost among other Seller Central messages, and you only find out when the next request arrives with a deadline attached.

What this actually costs

Less than most sellers fear, and the fear is why some put it off until they are forced. For a typical small to mid-sized seller in a low-hazard category such as home goods, apparel or accessories, annual premiums for $1,000,000 of general liability commonly land in the low four figures, and sometimes under a thousand dollars for smaller accounts. Against the revenue that triggered the requirement, it is usually small.

Category drives the price far more than revenue does. Anything ingested, applied to skin, used by children, powered by lithium batteries or load-bearing sits in a higher band, sometimes much higher. Supplements, cosmetics, kids' products, electricals and anything mounted above a person are where underwriters ask real questions and charge accordingly. If you sell in those spaces, budget properly and expect questions about testing, labelling and your supply chain.

Underwriters usually ask for a product list, annual revenue by category, where products are made, and whether you hold test reports. Having that pack ready before you ask for quotes makes the process faster and the quotes more comparable. Get at least two quotes, and check each one for a products exclusion before comparing prices.

Amazon also runs an insurance referral programme that connects sellers with vetted providers who already know the requirement wording. It is optional and not always the cheapest quote, but it removes the risk of a broker producing a certificate that fails review, which is worth something when a deadline is running.

What happens when a claim lands

Amazon runs a process for customer product safety and injury claims that sits partly outside your control. For lower-value claims, Amazon may settle with the customer directly and then look to the seller to stand behind it. For larger claims, Amazon will usually pass the matter to you and your insurer, which is exactly why it wants to know an insurer exists before anything goes wrong.

Two practical consequences follow. First, tell your insurer early. Policies contain notification conditions, and handling a claim yourself for a few weeks before involving the insurer can prejudice cover. A message from Amazon about an injury is a notifiable event even if it looks minor and even if you think the customer is mistaken.

Second, keep the paperwork a defence depends on. Supplier invoices, compliance certificates, test reports, batch records and the listing as it appeared at the time of sale all matter. A seller who can show the product met the relevant standard and the listing didn't overstate anything is in a very different position from one reconstructing a supply chain from memory a year later.

Keep the insurance question separate from the account health question. An injury claim can arrive alongside a product safety complaint that suppresses the listing. They are two processes with two remedies, and settling the insurance side does nothing to restore the ASIN. The listing comes back through the safety and compliance route, with documentation. Your broker can't help with that part.

First steps when Amazon forwards an injury claim

1. Save the message and any attachments, and note the date you received it.
2. Notify your insurer or broker the same day, forwarding everything Amazon sent.
3. Don't admit fault or offer settlement to the customer before your insurer advises.
4. Pull the batch records, test reports and the listing version for the order in question.
5. Check Account Health for any linked product safety complaint, and handle that separately.

A checklist before you upload

Run through this before submitting anything, because a rejected certificate costs days you may not have.

• Named insured matches the Seller Central legal entity exactly, including the suffix.
• "Amazon.com Services LLC and its affiliates and assignees" appears as additional insured, in full.
• Limits show at least $1,000,000 per occurrence and $1,000,000 aggregate.
• Cover is commercial general liability including products liability, written on an occurrence basis.
• Policy dates leave a comfortable runway, ideally more than sixty days.
• The insurer's rating meets the requirement, and you can say which agency rated it.
• You hold the endorsement document as well as the certificate.

Set a calendar reminder for renewal roughly six weeks before expiry. Amazon doesn't always chase a lapsed certificate straight away, but when it does, the request tends to come with a short deadline, and brokers move at their own pace. Sellers who treat this as an annual admin task never have to think about it as an emergency.

Insurance belongs with tax registration and product compliance. None of them grow your sales, and any of them can stop your sales. Handle them early and once, before you're doing it under a deadline with a suspended account and a broker who is out of the office. Our guide to why verification documents fail covers the same name-matching problem in a different setting.

Frequently asked questions