Packaging staff reviewing allergen label declarations

Manufacturers: Update Allergen Declarations for FDA Edition 5 and PEAL

An allergen declaration is the part of a food label that names every major allergen present in a product, and it has to match current regulator definitions, not last year’s. FDA’s Edition 5 guidance removed coconut from the major allergen list and widened the scope of milk and egg sources, and Canada and Australia have their own distinct rules. If you haven’t audited your SKUs against these changes, that’s the first task on your list this quarter.

TL;DR:

  • Manufacturers must update allergen names and declaration placements to comply with recent FDA, Canadian, and Australian requirements, especially after formulation changes.
  • The Contains statement must immediately follow the ingredient list, using specific allergen names and often requiring bolding and bilingual presentation in some markets.
  • Overuse of voluntary “may contain” warnings without documented cross-contact risk increases audit risks, emphasizing the importance of risk-based precautionary labeling.
  • Threshold-based allergen labeling (ED05) remains a regulatory discussion, so current practices should focus on accurate traceability and risk assessment rather than premature changes.
  • Consistent, thorough label reviews and supplier documentation are key to avoiding common compliance mistakes during audits and label updates across multiple markets.
Space-man
Prepare Your Next Product Run
Space-man supports manufacturers with private labeling, co-packing, and bagging or packaging services for consumer goods in Canada.
Visit Space-man

Table of Contents

What an allergen declaration must include

An allergen declaration isn’t a single fixed format. It’s a requirement that gets satisfied one of two ways: naming the allergen source directly inside the ingredient list, or bundling it into a separate “Contains” statement placed right after the ingredient list. Both approaches are legally equivalent in most jurisdictions, but they aren’t interchangeable in practice, and mixing them up is one of the most common reasons labels get flagged.

If an ingredient’s common name already identifies the allergen source clearly (say, “milk” or “peanut butter”), you don’t need a separate Contains statement for that item. But if an ingredient uses a technical or generic term that hides the allergen source (like “casein” for milk, or “lecithin” that could come from soy), you either have to rename it in the ingredient list to reveal the source, or declare it in a Contains statement. Most manufacturers choose the Contains statement because it’s cleaner and easier for shoppers scanning a label in a hurry.

Naming conventions get specific fast. Regulators don’t just want “tree nuts,” they often want the species named, and the same goes for milk and eggs now that FDA’s revised definitions expand beyond cow’s milk and chicken eggs to include other ruminants and fowl. Practical naming rules to keep in your back pocket:

  • Name the specific tree nut species (almond, cashew, walnut) rather than the generic category when the formulation calls for it.
  • Use the actual species when milk or egg comes from something other than cow or chicken, such as “goat milk” or “duck eggs.”
  • Spell out fish and crustacean shellfish by species or common type where source ingredients make that identification possible.
  • Keep wheat distinct from other gluten sources since wheat is a declared allergen in most frameworks while other grains may not be.
  • Match whatever terminology the ingredient supplier’s documentation uses, then verify it against the regulator’s accepted name list before printing.

Placement and legibility matter just as much as word choice. A Contains statement has to sit immediately after or below the ingredient list, not buried somewhere else on the panel, and it needs to be printed in a font size and contrast that a shopper can actually read without squinting. Some regulators, as you’ll see in the jurisdictional breakdown below, now require bolding for emphasis. Even where bolding isn’t mandated, it’s worth doing anyway, because a label that’s technically compliant but practically unreadable still generates complaints and, eventually, regulatory attention.

One detail that trips up co-packers and private label clients alike: when a product is reformulated, even slightly, the allergen declaration has to be re-verified from scratch. Swapping a supplier for a thickener or emulsifier can quietly introduce a new allergen source, and if the label isn’t updated, that’s a mislabeling problem, not a packaging one. We’ve found that this single oversight is behind a large share of avoidable allergen label corrections. For a deeper walk-through of how the ingredient list and Contains statement options actually work, our Big 9 naming guide covers the mechanics in more detail.

How US, Canadian, and Australian rules differ

If you sell across borders, you’re not dealing with one allergen framework. You’re dealing with several, and they don’t always agree on what counts as an allergen, how to name it, or where it has to appear.

