How Do I Connect Claude to Shopify? (Step-by-Step, 2026)

Build-in-public post — the exact setup we use to let Claude operate a Shopify store, not just talk about it. Part of our AI workflows pillar. The store I test all of this on is my own: MYNDR, built with Claude Code.
The customer pain point
Most people use Claude for Shopify the slow way: copy a question in, paste advice out, then go do the work manually in the Shopify admin. That's Claude as an advisor. The shift that actually saves hours is Claude as an operator — it reads your real catalog, runs real analytics on your real numbers, and (with your approval) makes the change directly.
The blocker is the connection. Until Claude can see your store, every conversation starts with you describing your store from memory. Once it's connected, Claude works on the store. This post is how you make that connection.
Table of Contents
- What "Connecting" Actually Means
- The Setup, Step by Step
- What Permissions It Asks For
- How to Verify It Worked
- What to Watch For
Key Takeaways
| Point | Details |
|---|---|
| What it is | The Shopify connector links Claude to your store so it can read products, orders, customers, analytics, and make changes via the Shopify API. |
| Setup | Enable the Shopify connector in Claude's connector settings → authorize your store → confirm the permission scope. A few minutes. |
| Plan requirement | Connectors require a paid Claude plan. See do I need a paid Claude plan to connect Shopify? |
| Safety | Claude proposes changes; you confirm before anything writes. Never skip the confirm step on bulk operations. |
What "Connecting" Actually Means
The Shopify connector gives Claude a structured pipe to your store's data and actions. Once connected, Claude can:
- Products & inventory — create/update products and variants, adjust pricing and stock, bulk-change product status
- Collections — create manual or smart collections, edit rules and images
- Orders & customers — list and inspect orders, search and look up customers
- Discounts — create percentage discount codes scoped to collections, with minimums and scheduling
- Analytics — run ShopifyQL queries for sales trends, conversion rate, top products, traffic sources (results render as charts)
- Store info — plan, currency, timezone, domain
It's the difference between "here's what you should do about your AOV" and "your AOV dropped 12% last month, here's the segment that caused it, here's the fix — want me to apply it?"
For the full prompt library to actually use this, see how to use the Shopify connector in Claude.
The Setup, Step by Step
- Open Claude's connector settings. In Claude (web or desktop), go to Settings → Connectors. Connectors are the managed integrations Claude offers — Shopify is one of them.
- Find the Shopify connector in the available connectors list and click to add/enable it.
- Authorize your store. Claude redirects you to Shopify's OAuth screen. Log into the store you want to connect (you must be a staff member with sufficient permissions on that store).
- Review and approve the permission scope (covered in the next section). Shopify shows exactly what access Claude is requesting.
- Confirm. You're returned to Claude with the store connected.
- Test it (see verification below) before relying on it for anything real.
If your store is on a custom domain, you connect via the store's primary domain or the *.myshopify.com admin URL — either resolves to the same store.
What Permissions It Asks For
Shopify's OAuth screen lists the scopes Claude requests — typically read/write on products, inventory, collections, orders, customers, discounts, and read on analytics/shop info. Read this screen. You're granting an AI assistant the ability to change your live store.
Our operating rule: that's fine because the workflow keeps a human gate. Claude proposes; you confirm before any write. The connector having write scope is what makes "apply this change" possible — the discipline of confirming before apply is what makes it safe. We cover that discipline in what AI-run means when the AI screws up.
If you want a read-only posture (analytics and inspection only, no changes), connect with a staff account whose Shopify permissions are read-only. Claude can't write what the authorized account can't write — Shopify's own permission model is the backstop.
How to Verify It Worked
Don't trust a "connected" badge. Verify with a harmless read query:
Using the Shopify connector, pull my store info — plan, currency,
timezone, and primary domain. Then tell me how many products are in
the catalog and the 3 most recent orders (just IDs and totals, no
customer PII).
If Claude returns your actual store details and real order IDs, the connection is live and reading correctly. If it returns generic placeholders or an error, the authorization didn't complete — reconnect.
Then test a scoped analytics read:
Run a ShopifyQL query for total sales the last 30 days vs the prior
30 days. Show it as a chart.
Real numbers + a chart = fully working.
What to Watch For
- Confirm before every write. The connector can change live products and pricing. Always make Claude show you the before/after and a count before it applies a bulk change. Build the habit on day one.
- Staff permissions are the real boundary. Claude inherits the authorized account's Shopify permissions. Connect with an account scoped to exactly what you want Claude able to do.
- Plan requirement. Connectors aren't on the free Claude tier — details in do I need a paid Claude plan to connect Shopify?.
- One store at a time, intentionally. If you run multiple stores, be deliberate about which one is connected in a given conversation — Claude acts on the connected store. Verify with the store-info read above before any bulk action.
- Disconnect when done if it's a shared machine. The connection persists. On shared/agency machines, disconnect after the session.
Talk to Branva
We run Claude-operated Shopify workflows — catalog ops, analytics, bulk updates, all with human review gates — as part of our managed operations. Book a free call and we'll show you what we'd automate first on your store.
Frequently Asked Questions
How do I connect Shopify to Claude AI?
Two ways: use the official Shopify connector inside Claude (Settings → Connectors → Shopify) for chat-based access to your store data, or connect via MCP for deeper workflows — including Claude Code for developer-style store operations. The connector route takes about 2 minutes and needs no code; the full setup for both is below.
Is the Shopify connector the same as MCP?
Related but not identical. MCP (Model Context Protocol) is the open standard for connecting Claude to tools; the Shopify connector is a managed integration Claude offers out of the box. For most operators the managed connector is the path — no server to run.
Do I need to be the store owner to connect it?
You need to be a staff member with sufficient Shopify permissions. The connector inherits whatever the authorizing account can do. Store owner works; a staff account with the right scopes also works.
Can Claude break my store?
It can change live data (products, prices, collections) because that's the point of write access — but only when you confirm. The risk isn't the connector; it's skipping the confirm step on bulk operations. Never let Claude apply a bulk write without showing you the count and a sample first.
Does connecting cost extra on the Shopify side?
No. The connector uses the standard Shopify API, available on all Shopify plans at no extra charge. The cost question is on the Claude plan side — see the linked post.
Related reading
- Do I Need a Paid Claude Plan to Connect Shopify? — the eligibility/pricing answer.
- How to Use the Shopify Connector in Claude (Operator Prompts) — the prompt library: AOV, conversion rate, bulk price updates.
- How Do I Use Claude to Analyze My Klaviyo Account? — the email-side equivalent.
- The AI Workflows pillar — every workflow we run.