Through October and November 2026, Shopify posted a series of app security changes on its developer changelog. Each one has its own deadline, and the deadlines differ for public apps, custom apps built by partners and apps created by merchants. Some have already passed. The next ones fall on December 1, 2026, January 1, 2027 and April 1, 2027.
Merchants should pay attention as well as developers. An app that misses a deadline can be removed from the App Store, blocked from new installs and, at the last stage, lose Admin API access. Agencies that maintain one custom app per client have more apps to check than most.
IP allowlists for public and custom apps
On November 5, Shopify made IP allowlists mandatory for public apps. An allowlist limits which networks can call the Admin API with your app’s tokens. The changelog gives the reason plainly: “Leaked tokens can be used from any network location.” Public apps that use bulk operations had until November 12 to set one up, after which their bulk operations fail. All other public apps had until November 20 at 11:59 PM ET.
According to Shopify’s November 19 update, public apps still without an allowlist are delisted and blocked from new installs. Existing installs keep working but are flagged to merchants in Settings > Apps, and the app is relisted automatically once an allowlist is added. Custom apps need an allowlist before they can be installed on a store outside your organization.
Allowlists are set in the Dev Dashboard. Apps with fixed outbound addresses can enter static IPs or CIDR ranges. Apps on serverless hosting with changing IPs can allow their hosting provider’s ASNs and list the countries they run in. Shopify accepts deadline extension requests from apps that call the Admin API from merchant infrastructure.
Expiring offline access tokens
The largest migration is for tokens. On October 27, Shopify set enforcement dates for moving public apps off non-expiring offline access tokens. Public apps created on or after April 1, 2026 already had to use expiring tokens. Older public apps now face these dates:
- January 1, 2027: apps that have not migrated are delisted and blocked from new installs.
- January 15, 2027: merchants using those apps see admin warnings about possible service interruption.
- April 1, 2027: affected Admin API requests made with non-expiring offline tokens return HTTP 403.
Custom apps follow a separate rule. From December 1, 2026, every newly created custom app, including partner-created apps and apps merchants create, must use expiring offline tokens. Custom apps created before that date can keep their current tokens. The code change is small. Add expiring=1 to the token request, store the refresh token Shopify returns and use it to get a new access token when the current one expires. Tokens from the client credentials grant already expire, so apps using that grant need no change.
Shopify also added a token expiry setting in the Dev Dashboard that rejects non-expiring token requests. Turning it on is a way to test your migration before the deadline does it for you.
Network access declarations for storefront code
The third change covers apps that run code on the online store. Under a November 19 changelog post, these apps must list the servers they load code from or send requests to in allowed_sources, under the network_access section of shopify.app.toml. An app that contacts no external servers declares an empty list. The rule covers apps with a theme app extension block or app embed, online store script tags, an app proxy, the write_themes scope or a web pixel with write_open_pixels. Apps that only write content such as products or metafields are out of scope, and so are custom apps installed only inside your own organization.
For public apps, Shopify rejects deploys and App Store submissions without the declaration from December 1, 2026, and merchants see an admin warning while existing versions keep running. From January 1, 2027 those apps are delisted and blocked from new installs. Custom apps installed outside your organization have deploys rejected from December 1, and from January 1 they cannot be installed on new stores outside it.
Other changes in the same update
The November 19 post lists a few smaller items. Apps that read abandoned checkout recovery URLs need level 2 protected customer data access, from December 1 for public apps and January 1 for partner custom apps. Merchant custom apps must request permission in the Dev Dashboard to run bulk operations. Multi-factor authentication is required on every partner account, and Shopify recommends passkeys. Custom apps created in the Shopify admin now appear in the Dev Dashboard, where they can use IP allowlists, API logs and expiring tokens.
What to do before December 1
For developers, we would start with an inventory. List every app you own, public and custom, and record four things for each: allowlist status, token type, whether it runs code on the storefront and whether it reads abandoned checkout URLs. Then fix them in deadline order. Network access declarations need a new app version deployed and released, so leave time for that.
For merchants, open Settings > Apps and look for flagged apps. Ask the developer of any flagged app, and of every custom app, for a written migration plan with dates. If an agency built a custom app for your store, ask whether it counts as installed outside their organization, because that decides which of these rules apply to it.





