On this page
Why this happens or what changed
The rule targets cross-organization custom app installations, a common agency and integration pattern. It does not apply to merchant-created apps in admin or the Dev Dashboard, or apps installed only within the owning organization. Public apps have their own deadlines. Shopify is reducing the risk that a leaked Admin API token can be used from an arbitrary network.
Practical fix
- Inventory the owning organization and installation organizations for each custom app; do not infer ownership from the store name.
- In Dev Dashboard → app → Settings → IP allowlist, enumerate every production egress path: web server, queue worker, scheduled job, integration platform, and deployment environment.
- Prefer fixed IPs or CIDR ranges for known egress. For dynamic hosting, consider provider ASN plus country restrictions; evaluate the broader exposure.
- Test against recent API traffic before enabling enforcement. Ensure retries and disaster-recovery regions have been considered.
- Repeat for every cross-organization custom app. Shopify warns that, starting January 1, one noncompliant app can affect your ability to install any app outside your organization.
Production considerations
A Shopify app’s inbound webhook endpoint and its outbound Admin API caller are different network paths. Allowlisting the server receiving Shopify webhooks does not automatically cover the worker sending GraphQL calls. Keep a documented emergency change process for egress changes; do not add broad hosting networks merely to silence a 403.
How to test this
- Confirm the app owner and the organization of each installation.
- From each production egress path, execute a safe, scoped Admin GraphQL read.
- From an intentionally unlisted test egress, confirm requests are rejected with HTTP 403 after enforcement.
- Run a representative scheduled job and a webhook-triggered downstream API call.
- Verify a new cross-organization install can complete after the allowlist is configured, without exposing production credentials in test logs.

