To connect Shopify to ChatGPT:
- Sign up free at portermetrics.com and connect your Shopify account with your Shopify account.
- In ChatGPT, click + → Connectors → Manage connectors → Add custom connector, name it Porter, paste
https://mcp.portermetrics.com/mcp, then click Add and authenticate with Google.
That’s it, you’re connected. Porter’s free plan covers up to 3 Shopify stores with no usage limits on ChatGPT’s free plan. No credit card required.
What makes Porter different:
- 155+ Shopify metrics and dimensions, across every reporting level in one connection.
- Universal Shopify MCP. Blend Shopify with Meta Ads, Google Ads, GA4, HubSpot, Klaviyo and 20+ more sources in one chat. Build white-label dashboards, automate alerts, and generate client reports. Your whole Shopify operation runs from one chat.
Prerequisites
- A Porter Metrics account with your Shopify account connected (free tier is enough to try it end-to-end)
- A ChatGPT account — the free plan works for ChatGPT Web; a Pro subscription is needed for Codex and Desktop MCP features
- Admin or standard access to the Shopify stores you want to connect
Connect Shopify to ChatGPT with MCP
For this tutorial we’re going with the MCP method. Here’s a quick explainer of what MCP is and why it’s the best path for Shopify.
MCP (Model Context Protocol) is the open standard that lets AI tools like Claude, ChatGPT, Codex and others access and use external APIs — the things that make tools like Shopify work under the hood. Instead of building a custom integration for every AI tool you use, you install one MCP and every compatible AI gets access to the same data.
The full setup takes under 5 minutes and breaks into three moves: connect Shopify to Porter, point ChatGPT at the Porter MCP, and ask your first question.
1. Connect your Shopify data to Porter
Porter sits between Shopify’s Admin API and ChatGPT. It handles OAuth, rate limiting, pagination and all the plumbing so ChatGPT only ever sees clean, structured data.
Sign up for Porter. Create a free account at portermetrics.com. The free tier is enough to run this full workflow end-to-end.
Connect your Shopify. In Porter, click Create → pick ChatGPT as the destination → select Shopify as the source → sign in with Shopify to grant access to your stores.
Select your stores. Choose the Shopify stores you want ChatGPT to query. When you select multiple stores under a single connection, Porter automatically blends their data together so you can query them as one.
Optional: enable automatic BigQuery storage if you’re connecting multiple stores with large data volumes. This keeps ChatGPT’s responses fast even at scale.
2. Connect the MCP to ChatGPT
Porter’s MCP URL is what you paste into ChatGPT. Once added, ChatGPT can query Shopify data on demand in any conversation.
Go to chatgpt.com and click the + icon in the chat input to open the tools menu.
In the menu that opens, hover over Connectors and click Manage connectors.
In the Connectors panel, click the + button at the top of the list to start adding a new connector.
Pick Add custom connector from the dropdown that appears.
A dialog opens with the name and URL fields. Type Porter in the first field to name the connector.
In the second field, paste https://mcp.portermetrics.com/mcp. Leave the advanced settings alone.
Click Add at the bottom right of the dialog. ChatGPT opens a sign-in window — use the same Google account linked to your Porter workspace and approve access.
Once the authorization finishes, you’ll see Porter’s tools appear in the connectors panel. You’re ready to start asking questions.
For a fuller walkthrough with screenshots at every step, see the Porter MCP tutorial.
3. Start building questions and dashboards
With Porter connected, open a new ChatGPT chat and ask anything about your Shopify in plain English. ChatGPT calls Porter behind the scenes, pulls live data from Shopify, and answers with tables, charts, or summaries.
Try one of these to verify the setup is working:
For a full catalogue of copy-paste prompts organized by use case (agencies, DTC brands, e-commerce teams, cross-channel), jump to the prompts section below.
Alternative ways to connect Shopify to ChatGPT
Porter MCP is the path we just walked through and the one we recommend for most marketers. It is not the only way to get Shopify data in front of ChatGPT, though. The most common alternatives are Shopify’s direct API, a live Google Sheets bridge or CSV upload, and BigQuery for scale. Each has trade-offs, so pick the one that fits how your team already works.
- 🔌 Shopify’s direct API — Talk to Shopify’s Admin API yourself. Maximum control, but you handle auth, rate limits and pagination — and you only get one source. (Shopify doesn’t ship an official MCP yet.)
- 📊 Google Sheets — Live Sheet or one-off CSV upload. Auditable, familiar, faster for big exports — but aggregation happens in the Sheet, not the API.
- 🗄️ Google BigQuery — For large stores or agencies running multi-store analysis. BigQuery aggregates; ChatGPT only queries pre-built summaries.
Via the Porter Metrics app in the ChatGPT marketplace
If you’d rather not paste a connector URL, install Porter straight from ChatGPT’s app gallery — it’s the same Porter connection behind the scenes, published as an approved ChatGPT app:
- Open the Porter Metrics app page in ChatGPT (or search “Porter Metrics” in the apps gallery).
- Click Connect and sign in with the same account you use in Porter.
- Authorize it and ask your first Shopify question — same live data as the MCP.
The trade-off to know: the marketplace app only updates after each ChatGPT review cycle, while the MCP updates the moment Porter ships. If you want every new tool and data source immediately, use the MCP; if you want the one-click install and don’t mind waiting for new features, the marketplace app is the shortest path — including write actions through your connected Porter account.
Via Shopify’s direct API
If you’re building a product around Shopify — or you’re a developer who’d rather own every layer of the integration — the most direct path is talking to Shopify’s Admin API yourself, or — where it exists — Shopify’s own official MCP. Shopify doesn’t ship an official, unified MCP as of June 2026. Shopify’s first-party MCP infrastructure is fragmented by surface (Storefront, Customer Account, Checkout, Dev) — each scoped to a single function, not general store data. Whichever route you pick, you still follow Shopify’s rate limits & quotas. Either way you skip Porter and call Shopify from your own code, from Codex, or from Shopify’s own connector.
The trade-off to know. Going direct gives you maximum control and the freshest possible data — every endpoint, every parameter, no abstraction layer in between. But you’re now responsible for OAuth flows, refresh tokens, rate limits, pagination, schema changes, and error retries. And critically, you only get one source. The moment you also want Google Ads, GA4 or HubSpot in the same conversation, you’re back to building (or stitching together) more integrations.
When this makes sense: engineering teams that need a single source with full control, products that ship Shopify data as a feature (where you own the integration anyway), or one-off scripts where you don’t mind writing the auth and pagination code yourself. For marketers who want to ask questions in plain English and blend Shopify with the rest of their stack in a single conversation, the Porter MCP path is dramatically less work.
Via Google Sheets (live Sheet or manual CSV)
If your team already lives in Google Sheets — or you want a paper trail before ChatGPT touches anything — feed Shopify into a Sheet, then let ChatGPT read the Sheet. You can automate the Shopify → Sheets pipeline with Porter so it refreshes daily, or do one-off CSV exports from Shopify’s native admin for static analysis.
The trade-off to know. With the MCP path, ChatGPT calls Shopify’s API directly and Shopify does the filtering and aggregation on its side — clean and deterministic. With the Sheets path, ChatGPT aggregates inside the Sheet itself, which can introduce hallucinations on totals, averages, and joins when you have thousands of rows. The upside is speed: for very large date ranges or historical analysis, a pre-built Sheet is dramatically faster than live API calls.
When this makes sense: finance teams that want to review numbers before ChatGPT acts on them, agencies already delivering client reports in Sheets, historical analysis across years of data, or any case where you care more about speed than real-time freshness.
Read the full Sheets tutorial →
Via Google BigQuery (for scale)
This is the path most people overlook — and it’s the one that saves you when your Shopify store gets serious. A single large merchant or an agency managing 10+ stores will hit API rate limits and latency problems querying ChatGPT directly. ChatGPT will literally tell you it’s taking too long or timing out on big pulls.
BigQuery fixes that. You load Shopify data into BigQuery tables on a schedule, then connect BigQuery to ChatGPT — either through a BigQuery MCP or via Codex with SQL queries. Instead of asking ChatGPT to pull raw Shopify data, you let BigQuery aggregate into small, optimized tables, and ChatGPT only queries the summarized output. Scale problem solved.
When this makes sense: enterprise stores with thousands of orders, agencies running multi-store analysis across 10+ clients, or any team already using BigQuery as a data warehouse. Porter loads Shopify (and 25+ other sources) directly into BigQuery so you don’t have to build your own ETL.
Read the full BigQuery tutorial →
Connecting Shopify to Codex
Most marketers lump ChatGPT and Codex together and miss the biggest advantage of the entire MCP ecosystem. They’re not the same tool — and the difference matters enormously once you start working with Shopify data seriously.
ChatGPT is a chat interface. You ask a question, ChatGPT pulls live data through the MCP, answers, maybe builds a quick dashboard inside the conversation. Great for one-off analysis. The problem: everything is ephemeral. Want to refresh the dashboard tomorrow? You regenerate it from scratch. Want the same report every Monday? You re-ask the question every Monday.
Codex is ChatGPT running inside your computer’s terminal. Because it has access to your filesystem, runtime, and other developer tools, it doesn’t just answer questions — it can build real software. Persistent scripts, scheduled routines, HTML apps, internal dashboards, integrations that run 24/7 without your input. Once it’s connected to Porter’s MCP for Shopify, a whole category of work becomes possible.
What Codex unlocks that ChatGPT alone cannot
This is where the MCP ecosystem pays off most. Because Codex can combine Porter’s MCP with other MCPs — Firecrawl for web scraping, Airtable for structured data, Notion for wikis, Vercel for deployment, Slack and Gmail for delivery — you’re no longer querying data. You’re building tools.
Feed Codex your Shopify targets and goals — AOV targets, inventory thresholds, sales goals — and ask it to generate a custom revenue dashboard for each client. It builds the HTML, pulls live data, deploys to a URL. No Data Studio embed to break when the vendor changes pricing, no template constraints. The dashboard updates automatically because it queries Porter’s MCP on every page load.
Best for:agencies that want white-label client dashboards without Looker or Data Studio dependencies.
Combine your own Shopify performance from Porter with competitor product catalogs and pricing scraped via Firecrawl. Codex stitches both into a weekly competitive intelligence report — your numbers next to their product assortment and pricing strategy, with an LLM summary on top of what changed week over week. Runs on cron, lands in your inbox every Monday morning.
Best for:in-house teams that need market context, not just internal numbers.
Use Airtable or Notion as the schema, Porter as the data source. Codex keeps every page populated with current Gross Sales, Net Sales, and Orders for every store — no stale screenshots, no copy-paste from Excel. New hires read one wiki entry and have full context on a client’s account.
Best for:agencies and ops teams onboarding analysts or rotating account managers frequently.
A Codex routine on cron pulls Shopify via Porter, evaluates thresholds — inventory drops below 10 units, daily sales drop 20% below trailing average — and pushes Slack or Gmail alerts the moment something crosses the line. You stop checking dashboards reactively; the dashboard checks itself and tells you when to look.
Best for:any team that’s ever discovered a problem 48 hours too late because nobody opened the report.
Bottom line: ChatGPT is for quick questions and ad-hoc dashboards. Codex is for building apps, live dashboards, alerts, and actual tools — anything you want to run on its own without re-asking. Same Porter MCP URL works in both, so you don’t pick once and lock in.
Use cases: what you can actually do once Shopify is connected to ChatGPT
Getting the connection right is half the battle. The real value shows up in what you do next. Here are the use cases Porter users build around their Shopify data — from simple Q&A to full client-facing workflows.
1. Chat and ask questions directly
The simplest use case — and still the one 80% of marketers start with. Open ChatGPT, ask a question, get an answer grounded in live data.
It’s the fastest way to replace a daily Shopify admin check-in. But chat is table stakes — the interesting use cases come next.
2. Blend Shopify with your revenue data (Meta Ads, Google Ads, Klaviyo)
This is where a 360° view gets real. When you connect Shopify and your revenue source (Meta Ads for paid acquisition, Google Ads for search campaigns, Klaviyo for email marketing), ChatGPT can map orders and products to actual purchases and revenue — using UTMs, order timestamps, and customer IDs — and give you attribution that no platform-side number can.
ChatGPT handles the UTMs, order timestamps, and customer IDs mapping and joins. You get a client-ready attribution report that no single platform can generate on its own.
3. Automated alerts and notifications on Slack or Gmail
With Codex you can turn Shopify monitoring into a routine that runs on its own. Hook Porter’s MCP (for the data) together with a Slack or Gmail MCP (for delivery), then write a Codex scheduled task that pulls performance every morning and pings you only when something actually needs attention.
No dashboards, no daily check-ins. The report comes to you — and only when it matters.
4. Client-ready presentations with live data (Gamma, HTML, PDF)
A common agency pain: you send clients a Shopify admin report export — and you spend an hour explaining a broken dashboard. With ChatGPT you can build the presentation itself — as a Gamma deck, a custom HTML page, or a PDF — populated with live numbers each time.
The presentation becomes a delivery artifact you send to the client, not a dashboard that depends on another tool staying up. No broken iframe, no login prompts, just the content.
Shopify fields and metrics you can query with ChatGPT
Before you start writing prompts, it helps to know what data is actually available. Porter MCP gives ChatGPT access to 155 Shopify fields and metrics across every reporting level, plus breakdowns by date, product type, customer segment, and channel. And the same MCP URL also unlocks 25+ other sources — so ChatGPT can blend Shopify with Google Ads, GA4, HubSpot and more in a single prompt.
Prompts you can copy-paste today
These prompts are organized by job: agencies, DTC brands & wholesale, e-commerce teams, and cross-channel blends.
1. For agencies
Use these when managing multiple Shopify clients or building rollup reports.
2. For DTC brands & wholesale
Use these for product performance, inventory, and customer segmentation.
3. For e-commerce teams
Use these for daily operations, trend analysis, and forecasting.
4. Cross-channel
Use these when blending Shopify with ad platforms, email tools, and analytics.
Limits, safety, and best practices for Shopify via ChatGPT
This is relevant for any marketer running time-sensitive campaigns (flash sales, product drops, holiday promotions) where real-time inventory accuracy is critical. The cost isn’t a ban — it’s overselling, customer service overhead, and potential chargebacks. Shopify’s rate limits are generous but bursty traffic during campaigns can exhaust the leaky bucket, causing sync delays that break automated workflows.
Shopify’s rate limiting is quota-based and pattern-based, not tool-based. Shopify doesn’t ban accounts because you used ChatGPT or an MCP. It throttles because of how the API was used: exceeding the leaky bucket rate limit (2 requests/second for standard plans), GraphQL query cost over 1,000 points, or sustained burst traffic above the allocated capacity. Read-only operations within quota are safe. Bursty write traffic, unoptimized GraphQL queries, and sustained high-frequency polling are not.
The two ways to burn through your Shopify quota
After reviewing official docs and community threads, two patterns come up again and again.
1. Unoptimized GraphQL queries exceeding cost limits. Shopify’s GraphQL API uses a points-based system where each field has a cost. Complex nested queries can hit the 1,000-point max cost per query quickly, causing throttling or query rejection. This triggers enforcement because Shopify’s system calculates query cost before execution and rejects expensive queries. Official docs: Shopify GraphQL Admin API rate limits. Instead, break complex queries into smaller, targeted requests and use pagination.
2. Sustained high-frequency polling for real-time data. Polling order status or inventory every few seconds burns through the leaky bucket (2 req/s standard, 4 req/s Advanced, 10 req/s Plus). When the bucket empties, requests get 429 errors and sync delays cascade. This is especially dangerous during flash sales when inventory accuracy is critical. Shopify REST API rate limits. Instead, use webhooks for real-time updates and poll only as fallback with exponential backoff.
3. Ignoring 429 responses and retrying immediately. When throttled, Shopify returns a 429 status with a Retry-After header. Immediate retries without respecting this header waste quota and extend the throttle period. This pattern can trigger longer-term rate limit enforcement. Shopify API status codes documentation. Instead, implement exponential backoff and respect the Retry-After header value.
Both behaviors trigger rate throttling. If you want to use ChatGPT for Shopify safely, respect the leaky bucket, optimize your queries, and use webhooks instead of polling.
The 5-rule scaling protocol
Based on Shopify’s documented rate limits and quotas and the behaviors that have actually caused throttling — not guesswork:
-
Respect the leaky bucket rate limit. Standard Shopify plans allow 2 requests/second with a burst capacity of 40 requests. Advanced plans get 4 req/s, Plus plans get 10 req/s. Shopify REST API rate limits. Exceeding this triggers 429 errors and sync delays. Porter MCP enforces this with built-in request throttling and automatic backoff.
-
Keep GraphQL query cost under 1,000 points. Shopify calculates query cost before execution and rejects queries exceeding 1,000 points. Shopify GraphQL rate limits. Complex nested queries burn points fast. Porter MCP optimizes query structure to stay well under this threshold.
-
Use webhooks instead of polling for real-time data. Polling every 5 seconds consumes 12 req/min — 720 req/hour — just for one data stream. Webhooks push updates instantly with zero API quota consumption. Shopify webhooks documentation. Porter MCP configures webhooks automatically where supported.
-
Implement exponential backoff on 429 errors. Shopify returns
Retry-Afterheaders on throttle. Immediate retries without backoff extend the throttle period. Shopify API status codes documentation. Porter MCP handles this automatically with progressive backoff intervals. -
Cache product/catalog data with TTL matching business needs. Product descriptions, images, and catalog structure change infrequently. Caching for 1-5 minutes reduces API calls by 80%+ during reporting workflows. Shopify API usage best practices. Porter MCP caches aggressively and refreshes on webhook triggers.
What Porter MCP does differently: it enforces these limits and safeguards at the platform level. Porter uses read-only API scopes by default, implements leaky-bucket-aware request scheduling with automatic backoff, batches related queries into optimized GraphQL requests, configures webhooks for real-time updates instead of polling, and caches catalog data with intelligent TTL. That’s the behavior Shopify’s automated systems handle gracefully and don’t flag.
Frequently asked questions
Ready to chat with your Shopify?
Open ChatGPT, add the Porter connector, and ask your first question. If you don’t have Porter yet, start a free trial and connect your Shopify account — you’ll be chatting with your campaigns in under five minutes.
rocket_launchStart free Porter trialopen_in_newOpen ChatGPT