The Label Difference That Costs Sellers Claims

Short answer: "general liability" and "commercial general liability" are the same product. Nearly every small-business policy sold in the US is written on the ISO CG 00 01 form — a Commercial General Liability (CGL) standard that dates back to 1986. Insurers and brokers use both names interchangeably, which is where the confusion starts.

The real problem isn't the label — it's what the form excludes. CGL was built for plumbers, retailers, and contractors, not for sellers moving thousands of SKUs through FBA. Standard CGL forms exclude cyber breaches, ransomware, data theft, and regulatory fines, and they carve out chunks of product liability that eCommerce sellers assume are included.

Most sellers miss this. CGL was built in 1986 for plumbers, retailers, and contractors-not for someone moving 14,000 SKUs through FBA. Standard CGL forms exclude cyber breaches, ransomware, data theft, and regulatory fines (Assureful). They also carve out chunks of product liability that eCommerce sellers assume are included.

You already did the work. You bought a policy to pass an Amazon compliance check. You uploaded the COI to Seller Central and moved on. The question isn't whether you have general or commercial general liability-they're the same. The real issue: what does your specific form exclude, and does your current sales mix match the forecast you gave 18 months ago?

Two Policy Names, Several Non-Obvious Coverage Gaps

Most CGL forms sold to eCommerce sellers carry at least one exclusion that matters for imported goods. The most common: a third-party vendor clause that strips coverage when the manufacturer of record is an overseas factory. The insured seller becomes the liable "importer," and the exclusion ends the claim before it starts.

Product liability claims in eCommerce often exceed $50,000 in legal fees and settlements — enough to close a small store even when the product came from a third-party manufacturer (Assureful). Two years of paying premiums counts for nothing if the triggering claim falls inside an exclusion the seller never noticed at renewal.

The real problem sits beneath the naming debate. Both "general liability" and "commercial general liability" describe forms built for brick-and-mortar businesses in the 1980s. They were designed for plumbers, landlords, and retail shops. Not for someone sourcing from three factories across Jiangsu and Guangdong, selling through FBA, and shipping to six countries.

When your overseas factory is the manufacturer and you are the importer, standard CGL exclusions often treat you as the liable party. The declarations page does not say that. It does not tell you whether your supplier's products are actually covered. You find out when a claim arrives.

The second gap is the forecast problem. Most sellers filed a revenue estimate at signup. That number locked their coverage limits. If your store grew 40 percent since that filing, your current sales mix is underinsured until a claim triggers a coverage audit. Traditional policies bill annually against a projection you barely remember writing. Assureful's pay-as-you-sell model syncs premiums to actual monthly sales, which closes that specific gap without requiring you to remember to update anything.

The name on the declarations page tells you almost nothing. The endorsements, exclusions, and the revenue figure your broker used to price the form tell you everything.

Where Each Policy Stops Paying and Why

Roughly 19% of small-business GL policies either exclude product liability entirely or require a separate endorsement to add it (assureful.com). Products-completed operations coverage — the clause that pays when a product causes injury after it has left your warehouse — is the most commonly missing piece. Sellers assume the word "general" means comprehensive. It does not.

Amazon's compliance requirement says "general liability." Shopify merchant terms say "commercial general liability." They are the same product, but neither marketplace's language tells you whether products-completed operations, marketplace sales, or imported goods are actually in your form. Legal defense on a product-related lawsuit runs $35,000 to $54,000 before any settlement lands — the number that matters when an exclusion kicks in.

Here's where standard CGL stops paying:

• Injuries that happen before the sale, on your premises or through your operations, are typically covered.
• A buyer opens a package, uses the product, and is hurt three weeks later. That's a products-completed operations claim. A plain CGL form, without the endorsement attached, does not respond to it.

The distinction sounds technical. The outcome is not. When a plain CGL form excludes products-completed operations, the seller absorbs the full defense cost — and in the sellers we have seen, the wholesale accounts often drop them within 60 days of the filing, even before the case resolves.

Multi-channel selling sharpens the risk further. Amazon, Shopify, and wholesale accounts each carry separate contractual liability requirements. International fulfillment adds jurisdictional complexity that domestic CGL forms were not built to handle (hotalinginsurance.com). A single policy certificate satisfying one channel often leaves the others exposed.

The platform risk runs deeper than claims. Account suspensions, frozen inventory, and delisted listings can erase years of profit (assureful.com). CGL does not address marketplace compliance disputes. It does not respond to a platform freeze. Sellers who treat their CGL certificate as complete coverage find that out during the suspension, not before it.

The stopping point is not random. These forms were written for businesses that interact with customers face to face, in fixed locations, with predictable product flows. A seller sourcing from Jiangsu, fulfilling through FBA, and shipping to six countries does not fit that model. The form was not updated. The risk was.

Coverage Assumptions That Trigger Denied Claims

Two assumption failures show up repeatedly in denied eCommerce claims. Both are preventable. Both are expensive when missed.

Failure one: forecasted revenue does not match actual revenue. Traditional annual GL policies price premiums on a forecast the seller types into an online application at bind time. When actual sales end up 2–3x the forecast, carriers treat the gap as a material misrepresentation. A policy priced on $210,000 in forecasted revenue will not reliably pay out on a $18,000 settlement if actual sales hit $630,000. The carrier denies on revenue mismatch, the seller eats the settlement, and the retail partner often drops the relationship over lapsed compliance.

Failure two: no products-completed operations endorsement. When a claim involves a product used at home weeks after purchase — the most common pattern in cosmetics, supplements, and electronics — base CGL forms do not respond. The "products-completed operations" endorsement is what covers exposure after a product has left the warehouse. It is optional on standard forms. Most sellers never check whether theirs has it until the insurer is reading the claim back to them.

