A guest with a severe peanut allergy orders your signature salad, but your server can't quickly confirm if the dressing contains tree nuts. This scenario plays out daily in restaurants where allergen data gets scattered across recipe cards, supplier sheets, and staff memory. Here's how to build a foolproof system that puts every allergen detail at your team's fingertips.
Why allergen information is crucial
Since 2014, restaurants in the EU are required to provide allergen information upon request from guests. This applies to all 14 official allergens: gluten, crustaceans, eggs, fish, peanuts, soy, milk, tree nuts, celery, mustard, sesame seeds, sulfites, lupin, and mollusks.
⚠️ Attention:
An error in allergen information can be life-threatening for guests. Additionally, you as a business owner are liable if you provide incorrect information.
The problem with scattered records
Most kitchens scatter allergen information across multiple locations:
- Recipes in a binder
- Allergens on sticky notes
- In the head chef's memory
- On ingredient packaging
Your chef takes a sick day or quits? That knowledge vanishes. During a Saturday night rush, nobody's digging through three different folders to answer an allergen question.
💡 Example situation:
Guest asks: "Does the Caesar salad contain gluten?"
Without a system, you check:
- Croutons (bread = gluten)
- Dressing (sometimes soy sauce = gluten)
- Worcestershire sauce (often contains gluten)
One missed ingredient = risk for the guest.
Build a master allergen database by ingredient
Start with every single ingredient you stock. Document which allergens live in each one. Check packaging labels or request allergen declarations from your suppliers - don't guess.
💡 Example ingredient database:
- Parmesan: Milk
- Soy sauce: Soy, Gluten
- Mayonnaise: Eggs
- Walnuts: Tree nuts
- Shrimp: Crustaceans
Most suppliers maintain allergen declarations - just ask for them. Store these digitally and update your database whenever you switch suppliers or introduce new products. One of the most common blind spots in kitchen management is assuming ingredients stay consistent across different suppliers.
Auto-calculate allergens for each recipe
Once you've mapped allergens to ingredients, you can automatically determine which allergens appear in each dish. Build recipe overviews that show every ingredient plus its allergen profile.
💡 Example: Caesar Salad
Ingredients and their allergens:
- Romaine lettuce: no allergens
- Parmesan: milk
- Croutons: gluten
- Anchovies: fish
- Mayonnaise: eggs
Caesar Salad contains: gluten, fish, eggs, milk
Track cross-contamination risks
Allergens sneak into dishes through shared equipment too. Map out which tools you use across different preparations and where contamination might occur.
- Fryer: fish and fries in the same oil
- Grill: bread and meat on the same surface
- Cutting board: nuts mixed with other ingredients
- Mixer: different dressings in sequence
⚠️ Attention:
Uncertain about cross-contamination? Always inform the guest. "May contain traces of..." beats taking a dangerous gamble.
Digital systems beat paper trails
Paper allergen lists disappear, get outdated, and become impossible to find during busy service. A digital system stores allergen data per ingredient and automatically calculates which allergens appear in each dish.
Digital registration advantages:
- Stays current when you modify ingredients
- Fast lookups during service
- Multiple staff members can access it
- No risk of losing critical information
Remember: any system only works as well as the data you feed it. You're still responsible for accurate allergen registration.
Train your team on allergen protocols
Ensure every team member knows where allergen information lives and how to access it quickly. Run practice scenarios where guests ask specific allergen questions.
💡 Training scenarios:
- "Is this dish gluten-free?"
- "I'm allergic to tree nuts, what can I eat?"
- "Does the pasta contain crustaceans?"
- "Can the chef make this without milk?"
How do you set up an allergen registration system?
Inventory all ingredients
Make a list of all ingredients you use. Check packaging for which allergens they contain and ask suppliers for allergen declarations. Update this list when you add new products.
Link allergens to recipes
For each recipe: add up all allergens from all ingredients. Don't forget garnishes, sauces, and oils. Also note possible cross-contamination via equipment.
Make information accessible to your team
Ensure all team members can quickly look up which allergens are in each dish. Practice scenarios and establish clear procedures for when in doubt.
✨ Pro tip
Audit your allergen declarations every 90 days by spot-checking 5 random ingredients against current supplier documentation. Suppliers often reformulate products without prominent notifications, and these changes can introduce new allergens.
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 track all 14 allergens for each dish?
Yes, you're legally required to provide information about all 14 EU allergens upon guest request. Even if your dish only contains 2 of them, you must be able to confirm the absence of the other 12.
What if I'm not sure whether an ingredient contains allergens?
Request an allergen declaration from your supplier immediately. If you're still uncertain, inform the guest "may contain traces of..." It's better to be cautious than take a dangerous risk.
How often should I update my allergen database?
Update whenever you change ingredients, suppliers, or recipes. Schedule monthly reviews to verify all information remains accurate and check if suppliers have modified their formulations.
Can I just say "may contain traces of all allergens" for everything?
Absolutely not - that's illegal. You must provide specific information about which allergens actually appear in each dish. Generic warnings don't substitute for accurate data.
What happens if I provide incorrect allergen information?
You're liable for any damage from incorrect information. This can result in food safety authority fines and damage claims from guests who become ill.
How do I handle dishes with complex sauces or marinades?
Break down every component of sauces and marinades into individual ingredients, then map allergens for each one. Many commercial sauces contain hidden allergens like modified starches or flavor enhancers.
Should I create separate prep areas for allergen-free dishes?
For severe allergen risks, dedicated prep areas eliminate cross-contamination. At minimum, use separate cutting boards, utensils, and clean surfaces thoroughly between allergen and non-allergen preparations.
⚠️ 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.
All your recipes in one place, forever
Recipes in heads, on notes, in folders — that doesn't work. KitchenNmbrs centralizes all your recipes with costs, allergens, and portions. Try it free for 14 days.
Start free trial →