FDA Label Claim Substantiation: What You Need to Prove

Most food manufacturers know you can't put a claim on a label without backing it up — but far fewer know exactly what documentation FDA expects you to have on file before that product ships.

The gap between "we believe this is accurate" and "we have documentation to prove this" is where recalls and warning letters are born. FDA's approach to label claims is not passive. Under 21 CFR Part 101, the agency evaluates claims on finished product labels against both regulatory definitions and the actual formulation behind them. When those don't align — whether it's a nutrient content claim that doesn't match your Nutrition Facts panel, or a structure/function claim with no supporting data — you're exposed.

This matters more than ever because FDA's enforcement posture has shifted. The agency has increased warning letters tied to label violations, and class-action litigation targeting misleading claims has surged. A single unsupported claim on a label isn't just a regulatory problem — it's a liability vector that follows your brand long after the label is corrected. The good news: substantiation failures are almost entirely preventable at pre-launch review.

Here's exactly what FDA requires, claim by claim, and what your documentation file should contain before a SKU goes live.

Understanding the Three Claim Categories

FDA organizes label claims into distinct categories, each carrying different substantiation requirements. Conflating them is one of the most common errors QA teams make.

1. Nutrient Content Claims

These claims characterize the level of a nutrient in a food — "low sodium," "high fiber," "reduced fat," "good source of vitamin D." They are governed by 21 CFR Part 101, Subpart D, and each term has a precise regulatory definition tied to specific numeric thresholds.

"Good source" means 10–19% of the Daily Value per reference amount customarily consumed (RACC). "High" or "Excellent source" means 20% or more of the DV per RACC. "Low sodium" means 140mg or less per RACC and per 50g. These are not approximations — they are regulatory bright lines.

What you need to prove it:

• Certificate of Analysis (COA) from an accredited laboratory confirming nutrient levels per RACC
• Formulation documentation showing the recipe or ingredient breakdown that supports the tested values
• Nutrition Facts panel that is mathematically consistent with the claim (e.g., if you claim "high fiber," the Nutrition Facts must show ≥20% DV fiber)
• RACC documentation — confirm your serving size is correct per 21 CFR 101.12 before applying thresholds

A common breakdown point: a manufacturer updates a formula mid-cycle (changes a supplier, adjusts a ratio), but the claim and Nutrition Facts panel are not recalculated. The label now makes a claim the product can no longer support.

2. Health Claims

Health claims describe a relationship between a food, food component, or dietary supplement and a disease or health-related condition. They are tightly regulated under 21 CFR Part 101, Subpart E, and fall into two types:

• Authorized health claims: Supported by significant scientific agreement, pre-approved by FDA (e.g., calcium and osteoporosis, sodium and hypertension)
• Qualified health claims: Supported by emerging evidence, require specific disclaimer language and FDA enforcement discretion

What you need to prove it:

• Confirmation that you're using an exact FDA-authorized claim or a qualified claim with the required disclaimer language
• Evidence that your product meets the eligibility criteria for the claim (e.g., authorized health claims often require the food to meet specific nutrient disqualifying levels for fat, saturated fat, cholesterol, and sodium)
• Documentation that your claim language matches the authorized model claim — paraphrasing an authorized claim can invalidate it

This is an area where label copy written by marketing teams without QA review creates risk. A claim that is almost identical to an FDA-authorized claim but not exactly worded correctly is not a compliant claim.

3. Structure/Function Claims

These claims describe the role of a nutrient or ingredient in maintaining normal structure or function of the body — "calcium builds strong bones," "fiber maintains digestive health." For conventional foods, structure/function claims are permitted but must be truthful and not misleading under 21 CFR 101.93 and Section 403(r)(6) of the FD&C Act.

Note: For dietary supplements, 21 CFR 101.93 requires a 30-day pre-market notification to FDA. Conventional food manufacturers often don't realize this distinction — check which category your product falls under before assuming notification isn't required.

What you need to prove it:

