Shopify Analytics will tell you what sold. It is much worse at telling you why, what to do about it, and what would have happened if you had not run that discount. Connected to your orders, Claude answers the questions you would ask an analyst, in the time it takes to type them.
The Shopify connector gives Claude the orders, products, variants, inventory levels and discount codes your scopes allow. For sales analysis the orders scope is the important one: every order with its line items, prices, discounts, shipping, fulfillment status, channel and country.
Customer records are a separate scope, and the setup guide suggests leaving it out. You lose nothing for analysis. Repeat-purchase behavior can be worked out from orders without names, emails or addresses ever leaving Shopify, and that is the version this guide uses.
Money in your currency: the figures in this guide follow the currency switch at the top of the site. Claude reports in whatever your store settles in.
Start broad and let the answers point at the next question. These five cover most of what a store owner wants to know on a Monday.
Expect the shape of a real answer: sales are up, but the rise is two products and one channel; four products have not sold in 60 days; a third of orders come from one country you do not ship to cheaply. Each of those is a next question.
Average order value is the number most easily moved by a product decision rather than a marketing one. Ask Claude which products are bought together, and which products appear alone in orders that are just under your free-shipping threshold. The first list is your bundle. The second is the add-on you should suggest at the cart.
A roaster who learns that a 12 oz bag plus filters is the most common pairing, and that most $32 orders are one bag of the house espresso, has two changes to make that afternoon: a bundle, and a filter prompt on that product page. Both are things Claude can then build.
Shopify marks orders from a returning buyer. Claude can group on that flag without ever reading who the buyer is. The questions that matter: what share of orders are repeats, how long between first and second order, and which first product leads to the most second orders.
That last one is the quietly valuable answer. The product that creates repeat customers is the one to put in front of new visitors, even if it is not the best seller.
Every store has a code that was meant for new customers and is being used by old ones, or a free-shipping rule that fires on orders that would have shipped anyway. Claude can find both from orders alone.
The fix is usually a rule change in the discount settings. Claude can make it, or tell you exactly what to click.
Pair sales velocity with inventory levels and you get a reorder list instead of a stock list. Tell Claude your supplier lead time and it will tell you what runs out before the next delivery arrives.
Dashboards get ignored because they show everything. A report gets read because it says five things. Have Claude write it, in the same shape each week, and send it to you.
In Claude CMS that is a Swarm task: it runs on the schedule, reads the store through the connector and sends the email from your own address. If a week is ordinary, the report says so in two lines.
Analysis is only worth doing when it ends in a change, and the connector that read the orders can also make most of the changes: create the bundle as a product, add the add-on suggestion to a product page, tighten the discount rule, update a collection, write the landing page for the product that creates repeat buyers.
Keep the two steps separate. Ask the question, read the answer, then say what to change. Claude does not alter the store because of something it noticed; it alters the store because you told it to.
Does Claude need access to my customers?
No. Everything here works from orders, products and inventory. Leave the customer scopes off when you install the app and repeat-buyer analysis still works, using the flag Shopify puts on each order.
How far back can it look?
As far as your order history goes. Large stores with years of orders are read in pages; a 90-day question answers in under a minute, a five-year one takes a few.
Can it compare with last year?
Yes. Ask for the same period a year earlier and it reads both ranges.
Will it make changes to the store on its own?
No. It reads when you ask a question and writes only when you ask for a change. Scheduled reports are read-only unless you tell the task otherwise.
Every guide on this page assumes one thing: your store is connected. That is a one-time job of about fifteen minutes, covered step by step in Connect your Shopify store, or one click from the Connections tab if you already have a Claude CMS account. After that, this guide is a conversation.
Step-by-step guides, each one a conversation with Claude: SEO, sales analysis, landing pages, a redesign, and everyday edits.
Titles, meta descriptions, alt text, collections and internal links, written and kept current from a conversation.
Read the guide →
A campaign page from a brief, in your theme, pushed unpublished, previewed, then published and linked.
Read the guide →
Duplicate the theme, work in passes, preview every pass, publish when it is right, roll back if it is not.
Read the guide →
The six-step loop: clone a page locally, preview it, iterate, pick the unit, push, verify, link.
Read the guide →
