See all services → Shopify Plus Partner
Action Required Developer

Audit Your Installed Apps For Shopify IP Allowlists

Public apps without an IP allowlist lose bulk operations on November 12 and are delisted from the App Store on November 20. Custom and merchant-created apps are exempt. Here is how to audit your app portfolio before the dates land.

Executive summary

What changed

Shopify now requires each public app to declare the networks its Admin API tokens may be used from. With enforcement on, Shopify inspects the source address of every GraphQL and REST Admin API request made with that app's tokens. Requests from outside the list fail with a 403, as do requests whose source address Shopify cannot confirm.

The enforcement sequence is staged. From November 12, 2026 at 11:59 PM ET, bulk queries and mutations from public apps without an allowlist fail to execute. From November 20, those apps are delisted, blocked from new installs, and flagged to merchants in the admin. From January 15, 2027, merchants see a warning. From April 1, 2027, Shopify rejects the app's Admin API requests outright.

Custom apps and apps a merchant created in the Dev Dashboard or admin are not affected. Apps still calling the Admin API from merchant infrastructure are expected to move to an architecture that limits token exposure, and can request a deadline extension.

Why it matters

For enterprise merchants, this is an app portfolio risk question, not a development task. The November 12 bulk operations cutoff is the sharp edge. Bulk operations are how serious integrations move catalogue, inventory, and order data at volume, so the apps most likely to be affected are the ones holding your ERP, OMS, and PIM in sync. A failure there is invisible on the storefront and expensive in the warehouse.

There is a procurement angle too. Allowlist status is now surfaced to merchants in the admin, which makes it a cheap, objective signal of how seriously a vendor treats security. Teams that run integrations through purpose built custom apps rather than a stack of off the shelf connectors carry less of this exposure, because custom apps are exempt and their egress is already known.

Role-specific impact

Use-case example

Real-world scenario

A multi store merchant runs 11 public apps across three regional stores. Two of them, a fulfilment connector and a product feed app, use bulk operations to reconcile roughly 250,000 inventory records nightly. If either misses November 12, reconciliation stops without a storefront error, and the first symptom is an oversell on a top seller days later. A two hour vendor audit now, with a named owner per app, beats a peak season inventory correction across three stores.

Implementation checklist

  1. Export your installed app list per store and mark which came from the App Store, since those are the public apps in scope.
  2. Identify which of those apps run bulk operations or feed an ERP, OMS, or PIM, and treat those as November 12 priorities.
  3. Ask each vendor to confirm in writing that an allowlist is configured and enforced, with a date.
  4. For apps you build and distribute, configure the allowlist in the Dev Dashboard, test it against recent traffic, then turn enforcement on.
  5. If your app calls the Admin API from merchant infrastructure, submit an extension request and plan the architecture change rather than relying on the extension.
  6. Add sync monitoring and alerting so a silent bulk operation failure is caught within hours, not days.

FAQ

Q: Will our storefront go down if an app misses the deadline?

A: No. Existing installs keep working, and full Admin API rejection begins only on April 1, 2027. The near term loss is bulk operations from November 12 and new installs from November 20.

Q: Do our own custom apps need an allowlist?

A: No, custom and merchant created apps are exempt. It is still worth configuring, because it limits what an attacker can do with a leaked token.

Resources

Restrict API access with an IP allowlist

Need guidance? Talk to Makro.