QR menus · 8 min read
QR Code Menus for Allergies: What Guests Need to See
A qr code allergy menu should show ingredients, cross-contact notes and possible changes clearly. Here's what restaurant operators should check.
Key takeaways
- Put ingredients and preparation notes on each affected dish.
- Keep a written alternative and check both versions after changes.
- Have staff confirm allergy orders with the kitchen.
A QR code allergy menu should show guests what's in each dish, where cross-contact may occur, and which changes the kitchen can confirm for their order. It should be easy to read at the table, with a clear way to speak to staff before ordering.
What should guests see when they scan a QR code allergy menu?
Start with the menu, not a wall of instructions. A guest sitting with a party of six needs to find the same dishes everyone else is discussing, then open the details that matter to them. Put the dish name, description and allergen information together so they don't have to compare two documents on a phone.
Make it obvious whether an allergen is an ingredient, whether a change might be possible, or whether the kitchen still needs to answer a question. An icon can help someone scan a list, but it shouldn't carry the whole message. Write the allergen name beside it. If a dish contains sesame in its dressing, say so in words a guest can read without learning your symbol key.
In the U.S., the nine major food allergens are milk, eggs, fish, crustacean shellfish, tree nuts, peanuts, wheat, soybeans and sesame. The FDA lists all nine. Guests may also ask about ingredients outside that list. Give them a way to ask rather than treating the nine as the end of the conversation.
How much ingredient detail does an allergy menu need?
Show the components that could change a guest's decision. A dish name such as “grilled chicken bowl” doesn't tell anyone what's in the marinade, sauce, garnish or cooking oil. If the menu only marks the main protein and base, staff will still have to reconstruct the dish while the guest waits.
Work from the recipe your kitchen actually uses. For each item, check the base, sauces, dressings, marinades, toppings, garnishes and oil. Check packaged components against their current labels. Record the answer where the guest or staff can find it, and make sure the line has the same information.
Consider a bowl that arrives with a sesame dressing unless the guest asks to leave it off. The menu should identify sesame in the standard dish and describe the dressing as a possible omission only if the kitchen has confirmed that change. A note such as 'sesame can be omitted on request' would leave too much unsaid: the bowl's other components and preparation still need review for that order.
This is a useful place to compare your menu against an allergen matrix. If the matrix says one thing and the phone menu says another, pause publication until someone checks the recipe. A polished screen can't fix uncertain source information.
How should a QR menu explain shared fryers and cross-contact?
A guest needs to know more than whether an allergen appears in the recipe. Cross-contact is the unintended introduction of an allergen into another food, as the FDA explains. That question comes up quickly when dishes share a fryer, grill or prep station.
Write the exposure where it belongs: on the affected dish. If fries and breaded shrimp use the same fryer, a note hidden on a general policy page won't help someone looking at the fries. Say which equipment is shared and what the kitchen has confirmed about its use. Don't turn an uncertain practice into a reassuring label.
The same review applies to cooking oils. Ask the kitchen what oil is used for each method and whether it changes. If the fryer oil, grill process or prep station changes, update the menu before staff rely on yesterday's note. The restaurant cross-contact checklist can help structure that review.
During a rush, a server might say, “The menu notes a shared fryer. I'll check with the kitchen about your order.” That's a useful handoff. Guests should tell staff about their allergies, and staff should confirm the order with the kitchen even when the QR menu contains detailed notes.
How do you show modifications without promising too much?
Separate the standard dish from the proposed change. “Contains milk” describes the dish as served. “May be made without the cheese; ask staff to confirm” describes a possible modification. Those statements answer different questions, so don't replace one with the other.
Only publish a modification after the kitchen checks the full ticket path. Can the cheese be omitted every shift? Is it mixed into a sauce before service? Does another component need to change? If the answer depends on the day's prep, tell guests to ask staff. The server can then confirm with the kitchen before the ticket goes through.
For a salad with a nut topping, a note such as “nuts can be omitted” doesn't address the dressing, garnish or prep station. A better note names the standard ingredients, identifies the proposed omission and flags any preparation question that still needs confirmation. Keep the wording as specific as the kitchen's knowledge allows.
Make these notes visible before the guest settles on an order. If the only qualification appears after several taps, someone may read the dish name aloud to the table without seeing it. Staff also need a quick way to find the same note when the guest asks.
Where should the QR code go, and what if a guest can't use it?
Put the code where guests make food choices: on the table, on the printed menu or beside a buffet item. Label it “Scan for ingredients and allergy information.” “Scan me” doesn't explain why someone should reach for their phone. Test the printed code from a seated position under normal dining-room lighting.
Open the link on a phone and try to complete a real task. Can you find a dish, read its ingredients and spot its shared-fryer note without pinching and zooming? Can you get back to the menu without losing your place? Ask a server to try it during a pre-shift meeting. If they can't find an answer quickly, guests may struggle too.
Keep a written alternative that staff can hand over or show. A phone may be uncharged, a connection may fail, or a guest may prefer paper. For California restaurant chains with 20 or more locations, SB 68 requires written notice of the nine major allergens in each menu item; a digital format such as a QR menu is allowed when a written alternative is available on request. Check the requirements that apply to your operation.
The paper and digital versions need the same review routine. If today's supplier change reaches the QR menu but not the printed chart, staff are left with conflicting answers at the table.
What should staff do when a guest asks an allergy question?
Treat the menu as the start of the conversation. When a guest says they have an allergy, staff should note the restriction, find the relevant dish information and confirm the proposed order with the kitchen. If the kitchen can't establish an ingredient or preparation detail, staff should say that clearly.
Give servers a short service script they can use while the line is busy: “Thanks for telling me. Let's look at the dish details, and I'll check your order with the kitchen.” Then give the kitchen a clear ticket that identifies the allergy and any requested change. A vague note such as “no nuts” may miss the actual question about the sauce or shared station.
Practice with one real menu item at pre-shift. Have a server find its ingredients, identify a possible modification and explain a shared-equipment note. Have the kitchen explain what it can confirm. This shows where the published wording needs work before a guest is waiting for an answer. For a fuller routine, see how to handle guest allergy questions.
How do you keep the QR allergy menu current?
Give someone ownership of each published change. When a recipe, supplier, oil or preparation method changes, have the kitchen review the affected dishes and have a manager check what guests will see. Record who approved the update and when. Then open the QR link on a phone and check the affected dish yourself.
A supplier swap can touch several items at once. If a sauce appears on four dishes, review all four rather than editing the first one you remember. If a fryer starts handling a new item, review the other dishes that share it. The recipe and supplier change guide offers a practical update sequence.
Also check the information staff use during service. A current QR page alongside an old binder creates a new problem. Tell the team what changed before the next shift and remove outdated copies from the counter.
Can guests filter the menu for their own allergies?
Filtering can help a guest at the table narrow a long menu while staying in the conversation with their party. It works only as well as the restaurant's reviewed dish information. The result still needs to show why a dish appears in a given group and where staff confirmation is needed.
Can I Dine?™ offers an allergy-aware QR code menu as one option. A restaurant uploads its menu, reviews dishes, ingredients, cooking oils and shared fryer, grill or station groups, then publishes a branded guest page and QR code. Guests scan at the table in their phone browser, choose their restrictions and see dishes sorted into suggested, may need a modification and avoid. The Severe allergy setting removes dishes with relevant shared-equipment or cooking-oil exposure from suggested results.
Can I Dine?™ organizes the information the restaurant provides; it doesn't inspect the kitchen or certify preparation. Guests should tell staff about their allergies, and staff should confirm each order with the kitchen. Whatever menu format you choose, that conversation has to remain easy to start.
Frequently asked questions
What information should a QR code allergy menu show?
Show each dish's ingredients, including sauces, garnishes, marinades and cooking oils, alongside any relevant shared-equipment notes. Make possible modifications distinct from the standard recipe and mark questions that staff must check with the kitchen. Guests should tell staff about their allergies before ordering, even when the menu has detailed information.
Is an allergen icon enough on a QR menu?
An icon can help guests scan the menu, but write the allergen name too. Guests shouldn't have to remember a symbol key or guess whether a mark means the allergen is an ingredient or a cross-contact concern. Put the explanation on the affected dish, where someone choosing an order will see it.
Should a restaurant keep a printed allergy menu if it uses a QR code?
Keep a written alternative available and review it whenever the digital information changes. Guests may have a dead phone, limited connectivity or a preference for paper. California's SB 68 also allows qualifying chains to use a digital format when a written alternative is available on request. Staff should know where to find the current version.
How often should a QR code allergy menu be updated?
Review affected dishes whenever a recipe, ingredient, supplier, cooking oil or preparation method changes. Check every dish that uses a changed component or shares affected equipment, then open the guest page to verify the published notes. Tell staff what changed before service so their answers match what guests see.
Can guests rely on a filtered QR menu without speaking to staff?
No. A filter reflects the dish and preparation information the restaurant has provided. It can't answer an unrecorded question about today's prep or confirm a requested modification for a particular order. Guests should tell staff about their allergies, and staff should confirm the order with the kitchen.
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.