To check whether your QR menu matches your maintained menu, compare each guest-facing item with one approved source record, then scan the actual QR code and inspect what a guest sees. Repeat the check after ingredient changes and on a schedule. Record mismatches, assign an owner, and keep an item on hold when its information cannot be confirmed.
The important question for a software buyer is not simply whether a QR menu can display allergen information. Ask how an approved change reaches the display, who can publish it, and how staff can tell whether the update is live. A menu that looks correct in an editing screen may still need a separate check on the guest’s screen.
Map the source record to every guest view
Start by naming the maintained menu record your team treats as authoritative. It might be a controlled recipe file or another approved record. For each dish, it should identify the current recipe and ingredients, the allergen information your qualified reviewer has approved for display, the review date, and the person responsible for the record. Keep supplier and ingredient details available for that review.
Give dishes stable identifiers where practical. Names can change or be duplicated: a lunch salad and a dinner salad may have similar names but different dressings. A stable identifier helps the person making an update find the right item in every channel.
Next, make a short channel map. Include the QR menu, your website menu, direct online ordering, printed menus, and any other place where guests see or receive allergen information. Note who maintains each one and whether it receives changes from the same record or needs a separate update. Include staff reference sheets if your team uses them to answer questions.
For each channel, identify the path from approval to display. Does a manager enter information directly? Is there an import? Does someone have to publish a change after saving it? Can an item appear in more than one category or menu? Ask the vendor to demonstrate the actual path for your setup, including how staff find an item and check its published state.
Do not assume that a shared item name means shared information. A QR code might open a menu-only page, while another channel uses a different ordering catalog. A guide to where QR ordering fits in table service can help you decide which guest journey to map first.
Trace a change with a decision worksheet
The following example is hypothetical. Assume a restaurant maintains an approved recipe record and displays allergen information on a QR menu, a website menu, and a printed staff reference. A supplier change means the dressing for its grain bowl now contains sesame. A qualified reviewer has checked the ingredient information and approved the updated item record. The restaurant’s rule is to hold the changed version from service until each required guest and staff view is updated or a manager has put an approved alternative in place.
The worksheet shows the decision at one point in that change. “Match” means the displayed information agrees with the approved record; it does not mean the dish has been independently verified as safe for a particular guest.
| Check point | Approved or expected information | Observed result | Decision |
|---|---|---|---|
| Maintained record | Grain bowl dressing contains sesame; update approved | Record shows sesame and review date | Use this record for comparison |
| QR guest view | Grain bowl shows sesame | Scanned page still shows the earlier information | Mismatch; hold changed version and correct display |
| Website menu | Grain bowl shows sesame | Website shows sesame | Matches; recheck after any further edit |
| Staff reference | Staff can identify the current dressing | Printed sheet has the earlier information | Replace sheet and brief staff before release |
The result is a hold, not a pass: two of the three checked views need attention. The manager assigns an owner to update the QR menu and another to replace the staff sheet. Once those jobs are complete, someone checks the published QR page again by scanning the code, checks the replacement sheet against the approved record, and records the results. Only then can the manager consider releasing the changed version under the restaurant’s rule.
If the old dressing is still in use while the new one is waiting, staff need an unambiguous way to distinguish the versions. If that cannot be done reliably, holding the item is the simpler choice. Avoid making an unreviewed change merely to make screens agree: consistency with an incorrect source does not solve the problem.
Use the same worksheet when an ingredient is removed, a supplier substitutes a product, a sauce changes, or a modifier is added. Check variants as well as the base dish. A guest who adds a topping or chooses a different sauce may see a different combination from the one reviewed on the main item page.
Check the guest view and handle missing information
Inspect the page a guest actually opens, not just the back-office entry. Scan the physical table code with a phone, open the relevant item, and compare its name, variant, and displayed allergen information with the approved record. Check the route a guest would follow from the menu category to the item details. If different codes or menus are in use, include each relevant route in the check.
Ask the vendor what happens between saving and publishing a change. Can staff see when an update was made? How do they know it is visible to guests? If a page still shows earlier information, what should they check before treating the update as complete? Have the vendor demonstrate these steps rather than relying on a feature label.
Missing information deserves its own procedure. An empty field, an absent symbol, or a note that has not been reviewed should not be treated as evidence that an allergen is absent. Staff should know who to contact, where to find the approved record, and when the answer requires further review. If the information cannot be confirmed, the trained staff member should say so and follow the restaurant’s hold or escalation procedure rather than guess.
Give guests a non-phone route to ask questions, too. A server or other designated staff member should be able to consult the current reference and involve the person responsible for an unresolved question. The QR display supports that conversation; it does not replace the need for staff to understand what they can and cannot confirm.
During a vendor demonstration, use a simulated item and a practice data set to check how a missing field appears and how an update is reviewed. Do not place a real order, take a payment, send a guest message, or dispatch a courier as part of the practice. A later live-service pilot is different: use your approved menu records and operating procedures, assign a manager to monitor the rollout, and stop using a channel for affected items if the information cannot be confirmed.
Set review ownership and an audit schedule
Choose a qualified person to review ingredient and allergen information before it becomes the approved source. The right reviewer depends on your operation and the question involved. Make sure that person can obtain current ingredient details and raise an unresolved question rather than being pressured to approve an uncertain record.
Separate review from publishing where your staffing allows it. The reviewer approves the content; a named publisher updates the relevant channels; a checker compares the live views with the approved record. In a small restaurant, one person may perform more than one role, but the checklist should still show which steps were completed and when.
Set two triggers for checks. The first is a change trigger: review affected items whenever a recipe, ingredient, supplier product, modifier, or menu presentation changes. The second is a scheduled audit: select a recurring interval your team can maintain and compare a defined set of active items across channels. Rotate through the full menu rather than checking only popular dishes forever. Increase the scope when you find repeated mismatches.
A useful audit record contains the item identifier, approved record date, channels checked, result, owner, correction, and date of the recheck. Keep a list of open mismatches where the manager on duty can find it. When a correction is made, close the issue only after someone verifies the guest-facing view and any staff reference, not merely after someone says the edit was saved.
Bring your own worksheet to a demonstration. Ask how staff would find each item, make an approved update, publish it, and verify the result on a phone. Also ask what remains a manual step when information appears on a website, printed menu, or other channel. The answers help you decide whether the workflow fits your staffing and review process.
Fleksa’s QR ordering lets guests scan, order, and pay at the table in a browser without downloading an app. That is a different buying decision from displaying a menu alone. For the service workflow, review the QR ordering FAQ and consider the questions in the QR ordering system cost guide. Bring a sample item and your channel map to Fleksa, and ask for a demonstration of the relevant update and verification workflow.
Frequently asked questions
How often should we check QR allergen information?
Check affected items after a relevant ingredient or menu change, and run a scheduled audit of active items. Choose an interval your team can maintain, and expand the audit when mismatches recur.
Does a QR menu need to show the same information as a printed menu?
Both should be checked against the approved record for the item and version they describe. If their formats differ, make sure staff understand where details are presented and how to handle a guest question.
What should staff do when allergen information is missing?
Do not assume an absent entry means an allergen is absent. Refer the question to trained staff, consult the approved record, and follow the restaurant’s escalation or hold procedure if the answer remains uncertain.