The revenue mismatch is not unusual. Traditional annual-premium GL policies force sellers to forecast sales upfront. A policy priced on $210,000 in forecasted revenue performs nothing like one sized to $630,000 in actual revenue. During quiet months, sellers overpay. During spikes, they are underinsured. Renegotiating mid-term means fees, friction, and a carrier that now knows you underestimated (assureful.com).

A seller who forecasts low to keep premiums down is making a bet. That bet pays off until it does not.

There is a second assumption that triggers denials just as reliably. Sellers treat CGL as a catch-all. It is not. CGL does not cover employee injuries. It does not cover professional mistakes. It does not cover damage to your own property or auto accidents (kaplaninsurance.com). Each of those gaps requires a separate form. Assuming otherwise leads to denied claims at the worst possible moment.

The pattern across these denials is consistent. A seller buys coverage quickly. They do not revisit it. Revenue grows. Product lines expand. Channels multiply. The policy stays frozen at the 2021 version of the business. The claim arrives against the 2024 version. The insurer responds to what the policy says, not what the business became.

By the time the fine print matters, the moment to fix it has already passed.

Which Policy Actually Protects eCommerce Operations

Here is the crux. The question is not whether you need general liability or commercial general liability. Those terms describe the same policy form. The real question is whether any CGL, sold once a year against a forecast, can cover how an online seller actually operates.

For most eCommerce sellers, it cannot. And Amazon is the reason most sellers have not noticed.

Amazon requires $1M in CGL coverage once a seller hits $10,000 in monthly sales. Walmart Marketplace, Target Plus, and Shopify Collective enforce similar rules. That mandate created a generation of sellers who bought a policy just to satisfy Seller Central. They filed the certificate. They moved on.

The problem is what a standard CGL form excludes:

• Cyber events
• Intellectual property disputes outside the narrow advertising injury clause
• Product liability for imports where the manufacturer sits offshore

A Jiangsu ceramic supplier cannot be sued in an Illinois court. The seller can.

So the seller who bought CGL to check the Amazon box is underinsured. They do not know it yet.

Adding product liability, cyber, and IP endorsements gets you closer. Now the annual forecast problem returns. A seller projecting $400,000 at renewal who ships $1.2M is underpriced and overexposed. A seller projecting $900,000 who ships $350,000 overpaid by thousands.

The fix is structural. Coverage has to move with the business. That means monthly billing tied to actual sales. Product categorization that updates as the catalog changes. Endorsements written for imported goods, licensed content, and customer data by default.

This is what Assureful was built for. Pricing runs against actual monthly revenue. The underwriting engine assesses product mix across 33,000+ categories. Imported product liability and cyber sit inside the base coverage, not bolted on after a claim exposes the gap.

Disclosure: Assureful is mentioned as a coverage provider in this article. The author has a business relationship with Assureful.

A typical corrective move: a Shopify seller importing from Jiangsu switches carriers and ends up with imported product liability and cyber endorsements the previous broker never mentioned. A prior kitchen-fire claim had settled at a $14,000 out-of-pocket loss. The next one lands inside the new policy's coverage.

A policy that pays versus a policy that denies. The difference is whether it was built for the business you actually run.

Choosing Wrong Leaves Your Store Unprotected

Sellers compare a $26 quote to a $99 quote and pick the cheaper one. They are comparing different underwriters, different claims teams, different coverage triggers. The gap stays invisible. Then the demand letter arrives.

Two illustrative cost points from sellers whose policies technically "covered" them: a Shopify seller importing diffusers absorbed $14,000 out of pocket because a third-party vendor exclusion applied to her manufacturer. A Walmart seller paid $38,000 on a skincare reaction claim because his CGL excluded the cosmetics category. Both had policies. Neither had the right one.

Checklist: What to Review in Your Policy

• Search your policy for these terms:
  • "products-completed operations"
  • "third-party vendor exclusion" or "importer exclusion"
  • "marketplace endorsement" (specific to Amazon, Walmart, etc.)
  • "cyber" or "ransomware"
  • "revenue" or "audit clause"
  • "worldwide territory"
  • "intellectual property infringement"
• Check for endorsements or exclusions that apply to:
  • Imported goods
  • Products sold through online marketplaces
  • Cyber events and data breaches
  • Actual sales revenue versus forecasted revenue

Questions to Ask Your Broker

• Does my policy cover products sold through all my sales channels (Amazon, Shopify, Walmart, wholesale)?
• Is there a products-completed operations exclusion?
• Am I covered for imported goods I sell as the importer of record?
• Are cyber and ransomware incidents included?
• How does the policy handle changes in my annual revenue or product mix?
• Does the COI I provide to each platform actually reflect coverage for that channel?

How to Confirm Your COI Covers Each Channel

1. Obtain the full policy, not just the certificate.
2. Match the named insured and business description to your current operations.
3. Check for channel-specific endorsements or exclusions.
4. Review the territory and jurisdiction clauses.
5. Ask your broker to confirm-in writing-that your policy covers all current sales channels and product types.

Key Takeaways

• Don't rely on the label-read the actual policy form and endorsements.
• Update your coverage as your business grows and changes.
• Verify product liability, cyber, and channel-specific protections are included.
• Consult a broker who understands eCommerce and can explain exclusions in plain language.

The gap between what sellers think is covered and what actually is can be wide-and expensive. Take the time to review your policy now. The claim that exposes the gap rarely comes with warning.