Here's something that keeps me up at night: one mishandled allergen request can destroy a restaurant's reputation overnight. Most establishments wing it with scribbled notes and verbal communication. But guests' lives depend on getting this right every single time.
Why allergen registration matters so much
An allergic reaction can become life-threatening within minutes. As a restaurant owner, you're legally required to provide allergen information and ensure accuracy. Poor registration leads to serious incidents and massive liability exposure.
⚠️ Note:
EU legislation (Reg. 1169/2011) requires restaurants to provide correct allergen information. Without proper registration during an incident, you face serious liability risk.
The 14 EU-mandated allergens
You must always indicate whether a dish contains any of these 14 allergens:
- Gluten (wheat, rye, barley, oats, spelt, kamut)
- Crustaceans (shrimp, lobster, crab)
- Eggs
- Fish
- Peanuts
- Soy
- Milk (including lactose)
- Nuts (almond, hazelnut, walnut, cashew, etc.)
- Celery
- Mustard
- Sesame seeds
- Sulfites (>10 mg/kg)
- Lupine
- Mollusks (mussels, squid)
Step-by-step registration process
Effective registration starts before guests sit down. You need a system that flows seamlessly from ordering to kitchen execution.
💡 Example registration:
Guest asks: "Does the carbonara contain gluten? I'm a celiac patient."
- Register: Table 5, carbonara, NO GLUTEN
- Note: Celiac (severe allergy)
- Communicate to kitchen: ALLERGEN ALERT
- Confirm with guest: "We'll prepare your carbonara gluten-free"
Digital vs. paper registration
Many restaurants still rely on notes and verbal communication. This dramatically increases error risk - a mistake that costs the average restaurant EUR 200-400 per month in wasted ingredients and potential liability issues. Digital systems provide structure and accountability.
Benefits of digital registration:
- No lost notes
- Direct link to dish and table
- Automatic notification to kitchen
- Proof that you acted correctly
Communication to the kitchen
The kitchen needs clear allergen alerts. You can't rely on just a note - you need a foolproof system.
💡 Kitchen communication example:
Table 12 - Salmon - ALLERGEN: NO NUTS
- Use clean pan and utensils
- Check all sauces and garnishes
- Avoid cross-contamination
- Chef verifies before serving
Keep your registrations
Allergen registrations become crucial evidence if incidents occur. Store them for at least 2 years, just like HACCP records. During an incident, you must demonstrate proper procedures were followed.
⚠️ Note:
Apps don't automatically register requests. You must input allergen information manually. The app simply organizes and stores your data.
Training your team
Everyone with guest contact must understand allergen protocols. From servers to cooks: everyone needs to know the system.
Essential training topics:
- Recognize the 14 mandated allergens
- Registration process step by step
- What to do when uncertain (always ask!)
- Prevent cross-contamination in the kitchen
How do you register an allergen request? (step by step)
Note the request immediately
As soon as a guest makes an allergen request, write it down. Note the table, dish, and specific allergen. Ask follow-up questions if unclear - one extra question is better than a mistake.
Check your dish information
Verify whether the requested dish contains the allergen. Look not only at main ingredients, but also at sauces, garnishes, and cross-contamination. If in doubt: ask the kitchen.
Communicate to the kitchen
Clearly communicate the allergen request to the kitchen. Use a fixed format: table, dish, allergen. Make sure the chef confirms they understand.
Confirm with the guest
Tell the guest what you'll do. "We'll prepare your pasta without nuts and use a clean pan." This builds confidence and shows you take it seriously.
Save the registration
Store the allergen request in your system. This is important proof that you acted correctly. Keep it for at least 2 years, just like other food safety registrations.
✨ Pro tip
Implement a 30-second allergen verification call between service and kitchen staff for every request. This double-check system catches 90% of potential errors before dishes leave the pass.
Calculate this yourself?
In the KitchenNmbrs app you can do this in just a few clicks. 7 days free, no credit card.
Was this article helpful?
Frequently asked questions
Do I need to keep all allergen requests?
Yes, keep all registrations for at least 2 years. This becomes crucial evidence if questions arise later about how you handled an allergen request.
What if I'm not sure whether a dish contains an allergen?
Always err on the side of caution and say 'no' to the guest. It's better to refuse an order than risk someone's health.
Can a digital app automatically register allergen requests?
No, you must manually enter allergen requests every time. Apps help organize and store this information, but can't replace human input.
What happens if I register an allergen request incorrectly?
This can trigger life-threatening allergic reactions in guests. You also face serious legal liability if proper procedures aren't followed.
Does my entire team need to know how allergen registration works?
Absolutely - everyone with guest contact or food preparation duties must know the protocol. Allergens are everyone's responsibility, from servers to kitchen staff.
How should I handle guests who claim multiple severe allergies?
Take every claim seriously and document each allergen separately. Consider recommending simpler dishes with fewer ingredients to minimize cross-contamination risk.
⚠️ EU Regulation 1169/2011 — Allergen Information — https://eur-lex.europa.eu/eli/reg/2011/1169/oj
The allergen information on this page is based on EU Regulation 1169/2011. Recipes and ingredients may vary by supplier. Always verify current allergen information with your supplier and communicate this correctly to your guests. KitchenNmbrs is not liable for allergic reactions.
In the UK, the FSA enforces allergen regulations under the Food Information Regulations 2014.
📚 Sources consulted
- EU Verordening 852/2004 — Levensmiddelenhygiëne (2004) — Official source
- EU Verordening 853/2004 — Hygiënevoorschriften voor levensmiddelen van dierlijke oorsprong (2004) — Official source
- EU Verordening 1169/2011 — Voedselinformatie aan consumenten (2011) — Official source
- NVWA — Hygiënecode voor de horeca (2024) — Official source
- NVWA — Allergenen in voedsel (2024) — Official source
- Codex Alimentarius — International Food Standards (2024) — Official source
- FSA — Safer food, better business (HACCP) (2024) — Official source
- BVL — Lebensmittelhygiene (HACCP) (2024) — Official source
- Warenwetbesluit Bereiding en behandeling van levensmiddelen (2024) — Official source
- WHO — Foodborne diseases estimates (2024) — Official source
Food Standards Agency (FSA) — https://www.food.gov.uk
The HACCP standards shown in this application are for informational purposes only. KitchenNmbrs does not guarantee that displayed values are current or complete. Always consult the FSA or your local authority for the latest regulations.
Written by
Jeffrey Smit
Founder & CEO of KitchenNmbrs
Jeffrey Smit built KitchenNmbrs from 8 years of hands-on experience as kitchen manager at 1NUL8 Group in Rotterdam. His mission: give every restaurant owner control over food cost.
Allergen registration that's truly compliant
EU legislation requires allergen documentation for every dish. KitchenNmbrs automatically generates allergen matrices based on your ingredients. Try it free for 14 days.
Start free trial →