Case Study: Restaurant Group Manages Allergens Across 8 Locations with One Tool
A UK restaurant group managing 8 sites reduced allergen compliance risk and administration by centralising allergen data management through Allergen Matrix.
Managing allergen information consistently across multiple restaurant sites is a significant compliance challenge. When menus change, seasonal specials launch, and ingredient suppliers switch — the risk of allergen information being out of date at any one site is real.
The Challenge
An 8-site UK restaurant group was managing allergen information in a combination of laminated wall charts at each site, a shared Google spreadsheet updated by the head chef, and PDF menus updated monthly. When a menu change occurred, the process of updating all 8 sites was slow and error-prone.
A near-miss incident — a guest at one site was served a dish containing sulphites that had been removed from the menu at head office but not yet updated at the site — prompted a review.
The Centralised Solution
The group implemented Allergen Matrix for their Shopify-based ordering platform:
- All menu items tagged centrally with allergen data
- Changes made centrally propagate to all site-level online menus immediately
- Live filterable allergen matrix embedded on each site's ordering page
- Audit log captures all changes with timestamp and author — evidence that allergen data was updated on a specific date
The Compliance Benefit
In a food allergen incident investigation, the audit log provides evidence that the business maintained accurate allergen records. This is meaningful legal protection in addition to the operational benefit.
The Operational Benefit
Menu changes no longer require a manual update at 8 sites. One change in the admin cascades to all live menus. The estimated time saving was 6 hours per menu change cycle.
Why Fragmented Systems Create Serious Risk
When allergen data lives in multiple places — printed charts, spreadsheets, PDFs, and verbal briefings — the likelihood of version mismatch increases with every menu update. A spreadsheet updated on a Tuesday morning means nothing to the laminated chart still hanging in a kitchen on Friday evening. These gaps are not theoretical. UK food allergen law, specifically Natasha's Law and the Food Information Regulations, places the legal burden of accurate allergen disclosure squarely on the food business operator. A fragmented system is difficult to defend in an incident investigation.
The practical problem is compounded in multi-site operations where individual site managers often adapt menus locally. Seasonal ingredient substitutions, supplier changes, and specials added at site level can all introduce allergen discrepancies that head office has no visibility over. Without a single source of truth, the compliance burden effectively multiplies by the number of sites. Each location becomes its own compliance risk, and the head office has limited ability to audit or correct the situation without manual intervention.
Centralising allergen data on the same platform used for ordering removes the possibility of a mismatch between what a customer orders and what allergen information they were shown. When the product record is the allergen record, updates are structurally enforced rather than relying on staff remembering to update a separate document. This architectural approach — making compliance a property of the product data itself — is fundamentally more reliable than any process that depends on human coordination across multiple systems.
How the Implementation Was Structured
The group's Shopify setup was already being used for online ordering across all eight locations, which made the integration straightforward. Each menu item was mapped to its allergen profile during an initial data entry phase, which the head chef completed over approximately two working days. The team prioritised high-risk items first — dishes containing celery, mustard, and tree nuts — before completing the full menu. This phased approach meant the highest-risk allergen data was live and accurate within the first 48 hours of setup.
Once the initial data was entered, the filterable allergen matrix was embedded directly on each site's ordering page using a Shopify section. Customers can filter by any of the 14 major allergens recognised under UK and EU food law, and the matrix updates in real time as filters are applied. The display is designed to be readable on mobile, which is where the majority of the group's online orders originate. Front-of-house staff were also briefed to direct customers with allergen queries to the live matrix rather than printed materials, which instantly became the secondary source.
The audit log feature proved to be a significant operational benefit that the team had not originally prioritised. Every change to allergen data — whether a new dish is added, an allergen is removed, or a supplier substitution is flagged — is recorded with the time, date, and Shopify user account that made the change. This means that in the event of a complaint or investigation, the business can demonstrate precisely when a change was made and by whom. For a multi-site operation, this level of traceability would previously have required a dedicated compliance management system at considerably greater cost.
Training Staff Across Multiple Sites
One underestimated challenge in multi-site allergen compliance is staff training consistency. A central system solves the data problem, but it does not automatically solve the human problem. Staff at each site need to know where to find allergen information, how to interpret it, and what to do when a customer has a complex allergy query that falls outside standard filtering. Without consistent training, even accurate allergen data can fail at the point of customer interaction, which is where the compliance obligation ultimately sits.
The group addressed this by creating a short internal training document that referenced the live allergen matrix as the single authoritative source. Staff were trained to direct all allergen queries to the embedded matrix first, and to escalate to the kitchen manager for any query involving anaphylaxis risk or multi-allergen combinations. This escalation protocol was deliberately simple — two steps, no ambiguity — because complexity in a busy service environment tends to be ignored. The training document itself was updated once, centrally, and distributed digitally rather than printed, which meant all sites received identical guidance simultaneously.
Ongoing staff turnover is a persistent compliance risk in hospitality. New staff joining a single site in a multi-site operation may receive allergen training from a colleague rather than a manager, and informal training often degrades over iterations. By anchoring the training to a live digital tool rather than a printed procedure, the group ensured that any staff member, regardless of when they joined or who trained them, is directed to a source that is always current. The tool itself carries the compliance burden, and the training simply teaches people how to use it correctly.
Handling Seasonal Menu Changes and Supplier Switches
Seasonal menus are a particular allergen compliance challenge because they introduce new dishes, new ingredients, and sometimes new suppliers within a short implementation window. A spring menu launch that introduces a new dish containing sesame — now a declarable allergen under updated UK guidance — requires that the allergen data be live and accurate before the dish is served, not after. In a multi-site operation, the risk of a dish going live at one site before allergen data has been updated is highest during these high-pressure change periods.
Supplier switches introduce a related but distinct risk. A dish that has always been allergen-free for a specific allergen may become a risk if a new supplier uses shared production equipment or a different ingredient formulation. This type of change is easy to overlook in a busy kitchen environment, particularly if the dish looks and tastes identical. Centralised allergen management only protects the business if the data entry process includes a supplier-switch review step. The group built this into their supplier onboarding checklist, requiring a formal allergen declaration from any new supplier before the product enters the kitchen.
Within the Allergen Matrix setup, the group created a standard operating procedure for menu change cycles. Any new dish or ingredient change triggers a mandatory allergen data review before the item goes live on the ordering platform. Because the Shopify product record and the allergen record are the same object, it is not possible to publish a new dish without completing the allergen tagging step. This structural enforcement removes the possibility of a dish going live without allergen data, which was the precise failure mode that had caused the original near-miss incident.
What Other Multi-Site Food Businesses Can Learn
The core lesson from this case study is not specific to restaurant groups. Any food business operating across multiple locations — whether that is a café chain, a contract catering operation, or a food hall with multiple concessions — faces the same structural risk when allergen data is managed in disconnected systems. The solution is not more rigorous manual processes. Manual processes are inherently fragile under the pressures of a live food service environment. The solution is a system architecture where accurate allergen data is a structural property of the product record, not a separate document that must be kept in sync.
The secondary lesson is about audit trails. Food allergen incidents can result in serious legal consequences for food businesses, and the ability to demonstrate that allergen data was accurate and up to date at the time of an incident is a meaningful legal protection. An audit log that records every change with a timestamp and user attribution is not a bureaucratic extra — it is evidence. Businesses that rely on undated printed documents or manually updated spreadsheets cannot produce this evidence, which is a significant disadvantage in any formal investigation or legal proceeding.
If you operate a multi-site food business and publish content, menus, or compliance information across several web properties, maintaining consistency across those pages is a related challenge. BlogFlow helps Shopify merchants manage and publish content centrally, so that updates reach all relevant pages without manual repetition. Consistent, accurate content across all your customer-facing pages is as important for trust as it is for compliance.
Centralise allergen management across your food business with Allergen Matrix.
Try BlogFlow free at saltai.app — no credit card required.
SaltAI Team
SaltAI builds focused Shopify apps for food merchants and general merchants. Every app is tested in production at a real food store — including Vanda's Kitchen — before it ships.