The kiosk reads what the phone shows.
2D imaging is compounding at 6.8–9.8% CAGR inside a $1.6 B retail-focus scanner market (2025 market reports), and the ticket, parcel and prescription queues keep moving to self-service. In kiosk fixture tests our X series reads dimmed and curved display codes at ≥95%. The window — not the waiter — now owns the read.
Four pressures that decide a kiosk scan program.
- Screen codes are not labels: phones hit the window tinted, dimmed and tilted; the engine has to hold ≥95% first-pass class on the traffic mix the booth actually sees.
- The fascia owns the geometry: ticket pods and cabinet doors give the engine a thin sliver of window — the X22 bare core exists precisely for that build, and smart-locker and pharmacy-cabinet runs are a named reference class for it.
- Queues punish retries: at peak hours the difference between one read and three is the whole queue; sustained-flow firmware behavior shows up faster than any spec sheet promises it.
- 24/7 posting: parking, transit and cabinet sites run continuous duty — the 2-year warranty plus a 10–25-day production window (under 5,000 pcs) is what lets an operator stock spares by schedule.
What a 2026 kiosk program needs
| Requirement | Reference target | Our lines |
|---|---|---|
| Screen QR capture | Dimmed and curved display codes, ≥95% class in kiosk fixture tests | X9 / X22 / X10 |
| Labels & documents | 4 mil precision class — QR, DataMatrix, PDF417, full 2D set | All X-line |
| Embedding form | Bare core riding inside your own fascia | X22 |
| Mount geometry | Riser and rack-rail position for elevated windows | X10 |
| Duty | Sustained-flow station class, 24/7 venues | X9 / X30 |
| Control path | Serial trigger/result, MCU-driven via free SDK | X22 |
| Host interfaces | USB HID/CDC + RS232 | All X-line |
| Read range | 0–80 cm class (family-class value) | Per-model curve in datasheet |
Your fascia, the family's engine.
- X22 bare core behind the reader window of ticket pods and lockers — serial trigger/result lets the kiosk controller sequence a concession QR, a ticket PDF417 and a parcel DataMatrix through one engine.
- X9 for the sustained flow of high-traffic windows; X10 for the riser-mounted position that looks down at the work deck.
- Same decode silicon and the same SDK dialect across all three — one firmware track for your whole venue fleet, and one FAE contact.
- MOQ 1 pc for the mock-up: send the fascia drawing and three app screenshots, and the fixture verdict comes back within 48h.
What integrators report after switching.
Kiosk integrators take their app's real screen codes through a fascia mock-up before the mold: the ≥95% class verdict is measured in the fixture session, not promised in a datasheet.
Pattern · Kiosk integrators — EU & North America
Automated locker builders drive the X22 core from the cabinet's own controller — the serial command set lives in firmware, and there is no PC anywhere in the building.
Pattern · Locker & cabinet builders — Middle East & Southeast Asia
Transit ticketing operators hold peak-day logs where dimmed screens keep their first-pass reads; spares planning rides on the 2-year warranty and the 10–25-day production window.
Pattern · Ticketing operators — Asia-Pacific
Kiosk FAQs
That is an optical-path question, and it is answered by a fixture, not by us guessing: send your glass and mount, and the FAE returns a window plan with read distances within 48h. No glass spec promise without the session.
The engine family is graded by first-pass rate on your actual traffic — dimming, tilt and polarizing films included. One unit in a 48h mock-up raises the true worst case before you commit a fleet.
Yes — serial trigger/result via a small MCU is the standard pattern; the free SDK ships embedded examples, and the FAE line reviews your controller interface within 48h.
Qualify the window before the mold.
Send your fascia drawing and three screenshots of the app — we return a coverage matrix, updated SDK links and a sample offer within 48h.
