Central allergen management ensures all locations provide guests with the same, correct information. Without a unified system, you get different answers per location, which creates risks and confusion. Managing allergen statements uniformly across all your locations protects both your guests and your business.
Why central allergen management is crucial
If you have multiple locations, each one must be able to provide the same allergen information. A guest who asks about nuts in the carbonara at location A should get the same answer as at location B.
⚠️ Heads up:
Different answers per location about allergens can lead to serious health risks and legal problems. EU regulations require consistent, correct information.
Without a central system, this happens:
- Chef A says: "Our pasta contains no nuts"
- Chef B says: "I'm not sure, we use different suppliers"
- Guest with a nut allergy gets contradictory information
The 14 mandatory allergens for all locations
Each location must be able to provide information about these EU-mandated allergens:
- Gluten (wheat, rye, barley, oats, spelt, kamut)
- Crustaceans (shrimp, crab, lobster)
- Eggs
- Fish
- Peanuts
- Soy
- Milk (including lactose)
- Tree nuts (almond, hazelnut, walnut, cashew, etc.)
- Celery
- Mustard
- Sesame seeds
- Sulfur dioxide and sulfites (>10 mg/kg)
- Lupin
- Mollusks (mussels, squid)
Problems with decentralized allergen management
💡 Example:
You have 3 locations. Location A uses supplier X for pesto, location B uses supplier Y. Supplier X uses pine nuts (tree nuts), supplier Y doesn't.
Without a central overview, nobody knows this difference. Result: location A says "contains nuts", location B says "no nuts".
Common issues include:
- Different suppliers: Each location buys from different suppliers
- Recipe variations: Chef A adds cashews, chef B adds almonds
- Outdated information: Supplier changes composition, but not all locations know about it
- Staff turnover: New employees don't know the allergen status
Setting up central allergen management
A central system starts with one source of truth for all recipes and ingredients. After managing kitchen operations for nearly a decade, I've seen how critical this foundation is for consistent allergen reporting.
💡 Example of central setup:
- Head office: Manages master recipe list with allergens
- Location 1, 2, 3: Use the same recipes and ingredient list
- Updates: Changes are implemented centrally and pushed to all locations
- Access: Each location can look up the correct info in real-time
Digital vs. paper allergen management
Paper lists per location create multiple problems:
- Different versions per location
- Updates don't reach all locations
- Looking things up takes time during busy service
- Loss of documentation
Digital central management offers clear advantages:
- One database for all locations
- Automatic updates to all locations
- Quick lookup via smartphone/tablet
- Always the latest version available
⚠️ Heads up:
Digital systems help with registering and centrally managing allergens, but you remain responsible for correctly filling in and keeping the information up-to-date.
Practical implementation per location
Each location needs access to the same information, but adapted to their specific situation:
💡 Example implementation:
Location A and B have the same carbonara, but A uses pancetta from supplier X, B from supplier Y:
- Central recipe: Carbonara with eggs, milk, wheat (pasta)
- Location-specific: A notes supplier X pancetta (contains celery), B supplier Y (no celery)
- Result: Both locations give correct, but different answers about celery
Training and communication with teams
The most advanced system won't work without proper team training:
- Weekly briefing: Discuss changes in allergens
- Access for everyone: Not just the chef, but also servers should be able to look up info
- Standard responses: "Let me look that up" is better than guessing
- Escalation: When in doubt, always refer to the chef or manager
Costs and time investment
Central allergen management takes time to set up, but saves daily hassle:
- One-time: 2-4 hours per location to review all recipes
- Weekly: 30 minutes to implement changes
- Daily: 2 minutes per location to check for updates
Digital systems make this process more efficient by automatically sending central updates to all locations.
How do you set up central allergen management? (step by step)
Inventory all recipes and ingredients
Collect all recipes and ingredient lists from each location. Also note supplier differences per location. This becomes your base database.
Register allergens per ingredient centrally
Go through all ingredients and note which of the 14 EU allergens they contain. Check supplier specifications and product labels. Create this in one central system.
Automatically link allergens to dishes
Once each ingredient has its allergens, you can automatically see which allergens are in each dish. This prevents manual errors and saves time.
Give all locations access to the same system
Make sure each location can access the same information via smartphone, tablet, or computer. Train your teams to use the system during service.
Create an update procedure for changes
Assign one person responsible for updating allergen information. New suppliers or recipe changes must be implemented centrally and pushed to all locations.
✨ Pro tip
Review your top 12 dishes across all locations within the first 30 days of setup. This covers roughly 75% of daily allergen questions and gives you immediate consistency where it matters most.
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
Does each location need to use the same suppliers for consistent allergen information?
No, that's not necessary. You can use different suppliers, but you must register per location which allergens are in the specific products. The central system keeps track of these differences.
What if a supplier changes the composition of a product?
Suppliers are required to communicate changes in allergens. Make sure this information is updated centrally and communicated to all locations. Check product specifications regularly.
Can locations adjust allergen information themselves in the central system?
It's better to assign one person responsible for updates to prevent errors. Locations can report changes, but the central administrator implements them across all locations.
How do I prevent teams from giving different answers about the same dish?
Train your teams to always consult the central system, not rely on memory. Standard phrases like "Let me look that up" work better than guessing, and create consistency across all locations.
⚠️ 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 →