Allergen Matrix App for Restaurants: A Practical Guide

By Ashley Sykes

Most operators start with a spreadsheet.

They build an allergen table, tick the 14 allergens, print it out, and assume the job is done.

A matrix only works if the person who needs the answer can get it in seconds, during a busy shift, and trust it enough to act on it. That is why searches for allergen matrix app, digital allergen matrix and allergy matrix app are growing. Operators are trying to turn an admin document into something usable.

In the UK, the baseline is clear: you must provide allergen information for both prepacked and non-prepacked food, and the 14 allergens are the legally required set. The question is not whether you need a matrix. It is whether your current one actually works in service.

This guide explains what an allergen matrix really is, how UK requirements shape it, and what an app must do to be reliable across single sites and multi-site groups.

What an “allergen matrix” actually means in practice

An allergen matrix is a structured table that shows which dishes contain which allergens.

Typically:

• Rows = menu items
• Columns = the 14 legally recognised allergens
• Cells = “contains”, “may contain”, or blank

That is the theory.

In practice, it is a living food allergen chart. It needs to reflect:

• Ingredient changes
• Supplier substitutions
• Recipe tweaks
• Seasonal menu rotations
• Modifier selections (add cheese, swap sauce, choose wrap type)

If your matrix only updates when someone remembers to edit a spreadsheet, it is already out of date.

A proper

digital allergen matrix

connects to how dishes are built. It understands ingredients, batches and variants. That is what separates a document from a system.

Paper matrix vs digital matrix: where errors creep in

Most operators start with:

• An Excel file
• A printed allergen folder behind the till
• A PDF on the website
• A “just ask our staff” notice

The risk is not intent. It is drift.

Common failure points:

• Ingredient substitutions - A supplier swaps a sauce. The recipe changes. The matrix does not.
• Menu development - New dishes are launched. The matrix update lags behind marketing.
• Multi-site variation - One site runs a different supplier. Head office matrix says one thing. Reality says another.
• Modifier complexity - “Add halloumi” changes milk allergen status. “Gluten free bun” changes cereals containing gluten. Static matrices struggle with this.
• Delivery platforms - The website PDF is updated. The aggregator copy is not.

A strong allergy matrix app removes manual duplication. It becomes the single source of truth that feeds the website, QR code allergen menu and internal service view.

The 14 allergens you must design around (UK)

In the UK, food businesses must provide information on 14 specified allergens. These are defined in retained EU law and enforced through local authorities.

The 14 are:

• Celery
• Cereals containing gluten (wheat, rye, barley, oats, spelt, khorasan)
• Crustaceans
• Eggs
• Fish
• Lupin
• Milk
• Molluscs
• Mustard
• Peanuts
• Sesame
• Soya
• Sulphur dioxide and sulphites (above 10mg/kg or 10mg/litre)
• Tree nuts (e.g. almond, hazelnut, walnut, cashew, pecan, Brazil nut, pistachio, macadamia)

You can read the official guidance from the Food Standards Agency here:

https://www.food.gov.uk/business-guidance/allergen-guidance-for-food-businesses

An allergen matrix app must:

• Clearly distinguish between “contains” and “may contain”
• Allow you to manage sub-categories (e.g. different tree nuts)
• Be flexible enough to include extended allergens if your business chooses to (e.g. garlic, onion, strawberry)

The legal baseline is the 14. The operational reality may go further.

Written allergen information & conversation best practice

UK law requires that allergen information is:

• Available in writing
• Supported by conversation if needed

That means:

• A verbal-only approach is not sufficient
• A sign that says “ask our staff” is not enough on its own

Good practice looks like this:

• Written source
• A clear, accessible allergen matrix or QR code allergen menu available at point of choice.
• Trained staff
• Team members who understand how to interpret the matrix and when to escalate.
• Clear disclaimers
• Transparent statements about cross-contact and shared kitchens.
• Escalation process
• A defined route to a supervisor or manager for complex queries.

An allergen matrix app should support this by:

• Giving staff a fast internal view optimised for service
• Logging updates so managers know information is current
• Allowing guest-facing access via a mobile-friendly interface

The goal is confidence. Guests need to see that you take it seriously. Staff need to feel supported rather than exposed.

Delivery and takeaway: allergen information at two stages

For distance selling (online orders, click and collect, delivery apps), allergen information must be provided at two stages:

1. Before purchase

The customer must be able to access allergen information before placing the order.

This means:

• On your website
• On your ordering platform
• Or clearly signposted before checkout

A PDF buried in a footer is not ideal. A searchable digital allergen matrix or integrated QR code allergen menu performs far better.

2. At the point of delivery

Allergen information must also be available when the food is delivered.

This could be:

• On packaging
• On a printed label
• Via a link included in the confirmation
• Through clear signposting on the receipt

Distance selling is where many businesses fall short. The app you choose needs to handle it by design.

The 6 features that make an allergen matrix usable in service

Not all systems labelled “allergen matrix app” are equal. These are the core capabilities that matter.

