Integration guide

Help Scout and Shopify: Order Data Next to the Email

The integration that makes Help Scout viable for an ecommerce store. Orders, fulfilment and tracking in the sidebar, which is most of what ecommerce support actually needs to answer.

Connector
Native — Shopify app from the Help Scout apps directory
Sync direction
Shopify → Help Scout
Setup time
15 minutes per store
Availability
Available across Help Scout plans; multiple stores supported
What moves between Help Scout and Shopify
What Direction Detail
Recent orders Shopify → Help Scout The customer's recent orders with status, matched by email address. The core of the integration.
Fulfilment and tracking Shopify → Help Scout Shipment status and tracking numbers, which resolve the single highest-volume ecommerce question outright.
Line items Shopify → Help Scout Products, variants and quantities — needed for anything beyond a where-is-my-order question.
Customer value Shopify → Help Scout Total spend and order count, giving agents a sense of whether this is a first-time buyer or a regular.
Order links Shopify → Help Scout Direct links into the Shopify admin for anything the sidebar cannot answer, which saves a search.
Multi-store Shopify → Help Scout Several stores can be connected, with the sidebar indicating which store an order came from.

Setting it up

  1. Install the Shopify app from Help Scout's apps directory and connect each store you support.
  2. Choose which fields display. Order status, tracking and line items earn their place; total spend is useful; anything more crowds the panel.
  3. Build saved replies that use the sidebar data — a shipping status reply especially, since that is the highest-volume conversation type in ecommerce.
  4. Test with a guest checkout and, if relevant, a subscription order, because those are the two cases where the sidebar comes up empty.
  5. Agree the refund process. Since agents cannot refund from Help Scout, decide whether they switch to Shopify themselves or escalate.
  6. Measure handling time on shipping conversations before and after. The effect is usually large enough to be worth recording.

Where the integration stops

  • Read-only. No refunds, cancellations or order edits from Help Scout. Refund-heavy stores will find agents switching to Shopify constantly.
  • Email matching only. Guest checkouts and purchases made under a different address show nothing.
  • Recent orders, not full history. Long-standing customers may need a lookup in Shopify.
  • Subscription data is often missing. Orders managed by a subscription app frequently render incompletely, which matters if that is your business model.
  • No ticket data flows to Shopify, so marketing automations there have no idea a customer has an open complaint.

What ecommerce support actually consists of

A small number of question types, repeated endlessly. Where is my order. When will it arrive. What did I buy. Can I return it. Is this the right size.

Four of those five are answerable from order data. Putting that data beside the email removes a tab switch from the majority of conversations, which at ecommerce volumes is a substantial amount of time.

The read-only question

This is the fork in the road for choosing Help Scout for a store.

If your agents mostly answer questions, read-only is fine and the simplicity is a benefit. If your agents mostly perform actions — refunds, exchanges, address changes, cancellations — then every one of those is a context switch, and a helpdesk with write capability in the sidebar will feel meaningfully faster.

Count your last hundred conversations by type before deciding. Most stores are more question-heavy than they assume, but the ones that are not should know it before committing.

The saved reply that pays for the integration

Shipping status. It is the highest-volume conversation type in almost every store, it is fully answerable from the sidebar, and a saved reply that pulls the tracking number turns a two-minute interaction into a fifteen-second one.

Building that one reply properly delivers more measurable value than the rest of the configuration combined.

The subscription caveat

If your store runs subscriptions through a third-party app, check what the sidebar shows for a subscription customer before assuming this covers your support load. Next billing date, pause status and plan changes typically live in the subscription app rather than in Shopify's order data, and the panel will not surface them.

For subscription-led stores, the subscription platform's own Help Scout app is usually the more important install, with the Shopify one as a supplement rather than the other way around.

Frequently asked questions

Can agents issue refunds from Help Scout?
No — the integration is read-only, so refunds and cancellations happen in Shopify. Whether that is a problem depends entirely on your refund volume. A store where a handful of refunds happen daily loses very little from agents switching tabs. A store where refunds are a substantial share of contacts will feel the friction on every one, and should weigh a helpdesk whose Shopify integration includes order actions. It is one of the clearest functional differences between Help Scout and the heavier ecommerce-focused helpdesks.
Why is the sidebar empty for some customers?
Email mismatch, almost always. The app matches the conversation's sender address against Shopify customers, so a guest checkout made with a different address, a gift purchase, or an email sent from a work account produces nothing. There is no configuration that fixes this. The practical answer is a saved reply that asks for an order number early, plus the agent habit of searching Shopify on the surname or domain when the panel is blank.
Is Help Scout a reasonable ecommerce helpdesk?
For stores whose support is predominantly email and predominantly answerable from order data, yes — and the simplicity is a genuine advantage over heavier tools that need configuring before they are useful. Where it fits less well is high-volume operations needing order actions in the sidebar, deep subscription handling, or the automation and routing depth that a large support team depends on. The honest dividing line is refund and exchange volume: if agents are performing order actions many times a day, the read-only sidebar becomes the bottleneck.