Custom Allergen Menu Cards Guide

A customer-facing allergen menu card maps every dish on your menu to each declared allergen, so guests with allergies can order with confidence and staff can answer questions consistently. Done well, it builds trust, speeds up service and reduces incident risk. Done badly — vague, out of date, or over-promising — it becomes a legal liability. The difference is in the design and the update discipline. This guide walks through how to design allergen menu cards that work: the principles that keep them accurate, the wording that manages cross-contact honestly, and the version control that stops an old card outliving a recipe change. Why a Customer-Facing Card Matters Guests with food allergies often feel anxious eating out, and rightly so — a single mistake can be serious or fatal. A clear allergen card signals that your venue takes allergies seriously, reduces repetitive questions during service, and gives your team a shared reference so two servers never give conflicting answers. It also supports your due-diligence position by showing you have a structured system for communicating allergen information. Design Principles for an Effective Card Follow these principles when building the card: Use the menu's exact dish names so guests can match the card to what they are ordering without ambiguity. Map every dish to each declared allergen using a simple, consistent code such as Yes, No, or On Request (for dishes that can be modified). State cross-contact risk explicitly rather than implying absolute safety — shared fryers, grills and preparation surfaces matter. Add a kitchen-environment footnote making clear that the kitchen handles allergens and traces cannot be fully guaranteed. Date and version the card so both staff and guests can confirm it is current. How should you word cross-contact honestly? Avoid absolute claims like "allergen-free". Instead, describe the control and its limits, for example: "This dish is prepared without peanuts, but our kitchen handles peanuts and we cannot guarantee the absence of traces." Honest wording protects the customer and your business. Which Allergens Should the Card Cover? Cover the allergens required to be declared in Australia under Plain English Allergen Labelling, set out in FSANZ Standard 1.2.3 . These include gluten (from wheat, rye, barley and oats), crustacea, molluscs, egg, fish, milk, peanuts, tree nuts, sesame, soy, lupin and added sulphites. Use the same plain-English terms on the card that you use elsewhere, so nothing is lost in translation. The Update Workflow The single biggest risk with allergen cards is a stale card outliving a recipe change. Prevent it with a fixed workflow: Treat every menu or recipe change as an allergen review trigger. Re-derive the allergen mapping from the updated recipe and supplier specifications. Increment the version number and date on the card. Replace all printed and digital copies at once, and destroy superseded versions. Record who approved the change and when. Building this into your menu launch checklist means the card can never quietly fall behind the kitchen. Train Front-of-House to Use It The card is only as good as the person using it. Servers need to know how to walk a guest through the card, when to escalate to the chef, and how to confirm a specific order against the kitchen-side allergen matrix before it is served. Reinforce that "I think so" is never an acceptable answer — if there is any doubt, they check. Print, Digital or Both? You have three practical formats, and many venues use a combination: Printed cards are reliable, need no device, and work anywhere in the venue — but they must be reprinted and re-distributed on every change. Digital cards (a QR code to a hosted allergen menu) update instantly and can never be "the old version" if managed centrally, but they depend on a customer's phone and connectivity. A hybrid keeps a printed card at the pass for staff and offers a QR-linked digital version for guests, so both audiences are covered. Whichever you choose, the source of truth should be a single allergen matrix. When the matrix changes, both the print and digital outputs should regenerate from it, so they can never disagree. Accessibility and Readability An allergen card that guests cannot read defeats its purpose. Use a clear, reasonably large type size, strong contrast, and a simple grid rather than dense prose. Avoid relying on colour alone to convey meaning — pair colours with text or symbols so the card works for colour-blind readers. Keep the layout consistent from version to version so regular guests know where to look. If your venue serves a multilingual community, consider a translated version of the key allergen terms. What to Avoid on an Allergen Card Certain choices turn a helpful card into a liability: Absolute "free from" claims you cannot guarantee in a shared kitchen. Vague dish descriptions that do not match the menu, leaving guests unsure which row applies. No version or date , so staff cannot tell whether the card is current. Burying cross-contact information in fine print where anxious guests will miss it. Leaving old cards in circulation after a menu change. Honesty and clarity protect both the customer and the business far better than reassuring but unverifiable promises. Connecting the Card to Your Wider Allergen System A customer-facing card should never stand alone. It is the visible tip of an allergen management system that also includes a full dish-by-dish allergen matrix, kitchen-side reference cards, ingredient and supplier specifications, and trained staff. When these elements are connected — ideally all drawing from a single source of truth — a change made once flows through to every output, and nothing drifts out of sync. When they are managed separately, it is easy for the printed card to say one thing while the kitchen matrix says another, which is precisely the gap that leads to an incident. Review the whole chain on a regular cycle, not just when some