Reconcile Shopify Sales With Xero Using AI
Shopify and Xero rarely agree. Three prompts that reconcile the gap, find refund and fee drag by product, and flag overdue customers.
Shopify's own MCP serves shopping agents, not merchants. Here's how to connect Shopify to Claude for reporting, and what syncs.
Shopify holds your orders, customers, products, fulfilments, refunds and returns. Claude can answer questions about all of it in natural language, but Shopify's own MCP server isn't the way to do that. This guide explains what Shopify's MCP is for, and walks through connecting Shopify to Claude for reporting using Tugger's built-in MCP server, so you can ask "what was net revenue by month after refunds" or "which products are selling faster than we can restock" and get an answer from your own store data.
If you've searched for a Shopify MCP server you'll have found Shopify's own, and it's worth being clear about what it does. Shopify's MCP is built for agentic commerce: it lets AI shopping assistants browse your catalogue, answer customer questions and complete a checkout on a customer's behalf. It is a storefront tool, pointed outward at buyers.
It does not give you, the merchant, a way to ask Claude about your sales, margins, customers or returns. For that you need your store's Admin data in a place Claude can query, which is a different problem and the one this guide solves.
Tugger syncs your Shopify Admin data on a schedule into a managed data warehouse, then exposes that warehouse to Claude through an MCP server. Claude queries the warehouse, never your store, so the connection is read-only and nothing Claude does can touch an order or a product.
Typical questions:
Claude writes the query, runs it against the warehouse and explains the result. You can follow up in the same conversation, ask for a chart, or ask Claude to compare two periods.
Once Shopify is connected, the two most useful first questions are about customers and cash. See Shopify customer retention analysis with AI for the repeat-purchase questions, and reconciling Shopify sales with Xero using AI for matching payouts to the ledger.
Tugger runs a first sync and then refreshes on a schedule. You can see sync status and history in the Tugger dashboard. If you run more than one store, repeat for each.
In any new chat, open the connectors menu and switch Tugger on. Claude can now see the tables Tugger has synced from Shopify.
"Show me net revenue by month for the last twelve months, after refunds, excluding cancelled and test orders."
That question is a good first test because it is the one most Shopify exports get wrong. Shopify's order total includes amounts that were later refunded, and test and cancelled orders sit in the same list. The warehouse carries the rule once, so Claude nets refunds off and excludes the noise every time, for whoever asks.
Tugger's Shopify connector syncs 42 tables through the Shopify GraphQL Admin API.
| Area | Tables |
|---|---|
| Orders | Orders, line items, non-fulfillable line items, shipping lines, discount applications and allocations, tax lines at order and line level, draft orders and draft line items |
| Payments | Transactions by gateway, transaction fees |
| Refunds and returns | Refunds, refund line items and transactions, returns, return line items with reasons, exchanges, reverse fulfilment orders |
| Fulfilment | Fulfilment orders and line items, fulfilments with tracking, fulfilment services, location moves |
| Products | Products, variants with SKUs and pricing, collections, product-collection membership, taxonomy categories, publications by sales channel |
| Customers | Customer records with addresses, marketing preferences and order statistics |
| Marketing | Marketing events and activities with channel, UTM and spend |
| Configuration | Locations, business entities, sales channels, event log |
Amounts are held in presentment currency, so if you sell in more than one currency Claude can report by currency or convert. If you need an entity that isn't listed, ask us.
Most product businesses on Shopify run their stock somewhere else, in Cin7, Unleashed or a similar system. Once both are in the Tugger warehouse, the questions that matter most become answerable in one go: which Shopify products are selling faster than stock on hand in Cin7 will cover, which SKUs have open Shopify orders against zero free stock, or how Shopify sales compare with wholesale sales out of the same inventory. No direct Shopify connector can see the other system; the warehouse can.
Several tools connect an AI assistant straight to the Shopify Admin API. That works for one-off lookups, but it has three drawbacks for reporting.
Tugger is UK-based and ISO 27001:2022 certified, and the warehouse runs on Azure in the UK by default or in any Azure region on request. The same warehouse also feeds Power BI and Tableau, and the MCP server works with Claude, ChatGPT and Gemini.
Connecting Shopify to Claude for reporting with Tugger takes no code and no faff. Try Tugger free for 10 days or book a demo and we'll walk through it with your own store data.
Don't just take our word for it.
It’s helped me keep my finger on the pulse of each department without having to be down in the trenches to get that pulse.
One of our customers wants a monthly evaluation pack built from thousands of Simpro jobs. It used to take a full day. Now our data reaches Claude through Tugger and the pack comes back in ten minutes, exactly how they want it.
Batch invoicing and reporting used to eat hours of admin time each week, chasing details back and forth between Simpro and our spreadsheets. Now it runs on its own, and because Tugger guides the AI to the right figures, I can trust what comes out.
Working with the AI agent through Tugger, blending Simpro, Xero and my other systems together, I came up with a really detailed, factual investigation.