Skip to main content

Shopify's IP Allowlist Deadline Is an Integration Ownership Test

App servers reaching a Shopify store through an IP allowlist gateway, while a request from an unlisted machine is blocked

An app can still be installed after November 20 and still be on a path to losing its Admin API access.

That gap between an App Store listing and a working integration is where enterprise commerce teams need to pay attention. Shopify’s new IP-allowlist requirement is being described as a developer task. For merchants, it is an integration-continuity question: which applications can access orders, inventory and customer data, who owns their credentials, and what happens when those connections fail?

What Shopify is changing on November 20

Shopify is requiring public applications that call the GraphQL Admin API or REST Admin API to configure an IP allowlist.

The general deadline is November 20, 2026, at 11:59 PM Eastern Time.

A public application without an allowlist will be delisted from the Shopify App Store, prevented from receiving new installations and flagged in the merchant’s Shopify admin.

There is an earlier deadline for applications using bulk operations. November 12 has already passed. Shopify is enforcing the requirement against bulk queries and mutations from public applications without an allowlist.

The distinction matters: November 20 does not mean every existing installation immediately stops working.

Shopify says existing installations continue working, with Admin API requests from non-compliant applications scheduled to fail from April 1, 2027.

The official public-app announcement and 14 November security update should be the reference for implementation decisions.

Which Shopify applications are affected?

The requirement is not identical for every application type.

Public applications using the Admin API: The IP allowlist is required by November 20. Bulk-operation applications had the earlier November 12 deadline.

Custom applications installed outside their owning organization: Shopify has introduced a separate requirement. New installations on external stores need an allowlist from November 20, 2026. Existing installations need one by January 1, 2027.

Applications installed only within their own organization: They are unaffected by this particular mandatory timeline.

Applications created by merchants in the Shopify admin or Dev Dashboard: They are also excluded from the mandatory requirements described above, although Shopify recommends IP restrictions for other applications too.

A retailer should therefore not ask simply whether an app is public or private. It should establish who owns the app, where it is installed and whether it makes Admin API calls.

What does an IP allowlist actually protect?

An IP allowlist restricts the network locations from which an application’s access token can be used to make Shopify Admin API requests.

Consider a typical inventory integration.

A third-party application stores an Admin API token and periodically reads or updates product and inventory information. If that token leaks through a log, exposed configuration or compromised dependency, an attacker may attempt to reuse it from another machine.

An IP allowlist narrows that exposure.

Shopify rejects covered API requests originating outside the permitted IP addresses or networks, returning a 403 response.

Importantly, this concerns the application’s outbound network connection to Shopify. It is not the merchant’s office IP address, the shopper’s IP address or simply a list of addresses from which webhooks may arrive.

Shopify’s technical guide explains the control and its verification process.

Static IP addresses or ASN: which should an app use?

The implementation depends on where the application runs.

For applications using predictable outbound network addresses, the developer can configure specific public IP addresses or CIDR ranges.

Serverless and dynamic hosting environments are more complicated because outbound addresses may change.

Shopify introduced ASN-based allowlisting to accommodate this model.

On November 11, Shopify also expanded the configuration to support IP addresses and ASNs together.

The current limits include:

  • Up to 250 IP addresses or ranges.
  • Up to 10 ASNs.
  • Country restrictions for up to 10 countries.

There is an important security trade-off.

A specific IP address restricts access to a narrower set of infrastructure. An ASN covers addresses announced by the hosting provider’s network, potentially including addresses used by other customers of that provider.

Shopify itself recommends using specific IP addresses wherever possible and reserving ASN-based access for dynamic infrastructure.

For an enterprise integration, the developer should be able to explain why the chosen approach is appropriate, which regions are included and how changes in outbound infrastructure are managed.

What merchants should ask their Shopify app vendors

This is where the platform announcement becomes an enterprise architecture issue.

A retailer may have applications responsible for product synchronisation, shipping rates, tax calculation, promotions, customer reviews, inventory updates, fulfilment notifications or marketplace order ingestion.

A single broken integration can create operational work well beyond the application itself.

Before the November 20 deadline, ask each critical vendor the following questions.

1. What type of application are we running?

Is it a public Shopify app, a custom application installed outside the owning organization, or an application created internally by the merchant?

Which requirement applies?

2. Does the application use the Admin API?

Ask whether it uses GraphQL Admin API or REST Admin API, and whether any workflows depend on bulk queries or bulk mutations.

If bulk operations are involved, ask for confirmation that they are currently functioning under the new restrictions. Their earlier deadline has already passed.

3. Has the IP allowlist been configured?

Do not settle for a general statement that the application is secure.

Ask whether its outbound IP addresses or networks have been configured in the Shopify Dev Dashboard and whether enforcement is enabled.

4. Is the application using static IPs or ASNs?

If it uses ASN-based restrictions, ask which provider and countries are included.

Ask why this is necessary instead of using narrower fixed egress addresses.

5. Has the configuration been tested?

Shopify documents a practical verification approach: make a GraphQL Admin API request from outside the permitted ranges and confirm that it fails with a 403 response.

The application should also monitor unexpected 403 responses from its own servers because they can indicate missing outbound addresses.

6. What happens when an API connection fails?