1. Ingredient-level control

If you only tag allergens at dish level, you are one recipe edit away from an error.

A strong digital allergen matrix:

• Stores allergens at ingredient level
• Allows ingredients to roll up into batches
• Allows batches to roll up into menu items

That structure means a supplier change updates every affected dish automatically.

For multi-site groups, this is essential.

2. Clear “contains” vs “may contain” logic

Cross-contact is one of the most misunderstood areas in hospitality.

An effective allergy matrix app must:

• Allow separate tagging for “contains” and “may contain”
• Prioritise “contains” in guest-facing display
• Allow site-level overrides if cross-contact differs between kitchens

Without this, you risk either under-declaring or over-warning to the point of confusion.

3. Modifier and variant handling

Modern menus are customisable:

• Choose your protein
• Swap the bun
• Add sauce
• Remove cheese

Each of those can change allergen status.

A practical allergen matrix app must:

• Support modifier groups
• Recalculate allergen profiles dynamically
• Show combined allergen impact clearly to the guest

Static matrices struggle with this. A digital allergen matrix should not.

4. Multi-site publishing control

Single site and multi-site needs are different.

Multi-site operators require:

• Brand-level control
• Location-level overrides
• Central updates with site visibility
• Permission layers for head office and local managers

An allergen matrix that cannot handle brand hierarchies will create operational friction.

If you operate across multiple locations, this is non-negotiable.

5. Guest-facing publishing (mobile-first)

A QR code allergen menu is now standard in many venues.

The app should:

• Generate a branded, mobile-friendly menu
• Allow filtering by allergen
• Present information clearly without overwhelming guests
• Work instantly without login or downloads

This is where a

digital allergen matrix

moves from compliance to customer experience.

6. Audit trail and version history

If Environmental Health visits, you need evidence of control.

An allergen matrix app should:

• Log who made changes
• Record timestamps
• Allow historical reference
• Provide export capability

Spreadsheets rarely offer robust traceability. An app should. This is not about paranoia. It is about professional standards.

UK requirements you must design around

When evaluating an allergen menu app, sanity check it against UK expectations:

• Covers all 14 allergens clearly
• Provides written information in a durable form
• Supports conversation and staff training
• Works for distance selling
• Allows accurate updates when ingredients change

If the tool does not naturally support those, you will end up building workarounds.

Checklist: choosing an allergen matrix app

Use this as a practical filter when reviewing options.

Core compliance

• Does it include all 14 allergens by default?
• Can it distinguish between contains and may contain?
• Is written information accessible to guests?

Operational control

• Can allergens be assigned at ingredient level?
• Do changes cascade automatically to dishes?
• Is there an audit trail?

Menu complexity

• Can it handle modifiers and variants?
• Does it dynamically recalculate allergen impact?

Publishing

• Does it create a QR code allergen menu?
• Is it mobile-friendly?
• Can it publish across multiple sites consistently?

Governance

• Are there role-based permissions?
• Can head office manage centrally?
• Can local variations be controlled without breaking the system?

If you cannot confidently tick most of these, you do not have a resilient system.

Single site vs multi-site: what changes?

For a single independent restaurant:

• Simplicity and clarity matter most
• Ingredient-level tagging is still valuable
• A clean food allergen chart app with QR publishing may be enough

For multi-site groups:

• Centralised data management is critical
• Site-level overrides are essential
• Audit trails and permissions are non-negotiable
• Publishing consistency across brand is required

The bigger the estate, the more dangerous spreadsheets become.

Practical closing checklist

Before you rely on any

allergen matrix app

, test it:

• Change one ingredient in a core sauce. Does every affected dish update?
• Add a gluten free bun modifier. Does the allergen profile adjust?
• View the guest-facing screen on a mobile during a simulated busy service. Is it clear?
• Check what evidence you can export if asked for documentation.
• Review how delivery allergen info is shown pre-purchase and at delivery stage.

If the system fails those tests, it will fail under pressure.

An allergen matrix is not an admin artefact. It is part of your service infrastructure.

FAQs

What is an allergen matrix app?

An allergen matrix app is a digital system that stores allergen data for menu items and publishes it in a structured format, typically as a digital allergen matrix or QR code allergen menu.

Is a spreadsheet enough for allergen management?

For very small, stable menus, possibly. But spreadsheets rely on manual updates and offer limited traceability. As menus and teams grow, risk increases.

Do I legally need to show all 14 allergens?

Yes. UK food businesses must provide information on the 14 specified allergens. You can go beyond them, but you cannot omit them.

Do I still need staff conversation if I have a QR code allergen menu?

Yes. Written information must be supported by conversation where needed. Staff training remains essential.

How should allergen information work for delivery?

It must be available before purchase and again at delivery. Your allergen menu app should support both stages clearly.

If you treat allergen information as a compliance afterthought, you will always be reacting. If you treat your allergen matrix app as core infrastructure, you give your team clarity and your guests confidence.