Handling Allergen Requests from Customers

When a customer tells you they have a food allergy, verify the answer — never guess. Check your allergen matrix or ingredient records for that specific dish, confirm the exact allergen the customer is avoiding, and communicate it clearly from the front counter through to the kitchen and back. If you cannot be sure the meal is safe, it is generally safer to say so and offer an alternative than to risk a reaction. Requirements vary, so confirm your obligations with your state or territory food regulator. Key takeaways: Verify, don't guess: check your allergen matrix or ingredient records for the specific dish before you confirm anything to a customer.. Confirm the exact allergen — 'nuts' could mean peanuts or a specific tree nut, and plant milks like soy and almond are themselves declared allergens.. Communicate the request the whole way through: front counter to kitchen and back, with a repeat-back so it survives the handover.. Guarding against cross-contact (clean equipment, fresh gloves, no shared fryer) matters as much as the recipe itself.. If you genuinely cannot guarantee a dish is safe, it is generally safer and more honest to say so and offer an alternative than to serve and hope.. Clarifying vague allergen terms: Customer says, What to confirm or check. 'Nuts' — Ask whether it's peanuts, a specific tree nut, or both, then check the correct allergen. 'Dairy-free' — Treat as a milk allergy unless the customer says it's a preference. 'Gluten-free' — Covers wheat and other gluten-containing cereals; watch soy sauce, batters and thickeners. Plant-milk swap — Soy, almond and oat milks are themselves declared allergens, so a substitute can create a new hazard. Why a customer allergen request is a safety-critical moment For a customer with a diagnosed food allergy, even a trace of the wrong ingredient can trigger a reaction — from hives and swelling to anaphylaxis, which can be life-threatening. That means an allergen request is not a preference like 'no onion'; it is a food safety instruction that your business needs to get right every time. Under the Australia New Zealand Food Standards Code, businesses selling unpackaged, ready-to-eat food generally must be able to provide accurate allergen information about the declared allergens when a customer asks. Regulators and coronial inquiries in Australia have treated getting this wrong as a serious matter, so treat every request accordingly. The declared allergens under the Code are: peanuts, tree nuts, milk, egg, sesame, fish, crustacea, molluscs, soy, lupin, wheat and other cereals containing gluten, and added sulphites (10 mg/kg or more).. A reaction can come from a hidden ingredient (sauces, marinades, stocks, oils) or from cross-contact during preparation, not just the obvious main ingredient.. 'I think it's fine' is not an acceptable answer — the standard is accurate information, which means checking, not remembering.. Verify, don't guess — the golden rule The single most important habit is to never answer an allergen question from memory or assumption. Recipes change, suppliers change, and the person plating a dish today may not be the person who wrote the recipe. Every allergen answer should be traceable back to a written source: your allergen matrix, ingredient statements from suppliers, or product specifications. If a staff member is asked whether a dish contains an allergen and they are not certain, the correct response is to go and check — not to guess in either direction. Guessing 'yes it has nuts' loses you a sale; guessing 'no it's fine' can hurt someone. Answer from a document, not from memory — pull up the matrix or the recipe card.. If the answer isn't written down anywhere, treat that as a gap to fix, not a reason to improvise.. Reformulations and 'specials' are the highest-risk items because they often aren't in the matrix yet — check the actual ingredients used that day.. When in genuine doubt, the safe default is to tell the customer you can't confirm it's safe.. Checking the allergen matrix the right way An allergen matrix is a grid of your menu items against the declared allergens, showing which allergens each dish contains. It is only useful if it is accurate, current and actually consulted. When you check it, look at the specific dish and the specific allergen the customer named, and remember that a matrix usually reflects the recipe as written — it does not automatically account for a substitution a chef made or a change of supplier. Keep the matrix where front-of-house can reach it during service, and update it whenever a recipe, ingredient or supplier changes. Match the exact menu item, including any add-ons, sides, sauces and garnishes the customer will actually receive.. Check whether the matrix distinguishes between allergens present in the recipe and allergens that may be present through cross-contact ('may contain').. Confirm the matrix is the current version — an out-of-date matrix is worse than none because it gives false confidence.. Cross-check high-risk hidden sources: batters, crumbing, stocks, dressings, thickeners, glazes and cooking oils.. If the matrix and the kitchen disagree, the kitchen's actual ingredients win — then fix the matrix.. Confirm the exact allergen — narrow terms cause errors Vague language is a common cause of allergen incidents. A customer who says 'I'm allergic to nuts' may mean peanuts (a legume), a specific tree nut like cashew, or all of them. Under Plain English Allergen Labelling, the Code names tree nuts individually — almond, Brazil nut, cashew, hazelnut, macadamia, pecan, pine nut, pistachio and walnut — while coconut is not treated as a declared tree nut, so pin down which nut actually matters. 'Dairy-free' may be a milk allergy or a lifestyle choice — treat it as an allergy unless the customer makes clear it isn't. 'Gluten' means wheat, rye, barley, oats and their hybrids. Ask a brief clarifying question so you check the right column and give the right advice. Also remember that some substitutes are themselves allergens: soy, almond and oat milks are all declared allergens, so swapping in a plant milk can introduce a new risk. 'Nuts' — ask whether it's peanuts, a specific tree nut, or both, so you check the correct allergen.. 'Dairy-free' — treat as a milk allergy unless the customer says it's a preference.. 'Gluten-free' — covers wheat and other gluten-containing cereals; watch soy sauce, batters and thickeners.. Substitutes carry their own allergens — a soy or almond milk swap can create a new hazard for a different customer.. Communicating the request from front to back — and back again Most allergen failures happen at a handover, not at the recipe. The order has to travel intact from the customer, to whoever takes it, to the kitchen, to the plate, and back to the right customer. Build in a repeat-back at each handover so nothing is dropped. Flag the order clearly — on the ticket, in the POS, verbally at the pass — so it is visibly different from a normal order. On delivery, confirm which plate is the allergy meal and hand it to the right person rather than leaving it on a shared tray. If a customer at the same table has an allergy, the whole table's handling matters, not just their plate. Flag the allergy on the docket and in the POS, not just verbally.. Repeat the order back to the customer, and have the kitchen repeat it back at the pass.. Physically identify the allergy plate on the way out so it reaches the right person.. Tell the customer honestly what you have and haven't been able to control (for example, a shared fryer).. Guarding against cross-contact during preparation Getting the recipe right is only half the job — an allergen-free recipe can still become unsafe if traces transfer during preparation. Treat an allergen order as a separate build: clean hands, fresh gloves, a clean board and utensils, and a clean pan. Shared equipment is the classic trap — a fryer where crumbed and battered items cook transfers gluten and other allergens to everything cooked in that oil, and a bench dusted with flour can contaminate a 'gluten-free' plate. Store and prepare allergen-free items away from the allergen source, and clean thoroughly between tasks rather than just wiping. Use clean, dedicated equipment and fresh gloves for the allergen build.. Never rely on a shared fryer for an allergen-free order — the oil carries traces.. Prepare allergen orders first, or in a cleaned, separated space, to avoid airborne flour and splash.. 'May contain' is a legitimate, honest answer when you genuinely cannot rule out cross-contact — tell the customer.. When to say no — refusing to serve safely and honestly Sometimes the safest and most professional response is to tell a customer you cannot guarantee a dish is safe for them. This is not a failure — it is exactly what the 'verify, don't guess' rule leads to when you genuinely can't control a risk. If your kitchen can't avoid cross-contact for a severe allergy, if the information isn't available, or if a customer asks for something you can't verify, say so plainly, explain why, and offer an alternative you can stand behind. Being upfront protects the customer and the business far better than serving something and hoping. Never let pressure — a queue, a rush, a persistent customer — push you into confirming something you haven't checked. Be honest about limits: 'We can't guarantee this is free from traces because we use a shared fryer.'. Offer a safe alternative wherever you can rather than simply refusing.. Don't be talked out of a safety call by time pressure or a customer downplaying their allergy.. Record recurring 'we can't serve this safely' situations — they often point to a fixable gap in your setup.. Worked examples: A customer orders a salad and says they're allergic to nuts: Rather than assuming the salad is fine, ask whether it's peanuts, a specific tree nut, or both. Check the exact dish, including the dressing and any garnishes, against your allergen matrix or ingredient records before you confirm anything. If a topping or dressing isn't documented, go and confirm with the kitchen instead of guessing. Switching to a plant milk for a coffee: A customer asks for a dairy-free coffee, so you reach for almond milk. Remember the swap itself introduces a declared allergen, so it could be unsafe for a different customer with a tree-nut allergy. Confirm what the customer is actually avoiding, and keep the substitute in mind when the same jug or equipment is used for other orders. Checklist: Every staff member knows to check, never guess, when asked about an allergen. A current allergen matrix or ingredient records cover every menu item, side, sauce and special. Front-of-house can reach the allergen information during service. Staff ask a clarifying question to confirm the exact allergen (e.g. peanut vs a specific tree nut). Allergy orders are flagged on the docket and in the POS, not just verbally. A repeat-back happens at each handover — customer, order-taker, kitchen, pass. Allergen orders are built with clean equipment, fresh gloves and no shared fryer. The allergy plate is identified and delivered to the correct customer. Staff know it is acceptable — and safer — to say 'we can't guarantee this is safe' and offer an alternative. The matrix is updated whenever a recipe, ingredient, supplier or special changes. Common mistakes: Answering an allergen question from memory or assumption instead of checking a written source. Treating 'dairy-free' or 'gluten-free' as a preference rather than a possible allergy. Not clarifying vague terms like 'nuts', so the wrong allergen is checked. Forgetting that substitutes like soy, almond and oat milk are themselves declared allergens. Getting the recipe right but contaminating the plate through a shared fryer, board or flour-dusted bench. Losing the request at a handover because it wasn't flagged and repeated back. Delivering the allergy plate to the wrong person on a shared tray. Letting a rush or a pushy customer pressure staff into confirming something they haven't verified. Relying on an out-of-date allergen matrix that no longer matches the kitchen.