FloGPT for Shopify — Integration Guide

FloGPT is distributed as an embedded Shopify app. Open the FloGPT listing on the Shopify App Store, click Add app, and approve the requested OAuth scopes. Shopify redirects you straight into the embedded FloGPT admin.

1. Open the Shopify App Store and search for FloGPT.
2. Click Add app. Shopify prompts you for the OAuth scope grant.
3. On first install, FloGPT auto-creates a Shopify-scoped account for your store using <shop>@shopify-merchant.flogpt.com. You don't need to register separately.
4. The app provisions a unique widget ID and registers webhooks declaratively from shopify.app.toml.

FloGPT requests read-only scopes for the data the AI agent needs to answer support questions and recommend products. Refund and cancel actions never happen silently — they route to a human ticket with the call or chat transcript attached.

The chat widget installs as a theme app embed. No theme code changes are required and you can toggle the widget on or off without touching Liquid.

1. From the embedded FloGPT admin, click Open theme editor. The link deep-links straight to your live theme's App embeds drawer with the FloGPT embed pre-selected.
2. Toggle FloGPT Chat Widget to on.
3. Click Save. Visit your storefront — the chat bubble should appear in the configured corner within seconds.

The embed automatically detects your shop domain and the widget loads its configuration from FloGPT — no widget ID needs to be hardcoded into the theme.

The embedded admin covers widget toggles and customization. For everything else — knowledge base, voice agents, call pipelines, workflows, analytics — click Open Dashboard.

• The button mints a fresh single-use SSO code on every page load with a 60-second TTL.
• It redirects to /auth/shopify-sso?code=… on the FloGPT frontend, which exchanges the code for a session.
• If the SSO code can't be minted, the button is replaced with a clear diagnostic banner — you'll never end up on a generic login screen.

During a call or chat, the FloGPT agent reaches Shopify through a single shopify tool whose action list is narrowed to the scopes you've granted — the LLM is never shown an action it has no permission to run.

Outbound calls fire from Shopify webhooks and time-relative cadences. Each trigger ships with a Shopify webhook subscription, a dedupe key, a phone resolver and a default call script — drop it into a pipeline and the agent starts dialing.

Webhook subscriptions are declared in shopify.app.toml (the App Store source of truth) and reconciled on every page load of the embedded admin. The API version is pinned to 2026-01.

Shopify permits access to protected customer data only where it delivers app functionality. Every field FloGPT reads is listed below against the feature that consumes it. Access is read-only throughout.

Minimization is enforced in product, not policy

• Per-field opt-in. You choose, per action, which fields the AI is allowed to receive. Unselected fields are stripped before the response reaches the model — not hidden in the UI afterwards.
• Self-service only. Switch on Require authenticated user email for order listing and Restrict to authenticated user for customer lookup, and the agent can only ever retrieve the signed-in shopper's own records — arbitrary lookups become impossible.
• Ownership check before disclosure. Order tracking matches the caller's phone against the phone on the order and refuses the lookup on a mismatch. Order-name matching is exact, so #100 cannot surface #1001.
• Capped result sets. At most 10 orders or 5 customer records per lookup, so no path enumerates your customer list.
• Transcript redaction. Opt-in masking removes email, phone, card number, SSN, IP and street address from chat and call transcripts before they are stored.

Deletion behaviour

On customers/redact, every materialized PII field on the customer and order mirrors is nulled and the raw Shopify payload is removed outright. Non-PII accounting fields (totals, currency, financial status) are kept so your bookkeeping survives the deletion. On shop/redact all orders, customers, the merchant record and the OAuth session are deleted, and stored webhook payloads for the shop are scrubbed — only non-PII audit metadata proving the request was honoured remains.

Scopes FloGPT does not request

None of the scopes below are in the OAuth grant, and none are requested through the Partner Dashboard. They are listed only so this page can be diffed against the manifest without the gaps reading as undisclosed access.

How merchants pay for FloGPT

FloGPT bills through Shopify App Pricing, with plans defined in the Partner Dashboard. App Pricing apps are refused the Billing API outright, so the app never calls appSubscriptionCreate, appUsageRecordCreate, appSubscriptionLineItemUpdate or appSubscriptionCancel. Merchants subscribe on Shopify's hosted plan page and the app observes the result: the only billing read is currentAppInstallation.activeSubscriptions, which is the app's own installation data and needs no access scope. Metered usage is reported through the App Events API and priced by Shopify from the dashboard meters.

The app_subscriptions/update webhook subscription is retained solely for merchants whose app plan predates the move to App Pricing — those continue to bill through the Billing API and continue to emit it. It carries no shopper data and is unrelated to subscription contracts.

FloGPT implements Shopify's mandatory compliance webhooks plus additional opt-in privacy controls for chat and call transcripts.

The embedded admin runs four health probes on every load — backend sync, SSO code minting, public widget lookup, and widget asset CDN — and surfaces a diagnostic banner the moment one of them fails. The most common issues and their fixes: