Most Amazon sellers think they’re covered. Most of them are wrong. Getting a certificate of insurance and adding Amazon as an additional insured isn’t the finish line — it’s barely the starting gate, and confusing the two has led to six-figure out-of-pocket losses for sellers who believed they’d done everything right.
This post is not about whether you need insurance. If you’re selling on Amazon at any meaningful scale, that question is settled. This is about the structural gap between what Amazon’s seller insurance requirements demand and what an ecommerce product liability coverage policy actually needs to do to protect your business when a claim lands.
What Amazon’s Insurance Policy Actually Requires — And What It Doesn’t Say
Amazon’s seller central insurance policy mandate kicks in once your gross proceeds exceed $10,000 in any single month. At that threshold, Amazon requires you to carry commercial general liability (CGL) insurance with a minimum of $1 million per occurrence. The policy must name Amazon and its affiliates as additional insureds, and you must provide proof of coverage within 30 days of receiving the notification.
That’s the letter of the requirement. Here’s what the policy language doesn’t spell out:
- Product liability vs. general liability: Amazon mandates CGL, which can include products-completed operations coverage — but only if your insurer explicitly writes it in. Many low-cost CGL policies strip out products coverage or cap it separately. Sellers who upload a CGL certificate and assume they have product liability insurance are frequently mistaken.
- Claims-made vs. occurrence-based policies: Amazon doesn’t specify. An occurrence-based policy covers incidents that happen during the policy period, regardless of when the claim is filed. A claims-made policy only covers claims filed while the policy is active. For physical products that may cause harm months or years after sale, occurrence-based is far more defensible — and Amazon’s requirement is silent on this distinction.
- Geographic scope: Amazon requires coverage for operations in the US. If you’re sourcing from overseas or selling into territories via Amazon Global, your policy’s territorial limits may create holes your certificate won’t reveal until a claim surfaces.
The Additional Insured Trap
Adding Amazon as an additional insured protects Amazon. It does not extend your coverage — it grants Amazon the right to file claims under your policy directly. What many sellers don’t realize is that when Amazon is named as an additional insured and a customer sues both Amazon and the seller, Amazon’s legal team can effectively leverage your policy limits to defend Amazon’s position first. If your aggregate limit is $1 million and Amazon’s defense consumes $600,000 of it, your remaining protection for your own business exposure is $400,000. Structure your limits accordingly.
The Real Risk Architecture for Amazon FBA Sellers
When evaluating the best insurance for Amazon FBA operations, most guides focus on policy type. That’s the wrong starting point. Start with your risk architecture — the specific liability vectors your product category and fulfillment model create — then build coverage around that.
Mapping Your Actual Exposure
Amazon FBA introduces liability variables that a brick-and-mortar retailer doesn’t face. Consider:
- Manufacturer liability by default: If you import private label products, US courts frequently treat you as the manufacturer. Your supplier’s insurance — if they even carry it — is largely irrelevant to a US plaintiff. You are the liable party.
- Amazon’s A-to-Z claims and chargebacks are not covered by insurance: These operational costs are separate from third-party bodily injury or property damage claims. Conflating the two leads to under-insuring the actual liability risk while operationally treating insurance as a refund mechanism.
- Co-mingled inventory: FBA’s commingled inventory program means your product units can be substituted with units from other sellers of the same ASIN. If a defective unit from a different seller causes harm and your ASIN is on the package, you may face claims even for units you never sourced. This is not theoretical — it has been the basis of actual litigation.
- Digital product adjacency: If your physical product connects to an app, pairs with software, or involves any digital component, some CGL policies exclude tech-related liability. A smart home device, a Bluetooth-enabled accessory, or a product with embedded firmware may fall into coverage gray zones your insurer won’t clarify until after a claim.
Structuring Coverage Tiers by Revenue Band
Rather than a flat threshold approach, structure your ecommerce product liability coverage around revenue tiers and product risk categories:
- Under $250K annual revenue: A $1M/$2M CGL with explicit products-completed operations endorsement, occurrence-based, is typically sufficient. Prioritize a carrier with ecommerce-specific underwriting experience over generic small business insurers.
- $250K–$2M annual revenue: Add an umbrella policy ($1M–$5M) sitting above your CGL. At this revenue level, a single product liability judgment can exceed your base policy limits. The incremental premium cost of an umbrella is modest relative to the exposure.
- $2M+ annual revenue: At this scale, you need a broker who specializes in ecommerce and product liability, not a generalist. Consider product recall insurance separately — CGL does not cover recall expenses, and a voluntary or regulatory recall of an FBA product at volume can cost more than the underlying liability claim.
Choosing a Policy That Survives a Real Claim
The market for product liability insurance for Amazon sellers has matured considerably. There are now carriers and MGAs (managing general agents) that specifically underwrite ecommerce businesses — some with Amazon-specific policy language built in. The question is not which brand is “best” in the abstract but which policy structure survives your specific claim scenario.
What to Verify Before You Buy
Before signing any policy, work through these checkpoints with your broker or carrier:
- Products-completed operations coverage: Confirm it’s explicitly included, not assumed under the CGL umbrella. Ask for the endorsement number in writing.
- Defense costs inside or outside limits: Some policies count legal defense costs against your per-occurrence limit. Others provide defense costs in addition to the limit. The latter is meaningfully better — a product liability defense can run $50,000–$200,000 before a verdict is reached.
- Vendor’s endorsement language: Verify the additional insured language meets Amazon’s specific requirements. Amazon periodically updates its seller central insurance policy language, and a generic additional insured endorsement may not satisfy their current vendor requirements.
- Exclusions for imported goods: Some US carriers include exclusions for products manufactured outside the US. If you’re sourcing from overseas — which describes the majority of private label FBA sellers — this exclusion will void coverage on the claims most likely to occur.
- Claim reporting obligations: Understand your duty to report. Many policies require notification of a potential claim — not just an actual claim — within a specific window. Missing that window can void coverage retroactively.
The Carrier Relationship Matters More Than the Premium
At the point of a product liability claim, you are entirely dependent on your carrier’s willingness to defend and indemnify. Low-cost policies from carriers with aggressive claims-denial track records are not bargains — they’re deferred expenses with interest. Review carrier AM Best ratings (A- or better is the standard threshold for commercial liability), check surplus lines vs. admitted carrier status in your state, and ask your broker explicitly: “Has this carrier denied coverage on a claim similar to my product category in the last three years?”
That last question will tell you more about the real value of a policy than any premium comparison.
Building Insurance Into Your Operational Risk Stack
Insurance for Amazon FBA is not a compliance checkbox — it’s one layer of a risk management stack that should include supplier contracts with indemnification clauses, product testing documentation, quality control records, and Amazon’s Brand Registry protections. A well-structured insurance policy amplifies those protections. A poorly structured one creates a false sense of security that leaves your business exposed exactly when you need coverage most.
The sellers who navigate product liability incidents with their businesses intact are almost never the ones who spent the least on insurance. They’re the ones who treated coverage as a strategic asset, understood the mechanics of their policy before a claim arose, and built relationships with brokers who understood the specific operational context of selling on Amazon.
Review your current policy against the framework above. If you can’t immediately answer whether your coverage is occurrence-based, whether products-completed operations is explicitly endorsed, or whether your aggregate limits account for Amazon’s additional insured position — those are gaps worth closing before Amazon’s notification arrives.
For deeper analysis on ecommerce compliance, brand protection strategy, and operational risk frameworks for Amazon sellers, explore more at Macetric.com. Our coverage is built for operators who are past the basics and focused on building resilient, scalable businesses.
