Executive summary
- What: Custom apps installed on stores outside the organization that owns them must have an IP allowlist, enforced for new installs from November 20, 2026 and for existing installs from January 1, 2027.
- Why it matters: Agency-built and vendor-built custom apps are the common case here, and from January 1, 2027 a single non-compliant app blocks your ability to install any app on outside stores.
- Who should act: Partners and agencies who own custom apps deployed to client stores, and merchants relying on a third party's custom app for integrations.
What changed
Shopify checks the source IP of GraphQL and REST Admin API requests made with an app's tokens and rejects anything outside the allowlist with a 403. Two dates apply to custom apps installed outside the owning organization: from November 20, 2026 at 11:59 PM ET an allowlist is required for new installs, and from January 1, 2027 at 11:59 PM ET for existing installs too.
Three categories are unaffected: apps installed only on stores inside your own organization, which Shopify still recommends allowlisting; apps a merchant creates themselves in the Dev Dashboard or the admin; and public apps, which carry a separate and more aggressive timeline.
The multi-app rule deserves emphasis. From January 1, 2027, one app without an allowlist affects your ability to install any of your apps on outside stores. Compliance is assessed across your portfolio, not per app.
Why it matters
The security argument is sound: a leaked token can be used from anywhere, and an allowlist reduces a credential leak from a total compromise to a network-bound one. For enterprise merchants, a vendor's token spill stops being your incident by default.
The risk sits in the exceptions, and they are easy to miss. An allowlist does not work with access tokens used by the Shopify Flow send HTTP request action, or with Admin API requests from a storefront hosted on Oxygen. Shopify cannot confirm the source address of either, so it rejects them. If a client workflow depends on Flow calling an endpoint with app credentials, turning on enforcement breaks it, and the failure will look like an intermittent integration fault rather than a policy decision. Requests that are never rejected include dev preview on development stores and direct API access from embedded app pages and POS UI extensions. Mapping these paths before enforcement is the difference between a quiet change and a production incident, which is why custom app inventory belongs on a standing schedule rather than a one-off, as discussed in how custom Shopify apps can elevate your store.
Role-specific impact
- Marketers: no direct impact, but campaign tooling that reaches Shopify through a custom app belongs on the audit list.
- Developers: determine whether your egress addresses are static or dynamic, configure CIDR ranges for the former and provider ASNs for the latter, and test against recent traffic before enforcement.
- Store admins: ask every vendor with a custom app on your store to confirm in writing that their allowlist is configured ahead of January 1, 2027.
Use-case example
Real-world scenario
An agency maintains custom apps on 18 client stores, all outside its own organization. Fourteen run on fixed infrastructure and were straightforward: list the static egress addresses as CIDR ranges. Two run on serverless functions and needed provider ASNs scoped by country. The last two depended on a Shopify Flow send HTTP request step using app credentials, which an allowlist cannot support, so that logic moved into the app. The audit took two days. Finding the Flow dependency on January 2 would have cost far more.
Implementation checklist
- List every custom app you own that is installed on a store outside your organization.
- For each app, identify the egress IP addresses or ranges it uses to call the Admin API.
- Configure static addresses as CIDR ranges in the Dev Dashboard, using public addresses and the NAT gateway address where applicable.
- For dynamic addresses, add your hosting provider's ASNs and limit them to the countries the app runs in.
- Search for Shopify Flow send HTTP request steps and Oxygen-hosted Admin API calls that use app tokens, and re-architect them, because an allowlist cannot cover them.
- Validate the allowlist against recent request logs before enforcement begins.
- Complete new-install compliance by November 20, 2026 and portfolio-wide compliance by January 1, 2027.
FAQ
Q: Do apps we only install on our own organization's stores need this?
A: Not as a requirement, but Shopify highly recommends it, and the protection is identical.
Q: What happens if one of our apps misses the deadline?
A: From January 1, 2027, a single app without an allowlist affects installs of every app you own on stores outside your organization. Treat it as a portfolio-level deadline.
Resources
Restrict API access with an IP allowlist
Need guidance? Talk to Makro.