Shopify’s Global Catalog REST API stops serving traffic on Nov. 2, according to a developer changelog posted Oct. 9, so anything still calling it will break.
Most store owners have never touched this endpoint, and that is exactly the problem. The people who call it are the apps and agent tools sitting between your products and your customers, and nobody tells you which of yours do. Here at Ecommerce Paradise I track the plumbing changes that quietly hit conversion, and this one lands three weeks before the holiday rush starts.
Below is what Shopify actually announced, why the move makes sense given where the platform is heading, and the short list of checks I would run before Nov. 2 arrives.
Every platform change is a reminder that you need a clean legal entity under your store before anything else breaks. If you have not yet formed your LLC, do it with Northwest Registered Agent, the best LLC formation service for ecommerce owners, because it puts its own address on your public filings instead of selling yours. Form your LLC with Northwest →
Shopify Will Stop Serving the Global Catalog REST API on Nov. 2
The announcement comes from Shopify’s developer changelog, which says the Global Catalog REST API stops serving traffic on Nov. 2, 2026. The post went up on Oct. 9. After that date, requests to the old endpoint are no longer answered, so any app, script, or agent that still depends on it needs to move before the cutoff.
The replacement is the Global Catalog MCP server. According to Shopify’s Catalog MCP documentation, it exposes three tools, search_catalog, lookup_catalog, and get_product, and callers identify themselves through a ucp-agent profile in the request metadata. MCP here means Model Context Protocol, the standard that lets AI agents call tools like a catalog search. The catalog tooling sits on top of what Shopify calls the Universal Commerce Protocol, which Shopify documents separately.
The changelog is written for developers, and it does not tell merchants to take any action. It also does not say how many apps or stores still call the REST endpoint. That gap matters, because the number of affected stores is the one figure that would tell you whether this is a footnote or a fire.
The timing fits a pattern of announcements over the past month. Shopify’s Oct. 6 post on agentic shopping for the holidays featured merchants including Stanley 1913 and Aviator Nation, which tells you the company wants AI agents shopping real stores before Black Friday. A week earlier, TechCrunch reported on Sep. 28 that Shopify opened checkout to browser-based AI agents. Greenberg put the motive plainly in that report: “Shopping with an agent shouldn’t feel like watching paint dry.”
Not everyone is rolling out the welcome mat. A second TechCrunch piece, published Oct. 6, found that sites including Amazon, Walmart, Delta, United, Yelp, eBay, and Zillow are blocking AI agents, and that Cloudflare changed its crawler defaults on Sep. 15. In the same piece Meta, which is pushing an open standard with a coalition of eight companies, said: “Turning away a personal agent means turning away the customer behind it.”
Then there is the measurement side. Practical Ecommerce published a guide on Oct. 11 explaining how to track ChatGPT traffic in GA4. Its core advice is to build a filter on traffic sources containing “gpt”, and it warns that visits arriving with a noreferrer attribute lose their source and show up as direct. If you have been wondering whether agent-driven traffic is real for your store, that caveat means your current reports probably undercount it.
Why Shopify Keeps Moving Its Catalog Behind MCP and UCP
None of this started on Oct. 9. Shopify laid out its agent commerce direction in its Jan. 11 post on AI commerce at scale, and the pieces have been landing since. I covered AI agents submitting orders on Shopify when that capability showed up.
Before that came the personal agent protocol between Shopify and Stripe, which I broke down in a separate post. The other Shopify changelog item that caught my eye this month, about compare-at prices and agents, points the same direction: agents read your catalog directly, so catalog structure is now a sales channel.
Retiring a REST endpoint in favor of MCP is the boring version of that strategy. A REST API answers a developer who wrote code against it. An MCP server answers an agent that discovered it, asked what tools exist, and called them with an identity attached. Shopify is consolidating on the second model and shutting the first one down rather than maintaining two doors into the same catalog.
Here is the counterpoint, and it is a real one. For a typical Shopify store selling a few hundred products, this deprecation changes nothing today. Nothing in the changelog says the REST endpoint powers the standard admin, themes, or checkout. If your apps are all mainstream and maintained, your vendors have probably handled the migration already, and Nov. 2 will pass without you noticing. A hard shutdown date on a developer endpoint is common, and most of them are non-events for merchants.
What makes this one worth a post is the combination of the date and the use case. The endpoint exists to let software search a catalog across stores. That is precisely the kind of software that will see more demand this holiday season, so a quiet break there costs more in Q4 than it would have in March.
What a Dead Catalog Endpoint Means for Your Apps and Agent Traffic
My read is that this shutdown is a dependency audit disguised as a deprecation notice. You do not need to learn MCP. You need to find out who in your stack does.
I sort the risk into three buckets. The first is third-party apps, anything that reads your product data to recommend, sync, search, or advertise. Ask every vendor that touches your catalog whether any part of their product calls the Global Catalog REST API. That means your email platform, such as Klaviyo.
Do the same for your support desk, such as Gorgias. Then check your post-purchase tracking tool, such as AfterShip. Most vendors will say no. The one that says “let me check” is the one to watch.
The second bucket is custom code. If a freelancer ever built you a feed, a product finder, or an internal agent that queries catalog data, that code may still point at the old endpoint, and the person who wrote it may be long gone. This is the bucket that bites, because nobody owns it. I would have the current developer or agency search the codebase for the endpoint this week. If you want a faster first pass, I would paste the integration list into Claude and have it draft the vendor email for you.
The third bucket is the one with upside. Agents that find your products through the catalog server are reading your titles, specs, and prices exactly as they sit in Shopify. Messy data costs you there the same way it costs you on shopping ads, and I have written before about how fast-changing prices can get products disapproved. For a high-ticket store, where the buyer is comparing a few serious options, a clean spec sheet and a stable price are the whole game. If you are still choosing what to sell, my guide to what high-ticket dropshipping is explains why these margins reward careful catalog work.
There is also a people problem hiding in this. Whoever installed your apps two years ago may not be the person reading vendor emails today. I would assign one named owner for the integration list before Nov. 2, even if that owner is you with a calendar reminder. A deadline with no owner is how a Tuesday-morning outage turns into a week of lost orders, and the cheapest fix is a single recurring line item on someone’s schedule.
Now a quick sense of scale. This is a hypothetical, not data from any store. Say a store does $50,000 a month, which is about $1,667 a day, and a broken recommendation widget costs it 2 percent of orders. That is roughly $33 a day. If it takes 10 days to notice and fix, the loss is about $330. Annoying, not fatal. The same bug in the middle of the holiday peak, with volume well above that baseline and carrier surcharges already squeezing margin, costs more, and the real damage is that you find out from a customer instead of a dashboard.
This is also where the operator tax shows up. Every store runs on a stack of integrations that someone has to watch, and deprecation notices like this one are why. If you would rather not own that upkeep, that is the argument for a done-for-you turnkey store, where my team builds and runs the store while you run the business.
Already have a store and a pile of apps you do not fully trust? Want my team to scale the store you already have, with the plumbing watched while you focus on growth? See the scaling service →
Five Checks to Run Before Nov. 2
This is what I would do, in this order, and it should take an afternoon plus a few emails.
- List every app and integration that reads your product data. Open your Shopify admin, go through the installed apps, and add anything a developer connected by hand. Email each vendor one question: does your product call the Global Catalog REST API, and if so, when do you move to the MCP server? Get the answer in writing before the end of next week.
- Have your developer search the code. Any custom feed, product finder, or agent that queries catalog data should be checked for the old endpoint. If you do not have a developer on call, this is a sign you need one on retainer before Q4, not after.
- Set up AI referral tracking in GA4. Follow the Practical Ecommerce method and filter sources for “gpt”, then compare it against your direct traffic and remember that noreferrer visits hide their origin. Even rough numbers will tell you whether agent traffic deserves a budget line, and my measured cost of a ChatGPT ad click gives you a price to compare it to.
- Clean your product data. Make sure every high-ticket listing has a complete title, specs, and one stable price, and check that compare-at prices follow the logic I described in my agents and compare-at prices breakdown. A visibility tracker such as Semrush can show you where your pages appear while you work.
- Set a change freeze for peak season. Pick a date in mid-November, finish all migrations before it, and write down who to call if something breaks. If you want a second set of eyes on the plan, Explore Turnkey Builds and we will go through the stack together.
One more habit worth building: read the Shopify developer changelog once a month. It is dry, but it is where these dates appear first, and it costs you ten minutes. Compare that with finding out on Nov. 2 that a widget quietly died.
Frequently Asked Questions
Does the Global Catalog REST API shutdown affect my Shopify store directly?
Only if you, an app, or a developer you hired calls it. The changelog is written for developers and does not tell merchants to take action. I have not seen Shopify publish how many stores or apps still use the endpoint, so the safe move is to ask your vendors rather than assume.
What replaces the Global Catalog REST API?
The Global Catalog MCP server, which exposes search_catalog, lookup_catalog, and get_product tools, per Shopify’s documentation. Google has a parallel effort, and I covered Google’s UCP hub in Merchant Center if you sell through shopping ads.
How do I know if ChatGPT or other AI agents send me traffic?
Filter GA4 sources for “gpt”, as Practical Ecommerce recommends, and treat the result as a floor. Visits that arrive with a noreferrer attribute are logged as direct, so real agent traffic is likely higher than what you see.
Should I block AI agents from my store?
Big retailers like Amazon and Walmart are blocking them, per TechCrunch, while Shopify is opening checkout to them. My read is that high-ticket stores should stay open and measure, but that is a judgment call, and it is not risk-free. I covered a Shop Pay AI checkout security bug that shows why you should watch what agents can do on your site.
I am just starting out. Does any of this matter yet?
It matters for the platform you choose, not the first week you launch. Start with a niche that has real margin, and my high-ticket niches list is the place to begin. You can grab the free niches list too.
When should I ask my vendors about the migration?
This week. Nov. 2 is the cutoff, but vendors that need to rebuild an integration will be slammed by holiday support volume in November, and the ones that wait until the last two weeks will answer slowly or not at all. An early written answer gives you time to switch tools if you have to.
Is MCP the same as UCP?
No. MCP is the protocol agents use to call tools, and UCP is Shopify’s Universal Commerce Protocol for commerce actions. The catalog server uses both, according to Shopify’s docs. For the email side of the stack, see my guide to ecommerce email marketing flows.
Not sure which parts of the stack are worth your attention before Q4? Want 1-on-1 coaching to launch or fix your high-ticket store? Get the coaching details →
I will keep an eye on what Shopify and the app vendors say about this, and if the number of affected stores ever gets published, I will tell you. Until then, spend the afternoon on the audit. Subscribe to the YouTube channel for daily breakdowns. More breaking news coming through the day.
Related Articles
If this was useful, these go deeper:
- How Meta Muse shopping treats known merchants
- Google’s direct offer asset in AI Mode
- ChatGPT ads and bulk product campaigns
- Using Claude to build a leaner high-ticket business
- The best AI tools for small business
Trevor Fenner is an ecommerce entrepreneur and world traveler from Seattle, Washington, and the founder of Ecommerce Paradise, a platform focused on helping entrepreneurs build and scale profitable high-ticket ecommerce and dropshipping businesses. With over a decade of hands-on experience, Trevor specializes in high-ticket dropshipping strategy, niche and product selection, supplier recruiting and onboarding, Google & Bing Shopping ads, ecommerce SEO, and systems-driven automation and scaling. Through Ecommerce Paradise, he provides free education via in-depth guides like How to Start High-Ticket Dropshipping, advanced training through the High-Ticket Dropshipping Masterclass, and fully done-for-you turnkey ecommerce services for entrepreneurs who want a faster, more hands-off path to growth. Trevor is known for emphasizing sustainable, real-world ecommerce models over hype-driven tactics, helping store owners build scalable, sellable, and location-independent brands.
He maintains homes in Seattle and Bali, spends most of the year overseas, and usually returns to Seattle for about a month each summer.
