← All vendor deprecations

Shopify deprecations and shutdown dates

Deprecations, shutdowns and breaking changes Shopify has announced, from its official changelogs and reviewed by the StackClock team.

Upcoming (3)

ShopifycriticalBreaking change

`abandonedCheckoutUrl` now requires level 2 protected customer data access

Takes effect 1 Dec 2026 · published 20 Nov 2026

Starting December 1, 2026 for public apps, and January 1, 2027 for custom apps, the abandoned checkout recovery URL requires approval for all four protected customer fields (name, email, phone, and address) on all supported Admin API versions and unstable . If your app reads AbandonedCheckout.abandonedCheckoutUrl or abandoned_checkout_url but doesn't need it, stop using the field. If your app needs it, request access before your date. This is a breaking change made for security reasons. Which apps and when | App | Date | How to get access | |

ShopifyhighBreaking change

Migrate to expiring offline access tokens before January 1, 2027

Takes effect 1 Jan 2027 · published 30 Oct 2026

Public apps still using non-expiring offline access tokens must migrate to use expiring offline access tokens before January 1, 2027 to remain listed in the Shopify App Store and continue accepting new installs. New client credentials access helps your backend recover access without waiting for a merchant to reopen your app. Using a request signed with your app's private key, your backend can obtain a fresh, short-lived access token without a refresh token. The enforcement timeline has been updated with incremental penalties for non-compliant apps: January 1, 2027: Non-compliant apps are delisted from the Shopify App Store and blocked from new installs. Existing installations can continue making affected API requests until April 1. January 15, 2027: Merchants using non-compliant apps see warnings in Shopify admin about the risk of service interruption and the action they can take. April 1, 2027: Affected Admin API requests using non-expiring offline access tokens return HTTP 403.

ShopifymediumDeprecation

Storefront MCP policies and FAQs tool is being deprecated in favor of UCP MCP Ask tool

Takes effect 15 Jan 2027 · published 16 Nov 2026

