A restaurant can use QR ordering for age-restricted items only if its service process gives staff a clear opportunity to check eligibility before the item reaches the guest. A notice on the phone is helpful, but it is not the handoff. Look for a way to identify the restricted item, hold it for review, record the decision, and prevent service when the check has not been completed.
Start with the path your staff will actually follow on a busy shift. The important question is not simply whether a guest can select a drink. It is whether the right employee can see that a check is due, find the right guest, and stop the item if the check fails.
Map the order from selection to service
Write down each point where the order changes hands. For table service, that usually starts when a guest scans a code and selects an item. It ends when an employee delivers the item or records that it will not be served. Include the steps in between: how the order identifies the table, where staff see it, who checks eligibility, and what happens to payment if an item is removed.
Fleksa's QR ordering software lets guests scan, order, and pay at the table in a browser without downloading an app. That describes the guest ordering path; ask Fleksa to show how a restricted-item review would work in your intended setup before relying on it for service.
A practical handoff has five parts:
- Identify the item. Staff need to recognize which order lines require a check, including items with different sizes or modifiers.
- Identify the guest. A table number identifies a physical table, not necessarily the person who selected the item. Decide how staff will match each restricted item to its intended recipient.
- Assign the check. Name a role, such as the server responsible for the table, and a backup for shift changes or breaks.
- Hold the item. Decide what prevents preparation or delivery before review, and how employees can see whether that hold remains in place.
- Record the outcome. Staff need a usable path for an approved item, a declined item, and a check that cannot yet be completed.
Walk the path through every screen or ticket staff will use. If the kitchen, bar, and floor team see different views, ask what each view shows when an item is awaiting review. A flag visible only on the manager's screen is of little help to the person carrying the drink.
Also decide what happens when a guest cannot use a phone. A staff-taken order should enter the same verification process rather than create an informal exception. For the wider choice between phone ordering and staff-led service, see the guide to where QR ordering fits in table service.
Compare a guest notice with a staff review step
A pre-order notice can tell a guest that identification may be requested and that an item may be refused. It sets expectations before the guest taps submit. But a message displayed to the guest does not tell the server that a check happened, and a guest's confirmation is not the same as a staff decision.
A stronger workflow makes the unresolved check visible to staff and gives them a defined next action. Ask the vendor to demonstrate whether a restricted line can be held or marked for review, who can change its status, and whether the status is visible at the point of service. If the software cannot enforce a hold, ask whether a clearly documented staff procedure can reliably fill the gap. Consider how that procedure would work during a rush, not just when a manager is watching.
Use the following worksheet to compare a demonstration against your operating requirements. The first column is the decision point; the other columns show what to look for and what to do if the path is unclear.
| Decision point | Acceptance check | If the check fails |
|---|---|---|
| Guest selects a restricted item | Staff can distinguish it from unrestricted lines and identify the table. | Do not route that item through phone ordering until staff can identify it reliably. |
| Order reaches the service team | The responsible employee can see that verification is still needed before delivery. | Use a documented staff-led path or remove the item from QR ordering. |
| Staff make a decision | Approved, declined, and unresolved items have distinct next steps. | Keep the item unserved while the decision or correction is unresolved. |
| Order contains other items | Staff can handle unrestricted lines without mistaking them for approved restricted items. | Pause the affected order and use the manager's exception procedure. |
| Payment needs correction | The team can explain and carry out the appropriate void or refund for the payment state. | Escalate to the person authorized to resolve it; do not assume a refund occurred. |
The decision boundary is straightforward: if your team cannot reliably tell whether a restricted item is awaiting review and prevent it from being served, do not offer that item through the QR path. You can still consider QR ordering for other items while using a staff-led process for restricted ones, subject to your local requirements.
Ask about permissions and audit detail too. Who can mark a check complete? Can another employee see the current decision after a shift handoff? What happens if someone changes the order? Avoid collecting or retaining identification details by default; ask your qualified adviser what your operation needs and what it should avoid keeping.
Run two simulated acceptance checks
The following examples are hypothetical. They assume an on-premise restaurant wants a staff check before a restricted item is served. They are not claims about any product's features. Use a demonstration or sandbox with fictional orders. Do not take a real card payment, send a message to a guest, or dispatch a courier during practice.
Check 1: A selected item is declined
Create a fictional order for one restricted drink at table 6. Have one employee play the server and another play the guest. The server should find the order, identify the intended recipient, and follow the restaurant's procedure for a check that does not pass. The item must not move to service as an approved item.
Then trace the correction. Can the employee remove or cancel that line? Does the display used by the bar or floor team reflect the change? If the mock order is marked unpaid, ask how the final amount would be adjusted. If it is marked paid in the simulation, ask who would initiate a void or refund and how the team would confirm its status. No actual payment or refund is needed for the exercise.
The check passes only if the team can explain and demonstrate the route from selection to refusal, including the stop at service and the payment correction path. If an employee must guess whether someone else completed the check, revise the process and run the scenario again.
Check 2: One table, mixed items
Create a second fictional order for table 9: two meals, one soft drink, and one restricted drink. Table 9 is one physical table; the number alone does not establish which person is meant to receive the restricted drink. Ask the server to find the intended recipient and complete the restaurant's review before delivering that line.
Now simulate a declined check. Can staff cancel the restricted drink while the meals and soft drink remain available to serve? Can the team distinguish the declined line from the remaining order on the views they use? If the system cannot separate those actions clearly, the acceptance decision may be to pause the entire order and handle it with a manager, or keep restricted drinks off the QR menu.
For a simple payment explanation, assume the fictional meals and soft drink total $24 and the restricted drink is $8. The full item total is $32; removing the drink leaves $24. These figures include only item prices. They exclude taxes, tips, processing fees, and other fixed, variable, or exception costs. The example describes an order adjustment, not the restaurant's operating cost. Ask the vendor to show how the actual payment state and any applicable charges are handled.
After simulations, train the team on the chosen procedure and observe a live service pilot only when the workflow, staff roles, and applicable requirements are ready. A live pilot involves real guests and normal service controls; it is not a substitute for the no-payment practice above. Record any handoff confusion and correct it before expanding use.
Review local rules and operating responsibilities
Rules for age-restricted sales can vary by jurisdiction and by item. Before putting a restricted item on a phone-ordering menu, have a qualified local adviser review the rules that apply to your location and service model. Give that person the actual workflow, not just the name of the software.
Bring a short list of questions:
- Which items and service situations require an eligibility check, and when must it occur?
- Who may perform the check, and what identification or other evidence may be accepted?
- What should staff do when the intended recipient cannot be identified or the check is declined?
- What records, if any, are required or restricted, and how should the team protect guest information?
- Do the rules differ for table service, pickup, or delivery? Review those paths separately rather than assuming a table-service procedure applies to all three.
Match the answers to staff training, manager escalation, and any settings the vendor demonstrates. Your restaurant management workflow should also make ownership clear when an order changes hands: the server, bar staff, and manager need to know who acts next.
Next, take the worksheet and both scenarios to a vendor demonstration. Ask to see the staff view, the unresolved-review state, the declined-item path, and the payment correction process for your setup. Discuss your requirements with Fleksa and compare the demonstrated workflow with the service procedure your team can actually follow.
Frequently asked questions
Is an age notice on a QR menu enough?
A notice can prepare guests for a check, but it does not show staff that a check was completed. Have a qualified adviser review your local requirements and use a staff process that stops unresolved items from being served.
Can the rest of a mixed order still be served?
That depends on the ordering workflow and your procedures. Ask the vendor to demonstrate how staff can decline the restricted line while keeping other lines clear and accurate. If they cannot, use your manager's exception procedure.
What should happen if a guest already paid?
Staff should keep the declined item unserved and follow the appropriate correction process for that payment state. Ask who can initiate a void or refund, how its status is confirmed, and how the guest is informed during normal service.