In the United States, the baseline is the Food Allergen Labeling and Consumer Protection Act (FALCPA), later expanded by the FASTER Act to add sesame as a ninth major allergen alongside milk, eggs, fish, crustacean shellfish, tree nuts, peanuts, wheat, and soybeans. On January 6, 2025, FDA published a revised Edition 5 of its Food Allergen Q&A guidance, and this is the update manufacturers need to be checking their labels against right now. The revision removed coconut from the major allergen list, meaning coconut-containing products no longer need the “tree nut” declaration solely because of coconut. It expanded the interpretation of milk and egg to cover other mammal and fowl sources beyond cow and chicken. The Federal Register notice walks through FDA’s rationale and situates the change within the existing FALCPA and FASTER Act framework.

In Canada, Health Canada and the Canadian Food Inspection Agency require declaration of priority food allergens either directly in the ingredient list or in a Contains statement, and the list recognizes 11 priority allergen groups. Canada also requires added sulphites to be declared once they reach 10 parts per million or more, a threshold that catches manufacturers who assume sulphites only matter in wine or dried fruit. Two features of the Canadian system catch newcomers off guard: prescribed source names are mandatory (you can’t just write “natural flavor” if that flavor derives from a priority allergen), and most packaged foods require bilingual English and French labeling with identical content and prominence in both languages. A Contains statement that’s complete in English but missing an allergen in French isn’t a translation slip, it’s a compliance failure.

In Australia and New Zealand, the Plain English Allergen Labelling framework, known as PEAL, took a different approach entirely. Rather than leaving manufacturers to choose their own wording, Food Standards Australia New Zealand now mandates specific required names for each allergen, bold type for the declaration, and a summary Contains statement co-located with the ingredient list. Packaged products manufactured after February 25, 2024 had to comply, and the framework marked its one-year implementation milestone in early 2025, giving regulators a real-world dataset on uptake and remaining gaps.

A quick note on the EU and other markets: the European Union operates its own 14-allergen framework that includes items like celery, mustard, and lupin alongside the more globally recognized allergens, and individual member states layer on their own labeling nuances on top of the shared EU baseline. If you’re shipping into Europe, a useful starting point for understanding how that 14-allergen list plays out in a real consumer context is this breakdown of allergens to check on takeout menus, which illustrates how granular the expectations can get at the point of sale.

One stat worth sitting with: Canada’s rule requiring sulphite declaration at 10 parts per million or more is a lower bar than many manufacturers assume, and it’s a common miss for products that use sulphite-based preservatives in trace amounts rather than as a headline ingredient.

The practical takeaway: a label built for the US market is not automatically compliant in Canada or Australia, even if every allergen source is technically declared somewhere on the pack. Naming conventions, placement rules, and formatting requirements all shift, and a single multi-market label almost never works without jurisdiction-specific review. Our overview of how these rules compare across major markets is a useful reference point if you’re managing labels for more than one country at once.

How US, Canadian, and Australian rules differ — overview diagram

When should you use a “may contain” warning?

Precautionary allergen labeling, the “may contain” statement you see on cross-contamination risk products, is voluntary in most jurisdictions, which surprises a lot of manufacturers who assume it’s a legal requirement the same way the Contains statement often is. Voluntary doesn’t mean optional in the sense of “skip it if convenient,” though. It means you have to justify it with actual process data, not habit or legal caution.

The problem regulators flag again and again is overuse. If every product in your line carries a “may contain tree nuts” warning regardless of actual cross-contact risk, that pattern reads to an inspector as a shortcut around proper allergen control, not as an abundance of caution. FDA’s consumer guidance on reading allergen labels points to exactly this concern: precautionary statements shouldn’t substitute for a real allergen control program that includes dedicated equipment, scheduling, and validated cleaning between allergen-containing and allergen-free runs.

Pro Tip: Before adding a “may contain” statement, document the specific cross-contact pathway it addresses. If you can’t point to a shared line, shared equipment, or a supplier-level risk, you probably shouldn’t be using the statement at all.

Good PAL practice follows a short set of principles:

  • Use precautionary language only when a documented cross-contact risk exists, not as a default disclaimer across your whole catalog.
  • Keep the wording specific to the allergen actually at risk rather than a blanket “may contain allergens” statement that tells shoppers nothing useful.
  • Tie every PAL instance to a validated risk assessment or cleaning verification record you can produce on request.
  • Review PAL usage whenever you change suppliers, lines, or production scheduling, since the underlying risk can shift even if the formula doesn’t.