Storefront MCP search_shop_policies_and_faqs is deprecated. Migrate to UCP MCP's ask_business tool by January 15, 2027. What's changing The search_shop_policies_and_faqs tool on the Storefront MCP server ( https://{shop}.myshopify.com/api/mcp ) is deprecated in favor of the UCP Ask MCP tool. UCP MCP implements the UCP ask capability ( dev.ucp.common.ask ) and exposes the following tool at the https://{shop-domain}/api/ucp/mcp endpoint: ask_business : Answer a buyer's question about the store's policies and services, using the store's knowledge base and policies. The deprecated tool will be maintained until January 15, 2027, but all documentation will refer to Ask MCP. What you should do If you're building with search_shop_policies_and_faqs : Migrate calls to ask_business , and update endpoints to use https://{shop-domain}/api/ucp/mcp . Include a meta object carrying ucp-agent.profile in every request. Your agent profile must declare dev.ucp.common.ask . Send the question in a

Past and undated (12)

ShopifyhighDeprecation

Global Catalog REST API stops serving traffic on November 2, 2026

Takes effect 2 Nov 2026 · published 11 Oct 2026

The Global Catalog REST API, which was deprecated in April 2026, stops serving traffic on November 2, 2026. If your app still calls it, you need to migrate to Global Catalog MCP, which implements the Universal Commerce Protocol (UCP), before that date.

ShopifyhighBreaking change

Market.metafields matches keys in any case as of Storefront API version 2027-01

No date announced · published 16 Nov 2026

As of Storefront API version 2027-01 , the metafields field on the Market object matches each requested key in any case, as Market.metafield already does. This is a breaking change for apps and custom storefronts that request a market metafield key in a different case from the stored key, or that read a key that the buyer's markets store that differ by letter case. If your app does either, review its Market.metafields queries before you move it to 2027-01 . What changed In version 2027-01 , Market.metafields returns a metafield when the requested key matches the stored key in any case. In earlier versions, Market.metafields returns a metafield only when the requested key and the stored key have the same case. For example, a market stores a metafield with the namespace custom and the key colour : In version 2026-10 and earlier, the entry for { namespace: "custom", key: "Colour" } is null . In version 2027-01 , the entry returns the stored metafield. Who's affected The change appl

ShopifyhighBreaking change

currententrychange now returns the previous page in event.from for customer account full-page extensions

No date announced · published 6 Nov 2026

Starting in API version 2027-01 , in customer account full-page extensions the Navigation API currententrychange event sets event.from to the page the customer navigated away from, instead of the page they navigated to. This is a breaking change for customer account full-page extensions that read the new page from event.from . Update them to read shopify.navigation.currentEntry before you move them to 2027-01 . What changed In customer account full-page extensions ( customer-account.page.render and customer-account.order.page.render ), currententrychange passes a NavigationCurrentEntryChangeEvent whose from property is documented as the previous history entry. In API version 2026-10 and earlier, from is the new entry instead, the same value as shopify.navigation.currentEntry . Starting in 2027-01 , from is the previous entry. Who's affected Full-page extensions on API version 2027-01 or later that use event.from to find the page the customer navigated to are affected. Extensions o

ShopifyhighBreaking change

Gift Card line_item_id will become read-only in REST Admin API version 2027-01

No date announced · published 6 Nov 2026

In REST Admin API version 2027-01 and later, the line_item_id property on the Gift Card resource is read-only. Shopify ignores the property in create and update requests. Remove it from those requests before you upgrade. What changed In REST Admin API version 2027-01 and later, apps can't add, replace, or clear a gift card's line-item association through Gift Card create or update requests. Shopify ignores any line_item_id value in those requests. Gift Card responses still include existing line-item and order associations. Earlier API versions keep their current behavior. Who's affected This change affects you if all of the following are true: Your app uses the REST Admin API Gift Card resource. Your app includes line_item_id when it creates or updates gift cards. You plan to upgrade your app to API version 2027-01 or later. If your app only reads line_item_id from Gift Card responses, or stays on an API version earlier than 2027-01, then this change doesn't affect you. Why t

ShopifymediumBreaking change

Managed mode for Shopify Tax

No date announced · published 30 Oct 2026

Shopify Tax managed mode helps Shopify apply the correct tax behavior for US sales by managing some store settings and API behavior directly. To keep those settings consistent, some Admin API writes now validate against the requirements of managed mode. Managed mode sets requirements that Shopify uses to keep tax behavior consistent across a store. In some cases, the API now prevents apps from writing settings that would conflict with those requirements. In other cases, tax behavior now depends on more specific product or store data instead of simple boolean settings. For app developers, the main pattern is: Requests that already use the required settings, or that omit settings the app doesn't need to manage, continue to work. Requests that try to override managed-mode requirements might now return validation errors. These changes affect apps that configure markets, publish products, create custom line items, or preview checkout branding for stores that use Shopify Tax managed mod

ShopifyhighBreaking change

Cart mutations reject unconfirmed writes in POS UI extensions 2026-10

No date announced · published 11 Oct 2026

In POS UI extensions API version 2026-10 , Cart API mutations reject when Shopify POS doesn't confirm that the cart changed. In earlier versions these mutations resolve whether or not POS applied the write. This is a breaking change for apps that adopt 2026-10 , and those apps need to handle a rejected promise on every cart mutation they call. Apps on 2026-07 and earlier are unaffected. What changed POS reports the outcome of every cart write. Only a success result confirms that the cart changed. Earlier API versions resolve the mutation regardless of that result, so an app can't tell an applied write from a dropped one, and an app can show a fee or a discount as applied when the cart never changed. In 2026-10 , these mutations reject unless POS confirms the write: bulkCartUpdate , removeLineItem , applyCartDiscount , addCartCodeDiscount , removeAllDiscounts , setCustomer , removeCustomer , addLineItemProperties , bulkAddLineItemProperties , removeLineItemProperties , setLineItemDis

ShopifymediumBreaking change

metafieldInteger collection condition removed in Admin API 2027-01

No date announced · published 4 Oct 2026

As of API version 2027-01 , the metafieldInteger collection source condition inputs and types is removed from GraphQL Admin API. If you use metafieldInteger to create or read collection source conditions, you need to migrate to metafieldInt before you upgrade to API version 2027-01 . What changed With metafieldInt , the value field on integer metafield conditions changes type from Int to String , to align with the metafield value field on the Storefront API. For details, see the Storefront Metafield.value field reference . The following types and fields are replaced: CollectionSourceInclusionConditionMetafieldInteger is replaced by CollectionSourceInclusionConditionMetafieldInt CollectionSourceInclusionConditionMetafieldIntegerRelation is replaced by CollectionSourceInclusionConditionMetafieldIntRelation CollectionSourceInclusionConditionInput.metafieldInteger is replaced by CollectionSourceInclusionConditionInput.metafieldInt CollectionSourceInclusionConditionUpdateInput.metafi

ShopifymediumBreaking change

Segment query functions switch to MATCHES operators in Admin API 2026-10

No date announced · published 4 Oct 2026

As of GraphQL Admin API version 2026-10, functions in the segment query language now use the operators MATCHES / NOT MATCHES instead of = true / = false . For example, the previous query shopify_email.opened() = true would now be represented as shopify_email.opened MATCHES () . The parameters for each function have also been expanded to use their own operators. For example, the query products_purchased(quantity: 5) = true would now be represented as products_purchased MATCHES (quantity = 5) . This expands the functionality of parameters. For example, the following queries were not possible before: products_purchased MATCHES (quantity != 5) , products_purchased MATCHES (quantity > 5) . Additionally, the following named dates have been deprecated: 12_months_ago , 90_days_ago , 30_days_ago , 7_days_ago . Instead, the you can use the existing date offsets in your segment queries. For example, the named date 12_months_ago is equivalent to the date offset -12m . Learn more about customer

ShopifymediumBreaking change

Events subscription query complexity limit drops from 250 to 100 points

No date announced · published 4 Oct 2026

We’re reducing the query complexity limit for Events subscriptions from 250 to 100 points. This change does not affect Classic Webhooks. Shopify assigns each Events query a complexity score based on the fields it selects, the types of data those fields return, and the number of items requested in connections using first or last, following the GraphQL query cost calculation . The limit applies to each subscription query, and queries executed by Events subscriptions don’t count toward your app’s API rate limits . What to do Review subscription queries that exceed 100 points and shape each subscription around the changes your app handles: Split subscriptions by the work they do : You can configure multiple subscriptions for the same topic, each with its own triggers and query. Query the changed resource directly : For example, for a variant price change, query the affected variant’s price, SKU, and parent Product ID instead of fetching the Product’s first 250 variants. This avoids re

ShopifyhighBreaking change

automaticDiscounts query removed in Admin API 2027-01

No date announced · published 4 Oct 2026

The deprecated automaticDiscounts query is removed from the GraphQL Admin API in version 2027-01 . If your app reads a shop’s automatic discounts through automaticDiscounts , you need to move to the discountNodes query with a method:automatic filter before you upgrade to 2027-01 . Apps on 2026-10 and earlier keep working unchanged while those versions are supported. What changed As of API version 2027-01 , automaticDiscounts no longer exists on QueryRoot . Requests that include automaticDiscounts on 2027-01 return a validation error instead of data. The DiscountAutomaticConnection and DiscountAutomaticEdge types are also removed, because no other fields in the schema return them. Use discountNodes instead, with query: "method:automatic" . It returns a connection of DiscountNode objects, each exposing the discount itself on the discount field. discountNodes accepts filters similar to the removed query, including status , discount_type , discount_class , created_at , and starts_at . F

ShopifymediumBreaking change

POS UI Extensions: session.currentSession.staffMemberId removed in API 2026-10

No date announced · published 4 Oct 2026

As of API version 2026-10, the static session.currentSession.staffMemberId field has been removed from the POS UI Extensions Session API. It was deprecated in 2026-07 in favour of session.staffMember, a reactive signal that updates when a different staff member pins into POS. Before targeting API version 2026-10, replace reads of session.currentSession.staffMemberId with session.staffMember.value?.id. To react to staff changes while your extension is running, subscribe to the signal with session.staffMember.subscribe((staffMember) => { ... }), or read .value during render in a Preact component with @shopify/ui-extensions/preact imported to re-render automatically. Extensions on 2026-07 and earlier are unaffected. The BaseData session.staffMemberId available to receipt targets is a separate API and is unchanged. https://shopify.dev/docs/api/pos-ui-extensions/2026-10/apis/session-api

ShopifyhighBreaking change

Events payloads, trigger syntax and delivery headers changed

No date announced · published 4 Oct 2026

Starting today, we're updating Events payloads, trigger syntax, and delivery headers. Classic Webhook subscriptions are unaffected. What's changed fields_changed now describes how each path changed The flat array becomes an object containing three arrays: added , updated , and removed . Developers can distinguish a resource or relationship being added, a value being updated, or a resource or relationship being removed without querying just to infer what happened. Update payload handling to read fields_changed.added , fields_changed.updated , and fields_changed.removed . Adding a variant to a Product, for example, keeps the Product's action as update and places the variant path in fields_changed.added . Before: { "topic": "Product", "action": "update", "fields_changed": [ "product[id: 'gid://shopify/Product/123'].variants[id: 'gid://shopify/ProductVariant/456']" ] } After: { "topic": "Product", "action": "update", "fields_changed": { "added": [ "product[id: 'gid://shopify/Produ

Which of these affect you?

Paste your package.json or requirements.txt and see the Shopify changes that match the SDKs you use, free and without signing up.

Check my stack