Shopify’s Security Rules Now Cover Agency-Built Custom Apps

Shopify is extending mandatory IP allowlists to custom apps installed on stores outside the organization that owns them. New installations need an allowlist from 11:59 p.m. Eastern on November 20. Existing installations must comply by 11:59 p.m. Eastern on January 1, 2027.

If an agency built your inventory connector, reporting tool, or fulfillment integration, “it's a custom app” no longer exempts it.

What Shopify Announced

Shopify's November 11 announcement expands requirements that previously applied to public apps.

Which Custom Apps Are Affected

The rule targets custom apps installed outside their owner's organization, which describes most agency-built integrations. Two categories are excluded:

  • Merchant-created apps
  • Apps installed only within the owner's own organization

What the app does tells you nothing about which rule applies. Ownership and installation location decide it.

The Two Deadlines

New installations need a configured allowlist from tonight, November 20, at 11:59 p.m. Eastern. Existing installations have until January 1 at 11:59 p.m. Eastern.

One Bad App Can Block an Agency's Whole Portfolio

Shopify warns that from January 1, a single noncompliant app can prevent its owner from installing any of its apps on stores outside its organization.

That turns this into an agency-wide problem. Your provider might configure your connector correctly and still lose the ability to install anything new because another client's app was missed.

How This Differs From Public App Rules

We covered Shopify's public app token deadlines earlier this month. This expansion is separate.

Public Apps After November 20

Shopify's November 14 clarification says noncompliant public apps calling the Admin API will be delisted and blocked from new installations after November 20. Existing installations keep working.

Bulk Operations Have Their Own Rules

Bulk queries and mutations carry separate enforcement. Partner-created apps must enable bulk operations through API access requests, and that access lapses after 31 days without starting a bulk query or mutation.

A daily sync working fine says nothing about an infrequent bulk export. Test the workflows you actually rely on, including the ones you only run occasionally.

Questions to Ask Your Agency

You do not need access to other clients' systems. You need a clear, accountable answer.

Confirm Ownership and Scope

Ask your provider to confirm:

  • Which organization owns the app
  • Whether your installation falls under the new requirement
  • Whether they have reviewed every other externally installed app they own

Record the answers next to the app's support contact and the business process it runs. Do not rely on a former employee's memory of who built what.

Ask About Specific Workflows

“Can we still export the full catalog?” gets a more useful answer than “Is the app compliant?” Name the actual job you need working.

Test the Processes That Run in the Background

An allowlist restricts which network locations can make requests on an app's behalf. It has to match every piece of infrastructure making those requests, including scheduled workers and backup environments used during incidents.

Your role is to request evidence, not guess server addresses.

Check Each Integration Against Real Data

For an inventory connector, compare the last successful update time against a sample of stock quantities. For a reporting integration, confirm a fresh export contains current records. For any agency deployment, ask how a hosting change will flow through to the security configuration.

Keep Tests Read-Only

A mass catalog rewrite is a risky way to test connectivity in the middle of holiday trading. Use read-only checks wherever possible.

Capture the First Error

When something fails, save the time, job identifier, and error message before retrying. Repeated retries can bury the first useful failure.

Keep Credentials Protected

An allowlist does not remove the need to protect access tokens. The PHP2Shell vulnerability showed how exposed integration credentials put ecommerce accounts at risk, though that incident is unrelated to why Shopify introduced this rule.

Never send credentials in ordinary email or support screenshots. Use your provider's approved support process.

What to Do Now

Get written ownership and readiness confirmation for any installation planned in the coming days. For existing externally owned custom apps, schedule testing well before January rather than during the holiday shutdown.

Give every critical integration one internal owner, one vendor escalation contact, and one documented fallback. Close the task only when the business workflow actually succeeds, not when someone says the setting is switched on.

Alexa Alix

Meet Alexa, a seasoned content writer with a flair for transforming intricate concepts into engaging narratives across an array of industries. With her passions extending to nature and literature, Alex is adept at weaving unique stories that resonate. She's always poised to collaborate and conjure compelling content that truly speaks to audiences.

Related Articles