Food Allergen Management in Australian Hospitality Venues

A useful allergen-management system connects five things: current supplier information, controlled recipes, cross-contact controls, clear communication with the customer, and a defined escalation process when staff are unsure. An allergen matrix can support that system, but it cannot replace ingredient labels, supplier evidence, trained staff or a truthful conversation about what the venue can and cannot control.

For a small café, restaurant or food truck, the goal is not a complicated compliance folder. It is a dependable process that works when a supplier substitutes a product, a special changes during service or a customer asks a question at the busiest point of the shift.

Start with the requirements that apply to your venue

Food allergen requirements sit within the Australia New Zealand Food Standards Code, but the way a food business is supervised can also depend on its state or territory, local council, food-safety program and operating model. Food Standards Australia New Zealand (FSANZ) lists the allergens that must be declared and explains the required names used in allergen information.

For food sold from a café, restaurant or takeaway without a label, allergen information must generally be displayed with the food or provided to the customer on request. That does not mean a team can guess, rely on memory or answer with “it should be fine”. The venue needs current information and a method for finding it before accepting the order.

Before designing the system, confirm:

• which authority regulates the venue and whether a documented food-safety program applies;
• which menu channels are used, including printed menus, boards, QR menus, delivery platforms and phone orders;
• which ingredients arrive prepacked, which are decanted and which are prepared on site;
• where substitutions, specials and supplier changes occur; and
• who is authorised to answer an allergen question or decline an order when reliable information is unavailable.

Record the authority, source links and date checked in the venue's food-safety records. Requirements and supplier products can change.

Assign responsibilities before writing the matrix

Allergen safety fails when everyone is expected to help but nobody owns the source information. Assign the work by role.

In a two-person business, one person may hold several roles. The responsibility still needs to be explicit. “Ask the chef” is not sufficient if the chef does not have the current supplier label or if the question concerns cross-contact at the coffee station.

Build a controlled ingredient source

The matrix is only as reliable as the information beneath it. Start with the products actually used, not a remembered shopping list.

Create an approved-product register

For each purchased ingredient, record:

• product and brand name;
• supplier and supplier item code where available;
• pack size or identifying detail;
• current ingredient and allergen information source;
• date reviewed;
• menu items or recipes that use it; and
• who approved it.

Retain a readable label image or current specification where appropriate. When products are decanted, keep the link between the storage container and the original product. A container labelled only “sauce” is not a reliable source for a customer question.

Control substitutions

A different brand, pack size or “equivalent” product may have different ingredients or precautionary statements. Set a rule that a substitution cannot enter production until an authorised person has checked its label, updated affected recipe information and told the shift team what changed.

If the information cannot be verified, isolate the substitute from use for allergen-sensitive orders. This is a service and purchasing decision, not something to resolve by reassurance at the table.

Include every component

Review sauces, spice mixes, stocks, marinades, dressings, garnishes, fryer products, drink powders and finishing oils—not just the ingredient named on the menu. Check optional sides and common modifications as well. A dish record that covers the main component but omits its garnish or shared sauce leaves a gap exactly where service changes happen.

Build an allergen matrix staff can use

Use the current allergens and required names in FSANZ guidance as the basis for the columns. Use menu items or controlled recipes as the rows. A simple status system can distinguish:

• contains—the controlled recipe includes the allergen;
• does not contain as an ingredient—the current recipe does not include it, but cross-contact still needs assessment;
• uncertain—information is missing, contradictory or under review; and
• not applicable—used only where the field genuinely does not apply.

Do not treat a blank cell as “no”. A blank is an unresolved record.

Add document-control fields such as recipe version, product version, review date and reviewer. If the matrix is printed, show its version and withdrawal process so an old copy does not stay beside the till after a supplier change.

Test the matrix against real questions

Choose several common orders and follow the information from the customer-facing menu through the recipe and every purchased component. Then test changes:

1. What happens if the regular bread is unavailable?
2. Who updates the matrix when the mayonnaise changes?
3. Can a casual employee find the current information during service?
4. Does the order ticket clearly carry the allergen question to the person preparing the food?
5. What happens if the kitchen cannot control cross-contact for that order?

If the answer relies on one person's memory, the system is not yet ready.

Assess and control cross-contact

Ingredient information and cross-contact are related but different. A recipe may not intentionally contain an allergen while the preparation environment creates a cross-contact risk.

Map the practical routes in your venue:

• shared fryers, grills, toasters, blenders or coffee equipment;
• utensils, chopping boards, cloths and storage containers;
• open ingredient bins and flour or powder movement;
• hands, gloves and aprons moving between tasks;
• splash, crumbs or garnish at the pass; and
• food held or transported together in a truck or small kitchen.

For each meaningful risk, decide whether the venue can separate, clean, schedule or otherwise control the task. Write the method in the relevant procedure, train it and observe it in practice. Do not promise an allergen-free environment unless that claim is accurate and supportable for the venue.

Where a requested control cannot be achieved consistently, the escalation rule may require the manager to explain the limitation and decline to represent the item as suitable. A calm, honest boundary is safer than an improvised promise.

Use one customer-to-kitchen communication sequence

Staff need wording and actions that work under pressure. A practical sequence is:

