What Spanish law requires of restaurants on allergens
If you serve food that comes out of your own kitchen (unpackaged), you have to tell the customer whether it contains any of the 14 allergens that must be declared. This obligation comes from Regulation (EU) No 1169/2011 on the provision of food information to consumers, developed in Spain by Royal Decree 126/2015 for food served unpackaged, such as the dishes on a set menu or an à la carte menu.
The rules allow two routes: giving the information in writing (on the menu, on a board, on a separate sheet) or giving it verbally, but only if the establishment has a written, registered system to back up that verbal information and the staff are trained to give it correctly. If you don't have that system in place, writing it down is the safe and simplest route.
This isn't loose bureaucracy: it's real protection for your customers with allergies or intolerances. Getting it wrong here isn't only a legal matter — it can mean serious harm to someone who trusted you.
The 14 allergens that must be declared, and where they hide
The list is always the same: gluten, crustaceans, eggs, fish, peanuts, soya, milk (dairy), nuts, celery, mustard, sesame, sulphites, lupin and molluscs. It seems easy to keep under control when you're thinking about the main dish, but the problem is almost never there.
It tends to hide in the accompaniments: a sauce made with cream or butter (dairy), a stock thickened with flour (gluten), the frying oil you've also used for a batter containing egg, a dressing with mustard, a bread roll topped with sesame, or olives and pickles containing sulphites. In a bar with a daily set menu, the typical danger spots are the soup, the sauce on the side and the bread on the table.
That's why checking the recipe "as written in the book" isn't enough: you also need to check whatever you add when plating up and whatever you use for frying or garnishing.
How to organise it internally: a sheet per dish and a trained team
The most practical method is to keep a sheet for each dish listing the ingredients with the allergens flagged. You update it the moment you change a recipe or a supplier, not "when there's time": switching to a different brand of sauce can bring in a new allergen without anyone noticing.
When a customer asks, the waiter checks the sheet rather than improvising from memory. That's the difference between a reliable answer and a dangerous guess. It's also worth setting minimum hygiene rules to prevent cross-contamination: separate utensils and surfaces for "gluten-free" or "dairy-free" dishes, for example.
And basic training is needed, repeated whenever the team changes or someone new joins for the busy season. It doesn't need to be a long course: it's about every member of staff knowing where the information is and how to check it in front of the customer.
How to show allergens on the menu: icons, letters or text per dish
Several written formats are valid. Icons with a key at the bottom are the most visual and work well on menus with lots of dishes. Initials next to each dish (with their own key) take up less space and suit set menus that change every week. Full text next to each dish is the clearest option, but it can overwhelm a long menu.
Choose according to the size of your menu: with few dishes, full text is viable; with many, icons or initials with a clearly visible key are more practical. What matters is that the key stays in plain sight, not tucked away on the back or in tiny print.
If you decide to use verbal information instead of (or alongside) the written kind, remember that you need the registered system available and trained staff: it isn't just a case of "the waiter knowing it" — you need something in writing to fall back on.
The online menu: let customers see allergens before they book
Your website's menu should say exactly the same as your printed one. If a customer checks the menu on their phone before booking, they should find the same allergens, the same badges and the same information they would see sitting at the table.
This is where a tool can genuinely help: WordNext's "Menu" block, available on every plan (including the free one), lets you build sections and dishes with prices, icons for the 14 allergens, badges such as vegetarian, vegan, spicy, gluten-free or recommended, and a "sold out" box that hides the dish from the website without deleting it. So when something changes on the printed menu, you update the online version at the same time.
You can see how it looks on the menu of this example blog: it belongs to a fictional restaurant built with WordNext, not a real business, but it's useful for seeing the format. If you also take bookings through your website, it makes sense for customers to be able to check the allergen menu before booking, as on the booking page of this same example blog.
What to do when a customer mentions an allergy or intolerance
A short protocol avoids most scares. First, always ask which specific allergen is involved: not all "intolerances" are the same, and the right answer varies enormously from case to case. Second, check the dish's sheet before answering — don't reply from memory.
Third, warn the kitchen clearly, not just "keep an eye on table 4". Fourth, avoid cross-contact during preparation: clean utensils, a separate surface where necessary. And fifth, be honest if you cannot guarantee the complete absence of traces: it's better to say "I can't promise you zero risk" than to promise something you can't control.
Frequently asked questions
Is it compulsory to show allergens on the menu of a bar or restaurant in Spain?
Yes. If you serve unpackaged food, you must declare the 14 mandatory allergens, under Regulation (EU) No 1169/2011 and Royal Decree 126/2015.
Can I give allergen information verbally, or does it have to be in writing?
You can give it verbally, but only if you have a written, registered system available and your staff are trained to pass the information on correctly. If you don't have that in place, the written route is the safest.
How do I keep allergens up to date when the menu or set menu changes often?
With a sheet per dish that you review every time a recipe or a supplier changes. Update the online menu at the same time as the printed one so the two never drift apart.
Is a dish marked "gluten-free" suitable for coeliacs?
Not necessarily. A dish containing no gluten as an ingredient doesn't guarantee there's been no cross-contamination in the kitchen. Explain that to the customer and don't promise "trace-free" lightly.
This blog belongs to an example restaurant built with WordNext. If you'd like something similar for your own, you can create your restaurant website for free.