Digital menu allergen compliance

Publishing allergens online raises the standard rather than lowering it. A guest who reads your menu before travelling has relied on it in a way a verbal answer never allowed — and they hold you to it.

Get started free See the product

Publishing raises the standard

Five ways a digital menu misleads

Every one of these is a compliance failure in its own right, independent of whether the allergen information was ever correct.

The dish changed, the listing did not

A sauce swapped, a garnish added, a supplier changed. The kitchen and the website now disagree, and the guest is reading the website.

Contains and may contain share one column

A single asterisk covering a whole menu communicates nothing and protects nobody. The guest cannot act on it.

The allergens hiding in staples

Stock contains celery and usually wheat. Soy sauce contains wheat. Breadcrumb contains wheat and shared fryer oil. Tahini is sesame. Horseradish is mustard.

Everything carries a cross-contact warning

When every dish is flagged, the warning stops meaning anything. A guest who has learned to ignore it will ignore the one dish where it matters.

Marketing outruns the kitchen

A caption or advert calling a dish nut-free or gluten-free, written before a recipe change. Published promotional content is the hardest version of this to defend.

The fix

One specification, everywhere it appears

Where the printed menu, the online listing, the allergen matrix and the training material are maintained separately, they will diverge. The question is only when.

One source of truth

Printed menu, online listing, allergen matrix, point of sale and training material all derive from the same specification.

Change control before publication

A menu or supplier change triggers re-verification of the affected dishes before they go live, rather than afterwards.

Dated and reviewable

Every allergen statement carries a review date. It costs nothing and it demonstrates a controlled process rather than an unmanaged page.

Digital menu compliance questions

Does PPDS apply to a restaurant website?

PPDS covers food prepared on site and packaged for direct sale without further processing, so a packaged sandwich you sell is in scope. A standard restaurant menu is governed by the written allergen information rules — in England, Natasha's Law — which require written information to be available before the order is placed.

Does the website have to be updated every time a recipe changes?

It has to be accurate. The obligation is on the information being correct at the time it is given, not on a particular update mechanism. MenuOps makes accuracy structural by regenerating the affected rows when you upload the new menu.

What if our menu is in another language?

English menus give the best extraction. Other languages can be stored and displayed, but if allergen accuracy is the priority we would review the output with a manager before publishing rather than trust it directly.

What about our social media?

Treat every allergen claim in a caption, advert or photo as a claim that must be verifiable against the current specification at the moment it is published. That is the rule that catches most of these before they go out.

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