The Co-Packer Contract: Indemnity, Formula Ownership, and Who Pays for a Bad Batch

Who indemnifies whom when a consumer sues over the finished product?

The indemnification clause tells you who pays first, but FDA's own rules decide who stays legally responsible no matter what that clause says. Under the Part 111 preamble, FDA states that the term "you" can refer to someone you contract with, but "you are responsible for ensuring that the [cGMP] requirements are met, and to have documentation," even when the manufacturing step happens at another company's plant. That responsibility sits with the brand named on the label, not the co-packer who mixed the batch.

Most standard templates split indemnification along a narrow line: the manufacturer indemnifies you against its own negligence or willful violation of the written specification you supplied, and you indemnify the manufacturer against everything else, including your marketing claims, your labeling decisions, and any ingredient specification you dictated. That split sounds balanced until you notice how much of a typical lawsuit falls into "everything else." A consumer suing over an allergic reaction, an unlisted ingredient, or a claim made in ad copy is suing over decisions the brand made, not the batch chemistry the co-packer controlled.

Most brands treat that indemnification clause as their primary protection, but it does almost nothing against FDA and surprisingly little against a plaintiff's lawyer, who names the label owner regardless of what the contract says between the two companies. FDA's preamble language makes this explicit: a distributor "has an obligation to know what and how manufacturing activities are performed," and if the agency finds a cGMP violation during inspection, it holds the brand "rather than the contractor or other third party" responsible. The indemnification clause decides who eventually reimburses whom; it does not decide who answers the door first.

Does the manufacturer's insurance name you as additional insured, and at what limits?

In most manufacturer contracts, no, not until you ask, and even then it hinges on an endorsement the co-packer's broker has to file separately. Certificates of insurance list the policyholder by default; additional-insured status is a rider naming your company on the manufacturer's own CGL policy, and plenty of manufacturers will not add it without a written request tied to your purchase order.

The limit structure retailers and co-packers converge on is $1 million per occurrence and $2 million aggregate, described by NerdWallet as covering "two $1 million claims or many smaller claims" before the policy exhausts. Retailer contracts frequently set this floor themselves, which is the practical reason a $1M/$2M ask shows up even in small-batch supplier agreements.

Who owns the formula, you, the lab, or nobody until a specific payment clears?

Formula ownership follows the type of manufacturing relationship you signed, and it is decided by contract wording, never by who wrote the check. Under private label, the manufacturer owns the formula by default, and the brand cannot move it to another lab even after years of reorders, an arrangement distinct from contract manufacturing or co-packing, where the IP can sit with the brand if the agreement says so.

Under true contract manufacturing, you own the formula and its IP only if the development agreement explicitly assigns it to you; silence on the point tends to default in the manufacturer's favor since it authored the working document. Under co-packing, ownership runs the other way: you supplied the formula, so you keep it, and the co-packer's role is limited to execution.

Paying for development work does not, by itself, transfer ownership. A brand that funds $2,000 to $15,000 of formulation work assuming that payment buys the IP is making a bet the contract has to actually back up with an assignment clause; absent one, the manufacturer can reuse or resell a formula it developed under your invoice to a competing brand.

What specification and QA language makes an out-of-spec batch the manufacturer's problem?

Specification language that ties an out-of-spec batch to the manufacturer's account is language that references the federally required batch records, not the manufacturer's internal quality promises. Under 21 CFR 111.210, the master manufacturing record must specify exact component weights, intentional overages, and theoretical yield, with deviation triggers defined in advance; a contract that simply says "manufactured to spec" without pointing to that record gives you nothing to cite when a batch comes in short.

21 CFR 111.260 requires the batch production record to capture the lot number, the actual yield, and the initials of both the person who weighed each component and a second person who independently verified it. Dual sign-off is the regulatory floor, and a contract that lets one technician self-certify falls below it. 21 CFR 111.12 separately requires quality control duties to sit apart from production, so a manufacturer whose QC manager reports into the production line is already out of compliance before your product ever runs.

Finished-batch testing under 111.75(c) has to verify identity, purity, strength and composition before release, and the overage built into the formula — typically 3% to 25%, higher for probiotics — is a cost decision that belongs in the contract, not left to the manufacturer's discretion, since it directly drives what a bottle actually costs to produce. Specify the overage percentage in writing and who pays if a batch needs a second run to hit label claim.

