Help center Core configuration Integrations & migrations Connect Shopify stores and verify complete purchase-history access Updated Friday, November 13, 2026 · Marc Staine Connect Shopify so agents can answer purchase and shipment questions from a Contact or Case. The integration reads customer profiles and orders on demand. It does not create orders, issue refunds, cancel purchases, or copy your complete order database into Supportbench. At a glanceFor: administrators with integration-edit permission. Applies to: Supportbench Core.Start here: Settings → Integrations → Shopify Availability and who configures what · Prepare the store and administrator access · Connect a Shopify store · Understand every control and status · Verify orders older than 60 days · Worked example: two regional stores · Maintain the connection and handle privacy requests · Troubleshoot and recover · Test safely before using a live store · Example of purchase visibility Availability and who configures what This guide applies to the Core Shopify integration after Supportbench enables the matching release and database setup for your account. If Shopify is absent from Settings, ask Supportbench about availability. Example screenshots use fictional data rendered by the actual Core controls; they are not evidence of a live Shopify connection.Supportbench owns the shared public Shopify app, its credentials, callback registration and Shopify access reviews. A customer administrator connects their own store and approves access. Customers do not create a replacement private app or paste a Client secret into this Settings tab. Prepare the store and administrator access A store is an individual Shopify shop, identified by its permanent myshopify.com address. One Supportbench account can connect several stores. Each store keeps its own customer match, purchase totals, currency, and order history. A Shopify customer ID identifies a customer within that store; it is different from a Supportbench Contact ID.Confirm that you can edit integrations in Supportbench and authorize apps for the intended Shopify store. Agents who can view a Contact can view its Shopify purchases; Contact edit permission is needed to change its customer link.Confirm that you can open the intended store in Shopify. Shopify selects the store during installation; Supportbench does not ask you to type a Shopify store address. Have your own Supportbench account address ready, for example northline.supportbench.net.Ask Supportbench to confirm that the Core release, manual database update, and Shopify app registration are ready. An operations administrator should not create a private replacement app or paste tokens into a Contact.Arrange a test customer with a known recent order and a known order older than 60 days. Record both order numbers and the correct store so verification has an objective result. Connect a Shopify store Open Settings → Integrations → Shopify and choose Connect store. This opens the Supportbench Shopify App Store listing. You can also start from the listing itself. Shopify is the last integration in Settings and opens in its own workspace tab in tabbed mode.In Shopify, select the intended store, choose Install, review the read permissions and authorize Supportbench. The Shopify authorization happens before Supportbench account selection.On Connect your store to your support team, check the authorized store name. Enter your Supportbench account address, such as northline.supportbench.net, then choose Continue to sign in. This is your helpdesk address, not your Shopify store address.Sign in on your own Supportbench account using your usual password, single sign-on and any verification steps. Stay in the same browser. You need permission to manage integrations.Check the store and Supportbench account shown on the confirmation page. Choose Connect this store. Choose Not now if the account is wrong; the store remains unreadable.Setup returns to Settings → Integrations → Shopify. Choose Verify connection. Confirm Connected and full-history access, then compare a known recent order and an order created more than 60 days ago with Shopify.Repeat for another store. Each store has separate customers and totals. Opening an already-connected Supportbench app in Shopify returns to its existing account without resetting customer matches.Worked example: Northline Manufacturing selects its Northline Supply store in Shopify, then enters northline.supportbench.net. Its integration administrator signs in, checks both names and chooses Connect this store. A support agent then opens Jamie Chen’s Contact and the Shopify tab to verify the intended customer and order. The integration is free; a Supportbench account is required and its subscription is separate.If you do not have a Supportbench account, use Explore Supportbench and create your account on the setup page. Once it is ready, reopen the app in Shopify to start a fresh setup. Authorization must finish within ten minutes; account selection and confirmation expire after thirty minutes. The sign-in handoff lasts twenty minutes. If a browser was changed, setup expired or the wrong account was selected, reopen Supportbench in Shopify and start again. A store cannot silently transfer between Supportbench accounts. Contact Supportbench to resolve ownership. Understand every control and status Control or statusPurpose and expected resultSupportbench account addressShown after Shopify authorization. Enter the helpdesk address your team uses to sign in, for example northline.supportbench.net.Connect storeOpens the published Shopify App Store listing. Shopify chooses the store and asks for authorization. Before listing availability, this button is unavailable with an explanation; development-store installs start from Shopify Dev Dashboard. No API token is entered or displayed.ConnectedThe installed connection has the required scopes and its protected-data probe succeeded. Verify representative orders before operational rollout.History access incompleteRequired order-history or customer-data access is missing. The agent view must not present a 60-day subset as complete history.Authorization in progressAn unfinished installation currently owns the connection request. Complete it or retry after the pending period.Verify connectionChecks the current store identity, granted scopes, protected customer fields, and an older-order query. An empty test result does not prove that a particular historical order exists.ReconnectStarts fresh authorization for the same store. Use it after revoked or expired access, or to grant newly approved scopes.DisconnectStops purchase visibility and removes this installation’s stored credentials and links. It does not delete Supportbench Contacts or Shopify orders.Privacy requests / Download responseProvides the retained integration-link data for a verified Shopify data request. Use your organization’s privacy process to supply the response; this does not send an email. Verify orders older than 60 days Shopify normally restricts order access to the most recent 60 days. Supportbench requires read_all_orders together with read_orders and read_customers. Shopify approval and the merchant’s granted permissions are separate from merely declaring these scopes in an app.Choose Verify connection in Shopify settings. Resolve any incomplete-access message.Open the approved test Contact and select its Shopify tab. Check the selected store and matched customer.Use Load older orders until the known order older than 60 days appears. Confirm its order number, date, currency, and amount against Shopify.Expand that order and check the available items and shipment information. Include a cancelled or refunded order in testing if those records exist for the customer.Record the successful comparison before making purchase visibility part of your team’s standard workflow.History is loaded 20 orders at a time without a date cutoff. Closed, cancelled, refunded, and archived orders remain eligible when associated with the linked customer and accessible through Shopify. Draft orders and abandoned checkouts are not included. Deleted or redacted information cannot be restored by this integration. Worked example: two regional stores Northline support teamNorthline connects northline-ca.myshopify.com and northline-us.myshopify.com. Jamie has purchased from both using the same email address. In the Contact Shopify tab, select the Canadian store to see its Canadian-dollar total and orders; select the US store to see the separate US-dollar history. Do not add the two totals together or assume a matching order number identifies the same purchase across stores.Before rollout, the administrator checks Canadian order #1048 from this month and #1002 from last year. The older order appears after Load older orders. They repeat the test in the US store because a successful Canadian connection does not verify the other store. Maintain the connection and handle privacy requests Core renews expiring access tokens when the integration is used. An unused connection can eventually require authorization again when its refresh credential expires. Reconnect is also appropriate after an app uninstall or revocation. Refresh in the agent view retrieves current purchase information; it does not repair missing permissions.Use Disconnect when a store should no longer supply purchase information to this Supportbench account. If removing the app completely, also follow your Shopify administration process.Review Privacy requests when Shopify sends a customer data request. Download the response and route it through your organization’s verified privacy process. The response contains integration linkage, not a replica of Shopify orders.Customer redaction removes the relevant external linkage and suppresses rematching. Independent Supportbench Contact records remain governed by your organization’s separate retention process.Restrict downloaded privacy responses to authorized staff. Never include app secrets, tokens, callback URLs containing codes, or complete customer payloads in routine troubleshooting. Troubleshoot and recover SymptomRecoverySetup requiredAsk the deployment administrator to check the app configuration and manual shared/tenant database prerequisites. Agents cannot fix this by editing a Contact.History access incompleteConfirm Shopify approved all-order and protected-customer access, reconnect to grant approved scopes, then verify again. Do not describe recent-only data as a full history.Reconnect requiredReconnect the intended store using an authorized Shopify administrator, then verify a known customer and old order.Store linked elsewhereConfirm the correct Supportbench account. Contact Supportbench for ownership investigation; reconnect does not transfer another account’s store.Shopify busy or refreshingRetry shortly. The application keeps failures distinct from a genuine empty history. Avoid repeatedly starting installations.Connected but no customer matchCheck the Contact’s email and selected store. A Contact editor can manually select the correct Shopify customer.Some fields unavailableCheck the visible message and Shopify customer-data approval. Do not infer that missing personal details mean the customer has no orders. Test safely before using a live store Shopify development stores provide a real API test environment. A developer with a Shopify Partner account can create one in Dev Dashboard → Stores → Create store → Dev. Shopify can generate sample customers, products and draft purchases. Complete the relevant draft orders in the development store before testing this integration: draft orders are outside its purchase list.Ask Supportbench to prepare an isolated test app, callback and account. Do not use production customer records as demonstration data.Install/open the app from Shopify Dev Dashboard on an authorized development store. Complete Shopify authorization, enter the Supportbench account address, sign in and confirm the store/account. Then choose Verify connection.Create a Supportbench test Contact whose email exactly matches a Shopify test customer. Open its Shopify tab and verify the customer and a real completed test order.Test both recent orders and an order whose Shopify creation timestamp is genuinely more than 60 days old. Newly generated data may not provide that historical sample; changing another order date is not proof of older-order access.Exercise multiple stores, refunds, cancellation, item pages, expired credentials, unlinking and role restrictions before release acceptance.An offline demo is also useful for training and sales. It can show the same controls using fictional replies and can run without a Shopify account. It demonstrates the interface only; OAuth, Shopify approvals, real history and database authorization still need integration testing.See Shopify development stores and generated test data. Example of purchase visibility See the Contact purchase-history example for a screenshot of the actual Core Shopify control with fictional data. The surrounding frame is illustrative; this is not a live Shopify connection. Continue learning Manage companies and contactsWork with Cases and customer conversationsView Shopify purchases, shipments and customer links Was this article helpful? Yes No Thank you for your feedback.