PIING
Your first store-recognition pilot: what to test
A practical rehearsal for the pass, the staff view and the visit record. Start small, test the awkward cases and decide what success means before rollout.
In this article
Choose one store and one useful outcome.
Before choosing hardware, agree what should become easier. Perhaps staff need to recognise members before checkout. Perhaps the team wants to record visits that do not end in a sale. Pick a clear starting point and an owner who can watch the pilot on the shop floor.
Start with a small test group and a supported QR route. The purpose is to learn how the customer, staff member and record connect, not to launch every possible integration on the first day.
Sofia Smith
- Store
- Soho
- Last visit
- Today, 12:04
Two possible outcomes.
Each can start a different flow.
A purchase follows.
A qualifying order within your attribution window.
- Event
- Purchase event
- Your flow
- Post-purchase care
No purchase follows.
No qualifying order after your chosen no-purchase window.
- Event
- No-purchase event
- Your flow
- A helpful follow-up
Your reward rules apply. Klaviyo controls who receives a message and when.
Rehearse the customer match.
Install passes for test members on iPhone and Android. Scan them at the intended check-in point and confirm the correct customer, location and time are recorded. Rehearse a returning member, an unknown code and a customer who cannot find their pass.
For staff-led recognition, check the fallback search and make sure the team knows how to distinguish similar names. Opening a customer profile is not the same action as recording a Counter check-in. Test that distinction before asking staff to rely on the visit count.
Point the camera at the customer’s pass.
Open Scan in the Piing POS tile. Use the device camera or a connected scanner to read the customer’s pass.
Show only the context staff will use.
Confirm where the points, tier or store credit comes from and whether the staff role can see it. Check a member with a balance and one without. If the connected source is unavailable, the team needs to understand the missing value rather than assume it is zero.
Keep the existing loyalty programme in charge of its balance and rules. Reading points for a pass is different from awarding points for a visit. If the pilot includes visit rewards, agree limits and test repeat check-ins with approved test accounts.
Follow a visit through the systems.
Inspect the visit record before testing a follow-up. If a CRM connection is in scope, confirm a sample event reaches the intended test customer and that consent, suppression and frequency rules still apply. A successful connection screen is not evidence that the entire journey works.
For reporting, test the configured attribution window with approved test data. Check both a qualifying later order and an order that should not match. Visit-linked revenue describes an association; it does not establish that a message or visit created extra revenue.
Make the rollout decision explicit.
Keep a short record of what was tested, the devices used, the expected result and what happened. Review customer matching, scan reliability, staff usability and missing-data behaviour separately. Fix the confusing cases before adding more locations.
A useful pilot ends with a decision: roll out the tested workflow, refine it, or change the approach. See recognition methods, supported connections and talk through a Piing pilot.