Returning guests with allergies create serious liability if you don't track their dietary restrictions properly. That regular customer with the shellfish allergy expects you to remember her needs, but can you recall exactly which items she avoids? Smart guest profiling protects both your customers and your business.
Why guest profile data is crucial for allergen management
Allergens aren't something you guess about. One mistake sends someone to the hospital. With familiar faces, you might think you remember their restrictions, but memory fails during rush periods. Staff turnover makes this even worse.
⚠️ Heads up:
You're legally required to provide accurate allergen information. If you give a guest wrong information based on assumptions, you're liable for the consequences.
What guest data you need to record
Basic contact info won't cut it for allergen management. You need detailed records that actually protect people:
- Specific allergens: Not "nuts" but "cashews and almonds"
- Severity level: Is cross-contamination dangerous or only direct intake?
- Preferred dishes: What does this guest usually order?
- Last visit: When were they here last?
- Notes: Special details the team needs to know
💡 Example:
Guest: Mrs. Johnson, regular customer since 2023
- Allergy: Shellfish (shrimp, lobster, mussels)
- Sensitivity: Cross-contamination dangerous
- Preference: Always the steak, never fish
- Note: Always asks about sauce ingredients
Result: Team immediately knows what she can and can't eat
Digital vs. paper guest registration
Paper systems fail miserably for allergen tracking. Notes get lost, handwriting becomes illegible, and you can't search through scattered information quickly enough during service.
Digital systems solve these problems:
- Search by name, phone number, or allergen
- Automatic alerts when making reservations
- Accessible to the whole team
- Backup and history preservation
Linking with menu and recipes
Guest data means nothing if you can't connect it to your actual menu items. For every guest with restrictions, you need instant answers:
- Which dishes are completely safe?
- Where's the cross-contamination risk?
- What alternatives can you offer?
💡 Example:
Mr. Smith has a gluten allergy and is reserving for tonight
- System shows: 8 of 24 dishes are gluten-free
- Alert: Fryer is also used for breaded items
- Suggestion: Grilled fish with potatoes (his favorite dish)
Server can advise immediately without asking the chef
Training your team
Even perfect systems fail if your staff doesn't use them correctly. This is a pattern we see repeatedly in restaurant financials - liability claims spike when teams skip documentation steps. Make sure everyone understands:
- How to enter new guest data
- Where to find allergy info in reservations
- When extra caution is needed
- How to handle unknown allergies
Build it into your standard routine: ask every new guest about allergies and record this information immediately.
Legal aspects and liability
In the EU, you must provide allergen information about the 14 main allergens for every service. This includes returning guests. You can't rely on "it worked fine last time" as proof that a dish remains safe.
⚠️ Heads up:
Recipes change, suppliers switch ingredients. What was safe last month might be dangerous now. Always verify current ingredient lists.
Practical tools and systems
Effective guest profile management requires systems that connect allergen data directly to your recipes. The right software provides:
- Guest profiles with complete allergy history
- Automatic matching with current menu
- Alerts for risky combinations
- Overview of safe alternatives
This prevents dangerous mistakes and gives your team confidence when advising guests about their options.
How do you set up guest profile management? (step by step)
Collect existing guest data
Go through your reservation books and notes from the past years. Make a list of regular guests and their known allergies. Ask your team about guests they remember with specific restrictions.
Choose a digital system
Select software that can link guest profiles to menus and allergen information. Make sure the system is accessible to your whole team and easy to search.
Enter guest data with allergy details
Start with your 20 most loyal guests. Note not only which allergens, but also the severity level and preferred dishes. Update this information with each visit.
Link profiles to your menu
Make sure each guest profile automatically shows which dishes are safe and which are not. Test this system with a few known allergy cases before fully implementing it.
Train your team in using it
Teach everyone how to create new profiles, update existing ones, and look up allergy info. Make it a routine to check if any allergies are known with each reservation.
✨ Pro tip
Review and update your top 20 guest profiles every 90 days to catch recipe changes, new allergies, or preference shifts. This 15-minute task prevents dangerous assumptions about familiar customers.
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 legally store guest allergy information?
Yes, if it's necessary for safe service. Store this data securely and use it only for allergen management. Guests have the right to view their data or request deletion.
What if a guest develops a new allergy since their last visit?
Update their profile immediately and alert your team. Allergies can develop at any age, so ask about changes with each reservation.
How long should I keep guest allergy data?
There's no legal requirement for retention periods. Most restaurants keep data for active guests (visited within 2 years) and delete older profiles to maintain database efficiency.
What if my staff forgets to check allergy information?
Make allergy checks part of your standard reservation procedure. Automatic system alerts help, but staff training and discipline remain crucial for guest safety.
Can I share guest profiles between multiple restaurant locations?
Technically possible, but watch privacy requirements. Guests must know their data is shared, and menus differ between locations, so always verify local ingredients.
How do I handle guests who don't remember their exact allergies?
Never guess or rely on vague descriptions. Ask them to check with their doctor or allergist before dining. It's better to lose a sale than risk someone's health.
What should I do if a guest's allergy isn't in my system's preset options?
Add custom allergy fields or detailed notes. Many systems allow free-text entries for unusual allergies or specific ingredient sensitivities that don't fit standard categories.
⚠️ 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 →