PIING
Reading In-store kioskKiosk troubleshooting
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
- The kiosk will not open
- Pairing does not complete
- The camera will not start
- A pass will not scan
- The member is recognised but the store is wrong
- The greeting is missing a value
- A reader tap does not change the kiosk
- The tablet leaves the kiosk or sleeps
- What to send support
Search or browse documentation
In-store kiosk 5 / 5
Kiosk troubleshooting
Diagnose camera recognition, pairing, store assignment, reader bridging, private launch links and device lockdown in the right order.
Start with the issue you can see below. After making a change, test a Piing pass and check that the visit appears against the right customer and store.
The kiosk will not open
- Confirm the tablet uses the current private launch link for that kiosk record.
- If the kiosk was re-paired in admin, unpaired or removed, the old link no longer works. Reconnecting from POS keeps the existing link active.
- Check whether the merchant has switched the kiosk off. A valid link then shows the friendly not-available state.
- If the link may have been exposed, re-pair or unpair it rather than sharing it again.
Pairing does not complete
- Generate a fresh pairing challenge. It expires after 15 minutes.
- Enter the current 4-digit PIN exactly as shown.
- After repeated wrong PINs, start again with a new challenge.
- If the tablet cannot scan the pairing QR, open the public pairing address shown beneath it or use the private launch-link option.
- Make sure the tablet has a store assigned on the Kiosks page before generating its code. An unassigned tablet cannot be paired.
The camera will not start
- Grant camera permission for the Piing kiosk site, then reload.
- Check browser and operating-system privacy controls, including restrictions imposed by device management.
- Make sure another app is not holding the camera.
- Clean and uncover the front camera.
When the camera is denied or unavailable, Piing can show the phone check-in QR fallback. That is different from the separate join QR.
A pass will not scan
- Open the Wallet pass barcode and increase the phone brightness.
- Hold the whole QR inside the camera frame rather than touching the phone to the tablet.
- Test at the final mounting angle and shop-floor lighting.
- Confirm the pass belongs to the same merchant and is linked to a customer.
- Use a Piing-issued Wallet pass. The connected loyalty provider supplies the programme values, not the customer-facing scan credential.
Google Wallet is QR in Piing. Do not troubleshoot it as an NFC phone tap.
The member is recognised but the store is wrong
Open Kiosks and check the tablet's assigned store. To move it, select Unpair, choose the new store, select Save store, then generate a fresh pairing code. The tablet cannot choose another store after scanning. If visits should appear in a Shopify POS feed, also check the POS-location mapping for that store.
The corrected assignment applies to future visits; it does not rewrite historical records.
The greeting is missing a value
- Confirm the field is enabled in kiosk settings.
- Check that the customer's source actually has a current value.
- For points, tier or rewards, inspect the supported loyalty connection and its read status.
- For wishlist context, confirm the configured wishlist route has data for that customer.
- Reload the kiosk after saving settings.
Piing should omit an unavailable value rather than fabricate a zero.
A reader tap does not change the kiosk
The reader and kiosk must share a store assignment, a live kiosk session must be on screen and A reader tap also flips the kiosk screen to the customer must be on.
First check whether the visit itself was recorded. If it was, the reader is working and only the screen bridge needs attention. The bridge supports a resolved physical card or approved Apple Wallet VAS tap; Google Wallet uses the kiosk camera.
The tablet leaves the kiosk or sleeps
Piing's page protection is not an operating-system lock. Apply Guided Access, Android app pinning, mobile-device management or a dedicated kiosk browser, and set an appropriate power policy. See Lock the tablet to the kiosk.
What to send support
If the problem remains, contact us with the kiosk name and device code, assigned store, tablet model and operating system, time of the test, pass platform and whether a check-in row was created. Do not send the private launch link in an open support channel.
Related guides
Was this guide helpful?
You’ve reached the end of In-store kiosk.
Still need a hand? Contact us