PIING
Reading Apps and platformsRetail ID for non-Shopify retailers
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
- What remains the same
- What is scoped
- The Retail ID workspace
- Data boundary
- Product boundaries
- Commercial model
- Next steps
Search or browse documentation
Apps and platforms 3 / 5
Retail ID for non-Shopify retailers
How Piing brings recognition, Wallet passes and visit events to non-Shopify and bespoke retail stacks.
Retail ID is the non-Shopify route for retailers that want the same recognition, Wallet and visit-event model without pretending every commerce stack is identical. The customer journey remains consistent, while identity resolution, loyalty values, CRM delivery and operational controls are scoped to the systems the retailer actually runs.
What remains the same
- Recognition. A kiosk, Piing reader or printed QR route creates a known store visit.
- Wallet. Apple and Google Wallet passes carry the merchant's brand, identity and configured live values.
- Visit events. Store, time, source and customer context flow into analytics and enabled destinations.
- Attribution. The implementation can relate visits to later orders and distinguish an attributed purchase from a visit with no purchase when the configured window closes.
- Staff context. The implementation can surface selected customer, loyalty and visit details for the store team.
Shopify POS is specific to the native Shopify product, so it is not presented as part of every Retail ID deployment.
What is scoped
Retail ID connects to the retailer's real stack rather than advertising a generic list of commerce adapters. The implementation scope covers:
- the commerce or customer system used to resolve identity;
- the loyalty platform used for points, tier, rewards or membership status;
- the CRM or messaging tools that receive visit and outcome events;
- wishlist or customer attributes used for staff context and Wallet messages;
- signed webhooks, API routes and the operational logs required to support them.
Klaviyo, Attentive, Ometria, HubSpot, LoyaltyLion, Rivo, Yotpo, Antavo, Swym and Wishlist King are the current named Piing integrations. A retailer using another commerce or enterprise system should treat that connection as a Retail ID scope, not as a self-serve connector claim.
The Retail ID workspace
The Retail ID workspace holds the retailer's brand settings, locations, kiosks, Wallet configuration, member context, integration routing and delivery status. The exact controls available depend on the contracted implementation, because the source systems and operating model differ by retailer.
Data boundary
The retailer's commerce or customer platform remains the primary record. Piing processes the identifiers, customer context and events needed for the configured workflows, stores the operational records needed to run and support the service, and sends selected outputs to the retailer's destinations. Payment card data and biometric recognition are outside the Piing model.
Product boundaries
Piing: Intelligence and Piing: Alerts are Shopify-only products. Intelligence writes to Shopify metafields, and Alerts renders inside a Shopify theme. A Retail ID project can scope equivalent outcomes for another platform, but those outcomes are not presented as the two Shopify apps.
Fuego can work alongside Piing as a mobile-commerce layer. It is not described as the loyalty engine.
Commercial model
Retail ID is scoped around store count, implementation work and the systems being connected. Subscription and payment arrangements are confirmed in the direct agreement. The pricing page shows the standard Piing per-store bands and makes clear where a Retail ID quote is required.
Next steps
Related guides
Was this guide helpful?
Next guide in Apps and platforms
Supported platforms and integrations
Where each Piing product runs, which integrations are current, and where Retail ID is required.
Still need a hand? Contact us