QRForge

QR codes for self-service kiosks

Start on your phone, finish at the kiosk โ€” skip the on-screen typing.

Recommended: Dynamic URL
๐Ÿ“ท Image placeholder
A QSR self-service kiosk with a QR code visible on the screen frame for phone-based ordering handoff
Suggested source: Your own photo, or Wikimedia Commons search: 'self-service kiosk'
A phone-handoff QR on the kiosk bezel removes the on-screen-keyboard bottleneck. ยท Source: Your own photo, or Wikimedia Commons search: 'self-service kiosk'

The kiosk industry has a problem it doesn't like talking about: the Americans with Disabilities Act applies, and a lot of deployed kiosks don't fully comply. DOJ rules under ADA Title III require that self-service kiosks โ€” whether for airline check-in, restaurant ordering, or patient intake โ€” be accessible to people with disabilities, and a string of settlements with airlines and restaurant chains (Eatsa's 2017 NFB settlement is the canonical one) has made clear that a touchscreen-only interface with no accessible alternative is a lawsuit waiting to happen. A QR code that routes the interaction onto the customer's own phone is not just a UX improvement; in many cases it's part of the accessibility answer, because the customer's phone already has their preferred screen reader, font size, and language configured. The other structural issue is throughput. McDonald's Experience of the Future kiosk rollout, which started around 2015 and went global by the early 2020s, proved that kiosks lift average order value noticeably โ€” Deutsche Bank analyst estimates of the effect were frequently cited in industry press at the time. But kiosks also have a bottleneck: the second person in line watching the first person type an email address into an on-screen keyboard. A QR that hands off the session to the customer's phone โ€” they type on their own keyboard, submit, and the kiosk renders the order for confirmation โ€” removes the slowest single step in the interaction. Three patterns are worth doing. Phone-first session handoff for typing-heavy flows. A QR-linked accessible alternate for users who can't reach or use the touchscreen. Per-kiosk dynamic QRs for real-field analytics, because you almost certainly don't know which of your kiosks actually get used.

Pattern 1Dynamic URL

Phone-first session handoff for typing-heavy flows

Every kiosk flow that asks for an email, a loyalty ID, or a delivery address suffers the on-screen-keyboard tax โ€” typos, slow input, and the deeply inefficient dance of people behind in line watching. The handoff pattern inverts it: the customer scans a QR on the kiosk, a companion page opens on their phone pre-populated with a session token, and they complete the typing-heavy sections on their own device. The kiosk screen polls the session and updates in real time; the customer confirms, pays, and leaves. The QR itself is static per kiosk, but the session token is minted fresh on each tap so there's no cross-talk between customers. Toast, Square, and several airline check-in vendors all quietly ship a version of this; it's invisible when it works, which is why most operators haven't noticed they're behind. Implementation is easier than it sounds โ€” a short-lived token in the URL hash, a WebSocket on the kiosk, and a responsive form. The ROI is throughput: order completion times drop noticeably when the typing moves off the shared screen.

Pattern 2Dynamic URL

Accessible alternate that keeps you out of an ADA lawsuit

The ADA settlements that have hit restaurant and airline kiosks in the last decade share a common theme: the operator offered no functionally equivalent path for users who couldn't see, reach, or operate the touchscreen. A QR labeled 'Need an accessible version? Scan here' that routes to a mobile web form with proper semantic HTML, ARIA labels, and full keyboard support is a reasonable step toward compliance โ€” it lets the customer use their phone's native accessibility stack (VoiceOver on iOS, TalkBack on Android) instead of relying on the kiosk's typically worse assistive hardware. The Department of Justice published specific guidance on self-service kiosks in 2024 under an ADA Title II rule update; while the rule technically covers state and local government, the direction of travel is clear for private-sector operators too. The pragmatic approach: build the mobile alternate first, make sure it's functionally identical, print the QR prominently, and document the decision. The insurance case for this alone is cheaper than a single settlement.

Pattern 3Dynamic URL

Per-kiosk dynamic QRs as field telemetry

Most kiosk vendors bundle analytics, but the analytics are heavily focused on completed orders. What you're missing is the 'they walked away' data โ€” the customers who approached a kiosk, looked at it for five seconds, and went to the counter instead. A dynamic QR unique to each kiosk, placed prominently with copy like 'Scan to order on your phone,' captures scan volume per device. A kiosk with high scan volume and low completion is a kiosk with a broken touchscreen, glare from an overhead light, or a busted card reader โ€” all fixable, none of which show up in your standard dashboard because the customer never got to the problem. Pair this with a simple 'report a problem' sub-link from the same landing page and you get field telemetry the vendor doesn't provide. Elo Touch, Pyramid Computer, and other enterprise kiosk hardware vendors all ship remote-diagnostics SDKs, but the QR crowd-sourced signal is faster and catches class-of-problem issues (bad placement, confusing signage) that hardware telemetry never sees.

๐Ÿ“ท An airline check-in kiosk with an accessibility QR code on the side panel
Your own photo
Source: Your own photo

Printing and placement tips

Build one now

The free generator handles every pattern above. Upgrade to Pro when you want dynamic destinations or scan analytics on top.

Further reading and sources

Related

โ† All use cases
QR codes for self-service kiosks ยท QRForge