How to connect Claude to Shopify: three paths, one rule

You pull the same order and stock numbers out of your Shopify admin by hand every Monday. You have heard an assistant can do it, and you do not want to hand it the keys to the store.

The short answer. Install the Shopify connector from inside Claude on a desktop browser, then approve a data access level in your Shopify admin. Start read-only. The connector ships 25 tools, changes product status 50 at a time at most, and cannot touch a live theme, refunds or settings. Approve every write as a list first.

Who this is for. The founder or operator of a live Shopify store who wants answers from store data without writing code. It is not for developers building a custom app. They should start from Shopify’s developer docs.

A connector is a plug-in that lets an assistant read and change your store data, within the access you approve. This one is built on the Model Context Protocol, an open standard for plugging an assistant into an outside system. Shopify’s own help pages describe it in connecting third-party tools to your store. Our Shopify AI agent hub covers the wider set of agent jobs.

Three paths exist, and only one suits someone who has never opened a terminal. A terminal is the text window developers type commands into. Pick the wrong path and a bulk write, which is a change applied to many records at once, can stop partway.

The first session is for questions, not changes

Install the connector and ask questions. Nothing else. A wrong answer then costs a second question, not a wrong price on a live product.

Shopify says to mention Shopify by name so Claude uses the connector. It also says to keep each request to one task, because a question that layers several comparisons can fail or return a hard-to-read result.

Useful first questions:

• Show my 10 most recent orders.
• Show total sales for the last 30 days, broken down by product.
• What is my average order value this month compared to last month?
• How much stock of this product sits at each location?
• Open order 1234 and summarise its status, items and tracking.

Claude sees Shopify data only. Ad spend, shipping cost and returns sit outside it. So does COGS, the cost of goods sold: what each unit costs you before you sell it.

Three paths exist, and the job picks the path

Pick the path that matches the job, not the one that sounds most powerful. For most owners the connector covers it.

Path 1: the connector app, no code

This is the default, and what most people mean by a Shopify Claude connector.

• Open the Shopify connector page on claude.com on a desktop browser and choose “Add to Claude”.
• Claude sends you to Shopify to sign in. Pick the store you want connected.
• Read the install page. It lists the data access being requested. Approve or decline there.
• Go back to Claude. Ask it which store it is connected to before anything else.

Shopify sets out the flow on its third-party tools page. If a screen does not match this page, trust Shopify’s page.

Path 2: a second connector joins Shopify to your other tools

Because Claude uses the open standard, you can add a second connector and ask a question that crosses both. Klaviyo documents an MCP server that an assistant such as Claude can connect to, and says it supports tasks from campaign creation to flow performance reports. With both connected, one question can span orders and email. Check the connector directory inside Claude for your own stack. Shopify MCP explained for store owners breaks down the three kinds Shopify ships.

Path 3: Claude Code and the Shopify CLI carry the bulk work

Shopify’s help says a connected tool changes items one at a time, so a large batch can stop partway. When the job is hundreds of products, a theme change, or something you will repeat, use a developer path. Claude Code is the version of Claude that runs in a terminal on your own machine.

The developer path is the Shopify AI Toolkit. It gives a coding agent Shopify’s docs and API schemas, and validates GraphQL, Liquid and extensions against them. GraphQL is how code asks Shopify for data. Liquid is Shopify’s template language for themes. With Node.js 18 or higher, Shopify documents this install for Claude Code:

Shopify also documents an MCP server route, then a restart of Claude Code:

The toolkit page says store management runs through Shopify CLI’s authenticated store context, with you choosing when to execute. Shopify’s help calls the CLI connector the route for developers connecting from their own machine.

What we saw on a real store

Path 3 is the one we use for client work. A client store, a made-to-order brand shipping worldwide, needed 51 city pages: 50 “made for” pages and one delivery hub. A coding agent built them from one template and a data file per city.

We pushed the pages to Shopify as unpublished drafts on a duplicate of the live theme. The founder reviewed the preview and gave the go. Source: the client work board and project record, checked 22 September 2026.

The pattern is the point: write to a draft, preview, and let a person publish. Shopify documents the same split. A connected tool can change an unpublished theme but not the live one.

Shopify documents a plugin for ChatGPT with the same actions list and the same desktop-browser setup. Sidekick vs Claude vs ChatGPT routes six real tasks to the right assistant.

Ten prompts worth running first, each asking for its source

Each prompt asks the assistant to show its source. A number with no named records behind it may not have been read from your store. Eight of the ten only read. The two that write are staged: propose, review, apply.

• “Confirm which store you are connected to, then list what you can read and change.”
• “Show total sales for the last 30 days against the 30 days before. Name the date range behind each figure.”
• “List products with no sale in 180 days. Show the query you ran and say if it was cut short.”
• “List products under 10 units at one location and over 100 at another. Name both locations.”
• “Open order 1234 and draft a reply from its fulfillment status and tracking. Quote the order number.”
• “Show my average order value this month against last month. Name the source of each figure.”
• “Show how many new and returning customers I had this month.”
• “Show my 10 most recent orders and flag anything odd in value or destination.”
• “Propose an 8 percent price rise across this collection. Output the before and after list. Change nothing.”
• “Draft new descriptions for these 20 draft products. Show all 20 as a list before writing anything.”

Permissions you approve cannot be lowered later

Shopify’s considerations page is plain about where responsibility sits. Once you approve a tool, the data leaves Shopify and is governed by the tool provider’s terms. Monitoring your store for changes is your job.

Four rules we use on client stores:

• Grant the minimum. Start read-only. A staff account is a login you create for one team member with its own permissions. Shopify says you cannot lower an access level you already approved. To reduce it, uninstall and install again.
• Approve every write on its own. Ask for the change as a list first. Apply it in a second message.
• Keep agents off live themes. A theme is the code that renders your storefront. Do theme work on a copy, preview it, and have a person publish.
• Confirm the store before any change. The connector works with one store at a time. Start a new conversation after you switch stores, because an old one can keep the earlier connection.

What the connector cannot touch

Per Shopify’s help pages, a connected tool can change an unpublished theme. It cannot edit, publish or delete a live one. It cannot change settings such as your plan, payments, taxes or domains. It cannot issue refunds, cancel or capture orders, process returns, or adjust gift cards, even if you approve write access. Orders are read only. Discounts are percentage-off and create only.

The connector also sees Shopify and nothing else. An answer about profit is incomplete unless you add ad spend, shipping and cost of goods yourself.

Run the read-only prompts this week

The connector is the door. The work behind it is a small set of repeatable jobs, not one clever prompt. Run the read-only prompts above this week, and read our Shopify Flow prompts guide for the jobs that belong in a fixed rule instead.

An assistant reading your admin sees what is in the admin. It cannot see how checkout behaves on a slow phone, or which app fires a tracker twice. Those findings sit on the storefront. Our Shopify operations work starts there.

Facts checked October 2026, re-check by 5 April 2027. Sources: Shopify connector for Claude on claude.com, Shopify help on third-party tools, Shopify AI Toolkit, Klaviyo MCP server.