1. Digital Stamp Card QR
The paper stamp card is dead for most retail and hospitality contexts. A QR at point of sale links to the digital stamp card. Customers scan to add a stamp. Benefits over paper:
- No lost cards (account-linked, not device-linked).
- No fraudulent stamp-offs.
- Automated reward triggers (10th stamp = free drink, sent via push or email).
- CRM data: you know who your loyal customers are and can contact them.
2. Transaction QR for Points
At checkout, the cashier displays a transaction QR (or the customer scans their member QR). The points engine calculates points for the transaction value and credits the account. The customer receives instant confirmation on their phone.
3. Tier Progress QR
A QR in the loyalty programme app or monthly statement email links to the tier progress page: points to next tier, tier benefits comparison, and personalised actions to reach the next tier (e.g., "Make 2 more purchases this month to reach Gold").
4. Referral QR within Loyalty
Each member has a referral QR encoding their unique referral code. Sharing earns bonus points when a new member registers. The referral QR is the most cost-effective acquisition channel in mature loyalty programmes — referred members show 25% higher lifetime value than acquisition-channel members.
5. Partner Reward QR
Coalition loyalty programmes (e.g., earn at multiple brands) use QR codes at each partner's point of sale. The partner QR is unique to the coalition programme, allowing the central points engine to attribute transactions correctly across all participating brands.
Putting this into practice
Start with the smallest real test you can run. Generate the code, print it at the exact size you plan to use, and scan it with two different phones in the lighting where it will live. Check that the destination page loads quickly on a mobile connection and that the call to action next to the code tells people what they will get. If anything feels slow or unclear, fix it before you print a full batch, because reprints cost more than a short test. Keep a note of the size, material, and placement that worked so the next batch starts from a proven setup.
Common mistakes to avoid
The most common mistakes are easy to avoid once you know them. Long payloads make modules tiny, low contrast makes edges hard to read, and text placed too close to the border eats the quiet zone the scanner needs. Covering a corner finder pattern with a logo or a sticker breaks detection entirely, and a code placed behind glare or on a curved surface fails even when the print is perfect. Review each of these points on a proof copy, and treat any failure as a reason to adjust the design rather than a reason to blame the scanner.
Quick checklist
- Keep the payload as short as practical so modules stay large.
- Keep dark modules on a light background with strong contrast.
- Leave a clear quiet zone on all four sides of the symbol.
- Test the printed code at the real viewing distance and lighting.
- Confirm the destination page loads fast on a phone.
- Recheck the code after any change to the link, design, or placement.
Related tools and guides
- For local payments, the [Pakistan payment QR](/pakistan-payment-qr) page explains the regional flow and what customers see.
- The [regional payment QR](/regional-payment-qr) guide covers payment codes used across different markets.
- The [bulk generator](/bulk-generator) builds many codes from a table when one-off generation would take too long.
- Test every code with the [QR scanner](/qr-scanner) on more than one phone before you publish or print it.
- The [UTM builder](/utm-builder) adds campaign parameters so scans show up separately in your analytics.
- The [blog](/blog) collects more guides on sizing, printing, security, and payments for QR codes.
