If your public Shopify app calls the Admin API, it needs an IP allowlist configured by November 20, 2026 — or by November 12, 2026 if it runs bulk operations. Miss the November 20 date and Shopify delists the app from the App Store, blocks new installs, and flags it to merchants. Custom apps are no longer all exempt: since November 11, a custom app installed on a store outside the organisation that owns it needs an allowlist too — for new installs from November 20, 2026, and for existing installs from January 1, 2027. Only apps a merchant built for their own store are still fully unaffected.
Shopify recommended the IP allowlist on October 27 and made it a requirement nine days later, in its November 5 developer changelog. The timing is deliberate: this lands right before the busiest selling weeks of the year, and the first deadline is two days from now.
What an IP allowlist actually does
An IP allowlist tells Shopify which servers your app is allowed to call the Admin API from. You list your app's IP addresses or network ranges in the Dev Dashboard, and from then on, your app's access tokens only work when the request comes from those addresses.
The reason is stolen tokens. In Shopify's own words from the changelog: "Leaked tokens can be used from any network location." A token that escapes — in a public repo, a log file, a screenshot — can today be used from an attacker's server anywhere in the world. We wrote last week about how thousands of secrets ended up exposed on public GitHub; an allowlist is the control that makes a leaked app token far less useful, because it stops working the moment it is used from somewhere that is not your infrastructure.
The deadlines, in order
Shopify published the full enforcement timeline in its November 5 app security update. There are two tracks — the IP allowlist, and the separate migration to expiring offline access tokens — and they converge in the spring:
| Date | What happens |
|---|---|
| November 12, 2026, 11:59 PM ET | Bulk queries and bulk mutations from public apps without an IP allowlist fail to execute. |
| November 20, 2026, 11:59 PM ET | Public apps without an IP allowlist are delisted from the App Store and blocked from new installs, and flagged in merchants' Settings > Apps. |
| November 20, 2026, 11:59 PM ET | Custom apps installed outside their owning organisation need an IP allowlist for new installs. |
| January 1, 2027 | Custom apps installed outside their owning organisation need an IP allowlist for existing installs; from this date one non-compliant app blocks new installs of any of the owner's apps on outside stores. |
| January 1, 2027 | Public apps that have not moved to expiring offline access tokens are delisted, blocked from new installs, and flagged in Settings > Apps. |
| January 15, 2027 | Merchants see a warning about non-compliant apps in their admin. |
| April 1, 2027 | Admin API requests from non-compliant apps fail. Existing installs stop working at this point. |
Two details in that table matter more than they look. First, existing installs keep working until April 1, 2027 — a missed November deadline is a growth and reputation problem (delisting, flags, warnings), not an instant outage. Second, the January token deadline is a separate piece of work from the November allowlist. An expiring offline token lasts one hour; a non-expiring one stays valid until the app is uninstalled or the secret is rotated, which is exactly why Shopify wants them gone. Finishing the allowlist this week does not finish the token migration.
Who is not affected
To be completely clear, because this is where most of the confusion is: the requirement applies to public apps, and — since November 11 — to custom apps installed on a store outside the organisation that owns them. That last part is the one that catches agencies: if you built a custom app for a client and installed it on their store, that app needs an allowlist for new installs from November 20, 2026, and for existing installs from January 1, 2027. Per Shopify's November 11 changelog, these are unaffected:
Custom apps installed only on stores within your own organisation.
Apps created by merchants themselves, either in the Dev Dashboard or in the Shopify admin.
If the app on your store was built by your own team for your own store, nobody needs to do anything for these deadlines. If it was built for you by an agency or a partner and installed from their organisation, ask them whether its allowlist is configured — that is the case the November 11 update added.
"Why is my app flagged?" — the merchant side
Store owners will see this change before developers finish dealing with it. Shopify has already added each app's security setup to your admin: go to Settings > Apps and you can see an app's IP allowlist and token status today. After November 20, apps without an allowlist are flagged there. From January 15, 2027, Shopify will show a warning in the admin about non-compliant apps.
If you see a flag, it does not mean your store has been hacked or your data has leaked. It means the app's developer has not done a configuration job Shopify assigned them. Your practical moves:
Don't uninstall in a panic. Existing installs keep working until April 1, 2027. Uninstalling a flagged app in the middle of Black Friday week will hurt you more than the flag does.
Ask the developer one question: "Have you configured your IP allowlist?" A serious app team will already know about the November 5 announcement.
Check again after November 20. If an app you depend on is still flagged and its developer has gone quiet, that is the moment to line up a replacement — while there is still time before April.
Flags are also a quiet quality signal. An app that misses an announced, dated, platform-wide security deadline is telling you something about how it is maintained — the same maintenance that decides whether it keeps up with your store the rest of the year. It is the flip side of what we see with apps that quietly slow a store down: the cost of an unmaintained app rarely shows up where you expect it.
How to comply, if you build apps
The allowlist itself is a short job. In the Dev Dashboard, open your app's Settings and find the IP allowlist section:
Static infrastructure: add your servers' public IP addresses or CIDR ranges.
Serverless or dynamic IPs: allowlist by network instead — add your hosting provider's ASNs and list the countries your app runs in. Shopify added ASN support for exactly this case.
Test before you enforce: the dashboard lets you run a test against your app's recent API traffic, so you can see which real requests would break before anything is blocked.
While you are in there, filter your Dev Dashboard API logs by token type to find every non-expiring offline token your app still uses, and put the token migration on the calendar before January 1 — it touches your auth flow, so it deserves more than a Friday afternoon. One more item is coming: bulk queries and bulk mutations will each need their own access scope. If your app ran a bulk operation in the last 180 days, Shopify grants those scopes automatically; otherwise, add them to your app config before your next deploy once the scope names are published.
If your app makes Admin API calls from merchant infrastructure — the pattern Shopify is pushing developers away from — you can request an extension to these deadlines, but the direction is set: move the calls to infrastructure you control.
What we'd do
At Lynxwell Digital, this is the order we'd work in for any public app this week. Bulk operations first, because that deadline is Thursday and a failed bulk job during a sale is the one consequence here that loses money on day one. Then the allowlist for every remaining public app, tested against real traffic before enforcement. Then the token migration in December, with time to spare before January 1, not during the Christmas shutdown. None of this is work to schedule for the week of Black Friday itself — Shopify chose these dates precisely so the platform is locked down before peak, and the teams that treat it that way will not be debugging access problems while their merchants are selling. Our own build and upgrade work is priced the same transparent way, which you can see on our pricing page.
Need the allowlist or the token migration done for your app? We handle both for a fixed price, finished this week — tell us about your app here.
FAQ
What happens if a public app misses the November 12, 2026 deadline?
Only its bulk operations are affected: bulk queries and bulk mutations from a public app without an IP allowlist fail to execute after November 12, 2026 at 11:59 PM ET. The rest of the app keeps working. The bigger consequences — delisting, blocked installs, merchant flags — arrive on November 20 if the allowlist is still missing.
Are custom apps affected by the IP allowlist requirement?
Yes — if the custom app is installed on a store outside the organisation that owns it. Those apps need an IP allowlist for new installs from November 20, 2026, and for existing installs from January 1, 2027, per Shopify's November 11 changelog. From January 1, 2027, one app without an allowlist blocks its owner from installing any of their apps on stores outside their organisation. Custom apps installed only within their own organisation, and apps merchants created themselves in the Dev Dashboard or the Shopify admin, are still unaffected.
Why is an app flagged in my store's Settings > Apps?
The flag means the app's developer has not configured an IP allowlist (or, from January 1, 2027, has not moved to expiring offline access tokens). It is a compliance flag about the developer's setup, not a sign your store was breached. Existing installs keep working until April 1, 2027, so there is time to ask the developer or plan a replacement.
What if my app runs on serverless hosting with no fixed IP address?
You allowlist by network instead of by address: add your hosting provider's ASNs in the Dev Dashboard and list the countries your app runs in. Shopify added ASN support specifically for apps on serverless platforms and dynamic IPs.
When do existing installs of a non-compliant app stop working?
April 1, 2027. Until then, existing installs keep working even if the app is delisted and flagged. From April 1, 2027, Admin API requests from apps that missed either the allowlist or the expiring-token requirement fail, per Shopify's published timeline.