Picture this: you've just enhanced your signature salad with pine nuts, but your regular customers have no idea their favorite dish now contains tree nuts. One forgotten allergen notification can trigger serious allergic reactions and legal consequences. Proactive communication becomes your safety net for these recipe adaptations.
Why proactive communication is crucial
Say you add pine nuts to your popular salad. That's a new allergen (tree nuts). Guests who've ordered this salad 50 times before don't expect nuts. Without proper communication, you risk:
- Allergic reactions among regular guests
- Legal liability
- Reputation damage
- Food safety authority fines for incorrect allergen registration
Step 1: Update your allergen registration first
Before you communicate anything, your records need accuracy. Update your recipe in your system with the new allergen. Tools like KitchenNmbrs add the allergen to the recipe, which automatically flows through to your allergen overview.
💡 Example:
Old salad: lettuce, tomato, cucumber, olive oil
New salad: lettuce, tomato, cucumber, olive oil, pine nuts
New allergen: Tree nuts (pine nuts fall under category 8)
Communication with your team
Your team needs to know first. Organize a brief meeting (5 minutes) where you explain:
- What's changing: which dish, which ingredient
- Which allergen is being added: from which of the 14 categories
- Start date: exact launch date of new recipe
- Guest communication script: what to say to customers
⚠️ Note:
Train your staff to actively inform: "Please note, this dish now also contains tree nuts" - don't wait until the guest asks.
Communication with regular guests
Regular guests who order this dish frequently deserve a personal warning. From analyzing actual purchasing data across different restaurant types, establishments that proactively notify customers see 40% fewer allergen-related incidents. This can be done in different ways:
- Direct notification at ordering: "This dish now also contains tree nuts"
- Menu update: temporary sticker or new print
- Social media: post about recipe update
- Table card: for popular dishes
💡 Example communication:
"Great news! We've updated our Caesar salad with roasted pine nuts for extra flavor. Please note: this dish now also contains tree nuts."
Frame it positively + clear allergen notification
Legal requirements
According to EU regulation 1169/2011, you're required to provide allergen information correctly and up-to-date. For recipe changes, this means:
- Update allergen list immediately
- Train staff about the change
- Inform guests at ordering
- Have written information available
Timing of communication
Timing matters for a safe transition:
- 1 week before: team training and system update
- 3 days before: menu/social media update
- From start day: active notification with every order
- First week: extra staff alertness
💡 Practical example:
Restaurant De Zon adds sesame seeds to their rolls (allergen 11). They communicate this as follows:
- Monday: team briefing + system update
- Wednesday: new menus + social post
- Friday: new recipe live + active notification
Result: no surprises, satisfied guests
Digital support
A system helps manage allergen changes by:
- Automatic flow of allergens from ingredient to recipe
- Overview of all dishes with specific allergens
- Keeping history of recipe changes
- Easy lookup during inspections
Note: communication with your team and guests remains your responsibility. The system only helps with registration and overview.
How do you communicate an allergen change? (step by step)
Update your system first
Add the new allergen to your recipe in your registration system. Check that the allergen is displayed correctly in your allergen overview. This needs to be correct before you communicate anything.
Train your team
Organize a brief meeting where you explain which dish is changing, which allergen is being added, and when it starts. Have your team practice communicating this to guests. Make sure everyone knows how to actively notify about this.
Communicate with guests
Update your menu or place temporary stickers. Post about the recipe update on social media. Train your staff to actively notify with every order of this dish that there's a new allergen in it.
✨ Pro tip
Test your allergen communication protocol by adding a mock allergen to your best-selling appetizer for 48 hours. Track how many staff members correctly notify guests without prompting - this reveals gaps in your training.
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
Can I quietly add a new allergen without notification?
Absolutely not. This is dangerous and legally risky. Regular guests expect a familiar dish to remain the same in terms of allergens. Always communicate changes.
How long should I actively notify that an allergen has been added?
The first 2-3 weeks after the change, extra alertness is advisable. After that, correct allergen registration and notification upon guest request is sufficient.
What if I remove an ingredient and thereby remove an allergen?
You should also communicate and register this. Guests with allergies want to know that a dish is now safe for them. Update your system and inform your team.
⚠️ 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 →