Points-Based vs Stamp-Based Loyalty
Stamp systems: Simple. Fixed number of visits or purchases for a reward. Transparent and low-barrier for customers to understand.
Points systems: More complex but more flexible. Points awarded per £ spent. Points redeemed against a points-to-value scale. Tiered status levels possible.
QR codes work in both models — they are the access mechanism for the customer to identify themselves and accumulate value.
Building a QR Points Programme
Core mechanics:
- 1 point per £1 spent (or your chosen ratio)
- Points balance visible in app or via text message lookup
- Redemption: 100 points = £1 discount (or free item equivalent)
- Points expiry: 12 months from last transaction (standard UK practice)
Tiered programme:
- Bronze: 0–499 points earned in 12 months
- Silver: 500–1,499 — additional benefit (priority access to new products, 1.5x points events)
- Gold: 1,500+ — premium benefits (free shipping, exclusive discounts, early sale access)
Each tier is identified by the QR in the member's app — the till system reads the tier from the QR and applies the appropriate benefit automatically.
Personalised Offers via QR
Once a customer's purchase history is linked to their QR loyalty ID, personalised offers become possible:
- "You haven't bought X in a while — here's 20% off"
- "You always buy Y on Fridays — here's a Friday bonus points offer"
- "It's your birthday month — 50 bonus points when you visit this week"
These personalised offers, triggered by purchase-history data and delivered to the customer's app or by email, convert well because they are individually relevant.
QR Loyalty at the Point of Sale
The customer presents their loyalty QR at the counter before or after the transaction. The till scans it. Points are added. If a reward is due, it appears on the till screen. The whole interaction takes under 5 seconds.
Alternatively, for app-less implementations: the customer gives their phone number, the till looks up their account, points are logged. QR optional for customers with the app.
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.
