Executive summary
- What: the IP allowlist deadline for public apps and for custom apps installed outside your organization has passed, and four further requirements land on December 1 and January 1.
- Why: non-compliant public apps are delisted and flagged to merchants, and from January 1 an app without an allowlist cannot stay installed on a store outside the organization that built it.
- Who: any merchant running a partner app, agency-built custom app, or in-house integration holding Admin API tokens, usually the ERP, OMS, and middleware connections.
What changed
An IP allowlist constrains where your app access tokens can be used. Shopify checks the source address of every GraphQL and REST Admin API request made with those tokens, and you can allow specific addresses and ranges, whole networks by autonomous system number, or both.
Public apps lost bulk query access on November 12, 2026, then on November 20 were delisted, blocked from new installs, and flagged to merchants under Settings and then Apps. Existing installs keep working, with an admin warning from January 15, 2027, and relisting is automatic once an allowlist is added. For custom apps, an allowlist has been required since November 20 to install on a store outside your organization, and from January 1, 2027 every such app already installed needs one.
Four requirements follow. Apps running code on the online store must declare allowed_sources under network_access. Custom apps created on or after December 1 must use expiring offline access tokens. Apps reading abandoned checkout recovery URLs need level 2 protected customer data access, from December 1 for public apps and January 1 for partner custom apps. Merchant custom apps must now explicitly enable bulk queries and mutations.
Why it matters
The exposure sits in exactly the integrations enterprise merchants depend on most and audit least. A custom app wired to NetSuite, Dynamics, or a middleware layer was often configured years ago by someone who has since left, and nobody opens it until an order sync stops. Two of these requirements can stop that sync: a missing allowlist after January 1, and the bulk operations toggle, which silently blocks the queries most catalog and inventory synchronisation depends on.
One trap deserves naming. If your integration runs on infrastructure with dynamic outbound addresses, an allowlist pinned to specific addresses fails the moment your host reassigns them, and the symptom is a 403 that reads like an authentication fault. Allow the network by autonomous system number instead. For the wider control picture, see our overview of security and compliance on Shopify Plus.
Role-specific impact
- Marketers: audit anything reading abandoned checkout recovery URLs, usually cart recovery and lifecycle email tooling, which loses those URLs without approved level 2 access.
- Developers: add allowlists, declare allowed_sources for online store code, migrate to expiring offline tokens, and enable bulk operations where integrations need them.
- Store admins: check Settings and then Apps for compliance flags, confirm multi-factor authentication on every account with app access, and chase vendors of flagged apps for a remediation date.
Use-case example
Real-world scenario
A distributor runs three storefronts fed by one agency-built custom app pushing inventory from Epicor every fifteen minutes, installed on two stores outside the agency organization with no allowlist. The team allowed their two static egress addresses, enabled bulk operations, and rotated to expiring offline tokens in under a day. Waiting past January 1 would have blocked both external installs, taking inventory accuracy across roughly 14,000 SKUs with them.
Implementation checklist
- Inventory every app holding Admin API tokens on each store, and check Settings and then Apps for compliance flags.
- Add an allowlist to each app you control, using specific addresses for static egress and autonomous system numbers for dynamic.
- Confirm any custom app installed outside your organization has an allowlist before January 1, 2027.
- Declare allowed_sources under network_access for online store code, and migrate custom apps to expiring offline tokens.
- Enable bulk queries and mutations for merchant custom apps that need them, then re-test catalog and inventory syncs.
- Request level 2 protected customer data access where abandoned checkout URLs are read, and enforce multi-factor authentication on every account with app access.
FAQ
Q: Our app is installed and working. Can this wait until next quarter?
A: Not safely. Existing installs keep working, but merchants see an admin warning from January 15, 2027, and allowlists become mandatory on January 1 for custom apps installed outside the building organization.
Q: What does a failure look like once enforcement applies?
A: Admin API requests from outside the allowlist return a 403, including those whose source address Shopify cannot confirm. Because that reads like a credentials problem, brief whoever monitors your integrations so a network-origin failure is not misdiagnosed as an expired token.
Resources
IP allowlist configuration in the Dev Dashboard
Need guidance? Talk to Makro.