Allergen Matrix Builder Toolkit
Use one structured workflow to keep allergen information clearer, more consistent, and easier to update as menus evolve. Built with ingredient tagging, evidence tracking, house prep inheritance, matrix outputs, validation alerts, and publish history for smoother day-to-day control. This phrasing is a tightened restatement of the live feature set.
“Very practical system for menus that change often. The alerts and validation checks helped us catch missing information before anything was shared with staff or guests.”
Daniel K. | Operations Manager
The problem it solves
Allergen risk usually comes from inconsistent tagging and outdated documents.
Recipes change faster than PDFs, staff rely on memory, and unknown ingredients slip through. When supplier evidence is scattered or missing, allergen decisions become harder to defend and easier to get wrong.
This toolkit creates a single source of truth with evidence, automatic matrix outputs, and a publish workflow, so allergen gaps are easier to catch before outdated information, unknown ingredients, or weak publish control create avoidable service risk.
Why teams use this workflow
-
keep allergen declarations consistent across menu items and versions
-
separate declared allergens from trace or cross-contact risk
-
store supplier evidence so decisions stay more defensible and repeatable
-
use alerts to catch missing data before anything goes live
-
publish a clean matrix and print summary without rebuilding documents
How it works
Build your ingredient library, tag allergens, add supplier evidence, and connect house-made components to their source inputs. Then link menu items and recipe lines using ingredient IDs so the final allergen matrix updates from the underlying data instead of being rebuilt manually.
That gives you a clearer workflow for maintaining allergen declarations, controlling publish history, and reducing the chance of outdated or unsupported information reaching staff or guests. The second sentence is an inference from the live workbook structure and publish controls described on the page.
Best for
Bars and operators who need a reliable allergen workflow for menus with frequent recipe changes, including house preps.
Choose the right version
Both options use the same core toolkit. The difference is how much setup work you want to handle yourself.
Instant Download
You receive the full template workbook plus A4 print pack, ready to use internally.
Add your own ingredients, evidence, house preps, and menu items, then use the toolkit to manage allergen tagging and publish a cleaner matrix with a more controlled workflow from the start.
Best for teams that want the full workflow ready to use and prefer to manage their own ingredient tagging internally.
Includes:
-
instant download
-
Excel workbook + Google Sheets import file
-
full template workbook
-
A4 print pack
-
matrix workflow, logs, and support files
Done for You Setup (4 days delivery)
A done-for-you first build for your current menu.
Ingredient tagging, source linking, house preps, menu items, and the first publish-ready matrix are prepared for you, followed by a QA pass to reduce resolvable Unknown flags using the evidence you provide.
Best for operators who want faster implementation, less setup work, and a publish-ready first version built for current menu use.
Includes:
-
everything in Instant Download
-
done-for-you initial build
-
ingredient tagging and source linking
-
house preps and menu items built into the file
-
first publish-ready matrix
-
QA pass to reduce resolvable Unknown flags
What’s inside the toolkit
-
Ingredient Library with allergen tags
Uses Contains, Traces, and Unknown status to keep tagging more structured. -
Sources tab for supplier evidence
Stores supporting evidence so decisions are easier to review and defend. -
House Preps module
Lets house-made components inherit allergen tags from their inputs. -
Menu Items and Recipe Lines built from ingredient IDs
Keeps matrix outputs linked to the underlying data. -
Allergen Matrix with automatic flags
Generates clear Contains and May Contain style outputs for menu use. -
Cross-contamination notes and controls
Adds clearer context where trace risk needs separate handling. -
Alerts and QA dashboard
Highlights missing evidence and inconsistencies before publish. -
Version Log and Audit Log
Keeps publish history and changes easier to track. -
Print Summary (A4)
Makes staff access and archiving easier.
License & Support
This toolkit is licensed for internal use by one user or one business.
It may not be resold, redistributed, shared outside your business, or repackaged for resale.
Reasonable support is available for setup, formulas, and functionality questions. Genuine technical issues will be reviewed and corrected where applicable.
Delivery format
This toolkit is delivered as a ZIP download.
Inside the ZIP you will find:
-
Excel master workbook (.xlsx)
-
Google Sheets import file (.xlsx)
-
PDF quick-start guide
-
Overwrite-ready example menu
-
For the configured version, setup support is included as described above.
Customer feedback
Review requests are sent after purchase.
Feedback may be checked before publication.
★★★★★
“Clear, fast, and actually useful during menu development. Much easier than checking ABV and dilution manually.”
Marco L.
Bar Manager
★★★★★
“This made allergen tracking much easier to manage. Having ingredient tags, supplier evidence, and one clear matrix reduced a lot of uncertainty for the team.”
Sophie L.
Quality & Compliance Lead
★★★★★
“Very practical system for menus that change often. The alerts and validation checks helped us catch missing information before anything was shared with staff or guests.”
Daniel K.
Operations Manager
★★★★★
“Clean, structured, and much better than relying on scattered notes and outdated PDFs. It gave us a more reliable process for allergen updates and internal checks.”
Maya R.
Food Safety Coordinator
Keep allergen information easier to update and harder to get wrong
Use one practical system to tag ingredients, track evidence, and publish a cleaner allergen matrix, so recipe changes do not quietly create avoidable service risk. This is a conversion-focused restatement grounded in the page’s stated problem and feature set.