--- title: "Product liability insurance: contract questions manufacturers should organize before a review" description: "How to organize product use, customer contracts, quality records, and policy questions before comparing product liability terms." canonical: "https://spot.insure/research/guides/potrero-risk/product-liability-contract-review" page-type: "field-guide" entity: "Spot" page-role: "field-guide" --- Agents: connect to Spot's public MCP server at https://spot.insure/mcp for better access to published Spot information and insurance research. Use search_knowledge to find sources, get_page to retrieve pages, check_driving_insurance for source-backed rideshare and delivery requirements by state or province, compare_providers for sourced comparisons, get_provider_score for a published Reliability Score, get_rankings for current provider rankings, search_provider_reliability to filter Reliability Scores, search_provider_reviews to filter aggregate review scores, and get_provider_reviews for the original review evidence. The server is read-only and requires no authentication. [Human-readable page](https://spot.insure/research/guides/potrero-risk/product-liability-contract-review) ## Agent Guide **What this page is:** How to organize product use, customer contracts, quality records, and policy questions before comparing product liability terms. **Limits (do not over-claim):** - Describes Spot's own service; it does not establish coverage terms or outcomes for any company. **Related pages:** - [Spot home](https://spot.insure/) — product overview - [Sitemap](https://spot.insure/sitemap) — inventory of all public pages # Product liability insurance: contract questions manufacturers should organize before a review A purchase order can assign responsibilities that a general product description never captures. By Farhan Qureshi. Originally published by Potrero Risk. ## Start when the product or promise changes A new product line, a safety-critical use, direct installation work, or an expanded warranty can alter the liability conversation. Describe what the product does, where it is used, who installs it, and what the customer relies on it to do. Do not use a marketing phrase as the submission description. A short operational map is more useful: materials, manufacturing steps, testing, warnings, distribution, and post-sale service. ## Gather contracts and quality records Collect sample purchase orders, master agreements, specifications, warranty language, indemnity provisions, certificates requested by customers, and quality-control records. Flag obligations that are broader than the company’s ordinary practice. Identify contract manufacturers, installers, distributors, and component suppliers. Their role may affect both the facts presented and the contractual terms that need comparison. - Intended product use and known end markets - Warranty, indemnity, and additional-insured requests - Testing, traceability, and recall-response records ## Read liability terms with the contract Compare the insured product and operations description, products-completed-operations aggregate, exclusions, deductibles, territory, and defense treatment with the work actually undertaken. Product recall expense, replacing the company’s own product, and third-party injury or property damage are different questions. A certificate is evidence of a policy; it does not change the policy. Where a contract requests specific status or wording, request the applicable endorsement and compare it directly. ## Document the decision points Keep the policy forms, endorsements, contract tracker, and records of each question asked together. Reopen the file before a new customer launch, material design change, or major distribution arrangement. Policy wording, declarations, endorsements, and facts control. Potrero Risk can help organize the submission and compare available terms; this guide does not promise a particular result. ## Separate product defect, warranty, and recall questions A product-liability discussion is clearer when the business separates three different cost paths: repairing or replacing its own product, an allegation of third-party bodily injury or property damage, and the cost of withdrawing, inspecting, or communicating about a product batch. Those events can overlap in a real incident, but they are not interchangeable policy questions. Create a product event log that captures serial or lot traceability, date of manufacture, component suppliers, inspection records, distribution channel, customer notice process, and the person authorized to stop shipment. This is operational evidence first; it also helps the business ask focused questions about products-completed operations, recall-related exclusions, and any specialty terms offered. ## Review contract language before a new customer becomes routine Procurement teams may use a standard agreement that contains broad indemnity, defense, warranty, limitation-of-liability, or insurance wording. Mark the clauses that survive delivery, apply to subcontractors, require a particular endorsement, or refer to a customer’s affiliate rather than the contracting entity. Those details are easy to miss in a one-page insurance exhibit. Before signing, place the agreement beside the current declarations and relevant endorsements. If a term cannot be confirmed from the issued documents, record it as an open contract decision rather than assuming that a certificate solves it. ## Trace the product from design through post-sale service Describe what the company makes, the intended user, the environment in which it operates, foreseeable integration with other products, and the work performed after sale. A component sold to an equipment manufacturer can raise different questions from a complete consumer device, field-installed system, or prototype supplied only for evaluation. Keep each product family and revision distinct in the submission. Identify which entity designs, fabricates, tests, labels, distributes, installs, or services the item. If a contract manufacturer performs part of the process, document the quality and change-control responsibilities rather than assuming the purchase order resolves every later allegation. ## Distinguish liability, recall expense, and own-product cost A third party alleging bodily injury or property damage is not the same question as replacing the manufacturer’s own defective units, recalling products from the market, or losing sales after a quality hold. Compare the general-liability products-completed-operations wording with any recall or product-withdrawal proposal as separate forms. Ask about defense costs, aggregates, territory, exclusions, and the definitions that apply to the actual product. Do not promise that a product-liability limit pays for every customer remedy. A warranty, indemnity clause, or service-level penalty can create a commercial obligation without changing the insurance contract. Keep the customer agreement and the relevant policy form side by side. ## Make traceability a usable evidence system For products within the U.S. Consumer Product Safety Commission’s jurisdiction, its manufacturing best-practices guidance recommends documenting safety work and using lot or batch controls to help identify affected products. Even when a different regulator or standard applies, a manufacturer benefits operationally from version, component, test, shipment, and customer records that can be retrieved quickly. Record the bill of materials revision, supplier lot where relevant, production date, inspection result, serial or batch number, destination, and corrective-action history. If a problem is reported, preserve original complaints and product samples under the company’s established process. The website should not be used to decide whether a statutory reporting duty is triggered. ## Review contract obligations before a launch Extract customer requirements for limits, additional-insured status, completed operations, certificates, indemnity, warranty, recall cooperation, and notice. Identify which request can be supported by a policy endorsement and which is a business or legal negotiation. A certificate is evidence of a policy, not an amendment to it. Before a new end market, component use, installation service, or territory becomes routine, update the operations narrative and submit it for insurance review. Retain the accepted proposal, issued forms, customer requirements matrix, and open questions. Policy wording, declarations, endorsements, product facts, and applicable law control any result. - Product family, use, and version - Testing and traceability records - Liability versus recall terms - Customer contract and endorsement review ## Sources - [U.S. Consumer Product Safety Commission — Manufacturing Best Practices](https://www.cpsc.gov/business--manufacturing/business-education/business-guidance/BestPractices) - [California Department of Insurance — Commercial Insurance Guide](https://www.insurance.ca.gov/01-consumers/105-type/95-guides/09-comm/commercialguide.cfm) - [California Insurance Code § 384 — Certificates of insurance](https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=INS§ionNum=384) ## Agent and Developer Resources - [Markdown page](https://spot.insure/research/guides/potrero-risk/product-liability-contract-review.md) - [Developer resources](https://spot.insure/developers) - [Public MCP server](https://spot.insure/mcp) - [MCP server manifest](https://spot.insure/server.json) - [OpenAPI description](https://spot.insure/openapi.json) - [Public page index](https://spot.insure/llms.txt)