Validate the encoded content first
Scan the downloaded PNG or SVG and compare the decoded text or URL character by character with the intended value. Check HTTPS, spelling, uppercase and lowercase characters, WiFi security type, contact fields and any query parameters. Open links in a private browser to reveal permissions or login requirements hidden by an existing session.
For static codes, treat approval as permanent: changing the destination requires a new QR image. Record the approved destination, file name, revision date and owner so an old artwork cannot return during a later print run.
Test representative devices and camera paths
Use at least one current iPhone and one current Android device when the audience is mixed. Test the built-in camera and, if relevant, the specific warehouse scanner, banking app or event app used in the workflow. A code that works in a generic scanner may not be accepted by a specialized application expecting a particular data format.
Scan from the expected distance, then try a reasonable off-axis angle and lower light. Measure whether a person can discover the code, understand the call to action and reach the destination without staff explanation.
Test the real production output
Print at the final physical size using the intended printer, paper, label stock, ink and finishing. Check that the quiet zone remains clear after cutting, that bars or modules are not stretched and that lamination or packaging does not create glare, folds or curvature.
For a large order, request a physical proof and scan several samples from different positions on the sheet or production batch. Variation near the minimum readable size can turn a successful proof into inconsistent production results.
Plan monitoring and replacement
Assign an owner and review interval for public codes. Recheck after a domain migration, menu update, password change, payment-provider change or redesign. Inspect public stickers for damage and replacement labels.
Keep the original editable artwork, approved export and destination record together. A simple maintenance log makes it faster to identify which signs or packages must be replaced when content changes.
QR testing stages
| Stage | What to verify | Evidence to keep |
|---|---|---|
| Content | Decoded value exactly matches the approved destination | Destination record and revision |
| Devices | Representative phones or workflow scanners succeed | Device and app test notes |
| Production | Final size, stock, finish and lighting remain readable | Physical proof or photographed sample |
| Maintenance | Destination and public code stay valid | Owner, interval and replacement log |
Pre-production checklist
- Scan the exported file rather than only the preview
- Open the destination in a private browser
- Test representative iPhone and Android devices
- Use the final size, printer, stock and finish
- Try realistic distance, angle and low light
- Record the owner, destination and next review date
Frequently asked questions
How many phones should test a QR code?
Use representative devices rather than a fixed number. For a public consumer code, at least one current iPhone and one current Android device is a practical minimum, followed by the specialized app or scanner when required.
Why does a QR code work on screen but fail after printing?
Printing can reduce module sharpness, crop the quiet zone, lower contrast or add glare and distortion. Test the exact final material and size.
Do I need to retest a static QR code?
Yes. The pattern does not expire, but its destination, physical condition and surrounding environment can change.