Insurance requirements, typical coverage structures, and marketplace-specific thresholds change over time and vary by category and country — this is a conceptual orientation to the types of coverage relevant to a marketplace seller, not a recommendation of specific coverage limits or a statement of any marketplace's current requirement. Confirm current marketplace insurance requirements directly in your seller account's policy documentation, and work with a broker experienced in ecommerce/product liability coverage to size your actual policy.

Why this matters more than it might seem early on

A single serious product liability claim — a customer injury, a house fire attributed to a defective product, a widescale allergic reaction — can produce a legal defense cost and potential settlement/judgment that dwarfs a small or mid-sized seller's typical annual revenue, regardless of whether the underlying claim is ultimately proven or not; even successfully defending a meritless claim costs real money in legal fees. This is the core reason product liability coverage tends to be worth carrying well before a seller feels "big enough" to need it.

The main coverage types relevant to a marketplace seller

  • General liability — broad coverage for third-party bodily injury or property damage claims not specifically tied to a product defect (e.g., a warehouse visitor injury, if you have a physical location). A baseline most small businesses carry regardless of product category.
  • Product liability — specifically covers claims arising from a product you sold causing injury or property damage, whether from a design defect, a manufacturing defect, or a failure-to-warn claim (inadequate instructions/warnings). This is the coverage most directly relevant to a physical-product ecommerce seller, and the one most closely tied to your specific category's risk profile — a supplement or children's product seller generally needs to think about this more carefully than a seller of low-risk, low-injury-potential goods.
  • Cyber liability — covers costs associated with a data breach or cyberattack: notification costs, credit monitoring for affected customers, legal costs, and in some policies business interruption from a cyber incident. Increasingly relevant given how much customer payment and personal data an ecommerce business handles, even if you don't directly store payment card numbers yourself (most sellers offload actual card storage to a PCI-compliant processor, but you still typically hold names, addresses, order history, and sometimes email/marketing data that a breach would expose).
  • Business Owner's Policy (BOP) — a bundled package combining general liability and commercial property coverage, often a cost-efficient starting point for a small business with at least some physical footprint (inventory storage, office space).
  • Umbrella/excess liability — additional coverage on top of your other policies' limits, relevant once your underlying policy limits feel low relative to your actual risk exposure (higher sales volume, higher-risk category, or simply wanting more headroom before an unusually large claim exhausts your primary coverage).

Marketplace-required coverage

Amazon and some other marketplaces require sellers who exceed a certain sales volume (in a given category or overall — the specific threshold and its current value should be confirmed directly in the marketplace's current seller policies rather than assumed from older information) to carry product liability insurance meeting specific requirements, generally including:

  • A minimum coverage limit per occurrence and in aggregate (again, confirm the current figure directly with the marketplace rather than relying on a number that may be outdated).
  • The marketplace named as an "additional insured" on your policy — this isn't automatic on a standard policy; you typically need to specifically request this endorsement from your insurer/broker.
  • A Certificate of Insurance (COI) submitted to the marketplace as proof of coverage, which typically needs to be kept current and re-submitted if your policy renews or changes.

Missing this requirement once you cross the applicable threshold can result in listing restrictions or account-level consequences, so it's worth checking your current sales trajectory against the marketplace's stated requirement proactively rather than waiting for an enforcement notice.

How to actually get appropriately sized coverage

  • Work with a broker who specifically understands ecommerce and product liability, rather than a generalist small-business insurance agent — the category-specific risk nuances (a supplement seller's risk profile is genuinely different from a home-goods seller's) matter for both pricing and adequate coverage, and a specialist broker is more likely to price and structure this correctly the first time.
  • Some marketplaces and seller associations offer group insurance programs at negotiated rates for qualifying sellers — worth checking whether one exists for your category/marketplace combination before shopping independently, since a group program can sometimes offer better pricing or terms than an individual small-business policy would get on its own.
  • Size coverage to your actual risk, not just the marketplace minimum — the marketplace's required minimum is a compliance floor, not necessarily an adequate ceiling for your actual liability exposure, especially in a higher-risk category.
  • Review coverage annually and after any major change — a significant increase in sales volume, a new higher-risk product line, or expansion into a new country's marketplace are all reasons to revisit whether your existing coverage is still appropriately sized.

Cost factors worth understanding

Premiums are generally influenced by: your product category's inherent risk profile (children's products, supplements, and anything with combustion/electrical risk generally cost more to insure than low-risk categories like apparel or accessories), your sales volume, your claims history, and the coverage limits and deductible you choose. A specialist broker can usually give you a more useful sense of what's realistic for your specific situation than general benchmarks, since category and volume vary the number enormously.

What happens during a claim

Broadly: you notify your insurer as soon as you become aware of a potential claim (even before a lawsuit is formally filed, if you're aware of a serious complaint that could become one) → the insurer typically appoints defense counsel and manages the legal defense on your behalf as part of the policy → the insurer negotiates settlement or defends through trial, generally up to your policy's coverage limit, with you potentially responsible for any amount beyond that limit. Notifying late, or failing to notify at all until a claim escalates, can jeopardize coverage under some policies' notice requirements — treat a serious complaint as a "call your insurer" event rather than something to handle entirely on your own first and only escalate to insurance if it gets worse.

Common mistakes

  • Waiting until you "feel big enough" to need product liability coverage, rather than sizing it to your category's actual risk from early on.
  • Not requesting the marketplace-required additional-insured endorsement, assuming a standard policy already covers it.
  • Letting your Certificate of Insurance lapse without re-submitting after a policy renewal.
  • Treating the marketplace's minimum required coverage as automatically adequate for your actual risk exposure.
  • Delaying notifying your insurer of a serious complaint until it's already escalated into a formal claim or lawsuit.

FAQs

  • Do I need product liability insurance if I'm not required to by a marketplace yet? It's generally worth carrying well before you're required to, given how disproportionate a single serious claim's cost can be relative to a small business's revenue — treat the marketplace's requirement as a compliance floor, not the point at which the coverage first becomes worth having.
  • Does my marketplace's own liability protection (if any) replace the need for my own policy? Generally no — any protection a marketplace itself carries is typically for its own liability exposure, not a substitute for a seller's own required coverage, and marketplace seller agreements generally still require sellers to carry their own policy meeting specific requirements.
  • Is cyber liability really necessary if I use a third-party payment processor? Even without storing card numbers directly, you likely hold other personal data (names, addresses, order history, marketing lists) whose breach still carries notification costs and liability exposure — cyber coverage is worth evaluating based on the data you actually hold, not just payment card data specifically.