Amazon's New $1M Insurance Rule: What Changed on November 2
What happened: As of November 2, any seller with even one ASIN in Amazon's enhanced safety listing categories - small kitchen appliances, mattresses, tires, toys, and dietary supplements - now needs $1 million of commercial liability coverage, regardless of sales volume. The old rule only kicked in once a seller passed $10,000 in gross proceeds in a single month on Amazon.com; that threshold no longer shields low-volume sellers in these categories.
What exactly changed
Amazon confirmed the update in a notice posted to Seller Central's official forum, and independent seller-ops trackers including novadata.io and My Amazon Guy confirmed the same effective date and category list. For most sellers outside enhanced safety categories, nothing changes: the existing rule still applies - a 30-day window to secure $1M coverage once a seller crosses $10,000 in monthly gross proceeds. The change is narrow but absolute for the categories it touches: volume no longer buys a grace period.
Required coverage has to be commercial general, excess, or umbrella liability at $1M per occurrence and $1M aggregate, written on an occurrence basis so it covers every product a brand lists on Amazon - not just the flagged ASIN - and it has to name Amazon.com Services LLC and its affiliates as additional insureds. Amazon also tightened the path for Mainland China-based sellers: starting November 2, new policies from that group can only be purchased through the Amazon Insurance Accelerator program, though existing compliant policies are honored until they expire.
Why Amazon is removing the volume threshold
The enhanced safety categories - kitchen appliances, mattresses, tires, toys, supplements - share one thing: a defective or mislabeled unit can cause real physical harm regardless of how many units a brand has actually sold. A seller moving ten space heaters a month carries the same per-unit liability exposure as one moving ten thousand. Tying the insurance requirement to sales volume made sense as a blanket catalog rule, but it left a gap for exactly the sellers Amazon has the least visibility into - new or low-volume accounts in categories where a single incident can trigger a product-liability claim well above what a small seller could cover out of pocket.
What this means for brands
The immediate task is a catalog audit, not a policy purchase: pull every active ASIN, check which ones sit in an enhanced safety category, and confirm each one is covered under an existing policy's occurrence basis before assuming coverage carries over automatically. Brands selling across several categories - home goods and toys, for instance - often don't have a single person who can answer "which of our 400 SKUs are affected" from memory, and Amazon doesn't surface an enhanced-safety flag anywhere in Seller Central that's easy to bulk-export.
- Coverage gaps hide in category sprawl. A brand that only recently added a toy or supplement SKU to an otherwise unrelated catalog can miss that it's now subject to the $1M rule with no volume exemption.
- Policy terms matter more than the headline number. A $1M policy that isn't occurrence-based, or that doesn't name Amazon as an additional insured, doesn't satisfy the requirement even though the coverage limit looks right.
- Suppression risk is real and fast. Amazon has suppressed listings for insurance non-compliance before; a flagged ASIN in an enhanced safety category can go dark with little warning once the grace period Amazon allows for a given account runs out.
- This won't be the last category-level carve-out. Treating insurance compliance as a one-time check rather than an ongoing catalog state is what leaves brands exposed the next time Amazon narrows a threshold like this.
Checking "is this SKU in an enhanced safety category and is it covered" against a catalog of any real size by hand in a spreadsheet doesn't hold up past a few dozen SKUs, and it has to happen again every time the catalog changes. That's a recurring, rules-based problem - map category flags to policy status, alert when a new SKU lands in a flagged category, re-check before every file feed - that's a better fit for a lightweight internal tool than a quarterly manual review. It's the kind of narrow, purpose-built system our SaaS development team at YuSMP Group builds for marketplace brands: not a full compliance platform, just a tool that watches the one thing that can suppress a listing overnight.
How to check your own catalog
- Export the full active catalog. Pull every live ASIN via Seller Central or the SP-API Catalog Items report - don't rely on a mental list of "the toy and appliance SKUs."
- Cross-reference against the enhanced safety categories. Small kitchen appliances, mattresses, tires, toys, and supplements are the confirmed list as of this update; flag anything that falls in or near these.
- Pull your current policy and check three things. Coverage limit ($1M per occurrence and aggregate), basis (occurrence, not claims-made), and whether Amazon.com Services LLC and affiliates are named as additional insureds.
- Confirm the policy covers the flagged ASINs specifically. A general liability policy written for a different product mix may not extend cleanly to a newly added enhanced safety SKU.
- Set a recheck trigger. Any time a new SKU launches, re-run the category check before it goes live rather than catching a gap after a suppression notice.
For the data layer that makes a catalog-wide check like this possible without a manual export every time, see our breakdown of integrating your ERP with the Seller Central API, and for the build-vs-buy decision behind tooling like this, see our build-vs-buy framework for listing automation.
