Shopify Inbox handover
shopify_inbox_handover_v1 can offer a support handover when
the visitor needs returns, refunds, subscriptions, invoices, or a direct
store conversation.
Coming soon
Shopify Skills are still in private-pilot validation.
Shopify skills for HEAs
This page is kept for direct context, but it is hidden from public navigation and search until the Shopify connector, protected-customer-data gates, and merchant evidence are ready. Today, Shopify Inbox handover remains the public live behavior.
HEA-World for Shopify stores
Build toward a Shopify-ready Human-Enhanced Agent that answers from your knowledge, hands visitors to Shopify Inbox when support should take over, and can run secure read-only order lookup after the store connection and rollout gates are approved.
Live now
Shopify Inbox handover can open the store support chat for Shopify HEAs.
Connected setup
Connect Shopify in the HEA Editor so one HEA is bound to one authorized shop.
Pilot skill
Read-only order lookup requires
order_ref + email and explicit visitor confirmation.
App split
The dev app stays on test stores; the production app is reserved for real merchants.
Store support should feel native to the merchant, not bolted on.
The goal is not to make every Shopify visitor paste private keys into a chat. A creator logs into HEA, opens the HEA Editor, clicks Connect Shopify, authorizes the HEA Shopify app, and HEA stores the shop-specific connection behind the scenes.
What the first Shopify skills cover
We separate public support handover from private store access. That keeps the product believable and keeps customer data behind explicit merchant authorization.
Track order
shopify_order_status_read_v1 is available for connected
Shopify HEAs with read_orders. It collects
order_ref + email, asks before checking, then returns a
narrow read-only status summary.
Connect Shopify
The right setup surface is the HEA Editor's Shopify skills area: visible only for Shopify-ready HEAs, with connection health, scopes, and reconnect controls shown beside the skills that depend on them.
The secure connection path
HEA should know which HEA profile is connected to which Shopify shop because the creator intentionally started that flow from a logged-in HEA session. The Shopify app is the same public app for all merchants; the access token and connection record are shop-specific.
1. Creator starts
User logged into HEA clicks Connect Shopify on a specific HEA profile.
2. HEA signs state
HEA creates a signed nonce for
creator_id, hea_id, redirect target, and expiry.
3. Shopify authorizes
The merchant installs or authorizes the HEA Shopify app for that shop.
4. Callback verifies
HEA verifies Shopify HMAC plus signed state, then exchanges the code for a shop token.
5. Connection records
HEA writes the binding:
HEA X to shop.myshopify.com, token reference, scopes, and status.
Read-only order lookup, staged carefully
The order skill should behave like a normal support conversation first: answer what it can from public policy, ask only for the minimal verification fields, then call Shopify only when the HEA has an authorized store connection.
Collect the right proof
Ask for order reference and the email used on the order, not Shopify API keys.
Read only
Use narrow Shopify scopes for order status and fulfillment context. No writes in v1.
Escalate clearly
If no match, partial data, or permission failure appears, offer Shopify Inbox handover.
What a Shopify store can expect
Start with useful support handover, then add merchant-approved store access for a small private pilot. The goal is practical customer help without asking your team to share Shopify credentials.
Support handover
HEA can guide visitors and open Shopify Inbox when a human support path is the best next step.
Secure store connection
The merchant authorizes HEA through Shopify. No API keys are pasted into skills or resources.
Read-only order help
For private pilots, HEA looks up order status only after the visitor provides the right proof and confirms the check.
Least-privilege access
The first connected skill uses narrow read-only scopes and never changes products, orders, or settings.
Clear fallbacks
If the store is not connected or the lookup is unsafe, HEA falls back to support handover.
Pilot first
We validate the experience with selected merchants before scaling it into a broader Shopify rollout.
Start with the HEA, then connect the shop.
The minimum setup for proper work is already clear: one HEA profile, one Shopify dev store, the HEA dev Shopify app installed, and a narrow private pilot plan before production merchants use the production app.