PIING
Reading Apps and platformsSupported platforms and integrations
Apps and platforms
- The Piing platform
- How Piing: Intelligence fits your stack
- Retail ID for non-Shopify retailers
- Supported platforms and integrations
- How Piing fits your stack
In this guide
- Product availability
- Commerce and staff workflows
- Loyalty
- CRM and messaging
- Wishlist and customer context
- Custom destinations
- Works alongside Piing
- Not advertised as live
- Next steps
Search or browse documentation
Apps and platforms 4 / 5
Supported platforms and integrations
Where each Piing product runs, which integrations are current, and where Retail ID is required.
This page separates three questions that are often confused: where the product runs, which systems are current named integrations, and which connections require Retail ID scope.
Product availability
Scroll across to compare the columns.
| Product | Where it runs | Primary output |
|---|
| Piing | Shopify app with Shopify POS extension | Known visits, Wallet passes, attribution and visit context |
| Retail ID | Non-Shopify and bespoke retail stacks | Scoped recognition, Wallet and event implementation |
| Piing: Intelligence | Shopify only | Selected customer metafields from configured analysis |
| Piing: Alerts | Shopify only | Theme-native notification feed and attribution |
Intelligence is Shopify-only because it reads Shopify data and writes Shopify metafields. Alerts is Shopify-only because it renders inside a Shopify theme.
Wallet pass updates and Wallet notifications belong to Piing. Alerts is the separate storefront feed; its optional browser-push capability is not an Apple or Google Wallet notification.
Commerce and staff workflows
- Shopify. The primary customer and order record for the native Piing product and Piing: Intelligence.
- Shopify POS. The native staff extension and one of Piing's four recognition routes.
- Retail ID. The route for another commerce platform or a bespoke customer system. The exact connection is scoped to the retailer rather than advertised as a universal self-serve adapter.
Loyalty
Piing can read points, tier and available rewards from the current named loyalty integrations, and can send a visit action where the connector supports it and the merchant enables it:
- LoyaltyLion
- Rivo
- Yotpo
- Antavo
Piing can also run without a loyalty vendor by using Shopify store credit, merchant-controlled segments, visit-based status or simple membership values on the pass.
CRM and messaging
Piing can send typed visit and outcome events to:
- Klaviyo
- Attentive
- Ometria
- HubSpot
The visit-with-purchase and visit-without-purchase outcomes are separate, allowing the receiving tool to use different journeys for buyers and visitors who did not convert.
Wishlist and customer context
- Swym Wishlist Plus
- Wishlist King
- supported Shopify customer metafields
Saved-item context can be used in the staff view, Wallet messages and conversion attribution where the merchant configures that workflow.
Custom destinations
Signed webhooks provide the general route for a warehouse, in-house service or another destination that can receive an HTTPS event. The event catalogue documents the available event types and their payloads.
Works alongside Piing
Fuego can work alongside Piing as a mobile-commerce layer. It is not a loyalty integration and should not be described as the source of points or tier unless the retailer has separately built that relationship.
Not advertised as live
A logo in an old concept, a future adapter in source code, or a connector that requires retailer-specific engineering is not listed as a current public integration. If a required platform is not named above, contact us and treat it as a webhook or Retail ID scoping question.
Next steps
Related guides
Was this guide helpful?
Next guide in Apps and platforms
How Piing fits your stack
Piing adds a known physical visit, a Wallet channel and measurable outcomes while commerce, loyalty and CRM keep their existing roles.
Still need a hand? Contact us