Before asking a guest to join your loyalty program at checkout, staff should know how to invite them, capture the right contact detail, record their choice about marketing, and explain what the current purchase earns. They also need a quick way to handle a decline or an existing account without holding up the line.
Run through those paths before launch. A program can have an attractive reward and still cause trouble if the cashier cannot see whether enrollment succeeded or the guest leaves with the wrong expectation about a reward.
Map the invitation through the first reward
Start by deciding when an invitation makes sense. A cashier might ask after confirming the order and before finishing payment, when the guest can still make a choice without interrupting food preparation. If the line is moving slowly, give staff permission to skip the invitation rather than rush a guest through it.
Write a short invitation that explains the benefit without promising an immediate discount. For example: “Would you like to join our rewards program? Eligible purchases can earn points.” Staff should be able to explain what information is needed and what happens if the guest says no.
Then map the actual screens with your provider. Does the cashier enter a phone number or email, or does the guest enter it? Is the purchase linked to the account before payment, after payment, or through another step? What confirms that the account was created? Ask which order types are eligible to earn points; do not assume every channel works the same way.
Fleksa describes loyalty points for eligible orders in its loyalty documentation. Use that starting point to ask for a demonstration of the exact checkout and eligibility rules you intend to use.
A hypothetical enrollment decision
Assume a restaurant plans to award one point for each dollar of eligible food and drink purchases, with 100 points required for a $5 reward. A guest has no prior points and makes a $24 eligible purchase. Assume the entire $24 qualifies and that the account is successfully linked to the purchase.
The expected result is 24 points. That balance is not yet a redeemable $5 reward: the guest needs 76 more points under this example’s rules. A cashier can say, “You have 24 points toward a reward at 100,” if the system confirms that balance. They should not say the guest has earned a $5 reward.
This example compares points and the stated reward only. It does not calculate program cost; fixed software costs, variable costs, and exception costs are excluded. Set your own reward rules and ask how the system displays partial progress before using a script like this.
Use a checkout decision worksheet
The worksheet below turns that hypothetical setup into staff decisions. Its expected results depend on the restaurant’s chosen rules and on the provider demonstrating that the workflow supports them. Use it as a pass-or-fix record, not as a claim that a particular POS has these controls.
| Checkout situation | Staff check | Expected result or decision |
|---|---|---|
| Guest wants to join | Confirm the required contact detail and account creation step. | Continue only after the guest agrees; verify enrollment before describing a balance. |
| Marketing choice appears | Read the choice as presented and record the guest’s answer. | Do not treat a contact detail or loyalty enrollment alone as permission to send promotions. |
| New member buys $24 of eligible items | Check that the account is linked and the purchase qualifies. | Under the example rules, expect 24 points; no $5 reward is redeemable yet. |
| Guest declines | Leave enrollment unstarted or exit it. | Complete the ordinary sale without collecting loyalty details. |
| Guest says they already belong | Use the provider’s approved lookup or referral process. | Do not create a second account just to move the line. |
| Identifier looks wrong | Pause and confirm the detail with the guest. | Correct it through the approved process, or finish the sale and refer the issue. |
Mark each row as ready only when staff can demonstrate the path and explain its result. If a necessary step is unclear, decide who will resolve it and whether enrollment should wait. For instance, if the register cannot show that an account was linked, the cashier should not promise points for that purchase until the restaurant has an approved way to verify the result.
Practice declines and existing accounts
A decline should be uneventful. The cashier asks once, the guest says no, and the sale continues. Staff should know how to leave the enrollment screen without accidentally saving a partial account or changing the order. Avoid making the guest explain their decision. A simple “No problem” is enough.
Also decide what happens when a guest changes their mind midway. Can the cashier cancel contact entry? Does an incomplete record remain? Ask the provider to show the exit path and any cleanup needed. If the answer is not clear, do not have staff improvise at the register.
An existing member needs a different path from a new enrollee. Ask, “Are you already a member?” before collecting details for a new account. If the guest says yes, follow the approved lookup process and confirm the right account without announcing private information to the line.
If lookup fails, do not guess which record belongs to the guest. Offer the restaurant’s approved support route and complete the purchase according to its rules. Whether a purchase can be credited later is a separate provider question; staff should not promise that it can. Recovering or merging duplicate accounts is also a separate process from enrolling someone new.
Check mistakes, confirmation and receipts
A mistyped digit can send a guest down the wrong path or leave them unable to find their account later. In a practice environment, enter a deliberately incorrect test identifier and see what staff can review before saving. Then practice correcting it using the provider’s approved steps. Ask whether a correction changes an existing account, creates a new one, or requires a manager.
Keep the guest involved without repeating their full contact details loudly. A cashier might ask the guest to review the entry on a screen where available, or use another approved, discreet confirmation method. If the guest cannot confirm the detail, stop the enrollment rather than inventing a value to get through checkout.
Next, examine the confirmation a guest actually receives. Is there an on-screen success message, a printed receipt line, or another confirmation? Does it distinguish enrollment from points earned and from a reward available to redeem? If a receipt says only “member,” staff need to know where to check the balance before quoting one.
Ask what happens when the account is created but the purchase is not linked, or when payment does not complete. Those are different outcomes. A successful enrollment alone does not prove that a particular purchase earned points. Give staff an escalation route for an unclear result and a plain response: “Let us check that before we promise a balance.”
Use fictional test contact details and a simulated transaction for practice. Configure the practice so it cannot take a real payment, send a guest message, or dispatch a courier. If the provider cannot offer a safe simulation, use a walkthrough of screens and documented decisions instead.
Train the team and confirm consent rules
Keep a one-page register guide beside the POS or in the staff handbook. Include the invitation, required information, how to confirm success, the current reward threshold, and the steps for a decline or failed lookup. Name the shift lead or support channel for exceptions. Update the guide when the program rules or checkout screens change.
Practice in pairs: one person acts as the guest and the other works through the decision. Cover a new member, a decline, an existing member, a wrong identifier, and an interrupted transaction. The goal is not a memorized sales pitch. It is a consistent choice at each screen and a clear explanation of what the guest can expect.
Separate loyalty participation from marketing permission. Having an email address or phone number available does not by itself mean the restaurant should send promotional messages. Ask your provider how each choice is presented, stored, retrieved, and changed, and how staff can tell whether a guest has opted in. Confirm your current consent language and practices with qualified legal counsel; rules and business circumstances can differ.
For follow-up campaigns, consider who can access contact data, who can send messages, and how preferences are honored. Fleksa describes email and SMS campaigns alongside loyalty tools in its restaurant marketing automation offering; ask to see the relevant controls for your setup. Its marketing loyalty FAQ is another place to start preparing questions.
After simulated practice, a limited live service pilot can reveal where the process slows staff down. Use the real workflow only with guests who choose to participate, and have a shift lead available to record issues without collecting unnecessary guest details. Review whether staff followed the invitation and consent steps, whether confirmations were understandable, and which questions required escalation. Change the guide before expanding the program if the team cannot explain the outcome reliably.
Next step: Compare your checkout requirements with Fleksa and ask for a demonstration of enrollment, consent choices, account lookup, and first-purchase confirmation using your intended rules.
Frequently asked questions
Should every guest be asked to join?
Not necessarily. Set a consistent invitation point, but let staff skip it when the guest is in a hurry or the line needs attention. A decline should never prevent a normal purchase.
Can a new member redeem points from their first purchase?
Only if the purchase qualifies, the points are credited, and the resulting balance meets your reward rules. Explain the confirmed balance and threshold rather than treating partial progress as a redeemable reward.
What if a guest already has an account but staff cannot find it?
Follow the approved lookup and support process. Avoid creating another account or promising later credit unless your restaurant has confirmed how that exception is handled.