The inspection risk here is real. An unjustified or overly broad precautionary statement can prompt a deeper audit of your entire allergen control program, not just the label itself, because inspectors reasonably treat it as a signal that your facility is managing allergen risk through labeling rather than through process controls. That’s a much bigger conversation to have with a regulator than a simple label correction.

Threshold-based labeling and what ED05 means for you

A newer concept circulating in allergen regulation discussions is threshold-based labeling, often referenced by the shorthand ED05, which stands for the “eliciting dose” that would trigger a reaction in 5% of the allergic population for a given allergen. The idea behind it is to move precautionary labeling away from a blanket “may contain” approach and toward thresholds grounded in dose-response data, so that trace amounts genuinely unlikely to cause reactions in most allergic consumers wouldn’t require the same warning as amounts that pose a real risk.

This is a live discussion in food safety circles, not a settled rule. Industry coverage, including analysis from outlets like Quality Assurance & Food Safety, has tracked growing interest in threshold-based approaches as a way to make precautionary labeling more meaningful and less of a blanket liability shield, but no major regulator has adopted binding, universal thresholds for allergen labeling at this point. The conversation remains at the level of scientific debate, pilot proposals, and industry working groups rather than enforceable regulation.

What should you actually do with this information today? Mostly, watch and prepare rather than act. A few sensible steps:

  • Keep an eye on regulatory consultations in your core markets, since threshold frameworks could shift PAL expectations once adopted.
  • Improve your own traceability and testing data now, since any future threshold system will depend on manufacturers having reliable contamination data to work from.
  • Avoid loosening your current precautionary labeling practices based on threshold discussions alone, since nothing in the current regulatory landscape allows you to rely on an unadopted standard.
  • Treat threshold monitoring as a standing agenda item in your quality team’s regulatory review cycle rather than a one-time check.

The short version: ED05 is worth understanding and worth tracking, but it’s not yet a basis for changing how you label a product. Good manufacturing practice and documented risk assessment remain the foundation regulators expect, regardless of where the threshold conversation eventually lands.

Formatting rules, language requirements, and exceptions

Beyond naming and placement, a handful of formatting and special-case rules determine whether a technically correct declaration actually passes review.

  1. Bolding and co-located summaries. Australia and New Zealand’s PEAL framework requires bold type for allergen declarations along with a summary Contains statement positioned next to the ingredient list, a stricter visual standard than many manufacturers are used to from other markets.
  2. Bilingual identical content. Canada’s requirement that English and French declarations carry identical content and prominence means a shortened or reworded French Contains statement, even one that technically lists the same allergens, can still fail review if it isn’t a true mirror of the English version.
  3. Component exemptions and parenthetical declarations. Some minor or incidental ingredients that don’t carry the allergen into the final product in a meaningful way may qualify for exemptions, and where a compound ingredient contains an allergen, a parenthetical declaration right after the ingredient name, such as “natural flavor (contains milk),” is often the cleanest way to handle it without restructuring the whole ingredient list.
  4. Single-ingredient foods. Products with only one ingredient, like raw almonds or plain honey, generally still need the allergen named, but the declaration can often live in the product name itself rather than requiring a separate statement.
  5. Standardized alcoholic beverages. Beer, wine, and spirits frequently fall under separate labeling authorities rather than general food labeling rules, which means allergen declaration requirements for these products can diverge sharply from packaged food norms, and checking the specific beverage authority’s rules is worth doing before assuming general food rules apply.

These formatting details sound minor individually, but they’re where labels fail prepress review most often. A Contains statement with the right allergens but the wrong font weight, or a bilingual label with mismatched prominence between languages, is a correctable mistake, but only if someone catches it before the print run. Specialty categories like clean-label beverages often face their own formatting scrutiny too. This guide to clean-label coffee products shows how plain-English labeling expectations extend beyond traditional allergen categories into ingredient claims generally, which is a useful parallel if you’re managing a label with both allergen and clean-label considerations.

Your step-by-step label compliance checklist

