PIING
Piing · Integrations
Your stack.
With the visit in it.
Your customer record, loyalty programme and CRM already do important work. Piing brings them closer to the person standing in your store.
A recognised visit, connected to your existing tools
The visit joins the customer.
A known visit, whether or not an order follows.
- Total recorded visits
- 10
- Pass status
- Installed
- Available to
- Selected metafield workflows
Choose the fields and events you enable.
- Read
- Useful customer context.
- Record
- A recognised store visit.
- Connect
- Your configured next step.
A connection with a purpose
The tools stay familiar.
The experience gets richer.
Start with the customer and the moment you want to improve. Then connect the sources and destinations that make it possible.
01 · Shopify / Customer record
Shopify knows the order. Add the visit.
Record a recognised check-in alongside the customer’s orders. Selected visit fields can support segments, Shopify Flow and your connected tools.
02 · Your loyalty programme
The balance stays. The experience travels.
Bring connected points and tier into Wallet and the staff view. Your loyalty provider owns its balances and programme rules; supported visit rewards are enabled separately.
03 · CRM & messaging
Give the next message a real-world reason.
Send selected visit and outcome events to a supported CRM. Your flows decide who is eligible, when to follow up and what to say.
04 · The products they saved
Let the wishlist leave the website.
Bring supported saved products into the staff conversation. Enabled restock and price-drop triggers can also create a useful Wallet message.
Connections depend on provider access, customer matching and the fields your team enables. Swish / Wishlist King uses supported customer metafields; a direct API connection needs confirmation for your store.
Useful context, in.
A recognised visit, out.
Read what your team needs for the welcome. Send the check-in to the tools that handle the next step.
A visit can start your existing flow.
- Event
- Customer checked in
- Customer
- Sofia Smith
- Store
- Soho
Your CRM keeps the audience, consent, timing and sending rules. Enable purchase or no-purchase events separately.
Plan the connection
Start with the moment.
Then agree the data.
A useful brief names the customer action, the source of the data and the system that should respond.
Choose the experience.
A loyalty balance in Wallet, a saved item for the team or a visit event in your CRM. Give the connection one clear job.
Confirm the match.
Check customer identifiers, provider access and the fields available to the store. Agree which system owns each value.
Prove the whole journey.
Use a test membership to check the pass, record a visit and confirm the expected data reaches the configured destination.
Beyond Shopify · Retail ID
Your retail world
may look different.
Retail ID is the non-Shopify version of Piing, bringing recognition and Wallet membership to your existing retail stack. Centra and Salesforce CRM connections can read agreed customer data; other systems and event destinations are defined around your project.
Salesforce CRM means Sales & Service Cloud. Salesforce Commerce Cloud is not a ready-to-connect integration.
Before you start.
Do we need to replace our loyalty programme?
No. Your provider keeps ownership of points, tier and programme rules. Piing brings supported membership details into Wallet and the store visit. Visit rewards, where supported, are configured separately.
Does Piing bring everything in our CRM into the staff view?
No. CRM connections primarily receive the events and selected fields you configure. Inbound context comes from supported customer, loyalty, wishlist and Shopify metafield sources. The connection guide explains the direction and scope.
Can our developers connect another system?
Signed webhooks can deliver agreed events, and the Partner API can put Piing passes into your existing customer experience. We confirm identifiers, supported actions and the destination before implementation.