Every inventor eventually meets the same sentence, buried on page nine of a retailer's vendor agreement: Supplier shall defend, indemnify and hold harmless Buyer from any and all claims arising out of the Products. That clause moves the entire liability exposure from a company with an enormous legal department to one that may be a single founder and a contract manufacturer. Building the engineering record and the insurance that make it survivable is part of product development, not an afterthought for the lawyers.
The Three Ways a Product Is Defective
US product liability law is largely state law, but the framework is broadly consistent. A plaintiff generally alleges one of three defect types, and in most states a seller can be held strictly liable: the plaintiff need not prove you were careless, only that the product was defective and the defect caused the harm.
- Manufacturing defect. The unit that hurt someone departed from your own design: a cold weld, a missing screw, a contaminated batch of resin. Easy for a plaintiff to prove, and best defended with real process control and inspection records.
- Design defect. Every unit is dangerous because the design is. Most states apply a risk-utility test: could a reasonable alternative design have reduced the foreseeable risk at acceptable cost and function? The question is whether you had a safer option and did not take it.
- Failure to warn. The product is as safe as it reasonably can be, but the user was not told about a residual hazard or how to avoid it. This is the most common claim against small consumer-product companies and the cheapest to prevent.
Alongside strict liability, negligent design claims target the process: did you test, did you anticipate foreseeable misuse, did you act on what you learned? Foreseeable misuse is the phrase that catches inventors off guard. A stool will be stood on. A cord will be yanked. Designing only for the intended use is not a defense.
Your Design Record Is Your Defense
When a claim arrives, the most valuable asset is a contemporaneous engineering record showing that you identified the hazard, evaluated alternatives, and made a documented, reasoned decision. Regulated industries call this a design history file, and nothing stops a consumer-product company from keeping the same thing. At minimum, maintain:
- A hazard analysis listing each foreseeable hazard, its severity and likelihood, and the mitigation chosen.
- Design calculations for load-bearing, pressurized, heated, or moving components, including the factor of safety you selected and why.
- Test reports, including the tests that failed and what you changed. Files showing only successes read as incomplete, not as a clean record.
- Applicable standards you designed to. Meeting the relevant voluntary standard is not an absolute defense, but a product that meets no standard at all is very hard to defend. Start from the safety testing requirements for consumer products.
- Life and abuse data. Reliability testing such as HALT and life testing shows you understood the failure modes before shipping.
- A controlled change history through a formal engineering change order process, so you can say exactly which units contain which revision.
Warnings and Instructions
Warnings follow the safety hierarchy: design the hazard out, then guard it, then warn about what remains. A warning that substitutes for a guard you could have afforded will not save you. When you do warn, follow the ANSI Z535 family for signal words, colors, and layout, and specify labels that survive cleaning, sunlight, and abrasion. Symbols carry much of the load internationally, which makes designing markings people actually understand a liability issue and not only a design one. Instructions must be readable by the actual user population, not by an engineer.
The CPSC Reporting Duty
For products under Consumer Product Safety Commission jurisdiction, Section 15(b) of the Consumer Product Safety Act creates an affirmative reporting duty. If you obtain information reasonably supporting the conclusion that a product fails to comply with a safety rule, contains a defect that could create a substantial product hazard, or creates an unreasonable risk of serious injury or death, you must report immediately, generally read as within 24 hours of the information reaching a responsible official.
Founders get this wrong in two directions. Some report nothing, hoping the issue is isolated; late reporting carries civil penalties that dwarf the cost of the recall. Others assume reporting means an automatic recall; in practice many reports end in a corrective action plan short of one, and the agency runs a fast-track program for companies that voluntarily propose a remedy quickly.
A recall costs far more than replacement units: notification, reverse logistics, retailer chargebacks, destroyed inventory, and lost shelf space. Products for children carry their own mandatory testing and certification regime, described in the CPSIA requirements for children's products, and the enforcement posture there is markedly stricter.
Insurance: Occurrence vs Claims-Made
Product liability coverage for a small hardware company normally comes as the products-completed operations part of a commercial general liability policy, sometimes with a separate umbrella layer above it.
| Occurrence | Claims-made | |
|---|---|---|
| Trigger | Injury happens during the policy period, whenever the claim is filed | Claim is filed during the policy period |
| After you cancel | Prior years remain covered | Coverage ends unless you buy tail coverage |
| Fit | Physical products with long service lives | Professional services, some specialty lines |
For a durable good that will sit in a garage for a decade, occurrence coverage is what you want. Injuries surface long after the sale, and claims-made coverage leaves you exposed the moment you stop paying premiums. Premiums vary by product risk more than by company size. A low-risk accessory with no moving parts and no heat might carry a $1M per occurrence and $2M aggregate CGL policy for roughly $1,000–$3,000 a year. A mains-powered appliance, a juvenile product, a ladder, or anything contacting food or skin can run several times that, and some categories are hard to place at all without third-party certification in hand. Underwriters ask for your test reports and your instruction sheet, so the standards work behind a safety-relevant product directly reduces what you pay.
What the Retailer Will Demand
Expect the vendor agreement to require a defense and indemnity obligation covering claims arising from the product, limits typically starting at $1M per occurrence and $2M aggregate and often much higher for big-box accounts, an additional insured endorsement naming the retailer, a waiver of subrogation, primary and non-contributory wording, and a current certificate of insurance before the first purchase order ships.
Two points to negotiate rather than accept blindly. Indemnity that covers the retailer's own negligence is common in first drafts and is worth pushing back on. And confirm your policy actually responds to a contractual indemnity obligation, because a bare CGL policy does not automatically cover liabilities you assumed by contract.
Projects House builds the engineering record behind a defensible product: hazard analysis, design calculations, test plans, and documentation that holds up long after launch. Tell us where you are through our contact form. This article is general information, not legal advice.