How the phone resolves the experience
Scanning a QR code with a mobile device is no longer a technical hurdle for most visitors. Since iOS 11 and Android 8, native cameras on both platforms have recognised QR codes without requiring a separate application. The user points the camera at the code, a notification appears, and tapping it triggers the encoded action—typically opening a URL in the device browser.
This simplicity, however, masks several variables that affect whether a scan actually succeeds in a real-world environment. The camera must resolve the code's modules clearly enough for the software decoder to read the pattern. That depends on the code's physical size, the distance between the phone and the surface, lighting conditions, the angle of approach, and the quality of the printed or displayed code itself.
Two distinct scanning paths exist. The first is the native camera, which handles standard QR codes containing URLs and plain text. The second is scanning within a dedicated app—such as a venue's own application or a ticketing wallet. In-app scanning can trigger behaviours that a browser cannot, such as updating the user's location on an indoor map or logging the interaction against a known profile. The trade-off is friction: asking a visitor to download or open an app before scanning adds a step that reduces completion rates, particularly in transient settings like events or high-street retail.
For venues and retailers evaluating QR as part of a proximity strategy, the scanning experience is the point where physical infrastructure meets visitor behaviour. A code that works on a desk under office lighting may fail repeatedly when mounted at shoulder height in a dimly lit corridor. Understanding what happens during those few seconds between camera activation and content delivery is essential before committing to a deployment.
Design for successful first-time use
Retail environments
In shops, QR codes are typically placed on shelf edges, product displays, window posters or till points. The scanning distance is usually short—within arm's reach—so module size can be relatively small. The priority is ensuring the code is positioned where a customer can comfortably point a phone without blocking aisles or knocking stock. Codes placed at the base of a shelf, for example, require the visitor to crouch, which many will not do. Codes on reflective surfaces or behind glass can produce glare that defeats the camera's contrast detection.
A common retail use case is linking to product details, stock availability or variant options that the physical shelf cannot display. Another is payment redirection, where the scan opens a payment URL. In both cases, the page that loads must be optimised for mobile, render quickly on a retail Wi-Fi or cellular connection, and present the relevant information without requiring the visitor to scroll past navigation menus or cookie banners.
Museums and heritage sites
Museums use QR codes to deliver exhibit text, audio guides, video or deeper catalogue information. The environment differs from retail in important ways. Lighting is often deliberately low to protect sensitive objects. Visitors may be moving through in groups, making it impractical to step close to a label. Codes are sometimes placed at varying heights depending on the exhibit, from floor-level installations to overhead pieces.
For museums, the scanning distance is less predictable than in retail. A code on a plinth next to a small object might be scanned from 20 centimetres, whereas a code on a wall panel for a large painting might need to be readable from 60 centimetres or more. This directly affects the minimum physical size of the printed code. As a practical rule, the scanning distance in centimetres should be roughly matched by the code's width in millimetres—so a code intended for 60 cm scanning distance should be at least 60 mm wide, with a margin of quiet zone around it. This is not a guaranteed formula, because phone cameras vary, but it provides a starting point for physical testing.
Planning note: Treat numeric examples as illustrative until the same configuration has been measured in the intended venue and operating conditions.
Events and temporary installations
At conferences, exhibitions and festivals, QR codes appear on lanyards, badges, posters, screens and table signage. The scanning context is often hurried: attendees walking between sessions, holding a drink, or balancing a bag. Codes need to be large, high-contrast and placed where the visitor can approach straight on. Angled placements on tent walls or curved surfaces distort the code geometry and increase decode failures.
Temporary setups also introduce the question of printed versus displayed codes. A code shown on a digital screen avoids print-quality issues but introduces screen glare, refresh-rate artefacts on some displays, and the risk that the screen content changes before the visitor scans. Printed codes on laminated cards or rigid boards are more predictable but must be checked for smudging, creasing or adhesive damage during setup and throughout the event.
Failure modes and recovery options
Insufficient quiet zone
The quiet zone is the blank margin surrounding the QR code's three position-detection patterns. If text, logos, borders or other graphic elements encroach into this space, decoders frequently fail to recognise the code. This remains one of the most common print errors. The quiet zone should be at least four modules wide on all sides. If a designer has placed a logo inside the code or butted text against its edge, the code should be tested on multiple devices before going to production.
Low contrast or poor print resolution
QR codes rely on contrast between dark and light modules. Light grey on white, or a dark colour on a busy photographic background, reduces the signal the camera can distinguish. On printed materials, ink bleed on uncoated stock can blur adjacent modules together. For small codes—particularly those encoding long URLs—this blurring is enough to make the code unreadable. Checking a printed proof with a phone before committing to a full print run takes seconds and prevents costly waste.
Assuming universal scanning behaviour
Not all visitors are familiar with QR scanning. Some will try to photograph the code rather than scan it, resulting in an image in their camera roll rather than an opened link. Others will not notice the code at all without a clear call to action. A simple instruction such as "Point your camera here" alongside the code significantly improves scan rates compared to leaving the code unlabelled. For older visitors or those with less smartphone experience, a brief line explaining what will happen after scanning—"Opens exhibit information in your browser"—reduces uncertainty.
Ignoring device and platform variation
Camera quality, decoder implementation and default browser behaviour differ between devices. A code that opens instantly on a recent iPhone may trigger a delay, an error page or an unexpected app prompt on an older Android handset. If the target URL relies on JavaScript, certain in-app browsers on Android handle it differently from Safari or Chrome. Testing across at least three different devices—including an older or budget-model phone—before deployment catches problems that a single-device test will miss.
Placing codes in inaccessible or awkward positions
Codes behind physical barriers, above head height, on the underside of surfaces, or in locations where the visitor would block the code with their own body while trying to scan it will see low engagement. The test is straightforward: stand where the visitor would stand, hold a phone as they would hold it, and attempt the scan without moving obstacles or adopting an unnatural posture. If it feels awkward, the position needs to change.
Key pre-deployment checks
- Scan the printed or displayed code from the expected visitor distance and angle on at least three different devices.
- Verify that the landing page loads within a few seconds on a typical mobile connection and displays correctly without horizontal scrolling.
- Confirm the quiet zone is clear of all graphic elements, text and borders.
- Check for glare or reflections at the intended placement under the actual lighting conditions, including at different times of day if the space has natural light.
- Ensure a clear, concise call to action accompanies the code.
- Test what happens if the visitor has no cellular signal and the venue Wi-Fi requires a captive-portal login—does the scan still deliver value, or does it fail silently?
QR code scanning on mobile devices is technically straightforward, but reliable deployment in a physical space demands attention to the environment, the printed artefact and the visitor's posture and device. Treating the scan as a user experience rather than a simple link redirect is what separates a code that works from one that sits unnoticed on a wall.
