Executive summary
- What changed: The IP allowlist Shopify recommended on October 27 is now mandatory for every public app, with two deadlines: November 12 for apps using bulk operations, November 20 for everyone else.
- Why it matters: Enforcement lands in the middle of peak trading, and an app that misses the date gets delisted and flagged to merchants inside the Shopify admin.
- Who should act: Agencies and in house teams shipping public apps, plus merchants whose operations depend on third party apps during peak.
What changed
Nine days after recommending it, Shopify made the IP allowlist a requirement. With enforcement on, Shopify checks the source address of every Admin API request made with your app's tokens and rejects anything outside the list with a 403. A stolen token becomes useless away from your own infrastructure.
Two dates matter. Public apps running bulk queries or mutations need an allowlist by November 12 at 11:59 PM ET, after which those operations fail outright. Every other public app needs one by November 20, after which it is delisted from the App Store and blocked from new installs. Existing installs keep working until April 1, 2027, when requests start returning 403.
Supporting changes shipped alongside. Merchants can now inspect an app's token expiry and allowlist status under Settings and then Apps, where apps lacking an allowlist are flagged after November 20. Dev Dashboard API logs can be filtered by token type to find non expiring tokens. Network access declarations can be tested in development store previews, and a new tutorial covers running app security checks in CI. Shopify also signalled that bulk queries and bulk mutations will each require their own access scope.
Why it matters
The timing is the story. Shopify is enforcing a security control during the weeks when merchants can least afford an integration failure. For a Plus merchant, the exposure is not your own code but your app portfolio: a fulfilment app, a subscription app, or an ERP connector that misses November 12 stops running bulk operations exactly when volumes peak.
The merchant facing flag is the second shift. App security posture is now visible in the admin, which turns a developer obligation into a procurement signal. Teams that route Admin API traffic through a controlled middleware layer are in the easiest position, because egress already comes from a known set of addresses.
Role-specific impact
- Marketers: Treat November 12 as a freeze boundary. Campaign work depending on bulk catalogue or customer exports through a third party app belongs before it, not during it.
- Developers: Configure the allowlist, test it against recent traffic, then enable enforcement. Add the security checks tutorial to CI, and confirm nothing in your stack calls the Admin API through the Shopify Flow send HTTP request action or an Oxygen hosted storefront, because neither is compatible with an allowlist.
- Store admins: Open Settings and then Apps and note which installed apps already show an allowlist. Raise gaps with the vendor in writing now, not after an export fails.
Use-case example
Real-world scenario
Consider a merchant with 14 installed apps, four of which run nightly bulk operations to sync a 60,000 SKU catalogue and the prior day's orders into an ERP. If one vendor misses November 12, that job starts failing with no storefront symptom. Inventory drifts for a day or two before anyone notices, which during peak means overselling on fast moving lines. A one hour review of 14 vendors is cheap insurance against a stockout that reaches customers.
Implementation checklist
- List every public app you distribute and confirm which call the Admin API or run bulk operations.
- Capture your app's egress addresses as static addresses or CIDR ranges where you have them.
- Enter the allowlist in the Dev Dashboard, test it against recent traffic, then switch enforcement on.
- Filter Dev Dashboard API logs by token type and start the migration to expiring offline access tokens, still due January 1, 2027.
- As a merchant, audit installed apps and ask each vendor to confirm allowlist status in writing before November 12.
- Add app security checks to CI so regressions surface before release, not at a deadline.
FAQ
Q: Does this affect custom apps we built for our own store?
A: It is required only for public apps, not custom or merchant created ones. Shopify still recommends it, and the reasoning holds: an allowlist caps the damage if a token leaks.
Q: What actually happens to our store if a vendor misses the deadline?
A: Nothing visible at first. Existing installs keep working until April 1, 2027. The immediate loss is bulk operations after November 12 and new installs after November 20, so the risk is silent sync failure, not downtime.
Resources
Restrict API access with an IP allowlist
Need guidance? Talk to Makro.