Shopify Global Catalog REST API Retirement: A Developer’s Checklist for November 2, 2026
Shopify will retire the Global Catalog REST API on November 2, 2026. From that day, requests to discover.shopifyapps.com/global will fail, saved catalog calls included. Shopify’s notice mentions no grace period or fallback.
What is being retired?
The Global Catalog lets apps search and fetch product data across many Shopify merchants, not just one store. Four REST endpoints go offline: /global/v2/search, /global/v2/p/{upid}, /global/v2/p/by-variant/{vid}, and /global/v2/lookup.
What replaces it?
The Global Catalog MCP at catalog.shopify.com/api/ucp/mcp, built on Shopify’s Universal Commerce Protocol (UCP). This is not a GraphQL migration. Teams planning a GraphQL Admin API rewrite for this API are aiming at the wrong target.
How do the endpoints map to the new tools?
search becomes search_catalog
What changes in your code?
Every request now needs an agent profile.
Where does migration usually fail?
Not in the endpoint swap, which is small. It fails in two places:
Hidden callers. Outdated app versions, agency scripts, middleware wrappers and third-party App Store apps can all still call the old endpoint. Search your repos and outbound logs, and get written confirmation from every vendor.
Downstream data. If catalog data flows into ERP pricing, stock or orders, a renamed or re-nested field can break those flows days after cutover.
How should you cut over?
Run old and new calls side by side on identical inputs and compare the outputs. Use the Shopify AI Toolkit or the UCP CLI to test calls in isolation. Switch at least 48 hours before November 2, with a rollback plan ready.
Are Shopify-to-ERP integrations affected?
Integrations that run on Shopify’s Admin API, which only covers a merchant’s own store data, do not call the Global Catalog. appse ai connects Shopify and Shopify Plus to SAP Business One, Microsoft Dynamics 365 Business Central, and NetSuite through the Admin API, so its customers need no changes for this cutoff.
The full migration guide, with a week-by-week plan, is here:appse.ai
What is being retired?
The Global Catalog lets apps search and fetch product data across many Shopify merchants, not just one store. Four REST endpoints go offline: /global/v2/search, /global/v2/p/{upid}, /global/v2/p/by-variant/{vid}, and /global/v2/lookup.
What replaces it?
The Global Catalog MCP at catalog.shopify.com/api/ucp/mcp, built on Shopify’s Universal Commerce Protocol (UCP). This is not a GraphQL migration. Teams planning a GraphQL Admin API rewrite for this API are aiming at the wrong target.
How do the endpoints map to the new tools?
search becomes search_catalog
What changes in your code?
Every request now needs an agent profile.
Where does migration usually fail?
Not in the endpoint swap, which is small. It fails in two places:
Hidden callers. Outdated app versions, agency scripts, middleware wrappers and third-party App Store apps can all still call the old endpoint. Search your repos and outbound logs, and get written confirmation from every vendor.
Downstream data. If catalog data flows into ERP pricing, stock or orders, a renamed or re-nested field can break those flows days after cutover.
How should you cut over?
Run old and new calls side by side on identical inputs and compare the outputs. Use the Shopify AI Toolkit or the UCP CLI to test calls in isolation. Switch at least 48 hours before November 2, with a rollback plan ready.
Are Shopify-to-ERP integrations affected?
Integrations that run on Shopify’s Admin API, which only covers a merchant’s own store data, do not call the Global Catalog. appse ai connects Shopify and Shopify Plus to SAP Business One, Microsoft Dynamics 365 Business Central, and NetSuite through the Admin API, so its customers need no changes for this cutoff.
The full migration guide, with a week-by-week plan, is here:appse.ai
Fuente: Artículo original