PIING
Reading In-store kioskCustomise the kiosk screens
In-store kiosk
- Set up an in-store tablet
- Pair a tablet
- Customise the kiosk screens
- Lock the tablet to the kiosk
- Kiosk troubleshooting
In this guide
- Screen 1: pre-tap welcome
- Screen 2: recognised member
- Use a Piing-issued pass
- Screen 3: membership benefits
- Reader taps in the same store
- Design guidance
- Next steps
Search or browse documentation
In-store kiosk 3 / 5
Customise the kiosk screens
Shape the pre-tap, recognised-member and join-benefits states, including live programme values and the reader-to-screen bridge.
Piing has three kiosk states. The settings apply across the shop's kiosk experience, while each paired tablet keeps its own store assignment.
Screen 1: pre-tap welcome
This is the live attract state before anyone is recognised. Configure:
- headline and subtitle, with
{brand} for the current brand name;
- join prompt and supporting line beside the join QR;
- camera status and error copy;
- whether a secondary phone check-in QR is shown while the camera works;
- brand logo, background and accent colour.
The secondary phone check-in QR is off by default because the main instruction is to present the Wallet pass to the tablet camera. If camera access is denied or unavailable, Piing can show the phone route as a fallback. For a permanent printed route, use Scan-in points instead.
The idle state can also surface a short set of membership benefits. Use the strongest two or three, not a long terms list.
Screen 2: recognised member
Configure the greeting with {firstName} and {tier}, then choose which live values are useful at arm's length:
- tier;
- points balance;
- rewards and rewards-ready count;
- wishlist tile;
- an optional
+N points flourish.
The points flourish is display copy. Piing only changes a loyalty balance when the supported provider is connected, reward relay is enabled and the visit trigger has a configured value.
The kiosk uses available cached pass values and supported loyalty data. If a source cannot return a value, the screen should remain clean rather than presenting invented figures.
Use a Piing-issued pass
Ask customers to present the QR on their Piing Wallet pass. Loyalty providers such as Rivo supply connected points and tier data; Piing issues the pass used for this workflow.
Screen 3: membership benefits
When a new customer scans the join QR with their phone, the tablet changes to the benefits state while the phone continues to the merchant's sign-up route.
Configure:
- benefits heading and subtitle;
- concise benefit lines;
- optional tier names and perks;
- the merchant sign-up URL;
- the attribution parameter and value appended when it is not already present.
The default fallback is the Shopify account registration route. A custom URL must be a valid web address. Scanning this code proves intent to join, not completed registration, pass installation or a first check-in.
Reader taps in the same store
The NFC readers in this store control decides whether a recognised reader tap changes the kiosk to Screen 2. It is on by default.
Turn it off for a standalone reader that should record the visit and give its own feedback while the kiosk stays on the attract loop. The setting affects the screen bridge only; it does not disable the reader.
Design guidance
- Start from the real brand logo and one restrained accent.
- Design for a mounted landscape or portrait tablet at retail distance.
- Keep the pre-tap instruction singular and obvious.
- Use real programme values and realistic number lengths in testing.
- Preview the long customer name, long tier and zero-value states.
- Do not show every available field simply because it exists.
Save, reload a paired kiosk and test all three states before rollout.
Next steps
Related guides
Was this guide helpful?
Next guide in In-store kiosk
Lock the tablet to the kiosk
Combine Piing's in-page protection with an operating-system or managed single-app mode before the tablet reaches the retail floor.
Still need a hand? Contact us