Integrations & data.

Retrics installs from the Shopify App Store as a standard app. When you approve the install, Shopify issues an access token scoped to your store — you never paste API keys or hand us a password, and you can revoke the token from your Shopify admin at any time.

The base analytics connection requests read_customers, read_orders, and read_products. Approved stores may separately grant read_all_ordersfor history outside Shopify's standard window. These scopes cannot place, edit, or refund an order.

Only if you explicitly enable Shopify loyalty reward issuance does a separate OAuth step add write_discounts, used solely to create the requested discount codes. Retrics does not request order-write, theme-write, checkout, payment, or fulfillment scopes.

Because Retrics reads customer records, the connection operates under Shopify's protected customer data requirements. We access only the fields the analytics need, apply data-minimization and retention limits, and honor Shopify's mandatory customer-redaction and shop-redaction webhooks.

• Orders — order and line-item history, timestamps, totals, discounts, and fulfillment status. The backbone of cohort, repeat-rate, and lifetime-value math.
• Customers — the customer record tied to each order, so Retrics can build a per-customer purchase timeline and score lapse probability. Email, name, phone, and coarse location may be stored for profiles and search, approved sends, and exports. An irreversible email hash supports suppression, audience, and cross-channel matching.
• Products — product and variant records, used to compute cross-sell and reorder signals and to name real products on profiles, audiences, and exports.

Retrics does not read your theme, other apps' settings, your staff accounts, or anything outside the scopes listed above.

On connect, Retrics imports the history Shopify grants. With approved read_all_orders, that can include older orders; without it, Shopify limits the initial order window and Retrics labels history coverage instead of claiming a complete lifetime.

After that, new and changed orders and customers flow in continuously through Shopify webhooks, so the dashboard reflects your store in near-real-time. A scheduled reconciliation sweep runs regularly to catch anything a webhook may have missed and to keep the two systems in agreement.

Model scores — drift detection and lapse probability — recompute on a rolling schedule against your store's own history, so risk flags stay current as behavior shifts.

Your data is portable. From the screen you are looking at, you can export the customer list with its retention scores, the win-back, reorder, VIP and second-order lists, the revenue scorecard, any frozen audience, and a Klaviyo-shaped list ready to import — so the numbers can live in your own spreadsheets, BI tool, or warehouse. Care lists export with the Concierge tier that includes them.

The cohort grid and the recovered-revenue ledger have no export yet; those numbers stay on their screens for now. Where a customer has too little history for a prediction, the file leaves the cell blank rather than printing a score the screen would have withheld — a number in a file outlives the caveat that came with it.

The lists built for outreach — win-back, reorder, VIP, second-order, Care, and the Klaviyo-shaped file — drop your global control before the file is written. A download is contact, so those customers stay out of it; that is what keeps a CSV you mail from contaminating the measurement of a later campaign.

Exports reflect what Retrics computed from your store. They are yours to keep and use, and they persist even if you later disconnect.

Retrics flags win-backs, reorder nudges, and cross-sells, freezes the audience behind each one, excludes the global control it never messages, and holds the whole thing for your approval. It never sends on its own.

Sending from Retrics is unavailable in this release. All four routes below are built into the product and switched off — there is no plan, setting, account connection or onboarding step that turns them on. What is available is the campaign-safe CSV export, on every audience and every plan.

Export the campaign-safe CSV and send it from your existing platform. The frozen audience with your global control already dropped, in a Klaviyo-shaped file any platform can import.

• Email from Retrics — unavailable in this release. When it is not, it needs Scale and above plus a sending domain you have verified in Settings → Sending; Retrics gives you the DNS records and re-checks them. A verified domain opens email, and only email — SMS and WhatsApp do not ride it. Mail would leave on your domain, with a one-click unsubscribe on every message.
• SMS from Retrics — unavailable in this release. It rides a carrier connection Retrics runs, so there is nothing for you to connect. Only customers with a phone number and a subscribed SMS marketing consent in Shopify would be texted; the rest of the audience is logged as skipped.
• WhatsApp from Retrics — unavailable in this release. It would run on your own WhatsApp Business account: your number, your approved message template. Same phone-and-consent floor as SMS.
• Klaviyo handoff — unavailable in this release. Klaviyo is the one email platform Retrics connects to directly, creating a named list and importing the approved audience into it for you to send from there. Because Retrics would get no confirmation that you did, such an action is recorded as exported rather than sent, and it can never produce a causal result. Every other email platform is served by the campaign-safe CSV above — and while sending is unavailable, so is Klaviyo.
• Scheduled delivery — unavailable in this release. A campaign cannot be scheduled, because nothing would fire it.

Each channel carries its status on the pricing page. Nothing on this list is priced separately from the tier it sits in, and no tier price changes when a channel becomes available.

AI drafting is off today: Retrics won’t send model-written copy until it can mechanically prove a draft carries no discount, deadline or offer you never authorised. You write the message — the audience, the holdout and the campaign-safe export are unchanged.

Retrics already consumes Shopify's inbound webhooks to stay in sync and to honor mandatory data-redaction events.

Outbound webhooks and a read-only REST API — to pipe retention scores, risk flags, and ledger entries into your own systems — are entitled on the Scale tier. Authentication, endpoints, payload shapes, and signature verification are documented, and support will send you the current reference. The Concierge tier adds custom integrations built for your specific stack.

CSV export remains the supported path for anything the API does not cover.

Disconnecting the store inside Retrics stops future syncs but retains the imported history, so reconnecting does not start from an empty workspace. It is not a deletion request.

Uninstalling the app in Shopify immediately revokes our access, atomically disconnects that installation from active entitlements, and leads to Shopify's later shop/redact request. That request purges the exact disconnected installation. Deleting the entire Retrics workspace is a separate verified manual request with an operational target of completion within 30 days. Anything you exported beforehand remains yours.

Anything about scopes, sync, or exports: support@retrics.ai. Billing lives in Billing & plans.