News and analysis
Shopify Catalog: verify the integration before 2 November
Global Catalog REST will stop serving traffic, while responses add optional list_price. Preserve search and context-aware price display.
The catalog works today, but its integration may rely on an API with a scheduled shutdown. A response also gains an additional price field. Two Shopify updates dated 9 October deserve consideration together: changing how data is retrieved should preserve what a product card means for the actual buyer.
Establish which API is in use
Shopify announced that Global Catalog REST API will stop serving traffic on 2 November 2026. As of 13 October, the date is still ahead. The migration route is Global Catalog MCP, implementing UCP with tools for search and product lookup. This concerns a specific catalog API, not the shutdown of every Shopify API.
The team’s first step is to find real calls in the old integration. Search, individual product details and batch lookup may sit in different parts of the product. Replacing an address alone is insufficient when request and response contracts change. Assign an owner to each path and verify it in a separate environment before the deadline.
An additional price depends on context
In its second update, Shopify describes list_price as an optional product-variant field for compare-at prices. Its presence depends on merchant settings and the buyer’s regional context. The object contains an amount in minor currency units and a currency; price remains unchanged.
Do not treat a missing list_price as a failure or invent a crossed-out price. The interface should reflect the available response. Before displaying a markdown, establish that both values refer to the same context and are converted correctly for presentation.
Connect migration with the product-card check
The comparison suggests testing not only a successful network response, but also what the buyer sees from it. A protocol migration may preserve search while leaving an old assumption about the data structure in an interface or agent response.
Prepare checks for search, variant selection and a product without an additional price. Repeat them for supported regional conditions. Compare the product identifier, availability, currency and displayed values. If the application uses a saved catalog, verify that route as well as new search.
Finish with an inspectable result
Keep an inventory of migrated consumers and verification for each journey. After switching, establish that logs no longer show calls to the retired route. The action plan should account for 2 November without describing the existing integration as already unavailable.
Our first customer-portal release guide helps select acceptance scenarios. The archived custom API design discusses contracts without claiming this migration as our work. For your API integration, discuss catalog consumers and price-display conditions.