Shopify Developers Updates & Release Notes
458 updates curated from 466 sources by the Releasebot Team. Last updated: Nov 20, 2026
- Nov 19, 2026
- Date parsed from source:Nov 19, 2026
- First seen by Releasebot:Nov 20, 2026
App security updates: IP allowlist due tomorrow
Shopify Developers adds security tools for admin-created apps and token migration, including IP allowlists, API logs, expiring-token controls, and bulk-operation permissions, while outlining upcoming app security requirements and deadlines.
IP allowlist enforcement starts tomorrow, November 20. New requirements needed by December 1. All apps have access to security tooling in Dev Dashboard. You can also now test your token migration. The busiest shopping weeks of the year are almost here. Thanks to everyone who’s already turned on an IP allowlist, enabled expiring tokens, and taken other steps to help keep merchants protected when it matters most. This Friday, November 20, is the deadline for IP allowlist. We’re also sharing requirements that start December 1, and tooling updates to help you get ready for the next round of security improvements. Action required ■ Public apps without an IP allowlist are delisted after November 20, 2026 Enable IP allowlists now to avoid delisting and being blocked from new installs. Existing installs keep working but will be flagged in merchant Settings > Apps if they’re not compliant. Your app will be relisted automatically when you add an IP allowlist. Don’t wait, it only takes a few minutes. Read the dev docs to learn how. ■ Custom apps need IP allowlist before being installed. After November 20, 2026, an IP allowlist must be enabled on a custom app before installing it on a store outside your organization. Read the changelog ■ Network access declarations required for apps that run on the online store. Apps that run code on the online store must declare allowed_sources in the network_access section of shopify.app.toml. The first deadline is December 1, 2026, followed by January 1, 2027. Read the changelog ■ Custom apps need expiring offline access tokens will be required for every custom app created on and after December 1, 2026. Read the changelog ■ Apps that read abandoned checkout recovery URLs will require level 2 protected customer data access starting December 1, 2026 for public apps and January 1, 2027 for partner custom apps. If your app uses these URLs, request access to name, email, phone, and address before your deadline. Read the changelog ■ Merchant custom apps need access to enable bulk operations. Merchant custom apps created in the Dev Dashboard or the Shopify admin must now request permission to run bulk queries or mutations within the Settings section of the Dev Dashboard. Read the dev docs ■ Multi-factor authentication is now required on every partner account. Turn it on now; we recommend passkeys. For other upcoming security deadlines, see the security deadlines calendar. Also new this week ■ Admin-created custom apps are now in Dev Dashboard, giving them the same high quality security tools as all other apps, including IP allowlists, API logs, and expiring tokens. Existing tokens keep working. Read the changelog ■ Declare that your app uses only expiring access tokens. Turn on the Admin API token expiry card in your apps’ Settings to reject requests for non-expiring tokens, giving you confidence your migration is complete ahead of the deadline. Read the changelog Get help If you see something suspicious, tell us right away at [email protected]. You're responsible for fixing it and notifying affected merchants, and we'll support you through it. For general security questions, contact Shopify Support. For guidance on all our security practices, and a complete timeline, see the App Security Hub. We're here to answer questions on the App Security board in the developer community.
Original source - Nov 19, 2026
- Date parsed from source:Nov 19, 2026
- First seen by Releasebot:Nov 20, 2026
Function settings extensions can now report several errors at once
Shopify Developers adds support for multiple validation errors in function settings extensions, so merchants can see every issue at once on discount and checkout rule pages. Existing single-error behavior remains supported, and no action is required.
Function settings extensions can now report several errors at once. When your s-function-settings onSubmit handler rejects with an AggregateError, the Shopify admin shows every error on discount and checkout rule pages instead of only one. No action is required. What changed Previously, the admin showed one error when your extension rejected the promise you passed to event.waitUntil() in onSubmit, using the message of that error. Now you can reject with an AggregateError, and the admin shows the message of each entry in its errors list. Each entry is an Error, and you can give it a code string. ■ The admin shows up to 10 errors. Each message is trimmed to 300 characters, and duplicate messages appear once. ■ Your onError handler receives the same entries, with their codes, so you can mark the fields in your own UI. ■ An entry with no code, or a code that is empty or longer than 64 characters, gets a default code: UNKNOWN on discount pages and EXTENSION_ERROR on checkout rule pages. ■ Rejecting with a single Error still works and shows one error. The onerror property of s-function-settings is now typed as the AggregateError it receives in @shopify/ui-extensions 2025-10, 2026-10, and the 2027-01 release candidate. Who's affected This applies to apps with a function settings extension on discount or checkout rule pages, built with Polaris web components on API version 2025-10 or later. Extensions on earlier API versions keep the previous behavior and show a single message. Extensions that reject with a single Error also keep working as before. Why this matters When a merchant fills in several fields incorrectly, they now see every problem after one save. They do not have to fix one field, save, and then find the next error. What to do No action is required. To report several errors, reject with an AggregateError of Errors in your onSubmit handler: function fieldError(code, message) { return Object.assign(new Error(message), { code }); } async function save(settings) { const errors = []; if (!settings.minimumQuantity) { errors.push(fieldError('MINIMUM_QUANTITY_REQUIRED', 'Enter a minimum quantity.')); } if (settings.percentage > 100) { errors.push(fieldError('PERCENTAGE_TOO_HIGH', 'Percentage can be at most 100.')); } if (errors.length > 0) { throw new AggregateError(errors, 'Settings are not valid'); } // apply your metafield changes here } <s-function-settings onSubmit={(event) => event.waitUntil(save(settings))} onError={(event) => { for (const error of event.error.errors) { console.log(error.code, error.message); } }}> {/* your fields */} </s-function-settings> This sample checks two fields and throws one AggregateError with an Error per invalid field. Replace the checks and codes with your own. To test your extension, save settings with several invalid fields on a development store and confirm that the admin lists each error. Related docs ■ Discount Function Settings API reference ■ Build a discount UI extension with UI extensions
Original source All of your release notes in one feed
Join Releasebot and get updates from Shopify and hundreds of other software products.
- Nov 19, 2026
- Date parsed from source:Nov 19, 2026
- First seen by Releasebot:Nov 20, 2026
Network access declarations are now required for apps that run on the online store
Shopify Developers introduces required network access declarations for apps that load code on online stores, helping protect merchants. Developers must list external servers in app configuration before upcoming deploy, submission, and installation restrictions take effect.
We're adding network access declarations as a requirement to better protect merchants. Apps that run code on the online store must declare allowed_sources in the [network_access] section of shopify.app.toml. Timeline Shopify will reject deploys and delist apps that haven't added the required declarations as follows. Public apps: ■ December 1, 2026: Shopify rejects deploys and Shopify App Store submissions. Merchants see a warning in the Shopify admin. Existing app versions keep working. ■ January 1, 2027: Shopify delists apps from the Shopify App Store and blocks new installs. Existing installs keep working. Custom apps installed outside your organization: ■ December 1, 2026: Shopify rejects deploys. ■ January 1, 2027: Shopify blocks installs of your apps outside your organization until every app that's in scope declares its network access. What apps are affected Public apps, and custom apps that you install on stores outside your organization, are affected if they use any of the following features: ■ A theme app extension block or app embed. ■ Script tags on the online store. ■ An app proxy. ■ The write_themes access scope. ■ A web pixel with the write_open_pixels access scope. What apps are unaffected ■ Apps that only write content, such as metafields, menus, or products. ■ Apps that have a checkout UI extension but none of the features listed above. ■ Custom apps that you install only on stores within your organization. ■ Apps that merchants create in the Dev Dashboard or in the Shopify admin. ■ Web pixels that run in the default strict sandbox. Why we're making this change Injected scripts can load code onto a storefront from any server. Declaring your app's servers helps Shopify spot suspicious requests, which protects your app and the merchants who use it. What to do ■ Add the servers that your app's code loads from or sends requests to, such as your API or CDN, to allowed_sources. If your app doesn't contact any external servers, then set allowed_sources = []. An empty list counts as a declaration. ■ Optional: Add the hosts that your app links customers to, such as your app's own site, to allowed_navigation_hosts. This helps Shopify recognize links to sites that you trust, so customers are less likely to see an exit warning. ■ Test your configuration on a dev store with the Network access testing preview. The preview covers the online store only. ■ Run shopify app deploy, and then release the new version. Here's an example configuration: [network_access] allowed_sources = ["https://api.app.example.com"] allowed_navigation_hosts = ["app.example.com"] For examples and troubleshooting, refer to Declare your app's network access. For every upcoming date, refer to Upcoming security deadlines.
Original source - Nov 19, 2026
- Date parsed from source:Nov 19, 2026
- First seen by Releasebot:Nov 20, 2026
Expiring offline access tokens required for new custom apps as of December 1, 2026
Shopify Developers will require new custom and merchant-created apps to use expiring offline access tokens for Admin API requests starting December 1, 2026, extending a requirement already in place for public apps. Existing apps are unaffected, and client credentials tokens already meet the requirement.
Starting December 1, 2026, every new custom app must request and use expiring offline access tokens for GraphQL Admin API and REST Admin API requests. This has been required for new public apps since April 1, 2026. This update extends the requirement to new partner-created custom apps and merchant-created apps. If you already request expiring offline tokens, you likely don’t need to change your app. What changed For apps created on or after December 1, 2026, Shopify requires expiring offline access tokens for Admin API calls: ■ New offline tokens that you obtain with the authorization code grant or token exchange must be expiring. ■ You request an expiring offline token by including expiring=1 in your token request and then storing and using the refresh token that Shopify returns. ■ Tokens that you obtain through the client credentials grant already expire after 24 hours, so this flow already meets the requirement. ■ Tokens that you obtain through application-only access already meet the requirement. Existing custom apps and merchant-created apps that were set up before December 1, 2026 can keep using their existing offline tokens. Who’s affected The requirement for expiring offline access tokens applies to: ■ Custom apps created on or after December 1, 2026 ■ Apps that merchants create on or after December 1, 2026 The following aren’t affected by this change: ■ Custom apps and merchant-created apps that were created before December 1, 2026 ■ Public apps, which have already been required to use expiring offline tokens since April 1, 2026 Why this matters Expiring offline access tokens limit how long a leaked token can be used. If an expiring token leaks, it stops working after a fixed amount of time unless your app refreshes it. A non-expiring token keeps working until the app is uninstalled or you rotate the app secret, which increases the risk from a leak. What to do If your app uses token exchange or the authorization code grant: ■ Include expiring=1 in your token requests for offline access. ■ Store and use the refresh token that Shopify returns to obtain new access tokens when the current one expires. ■ If you use Shopify app templates or libraries, check that you’re on a recent version, because they already request expiring tokens by default. If your app uses the client credentials grant: ■ You don’t need to make any changes. Tokens from that grant already expire after 24 hours. For setup details and examples, see the expiring offline access token guide in the Admin API docs: Use expiring offline access tokens.
Original source - Nov 19, 2026
- Date parsed from source:Nov 19, 2026
- First seen by Releasebot:Nov 20, 2026
abandonedCheckoutUrl now requires level 2 protected customer data access
Shopify Developers will require approval for all four protected customer fields to access abandoned checkout recovery URLs, with deadlines for public and custom apps. Apps without approval will lose the field in API responses and webhooks, so developers should request access or update their integrations.
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 Abandoned Checkout.abandoned Checkout Url 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 Public apps | December 1, 2026 | Request access; a data protection review is required Partner custom apps (built by a partner for a specific store) | January 1, 2027 | Enable the four fields yourself in the Dev Dashboard; no review Merchant-created apps in the Dev Dashboard (apps a store or organization builds for its own use) | January 1, 2027 | Enable the four fields yourself in the Dev Dashboard; no review Apps created in the Shopify admin | Not affected | Nothing to do Why The recovery URL opens the buyer's checkout with their name, email, phone, and address filled in. Apps without access to those fields already can't read that data on the Abandoned Checkout object, so the URL now requires the same access. What happens if you don't act by your date The following applies to apps that aren't approved for all four protected customer fields: name, email, phone, and address (read_customer_name, read_customer_email, read_customer_phone, and read_customer_address). Approval for only some of them isn't enough. Apps approved for all four aren't affected. GraphQL Admin API: queries that select the field fail ■ abandoned Checkout Url returns an ACCESS_DENIED error, and the error nulls out the surrounding data. ■ List queries such as abandoned Checkouts return data: null, so you lose all the abandoned checkout data in that query, not just the URL. ■ A node or nodes lookup returns null for that checkout. ■ Bulk operations that select the field fail with ACCESS_DENIED after retrying for a few minutes. What to do: remove abandoned Checkout Url from your queries and bulk operations, or request access. # Before { abandonedCheckouts(first: 10) { edges { node { id abandonedCheckoutUrl } } } } # After { abandonedCheckouts(first: 10) { edges { node { id } } } } REST Admin API and webhooks: the field is left out Warning: If your app uses abandoned _checkout _url, it won't be there anymore. From your date, the field is removed from REST responses and webhook payloads for apps without access. There's no error, so your app won't be told it's missing. ■ abandoned _checkout _url is left out of GET /admin/api/{version}/checkouts.json responses and checkouts/create/checkouts/update webhook payloads. Everything else is unchanged. ■ REST returns this field by default, so your app may receive it today without using it. If your app never reads it, you won't notice the change. ■ If your app reads it, features that use the URL, such as recovery emails, SMS, or direct mail, lose their link, and code that assumes the key is present may fail. What to do: if your app uses the URL, request access before your date. Otherwise, make sure your app handles the field being missing. You can also stop receiving it by requesting only the fields you use with the fields parameter. How to get access If your app needs the recovery URL (for example, to send abandoned checkout recovery messages), request access to protected customer data: in the Dev Dashboard, go to your app's Settings > Access requests > Protected customer data > Manage, then select the name, email, phone, and address fields with your reasons. All four are required. ■ Custom apps (partner custom apps and merchant-created apps in the Dev Dashboard) can enable these fields themselves, with no review. ■ Public apps need a data protection review before access is granted. Reviews can take a couple of weeks, so request access as soon as possible. Development stores don't enforce protected customer data approval, so you won't see these errors there. Check your app's protected customer data status in the Dev Dashboard. Related docs ■ Work with protected customer data ■ Request access to protected customer data ■ Abandoned Checkout object
Original source Similar to Shopify Developers with recent updates:
- Shopify updates364 release notes · Latest Nov 17, 2026
- OpenAI updates314 release notes · Latest Nov 20, 2026
- ChatGPT updates255 release notes · Latest Nov 19, 2026
- Gemini updates478 release notes · Latest Nov 19, 2026
- Gemini API updates160 release notes · Latest Nov 19, 2026
- Notion updates158 release notes · Latest Nov 19, 2026
- Nov 19, 2026
- Date parsed from source:Nov 19, 2026
- First seen by Releasebot:Nov 20, 2026
RolloutChange now includes applyResult
Shopify Developers adds the applyResult field to the GraphQL Admin API’s Rollout Change interface in version 2027-01, helping apps track rollout change outcomes, completion times, and known failure reasons.
As of GraphQL Admin API version 2027-01, the Rollout Change interface has an applyResult field. Applying a rollout makes a treatment's changes permanent for every buyer. applyResult shows the outcome of the latest attempt to apply each change, so your app can find changes that failed. applyResult is null before the first attempt to apply the change. With an online access token, it's also null if the staff member can't read the changed resource. It uses the existing read_rollouts access scope. query { rollout(id: "gid://shopify/Rollout/1") { treatments { changes(first: 10) { nodes { id applyResult { status completedAt errorCode } } } } } } Rollout Change Apply Result has three fields: ■ status: IN_PROGRESS, SUCCESS or FAILURE. ■ completedAt: when the attempt finished. It's null while in progress, or if the time wasn't recorded. ■ errorCode: why the change failed, when known: RESOURCE_NOT_FOUND, VALIDATION_FAILED, LIMIT_EXCEEDED, INVALID_CHANGE or INTERNAL_ERROR.
Original source - Nov 18, 2026
- Date parsed from source:Nov 18, 2026
- First seen by Releasebot:Nov 19, 2026
App Events: Send events from Admin UI extensions and embedded apps
Shopify Developers adds app event reporting for Admin UI extensions and embedded apps, expanding usage tracking across Shopify’s admin, Checkout, and Customer Account surfaces. The optional API requires no changes to existing apps.
Admin UI extensions and embedded apps can now send app events to Shopify with shopify.app Events.emit(). At Editions, we launched app events for Checkout and Customer Account UI extensions. This release adds the Shopify admin, so you can now track app usage across all three surfaces. This is a new, optional API, so no action is required. What changed shopify.app Events.emit() is now available on two more surfaces: ■ Admin UI extensions: Extensions that use API version 2027-01 or later can call shopify.app Events.emit(). Extensions that you preview with shopify app dev can also send events. ■ Embedded apps (App Home): Apps that use App Bridge can call the same method from the app's pages in the Shopify admin. The method takes an event handle and an optional object of attributes: shopify.appEvents.emit("description_generated", { word_count: 120, placement: "product_details", }); Shopify adds your app and the shop to each event, so you do not need an access token or a shop ID. Do not include data in attributes that could identify an individual, such as names, email addresses, phone numbers, staff member IDs, or customer IDs. Events that Shopify accepts are visible in the Dev Dashboard logs, together with the events that your app backend sends. Events do not identify the extension that sent them or the staff member who used it. Each Admin UI extension can send a burst of up to 20 events, then 2 events per second. An embedded app has the same limit, shared across the app in one Shopify admin tab. Events from Admin UI extensions and embedded apps are not processed for billing. To report usage for Shopify App Pricing, send a billing event from your app backend. Who's affected This change applies to apps that have Admin UI extensions on API version 2027-01 or later, and to embedded apps that use App Bridge. Embedded apps do not need a specific API version. Admin UI extensions on earlier API versions do not have shopify.app Events. On should-render targets and data targets, emit() sends nothing and resolves {success: false, error: 'Emit is unavailable.'}. An embedded app gets the same result where the Shopify admin does not offer App Events. What to do No action is required as existing apps and extensions will continue to work without changes. If you want to send events from the Shopify admin, do these steps: ■ For an Admin UI extension, set api_version = "2027-01" or later in shopify.extension.toml. ■ Call shopify.app Events.emit() with an event handle and optional attributes. ■ Run shopify app dev and use the extension or app in a development store. ■ Check the result of emit(). If success is false, read error for the cause. ■ Open Logs in the Dev Dashboard to confirm that your events arrive. Related docs ■ Send events from Admin UI extensions ■ Send events from embedded apps with App Bridge ■ Monitoring and logs in the Dev Dashboard
Original source - Nov 18, 2026
- Date parsed from source:Nov 18, 2026
- First seen by Releasebot:Nov 19, 2026
draftOrderCreate and draftOrderUpdate require the apply_discounts_to_draft_orders permission to add discounts
Shopify Developers now reject draft order discount additions made by staff without the Apply discounts permission, returning a top-level ACCESS_DENIED error and null mutation payload. Apps should check top-level errors, not just userErrors.
In all supported API versions, draftOrderCreate and draftOrderUpdate return an ACCESS_DENIED error when an app acting as a staff member without the apply_discounts_to_draft_orders permission adds a discount to a draft order. The mutations don’t save the draft order and return null for the mutation payload. Apps that rely only on userErrors for failure handling need to update their error handling. What changed When a request runs as a staff member who doesn’t have the apply_discounts_to_draft_orders permission draftOrderCreate and draftOrderUpdate reject any change that adds discounts through the DraftOrderInput: ■ Adding a discount code to discountCodes that the draft order doesn’t already have ■ Setting acceptAutomaticDiscounts to true on a draft order that doesn’t already accept automatic discounts For draftOrderCreate any non-empty discountCodes or acceptAutomaticDiscounts: true counts as adding a discount because the draft order doesn’t exist yet. In these cases, the mutation returns a top-level GraphQL error with the code ACCESS_DENIED and null for the mutation’s payload. The error doesn’t appear in userErrors. Keeping or removing a draft order’s existing discounts still works. Example This request adds a discount code and turns on automatic discounts for an existing draft order: mutation draftOrderUpdate ($id: ID!, $input: DraftOrderInput!) { draftOrderUpdate (id: $id, input: $input) { draftOrder { id discountCodes acceptAutomaticDiscounts } userErrors { field message } } } { "id": "gid://shopify/DraftOrder/276395349", "input": { "discountCodes": ["SUMMER10"], "acceptAutomaticDiscounts": true } } If the staff member doesn't have the apply_discounts_to_draft_orders permission, the response is: { "errors": [ { "message": "Access denied for draftOrderUpdate field. Required access: `write_draft_orders` access scope. Also: The user must have access to manage draft orders.", "locations": [{"line": 2, "column": 3}], "path": ["draftOrderUpdate"], "extensions": { "code": "ACCESS_DENIED", "documentation": "https://shopify.dev/api/usage/access-scopes", "requiredAccess": "`write_draft_orders` access scope. Also: The user must have access to manage draft orders." } } ], "data": {"draftOrderUpdate": null} } draftOrderCreate returns the same error, with draftOrderCreate in the message and path, and null for data.draftOrderCreate. Who's affected You’re affected if your app: ■ Calls draftOrderCreate or draftOrderUpdate as a staff member, and ■ Expects to add discount codes or enable automatic discounts, and ■ Doesn’t ensure that the staff member has the apply_discounts_to_draft_orders permission Requests that don’t act as a staff member, such as requests made with an offline access token, aren’t affected. What to do ■ Check the top-level errors array, not just userErrors, for an ACCESS_DENIED error from draftOrderCreate or draftOrderUpdate. ■ If your app needs to add discounts, ask the merchant to give the staff member the Apply discounts permission under Draft orders. Related docs ■ draftOrderCreate ■ draftOrderUpdate ■ DraftOrderInput ■ Store permissions
Original source - Nov 17, 2026
- Date parsed from source:Nov 17, 2026
- First seen by Releasebot:Nov 18, 2026
Admin-created custom apps now appear in the Dev Dashboard
Shopify Developers moves admin-created custom apps into the Dev Dashboard, where merchants can manage credentials, inspect API and webhook logs, and configure IP restrictions. Existing apps, tokens, scopes, and integrations keep working, with no automatic token changes or restrictions.
Custom apps created in the Shopify admin are moving to the Dev Dashboard, where you can view their logs and set up an IP allowlist. Existing integrations keep working. What changed Custom apps that merchants or staff created in the Shopify admin now appear in the Dev Dashboard. Manage existing admin-created custom apps in the Dev Dashboard, including credentials and logs. Existing apps and integrations keep working: ■ Apps stay installed with their existing access scopes and webhook subscriptions. ■ Existing Admin API access tokens continue to work. In the Dev Dashboard, these apps now have access to: ■ Configure IP restrictions to control which IP addresses can use the app’s credentials. ■ Inspect API and webhook logs to investigate unexpected activity and troubleshoot integration issues. The migration doesn’t automatically replace any existing tokens or enable IP restrictions. For more on building and managing apps in the Dev Dashboard, see the dev docs Who’s affected This change applies to custom apps that were created in the Shopify admin, including apps transferred to a merchant. These custom apps will now appear in the merchant’s Dev Dashboard. Public apps and other app types that you already managed in the Dev Dashboard are not affected. Why this matters Managing all app types in the Dev Dashboard gives you: ■ Centralized control over app credentials and authentication. ■ IP restrictions that reduce the risk of credential misuse. ■ Logs for API calls and webhook deliveries that make it easier to audit traffic and debug issues. This helps you secure existing integrations without breaking them and gives you better visibility into app behavior. What to do No immediate action is required for your apps to keep working. To improve security and observability, you should: Review each migrated custom app in the Dev Dashboard and confirm that it appears with the expected installation and scopes. Enable IP restrictions for each app where you can safely limit traffic to known IP addresses. Use the API and webhook logs in the Dev Dashboard to confirm that requests and deliveries look as expected after any changes. After you enable IP restrictions, monitor the logs for a period of time to confirm that all integrations continue to function as expected.
Original source - Nov 17, 2026
- Date parsed from source:Nov 17, 2026
- First seen by Releasebot:Nov 18, 2026
Amazon EventBridge webhook payload size limit increased to 1 MB
Shopify Developers now sends webhook and Events payloads up to 1 MB inline through Amazon EventBridge, reducing follow-up API requests and downloads for large resources. The change applies automatically across API versions with no action required.
You can now receive webhook and Events payloads up to 1 MB (1,000,000 bytes) through Amazon EventBridge, up from 256 KB. This increase applies automatically across all API versions, and you don't need to update your existing subscriptions. What changed Previously, Amazon EventBridge deliveries capped payloads at 256 KB: ■ Classic webhook payloads over 256 KB fell back to a minimal {"id": ...} body, requiring a follow-up Admin API request to fetch the full resource. ■ Events payloads over 256 KB used large-payload overflow and delivered a temporary payload_url download link instead of the inline payload. Shopify now sends raw UTF-8 payloads up to 1,000,000 bytes directly to your Amazon EventBridge partner event source, leaving headroom under EventBridge's 1 MiB entry cap for the source, detail-type, and detail envelope. Large resources such as products with many variants or orders with many line items now arrive inline, reducing follow-up Admin API requests and payload_url downloads in your app. Payloads over 1,000,000 bytes keep the existing fallback behavior: classic webhooks send {"id": ...}, and Events deliveries send a stub payload with payload_url, payload_size_bytes, and expires_at. What to do No action is required. Existing EventBridge subscriptions configured in shopify.app.toml or through the GraphQL Admin API (eventBridgeWebhookSubscriptionCreate and webhookSubscriptionCreate) automatically receive inline payloads up to 1 MB across all API versions. To review how your app handles large deliveries: ■ Keep fallback handling in place for payloads that exceed 1 MB ({"id": ...} for classic webhooks and payload_url for Events), or narrow payloads with include_fields and targeted Events [events.subscription] query selections. ■ Verify that the downstream AWS targets attached to your EventBridge rules accept events up to 1 MB, or configure an EventBridge input transformer if a target enforces a smaller quota.
Original source - Nov 17, 2026
- Date parsed from source:Nov 17, 2026
- First seen by Releasebot:Nov 18, 2026
Updated B2B location access in the Customer Account API
Shopify Developers updates B2B access across all Customer Account API versions, limiting customers to company data and orders for companies they belong to. Restricted location fields may return null or empty results, and orders from companies they leave no longer appear in their history.
We've changed what B2B customers can read on all versions of the Customer Account API. Customers now read only the company data and the orders for companies that they belong to. Company location access The schema doesn't change. Some fields now return null, an empty list, or fewer results. Company Contact.locations returns an empty list unless the contact belongs to the current customer. The current customer reads the locations that they have a role in from their contact's locations field, from Company.locations, and from company Location(id:). On a Company Location where the current customer has no role, the following fields return null or an empty list: ■ Tax field: tax Identifier. ■ Contact fields: contacts and role Assignments. Orders after a customer is removed from a company When a merchant removes a customer from a company, order(id:) and draft Order(id:) refuse that company's orders and draft orders. customer.orders and customer.draft Orders exclude the orders and draft orders for that company. The customer's personal orders are still listed. What you need to do If your app reads a location's tax or contact data through another contact's locations or through an order's purchasing Entity, then expect null or an empty list for locations where the customer has no role. If your app shows a customer's order history, then the history omits the orders that the customer placed for a company that they no longer belong to. You don't need to change your queries.
Original source - Nov 16, 2026
- Date parsed from source:Nov 16, 2026
- First seen by Releasebot:Nov 17, 2026
- Modified by Releasebot:Nov 18, 2026
Opt in to Admin API token expiry in the Dev Dashboard
Shopify Developers adds an optional Admin API token expiry setting in the Dev Dashboard, helping app teams test migration readiness before enforcement begins for existing public apps in 2027. Enabling it applies across an app’s installed stores and can cause requests using noncompliant tokens to fail.
You can now turn on Admin API token expiry from your app’s Settings page in the Dev Dashboard. This optional setting lets you test your migration to expiring Admin API tokens before enforcement begins for existing public apps on April 1, 2027.
What changed
When you enable Admin API token expiry for an app, it applies across every store where that app is installed. GraphQL and REST Admin API requests then fail if they use either:
- A non-expiring offline access token
- A delegate access token with more than 24 hours remaining before expiry
Enforcement can take up to 30 minutes to take effect. Enabling the setting doesn’t migrate or revoke existing tokens.
You can turn the setting off if you encounter issues. Turning it off doesn’t change the April 1, 2027 enforcement deadline for public apps. That deadline doesn’t apply to custom apps or apps created by merchants.
Who’s affected
This setting is available for all app types in the Dev Dashboard. It affects an app only after you turn it on for that app.
The April 1, 2027 enforcement deadline applies to existing public apps. It doesn’t apply to custom apps or apps that merchants create for their own stores, although those apps can still use this setting to test their behavior with expiring tokens.
What to do
You don’t have to turn on Admin API token expiry. Public apps must still meet the existing migration deadlines described in the migration guide.
If you want to validate your migration early, you can:
- Complete your migration using the Admin API token expiry migration guide, then review your app’s GraphQL and REST logs for affected requests. The Dev Dashboard highlights potential token-expiry issues detected in the last 14 days, though detection can lag by a day.
- Open your app in the Dev Dashboard, go to Settings, and select Turn on in the Admin API token expiry card. Confirm that you understand that requests that don’t meet token-expiry requirements will fail.
- Allow up to 30 minutes for enforcement to take effect. Then check your app’s workflows and logs for rejected requests, including requests from background jobs, to confirm that your app handles expiring tokens correctly.
- Nov 14, 2026
- Date parsed from source:Nov 14, 2026
- First seen by Releasebot:Nov 14, 2026
- Modified by Releasebot:Nov 14, 2026
App security updates: Thank you, plus what's required next
Shopify Developers now lets apps combine IP addresses, CIDR ranges, and hosting provider ASNs in allowlists, while tightening security requirements and enforcement for public and partner-created apps.
Thank you for adding IP allowlists for bulk operations. Here's what's required now, what's new, and what's coming next for your apps and partner account.
Thanks to you, we've already seen the vast majority of apps that run bulk operations adopt an IP allowlist. That's a big step toward keeping merchants protected heading into the busiest weeks of the year.
Here's what's required, what's new, and what's coming next.
Action required
All public apps that call the Admin API: Turn on an IP allowlist by November 20, 2026 at 11:59 PM ET. Apps without one will be delisted from the Shopify App Store and blocked from new installs. Existing installs keep working. For apps that are delisted, we'll relist apps automatically once they add an IP allowlist.
Bulk operations: We're beginning enforcement on bulk queries and mutations from public apps without an IP allowlist. Turn on your allowlist to restore them.
Enable bulk operations for partner-created apps: Before your app can run bulk queries or bulk mutations, enable them from API access requests in the Partner Dashboard. If your app doesn't start a bulk query or mutation for 31 days, you'll need to enable it again.
Custom apps installed outside your organization also need an IP allowlist: These apps need an IP allowlist for new installs from November 20, 2026, and for existing installs from January 1, 2027. From January 1, one app without an allowlist blocks you from installing any of your apps on stores outside your organization. Apps installed only within your organization, and apps created by merchants, aren't affected.
New this week
- You can now use IP addresses and ASNs together. Your allowlist can include IP addresses, CIDR ranges and your hosting provider's ASNs at the same time, with up to 250 IP addresses or ranges. A request is allowed if it matches any entry. Country restrictions apply only to ASNs. For the strongest protection, use specific IP addresses wherever you can.
Coming soon
- MFA on every partner account. Starting next week, multi-factor authentication will be required on all partner accounts. We recommend passkeys. Turn on MFA now so it doesn't interrupt your work later.
Get help
If you see something suspicious, tell us right away at [email protected]. You're responsible for fixing it and notifying affected merchants, and we'll support you through it.
For general security questions, contact Shopify Support.
Everything lives in the App Security Hub, and we answer questions on the App Security board in the developer community.
Original source - Nov 13, 2026
- Date parsed from source:Nov 13, 2026
- First seen by Releasebot:Nov 14, 2026
- Modified by Releasebot:Nov 14, 2026
Market metafields break ties between equally specific markets by market handle
Shopify Developers changes how tied market metafields are resolved: buyers now get the value from the equally specific market with the lowest handle across Storefront API, Liquid, and Function APIs.
When a buyer matches two or more equally specific markets that set the same metafield,
Market.metafieldandMarket.metafieldsnow return the value from the market with the lowest handle, instead of the value that was updated most recently. This behavior change applies to the Storefront API, Liquid, and Function APIs on every API version. If your app or theme reads market metafields on stores with overlapping markets, check which value buyers get in a tie.What changed
A buyer can match more than one market. When several of those markets set the same metafield, the value comes from the most specific market. That doesn’t change.
When the most specific markets that set the metafield are equally specific, one of their values has to win. Before this change, the value that was updated most recently won. With this change, the value from the market with the lowest handle wins.
For example, a buyer in Canada matches two region markets: one for Canada and the United States, with the handle
canada-us, and one for Canada and Mexico, with the handlecanada-mexico. Neither market is more specific than the other, and both set thecustom.bannermetafield:- Before this change, the buyer got the
custom.bannervalue that was updated most recently. - After this change, the buyer gets the value from
canada-mexico, becausecanada-mexicocomes beforecanada-us.
Handles are compared by byte value, one character at a time. For handles that use only lowercase letters, digits, and hyphens, this is alphabetical order, with hyphens before digits and digits before letters.
Who’s affected
Shopify is rolling out this change first to stores where the new tie break behavior doesn’t change which values buyers see. For stores that might be affected, Shopify will contact merchants so they can adjust market handles before the change applies to their store.
The change applies to every API version of these fields:
- Storefront API:
Market.metafieldandMarket.metafields(see Market) - Liquid:
localization.market.metafields(see Market) - Function APIs:
Market.metafieldin each Function API whose input includes a market (for example, https://shopify.dev/docs/api/functions/latest/delivery-customization#Input.fields.localization.market.metafield)
These APIs returns different value only when all of these conditions are true:
- The buyer matches two or more equally specific markets that set the same metafield.
- No more specific market that the buyer matches sets that metafield.
- The tied markets store different values, and the most recently updated value isn’t the value from the market with the lowest handle.
Why this matters
The update time of a metafield isn’t visible in the Shopify admin. Merchants couldn’t see or control which value buyers got, and editing a metafield on one market could change what buyers in an overlapping market saw. Market handles are visible and editable in the Shopify admin, so merchants can choose which market wins a tie.
What to do
No action is needed for app partners.
Original source - Nov 13, 2026
- Date parsed from source:Nov 13, 2026
- First seen by Releasebot:Nov 14, 2026
- Modified by Releasebot:Nov 14, 2026
Market.metafields matches keys in any case as of Storefront API version 2027-01
Shopify Developers changes Storefront API 2027-01 so Market.metafields matches stored keys regardless of letter case, aligning its results with Market.metafield. The update may affect apps and custom storefronts that rely on case-sensitive key matching.
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 applies to apps and custom storefronts that query metafields on a Market object, from Localization.market or Country.market, with Storefront API version 2027-01 or later. Your app is affected only if one of these conditions is true:
- It requests a key in a different case from the key that the market stores.
- The buyer's markets store the same key in different cases.
Your app isn't affected if it requests each key in the case that the markets store it, or if it uses only Market.metafield, which already matches keys in any case. Versions 2026-10 and earlier don't change.
Why this matters
In earlier versions, Market.metafield and Market.metafields can return different results for the same key: Market.metafield finds the metafield, and Market.metafields returns null. In 2027-01, both fields return the same metafield, so your storefront shows the same value whichever field it queries.
What to do
Market.metafield already matches keys case-insensitively, and it returns the metafield from the buyer's most specific market. So on the version that you use today, Market.metafield returns the result that Market.metafields returns in 2027-01. You can compare the two fields to find out whether the change affects your app.
- For each market metafield that your app reads, query Market.metafield and Market.metafields with the same namespace and key, and compare the results.
- If the results are the same for every key, then you don't need to make changes.
- If a result is different, then check whether the difference has a material impact on your app or your storefront.
- If it does, then update your app and your metafields so that they don't depend on the case of keys. For example, request each key in the case that your markets store it, and use one case for each key on every market.
query CompareMarketMetafields @inContext ( country: CA ) { localization { market { metafield ( namespace: "custom", key: "Colour" ) { key value } metafields ( identifiers: [ { namespace: "custom", key: "Colour" } ] ) { key value } } } }Related docs
- Market object in the Storefront API
- Storefront API 2027-01 reference
- Retrieve metafields with the Storefront API
- About Shopify API versioning
Curated by the Releasebot team
Releasebot is an aggregator of official product update announcements from hundreds of software vendors and thousands of sources.
Our editorial process involves the manual review and audit of release notes procured with the help of automated systems.