Pre-Launch Allergen Review: FDA Compliance Checklist
Undeclared allergens are the single leading cause of FDA food recalls — and the majority of them trace back to errors that existed on the label or in the formula before the product ever shipped. A structured pre-launch allergen review catches these errors when fixing them costs you a revised proof, not a Class I recall.
Why Allergen Errors Happen Before Launch
Most allergen-related recalls don't stem from rogue contamination events. They stem from documentation failures: a supplier changes an ingredient and doesn't notify you, a formula is updated but the label isn't, or a co-packer runs a different lot of seasoning blend without flagging that it now contains soy. These are process failures, and they're preventable.
Under the Food Allergen Labeling and Consumer Protection Act (FALCPA), manufacturers are legally required to declare the presence of the nine major food allergens — milk, eggs, fish, shellfish, tree nuts, peanuts, wheat, soybeans, and sesame (added under FASTER Act, effective January 1, 2023) — either in the ingredient list using common names or in a separate "Contains" statement. The regulation covers any food that is, or contains an ingredient that is, one of those nine allergens, including proteins derived from those sources.
The FDA's enforcement posture has become increasingly aggressive. Between 2018 and 2023, undeclared allergens consistently represented 40–50% of all Class I food recalls — the category reserved for situations with a reasonable probability of causing serious health consequences or death. For manufacturers operating at volume, a single recall event can cost $10 million or more when you factor in product retrieval, customer chargebacks, regulatory response, and brand damage. The economics of a pre-launch review are straightforward.
The Pre-Launch Allergen Compliance Checklist
Use this checklist for every new SKU before label approval and first production run. It's organized by phase: formula verification, label review, supplier documentation, and production controls.
Phase 1: Formula Verification
Start with your Bill of Materials (BOM) or formulation sheet. Every ingredient — including processing aids, carriers, and incidental additives — must be reviewed against the FALCPA allergen list.
- List every ingredient by its declared name and supplier specification. Generic descriptions like "natural flavor" or "spice blend" are not sufficient at the formula level — you need the full breakdown from your supplier.
- Flag all derivatives and hidden allergen sources. Casein = milk. Hydrolyzed vegetable protein (HVP) may contain wheat, soy, or corn. Lecithin may be soy- or sunflower-derived. Tahini = sesame. Each of these requires declaration under FALCPA if the source is a major allergen.
- Check processing aids and carriers. Ingredients used in processing (e.g., release agents, anti-caking compounds, encapsulation carriers) that are present in the finished product at any level must be declared if they introduce a major allergen.
- Verify tree nut specificity. FALCPA requires you to declare the specific type of tree nut (e.g., "almonds," "cashews," "pecans") — "tree nuts" alone is not compliant as a "Contains" statement.
- Verify fish and shellfish specificity. Same requirement applies — you must name the species (e.g., "salmon," "cod," "shrimp," "crab").
- Cross-reference your formula against your most recent supplier spec sheets, not last year's. Formulas change. If you can't confirm the current spec, you can't confirm allergen status.
Phase 2: Label Review
Once your formula is confirmed, compare it line-by-line against the finished label artwork. This is where label/formula mismatches most commonly occur.
- Verify ingredient declaration order. Under 21 CFR 101.4, ingredients must be listed in descending order of predominance by weight. An ingredient listed out of sequence can trigger regulatory action independent of allergen concerns.
- Confirm common names are used for allergen-containing ingredients. "Sodium caseinate" must be followed by "(milk)" in parentheses or listed in a "Contains" statement. "Albumin" must be identified as egg-derived. FALCPA's plain-language requirement applies to any ingredient name that does not make the allergen source obvious to a reasonable consumer.
- Audit your "Contains" statement for completeness and accuracy. If you use a "Contains" statement, it must list every major allergen present in the product. Omissions are violations. Additions — listing an allergen not actually present — create legal and commercial exposure. It must be accurate in both directions.
- Confirm sesame is declared. The FASTER Act added sesame as the ninth major allergen effective January 1, 2023. Many manufacturers updated formulas to remove sesame rather than declare it, but if your product contains sesame at any level via an ingredient or processing aid, declaration is required.
- Review advisory statements ("may contain") for accuracy. FDA does not require precautionary allergen labeling (PAL), but if you use it, it must be truthful and not used as a substitute for proper allergen controls. Overuse of PAL statements has drawn FDA scrutiny. Only use it when a documented shared-equipment or shared-facility risk exists.
- Verify label version against current formula version. If your formula has been revised since the last label approval, confirm the label was updated accordingly. Mismatched version numbers between your formula and label specification documents are a red flag.
If you want to see how a professional allergen review documents these findings — including how flagged items are annotated for QA teams — the RecallGuard annotated sample report shows the format and detail level used in a real SKU review.
Phase 3: Supplier Documentation
Your label is only as accurate as your supplier data. This phase often reveals the most critical gaps because it depends on third parties outside your direct control.
- Collect current allergen declarations from every ingredient supplier. "Current" means within the past 12 months, or following any supplier reformulation notification.
- Request finished product allergen statements, not just raw material specs. A seasoning supplier's finished allergen statement covers the blend as manufactured — raw material specs for individual components may not capture cross-contact risk from their facility.
- Confirm suppliers notify you of formula or supplier changes. This should be a contractual requirement. Document it in your supplier agreements and verify it's an active practice, not just a clause no one enforces.
- Flag any ingredient sourced from a supplier you haven't audited or received updated documentation from. If you don't have a current spec, treat the allergen status as unconfirmed until you do.
- Document country of origin for high-risk ingredients. Allergen labeling requirements and thresholds vary internationally. If you're sourcing ingredients processed outside the U.S., confirm that your supplier's allergen testing and declaration standards align with FDA requirements, not just their local regulatory framework.
Phase 4: Production and Changeover Controls
Label and formula compliance can be airtight and still fail at the production level. These checks bridge the gap between documentation and execution.
- Confirm allergen scheduling and changeover procedures are documented. Shared equipment lines must have validated cleaning procedures and a defined production sequence that minimizes cross-contact risk.
- Verify lot-level ingredient traceability. In a recall scenario, you need to identify every lot that used a specific ingredient. If your ERP or batch records don't capture this, you're operating blind.
- Check that your product label matches what's actually being filled. Line changeovers where labels aren't swapped are a documented source of recalls — product in a box labeled for a different SKU with different allergens.
- Confirm finished product allergen testing protocol, if applicable. For high-risk products or those using shared equipment, a pre-launch finished product test against your declared allergen profile adds a final verification layer.
Integrating This Into Your Pre-Launch Process
This checklist works best when it's a formal gate in your product launch workflow — not an informal review someone does from memory the week before production. Assign ownership for each phase (QA, R&D, procurement), set a deadline for completion relative to the production date, and require sign-off documentation before label approval is finalized.
For teams that want a structured external review as part of their pre-launch process, a RecallGuard Single SKU Review ($349) covers allergen declarations, label/formula cross-checks, regulatory claim review, and supplier documentation gaps — with a written report your team can act on. It's designed to fit between label finalization and production approval without adding weeks to your timeline.
To understand how the review process works before committing, watch the 85-second walkthrough — it covers the submission process, what gets reviewed, and what the report output looks like.
The Takeaway
Allergen compliance failures are almost always traceable to a specific gap: a spec that wasn't updated, a label that wasn't compared against the formula, a supplier change that wasn't communicated. None of these are unpreventable. A disciplined pre-launch review — covering formula, label, supplier documentation, and production controls — catches them before they become enforcement actions or recalls. Build the checklist into your standard operating procedure, assign accountability for each phase, and treat pre-launch review as a non-negotiable step rather than a best-effort task.