.public-content{max-width:860px;margin:48px auto;padding:0 24px 64px;color:#242424;font:16px/1.65 Geist,Arial,sans-serif}.public-content h1,.public-content h2{font-family:"Instrument Serif",Georgia,serif;font-weight:400;line-height:1.15}.public-content h1{font-size:42px}.public-content h2{font-size:32px;margin-top:48px}.public-content h3{font-size:20px;margin-top:32px}.public-content a{color:inherit;text-underline-offset:4px}.public-content table{border-collapse:collapse;display:block;overflow-x:auto}.public-content td,.public-content th{padding:12px;border:1px solid #ddd}.public-content dt{font-weight:600}.public-content dd{margin:0 0 16px}.public-content nav{margin-top:48px;border-top:1px solid #ddd;padding-top:24px}.public-content-brand{font-weight:600;text-decoration:none}.public-content ul{padding-left:24px}@media(max-width:600px){.public-content{margin:24px auto;font-size:15px}.public-content h1{font-size:34px}.public-content h2{font-size:28px}}PIING

Reading IntegrationsWhat Piing reads back from your stack

Integrations

In this guide

What Piing can read
Where it appears
When values refresh
What goes the other way
Retail ID

Search or browse documentation

Integrations 3 / 12

What Piing reads back from your stack

Which customer, loyalty, order, wishlist and Intelligence values Piing can use for Wallet passes and in-store staff, and which systems stay the source of truth.

Piing does not copy every connected system into a second customer database. It resolves the customer in front of the store team, reads the context needed for the experience you have configured and leaves each source system in charge of its own data.

For Shopify merchants, Shopify remains the primary customer and order record. Loyalty platforms keep owning points, tiers and rewards. CRM and messaging tools mainly receive the Piing events you choose to send them.

What Piing can read

Loyalty context. A connected LoyaltyLion, Rivo, Yotpo or Antavo programme can supply the current points balance and tier used by the recognition screen and Wallet pass. The exact values available depend on the provider and merchant configuration.
Shopify customer fields. Merchant-selected customer metafields can appear in the Shopify POS or browser staff experience. This is useful for fields such as size, preferred category, birthday or another value the store already maintains.
Piing: Intelligence fields. Intelligence writes selected attributes to app-owned Shopify customer metafields. Piing's staff experience can read those fields back without creating a separate profile store.
Wishlist context. Supported Swym, Wishlist King or configured Shopify customer fields can provide saved-item context for staff, conversion attribution and Wallet messages.
Recent Shopify orders. Where the app has the required Shopify permission, the POS customer panel can show recent orders, value, item count, fulfilment state and line items. Shopify's standard read_orders permission covers the most recent 60 days; older history requires Shopify's separate approval.
Piing visit context. Piing's own check-in fields, such as last check-in, total visits, recent visits and store, can be written to Shopify and shown to staff when enabled.

Where it appears

The merchant chooses the fields and their order under Hardware & check-ins, then POS, in What staff see at POS. The same configured context can power the browser-based staff view.

Fields are read for the customer being recognised. Anything not enabled for the staff experience is not shown on the tile. See What staff see at POS for the exact controls.

When values refresh

At recognition. Piing resolves the customer and retrieves the context needed for that check-in and staff view.
When the source changes. Wallet values can refresh after events such as a purchase, check-in or loyalty update, according to the connected provider and Wallet configuration.
After an Intelligence run. Selected Intelligence outputs are written to Shopify customer metafields and become available to metafield-aware tools and the Piing staff experience.

Do not assume every integration supports a general scheduled profile pull. Piing does not currently claim to import arbitrary Klaviyo, Attentive, Ometria or HubSpot profiles and order histories into its own member record.

What goes the other way

Piing can send configured check-in, Wallet, loyalty and attribution events to CRM, messaging and webhook destinations. This outbound event routing is separate from the inbound values above. For example, a check-in can enter Klaviyo as an event without Piing importing the customer's Klaviyo profile back into Shopify POS.

See Integrations overview for the supported destinations, or Webhooks and custom integrations for a bespoke route.

Retail ID

For a non-Shopify retailer, the identity source, fields, order route and write-back behaviour are agreed as part of the Retail ID implementation. The Shopify-specific permissions and metafield behaviour on this page should not be assumed to apply unchanged to another commerce platform.

Related guides

Was this guide helpful?

Next guide in Integrations

Connect Klaviyo

Send in-store tap events to Klaviyo so flows and segments react to real shop-floor behaviour, with separate signals for browsers and buyers.

Still need a hand? Contact us