How to Show Allergens and Dietary Info on a Digital Menu

To show allergens and dietary information well on a digital menu, do two things: label every dish with clear, text-based allergen and dietary tags, and give guests a way to ask follow-up questions in their own words. Tags answer the obvious questions instantly; the ability to ask covers everything a fixed label can't. For severe allergies, a digital menu informs the conversation, it never replaces a check with your kitchen.

Most guests don't read a menu looking for trouble. But the ones who need allergen information really need it, and they often decide how much to trust your restaurant in the first thirty seconds of looking at the menu. Getting this right is part safety, part hospitality.

How should allergens be labeled on a digital menu?

Start with the labels themselves. A digital menu can do things paper can't, but the basics still matter most.

• Tag every dish, not just the obvious ones. A salad can hide nuts in the dressing. Bread can contain dairy. Don't make guests guess which items you've checked.
• Use text labels, never colour alone. A red dot means nothing to a guest who's colour-blind or unfamiliar with your key. Write the word: "contains peanuts", "made with dairy". Pair an icon with the label if you like, but the label carries the meaning.
• Cover the common allergens clearly. The ones guests ask about most are peanuts and tree nuts, dairy, eggs, gluten and wheat, soy, shellfish and fish, and sesame. If a dish contains one, say so plainly.
• Separate "contains" from "may contain." A dish made with peanuts is different from one prepared in a kitchen where peanuts are present. Both matter to a guest with a serious allergy. Don't blur them into one vague note.
• Mark dietary fit honestly. Vegetarian, vegan, halal, use these only where they truly apply, and only if you can stand behind them. A wrong "vegan" tag erodes trust faster than no tag at all.

The goal is simple: a guest should be able to look at any dish and know, in plain words, what's in it.

What's the difference between allergen tags and answering questions?

This is where most digital menus stop short. Tags are a fixed list. They answer the questions you predicted. But guests ask things no tag anticipates:

• "Can you make the pasta without cream?"
• "Is the soup actually vegan, or just vegetarian?"
• "I'm avoiding gluten, what's safe here that isn't just a salad?"
• "Which of your dishes are nut-free and dairy-free?"

A static menu can't answer any of these. The guest either flags down a server or, more often, quietly orders the one thing they're sure about, or doesn't order at all.

A digital menu that lets guests ask questions in plain language closes that gap. Instead of scanning twelve dishes to find what fits, a guest asks once and gets a specific, honest answer. That's the difference between displaying dietary information and actually helping someone use it.

Should a digital menu answer dietary questions directly?

Yes, as long as it answers honestly and knows its limits.

A good answer is specific and grounded in your actual menu data. "The grilled sea bass is gluten-free and dairy-free. The risotto contains dairy, but the kitchen can prepare it without parmesan, ask your server to confirm." That's useful. It moves the guest forward and points them to staff for the part that needs a human.

A bad answer over-promises. Anything that says "this is safe for you" about a severe allergy is a problem, because no menu, printed or digital, can guarantee what happens in a working kitchen. The honest framing is always: here's what's in the dish, here's what we can adjust, and please confirm anything serious with your server.

Answering directly is good hospitality. Answering carefully is good practice.

How do you handle allergens across multiple languages?

If your guests speak more than one language, your allergen information has to as well. A guest reading a menu in their second language is exactly the person most likely to misread a critical detail.

• Translate the allergen labels, not just the dish names. "Contains nuts" is useless to a guest if only the dish title is in their language.
• Support right-to-left properly for Arabic. RTL isn't just mirrored text, alignment, punctuation, and number direction all shift. A half-translated menu where the allergen note still reads left-to-right looks careless, and careless is the last impression you want around food safety.
• Let guests ask questions in their own language. A guest who can ask "هل يحتوي هذا على مكسرات؟" and get a clear answer is far safer than one squinting at a translation they're unsure of. Plain-language questions work best when the guest doesn't have to translate themselves first.

Handled well, multilingual support isn't a nice-to-have, it's the difference between a guest feeling looked after and a guest feeling at risk.

A practical checklist

Use this to audit your own menu:

• Every dish has text-based allergen tags, not colour codes alone.
• The common allergens, nuts, dairy, eggs, gluten, soy, shellfish, fish, sesame, are covered.
• "Contains" and "may contain" are clearly separated.
• Dietary tags (vegetarian, vegan, halal) are accurate and stand behind themselves.
• Guests can ask follow-up questions, not just read fixed labels.
• Answers are specific and honest, and point to staff for anything severe.
• Allergen information is translated fully in every supported language, with proper RTL for Arabic.
• Nothing on the menu claims a dish is "safe" for a serious allergy without a staff check.

A note on severe allergies

Be clear with yourself about what a digital menu can and can't do. It can give guests accurate, instant, well-organised information. It can answer questions a server might be too rushed to field. It can do this in several languages, at every table, without anyone having to ask twice.

What it cannot do is replace a human checking the kitchen for a guest with a life-threatening allergy. Cross-contact happens in prep, on shared surfaces, in fryer oil, places no menu can see. The right model is partnership: the menu informs and reassures for everyday dietary needs, and for anything severe, it hands the guest to your staff with the context already gathered. Say this plainly on your menu. Guests with serious allergies will trust you more for being honest about the limit, not less.

How tamr helps

tamr gives every dish clear allergen and dietary tags, then lets your guests ask the AI waiter anything the tags don't cover, in plain language, in English, Arabic, French, Japanese, or Spanish, with full right-to-left support. Answers stay specific and honest, and point guests to your staff when an allergy is serious. You also see what guests asked about, so you learn where your menu leaves people guessing.

Want to see it with your own menu? Book a demo → or read more about tamr for multi-location groups.