Quick answer: Shopify public apps must have an IP allowlist by November 20, 2026 at 11:59 PM ET or they can be delisted from the App Store and blocked from new installs. The earlier November 12 deadline for bulk operations has already passed. Agency or partner-owned custom apps installed on stores outside the owner’s organization also need an allowlist for new installs from November 20; existing outside-organization installs have a January 1, 2027 deadline.[2][3]
Do this now: Inventory every production system that sends Shopify Admin API requests, identify its outbound IP/CIDR or hosting-provider ASN, configure the allowlist in the Dev Dashboard, run Shopify’s recent-traffic test, enable enforcement, then prove an allowed request succeeds and a deliberately disallowed request returns HTTP 403.[4]
November 2026 deadline matrix
| App or request type | Deadline | What happens without an allowlist |
|---|---|---|
| Public app bulk queries and mutations | November 12, 2026, 11:59 PM ET | Bulk operations fail |
| All other covered public apps | November 20, 2026, 11:59 PM ET | App Store delisting, no new installs, and a flag in merchant Settings > Apps |
| Custom app: new install outside the owner’s organization | November 20, 2026, 11:59 PM ET | New outside-organization install is blocked |
| Custom app: existing install outside the owner’s organization | January 1, 2027, 11:59 PM ET | Allowlist becomes required for existing outside-organization installs |
| Public app merchant warning | January 15, 2027 | Merchants using the app see a Shopify-admin warning |
| Public app general Admin API enforcement | April 1, 2027 | GraphQL and REST Admin API requests are rejected |
Shopify’s rollout is staged. Existing public-app installs do not all stop on November 20, but affected bulk jobs may already be blocked, new installs can be blocked, and general GraphQL and REST Admin API rejection is scheduled for April 1, 2027.[1][4]
Who needs to act?
Public app developers
All public apps are covered by Shopify’s public-app requirement. The configuration belongs to the app developer, not the merchant using the app.[2]
Agencies and partners with custom apps
A custom app is covered when it is installed on a store outside the organization that owns the app. New installs need the allowlist from November 20, while existing installs have until January 1, 2027. Apps installed only within their owner’s organization and apps created directly by merchants in the Dev Dashboard or Shopify admin are excluded from this custom-app rule.[3]
Shopify merchants
A merchant cannot configure another company’s public app allowlist. The practical task is to review Settings > Apps, identify critical apps, and request written confirmation from each vendor that its allowlist and bulk operations are compliant. Shopify says apps without the required public-app allowlist are flagged in that screen after November 20.[1][4]
Static IP, CIDR or ASN: which should you use?
Use the narrowest rule that covers every legitimate outbound Admin API request:
- Single static egress IP: add that public IP.
- Several fixed addresses: add each address or the smallest valid CIDR ranges.
- NAT gateway: add the gateway’s public egress addresses, not private server addresses.
- Serverless or dynamic egress: add the hosting provider’s ASN and restrict it to only the countries where the app runs.
- Mixed infrastructure: combine fixed IP/CIDR entries with ASN entries.
Shopify supports up to 250 IP addresses or CIDR ranges and up to 10 public ASNs. IPv4 ranges must be /16 or narrower, IPv6 ranges /32 or narrower, and only public addresses are accepted. Shopify warns that an ASN is shared with other customers, so static IP rules are safer when available; country restrictions should be used with ASN entries.[4]
Do not guess your egress network
Build the list from infrastructure configuration, NAT or load-balancer settings, hosting-provider documentation, and Shopify Dev Dashboard API logs. Include every production path that holds an app token: web workers, queues, scheduled jobs, regional failover, data pipelines and approved third-party automation. Do not copy a provider-wide ASN from an unsourced forum post.
Step-by-step Shopify IP allowlist setup
- Open the app in Shopify Dev Dashboard. Go to Settings, find IP allowlist, and select Manage.
- Enter fixed networks first. Add individual public IPs or CIDR ranges under IP addresses or CIDR ranges.
- Add dynamic networks only when needed. Enter the hosting provider ASN under Networks (ASN) and limit it to the countries where the app actually runs.
- Run the built-in traffic test. Under Test against recent traffic, select Run test. Shopify checks whether addresses seen in the previous 30 days would be blocked.
- Resolve every legitimate miss. Identify the workload behind each unexpected address. Add it only if it is authorized; investigate it if it is not.
- Enable enforcement. Turn on Enforce IP allowlist and save.
- Run a positive test. From each production egress path, make a low-risk authenticated GraphQL Admin API request and confirm success.
- Run a negative test. From a controlled network outside the allowlist, use a test-shop token and confirm Shopify rejects the request with HTTP 403.
- Exercise background paths. Run one representative queue worker, webhook-triggered job, scheduled task and bulk operation where applicable.
- Record the owner and rollback condition. Save the approved networks, evidence, test time and responsible engineer in the deployment record.
These steps follow Shopify’s documented flow. The recent-traffic result can take a few minutes to include the newest calls, so a clean dashboard test is not a substitute for active positive and negative API tests.[4]
Copy-paste pre-enforcement inventory
App name:
Shopify app type: public / custom
Owning organization:
Stores outside owner organization: yes / no
Admin API clients:
- Web/API service:
- Queue workers:
- Scheduled jobs:
- Bulk operations:
- Regional/failover systems:
- Approved third parties:
Static public egress IPs/CIDRs:
Dynamic hosting provider ASNs:
Allowed countries for ASN rules:
IPv6 egress present: yes / no
Last 30-day traffic test completed:
Allowed-path API test completed:
Outside-allowlist 403 test completed:
Bulk operation test completed:
Rollback owner:
Evidence link:
Example validation request
Use a development store and a test token with only the permissions needed for the query. Do not paste production tokens into shell history, tickets or screenshots.
export SHOP_DOMAIN="your-development-store.myshopify.com"
export SHOPIFY_TOKEN="read-from-your-secret-manager"
curl --silent --show-error --fail-with-body \
--request POST \
"https://${SHOP_DOMAIN}/admin/api/2026-10/graphql.json" \
--header "Content-Type: application/json" \
--header "X-Shopify-Access-Token: ${SHOPIFY_TOKEN}" \
--data '{"query":"query { shop { name } }"}'
Run it once from an allowed production-like egress and once from a controlled disallowed network. The second request should return 403 after enforcement. Shopify documents that GraphQL and REST Admin API requests from an address it cannot verify, or from outside the configured rules, fail with 403.[4]
Serverless and dynamic-IP checklist
If the app runs on serverless infrastructure, do not keep adding short-lived addresses one by one. Shopify supports allowlisting by autonomous system number for dynamic egress, but this is broader than a fixed-IP rule.[1][4]
- Confirm the ASN from the hosting provider’s current documentation or from addresses observed in Shopify logs.
- Check whether the provider uses more than one ASN for the regions serving the app.
- Restrict ASN entries to the app’s actual countries.
- Keep fixed NAT gateway or dedicated egress IPs as the preferred long-term design where practical.
- Retest after region, hosting plan, networking or failover changes.
- Monitor for unexpected API source networks after deployment.
Compatibility traps that can cause a 403
Shopify says an IP allowlist does not work for access tokens used by Shopify Flow’s Send HTTP request action or for GraphQL Admin API requests sent from an Oxygen-hosted storefront because Shopify cannot confirm those source addresses. Dev preview requests on development stores and direct API access from embedded app pages or POS UI extensions are not rejected by this control.[4]
Before enabling enforcement, search the codebase and automation inventory for token use outside the core backend. A 403 after rollout may indicate a legitimate workload missing from the list, an unsupported request path, an incorrectly entered CIDR, missing IPv6 coverage, an incomplete ASN/country combination, or a request that is correctly being blocked.
403 troubleshooting sequence
- Confirm the failure is an Admin API 403 and capture the request ID, timestamp and workload—never the token.
- Check the source system’s current public egress IPv4 and IPv6 addresses.
- Compare the address with the configured CIDRs.
- If using an ASN rule, verify the source ASN and its geolocated country match the configured rule.
- Check whether a NAT, region, provider or failover change altered egress.
- Review Dev Dashboard API logs and rerun the recent-traffic test.
- Test a minimal query from a known allowed network.
- Add only verified legitimate infrastructure; do not open a broad range simply to clear the error.
- If the path is one Shopify documents as incompatible, redesign it rather than weakening the allowlist.
Merchant vendor questionnaire
Send this to vendors supporting inventory, fulfillment, subscriptions, ERP, reporting or other critical Shopify workflows:
Shopify’s November 2026 IP-allowlist requirement is approaching.
Please confirm in writing:
1. Is your app a public app or an outside-organization custom app?
2. Is IP-allowlist enforcement enabled for all Admin API infrastructure?
3. If you use bulk operations, did you validate them after the November 12 deadline?
4. Have you tested allowed requests and intentional 403 rejection from a disallowed network?
5. Is any merchant action required?
6. What is the incident contact if API or background jobs fail?
Do not uninstall a working app solely because it shows a warning. First confirm the vendor’s status, test the business workflow, review data-export and rollback options, and replace an app only through a controlled migration.
Frequently asked questions
Does every Shopify store owner need to enter IP addresses?
No. The requirement is configured by developers for covered public apps and for custom apps installed outside the organization that owns them. Merchants should audit critical vendors but cannot configure the network rules for someone else’s public app.[2][3]
Will existing apps stop working on November 20?
Not all API traffic stops on November 20. Public apps without an allowlist can be delisted, blocked from new installs and flagged; existing installs continue temporarily. Bulk operations may already fail, merchant warnings are scheduled for January 15, 2027, and general Admin API rejection is scheduled for April 1, 2027.[4]
What if my app uses dynamic or serverless IP addresses?
Use the hosting provider’s ASN and restrict it to the app’s operating countries, or move to stable egress IPs. Shopify supports IP and ASN entries in the same allowlist.[4]
How do I verify enforcement?
Run Shopify’s 30-day recent-traffic test, enable enforcement, confirm API success from each approved egress path, and verify a controlled request from outside the allowlist returns 403.[4]
Are merchant-created custom apps affected?
Apps created by merchants in Shopify admin or the Dev Dashboard are listed as unaffected by these public-app and outside-organization custom-app requirements. Shopify still recommends allowlists for apps used only within their owner’s organization.[2][4]
Can one noncompliant custom app affect other partner apps?
Yes. Shopify says that from January 1, 2027, a partner with multiple apps can be prevented from installing any app on stores outside its organization if one covered app lacks an allowlist.[3]
Last checked: November 18, 2026. This is a source-backed implementation checklist, not evidence that any specific third-party app has completed its migration. Validate your own infrastructure and current Shopify dashboard before enforcement.
Sources
- Shopify app security update
- Shopify public-app allowlist requirement
- Shopify outside-organization custom-app requirement
- Shopify IP allowlist setup documentation