PIING
Integrations
The tools you trust.
Now part of the visit.
Your loyalty programme keeps the points. Your CRM sends the message. Piing connects them to the customer who just checked in at your store.
One customer, online and in store.
Read customer and order details. Write selected visit fields to Shopify customer metafields for POS, segments and Flow.
What changes after a check-in
The visit becomes
something you can use.
The customer, store and time stay together, even if no order follows.
The integration directory
Find the right connection.
17 connections
Commerce For Shopify
Read customer and order details. Write selected visit fields to Shopify customer metafields for POS, segments and Flow.
Loyalty For Shopify
Bring connected points, tier and available rewards into the membership experience. Enable supported visit rewards separately.
Marketing For Shopify
Send check-in and purchase-outcome events. Your Klaviyo flows decide the audience, timing and follow-up.
Wishlists For Shopify
Read saved products for the staff conversation. Enabled stock and price-change triggers can create a relevant Wallet message.
Loyalty For Shopify
Show connected points and tier on a Piing pass and in store. Rivo keeps the balance; optional visit rewards are enabled separately.
Marketing For Shopify
Send selected visit events to Attentive. Your journeys retain control of audience eligibility, consent and sending.
Loyalty For Shopify
Read connected points and VIP tier for the pass and staff view. Optional Piing point awards need their own configuration.
Loyalty For Shopify
Read connected points and tier. When you enable loyalty events, your Antavo rules decide what each visit earns.
Marketing For Shopify
Send supported visit events to Ometria. Keep segmentation, consent and sending rules in the CRM you already use.
Marketing For Shopify
Send selected Piing events as HubSpot custom behavioural events, using the event definitions you configure.
Wishlists Via customer metafields
Read saved products from supported Shopify customer metafields. A direct Swish API connection needs confirmation for your store.
Wishlists Via customer metafields
Map the wishlist Wysh stores on your Shopify customer into Piing customer context and enabled wishlist-led Wallet messages.
Mobile apps Through the Partner API
Offer a customer’s Piing Wallet pass inside your Fuego app through a scoped Partner API implementation.
Commerce Through Retail ID
Read customer identity and recent orders through Retail ID. This connection does not write check-ins back into Centra.
Commerce Through Retail ID
Read agreed Sales or Service Cloud Contact fields through Retail ID. Salesforce Commerce Cloud is a separate, unavailable connection.
Loyalty Through Retail ID
Read supported member details and tier through Retail ID. Record visits using the interaction schema configured in Voyado Engage.
Loyalty Through Retail ID
Read profile and loyalty context through Retail ID, and write agreed visit properties to mapped Talon.One customer attributes.
Provider plans and API access can affect availability. Reading a loyalty balance does not automatically enable earning or redemption. Your CRM keeps its own consent and sending rules.
Beyond Shopify · Retail ID
Keep your platform.
Add recognition.
Retail ID is the non-Shopify version of Piing. Bring membership and store check-in to the customer system you already use.
A connection shaped around your store.
Agree the customer identifier, fields and event destinations before implementation. Each connection in the directory is labelled with the route it supports.
Customer lookup and event delivery are separate capabilities. An identity connection does not automatically write visits back into your commerce platform.
Salesforce CRM means Sales & Service Cloud. Salesforce Commerce Cloud is not currently available as a ready-to-connect integration.
For your development team
Your endpoint.
The same visit.
Use signed webhooks for agreed event delivery, or the Partner API to put Piing passes inside your own experience.
Need to connect another system? Talk through your stack
- Customer
- Member 02480
- Store
- Soho
- Time
- 12:04
Agree identifiers, subscribed events and permitted writes. Keep credentials on the server.