Allergens and ingredients on the digital menu: the information that protects the guest and the hotel
In a hotel restaurant, a guest’s allergy is not asked about once: it comes up at breakfast, at the pool, in room service and at the Saturday banquet. Here is how each dish gets labeled, which filters the guest sees, and how the note reaches the kitchen without getting lost on the way.
A guest with a peanut allergy does not eat once in your hotel’s restaurant: breakfast, something at the pool, dinner, and at eleven at night a room service order. Four revenue centers, four different people taking the order, and in room service nobody in sight at all. If the allergen information lives in the memory of the afternoon server, by eleven at night it no longer exists.
Why it matters more in a hotel than in a street restaurant
In an independent restaurant the diner arrives, mentions the allergy, eats and leaves. The information lives as long as the meal. In a hotel, the guest stays three nights and consumes in several places that do not share a server, a shift or sometimes even a kitchen. The allergy mentioned at the front desk on check-in has to reach the pool bar two days later.
On top of that, a hotel has consumption with nobody in front of the guest. The guest orders room service from a phone, or orders from the table through a QR code, and there is no one to ask whether there is any restriction. The digital menu has to ask that question on its own, and it has to have the answer ready for every dish. If it does not, the guest orders blind or does not order at all.
And there is a third reason: responsibility. When something goes wrong with a diner from the street, the problem belongs to the restaurant. When it goes wrong with a guest, the problem belongs to the hotel, with its name, its folio and its review. Allergen information on the digital menu protects the guest first, and the hotel immediately after.
Three levels of information that should not be mixed
The most common confusion is treating ingredients, allergens and diets as if they were the same thing. They are not, and when they are blended into a single text description, the guest cannot find what they are looking for and the kitchen does not know what is mandatory. It is worth separating them at the catalog level.
| Level | What it is | Who uses it | Example |
|---|---|---|---|
| Ingredients | What the dish contains, in order of importance | The curious guest and the server who describes it | Salmon, asparagus, butter, lemon |
| Allergens | The components that can cause a reaction | The guest with an allergy and the kitchen | Fish, dairy |
| Diets | The eating patterns the dish complies with | The guest who chooses by conviction or health | Gluten-free, suitable for vegetarians |
Ingredients are information. Allergens are safety. Diets are preference. The digital menu should show all three, but with a different hierarchy: the allergen cannot depend on the guest reading the whole description; it has to be marked with an icon or a label visible at first glance.
How a dish gets labeled: attributes, not text
The original mistake on many hotel digital menus is writing allergens inside the dish description: “Contains dairy and tree nuts”. That is free text. It cannot be filtered, it cannot be translated consistently, it does not reach the kitchen as data, and every person entering it writes it differently. The result is a menu where one dish says “contains walnuts”, another says “with tree nuts” and another says nothing, because whoever entered it forgot.
The right way is a product attribute in the catalog: a closed list of allergens, defined once for the whole hotel, ticked per dish with checkboxes. Fish, shellfish, dairy, egg, gluten, peanut, tree nuts, soy, sesame, celery, mustard, sulfites. The chef and the food and beverage manager decide the list, according to what regulation requires where the hotel operates and what the kitchen actually handles.
The dish inherits from the ingredient
When the catalog has recipes, the allergen is marked on the ingredient and the dish inherits it. If the house sauce contains peanut, every dish that uses that sauce is flagged without anyone having to remember. And if one day the recipe changes and the peanut leaves the sauce, it changes in one place. That is the strongest argument for not entering allergens dish by dish as text.
Contains, may contain, free from
A well-built attribute distinguishes three states: contains the allergen, may contain it through cross-contamination in the kitchen, and guaranteed free from it. The distinction matters because a guest with a severe allergy needs to know whether the kitchen can guarantee absence, not just whether the ingredient is in the recipe. And the kitchen needs to know which dishes it can promise and which it cannot.
The filters the guest sees
When the allergen is an attribute, the digital menu can offer filters. The guest who opens room service from the room ticks “gluten-free” and “dairy-free”, and the menu shows only what can be ordered. No need to read sixty descriptions or call the kitchen extension to ask. The decision is the guest’s, with complete information and no intermediaries.
The filter has to be honest. If a dish is marked “may contain” and the guest filtered for “free from”, that dish does not appear, or appears with the warning visible. The digital menu must never make a promise the kitchen did not sign off on. That is why the attribute states are defined with the chef, not with whoever designs the menu.
A detail guests appreciate: the filter chosen at breakfast can be remembered at dinner. If the digital menu is tied to the stay, the preference travels with the guest for the three days without having to be set again at every revenue center. That continuity is something a street restaurant cannot offer and a hotel can.
The note to the kitchen: from the table to the kitchen display without losing the allergy
Labeling the catalog properly solves half the problem. The other half is that the allergy declared by the guest travels with the order to the kitchen station and is visible at the moment of preparation. A flawless digital menu is useless if the server writes “no walnuts” on a napkin and the napkin stays at the bar.
- The allergy is captured on the order as data, not as a free comment, so it appears highlighted on the kitchen display.
- The kitchen display shows the alert on the dish line and in the order header, so both the cook assembling the plate and the person expediting it see it.
- If the dish ordered contains the declared allergen, the order stops before reaching the kitchen and asks the server to confirm.
- In room service, the allergy declared on the order is printed on the kitchen ticket and on the slip that travels with the tray.
- When the allergy was recorded at the front desk on check-in, the point of sale shows it when the room charge is opened at any revenue center.
The last point is what connects the restaurant to the rest of the hotel. If the guest told the front desk, that information belongs to the stay, not to a table. When the pool server opens the room charge (Room charge) and sees the alert before taking the order, the hotel is working as a single operation. When the server does not see it, every revenue center starts from zero.
Who keeps the information current
An allergen catalog is a snapshot of the day it was entered. The recipe changes, the mayonnaise supplier changes, the new chef adds sesame to the salad. If nobody reviews it, the digital menu keeps promising what is no longer true, which is worse than promising nothing.
Responsibility has to have a name. In most hotels it works like this: the chef owns the recipe and therefore the allergen; every recipe change requires reviewing the checkboxes before the dish goes back on the menu. The food and beverage manager reviews once a month, with the list of active dishes in hand. And purchasing gives notice when a supplier changes product, because the allergen in an industrial ingredient can change without the name changing.
Illustrative example: how much work it is
The figures below are invented to show the calculation; they do not describe any hotel. Suppose a menu of 60 active dishes across the restaurant, the pool and room service. Marking allergens for the first time, with the chef and the ingredient list at hand, takes about 4 minutes per dish: 60 × 4 = 240 minutes, that is, 4 hours of one afternoon. Every month 6 dishes change; reviewing their checkboxes takes 6 × 4 = 24 minutes. And if the menu is in two languages, the attribute is translated once for the whole hotel, not dish by dish, because the label is the same everywhere.
Four hours once and less than half an hour a month. Compared with what a single allergic reaction of a guest in room 214 costs, with the ambulance, the review and the call from the owner, the arithmetic needs no further explanation.
Room service and the pool: where there is nobody to ask
The two revenue centers where allergen information is needed most are the two with the least staff available to give it. In room service (Room service), the guest orders from bed without talking to anyone; the digital menu is the only server. At the pool, the server covers twenty loungers at a time, with music, with children, and the question “any allergies?” gets lost easily.
In both cases the solution is the same: the attribute in the catalog, the filter on the menu, the alert on the order and the note on the kitchen ticket. What changes is the presentation. In room service the label has to be large and visible on the phone. At the pool the order is taken on the server’s handheld and the alert must appear on that screen before sending to the bar, without having to look for it.
A secondary benefit few people calculate: the guest with a dietary restriction who easily finds what to order, orders. The one who does not find it leaves the hotel to look elsewhere. Allergen information is not only protection; it is revenue per occupied room that stays in the building instead of walking out the door.
In a hotel, the guest’s allergy has to travel with the stay across every revenue center, including the ones with no server present. That is only possible if the allergen is a catalog attribute, inherited from the ingredient, filterable on the digital menu and visible on the kitchen ticket.
What to do this week
- Define with the chef the closed list of allergens for your hotel and the three states: contains, may contain, free from.
- Open the digital menu from a phone as if you were a guest with a gluten allergy, and note how many dishes you can identify with confidence.
- Trace how an allergy declared at the table reaches the kitchen today: on what paper, on what screen, at what point it gets lost.
- Ask the front desk what happens with an allergy a guest mentions on check-in, and whether the restaurant sees it when opening the room charge.
- Schedule the allergen entry afternoon with the chef, dish by dish, starting with the room service items.
- Name the person responsible for the monthly review and write down the date of the first one.
In Inn Restaurant, allergens and diets are catalog attributes, inherited from the recipe, filterable on the digital menu (Digital menu) and highlighted on the kitchen display at every revenue center. If you want to see how an allergy travels from the front desk to the room service tray, book a 15-minute demo (contact).
More articles
Dish photos on the hotel’s digital menu: when they help and when they hurt
A photo on the digital menu of your hotel’s restaurant is a promise the kitchen has to keep at every table, in every room and on every lounger. Here are the criteria for deciding which dishes deserve one, how to keep the real plate consistent with the image, and how the effect shows up in the sales mix.
Kids’ menu, vegan menu and gluten-free menu in the hotel: how to catalog them without multiplying the menu
Every time a hotel restaurant adds a special menu, it adds a menu to maintain, translate, cost and explain at the front desk. Here is the alternative: a single catalog with attributes per dish, where the guest filters what they need and the kitchen sees the same thing as always.
Changing prices for high season: how to do it in a minute without reprinting anything
Every December and every Easter the hotel restaurant lives the same scene: menus with stickers over the old prices, servers charging the old price and a controller who finds the mix at month end. A price list with a start and end date solves all three.
Your hotel’s restaurant already sells well. Now the hotel needs to know it.
Fifteen minutes, with your menu and your tables. Nothing to install.