Allergen safety and restaurant operations, in one system
MenuOps reads your menus and SOPs, extracts every allergen, keeps the matrix current when the menu changes, and puts the answer in front of staff at the point of service.
major allergens mapped per dish
manual updates needed when the menu changes
for staff to reach a verified answer
of menu changes re-reviewed automatically
The platform
What MenuOps actually does
Six things that replace manual work behind allergen safety and staff training.
Automated allergen extraction
Upload a menu and every ingredient in every dish is mapped to the 14 major allergens — including the ones hiding in stock, soy sauce, breadcrumb and dressings that manual matrices miss.
Stays current automatically
When the menu changes, the matrix regenerates and the affected rows are flagged for review. This is the single largest source of compliance findings in hospitality.
Assessed staff training
Scenario quizzes on allergen queries, cross-contact and escalation, with immediate feedback and targeted re-training when someone gets it wrong.
Answers on the floor
Staff get the answer where the question is asked, in seconds, without interrupting the kitchen. Not a binder in the office, not a guess.
Inspection-ready records
Allergen information, training evidence, menu specifications and change history, all dated and attributable. The four questions an inspector asks, each with a document behind it.
A copilot grounded in your documents
Ask about ingredients, allergens, prep methods or pairings and get an answer grounded only in your own material. It says when something is not covered rather than inventing it.
Why it matters
The failures we are built around
Not the theoretical risk — the specific, recurring problems that show up at every inspection.
The matrix goes stale silently
A dish is altered on a Tuesday by someone who does not know a matrix exists, and the written allergen information is wrong from Wednesday with no signal to anyone.
Staff recite the list, not the dishes
Knowing the 14 allergens is not the same as recognising celery in the stock cube used in every sauce on the menu. That gap is where incidents happen.
Cross-contact is acknowledged but unaddressed
A dedicated fryer is discussed and then the fryer is shared. The policy exists; the physics does not match it.
Knowledge lives in the wrong place
If staff must find a person to answer an allergen question, they will interrupt someone. If they cannot, they will guess.
Getting started
From upload to signed-off matrix
Most restaurants are running staff training within a day of uploading their menu.
-
1
Upload your menu
A PDF or Word document is all that is needed. The full menu, in whatever format you currently send it to the printer.
-
2
Review the extraction
Every dish is mapped to the 14 allergens with the source ingredient named. A manager signs off each item — you keep control of what is published.
-
3
Invite the team
Staff get scenario-based training on your actual dishes, not a generic list. Results are recorded as evidence.
-
4
Update on every change
When the next menu lands, MenuOps regenerates the affected rows and flags exactly what changed, so review is minutes rather than a full re-audit.
Put this into practice
Upload a menu you already use. Review the allergen matrix MenuOps generates from it — that is the fastest way to know whether it is worth your time.