n-Help Scout's WooCommerce App Shows Ten Orders. Getting There Takes a Lot More Than Clicking Install.
Connecting WooCommerce to Help Scout means buying a separate plugin from WooCommerce's own marketplace, then manually enabling the legacy REST API, fixing your permalink settings, and generating credentials that disappear if you navigate away before copying them. Once all of that's done, the payoff is real: contact details, lifetime value, and up to ten recent orders per customer, right in the sidebar, across as many connected stores as you run.
What the integration covers once it's actually running
The sidebar is genuinely useful. Contact information, lifetime value, average order value, and up to ten recent orders per customer show up next to the conversation, with a one-click link through to the full order or the customer's profile in WordPress admin.
Multiple stores work, and they're labeled. Unlike Shopify's own Help Scout app, which never addresses running more than one connected store, WooCommerce's integration explicitly supports multiple stores and keeps each one distinctly labeled in the sidebar, so a multi-brand setup doesn't blur together.
It's a WooCommerce product, not a Help Scout one. The plugin is sold through WooCommerce's marketplace, and WooCommerce owns support for it. If something breaks on the technical side, Help Scout's own support isn't the first call.
Where the setup itself is the first obstacle
This isn't a one-click app install the way Shopify's is. You buy the plugin, install it on your WordPress site, enable WooCommerce's legacy REST API, make sure your permalink structure isn't set to 'Plain,' generate a Consumer Key and Secret, and paste all of it into Help Scout's own settings before any customer data shows up in a ticket. The credentials only display once; leave that screen before copying them and you're generating a new set.
Even after all that, the sidebar caps at ten recent orders per customer. A high-frequency buyer's eleventh-oldest order, or anything relevant to a dispute from further back, isn't there. An agent still has to open WordPress admin directly for that.
What we've built on top of Help Scout and WooCommerce
A multi-brand retailer running three WooCommerce stores through one shared Help Scout inbox had gotten the native plugin working on all three, correctly labeled, which covered the basics. The real friction showed up with their most loyal customers: anyone who'd placed more than ten orders on a single store had older purchases an agent simply couldn't see without a separate WordPress admin login, and most frontline agents didn't have one.
We built a direct connection to each store's own WooCommerce REST API, bypassing the ten-order cap entirely and pulling a customer's complete order history into the same sidebar the native plugin already populates. The labeled multi-store view stayed exactly as it was; agents just stopped hitting a wall at order eleven.
Got the WooCommerce plugin configured and still running into the ten-order limit?
Tell us how many stores you're connecting and how far back your agents actually need visibility. We'll build past the plugin's cap using WooCommerce's own API, on top of the setup you already have, not instead of it. And if WooCommerce isn't your actual bottleneck, we'll look at what is.
Let's talk