Kiosk implementation checklist
Run a kiosk rollout in three stages — architecture, testing, and launch — and know where to send each type of problem.
Work through a kiosk rollout in the order below so the expensive surprises surface early. Most kiosk projects fail at the testing stage for reasons that a one-hour architecture call would have caught.
Stage 1 — Agree the architecture
Get your kiosk provider, your OmniLab contact, and whoever owns the venue network in the same meeting. Confirm:
- Scanner output — which barcode types the scanner reads, and the exact text it produces.
- Web frame — the browser engine and version, JavaScript, touch handling, and full-screen mode. See Kiosk requirements.
- Address construction — how the kiosk adds the scanned value to the OmniLab address. See Kiosk URLs.
- Keyboard — whether new participants fill in a form, and what keyboard the kiosk provides.
- Screen — resolution and orientation, so the experience layout can be checked on the real panel.
- Network — firewall rules and domain allowlisting for the venue.
- Session end — how the kiosk decides a visitor has walked away and returns to the welcome screen. See Inactivity management, and confirm your provider will build the message and countdown.
Leave the meeting with a written note of who confirmed what. That note is what you hold people to in stage 2.
Stage 2 — Test on the real device
Test on the kiosk itself, not on a laptop. Give your OmniLab contact remote access to a test unit if you can — it turns a week of screenshots into an afternoon.
- Run the full journey for every start route you plan to use.
- Test the acquisition form with the kiosk keyboard, including a long email address.
- Scan a barcode that should not work, and confirm the visitor sees a clear message rather than a dead screen.
- Confirm the kiosk returns to the welcome screen when a visitor abandons a session mid-experience, and that the Stay button puts them back where they were.
- Check layout and touch target sizes at the kiosk's real resolution.
- Time the experience from scan to reward, and check it against how long people will actually stand there.
- Pull the network cable and see what the visitor sees.
Record every issue with the stage it happened at and who owns the fix. Re-test the whole journey after fixes, not just the part that changed.
Stage 3 — Launch and run
Before you go live:
- Swap the test address for the live campaign address on every unit.
- Republish every campaign covered by the idle-detection script, so the script actually reaches the live experience.
- Confirm rewards and prize stock are configured and the campaign is published.
- Brief in-store staff on what the kiosk does, how to restart it, and how to hand over prizes.
While the campaign runs, route problems by type:
| What is happening | Who to contact first |
|---|---|
| The game or form misbehaves, or the experience will not load | OmniLab support |
| A reward is wrong, missing, or out of stock | Your marketing team, in OmniLab Studio |
| The screen is frozen, the scanner will not read, or the keyboard is broken | Your kiosk provider |
| The kiosk has no internet connection | Your kiosk provider, then venue IT |
| A visitor complains about a prize or an outcome | Your in-store staff |
After the campaign, pull the participation and reward reports from OmniLab Studio, and agree with your provider whether the units are decommissioned or reconfigured for the next campaign.