Updating allergen declarations across a product line isn’t a single afternoon’s work, but it is a manageable process if you treat it as a sequence rather than trying to fix everything at once.

  1. Inventory every SKU and map its current formulation. Pull the full ingredient list for each product and cross-check it against the allergen definitions currently in force in every market you sell into.
  2. Flag labels that need a change. Any product affected by a naming update (like coconut no longer triggering a tree nut declaration under FDA’s revised guidance) or a formulation change involving a new supplier goes on the active list.
  3. Pull supplier documentation before touching the label. Certificates of analysis, ingredient specifications, and current supplier attestations need to confirm the allergen status of every component, and these documents should be versioned so you can show which COA was current at the time a label was approved.
  4. Route label art through formal prepress approval. Every allergen-related change needs a second set of eyes checking placement, bolding, naming, and bilingual accuracy before it goes to print, not after.
  5. Decide on your transition mechanism. Sticker corrections can work for minor naming fixes on existing inventory, but a reformulation affecting allergen content usually calls for a full reprint and a planned sell-through of old packaging rather than stickering over a substantive change.
  6. Set a realistic timeline and communicate it internally. Regulatory transition periods, like the sell-through windows regulators sometimes allow after a rule change, give you room to plan reprints around existing inventory instead of scrapping stock.
  7. File everything in a permanent compliance record. Sanitation validation records, allergen testing results, and the full approval trail for each label version need to live somewhere auditable, not in someone’s inbox.

Pro Tip: Build a standing calendar reminder tied to major regulatory review cycles (FDA guidance updates, Health Canada bulletins, FSANZ proposal milestones) so label audits happen on a schedule rather than only after a problem surfaces.

Health Canada’s industry guidance on ingredient and allergen lists is a useful reference for exactly this kind of checklist discipline, since it lays out the order, naming, and placement expectations in detail. If you want a more granular walk-through built specifically around the FDA Edition 5 update, our 60 to 90 day update checklist breaks the process down into a concrete timeline, and our federal and state labeling checklist covers the broader compliance picture beyond allergens alone.

What regulators check during an allergen audit

Inspectors don’t usually start an allergen review from scratch. They look for specific mismatches and patterns that experience has taught them correlate with bigger underlying problems.

The most common trigger is a straightforward mismatch between the ingredient list and the Contains statement, where an allergen named in one doesn’t appear in the other. This happens more often than it should, usually because a formulation changed and someone updated the ingredient list but forgot the Contains statement sits on a separate part of the artwork file. Another frequent trigger is a precautionary statement that looks disconnected from any documented risk, which as covered earlier can prompt a broader look at your allergen control program rather than a simple label note. Inconsistent or missing supplier evidence, where your label claims a formulation that your own supplier documentation doesn’t quite support, rounds out the list of common red flags.

A compliance folder that holds up under scrutiny generally includes:

  • A complete label version history showing every allergen-related change and when it took effect.
  • Current supplier certificates of analysis and specifications for every allergen-relevant ingredient.
  • Sanitation and cleaning validation logs for lines that run both allergen-containing and allergen-free products.
  • Corrective action records for any past label nonconformance, including how it was identified and resolved.

When a mismatch does surface, speed and documentation matter more than perfection. Minor naming corrections on products already in market can often be handled with approved stickers while a permanent reprint is scheduled. A genuine allergen omission, where a present allergen isn’t declared anywhere on the label, is a more serious matter that may require pulling inventory or, in severe cases, a recall, and it should be communicated to the relevant regulatory body promptly rather than quietly fixed on the next print run. Regulators generally respond more favorably to manufacturers who self-report and show a documented correction plan than to ones who wait to be caught.

What co-packing taught us about label changes

We manufacture and distribute freeze dried treats and also run private label and co-packing services for other consumer goods manufacturers. That combination puts us on both sides of the allergen label problem: we manage our own product labels, and we also handle packaging and labeling for brands that bring us their formulations and expect the finished package to be compliant on day one.

What that work has reinforced is that allergen label errors almost never come from ignorance of the rules. They come from timing gaps: a formulation change that happens faster than the label update, or a supplier swap that nobody flags as allergen-relevant because the new ingredient looks functionally identical on paper. Running co-packing and private label programs means we see this pattern across many different product types, not just our own candy lines, and it’s part of why we treat prepress review as a mandatory checkpoint rather than a formality.

