PIING
Why use a Piing Wallet pass rather than your loyalty vendor’s
Their pass updates at the till, then goes quiet. A Piing pass keeps the loyalty programme and shows up for the visit: your brand, a check-in and a reason to return.
In this article
Their pass goes quiet. The visit never happened.
A loyalty vendor’s Wallet pass knows the balance. It speaks when points change or someone checks out. Then it waits for the next purchase.
That is the problem. A customer can walk in, look at something they saved, and leave without buying. The vendor pass never records the visit, so the store misses the moment and the follow-up never starts. You still have a loyalty programme. You do not have a membership that works on the shop floor.
A Piing pass is built for that gap. Keep the vendor. Stop asking their pass to be your brand, your check-in and your message channel. Introducing Piing covers the wider visit. This one stays with the pass.
Their pass / A Piing pass
Same loyalty.
A pass that shows up.
The vendor keeps the points. The pass starts working between purchases.
Their pass
Quiet until the next sale
A Piing pass
Ready for the visit
Branding
Their passThe vendor’s template.
A Piing passYour logo, colours and artwork.
Notifications
Their passCheckout and points changes.
A Piing passCheck-in, milestones, wishlist and back in stock.
In-store check-in
Their passNo visit recorded.
A Piing passQR, Shopify POS or a Piing Tap Box.
Data out
Their passNo visit to send on.
A Piing passShopify metafields, Klaviyo and other CRMs.
Loyalty
Their passTheir pass is the programme.
A Piing passThe vendor stays the ledger. Piing connects.
Live messages cover a new pass, check-in, milestones, and a saved item seen in store, back in stock or on sale. Birthday, reward and tier-change messages are not live yet. Google Wallet check-in uses QR.
Keep their points. Carry your pass.
Piing joins the loyalty programme. It does not replace it. LoyaltyLion, Rivo, Yotpo and Antavo keep the points, the tier and the rules. Piing reads what the pass and the staff view need. Reading a balance does not change it. Awarding points for a visit is a separate switch, and it starts off.
Rivo makes the pattern obvious. Connect it, and live points and VIP tier appear on a pass Piing issues. Customers carry that pass. You do not also issue a Rivo one. If a qualifying check-in should earn, turn awarding on and Rivo’s rules decide the value. The Rivo integration covers the key, the read and the switch that stays off until you want it.
The other supported programmes work the same way: the vendor stays the ledger, Piing is the membership in their Wallet, and the visit is yours to record. The connection directory shows what each route reads, and what it sends back only after you enable it.
Put your brand in their Wallet.
The pass should look like the shop they already know. Piing issues and signs Apple Wallet and Google Wallet passes with its own credentials: your logo, your colours, your artwork. Need the passes under your own accounts? Bring them. Customers add the pass to the Wallet they already use. There is no Piing app to download.
Put real values on it. Connected points and tier, store credit, a name, visit counts. A simple membership does not need a made-up balance. Those values live in fields, so they refresh when the source changes, without new artwork. A points update can stay quiet, or it can carry a line when the moment deserves one.
Apple Wallet and Google Wallet are different layouts, so design both and check both. Passes are included in the Piing subscription, with no per-pass fee. See pricing, then design a pass customers will actually use.
Catch the visit, not only the sale.
Near the store is not in the store. Piing can offer a nearby Wallet suggestion for up to ten locations you choose. Apple and Google decide whether it appears. Piing does not follow a continuous location trail, and a lock-screen suggestion is not a recorded visit.
The visit starts at check-in. A Wallet QR at a kiosk, a till scanner or a printed sign. A staff scan in Shopify POS. A physical card on a Piing Tap Box or another supported reader. An iPhone tap needs Apple’s approval and a compatible reader. Google Wallet uses QR.
A supported NFC reader is one recognition route. Its top layer can be customised with your retailer logo. QR scanning can be the starting point.
Every accepted route writes the same visit: who came in, which store, when, and how. Staff open the context you have switched on. The loyalty programme still owns the balance. Start with QR. Add a Tap Box when the floor is ready for it. Compare the recognition routes, see the Tap Box, or rehearse them in a store-recognition pilot.
Message the visit. Send the record on.
A checkout ping is a thin reason to talk. Once the visit exists, message the moments Piing actually produces: a new pass, an accepted check-in, a visit milestone, and, with a supported wishlist, a saved item seen in store, back in stock or on sale. You write the line, switch the trigger on, and set the daily limit and the gap. Over the limit, the message is held, not saved for tomorrow. The pass can still update quietly in the background.
Birthday, reward unlocked and tier-change messages are in the list. They are not live yet.
Then let the visit travel. Piing writes last check-in and visit counts to Shopify customer metafields, ready for segments and Flow. The same event can go to Klaviyo, Attentive, Ometria or HubSpot, under the consent, suppression and frequency rules you already run there. That is a much wider audience than a single note tied to the till. Read Wallet push notifications for the moments, and the delivery controls for the limits.
See who came in. Then book the next step.
Piing’s reports show visits by store and by route, and the paid orders that follow inside the attribution window you set. A linked order means the purchase came after the visit. It is an association, not proof the visit created extra revenue. Read the analytics overview before a chart becomes a claim.
Piing: Intelligence does a different job. It turns Shopify order and product data into customer fields, checks confidence on anything inferred, and writes the fields you approve. Use them in segments, in Flow and, with both apps installed, in the staff view. It does not replace the visit report, and it does not need a pass. See how the analysis works.
Piing: Alerts is the storefront feed: audiences, frequency, and reporting for impressions, clicks and attributed orders. Its optional browser push is not a Wallet notification. Use the feed when the website is the right place. Use the pass when the membership is.
Book a demo to see a Piing pass on your programme, or see pricing if you already know the job. Piing is the recognition product. Introducing Piing sets the three apps side by side.