• Scientific literature or credible evidence supporting the claimed function (doesn't need to meet the "significant scientific agreement" standard, but must be truthful and not misleading)
• Ingredient or nutrient levels in your finished product that are sufficient to deliver the claimed benefit — a "supports immune health" claim on a product with trace amounts of zinc is a problem
• Claim language that describes maintenance of normal function, not treatment or prevention of disease (disease claims require drug approval)

Pre-Launch Substantiation Checklist

Before any SKU with a label claim ships, your documentation file should include all applicable items below. Run this checklist at the label review stage — not after production.

For Every Claim Type:

• ☐ Identify the specific claim on the label and its regulatory category (nutrient content, health, or structure/function)
• ☐ Pull the applicable 21 CFR section and confirm the product meets every criterion
• ☐ Confirm claim language matches the regulatory standard verbatim or is clearly compliant
• ☐ Verify the claim is reflected consistently across all label panels (PDP, information panel, back panel copy)
• ☐ Check that no other element on the label contradicts the claim

For Nutrient Content Claims:

• ☐ Third-party COA confirming nutrient values per RACC
• ☐ Serving size verified against 21 CFR 101.12 RACC tables
• ☐ Nutrition Facts panel values mathematically consistent with claim thresholds
• ☐ Formula version logged — confirm COA reflects current formula, not a previous version

For Health Claims:

• ☐ Identify the authorized or qualified claim being used
• ☐ Confirm product meets eligibility criteria (nutrient disqualifying levels, minimum nutrient levels)
• ☐ Qualified claims: required disclaimer language present and legible
• ☐ Claim language reviewed against FDA's model claim language

For Structure/Function Claims:

• ☐ Supporting literature on file (minimum: credible, peer-reviewed sources)
• ☐ Ingredient/nutrient present at a meaningful level in the finished product
• ☐ Language reviewed to confirm no disease claim language present
• ☐ If dietary supplement: 30-day pre-market notification filed with FDA

Where the Process Breaks Down

In practice, label claim substantiation fails at three predictable points:

1. Formula changes after label finalization. A supplier substitutes an ingredient, or a ratio shifts during scale-up. The label claims weren't re-evaluated because no one flagged the change as label-relevant. Your SOP should require a label claim re-review any time a formula is modified — not just a full reformulation.

2. Marketing copy written without QA input. Marketing teams often draft claim language based on intent, not regulatory criteria. "Packed with protein" is not the same as "high protein" (20% DV per RACC) — but it can still be challenged if protein levels don't support the impression. Any claim language, implied or explicit, should go through a compliance review.

3. Documentation exists but isn't linked to the label version. You have a COA — but is it for the current formula, the current serving size, the current package size? Version control between label documentation and product specifications is where many manufacturers have gaps.

If you want to see how a structured pre-launch review catches these issues before they become costly, the 85-second RecallGuard walkthrough shows exactly how the process works.

What Your Substantiation File Should Look Like

FDA does not prescribe a specific format for substantiation files, but during an inspection or in response to a 483, you need to produce documentation quickly. Build your file to be audit-ready from day one:

• Label version log: Date-stamped copy of every label version, linked to the formula version it represents
• Claim registry: A list of every claim on the label, the applicable 21 CFR citation, and the status of supporting documentation
• COAs and lab results: Organized by SKU, formula version, and test date — not filed generically by product name
• Scientific references: For structure/function claims, maintain a bibliography with relevance notes
• Review sign-offs: Documentation that QA reviewed the label and claims before launch, with date and reviewer

If you're not sure whether your current substantiation documentation would hold up under scrutiny, the RecallGuard annotated sample report shows the specific flags a pre-launch review surfaces — including claim substantiation gaps, Nutrition Facts inconsistencies, and allergen declaration issues.

One Final Note on "Implied" Claims

FDA evaluates labels based on the overall impression they create — not just the explicit claim language. A label that says "No artificial ingredients" when the product contains a synthetic preservative is a misbranding violation under 21 CFR 101.18, even if the specific claim wasn't technically defined. Images, vignettes, and brand language can all create implied claims that carry the same substantiation burden as explicit ones.

Run your label review against the full visual and copy presentation, not just the claim bullets.

If you have a SKU launching soon and want a structured pre-launch review covering claims, Nutrition Facts accuracy, allergen declarations, and supplier documentation — a single SKU review is available for $349 and typically returns within five business days.