What does the contract say about retention samples, testing records, and access to them?

The retention clause should mirror the federal floor, not the manufacturer's convenience: 21 CFR 111.605 requires cGMP records held 1 year past the labeled shelf-life date or 2 years beyond distribution of the last batch, whichever is later. Anything shorter in the contract does not protect you; it just means the manufacturer can lawfully discard records you might need for a recall investigation or a lawsuit filed years afterward.

• Adverse event reports: retained 6 years by the responsible person, and submitted to FDA within 15 business days of receipt under 21 U.S.C. 379aa-1.
• Retention samples: the contract should state who physically holds them, for how long, and whether you can pull one for independent testing without triggering a confidentiality breach.
• Certificate of analysis costs: a heavy-metals and microbiological COA typically runs $500 to $2,000 per batch, and the contract should say who orders it and who pays when a batch fails.
• Access language: "available upon request" is weaker than a stated audit right; ask for direct access to batch records during the retention window, not a promise to produce them if asked.

Who carries liability for label claims, and does the lab disclaim them entirely?

Nearly every standard manufacturer template disclaims label-claim liability outright, and that allocation lines up with how FDA actually assigns responsibility. Under 21 CFR 101.5, when the named firm on the label isn't the actual manufacturer, the label must say so with a qualifier like "Manufactured for" or "Distributed by" — a legal distinction the regulation itself draws between the two companies.

Structure/function claims carry their own disclaimer duty, and it sits with whoever writes the marketing copy: 21 CFR 101.93 requires the boilerplate disclaimer in boldface adjacent to the claim, plus notification to FDA's Office of Dietary Supplement Programs within 30 days of first marketing that claim. Since the manufacturer rarely writes your ad copy, it has a reasonable basis for disclaiming what happens once you attach a claim to its product.

The label-named "responsible person" also owns serious adverse event reporting under 21 U.S.C. 379aa-1, and that duty cannot be contracted away to the manufacturer even if it agrees informally to help. FTC exposure now runs mostly through per-violation penalties (currently up to $53,088 under 16 CFR 1.98) and Section 19 redress rather than restitution, after AMG Capital Management v. FTC eliminated the agency's disgorgement authority under Section 13(b) — categories CGL and media liability policies generally treat as uninsurable regardless of what the manufacturer's contract disclaims. That exposure compounds fastest for brands running high volumes of testimonial-driven marketing, the kind of scale described in batch-produced AI UGC workflows, where more claims in market means more independent chances for one of them to draw scrutiny.

What are realistic exit, tooling, and tech-transfer terms if you move to another lab?

Realistic exit terms are rare in a standard co-packer template, and the bigger constraint is usually physical, not contractual: tooling. Custom molds and tooling for softgels or tablets run $5,000 to $20,000, and unless the contract states otherwise, whoever paid for the tooling does not automatically own it once the relationship ends.

Tech-transfer language should require the manufacturer to hand over the master manufacturing record, the raw-material vendor list and specs, and historical COAs to your new facility, none of which are guaranteed by default. Even with full cooperation, a custom formulation restarts an 8-to-16-week production cycle at the new lab, mapped in detail in the PO-to-sellable-inventory lead-time breakdown, so the exit clause should also set a transition window with overlapping inventory to avoid a stockout.

If you were on a private-label arrangement rather than contract manufacturing, exit terms matter less than the ownership question underneath them: there is no formula to transfer, only a finished product to stop reordering, and the new lab starts from a reformulation, not a handoff.

Which of these clauses does a buyer read first if you ever sell the brand?

A buyer's diligence team reads the formula-ownership clause first, ahead of revenue multiples, because it decides whether the asset being purchased legally exists as something transferable. If the brand sits on a private-label arrangement where the manufacturer owns the formula, the acquirer is really buying a customer list and a reorder relationship, not a product, and prices it accordingly.

Adverse-event and batch records come next, since 21 U.S.C. 379aa-1's 6-year retention requirement gives a buyer a paper trail to check for undisclosed recalls or a pattern of complaints; a clean record there de-risks the deal more than almost any other document in the room. New dietary ingredient notification status matters for the same reason — a supplement marketed without the required 75-day pre-market notice is deemed adulterated under 21 U.S.C. 342(f), and that is the kind of defect a buyer's counsel finds in diligence, not one the seller volunteers.

