Allergen Management & PEAL Compliance

Why Allergens Are the Highest-Stakes Hazard in Hospitality A microbiological hazard might make a customer ill for a week. An allergen hazard can kill them in fifteen minutes. That asymmetry is why allergen management has moved from a side-of-desk task to a board-level compliance priority across Australian hospitality. According to the National Allergy Council, around one in ten Australian infants and about two in every hundred adults live with diagnosed food allergy, and the rate of presentations to emergency departments for food-related anaphylaxis has more than tripled in two decades. Australian regulators have responded by significantly raising the bar. The Plain English Allergen Labelling (PEAL) reforms under FSANZ Standard 1.2.3 — phased in from 25 February 2024, with a full transition deadline of 25 February 2026 — are the most significant change to Australian food labelling in a generation. They affect every packaged food sold in Australia, and they reframe the entire conversation about how hospitality venues describe and protect against allergens. This guide is the operator-level pillar reference for allergen management in Australia. It complements our PEAL allergen management feature and our category page on food safety topics . The 24 Declarable Allergens in Australia The PEAL reforms were issued by FSANZ following stakeholder consultation and align with allergen-management practices recommended by the Australian Department of Health and Aged Care and consumer-facing guidance from the NSW Food Authority . Operators should treat the PEAL list as the minimum legal baseline, not a ceiling — best-practice menus also flag culturally significant allergens (e.g. coconut for some communities) where relevant. Standard 1.2.3 lists the substances that must be declared whenever they are present as ingredients, processing aids, or are present through cross-contact above a defined threshold. As of the PEAL reforms the list comprises: Cereals containing gluten: wheat, rye, barley, oats, spelt, and their hybridised strains, declared individually by name (PEAL no longer permits the combined "gluten" declaration alone). Crustaceans: declared as "crustacean." Eggs. Fish. Milk. Peanuts. Soybeans. Tree nuts: almond, Brazil nut, cashew, hazelnut, macadamia, pecan, pine nut, pistachio, walnut — declared individually under PEAL. Sesame seeds. Lupin. Molluscs. Sulphites in concentrations of 10 mg/kg or more. Added sulphur dioxide in concentrations of 10 mg/kg or more. The expansion to require individual tree nuts and individual gluten-containing cereals — rather than collective categories — is the change that has caught most hospitality operators by surprise. A label that simply says "contains nuts" no longer satisfies PEAL when applied to a packaged product, and a customer-facing menu that says "may contain gluten" is no longer aligned with how packaged food is described in the same supply chain. Standard 1.2.3 and the PEAL Transition Plain English Allergen Labelling came into force on 25 February 2024. From that date, all newly manufactured packaged food in Australia and New Zealand had to comply. Existing stock manufactured before the date was given a two-year transition window, ending 25 February 2026. From that point, every packaged food on the shelf must comply. What PEAL requires Mandatory bold declaration in the ingredients statement. Each allergen must be bolded where it first appears, using a defined font and contrast. A separate "Contains" statement immediately after the ingredient list, summarising allergens present. Specific names rather than collective categories. "Wheat," "rye," "almond," "cashew" — not "gluten" or "tree nuts" alone. Cross-reference between processing aids and allergens. Allergens used as processing aids are declared in the same way as ingredients. Consistent terminology across the label. No variation between ingredients list, contains statement, and front-of-pack callouts. What PEAL implies for hospitality PEAL is technically a packaged-food rule, but its impact ripples through hospitality in three ways: Your supply chain is changing. Suppliers are reformulating, relabelling, and updating product specifications. Allergen statements on a sheet of paper from 2022 may no longer match the product in the box. Verifying allergen information at receipt has become a frontline control, not a back-office formality. Customer expectations are changing. Customers used to plain-English packaged labels expect the same clarity from menus, ordering apps, and verbal descriptions. Regulators are scrutinising consistency. If your supplier declares "wheat, rye, oats" on the can, and your menu says "gluten," and your verbal description to a customer says "no nuts" without reference to gluten — you are creating an inconsistency a regulator can use against you. Cross-Contact vs Cross-Contamination Two terms get used interchangeably in industry but mean very different things in allergen management. Cross-contamination generally refers to the transfer of microbiological pathogens — for example, raw chicken juices contaminating ready-to-eat salad. Cross-contact refers to the transfer of allergenic protein from one food to another. Even microscopic quantities — invisible to the eye, undetectable by smell — can trigger life-threatening anaphylaxis in a sensitised person. Cross-contact occurs through shared utensils, shared cutting boards, shared fryer oil, shared chargrills, airborne flour, splashed batter, and gloved hands that touched a previous allergen. The control measures for cross-contact are stricter than for cross-contamination because the dose required to cause harm is so much smaller. Allergen Matrices and Recipe Management An allergen matrix is the single most important document in your allergen management system. It is a master table of every menu item against every declarable allergen, indicating presence (Y), absence (N), and risk of cross-contact (M for "may be present"). How to build an allergen matrix List every menu item, including specials, modifications, and seasonal changes. For each item, list every ingredient — including processing aids, garnishes, sauces, and oils used for cooking. For each ingredient, document the allergens declared by the supplier on the current product specification. Roll up to the menu item level, marking allergens present and noting any "may be present" risks from shared equipment or shared preparation. Have the FSS sign off the completed matrix before it is used to inform customers. Re-verify whenever a recipe changes, an ingredient changes, a supplier changes, or the supplier issues a new specification. Manual matrices in spreadsheets work for small, stable menus. They fail for any operator with multiple venues, frequent menu changes, multiple suppliers per ingredient, or modified recipes. Digital allergen management tools link recipes to current ingredient specifications, automatically recalculating the allergen profile when an ingredient changes. Receiving and Verifying Ingredients The PEAL transition has created a temporary moment of high risk: supplier specifications written before PEAL may not match newly relabelled products. Verification at receipt is the safety net. For every ingredient delivery, especially for newly delivered batches: Compare the allergen statement on the actual packaging against the supplier specification you hold. If there is any difference, hold the product, contact the supplier, and update your specifications and matrix before using it. Photograph the label as evidence of the allergen statement at the point of receipt. Reject deliveries with damaged or unreadable allergen labelling. Substitutions: The Silent Killer Many of Australia's most damaging allergen incidents have begun with an unrecorded substitution: a chef who ran out of one brand of mayonnaise and used another, an apprentice who finished a tin of stock and opened a different brand, a kitchen porter who refilled a labelled container with a different product. To the kitchen, these substitutions feel routine. To a customer with a peanut or sesame allergy, they can be lethal. Effective substitution control involves three rules: Approved substitutions only. Maintain a list of pre-approved alternatives for every ingredient. If something is not on the list, it is not used. Container labelling discipline. Every decanted container is labelled with product, supplier, batch, and date — and is never refilled with a different product. Sign-off on changes. Any substitution requires an FSS sign-off and a matrix update before it is served. Cleaning Protocols for Allergens Allergen cleaning is not the same as standard cleaning. The objective is removal of allergenic protein, not just visible residue or microbial reduction. Wet wash with detergent and water. Allergenic protein is best removed by mechanical action with a wetting agent. Dry wiping moves protein, it does not remove it. Sanitisers do not eliminate allergens. Chlorine, quaternary ammonium, and alcohol do not denature peanut, milk, egg, or other allergenic protein at the concentrations used in food service. Dedicated equipment for high-risk allergens. Where possible, dedicate boards, knives, gloves, and tongs for nut, sesame, and shellfish handling. Sequence work with allergens last. Schedule allergen-containing preparations at the end of a service or shift, followed by deep cleaning before the next preparation. Validate cleaning effectiveness. ATP swabs do not directly detect allergenic protein, but allergen-specific swabs (ELISA-based) are available for periodic validation of high-risk surfaces. Front of House: Handling Allergen Enquiries Without Guessing Most allergen incidents in hospitality are not failures of cooking — they are failures of communication. A diner asks "is this safe for my peanut allergy?" and is told "I think so" by a staff member who has not checked. The allergen management system in the kitchen is meaningless if it does not extend through the conversation at the table. The front-of-house principles every venue should embed are: Verify, don't guess. Every allergen enquiry triggers a check against the current allergen matrix, not a memory or an assumption. Inform the kitchen. Allergen orders are flagged on the docket and verbally communicated. Kitchens should have a defined visual indicator (a coloured ticket, a sticker, a flag in the POS) that signals an allergen modification. Confirm at the pass and at the table. The plate is verbally confirmed when leaving the kitchen and again when delivered. Document refusals. If you cannot safely accommodate an allergy, say so plainly. A documented refusal is far safer than a hopeful attempt. Use accurate language. "We use peanut oil in our fryer" is fine; "I think we don't" is not. Staff Training and Competency Verification Every food handler should be able to answer four questions reliably: What are the 24 declarable allergens in Australia? How do I look up the allergen profile of a menu item in our system? What do I do if a customer asks about an allergen I cannot confirm? What are the signs of anaphylaxis, and what do I do if they occur? Training should not be a one-off induction. Refresher training every 6 to 12 months is appropriate, and competency should be evidenced — not just attendance. See our food safety training playbook for a structured approach. Anaphylaxis Preparedness Even with the best controls, allergen incidents occur. Every venue should: Have at least one staff member trained in anaphylaxis recognition and EpiPen administration on duty during all service periods. Maintain a documented incident response plan that includes immediate ambulance call, staff communication, isolation of the suspected food, and customer support. Investigate every incident — even those that do not result in anaphylaxis — to identify and close the gap in the allergen system that allowed it to happen. Cooperate fully with the inevitable regulatory investigation, with documentation supporting the truthful narrative of what occurred. Digital Allergen Management The complexity of allergen management — many ingredients, many recipes, frequent changes, individual customer modifications, multiple venues — exceeds what spreadsheet-and-paper systems can manage reliably. Digital allergen management platforms deliver: Single source of truth for allergen status of every ingredient, recipe, and menu item. Automatic recalculation when an ingredient changes. Customer-facing allergen filters for online ordering and digital menus. Sign-off workflows when recipes or specifications are updated. Audit trail of every allergen-related decision. Multi-venue consistency, so a customer ordering the same dish at any branch receives the same allergen information. The Big Allergens: Operator-Level Profiles Each declarable allergen has its own behaviour in a kitchen — its own typical hiding places, its own cross-contact pathways, its own customer profile. Knowing them by name is the difference between an allergen system on paper and an allergen system that protects. Peanut The most public-conscious allergen. Peanut protein is highly stable to heat and survives normal cooking; even invisible amounts can trigger anaphylaxis in sensitised individuals. Hidden sources: satay sauce, peanut oil (refined oil is generally safe but unrefined or "gourmet" oil retains protein), some Asian and African cuisines, granola bars, biscuits made on shared lines. Tree nuts (almond, Brazil, cashew, hazelnut, macadamia, pecan, pine nut, pistachio, walnut) PEAL now requires individual declaration. Allergy is typically nut-specific — a customer allergic to cashew may safely eat almond — but cross-contact between nuts in storage and processing is so common that many venues treat all tree nuts collectively. Hidden sources: pesto (often pine nut), marzipan, frangipane, granola, vegan cheeses, dukkah, baklava. Milk Distinct from lactose intolerance — milk allerg