This is often the most important question for the merchant.

If an inventory update fails, is the event retained? Can the operation be retried safely? Is there a dead-letter queue? Can the team replay the failed operation without creating duplicate changes?

For order integrations, the same questions apply to order creation, fulfilment updates, cancellation and returns.

7. Who owns incident communication?

The vendor should identify the engineering contact, expected notification process, escalation route and merchant responsibilities.

A security setting without an operational response process is incomplete protection.

The failure scenario matters more than the checkbox

Consider a retailer with three integrations:

  • An application synchronising product catalogue changes.
  • An application importing orders from an external marketplace.
  • An application updating stock availability across locations.

If an application relies on bulk operations and has not configured the required network restriction, its bulk jobs may already be blocked.

If a normal Admin API call originates from an address missing from the allowlist, it can also fail.

The operational consequences depend on what the application does with that failure.

A sound integration should make the failure visible, retain the business event where appropriate, avoid unsafe duplicate processing and provide a controlled recovery process.

Our view is that merchants should test the whole operating path, not just whether the allowlist setting appears enabled.

The test should cover successful authorised requests, rejected requests, monitoring, recovery and reconciliation against the source system.

A 403 caused by an unrecognised egress address is not something to hide behind an unlimited retry loop. The underlying network configuration must be corrected before the operation is replayed.

Do not confuse IP allowlisting with expiring access tokens

Shopify is tightening more than one aspect of app security.

IP allowlisting controls where an application’s access token can be used.

Expiring offline access tokens limit how long a leaked credential remains valid.

These are separate requirements with separate enforcement dates.

Shopify lists January 1, 2027 for the expiring offline access-token requirement, with subsequent Admin API enforcement on April 1, 2027.

Neither control replaces the rest of an application’s security responsibilities.

Least-privilege API scopes, secure credential storage, webhook authentication, tenant isolation, dependency management, monitoring and incident response still matter.

Shopify’s app security documentation covers these areas.

An IP allowlist is a useful security boundary, not a security certification.

What this means for enterprise commerce architecture

Shopify’s change highlights a question that applies to every commerce platform: who is responsible for the security and operational continuity of the integrations connected to the system of record?

The application vendor owns its code, hosting configuration and credentials.

The merchant owns the decision to grant access, the business criticality assessment and the continuity plan.

The implementation partner may be responsible for the custom integration and its deployment.

Those responsibilities need to be explicit.

Our recommendation is to maintain an integration register containing at least:

  • Application and vendor name.
  • Application distribution type and owning organization.
  • Admin API access and scopes.
  • Bulk-operation dependencies.
  • Egress IP or ASN configuration status.
  • Access-token expiry model.
  • Last successful security verification.
  • Business workflows dependent on the integration.
  • Failure recovery and reconciliation procedure.
  • Vendor escalation and incident contact.

This is more useful than recording a simple compliant/non-compliant flag.

It shows what the application can affect and what the business should do if the connection becomes unavailable.

The practical takeaway

The November 20 deadline is close, but the larger issue is not the deadline itself.

It is the number of commerce-critical integrations that operate without clearly documented ownership, access controls and recovery procedures.

Ask vendors for evidence. Verify the application type and API dependencies. Test the network restrictions. Confirm what happens when an integration fails.

For a separate but related question, see our Shopify Agentic Storefronts guide, which examines how merchants should govern AI-channel access, checkout and post-purchase responsibility.

A commerce integration should be judged not only by what it connects, but by how safely and predictably it operates when something goes wrong.

Frequently asked questions

Does Shopify’s IP allowlist requirement apply to every app?

No. The mandatory requirement applies to public applications using the GraphQL Admin API or REST Admin API. Custom apps installed outside their owning organization have a separate requirement. Merchant-created apps and apps installed only within their owning organization are excluded from these mandatory timelines.

Will existing Shopify apps stop working on November 20?

Not immediately. Public apps without an allowlist may be delisted and blocked from new installations, while existing installations continue working until later API enforcement. Shopify lists April 1, 2027 as the date when affected Admin API requests will fail. Bulk operations had an earlier November 12 deadline.

Can serverless applications comply with IP allowlisting?

Yes. Shopify supports ASN-based allowlisting for dynamic outbound networks. Specific IP addresses are preferable where practical because ASN rules can include addresses used by other customers of the hosting provider.

Do merchants configure the IP allowlist themselves?

The application developer or owner configures the application’s allowed networks in the Shopify Dev Dashboard. Merchants should verify the application’s security status, ask the vendor for evidence and establish an operational recovery plan.

Is IP allowlisting the same as expiring offline access tokens?

No. IP allowlisting restricts where API credentials can be used. Expiring offline access tokens restrict how long credentials remain valid. Shopify has separate enforcement dates for these controls.

What should merchants do if a critical app is flagged?

Contact the application vendor, establish whether the application uses the affected Admin API endpoints, request its remediation timeline and confirm that critical workflows have a tested recovery process.

Do not uninstall an application without first understanding its business dependencies.

tailoredd Platform Engineering
Written by

tailoredd Platform Engineering

Commerce Architecture and Integrations

The tailoredd Platform Engineering group covers architecture, migration strategy, and systems integration topics for enterprise commerce environments.

View Profile →