PIING
Reading Getting startedSet up Retail ID
Getting started
- What is Piing?
- Install the Shopify app
- Choose your setup
- Set up Retail ID
- Your first check-in
- Key terms glossary
In this guide
- Before you start
- 1. Confirm the customer record
- 2. Connect the working stack
- 3. Configure locations and recognition
- 4. Build the Wallet pass
- 5. Validate the staff and customer experience
- 6. Launch and monitor
- Product boundaries
- Next steps
Search or browse documentation
Getting started 4 / 6
Set up Retail ID
Scope and configure Piing recognition, Wallet passes, locations and event routes for a non-Shopify or bespoke retail stack.
Retail ID is the route for retailers that are not using the native Shopify product. The recognition and Wallet journey remains familiar, while the connection to commerce, customer, loyalty and messaging systems is scoped to the retailer's real stack.
Before you start
Bring the following to the scoping conversation:
- the commerce or customer platform that owns the customer record;
- the loyalty platform, if points, tier or rewards should appear on the pass;
- the CRM and messaging tools that should receive visit events;
- the number of stores and the locations planned for the first rollout;
- the recognition routes needed at each store, such as kiosk, reader or printed sign;
- the Wallet values, membership model and customer messages the pass should carry;
- brand assets and the people responsible for security and data review.
Contact us to open the implementation scope and Retail ID workspace.
Confirm the customer record
Agree which system is the primary customer record and which identifier each recognition route will resolve. Document what Piing needs to read, what it stores operationally, and what should be written back.
This step also defines the purchase-attribution route: where orders arrive from, which store and customer references are available, and how long the merchant wants the attribution window to remain open.
Connect the working stack
Configure the systems included in the scope:
- CRM and messaging: Klaviyo, Attentive, Ometria, HubSpot or a signed webhook route.
- Loyalty: LoyaltyLion, Rivo, Yotpo or Antavo where the implementation uses those providers.
- Wishlist and customer context: Swym, Wishlist King, supported customer fields or a scoped source.
- Commerce and identity: the retailer's system of record, connected through the agreed Retail ID implementation.
Each destination should be tested with a known customer, a completed check-in, a purchase outcome and a no-purchase outcome before rollout.
Configure locations and recognition
Create the store locations and choose the right recognition route for each one:
- a pre-check-in kiosk on a tablet;
- a Piing reader at the entrance or beside the kiosk;
- printed QR signage;
- another Retail ID route agreed for that retailer.
Pair kiosks and readers to the correct location. Validate that each source records the store, time and route consistently.
Build the Wallet pass
Set the pass colours, logo and membership model. Decide which live values should appear, such as points, tier, Shopify-equivalent credit, merchant segments, visit milestones or simple membership status. Confirm the QR route and the messages that should follow installation, check-in, milestones, rewards or saved-item events.
Validate the staff and customer experience
Run a controlled end-to-end test:
- Issue a test pass to a known customer.
- Check in through every route planned for the pilot store.
- Confirm the staff view shows only the agreed customer context.
- Confirm each enabled destination receives the correct event.
- Place an attributed test order and verify the purchase outcome.
- Run a no-purchase test through the full configured window.
- Check that the Wallet pass and messages update as expected.
Launch and monitor
Roll out to the pilot locations first. Monitor check-ins by day, location and route, delivery logs, attributed orders and no-purchase visits. Resolve any identity or delivery exceptions before expanding to the remaining stores.
Product boundaries
Piing: Intelligence and Piing: Alerts are Shopify-only. Equivalent profiling or storefront outcomes on another platform are a separate Retail ID scope, not the two Shopify apps.
Next steps
Related guides
Was this guide helpful?
Next guide in Getting started
Your first check-in
Understand the four recognition routes and validate a known visit, its downstream event and its attributed outcome.
Still need a hand? Contact us