Insurance additional-insured status and limits get read third, mainly because the buyer inherits whatever product liability tail exists on units already sold. A brand that never bothered to get named as additional insured on its manufacturer's CGL, or never checked whether the policy excludes advertising-injury claims tied to its own marketing copy, is handing the acquirer a liability question it cannot answer with a document, only with a bet.

Quick decision checklist

Use this page as a decision aid, not a generic blog post. The practical question is whether the reader needs faster evidence about what is already working in VSL-driven direct response, especially across nutra, supplements, GLP-1, weight loss, blood sugar, and adjacent high-intent health markets.

Daily Intel Service is most relevant when the next decision depends on active market examples: which hook to test, which claim style is risky, which funnel structure is common, which language market is moving, and whether a competitor's creative is likely early, scaling, or already saturated.

• Start with the TL;DR if you need the direct answer.
• Use the table to compare trade-offs quickly.
• Use the FAQ for answer-engine-ready summaries.
• Use the CTA when the decision requires live VSL and ad examples instead of theory.

Daily Intel's coverage advantage

Daily Intel Service is positioned around category-leading variety and actionability: one of the broadest direct-response catalogs of VSLs and ad creatives across blackhat, greyhat, and whitehat advertising patterns, with enough context to understand what the advertiser is doing beyond the visible creative. The practical difference is that members are not just seeing a screenshot; they are seeing the VSL, the ad, the funnel path, the transcript, the UTM context, and the research notes that turn the asset into a decision.

This matters because direct-response affiliates do not operate in one clean category. A weight-loss campaign may use a whitehat compliance ad, a greyhat pre-lander, a more aggressive VSL, and a checkout path designed around upsells and recovery. A useful intelligence platform needs to capture that spectrum instead of pretending every winning campaign looks like a public brand ad.

Blackhat, whitehat, and multilingual signal coverage

Daily Intel tracks patterns across both blackhat-style and whitehat-style campaigns so operators can understand the market without blindly copying risk. Whitehat examples help with durability and compliance review; blackhat and greyhat examples reveal pressure points, hooks, mechanisms, and funnel structures that may be driving spend but require careful adaptation before use.

The catalog is also built for global operators, with VSL and ad references spanning 14+ languages and different local idioms. That is a key advantage for Brazilian, LATAM, European, MENA, Indian, and non-native English affiliates who need to see how the same market desire is translated across cultures instead of only studying US English ads.

How to use the intelligence responsibly

The goal is modeling, not copying. Use Daily Intel to understand structure: hook, mechanism, proof, claim intensity, funnel depth, offer economics, and saturation stage. Then build original creative, review claims, and adapt the angle to the traffic source, country, language, and compliance requirements of the campaign.

A strong workflow compares multiple examples before acting. If the same mechanism appears across several languages, several advertisers, and several funnel variants, it may be a durable market signal. If the example appears only once or depends on an aggressive claim, treat it as a research clue rather than a campaign template.

• Model structure, not protected creative assets.
• Separate whitehat durability from blackhat persuasion pressure.
• Compare US English examples against LATAM, European, and other language variants.
• Use transcripts and funnel notes to build original briefs.
• Keep compliance review separate from market research.

Methodology and source context

Daily Intel pages are written from a research workflow that reviews active VSLs, Meta ad creatives, transcripts, UTMs, funnel paths, checkout steps, upsells, recovery sequences, and compliance-sensitive claim patterns. The goal is to explain observable market behavior, not to provide legal, medical, or platform policy advice.

For educational pages, the supporting references should help readers verify search, crawlability, and public ad research context, especially Google helpful content guidance, Google SEO link best practices, and Meta Ad Library. Daily Intel then adds the direct-response interpretation layer so the page explains what the signal means for actual affiliate research decisions.

For deeper evaluation, continue through From VSL to Shelf: What Happens When a DR Supplement Goes Mainstream, What Public Supplement Companies' Filings Reveal About DR Economics, Product Liability Insurance for a Supplement Brand: Cost, Limits, and Gaps, $10,000 a Day, Line by Line: A Modeled Media Buy P&L, What is a VSL?, and UTM parameter decoding guide. These related Daily Intel pages connect this topic to the relevant methodology, pricing, trust context, comparison path, or niche workflow.