Burrow for Shopify agencies

Connect a Shopify store with a read-only Admin API token — orders, fulfillments, refunds, and checkout signals land alongside WordPress, GitHub, Stripe, and analytics, with up to two years of history backfilled.

Connect Shopify to Burrow Read the docs

Read-only Admin API token
Up to 2 years of order history backfilled
Nothing added to the storefront unless you opt in

[ Connect in two minutes ]

How to connect Shopify

1

Create a custom app in your Shopify Dev Dashboard

In the store's Dev Dashboard, create a custom app with read access to orders. Copy the Admin API access token (Shopify shows it once) and the app's client secret.
2

Paste the store domain and token into Burrow

Add the Shopify integration, enter the store's myshopify.com domain and the access token. The client secret lets Burrow verify webhooks so orders stream in live; without it you still get scheduled syncs.
3

Map the store to a client project

Each connected store is mapped to the Burrow project for that client. Burrow registers order webhooks and backfills history — up to two years if the app has read_all_orders, otherwise the trailing 60 days Shopify exposes by default.
4

Optional — add the Burrow pixel for cart and checkout signals

Order data comes from the Admin API. For add-to-cart, remove-from-cart, and checkout-started events, paste the Burrow custom pixel into the store's Customer Events settings. Skip it if orders are all you need.

[ Capabilities ]

Commerce events in the client timeline

Order placed, fulfilled, cancelled, refunded — plus cart and checkout-started signals from the optional pixel — land in the same Burrow project as GitHub deploys, WordPress form submissions, and Stripe billing. No Shopify Admin screenshots needed.

Mixed-stack clients finally unified

Your client has a Shopify store, a WordPress blog, and a custom checkout. ManageWP sees WordPress. Shopify Admin sees commerce. Nobody sees both. Burrow does.

Commerce context in monthly reports

Automated digests include revenue milestones, order volume trends, and checkout health alongside engineering and marketing activity — so client reviews tell the full retainer story.

Example

Normalized Shopify order event in Burrow

{
  "source": "shopify",
  "type": "ecommerce.order.placed",
  "projectId": "client_northwind",
  "payload": {
    "orderId": "5012",
    "total": "247.00",
    "currency": "USD",
    "itemCount": 3,
    "checkoutMethod": "online_store"
  }
}

The Shopify dashboard shows the store. It doesn’t show the agency.

Shopify Admin is great for managing one store. Products, orders, fulfillment, analytics — all there. But for agencies managing the entire client relationship, Shopify Admin is one tab among many.

Client A has a Shopify store, a WordPress marketing site, and deploys through GitHub. Client B runs Shopify Plus with a headless Next.js front end, Stripe for subscriptions, and Craft CMS for editorial content. Client C has Shopify, WooCommerce (for a different brand), and a Laravel API serving both.

Your account manager’s Monday prep looks like this: open Shopify Admin for commerce data, ManageWP for WordPress health, GitHub for recent deploys, Stripe for billing, Google Analytics for traffic. Five tabs. Five logins. One story to assemble before the client call.

That assembly job is what Burrow eliminates.

Shopify order events, WordPress form submissions, GitHub deploys, Stripe invoices, and analytics milestones all flow into one Burrow timeline per client. The monthly digest writes itself from real data. The read-only portal gives the client live transparency without granting them admin access to anything.

Why Shopify Admin alone fails agencies

Shopify Admin is designed for merchants, not agencies managing merchants. The distinction matters:

Merchants want to see their own store data — orders, products, customers, revenue. Shopify Admin does this well.

Agencies need to see store data in context — alongside what the developer shipped this month, whether the contact form is working, what the analytics say about the campaign, and whether the billing relationship is healthy. Shopify Admin shows none of that context.

When checkout conversions drop 30% and your client asks why, Shopify Admin shows the drop but not the cause. Burrow’s timeline might show a theme deploy from GitHub 4 hours before the conversion drop — because both signals live in the same project. That correlation is invisible when each tool exists in its own silo.

The scenario

Client X runs a Shopify store alongside a WordPress blog and uses Stripe for subscription billing. Thursday afternoon, their checkout starts returning 500 errors on mobile after a theme update pushed through the Shopify Partner Dashboard.

Without Burrow: Your team finds out Monday when the client shares a revenue chart showing a 40% drop over the weekend. The developer investigates, finds the broken checkout, and fixes it. Three days of lost revenue. The client questions whether the retainer is worth it.

With Burrow: Shopify checkout error signals spike Thursday at 3pm. Burrow flags the anomaly. The developer rolls back the theme change the same afternoon. Revenue impact is measured in hours, not days. Monday’s client call: “We caught a checkout issue Thursday and resolved it within hours. Here’s the timeline.”

Burrow vs. Shopify analytics tools (Kleio, Triple Whale, Lifetimely)

Agencies running Shopify retainers often encounter merchant-facing analytics tools: Kleio ($29/mo — P&L, LTV, cohorts, profit tracking), Triple Whale (from $219/mo, scaling with GMV — attribution, P&L, creative analytics), and Lifetimely by AMP (free to $999/mo by order volume — LTV and cohort analysis). These tools answer the merchant’s question: “Am I profitable?”

Burrow answers the agency’s question: “What happened across this client’s entire stack this month — and what should we tell them?”

