Allergen information that's no longer accurate can be life-threatening for guests. If recipes change often but allergen registration doesn't keep up, you're putting customers at serious risk. Setting up a reliable system that tracks every recipe change is essential.
Why this is so dangerous
A recipe that once contained no nuts suddenly gets a nut sauce. A chef adds oat cookies to a dessert without mentioning it. Small changes can have fatal consequences for guests with allergies.
⚠️ Heads up:
In the Netherlands, restaurants are legally required to provide correct allergen information. If you provide incorrect information, you face liability risk.
The main causes of outdated information
- Seasonal changes: Different supplier, different ingredients
- Chef experiments: Additions without documentation
- Cost savings: Cheaper ingredient with different composition
- No central registration: Everyone keeps their own lists
- Time pressure: No time to update allergen list
💡 Example:
Your carbonara always contained only egg, cheese and bacon. But your new chef now adds parmesan cheese from a different supplier:
- Old cheese: milk only
- New cheese: also contains nuts (cross-contamination in factory)
- Guest with nut allergy: life-threatening reaction
Your allergen list still says: milk and egg only.
Signs that your system is no longer accurate
Check these red flags regularly:
- Different answers: Chef says A, server says B
- Uncertainty among staff: "I'm not sure"
- Outdated documentation: Allergen list older than 3 months
- New suppliers: Different brands, different compositions
- Complaints about taste: Dish tastes different than expected
The airtight control system
Here's how to build a system that automatically adapts to changes:
💡 Example system:
Every Monday the chef checks all recipes for the week:
- Have any ingredients been replaced?
- New supplier for existing product?
- Experimental additions become permanent?
- Cross-contamination possible due to new equipment?
For every YES: update allergen registration.
Digital vs. paper registration
Paper lists quickly become outdated. With every recipe change, you have to manually update all lists. If you forget one list, the information is no longer accurate - a mistake that costs the average restaurant EUR 200-400 per month in potential liability issues and lost customer trust.
Digital registration works differently: change the recipe, and the allergen info updates automatically. All employees see the new information immediately.
The new supplier protocol
New supplier = new risks. Even if it looks like the "same" product:
- Always ask for new specifications (even for known brands)
- Check for cross-contamination in factory (often listed in small print on label)
- Test small quantity first before adjusting recipes
- Update allergen info before serving the first plate
⚠️ Heads up:
"May contain traces of..." on packaging is not a precaution. It means cross-contamination is possible. Treat it as actually present.
What to do when in doubt
If you're not 100% sure about allergens in a dish:
- Say you're not sure (honesty prevents accidents)
- Offer an alternative you're confident about
- Look it up immediately for next time
- Document the question to prevent repetition
Many restaurants use digital tools to maintain allergen information centrally and automatically synchronize it with recipe changes.
How do you build a reliable allergen system? (step by step)
Inventory all current recipes and ingredients
Make a list of each dish on your menu and all ingredients in it. Also check sauces, garnishes and oils you use. Ask suppliers for current specifications of all their products.
Register all 14 EU allergens per ingredient
Go through each ingredient and check which of the 14 mandatory allergens it contains. Pay special attention to 'may contain traces of' texts on packaging. Treat these as actually present.
Create a weekly update routine
Schedule 15 minutes every Monday to review recipe changes. Check if new ingredients have been added or suppliers have changed. Update allergen registration immediately with any change.
Train your team on the new system
Make sure everyone knows where the current allergen info is located and how to access it. Make clear agreements about what to do when in doubt: always safety first.
Test the system with trial questions
Ask your team random questions about allergens in different dishes. Check if everyone gives the same answers and if these match your registration. Adjust where needed.
✨ Pro tip
Photograph every ingredient label within 48 hours of delivery, focusing on allergen warnings and 'may contain' statements. This creates a digital trail you can reference weeks later if questions arise about specific batches.
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
How often should I update my allergen registration?
With every recipe change, new supplier or seasonal switch. Plan a full check of all dishes at least monthly. When in doubt: better too often than too little.
What if a guest asks about allergens and I'm not sure?
Say honestly that you're not sure and offer an alternative dish you're confident about. Never guess - a wrong assessment can be life-threatening.
Do I also need to register cross-contamination in my kitchen?
Yes, if you process nuts and then make other dishes without thorough cleaning, cross-contamination can occur. Register this as 'may contain traces of nuts'.
Can I rely solely on information from my supplier?
Supplier information is your foundation, but you must track which ingredients you use in which dish. A supplier doesn't know how you prepare your dishes.
What happens if I provide incorrect allergen information?
You face liability risk if a guest gets sick from incorrect information. In the worst case, this can lead to a lawsuit and damages.
How do I handle seasonal menu changes with allergen tracking?
Create a seasonal checklist that flags every ingredient substitution. New seasonal items often come from different suppliers with different allergen profiles than your regular ingredients.
⚠️ 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.
Make better decisions with real numbers
Should you change your menu? Raise prices? Test a new concept? KitchenNmbrs simulates scenarios with your own data. Try it free for 14 days.
Start free trial →