QR menus · 7 min read
How to Introduce an Allergy-Aware QR Menu During Service
Learn how to introduce a QR allergy menu to guests during service, with staff scripts, kitchen checks, and a written backup for phone problems.
Key takeaways
- Introduce the QR menu at seating and invite guests to disclose allergies.
- Staff should confirm every allergy order and modification with the kitchen.
- Keep digital information, written alternatives, and staff briefings current.
Introduce an allergy-aware QR code menu when guests sit down: explain what they can filter, point out the code, and ask them to tell their server about allergies before ordering. Keep the introduction brief, offer a written alternative, and make clear that staff still confirm every order with the kitchen. The scan starts a conversation; it doesn't complete the allergy check.
What should staff check before introducing a QR allergy menu?
Before the first table scans, compare the published information with what the kitchen is actually serving. Don't launch the guest introduction while ingredient questions are still unresolved.
Work through every orderable item, including sides, sauces, desserts, drinks, and specials. Check components separately: a salad's dressing, garnish, and optional protein need attention alongside the base recipe.
Give the review a clear owner. The person updating the menu needs a kitchen contact who can confirm recipes, supplier substitutions, cooking oils, and preparation methods. If something's unknown, keep that uncertainty visible and ask for confirmation before recommending it.
Separate ingredient information from preparation information. Removing a topping doesn't answer whether the dish uses a shared fryer or prep station. Use a restaurant cross-contact checklist to structure that conversation.
For opening service, prepare a short change briefing: what's different, which dishes are affected, and who can answer questions. A server shouldn't discover a new dressing ingredient while standing beside a guest who's already selected it.
Where should restaurants put allergy menu QR codes?
Put the code where seated guests can see and reach it without moving glasses or passing one small card around a party of six. A table tent or a clearly marked area on the physical menu is a practical starting point.
Label its purpose. Try:
Scan for ingredients and allergy filters. Please tell your server about allergies before ordering.
An unlabeled code makes guests guess whether it opens ordering, payment, or menu information. Guidance on QR codes for allergen information recommends clear instructions and placement where guests naturally look during ordering.
Test the printed code from an actual seat, under service lighting. Check that it opens the correct menu and that the text is readable on a phone. Include patio and bar seating in the check. Don't assume a code that worked in the office works at every table.
What should servers say when introducing an allergy menu?
Use one short introduction for the whole table. Guests shouldn't have to announce a medical concern publicly just to learn that ingredient information exists.
A server could say:
“You can scan this code to view ingredient information and filter for allergies or dietary needs. Please tell me about any allergies before you order, even if you've used the filters. I'll check with the kitchen.”
Then give guests time to look. There's no need to explain every setting while they're settling in or helping a child into a chair.
If someone discloses an allergy immediately, acknowledge it before explaining the technology:
“Thanks for telling me. Which ingredients do you need to avoid? You can use the menu filters while I check with the kitchen.”
Don't reserve that conversation for guests who describe an allergy as severe. Every disclosed allergy needs staff attention.
FARE's restaurant resources emphasize staff training, menu transparency, and inviting guests to disclose allergies. Build those practices into the greeting instead of treating the code as a substitute for them.
For more detailed staff responses, keep your guide to handling guest allergy questions available during training.
How do you confirm an allergy order after guests filter the menu?
Keep the guest's screen and the kitchen's confirmation connected. A filtered result gives the server something specific to discuss; it isn't permission to skip verification.
Picture a Saturday dinner service. A guest selects a sesame restriction and asks whether a chicken sandwich can come without its bun. The server needs to check more than the bread: the marinade, sauce, garnish, cooking oil, and preparation method may all need review.
Use this sequence:
- Repeat the restriction. “You've told me you need to avoid sesame. Have I understood that correctly?”
- Confirm the exact request. Identify the dish, sides, sauces, and proposed changes. Don't assume “no bun” answers the whole question.
- Check with the kitchen. Ask the designated contact about ingredients and relevant shared equipment. If the answer's incomplete, say you're still checking.
- Report back before confirming the order. Explain what the kitchen confirmed, any modification, and any remaining uncertainty. Ask whether the guest wants to proceed.
Carry the restriction and agreed changes onto the ticket using your restaurant's established process. Make sure expo and the runner know which plate belongs to which guest. A detailed conversation at the table loses its value if the handoff ends at the point of sale.
If the kitchen can't confirm an ingredient or accommodate the request, say so plainly:
“We haven't been able to verify that sauce's ingredients, so I can't confirm it meets your restriction. I'll ask the kitchen about another option.”
Don't fill a gap with “probably” because the line's in the weeds.
What if a guest can't or doesn't want to scan the QR code?
Offer another route immediately. A dead battery, an unreadable screen, or a preference for paper shouldn't turn into a debate at the table.
Keep a current written alternative available and tell staff where it lives. Assign someone to update it whenever the digital information changes. A backup that's several revisions behind creates another ingredient question instead of answering one.
Use a straightforward response:
“That's fine. I'll bring our written allergen information, and we'll check your choices with the kitchen.”
If a guest needs help using the filters, explain the controls without taking their phone unless they've asked you to. Let them state their own restrictions and confirm what they've selected.
For location-specific disclosure requirements, review restaurant allergy laws by state. Don't treat having a QR code as proof that you've met every requirement.
How do you train staff to introduce the menu during a rush?
Rehearse the moments when the process could break down. Start with a normal greeting, then add a guest question, an uncertain ingredient, and a kitchen handoff.
Use a short role-play table:
| Service moment | Response to practice |
|---|---|
| A guest says, “I already filtered it.” | “Thanks. Please tell me your allergies too, so I can confirm with the kitchen.” |
| A guest asks about removing a sauce | “I'll check the other ingredients and preparation with the kitchen.” |
| The code won't load | “I'll bring the written information and help you review it.” |
| A runner can't identify the allergy order | Pause delivery and verify the ticket and plate with expo. |
Include hosts, servers, cooks, expo, and runners in the handoff practice. Give each role a clear responsibility and a person to contact when answers aren't available.
Keep emergency-response training separate from the menu demonstration. FARE provides restaurant training resources and emergency-response posters; knowing how to demonstrate a filter doesn't prepare someone to respond to a reaction.
How do you keep a QR allergy menu useful after launch?
Choose a process your team can maintain between deliveries and dinner service. Assign an owner, a backup, and a clear trigger for reviewing changes. Recipes, supplier substitutions, cooking oils, and shared-equipment changes all belong in that review.
For restaurants that want guests to filter the menu themselves, Can I Dine?™ is one practical option. The restaurant uploads its own menu, reviews dishes, ingredients, oils, and shared-equipment groups, then publishes. Guests scan at the table in their phone browser, without downloading an app, and choose their restrictions while everyone else in their party reviews the menu.
Results are sorted into suggested dishes, dishes that may need a modification, and dishes to avoid. A Severe allergy setting removes dishes with relevant declared shared-equipment or cooking-oil exposure. Those results organize restaurant-provided information; they don't inspect preparation or replace staff confirmation with the kitchen.
When introducing those results, explain the next step:
“These suggestions help you review the menu. Please tell me your restrictions and which dish interests you, and I'll check with the kitchen.”
Before each service, check for changes and test the guest page. After service, collect questions the menu didn't answer. Was a garnish missing? Did staff know who could verify a substitution? Update the information and briefing before the same question reaches another table.
Use a documented process for updating allergen information after recipe or supplier changes. Then keep the introduction consistent: show guests the menu, invite disclosure, and confirm their order with the kitchen.
Frequently asked questions
What should a server say when introducing a QR allergy menu?
Keep it brief: “You can scan this code to view ingredients and filter for allergies or dietary needs. Please tell me about any allergies before ordering, even if you've used the filters. I'll check with the kitchen.” Explain where the code is, give guests time to review, and offer written information if they don't want to scan.
Should guests still tell staff about allergies after using menu filters?
Yes. Guests should tell staff about every food allergy before ordering, even when they've selected filters. The server should repeat the restriction, confirm the exact dish and requested changes, and check ingredients and preparation with the kitchen. A filtered result doesn't replace that conversation, and removing an ingredient doesn't resolve questions about shared equipment.
What should restaurants offer when a guest can't scan the QR code?
Offer current written allergen information and staff assistance without making the guest explain why they can't scan. Keep the written version aligned with the digital menu, and make sure staff know where to find it. Guests should still disclose their allergies, and staff should confirm their chosen dishes and any modifications with the kitchen before completing the order.
When should a restaurant update its QR allergy menu?
Review and update the information whenever recipes, suppliers, ingredients, cooking oils, or preparation methods change, including shared-equipment arrangements. Assign an owner and a backup, brief staff on affected dishes, and update the written alternative too. Don't assume the QR code keeps the content current automatically. Staff still need to confirm allergy orders with the kitchen.
How should staff explain a dish that may need a modification?
Explain that the proposed change needs kitchen confirmation before the guest orders. For example: “The menu suggests asking about removing the dressing. I'll check the remaining ingredients and preparation with the kitchen.” Don't imply that removing one component resolves every concern. Tell the guest what the kitchen confirmed and clearly explain any uncertainty that remains.
Sources
Can I Dine?™ organizes the information a restaurant provides so guests and staff can have a clearer conversation. It doesn't inspect kitchens or certify allergen-free preparation. Always tell your server about your allergies before ordering.