Skip to content
Help Center
Submit a request Sign in

Find customer purchases and shipment details from a Contact or Case

Use Shopify purchase visibility when a customer asks what they bought, which items shipped, or whether an order was refunded. Keep the conversation in Supportbench and open Shopify when a separate authorized commerce action is needed.

At a glance

For: support agents and Contact editors. Applies to: Supportbench Core.

Start here: Contacts → open a Contact → Shopify, or Case → Contact → Shopify purchases

Check feature availability and example data  ·  Check prerequisites and select the store  ·  Read purchases from a Contact  ·  Inspect purchases while answering a Case  ·  Correct a different email or ambiguous match  ·  Worked example: a partially shipped business order  ·  Understand the boundaries  ·  Recover from a failed read  ·  Examples: purchases beside the conversation

Check feature availability and example data

These procedures apply when the Core Shopify integration has been enabled for your account. If the tab is unavailable, ask your administrator to confirm the applicable Core release and connection setup. Example screenshots are clearly labeled fictional demonstrations of the actual controls. Their order dates, totals and connection badges are illustrative.

Check prerequisites and select the store

Your administrator must connect the store and verify full history access. You need permission to view the Contact; a Case also requires access to the Case and its current Contact. Only Contact editors can change customer links. The panel is an agent tool and is not a customer-portal order page.

A store selector appears when more than one store is connected. Always check its value before interpreting a purchase. Totals and currencies belong to the selected store. Shopify’s customer total is a lifetime aggregate supplied by Shopify, not a sum of the visible page. Refunds and adjustments can make it differ from a simple sum of order labels.

Read purchases from a Contact

  1. Open the Contact and choose the Shopify tab. Select the store if a selector is shown.
  2. Confirm the customer name and email. The view indicates whether the customer was matched by email or linked manually.
  3. Review total spent, order count, customer-since date, and tags. Tags are labels supplied by Shopify; they do not grant Supportbench permissions.
  4. Read the purchase list newest first. Expand an order to inspect payment status, items, quantities, available shipment tracking, and refunded amount.
  5. Choose Load older orders for the next 20 orders. There is no 60-day cutoff once the required Shopify access is granted. Use Load more items when a large order has additional items.
  6. Choose Refresh before relying on time-sensitive information. Check the update time. Ordinary reads can reuse a server result for up to two minutes.
  7. Use Open order in Shopify or Open customer in Shopify for the full commerce record. Shopify may require its own sign-in and permissions.

Inspect purchases while answering a Case

  1. Open the Case and its Contact pane. Confirm the Case is linked to the intended Contact.
  2. Expand Shopify purchases. A collapsed panel does not fetch purchase data.
  3. Select the store, inspect the relevant order, and continue composing the response in the Case. Opening the panel does not send a reply or change the Case.
  4. If the Case Contact changes, reopen the panel and confirm the new identity. A former Contact’s orders must not be reused as evidence for the new customer.

The compact Case panel uses the same order information and controls as the Contact tab. It derives the customer from the authorized Case rather than accepting an unrelated Contact selection.

Correct a different email or ambiguous match

Automatic matching requires a unique exact email match. Similar names are not sufficient. If the customer bought using another email, ask a Contact editor to confirm the correct Shopify record.

  1. Choose Choose Shopify customer, or Choose a different Shopify customer on an existing match.
  2. Enter the customer’s email address or name and choose Search. Results come only from the selected store.
  3. Review the candidate’s displayed name, email, and phone where available. Use your support verification process before linking a different address.
  4. Choose Show this customer's purchases and confirm the person and store. The link changes only Supportbench’s association; it does not edit Shopify or merge Contact records.
  5. Recheck the customer header and a known order. If the candidate is wrong, use Choose a different Shopify customer to correct it.

Choose Remove customer match to hide purchases from the selected store for this Contact and pause automatic email matching for that store. Nothing is deleted from Supportbench or Shopify. This avoids immediately recreating the same incorrect link. Choose Match using email again when the Contact’s email is correct and automatic matching should resume for the selected store. Privacy-redacted customers remain suppressed and cannot be restored by ordinary linking.

Worked example: a partially shipped business order

A customer asks where the remaining items are

Jamie’s Case concerns order #1048. In Shopify purchases, the agent selects Northline Canada and confirms Jamie’s email. The order is paid but partially fulfilled. Expanding it shows the purchased quantities and a UPS shipment. The agent checks which shipment information Shopify provides, opens the order in Shopify if necessary, and explains the confirmed status in the Case. They do not infer a delivery date from a fulfillment badge alone.

Jamie also asks about a purchase from last year. The agent uses Load older orders and verifies the older order number and date. An empty current page or an API error is not evidence that no historical purchase exists.

Understand the boundaries

Information or actionInterpretation
Payment and fulfillment badgesSeparate aspects of an order. Paid does not mean shipped; fulfilled does not by itself prove final carrier delivery.
Item amountsThe view labels original unit amounts as each. Discounts, tax, shipping, and refunds can make the order total differ from multiplying visible unit amounts.
Tracking linksOpen the carrier’s supplied HTTPS tracking destination. Carrier information may update at a different time than Shopify.
No ordersThe matched customer has no returned orders; this is different from no customer match, unavailable fields, or a failed request.
Refunds and cancellationsVisible information only. This integration cannot initiate a refund, cancel an order, or edit a shipping address.
Company-wide purchasesThe view follows the linked Shopify customer. It does not combine every employee’s orders into a company total.
Missing historical recordsCheck the store/customer link and permissions. Drafts, abandoned checkouts, deleted records, and orders not associated with the linked Shopify customer are not promised by this view.

Recover from a failed read

  1. Read the message before drawing a conclusion about purchases. Missing access, a disconnected store, and no match have different remedies.
  2. For Shopify busy or a connection renewal message, retry shortly. For full-history or customer-field access failures, ask an integration administrator to verify and reconnect the store.
  3. If the customer link changed while you were reading, refresh the panel and verify the displayed identity again.
  4. Report the store, visible error, approximate time, and relevant Supportbench Case to your administrator. Do not copy private access tokens or a complete customer response into an ordinary support message.

Examples: purchases beside the conversation

Compare the Contact Shopify example with the compact Case Shopify example. Both screenshots use the actual Core controls and clearly labeled fictional data, with illustrative surrounding frames.

Was this article helpful?