Menu with Allergens: Simple, Legal, Guest-Friendly

When we were testing the allergen fields in SafestMenu, I spent an afternoon looking at how restaurants build a menu with allergens today, instead of how they're supposed to. What I found was a lot of pen. A laminated menu with "contains nuts" scrawled next to the salad. A photocopied allergen chart taped up behind the bar that nobody has time to read mid-rush. A server explaining, from memory, which of six specials is safe for the guest who just mentioned a shellfish allergy.

None of that is anyone's fault, exactly. Recipes change more often than menus get reprinted, so the information drifts out of date long before anyone notices. But the guest sitting there doesn't care why the note is wrong. They just want a menu with allergens marked clearly, before they order, not after.

Every menu with allergens starts with the same 14

Under EU Regulation 1169/2011, food businesses have to be able to tell a guest about 14 allergens: gluten, crustaceans, eggs, fish, peanuts, soybeans, milk, nuts, celery, mustard, sesame, sulphites, lupin and molluscs. Most owners I've talked to already know this list exists in some form, even if they couldn't rattle it off from memory.

The practical question isn't whether you have to communicate it. It's how you keep a menu with allergens accurate once the kitchen gets busy and the recipe for Tuesday's risotto isn't quite the recipe for Thursday's. That's the part that trips restaurants up, and it's rarely about knowing the rules. It's the system falling apart under real service pressure.

The bottom line: allergen menu requirements aren't optional and they aren't going anywhere, so the only real decision is how much work they cost you every week.

Why the sticky note behind the bar doesn't survive service

Here's a scene we watched more than once while testing: the kitchen swaps a vegetable stock for a chicken one because that's what came in that morning. Nobody tells the front of house - why would they, it's just a stock. The laminated menu still says the soup is vegan. A new server, three shifts in, has no idea there's an unwritten exception for that dish, because the "rule" lives in one chef's head and a sticky note that fell off two weeks ago.

Paper allergen fixes fail for a boring reason: every fix needs a human to remember it, repeat it, and pass it on to the next person, forever, with no record anywhere. That works for a day. It doesn't work for a season. And it definitely doesn't work at 8pm on a Friday, when the pass has six tickets on it and someone still needs an honest answer about celery.

Mark it once per dish, not once per printing

A digital menu turns allergen info from a thing you repeat into a thing you set. With SafestMenu, guests scan a QR code on the table and the menu opens right in their phone's browser - no app to download. You edit the menu from your own phone, and the change goes live the moment you save it.

The workflow is short:

1. Open the dish in your menu editor.
2. Tick the allergens that apply to it, from a fixed list.
3. When the recipe changes, tick or untick one box.
4. That's it - every guest scanning the code from that second on sees the update.

No reprint, no laminating run, no briefing the new server about the soup. The allergen mark lives with the dish, not with whoever happens to remember it that shift.

One mark, six languages, no lost-in-translation moments

This is the part I noticed while checking the multilingual side of things. A guest can switch the menu to their own language, out of six available, and the allergen mark on a dish stays exactly where you put it. You're not keeping a German allergen chart and a separate English one that quietly drift apart, which is exactly what happens with printed inserts. You set it once, on the dish, and it travels with every translation automatically.

It also changes the conversation at the table. A guest with a nut allergy can check the menu on their own phone, quietly, before ordering, instead of flagging down a server mid-rush and hoping for a confident answer. That's better for them and a lot less stressful for your staff. If you're weighing digital against paper more broadly, our full comparison covers the rest of the trade-offs, and this piece on what paper menus actually cost covers the reprint side in more detail.

Start with a menu that's honest by default

You don't need a new system to get this right, just a menu that updates as fast as your kitchen does. Your first menu, five dishes, is free forever, no card required. Build it at app.safestmenu.com, mark the allergens as you add each dish, and you'll never need a sticky note behind the bar again.

A menu with allergens marked isn't a compliance chore you finish once and forget. It's a habit: mark it when you write the dish, update it when the recipe changes, and let the QR code handle the rest.