[Home](/)/[Resources](/resources)/US Product Liability Law

United StatesProduct LiabilityLegal

# US Product Liability Law for Hardware Companies: Negligence, Strict Liability, and Breach of Warranty

Hardware companies face exposure on three separate legal theories — and a plaintiff's counsel will plead all three simultaneously. Understanding what each theory requires, where your engineering documentation helps, and what your warranty language is actually saying in a courtroom is the difference between a defensible product and a catastrophic recall.

Copy Link[Share on WhatsApp](https://wa.me/?text=https%3A%2F%2Fkrono-labs.com%2Fguides%2Fus-product-liability-law)

At a glance

Liability theories

Strict liability, negligence, breach of warranty

Key statute

15 USC § 2064 (CPSA substantial hazard)

Warranty source

UCC § 2-313 (express), § 2-314 (implied)

Federal preemption

Exception, not the rule — device/aircraft specific

CPSC report window

24 hours from responsible employee knowledge

## The three theories of product liability and how they apply to hardware

### Strict Liability: Restatement (Third) of Torts §§ 1–21

Under strict products liability, a plaintiff need not prove the manufacturer was careless — only that the product was defective and the defect caused the injury. The Restatement (Third) recognizes three defect types: manufacturing defects (the unit deviates from its intended design), design defects (the entire product line is unreasonably dangerous), and warning defects (failure to warn of risks that are not obvious). Most US states have adopted some version of this framework, though adoption of the risk-utility test for design defects is not universal.

### Design Defect: Consumer Expectations vs. Risk-Utility Balancing

Courts apply one of two tests to design defect claims. The consumer expectations test asks whether the product performed as an ordinary consumer would expect. The risk-utility test (predominant in the Restatement Third approach) asks whether the risks of the chosen design outweigh its benefits — measured against a reasonable alternative design. For electronics companies, the risk-utility analysis is where engineering documentation lives or dies: well-documented tradeoff analyses, FMEA studies, and design reviews can defeat the alternative-design element of a plaintiff's case.

### Negligence Per Se: Violating a Federal Standard

When a hardware product violates an applicable federal safety standard — CPSC, FDA, FAA, FCC — and that violation causes the plaintiff's injury, some jurisdictions apply negligence per se: the violation establishes negligence as a matter of law, eliminating the duty and breach elements from the plaintiff's burden. Compliance with federal standards, conversely, is evidence of reasonable care — but in most jurisdictions it is not a complete defense to a strict liability design defect claim.

### Implied Warranty of Merchantability: UCC § 2-314

Every sale of goods by a merchant carries an implied warranty that the goods are fit for the ordinary purposes for which such goods are used — unless properly disclaimed. For electronics, this means a device that fails prematurely, overheats unexpectedly, or malfunctions in normal use may breach this warranty even without proof of a specific design defect. Disclaimers must be conspicuous (UCC § 2-316(2)), typically in all-caps or contrasting type — buried fine print does not disclaim the implied warranty effectively under most state consumer protection laws.

### Express Warranty Creation: What Marketing Materials Can Do

Under UCC § 2-313, any affirmation of fact or promise that becomes part of the basis of the bargain creates an express warranty — no formal 'warranty' language required. Datasheets, product spec sheets, sales presentations, website copy, and demo videos can all create express warranties if they contain affirmations about performance, safety, durability, or operating conditions. Hardware companies frequently expose themselves through marketing language that engineering never reviewed. Sales and marketing teams must understand that 'rated for -40°C to 85°C operation' is a legally binding warranty statement.

### Federal Preemption and the Learned Intermediary Doctrine

Federal preemption of state tort claims arises when a federal agency has occupied a regulatory field (express preemption) or when state law conflicts with federal objectives (implied preemption). For hardware regulated by FDA as a medical device or by FAA as aircraft equipment, preemption arguments have succeeded in barring state failure-to-warn claims. The learned intermediary doctrine — relevant for B2B hardware — holds that warnings adequate for a sophisticated commercial buyer discharge the duty to warn, even if the end user is not warned. This doctrine has real traction for industrial electronics sold through integrators.

## How to build a defensible product liability posture from design through post-market

01

Conduct a formal product hazard analysis (FMEA, FTA, or PHA) during the design phase — not as a formality, but as a genuine engineering exercise that documents identified risks, failure modes, and the design decisions made to mitigate them.

02

Document risk-utility tradeoffs explicitly in design review records. If you chose Design A over Design B, write down why — the safety tradeoffs, cost tradeoffs, and technical constraints considered. This documentation is your primary defense to a design defect claim.

03

Review all warranty language before launch. Limit express warranties to specific, tested performance parameters. Disclaim implied warranties in conspicuous, capitalized language compliant with UCC § 2-316. Limit consequential damages for commercial buyers where permitted by state law.

04

Train product marketing and sales teams on warranty-creating statements. Every claim in a datasheet, white paper, product page, or sales demo is potentially an express warranty. Engineering must sign off on performance claims before they reach customers.

05

Establish a post-market vigilance program: field failure reporting, customer complaint tracking, systematic review of warranty claims. An unreviewed pattern of field failures that leads to an injury is the worst product liability scenario — it suggests you knew or should have known about the risk.

06

When a potential defect surfaces: issue a legal hold immediately to preserve all relevant engineering records, test data, and communications. Conduct root cause analysis. Assess whether the defect triggers a mandatory CPSC report under 15 USC § 2064 (substantial product hazard) — a 24-hour reportability window applies once a company has information reasonably supporting that conclusion.

07

If a recall is required, engage counsel and CPSC concurrently. Voluntary recalls under CPSC's Fast Track program resolve faster and carry less public stigma than mandatory recalls — but the remediation scope and consumer notification requirements are the same.

## Frequently asked questions

### Does passing CPSC or FCC certification protect you from product liability lawsuits?

No — and this is one of the most persistent misconceptions in the industry. CPSC and FCC certifications establish that a product meets specific regulatory standards at a point in time. They are evidence of reasonable care in the contexts those standards address, but they do not preempt state tort claims in most categories of consumer electronics. A product can comply with every applicable federal standard and still be found strictly liable for a design defect under state law if there was a reasonable alternative design that would have prevented the injury. Preemption is the exception, not the rule, outside of specific regulated categories like medical devices and aircraft.

### What's the difference between a manufacturing defect and a design defect under US law?

A manufacturing defect is a unit-level deviation: the product as manufactured differs from its intended design, and that deviation caused the injury. The design itself may be perfectly safe — the particular unit is the problem. A design defect is systemic: every unit in the product line carries the defect because the design itself is unreasonably dangerous. Manufacturing defect claims are typically proven with the defective unit; design defect claims require expert testimony on the risk-utility analysis and the existence of a reasonable alternative design. The litigation exposure for design defects is far larger because every sold unit is potentially defective.

### Can a limitation-of-liability clause in B2B contracts eliminate product liability exposure?

Partly, but not fully. A well-drafted limitation-of-liability clause in a B2B contract can cap or eliminate recovery for economic losses — lost profits, business interruption, consequential damages — between contracting parties. However, it cannot disclaim tort liability to third parties who are not party to the contract, and it cannot eliminate liability for personal injury or death under most states' public policy rules. In practice, a strong limitation clause protects you from your direct customer's commercial claims; it does not protect you from a personal injury lawsuit brought by your customer's customer or end user.

### When does a product defect trigger a mandatory CPSC report?

Under 15 USC § 2064(b) and CPSC regulations at 16 CFR Part 1115, a manufacturer, importer, or distributor must report to CPSC within 24 hours of obtaining information that reasonably supports the conclusion that a product contains a defect that could create a substantial product hazard, creates an unreasonable risk of serious injury or death, or fails to comply with an applicable consumer product safety rule. The 24-hour clock starts when a 'responsible employee' has the relevant information — not when legal counsel reviews it. Delayed reporting is itself a civil violation subject to up to $100,000 per violation and up to $15 million for a related series of violations.

**Disclaimer:** Educational resource only. Regulatory requirements change frequently. Consult a licensed US customs broker, trade attorney, or compliance specialist before making decisions.

[

Map your product, free

Every standard, document, and test that applies — free, no account required.

Start mapping](/platform/start)

Related guides

*   [US Warranty: Magnuson-Moss ActFull vs Limited warranty designation, disclosure rules, and the anti-tie-in restriction for hardware sellers.](/guides/us-warranty-magnuson-moss-act)
*   [UCC Article 2 Warranties for HardwareHow UCC Article 2 warranty obligations arise for hardware sellers: express warranties under 2-313, implied merchantability under 2-314, fitness for a particular purpose under 2-315, and drafting enforceable disclaimers and remedy limitations.](/guides/us-uniform-commercial-code-warranties)
*   [US Product Recall ProceduresComplete guide to US product recall procedures.](/guides/us-product-recall-procedures)
*   [US Post-Market SurveillanceComplete guide to US post-market surveillance requirements.](/guides/us-post-market-surveillance)
*   [Canada Product Liability LawCanada's product liability framework for hardware companies: the federal/provincial split, negligence vs. strict liability exposure, and how this compares to the US and Australian product liability regimes.](/guides/canada-product-liability-law)
*   [UK Consumer Protection Act 1987Part I of the Consumer Protection Act 1987: strict liability for defective products, who counts as a producer, the available defences including development risks, and how it interacts with the Product Regulation and Metrology Act.](/guides/uk-consumer-protection-act-1987)