Fixed quote after a free call

A restaurant allergen matrix the kitchen can keep up to date

Allergen information is only as good as the last recipe or supplier change. We build a workflow that links each dish to its ingredients and allergens, flags changes when a recipe is edited or a supplier swaps a product, produces a dated allergen matrix and menu sheet for the chef to approve, and routes guest allergen questions to a trained person. It never tells a guest a dish is safe. A typical build costs $1,000 to $2,500 and takes about four to five weeks.

The problem

Why restaurant allergen information drifts out of date

Menus change with the seasons, suppliers substitute products, and a sauce gets a new ingredient on a Tuesday. The printed allergen matrix behind the pass was accurate when it was made, and nobody is sure when that was.

The rules differ by country. The US recognises nine major allergens; the UK and EU regulate 14 and require allergen information for loose food as well as packaged food; the UK adds full ingredient labels for food prepacked for direct sale. A venue needs a record it can trust and a clear trail of who approved each change.

What we build

What our restaurant allergen matrix workflow includes

Recipe to allergen links

Each dish linked to its ingredients and the allergens regulated where you operate, in a sheet or database the kitchen controls.

Change flags

Edited recipes and supplier specification changes flagged for the chef before the next service.

Dated allergen matrix

A matrix and menu allergen sheet generated from the records, with the date and the approver's name.

Label drafts for prepacked items

For UK grab-and-go items, label drafts with the full ingredients list and allergens emphasised, for the chef to check.

Guest question routing

Allergen questions from email, chat or reservations go to a trained person with the dish records attached.

Change history

Every recipe change, who approved it and when, kept for inspections and training.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Recipe or supplier change

    A recipe edit or a new supplier specification is detected.

  2. 02 Automated

    Allergens recalculated

    The dish's allergen record is updated from its ingredient list.

  3. 03 Automated

    Change flagged

    The chef gets a list of dishes whose allergens changed.

  4. 04 Team review

    Team briefed

    The floor team gets the updated matrix at the pre-service briefing.

  5. 05 Manager or chef decides

    Chef approves

    The head chef checks every change, including cross-contact risk, and approves the matrix.

How it behaves

How allergen records behave

What each person sees and what runs in the background, including what happens when something goes wrong.

What the guest sees

  • Allergen information that matches today's menu
  • A trained person answering their allergen question
  • A reminder to tell staff on arrival

What the team sees

  • A dated, approved matrix at every briefing
  • A list of dishes that changed since last week
  • Guest allergen questions with the dish records attached

What the automation does

  • Detects recipe and supplier changes
  • Recalculates allergen records for the chef to approve
  • Keeps a full change history

Edge cases and fallbacks

Supplier substitutes a product on delivery
Logged and flagged to the chef before the dish is served.
Supplier sheet is unclear
The dish is marked for chef review; nothing is assumed.
Daily special not in the records
The chef adds it before service, or staff say allergen information must be checked.
Shared drive or workflow outage
The last approved printed matrix stays in use and the chef is alerted.

Architecture

Allergen records for a restaurant at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Recipes Kitchen records Supplier specs Product sheets n8n workflow Detect changes Allergen records Dish by dish Head chef Approves changes Allergen matrix Dated, signed Floor team Briefing sheet
  • Input
  • Logic and services
  • Data
  • People
  • Output

How it flows

  1. 1 Recipe edits and supplier specification changes are picked up by the workflow.
  2. 2 Each affected dish has its allergen record recalculated from its ingredients.
  3. 3 The head chef reviews every change, including cross-contact, and approves it.
  4. 4 A dated matrix and briefing sheet go to the kitchen and floor team.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Allergen matrix & menu change records project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Current recipes, matrix, suppliers, which country rules apply and who approves changes.

  2. 02

    Design

    About 1 week

    Record structure, allergen list for your jurisdiction, change rules and output formats.

  3. 03

    Build

    1 to 2 weeks

    Records, change detection, matrix and label drafts, question routing and history.

  4. 04

    Chef review

    About 1 week

    The chef checks every dish record against the current recipes before anything is published.

  5. 05

    Launch

    1 to 2 days

    First approved matrix issued and the team briefed.

  6. 06

    Support

    Ongoing

    Menu changes, new suppliers and new sites.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n Google Sheets, Airtable or your recipe costing tool Supplier specification sheets (email or portal) Google Drive or SharePoint for dated matrices Claude or OpenAI for reading supplier sheets (checked by the chef)

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Recipes, suppliers, jurisdiction and approval steps.

    $200 – $400

  • Build

    Records, change detection, matrix and routing.

    $500 – $1,300

  • Integrations

    Recipe tool or sheet, supplier inbox and storage.

    $150 – $400

  • Testing and chef review

    Every dish record checked against current recipes.

    $100 – $250

  • Launch and training

    First matrix issued and team briefing.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Entering a large back catalogue of recipes takes more time and is quoted on the call. Software costs are billed to you directly.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • Spreadsheet or database: Google Sheets, Airtable or your recipe tool on its own plan.
  • n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).
  • AI model usage: Pay-per-use fees for reading supplier sheets, usually small.

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

US: nine major food allergens

The FDA recognises milk, eggs, fish, crustacean shellfish, tree nuts, peanuts, wheat, soybeans and sesame, with sesame required from January 1, 2023.

Source: www.fda.gov

EU and UK: loose food needs allergen information

Article 44 of Regulation 1169/2011 applies allergen information to non-prepacked food and lets each country set how it is provided.

Source: www.legislation.gov.uk

UK: food prepacked for direct sale

Since 1 October 2021, PPDS food in England, Wales and Northern Ireland needs the food name and a full ingredients list with the 14 allergens emphasised.

Source: www.gov.uk

General information, not legal advice

Allergen rules and enforcement are set by your country and local authority; the chef or owner confirms what applies to the venue.

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Restaurant allergen menu questions questions, answered.

A table that shows which regulated allergens are in each dish on the menu. Kitchens and floor teams use it to answer guests, and inspectors may ask to see it. Ours is generated from the recipe records and approved by the chef, with a date on it.

No. At most it reads supplier sheets and suggests what changed. The head chef checks every record, including cross-contact risk, and approves it before it reaches the team.

The one that applies where you operate: the FDA's nine major allergens in the US, the 14 regulated allergens in the UK and EU, or your local list elsewhere. Groups across countries can keep both.

It can produce a guest-facing allergen sheet from the approved records. Guests are still asked to tell staff about allergies on arrival, and staff confirm.

If the tool offers an API or export, yes; otherwise we keep recipes in a shared sheet or Airtable base the kitchen controls. We confirm the route per project.

How quickly recipe changes reach the matrix, how many guest allergen questions are answered by a trained person on the same day and how current each site's matrix is.

Free 20-minute call

Want this for your restaurants & café?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call