A guest has earned a free appetizer. Their phone is dead. Your server can see the reward mentioned in an email, but the register requires a live barcode.
Is there another approved way to redeem it—or does the guest need to save it for another visit?
That distinction sits behind many restaurant loyalty reward redemption problems: what the guest earned, what your terms allow, and what your systems can actually process are not always the same thing.
SevenRooms’ 2026 reporting highlights consumer interest in loyalty that spans reservations and ordering. That makes redemption boundaries worth examining: a guest may experience one restaurant relationship while your systems recognize several separate channels.
This five-question quiz tests whether your operation has usable answers for everyday reward exceptions. It does not test whether your employees are clever enough to invent a workaround.
Score the process you actually have
For each scenario, choose the response your restaurant can reliably deliver today—not the answer you would like to give.
Then open the explanation and record your points. Everything is here: no email address, signup, or results form required.
If an answer depends on “ask whichever manager is working,” and managers handle it differently, choose the less-developed response.
These scenarios concern earned rewards and published offers. Discretionary recovery credits are a separate decision. A manager might authorize a goodwill adjustment, but that does not make an expired or invalid reward successfully redeemed.
1. The reward is on a phone the guest cannot use
A guest’s phone battery has died. They say their account contains a free appetizer. Your normal redemption flow requires an in-app barcode.
Which response describes your operation?
A. Staff apply an equivalent discount whenever the guest describes a plausible reward.
B. Staff check whether an approved alternative verification method exists. If none exists, they explain that limit and offer the defined next step without making the meal wait.
C. Staff know the barcode is required, but there is no agreed explanation or next step.
Reveal the explanation, score, and policy gap
Score: A = 0 · B = 2 · C = 1
The strongest process distinguishes proof of membership from proof of an available, unused reward. An email address or account lookup may establish identity without establishing eligibility.
An alternative works only if your actual system and policy support it. Staff should not assume they can retrieve, validate, or mark a reward redeemed without the barcode.
Policy gap to resolve: What alternative verification, if any, is permitted? If none is available, who explains the limitation, and what can the guest do next? Do not promise later reimbursement unless that process exists.
2. Yesterday’s visit has not produced any points
A guest spent $86 yesterday. Today, their account shows no points from that visit, and they expected those points to unlock a reward.
Which response describes your operation?
A. Staff give the guest a support address, but cannot explain posting times or what information support needs.
B. Staff issue the anticipated reward immediately because the guest has a receipt.
C. Staff check the published posting window and purchase eligibility, then use a defined missing-points process if needed. They explain separately whether a reward is available today.
Reveal the explanation, score, and policy gap
Score: A = 1 · B = 0 · C = 2
A receipt documents a purchase, not necessarily qualifying spend or an unlocked reward. Taxes, tips, excluded items, account association, and posting delays may matter under your program’s terms.
Missing points and current redemption eligibility are two different questions. Resolving the first does not automatically authorize the second.
Policy gap to resolve: Who investigates missing points, what evidence is necessary, and when should the guest expect an update? Specify whether any authorized role can correct points—and avoid promising an adjustment your tools cannot make.
3. The offer expired two days ago
A guest presents a birthday dessert offer that expired on Sunday. They are dining on Tuesday and say they could not visit over the weekend.
Which response describes your operation?
A. Staff can explain the expiration rule and whether an authorized exception exists. Any permitted exception follows a defined approval and recording process.
B. Staff decline expired offers, but some managers quietly accept them and others do not.
C. Staff tell the guest the offer can be extended, although nobody has confirmed that capability.
Reveal the explanation, score, and policy gap
Score: A = 2 · B = 1 · C = 0
Operational readiness does not require accepting an expired offer. A clear, consistently applied expiration boundary can earn full points.
The problem is an undocumented promise or a different rule on every shift. If your program permits a grace period, staff need its exact limits. If it does not, they need a respectful explanation—not an invented extension.
Policy gap to resolve: Is expiration firm, or is there a defined exception? Identify the authorized decision-maker and distinguish any separate goodwill adjustment from redemption of the expired offer.
4. The guest ordered through the wrong channel
A guest places a delivery order through a third-party marketplace, then calls your restaurant to apply a reward available only through your direct ordering channel.
Which response describes your operation?
A. Staff promise to apply the reward to the marketplace order after delivery.
B. Staff explain the channel restriction and available options, including whether any cancellation or reorder route is actually supported. They make no refund or redemption promises outside their control.
C. Staff know marketplace orders are excluded, but guests usually discover that only after placing an order.
Reveal the explanation, score, and policy gap
Score: A = 0 · B = 2 · C = 1
Guests may see your restaurant’s name on both ordering experiences and reasonably expect continuity. That expectation does not give your restaurant control over a marketplace’s payment, cancellation, or promotion tools.
Clear boundaries matter more as loyalty reaches across reservations and ordering.
Policy gap to resolve: Where are channel exclusions disclosed before purchase? What can your team actually change after an order is submitted, and which actions belong to the marketplace?
5. The code looks valid, but the register rejects it
A guest shows an unexpired offer for your location. The register returns “code not recognized.”
Which response describes your operation?
A. Staff repeatedly enter the code, then improvise a discount if the line gets long.
B. Staff refer every rejected code to a manager, but there is no troubleshooting sequence or follow-up owner.
C. Staff perform a short, approved eligibility check, then follow the unresolved-code process. They explain what can happen now and who owns any investigation.
Reveal the explanation, score, and policy gap
Score: A = 0 · B = 1 · C = 2
A restaurant reward code not working may reflect a mistyped character, excluded item, location restriction, prior use, or technical fault. An error message alone does not establish the cause.
A bounded check prevents repeated attempts from holding up payment. It also avoids assuming the register supports a manual override.
Policy gap to resolve: Which checks should staff perform, when should they stop, and what information should they record securely? Define the escalation owner and any authorized fallback.
Your total: how many decisions are already settled?
Add your five scores, for a maximum of 10.
- 8–10: Mostly defined. Review every answer below two points. One unclear boundary can still create inconsistent guest experiences.
- 4–7: Partly defined. You have some rules, but handoffs or explanations depend on who is working. Resolve the lowest-scoring scenario first.
- 0–3: Mostly improvised. Start by documenting eligibility, system limits, and decision authority before asking staff to “use judgment.”
This is a self-assessment, not a validated benchmark. A low score identifies missing operational support—not poor employee competence.
Restaurant loyalty exceptions become manageable when your team can explain three things: what qualifies, what is possible, and what happens next. Loyalty service recovery may address disappointment separately. It should never require staff to pretend a reward redeemed when it did not.