The distinction matters because agencies don’t just manage stores. They manage stores plus WordPress sites, deployment pipelines, contact forms, email campaigns, billing relationships, and uptime. Kleio shows the store’s profit margin. Burrow shows the store’s profit signals alongside the Friday deploy that broke checkout, the WordPress form that stopped delivering leads, and the Stripe invoice that cleared.

For agencies managing Shopify clients, the stack often looks like:

Kleio or Triple Whale: merchant-facing analytics — installed on the store, tracking P&L, LTV, and ad ROAS
ManageWP or MainWP: WordPress maintenance for the client’s marketing site or blog
GitHub: deploy and release tracking
Burrow: the agency operations layer that unifies Shopify commerce events, WordPress form signals, deploy history, and billing into one client timeline with automated reporting

They’re complementary. The analytics tool lives inside the store. Burrow lives across the entire retainer.

How it fits with other tools

Burrow doesn’t replace Shopify Admin, Kleio, ManageWP, or GitHub. It’s the layer above that unifies signals from all of them:

Shopify Admin / Kleio / Triple Whale: store analytics — products, orders, P&L, LTV, profit tracking
ManageWP/MainWP/WP Umbrella: WordPress maintenance — updates, backups, security
GitHub: code operations — deploys, PRs, releases
Burrow: unified client timeline — all of the above correlated per project with automated reporting

Frequently asked questions

Is Burrow a Shopify app?

Not an App Store listing. You connect each store through a custom app you create in that store's Dev Dashboard — a store domain and a read-only Admin API access token. That keeps the credential scoped to one store and revocable by the merchant at any time. Burrow is the operations layer above it, ingesting signals from Shopify, WordPress, GitHub, Stripe, and 20+ other tool categories.

What Shopify events does Burrow capture?

From the Admin API and webhooks: order placed, order fulfilled, order cancelled, order refunded, and per-line-item purchases. From the optional storefront pixel: cart added, cart removed, and checkout started. Together they feed the Ecommerce channel — revenue and order trends, the conversion funnel, best sellers, and abandoned carts — and the client's timeline. Custom checkouts can also send commerce events through the Burrow API.

How much order history does Burrow import?

Up to two years on connect, in the window you choose. Shopify's default read_orders scope only exposes the trailing 60 days; grant the custom app read_all_orders for the longer backfill. After the initial import, webhooks keep the timeline current and scheduled syncs catch anything missed.

Does Burrow write anything to the store?

No. The Admin API access is read-only, and the only thing Burrow registers on the store is its own webhook subscriptions for order events. The pixel is opt-in and only sends cart and checkout signals out — it changes nothing on the storefront.

Can I use Burrow if I only manage Shopify stores?

Yes, but Burrow's real value shows when you manage multiple systems per client. If your clients also run WordPress, deploy through GitHub, bill through Stripe, or use analytics tools — Burrow unifies all of those signals. For Shopify-only stores, Shopify Admin is sufficient.

How does this differ from Shopify Analytics?

Shopify Analytics tells you what sold. Burrow helps agencies correlate commerce signals with engineering deploys, form submissions, marketing events, and operational incidents. When checkout conversion drops the same day as a theme deploy, Burrow makes that connection visible.

How is Burrow different from Kleio, Triple Whale, or Lifetimely?

Those are merchant-facing Shopify analytics tools — they track P&L, profit margins, LTV, cohorts, and (for Triple Whale and Lifetimely) ad attribution for individual stores. Kleio does it for $29/mo flat, Triple Whale from $219/mo scaling with store GMV. Burrow is not a Shopify analytics replacement. It's an agency operations layer that puts Shopify commerce signals alongside WordPress events, GitHub deploys, Stripe billing, and form health in one client timeline. An agency running Shopify analytics for a client might use Kleio inside the store and Burrow across the full retainer.

Does Burrow do profit tracking or LTV analysis?

No. Burrow captures commerce events (orders, checkout, fulfillment) as operational signals for agency-level reporting and anomaly detection. For merchant-facing profit tracking, COGS, LTV, and cohort analysis, use a dedicated Shopify analytics app like Kleio ($29/mo) or Triple Whale. Burrow complements those tools by adding the operational context they can't see — deploys, form health, CMS events, and cross-platform signals.

Does Burrow handle Shopify Plus?

Yes. Custom apps and the Admin API work the same on standard and Plus stores, so the operational signals are the same — order events, checkout activity, fulfillment updates. Plus-specific features like checkout customization don't change how Burrow ingests events.

What about headless Shopify setups?

Send checkout events from whichever system owns the transaction — Shopify's Storefront API, a custom front end, or a third-party checkout. Burrow normalizes by project, not by hosting topology.

[ Related ]

Channel

Gross revenue across every store you manage

Gross revenue, order trends, and cart-to-purchase funnels across every client store — WooCommerce, Shopify, and Craft Commerce.

Use case

WooCommerce and ecommerce analytics for agency client reporting

Track WooCommerce orders, revenue, and checkout health across every client store — commerce data alongside deploys, forms, and billing.

Comparison

Shopify Analytics alternative

Shopify Analytics alternative for agencies — native reporting shows what sold in one store; Burrow shows the full client retainer, from orders to deploys and uptime.

Your agency's work deserves to be seen.

Start a 30-day free trial — no credit card required. Connect your first sources and see every client signal in one timeline.

Start free trial See a sample report ↗

Self-funded · Independent · Built for the long term