Allergen & Dietary Labels on Digital Menus: 2026 Restaurant Guide
About 1 in 3 customers now check menus for allergens, dietary tags, or "may contain" notices before they order. If your digital menu doesn't show this clearly, you don't just risk a complaint or a refund — you usually lose the order before it starts.
This guide covers what to label, how to label it on a digital menu, and the simple system that keeps it accurate as your menu changes. This isn't legal advice — talk to a regulator or counsel for that — but a practical playbook built for small restaurants, cafes, food trucks, and cloud kitchens.
Why allergen info on the menu matters more than you think
Three things are happening at once in 2026.
More customers have or live with someone who has a confirmed food allergy or intolerance. Dairy, gluten, nuts, soy, and shellfish sit at the top of the list across most regions.
Lifestyle dietary choices — vegetarian, vegan, halal, kosher, jain, keto — have moved from niche to mainstream. People filter menus by tag the way they filter Amazon by Prime.
Regulators in the EU/UK (Natasha's Law), the US (FDA labeling rules under FALCPA), and India (the FSSAI Display of Information by Restaurants framework) keep tightening expectations on prepared-food disclosure. Specifics vary, but the direction is one-way.
Even setting compliance aside, the business case is simple: if a customer can't tell at a glance whether your butter chicken contains nuts, they go to the next menu in their search results. In our experience working with small operators, the difference between a clearly-labeled menu and an ambiguous one is one of the highest-leverage edits you can make.
What to label: the short list
Two layers of labels matter. Allergens are the legally-relevant ones; dietary tags are the ones diners filter by.
Allergens (most regulators converge on these)
The top allergens called out by major regulators include peanuts, tree nuts, dairy/milk, eggs, wheat/gluten, soy, fish, shellfish, sesame, mustard, celery, lupin, molluscs, sulfites, and (regionally) corn or buckwheat. The exact list varies — check your local rules — but the practical advice is the same: cover the big seven (peanut, tree nut, dairy, egg, wheat/gluten, soy, shellfish) and add what's relevant to your cuisine and customer base.
Dietary tags (what diners actually filter by)
A short, well-applied list beats a long, inconsistent one. The tags worth supporting on most digital menus include vegetarian, vegan, gluten-free, halal, jain (no onion, no garlic, no root vegetables), kosher, a spice-level indicator, and optional calorie or nutrition info.
Pick four to six tags that fit your menu and apply them consistently. An empty tag picker — "we have one vegan dish" — looks worse than no tags at all.
Four ways to surface the info on a digital menu
Pick the right method based on your menu size and how often you change it.
| Method | Setup effort | Customer clarity | Maintenance |
|---|---|---|---|
| Free-text in the description | Low | Low — buried in paragraphs | Easy to forget when items change |
| Icons / colored badges next to the item name | Medium | High — scan-friendly | Manageable if tags live in a structured field |
| Filter chips (vegan-only, gluten-free-only) | Medium | Highest — diners self-serve | Needs structured tags from day one |
| Linked allergen matrix PDF | Low | Low on mobile, OK on desktop | Easy to drift out of sync with the live menu |
The combination that works for most operators is icons next to the item name plus filter chips at the top of the menu. Customers who don't care ignore them; customers who do care filter and order in seconds.
A concrete example: butter chicken on a digital menu
Bad version (free text only):
Butter Chicken — our signature creamy tomato curry, served with rice. ₹320
Good version (icons + structured tags):
Butter Chicken
🥛 Dairy🌶️🌶️ MediumOur signature creamy tomato curry, served with rice. ₹320 Contains: dairy, tomato. Cooked in cashew paste — not suitable for tree-nut allergies.
Same dish, far less ambiguity. The diner with a nut allergy doesn't have to message you to find out.
How to implement this on a digital menu
If you're using OrderViaChat, allergen and dietary fields are built into each menu item. The pattern is the same on most modern platforms — store the tags as structured data, not freeform text:
- Add tag fields per item — allergens (multi-select) and dietary (multi-select). Most digital-menu builders let you do this in the item editor.
- Decide on icons or short codes once, then reuse them everywhere. Inconsistency ("V" on one item, "Veg" on another) erodes trust quickly.
- Add a "Contains / May contain" field for items prepared in a shared kitchen. The "may contain" disclaimer covers cross-contact risk without scaring everyone away.
- Turn on filter chips at the top of the menu so a vegan or gluten-free customer can hide everything else with one tap.
- Add a single, plain-language disclaimer in the menu footer (template below).
A disclaimer template you can copy
Adjust to your jurisdiction and operation:
We prepare food in a shared kitchen and cannot guarantee that any item is free from allergens or cross-contact. If you have a severe allergy, please message us before ordering and we'll confirm what's safe to prepare for you.
That sentence does three jobs at once: it sets expectations, it invites a conversation, and it creates a paper trail (the chat thread) if a question ever comes up later.
Real-numbers example: what better labeling actually changes
Take a 40-item menu doing 600 orders a month at an average ticket of ₹450. Suppose adding visible dietary filters and clear allergen tags lifts order completion by a conservative 4% — not because more people walk in the door, but because fewer abandon the cart while squinting at descriptions.
| Metric | Before | After (+4%) |
|---|---|---|
| Monthly orders | 600 | 624 |
| Average ticket | ₹450 | ₹450 |
| Monthly revenue | ₹270,000 | ₹280,800 |
| Annual lift | — | ₹129,600 |
That's roughly a one-day lift per month from a one-time labeling pass. The lift is bigger when your existing menu is very ambiguous and smaller when it's already clean — but in our experience the direction is consistent.
Common mistakes to avoid
Tagging items "GF" when they're cooked in a shared fryer. That's a complaint waiting to happen. Use "GF prep available — please ask" if cross-contact is a real risk.
Letting tags drift when you change recipes. A single item update without a tag review is how mistakes slip in. Build a "tag review" step into your menu-edit checklist.
Hiding the disclaimer. Footer is fine; under three pop-ups is not.
Using too many tags. Six clear ones beat fifteen vague ones. Customers stop filtering when the list gets long.
Translating only the menu, not the allergen labels. If your menu serves Hindi, Spanish, or Arabic-speaking diners, translate the tags and the disclaimer too — partial translation reads as careless.
A 30-minute audit you can run today
- Open your live menu and list every item.
- For each item, mark its primary allergens and dietary tags in a spreadsheet.
- Add a "Contains / May contain" line for anything cooked in a shared station.
- Pick your final tag set (no more than six) and apply consistently.
- Add the footer disclaimer.
- Test the filter chips on a phone — that's how 80%+ of customers will actually see your menu.
That's the whole thing. No new software, no consultant, no new staff process. Just a structured pass through what you already serve.
Wrapping up
Allergen and dietary labels are no longer a "nice to have" on a digital menu. They're the difference between a confident customer who taps Order Now and a hesitant one who closes the tab. The good news: the work is one-time, the maintenance is small, and the lift compounds for as long as your menu lives online.
If you'd rather skip the spreadsheet and get a clean digital menu with structured allergen and dietary fields built in, try OrderViaChat free — create your digital menu in minutes at orderviachat.com. WhatsApp ordering, QR menus, and a kitchen display system are all included, with no commission per order.