Buyer guide · QR workflow
A QR-code loyalty program that works at the counter.
The QR code should shorten the loyalty handoff. The program still needs a clear earning rule, a staff routine, and a fallback when a camera or connection fails.
- Customer entry
- Business or program QR
- Counter action
- Scan, hardware reader, or search
- Fallback
- Member lookup and typed codes
Short answer
Start with the operating rule.
Use QR codes to move customers into the right program and let staff retrieve the right member at the counter. Reward Loyalty supplies printable program codes, a business-page code, member codes, and staff scanning options. The QR layer supports the loyalty workflow; it does not decide the earning rule or replace staff validation.
Who it fits
Use this model when the work matches.
A feature can exist in the product and still be the wrong starting point for a business. These conditions make the recommendation useful.
A visible counter or service handoff
The business has a natural moment to show a joining code and ask for the member code before staff complete the loyalty action.
A program that can run beside the till
The operator can start with the manual counter workflow and connect a POS later through the supported integration paths when that work earns its keep.
A customer benefit worth the scan
The code leads to a clear points card, stamp card, voucher, or prepaid pass. A QR code without a useful offer only adds another step.
Setup
Configure the decisions in this order.
The order keeps presentation work from hiding an unresolved commercial or operational rule.
-
1
Choose the loyalty mechanic first
Set the earning rule, qualifying action, reward, limits, and staff approval before printing anything.
-
2
Choose the entry code
Use the permanent business-page code when customers need to see several programs. Use a program code when one offer should open at once.
-
3
Set the member onboarding policy
Use email verification for a recoverable account. Enable anonymous members only when faster entry matters more than collecting an email at the first visit.
-
4
Prepare the counter route
Test the built-in camera, a phone camera, customer search, and any fixed 2D scanner the team will use.
-
5
Print from a tested file
Open the destination, scan the printed proof from an ordinary customer distance, and keep strong contrast around the code.
Operating workflow
What happens after launch.
The workflow matters because every extra counter decision raises training cost and increases inconsistent treatment.
Customer scans
The business-page or program code opens the relevant public page. A new customer signs in, registers, or enters through anonymous mode if the operator enabled it.
Customer presents one member identity
The wallet-level code identifies the member at the counter. A saved image, printed member card, typed code, or staff search can provide a fallback.
Staff confirms the action
Staff check the member and program, then award points, add stamps, redeem a reward, or record a pass visit.
Member sees the result
The open wallet updates after the server records the action. Saved QR codes remain displayable offline, while the staff transaction still needs a connection.
Product and operating limits
Know the boundary before launch.
A clear limit protects the buyer from choosing the feature for work it does not perform.
- A QR code is a route into a workflow, not proof that a purchase, visit, or redemption should count.
- The built-in camera scanner needs HTTPS and permission to use the camera. Staff can use a phone camera, hardware scanner, or customer search when it is unavailable.
- Member codes can display offline after the wallet has cached them. Staff still need network access to write the loyalty transaction.
- The manual counter flow does not prevent a later POS or commerce integration. Build that connection only when the required event and reconciliation rules are clear.
Implementation guides
Continue in the current product documentation.
Each link opens the setup or operating workflow behind the recommendation above.