Our prepress process checks allergen naming, Contains statement placement, and formatting consistency before any client label goes to print, because catching an error there costs a file revision, while catching it after printing costs the whole run. If you want to see the specific checks we run through on every label, our five-point prepress checklist walks through exactly what we look for before anything goes to press, and it’s informed directly by the kinds of allergen mismatches covered earlier in this guide.

Where allergen labeling rules are headed next

Our honest read on where this is going: plain-English labeling is winning. FSANZ’s PEAL framework and FDA’s steady march toward clearer, more specific allergen naming both point toward regulators losing patience with vague or technical ingredient terms that hide allergen sources from an ordinary shopper. If you’re still relying on generic terms that require a Contains statement to decode, expect that gap to keep narrowing.

Threshold-based labeling, the ED05 conversation, is worth watching closely but not worth acting on yet. The gap between “actively discussed in industry forums” and “binding regulatory requirement” is still wide, and manufacturers who jump ahead by loosening precautionary labeling based on threshold logic alone are taking on risk the regulatory framework doesn’t yet support. The better use of that energy is improving your own traceability and running genuine dose-response style risk assessments internally, so you’re ready whenever a threshold standard does arrive.

Our recommendation is simple: put label audits and supplier re-verification on a recurring schedule rather than treating them as a reaction to the next guidance document. Regulatory change in this space has been frequent enough in the last two years that waiting for the next update to force a scramble isn’t a sustainable posture.

— Chadi

How we support compliant labels for manufacturers and private label brands

If auditing and reprinting labels across a full product line sounds like more operational weight than your team wants to carry alone, that’s exactly the gap our private label and co-packing services are built to close. We handle dry food co-packing, pouch packaging, commercial freeze drying, confectionery and chocolate production, private label, and broader food manufacturing for brands that want their allergen declarations checked by a team that runs this process daily, not occasionally.

Space-man

Every label produced for a client goes through the same prepress review as applied to freeze dried candy and treat lines, checking allergen naming, placement, and formatting before anything goes to print. If you’re evaluating a co-packer or private label partner and want to see what finished products look like coming out of a facility, the freeze dried candy and treats collection is a good starting point, and if you’re ready to talk through a label audit or a private label quote, reach out through the co-packing and packaging services page to get the conversation started.

FAQ

How do I write an effective allergen disclaimer?

An effective allergen disclaimer names the specific allergen source using the prescribed terms your regulator requires, placed either in the ingredient list or in a dedicated Contains statement immediately following it. Avoid vague terms like “may contain allergens” without specifying which one, and only include a precautionary statement when a documented cross-contact risk actually exists, as outlined in FDA’s consumer guidance.

What allergens must be declared under major frameworks?

In the United States, the major allergens are milk, eggs, fish, crustacean shellfish, tree nuts, peanuts, wheat, soybeans, and sesame, with FDA’s Edition 5 guidance removing coconut from the tree nut category and expanding milk and egg source definitions. Canada recognizes 11 priority allergen groups plus added sulphites at 10 parts per million or more, while the EU uses a separate 14-allergen framework, so the exact list depends entirely on which market the product is sold in.

What does an allergen statement on a menu typically look like?

A menu-based allergen disclaimer typically identifies which dishes contain or may contain specific named allergens, often using a footnote or symbol system tied to a short list at the bottom of the menu, with wording like “contains peanuts” or “prepared in a kitchen that also handles shellfish.” The exact format varies by jurisdiction and isn’t standardized the way packaged food labels are, so restaurants generally follow local food safety authority guidance rather than a single universal template.

What is the required format for a packaged food allergen declaration?

The required format depends on the regulator: a Contains statement must appear directly after the ingredient list, and frameworks like Australia and New Zealand’s PEAL additionally require bold type and specific required allergen names rather than generic terms. Canada adds a bilingual requirement where English and French declarations must carry identical content and prominence, so a format that passes review in one market may still need adjustment for another.

Does Space-Man help manufacturers update allergen labels during production?

Our private label and co-packing services include prepress label review as a standard part of production, checking allergen naming, placement, and formatting before any label goes to print. Pricing for these services is available on request through our co-packing and packaging services page.

Sources

Retour au blog

Laisser un commentaire

Veuillez noter que les commentaires doivent être approuvés avant d'être publiés.