Run one eligible purchase through every checkout device and ordering channel. Confirm the enrollment prompt appears, the guest can use one consistent identifier, the earned reward is visible, and redemption works on a later transaction. Record each break separately so staff do not promote a loyalty path that has not been verified.
Treat loyalty enrollment as a checkout workflow
A loyalty program is not ready just because the rewards have been configured in a dashboard. The guest-facing path must appear at the right moment, accept the expected identifier, attach the visit to the right profile, and make the reward visible afterward.
Square's current support documentation provides one concrete example: after an eligible sale, its point-of-sale flow can present a loyalty screen where a customer enters a phone number. Square also says a customer should use the same phone number across payment methods, because a different number can create a new Customer Directory profile. These are Square-specific mechanics, not universal POS rules, but they show why restaurants should test identity and profile behavior on their own system.
- Document when the enrollment prompt should appear.
- Define the identifier your system uses to find an existing member.
- Confirm what creates a new profile instead of updating an existing one.
- Decide what staff should say when a guest already has an account.
Map the guest path from purchase to the next visit
Write the loyalty journey as a sequence that a manager can test without guessing. Start with an eligible purchase, continue through enrollment and reward confirmation, and finish with a later check-in and redemption. A successful signup alone does not prove the complete experience works.
Square's buyer documentation describes several enrollment paths, including checkout, an invitation email after an eligible purchase, and certain invoice transactions. It also describes a welcome SMS and a status page. Your restaurant may expose different channels, so test only the routes your own POS or ordering provider actually supports.
- Complete one purchase that qualifies under the live program rules.
- Enroll through the same prompt a real guest will see.
- Open the confirmation or status destination on a real mobile device.
- Return on a separate test transaction and verify check-in, earning, and redemption.
- Remove or clearly label the test profile when the audit is complete.
Verify every terminal and receipt setting
Do not assume one successful register represents the entire restaurant. Test each device type, service area, and ordering channel that can enroll or recognize members. A front counter, handheld, kiosk, online checkout, and catering invoice can follow different flows even when they feed the same guest database.
Square notes that some Android and Square Register configurations need the receipt screen and automatic receipt settings adjusted for the loyalty screen to appear. That detail is specific to Square, but the operator lesson is broader: a device-level setting can hide an otherwise configured program. Compare the live settings on every device instead of relying on the account dashboard alone.
- Use the same test script on every register and handheld.
- Check whether skipping or auto-printing receipts changes the enrollment prompt.
- Verify guest-facing displays are enabled where your platform requires them.
- Repeat the audit after terminal replacement, app updates, or checkout redesigns.
Prevent duplicate guest profiles
Duplicate profiles can split a guest's visit and reward history. During the audit, enroll once, then return with the same identifier and confirm the system recognizes the existing member. Repeat with another permitted payment method to see whether the membership remains attached correctly.
Also define a staff-safe recovery path for guests who changed phone numbers, entered a number incorrectly, or cannot find a reward. Staff should not improvise account merges or ask guests to expose more information than the system requires. Use your provider's approved profile-update process and document when a manager should take over.
- Test recognition with the same identifier on a second visit.
- Check whether another payment method still resolves to the same membership.
- Document the approved correction process for an outdated identifier.
- Track duplicate-profile incidents as a separate operational issue.
Test earning, visibility, and redemption separately
Enrollment, earning, reward visibility, and redemption are four different checkpoints. A guest can successfully join but still fail to see points, find a status page, or apply a reward later. Record each checkpoint independently so the team fixes the actual break instead of calling the whole program broken.
Square's documentation says customers can receive a welcome SMS, view loyalty status, and redeem at checkout through supported paths. It also notes that channel behavior can differ; for example, its invoice flow can accrue points but does not redeem rewards. Treat vendor documentation as the starting map, then verify the exact channels your restaurant uses.
- Confirm the eligible purchase produced the expected earning event.
- Verify the guest can find the balance or reward status afterward.
- Apply a reward in a later test transaction and check the final receipt.
- List channels that earn points but cannot redeem, if any.
- Train staff on the verified behavior rather than the advertised feature list.
Measure the funnel without claiming causation
Build a small weekly loyalty scorecard from events your systems can verify: eligible transactions, enrollment prompts shown, completed enrollments, recognized returning members, reward redemptions, and duplicate-profile support cases. If a platform cannot expose one event reliably, label that gap instead of estimating it.
Change one part of the path at a time, such as the staff prompt, the post-transaction timeout, or the placement of a signup reminder. Compare the same event counts before and after the change while watching checkout time and guest complaints. An improvement in one metric is a signal to investigate, not proof that the change caused more repeat visits.
- Keep eligible transactions as the denominator for enrollment checks.
- Separate completed enrollment from later recognition and redemption.
- Record checkout delays and guest confusion as guardrails.
- Review the test after any POS, loyalty, receipt, or online-ordering change.
Submit a restaurant or local business.
Share the business details, useful links, and what makes the place worth knowing for possible Restaurant Tech Report coverage.
FAQ
Does this audit require Square Loyalty?
No. Square's support pages are used as a transparent vendor example of how checkout enrollment, identifiers, status messages, and redemption can interact. Apply the audit to the live documentation and settings for your own POS, loyalty, and ordering providers.
What should a restaurant verify first?
Start with one eligible purchase on the busiest checkout path. Confirm the prompt appears, enrollment completes, the reward is visible, and the same member is recognized on a separate transaction before staff actively promote the program.
How often should the loyalty checkout path be retested?
Retest after terminal changes, POS or loyalty updates, receipt-setting changes, new ordering channels, or program-rule edits. A short scheduled check can also catch device drift before guests report it.