Docs: System guides

Read Shopify into Maplith

The web shop's orders, payments, products with SKUs, inventory and customers, which tie the shop to payments, accounting, shipping and subscription apps.

Web shop · Also known as Shopify Plus, Shopify admin · Checked 2026-10-20

On this page

Best path

Recommended: your agent fetches it. Shopify makes its own connector for Claude and plugin for ChatGPT, so your agent can usually look at the shop's structure and recent orders with access it already has. For more than a few thousand orders, use the CSV exports instead, because Shopify has no MCP server that gives a merchant read access to the whole store.

Try the paths in this order:

Your agent fetches it, with the access you already gave it. Connectors a vendor or client page confirms: Shopify connector for Claude; Shopify plugin for ChatGPT. The agent checks which fields orders, products, customers and inventory carry and fetches a few recent months with the connector, approved for read access only. Shopify says a connected tool can read data but not change it unless you approve write access.
Maplith reads an MCP server you already run. No official MCP server confirmed. Shopify's own MCP servers are the Dev MCP (docs and API schemas for developers), the Storefront and UCP servers (catalog, cart and checkout for shoppers) and the Customer Accounts MCP (one signed-in customer's own orders), and none of them gives a merchant read access to all their orders, products and customers. Maplith reads a server that serves MCP resources and takes a token a person types under Data sources › Systems, such as one your IT runs for a database.
Export files, the fallback that always works. See the export steps below.

Datasets that make a good map

Dataset	One row is	Key columns	Joins to
Orders	One order line: the order, its status and totals, and one product line with quantity and price.	order id, order name (order number), line item SKU, customer email (Maplith tries to mask it), created date, financial status, fulfillment status	Accounting invoices and shipping labels by order number; Recharge charges by Shopify order id; payment provider charges through the order's transactions.
Transactions	One captured payment or refund on an order.	order name (order number), kind, gateway, status, amount, currency, created date	Shopify Payments payouts and other payment providers (Stripe, PayPal) by order and amount; bank lines and accounting by payout.
Products and variants	One product variant with its handle, SKU, price and inventory settings.	product handle, product id, variant id, variant SKU, vendor, product type	Warehouse and logistics stock by SKU; Recharge subscriptions by Shopify variant id; ad product feeds by SKU or variant id.
Customers	One customer account with order count, total spent, tags and marketing consent.	customer id, customer email (Maplith tries to mask it), tags, total orders, total spent	Recharge customers by Shopify customer id; email marketing and CRM contacts by customer email.
Inventory	Stock for one variant at one location.	variant SKU, location, available quantity	Warehouse and 3PL stock reports by SKU and location.

Columns are named, never their values. Maplith tries to mask personal data such as email addresses, but that is best effort: you decide what goes in.

Joins and identifiers the vendor documents

Shopify’s documentation states these keys. Maplith checks them against the exports you share: a stated join is not a confirmed one.

From	To	How many	Source
Orders, `customer_id`	Customers, `id`	many to one	shopify.dev

Identifier	Looks like	Source
Orders, `id`	`gid://shopify/Order/123`	shopify.dev
Customers, `id`	`gid://shopify/Customer/123`	shopify.dev

Structure files

Shopify can describe its structure without any rows. Share structure only: no examples, rows or credentials.

Shopify GraphQL type definitions (holds structure only): Have your agent retain the Order and Customer field/type definitions from the documented schema, with reference types and no examples, query results or credentials. Source: shopify.dev.

The access to give

Who usually has the rights: The store owner, or a staff member the owner has given app development permissions.

Choose the narrowest access that covers the data:

read_orders
read_all_orders
read_products
read_customers
read_inventory
read_locations
read_shopify_payments_payouts

Where to click:

Open the Dev Dashboard and go to Apps
Click Create app, then Start from Dev Dashboard
Type a name and click Create
On the Versions page, under Scopes, select only read scopes such as read_orders and read_products
Click Release
Click Install app and pick your store
Open App settings and copy the Client ID and Client secret from the Credentials card

A key or token made here stays in the tool that reads the system, never in a chat. Maplith asks for one only under Data sources › Systems in the app.

Export steps

Format: CSV Date range: Orders for the last three months; all products and all customers

In Shopify admin, go to Orders and click Export
Choose Orders by date, set the start and end dates, pick the CSV format and click Export orders
For payments only, click Export transaction histories in the same window
Go to Products, click Export, choose All products and click Export products
Go to Customers, click Export, choose All customers and click Export customers
Large exports arrive by email to you and the store owner

How much data

About 200–3,000 orders (more rows in the CSV, since it has one row per order line) a month (an estimate). Estimate for a small company, not a measured figure: a small web shop ships tens to around a hundred orders a day.

An agent that reads rows through a chat reads every one of them, about one token per four characters. Above a few thousand rows a dataset, or for a daily refresh, an MCP server or an export is the better path.

Always

Read-only, and never a credential sent to Maplith through a chat.
The same recent period, a few months, from every system.
You decide what goes in.

Sources

Written from public documentation, last checked 2026-10-20:

← All system guides · Markdown version · What your agents do with Shopify