Quick answer
Test the final QR artwork on several real phones, at the intended printed size and distance, then complete signup and wallet installation. Confirm the destination domain, accessibility, weak-connection behavior and staff fallback.
Verify the destination before visual quality
Scan with the native camera on current iPhone and Android devices. Read the previewed domain before opening it and confirm HTTPS, the correct card and the expected business identity. The FTC warns that malicious QR codes can disguise harmful links; a merchant should control the destination and inspect replacement stickers.
Test the exact URL that will be printed, including campaign parameters. A shortened or redirect-heavy link adds failure points. Keep a written destination record so staff can recognize tampering and a future editor does not unknowingly reuse the artwork for another card.
Test the physical context
Print at 100 percent scale. Scan from the expected queue distance under bright light, dim light and glare. Try a slightly curved menu, countertop sign and phone screen. Preserve the quiet margin around the code; do not let a logo, fold or decorative pattern obscure modules.
The QR opens a page, but the page still needs usable buttons. W3C target-size guidance supports making interactive controls large enough to activate without precision. Check zoom, screen-reader labels, color contrast, keyboard focus and error messages on the signup form.
Complete the journey, not just the scan
Use a new test identity to submit the form, receive the card and add it through every installation option you advertise. Then open the card again, redeem a test reward and confirm staff can locate the record. A successful camera scan alone proves very little.
Throttle the connection or test on a weak mobile network. Provide a short readable fallback URL or staff-assisted route that does not require the customer to disclose credentials aloud. Record which device and browser failed before changing the design.
A practical pilot
Create a test matrix with device, operating system, browser, printed material, size, distance, lighting, network, signup result and wallet-install result. Require two people who did not create the QR to complete it. Re-test the production sample from the printer.
Use a staff test account first. Save the transaction or booking reference, the rule applied, the resulting customer balance and the person who made any correction. Review edge cases before inviting the public. A loyalty card is the customer-facing record of an offer; it does not replace the booking, payment, inventory or accounting system that proves what happened.
Boomerangme documents digital stamp cards and reward cards. You can explore Boomerangme to compare those mechanics with this workflow. This independent journal does not imply a native integration with the businesses or systems cited here. Verify the current settings in your own account and keep the primary operational record in the system that owns it.
What to record and review
For “How to Test a Loyalty QR Code Before You Print It,” keep a compact decision log beside the operating system that proves the transaction. Record the customer-facing rule version, qualifying reference, date, location or channel, value added or removed, staff user and exception reason. Do not copy sensitive operational notes into a public-facing wallet pass. Review a small sample weekly during the pilot: one ordinary earning event, one redemption, one correction and one case that did not qualify. Compare the saved record with what the customer can see. This is especially important for the how-tos workflow described here, because a card balance alone cannot explain a booking state, refund, product exclusion or staff override. If the same exception appears twice, improve the written rule or checkout process instead of relying on memory.
Quick questions
How many phones should test the QR code?
Use at least representative iPhone and Android devices plus the browsers and installation routes your customers actually use.
Is a successful scan enough?
No. Complete signup, installation, reopening and a test staff transaction.
What should staff do if a customer cannot scan?
Offer a readable first-party URL or assisted signup route without asking the customer to reveal passwords or private codes.
Sources & further reading
- FTC consumer alert on QR codesUS consumer-security guidance on checking QR destinations; checked October 23, 2026.
- WCAG 2.2 target size guidanceW3C accessibility guidance for interactive target size; checked October 23, 2026.
- Boomerangme stamp card documentationPrimary product documentation checked October 23, 2026.
Sources reviewed .
Numerical examples are illustrative unless a cited source states otherwise.