Allergen management software, built for restaurants

Generic document tools can store a matrix. They cannot read a menu, understand an ingredient list, or tell you what changed when you reissue a dish.

Get started free See the product

Why this is not a document tool with a template

The difference is whether the software understands what a menu is. One does; the others store the output of someone who already did the work.

	Generic doc tool	Menu builder	MenuOps
Reads a menu you upload	No	Only the items you re-key	Yes
Maps ingredients to the 14 allergens	No	No	Yes
Names the source ingredient	No	No	Yes
Separates contains from cross-contact	No	By hand	Yes
Flags what changed on a menu revision	No	No	Yes
Retains supplier specifications	By hand	No	Yes
Answers staff queries at the till	No	No	Yes
Keeps going current without a person	No	No	Yes

A document tool is useful once a matrix already exists. MenuOps is useful before one does, which is when the work is hardest.

What it does

Written for the way restaurants actually change menus

Extraction that names the ingredient

Not a list of allergens per dish — the actual source. 'Celery, in the base stock' is actionable. 'Celery' alone is a finding waiting to happen.

Review scoped to what changed

Reissue a menu and only the affected rows are flagged. Full re-auditing twenty dishes because two changed is why manual matrices get abandoned.

Training on your dishes

Scenario questions drawn from your menu, so staff are tested on what they actually serve rather than a generic list they will forget.

The answer at the point of service

Available where the question is asked. A correct answer that takes four minutes to retrieve does not survive a Saturday night.

Allergen software questions

How accurate is the automated extraction?

It maps ingredients in your menu text to the 14 major allergens, including indirect sources like stock, soy sauce and breadcrumb. It is a starting point for a manager to review, not a final authority — and it is built that way deliberately. Every item is signed off by a person before it is published, because an automated system that is trusted without review is worse than a manual one.

Will it catch an allergen we are not thinking about?

That is the main reason to use it. The allergens that get missed are the ones nobody searched for: celery in a stock cube, mustard in a marinade, sesame in a bread. These appear in the ingredient text and are mapped without anyone having to remember to look.

Does it replace our HACCP plan?

No, and it should not. Your plan and your procedures remain yours. MenuOps removes the manual maintenance that causes findings — the matrix drifting out of date and the training evidence not existing.

What about a menu in another language?

Extraction works best on English menus. Other languages are supported for storage and display, but if allergen review is your priority we would review the extraction output carefully before publishing.

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.

Get started free See pricing