1. Listen and clarify. Ask which allergen or ingredient the customer needs information about. Do not ask the customer to describe the severity as a way to reduce the venue's care.
2. Pause the order if needed. Tell the customer you will check current information.
3. Use the controlled source. Check the current recipe, product information and cross-contact procedure. Do not rely on a previous version or a colleague's recollection.
4. Escalate uncertainty. Refer the question to the authorised manager or kitchen lead. If reliable information is unavailable, say so plainly.
5. Explain limitations accurately. Describe what the venue knows and what it can control. Avoid guarantees.
6. Mark and repeat back the order. Use the venue's agreed POS, docket or verbal call method, then obtain kitchen acknowledgement.
7. Control preparation and handoff. Follow the documented preparation method and identify the finished order through to the correct customer.

Online orders need the same discipline. A free-text note on a delivery platform can arrive late or be overlooked. Decide whether those orders must be paused and confirmed, and what happens when the customer cannot be contacted.

Respond to uncertainty or an allergen incident

If a team member notices a possible mismatch before service, stop the affected order. Isolate it, recheck the source information and only restart when the authorised person confirms the next step. Do not remove a garnish and assume the remaining dish is unaffected.

If a customer may be experiencing a medical emergency, follow the venue's emergency procedure and call Triple Zero (000) when emergency assistance is needed. Staff should act within their training. Preserve relevant information—including the order, time, recipe version, product labels and staff involved—without delaying care.

After the immediate response:

• notify the responsible manager;
• record facts rather than assumptions;
• isolate relevant ingredients or equipment if ongoing risk is possible;
• check whether the food regulator, insurer or another authority must be contacted;
• review the communication and preparation chain; and
• assign corrective actions with owners and due dates.

An incident review is not about finding someone to blame quickly. It is about finding how the system allowed incomplete information, an uncontrolled change or a missed handoff to reach the customer.

Train and verify the team

A signature alone does not show that a person can use the system. Training should include a short explanation, demonstration and observed practice.

Ask the employee to handle scenarios such as:

• locating information for a menu item;
• escalating an uncertain supplier substitution;
• entering and handing over an allergen-related order;
• explaining the venue's cross-contact limitation without making a guarantee; and
• identifying the manager on duty.

Record the topic, date, trainer, employee and result. If the person is not yet confident or accurate, restrict the relevant responsibility, provide further coaching and check again. Refresh training when the menu, process or legal guidance changes, after an incident, and at a frequency suited to the venue's risk and staff turnover.

Worked scenario: a changed burger bun

A café's regular bun is unavailable and the supplier sends another brand. The receiving employee photographs the new label and marks the item “hold for approval”. The kitchen lead finds that the allergen declaration differs from the approved bun.

Before the product is used, the lead updates the purchased-product register, reviews every burger recipe, updates the allergen matrix and briefs the shift. Printed reference copies are replaced. The service lead confirms how affected orders will be marked. If the team cannot update an online menu immediately, the manager applies the venue's temporary communication process or makes the affected item unavailable through that channel.

The useful control is not merely noticing that the brand changed. It is preventing the change from bypassing the recipe, menu, service and customer-information chain.

Common allergen-management mistakes

• Copying a generic matrix without checking the exact products used.
• Treating “does not contain” as a promise that cross-contact cannot occur.
• Allowing substitutions before reviewing the label and affected recipes.
• Omitting garnishes, sauces, drinks and specials.
• Keeping several uncontrolled printed versions.
• Telling staff to ask the kitchen without defining who can decide.
• Recording training attendance without checking practical understanding.
• Making broad “allergen-free” or “safe” claims that the venue cannot support.
• Failing to connect delivery-platform notes with the kitchen handoff.
• Updating the matrix after an incident but not correcting the process that caused it.

Allergen-management implementation checklist

• ☐ Confirm the current requirements and regulator that apply to the venue.
• ☐ Nominate the system owner, kitchen approver and shift escalation role.
• ☐ Create an approved-product register with current source evidence.
• ☐ Link every menu item to a controlled recipe and all components.
• ☐ Build the matrix using current FSANZ allergen names.
• ☐ Mark uncertainty explicitly; never use a blank to mean “no allergen”.
• ☐ Document cross-contact controls and honest service limitations.
• ☐ Create one customer-to-kitchen communication sequence.
• ☐ Control supplier substitutions, specials and menu changes before use.
• ☐ Train staff through scenarios and verify practical understanding.
• ☐ Set review triggers and remove superseded copies.
• ☐ Record incidents, corrective actions, owners and completion.

Take the next useful action

Start with one current menu section. Verify every purchased ingredient, build the matching recipe rows and test one customer question from order to handoff. Fix the gaps before expanding the matrix to the rest of the menu.

The Free Hospitality Checklists collection can help establish the broader habit of assigned operational checks. If you want editable registers and training tools for this task, review the Allergen Management Pack. For the wider document-control context, read What Documents Should a New Venue Have Ready?.

General-information limitation: General operational information only. Confirm the current requirements that apply to your state or territory, council, food-safety program, menu, suppliers, equipment and operating model with the relevant authorities and qualified advisers. A checklist, matrix or template does not by itself make a venue compliant or remove allergen risk.

References and source review

• Allergen labelling, Food Standards Australia New Zealand. Accessed 24 August 2026.
• Allergy information for the food service industry, Food Standards Australia New Zealand. Accessed 24 August 2026.
• Cafés, restaurants and retail outlets, NSW Food Authority. Accessed 24 August 2026. Used as a state implementation example; operators must check their own jurisdiction.

Source review date: 24 August 2026