A QR code can scan perfectly and still send people to a broken or frustrating page. Before printing posters, menus, or packaging, check both the code and the experience it leads to. This checklist covers destination stability, mobile usability, print-proof testing, and the details that help a code scan reliably.
Key Takeaways
- Test the final printed proof at its actual size—not just a file on your screen.
- Scan from the distances and angles people will use, with more than one device.
- Keep the destination under a domain you control, and plan how you will handle future changes.
- A successful scan confirms only that the code can be read. Check that the page is useful, accessible, secure, and trustworthy too.
- Preserve clear space around the code and use strong contrast; test the finished design after any branding changes.
1. Confirm the destination before generating the code
Open the exact URL you intend to encode. Check the spelling, page content, and any query parameters, such as campaign-tracking tags. A typo or unwanted tracking value is easy to reproduce across thousands of printed copies.
Prefer a URL on a domain your organization controls. A short URL can be easier to read and may produce a less dense code, but only use a shortening service if you trust it and understand what happens if its account or service becomes unavailable.
Decide what happens if the destination needs to change after printing:
- A fixed destination: The QR code contains a URL that will stay useful. Keep that page available for the expected life of the print material.
- A changeable destination: The QR code contains a URL on a domain you control, and your server redirects that URL to the current page. You can update the redirect without replacing the printed code, provided you keep control of the domain and redirect configuration.
- A provider-managed dynamic code: A vendor may let you change the destination through its service. Check its ongoing terms, account requirements, and what happens if the service or subscription ends. The printed code depends on that service remaining available.
A code that directly encodes a destination generally cannot be edited after printing. For a redirect-based setup, test the redirect itself, keep it active as long as the print is in circulation, and avoid sending visitors through unnecessary redirect hops. Use HTTPS and make sure any change points to the intended page—not an unreviewed or user-controlled destination.
2. Check the landing page on a phone
Scan the code and review the page on a real mobile device. Confirm that it:
- Loads at the expected URL and does not end in an error, blank screen, or unexpected login wall.
- Fits a small screen without horizontal scrolling or tiny, hard-to-use controls.
- Shows the information promised beside the QR code, such as a menu, event details, or product instructions.
- Gives visitors a clear next step and does not require an app unless that requirement is clearly explained.
- Uses readable text, sensible heading order, and links or buttons that are usable with a keyboard and assistive technology.
- Presents a recognizable organization or business, uses HTTPS, and avoids surprising redirects or download prompts.
If the content is time-sensitive, include a useful fallback for when it expires. For example, a past-event page can explain that registration has closed and point to current information instead of displaying a dead end.
A scan is not a quality review. The camera may decode the pattern even when the destination is irrelevant, inaccessible, misleading, or no longer maintained.
3. Check the printed design
Review the QR code in the complete design, not in isolation. The size and clarity of its small squares—the modules—affect how much information a scanner must distinguish. A longer encoded URL or added logo can make the pattern denser, so avoid shrinking a code merely to fit a layout. If space is tight, consider a shorter destination on a domain you control, then generate and test the code again.
Keep a clear quiet zone around the code: an uninterrupted margin that separates it from text, borders, images, and other marks. QR Code guidance describes a margin of at least four modules around the symbol. Do not crop that margin or fill it with decoration. Also avoid placing text or artwork over the code unless the finished design has been carefully tested.
Use strong contrast between the code and its background. A dark code on a light, plain background is a dependable starting point. Avoid low-contrast colors, gradients, reflective finishes, or busy backgrounds. Accessibility guidance on non-text contrast is a useful reminder to make important visual information distinguishable, but it is not a substitute for testing whether a QR scanner can read a particular print treatment.
4. Test the final printed proof
Use this checklist after the design has been exported and printed at its intended size. A screen preview alone cannot confirm how ink, paper, finish, and print scaling affect the result.
- Verify the artwork. Scan the code from the actual proof and confirm that it opens the intended destination. If you revise the artwork, repeat the test on the revised proof.
- Test realistic distances. Try the closest and farthest distances people are likely to scan from the placement. For a tabletop menu, that may be arm’s length; for a poster, test from where someone would naturally stand. There is no single distance that suits every code size and setting.
- Use more than one device. Test with at least two different phones, preferably with different camera or QR-scanning apps. Make sure the page finishes loading, not merely that the phone recognizes the code.
- Test the real conditions. Check the proof under the lighting and viewing angle expected at the venue. If the material will be glossy, curved, or placed behind a barrier, test that kind of surface too.
- Check the whole journey. Confirm the final page, redirects, campaign parameters, and any sign-up or checkout step. Check that the page remains usable on mobile data as well as Wi-Fi if visitors may not have access to your network.
- Repeat after changes. Re-test if the code is resized, recolored, given a logo, moved onto different material, or paired with a new destination.
If a scan fails, first inspect the print size, quiet zone, contrast, and surface. Then try a less dense code or a simpler design. Do not assume that one successful scan in a design app guarantees that customers can scan the physical item.
Common Mistakes
- Testing only the QR image on a computer. The physical proof may have different size, contrast, glare, or print quality.
- Changing the destination without checking the printed URL. A static code cannot be edited; a redirect-based code works only while its redirect remains available and correctly configured.
- Using an unfamiliar short-link domain. Visitors may hesitate to open a link they cannot recognize, and a third-party service adds a dependency.
- Removing the margin to make the code fit. Nearby artwork can interfere with recognition.
- Adding a logo or decorative colors without re-testing. A design that looks attractive may make the code harder to scan.
- Treating a scan as proof that the page is good. Scanning does not verify relevance, accessibility, mobile usability, or trustworthiness.
Best Practices
- Put a short instruction next to the code, such as “Scan for the menu,” so people know what to expect.
- Use a stable URL on a domain you control, and document who can update any redirect.
- Keep a record of the encoded URL and the final approved artwork.
- Include a readable fallback URL or another way to get the information when appropriate, especially where people may not be able to scan.
- Recheck the destination periodically while the printed material remains in use.
Conclusion
Before approving a print campaign, test the destination, mobile page, and final physical proof. A clear, well-sized code and a maintained, trustworthy landing page make the scan useful—not just successful.
References
- DENSO WAVE: About QR Code — background on QR Code characteristics and structure.
- W3C: Understanding Success Criterion 1.4.11, Non-text Contrast — accessibility context for distinguishing visual information.