Talk to us

Blog · 20 November 2026 · Rob Sherwood

Shopify Storefront Apps Must Now Declare Network Access

If your Shopify app puts anything on the storefront, it now has to tell Shopify which outside servers it talks to. From 1 December, Shopify will refuse to deploy a new version of an app that hasn't, and that includes custom apps built for client stores.

Back in October I mentioned this setting in passing, in the post about IP allowlists. At the time Shopify only recommended it. On 19 November it posted a changelog entry headed Network access declarations are now required for apps that run on the online store. So it's moved from "nice to have" to "your next deploy fails without it".

What a network access declaration is

It's a short section in your app's shopify.app.toml file called [network_access]. It has two lists.

allowed_sources is the list of HTTPS origins your app's code loads from or sends requests to. Your own API, a CDN you serve scripts from, Google Fonts, that sort of thing. If your storefront code talks to nothing outside Shopify, you write allowed_sources = [] and that counts as a declaration.

allowed_navigation_hosts is optional. It lists the external sites your app links customers to, so those links skip the warning Shopify can show when a customer is about to leave the store.

Shopify's configuration reference currently allows up to 30 entries in each list. Navigation hosts are bare lowercase host names with no scheme, path or wildcard, and every subdomain has to be listed on its own.

Why Shopify wants it

Shopify's own explanation is refreshingly plain. If an attacker gets into an app's server and slips in a script that loads from somewhere else, then, in Shopify's words, "that request stands out".

That's the whole point. A storefront script can see what customers type and where they click. If you've written down the handful of places your app is meant to talk to, anything else is suspicious by definition. Under the bonnet it's built on Content Security Policy, the same browser mechanism you'd use on any website to say "only load scripts from these places".

Which apps are caught

The requirement applies if your app uses any of these:

  • a theme app extension (an app block or app embed)
  • script tags on the online store
  • an app proxy
  • the write_themes scope
  • a web pixel with the write_open_pixels scope

Apps that only write content such as products, menus or metafields aren't affected. Nor are apps whose only storefront presence is a checkout UI extension, web pixels left in the default strict sandbox, custom apps installed only within your own organisation, or apps a merchant created themselves in the Dev Dashboard or the Shopify admin.

So the group that most needs to pay attention is anyone with a custom app installed on a store outside their organisation. That's the usual shape when an agency or freelance developer builds something for a client's store.

The dates

For custom apps installed outside your organisation:

  • 1 December 2026: Shopify rejects deploys of apps that haven't declared their network access.
  • 1 January 2027: installs outside your organisation are blocked until every in-scope app declares it.

Public App Store apps get the same 1 December deploy block plus rejected submissions, and from 1 January they're delisted and can't be newly installed. In both cases, existing installs keep working.

That last bit is reassuring but slightly misleading. The app on your client's store won't stop on 1 December. What stops is your ability to ship a change to it. If a bug turns up in the middle of December trading, you don't want to find out about this requirement then.

Note the wording on the January date as well: "every" in-scope app. As with the IP allowlist rules I covered in last week's post, an old app sitting forgotten in your account can hold up installs of the others.

One more date worth knowing

Shopify's list of upcoming security deadlines also says that from 1 March 2027, script tags stop loading JavaScript for all apps. The suggested replacements are theme app extension app embeds or web pixels. If an older app still injects its storefront code through script tags, adding a declaration buys you December, but it doesn't buy you March. Plan the move to an app embed at the same time.

How I'd get ready

  • List every app in your Partner account and note which ones touch the storefront in any of the ways above. Include the old ones.
  • For each, work out every outside origin the storefront code actually calls. Read the code rather than trusting memory. Fonts, analytics, image hosts and your own API on a different subdomain are the usual surprises.
  • Add them to allowed_sources in shopify.app.toml. If there are none, add the empty list.
  • Create a dev store with the network access testing preview switched on and run shopify app dev against it. The preview only warns, it doesn't block, so you'll see console warnings for anything you've missed without breaking the store.
  • Test on the store's myshopify.com address rather than a theme preview, and don't install other apps on that dev store, because their declarations get merged into the same policy.
  • Run shopify app deploy and release the new version.

None of this is hard. It's a few lines of config and a careful look at what your code talks to. The careful look is the part that takes the time, especially on an app nobody has opened in a couple of years.

It's also worth doing for its own sake. Knowing exactly which outside servers your storefront code depends on is useful on any website, Shopify or not. Every third-party script is someone else's server you're trusting with your customers' browsers, which is part of why I use self-hosted Umami instead of Google Analytics on my own site.

If you're not sure what your app talks to

That's common when the developer who built it has moved on. We build and look after custom Shopify apps and integrations, and our code audit (£250 + VAT) will tell you what an app does, where it runs and which outside services it calls. If you'd rather someone just kept on top of Shopify's changes for you, Look after it starts from £355 a month + VAT.

Either way, if you think one of your apps is affected, get in touch before 1 December rather than after.

Cheers, Rob

Tell us what you've got

It goes straight to Rob and Jase. You'll hear back from one of us, usually the same day, and we'll tell you honestly whether we're the right people.

Just want it checked? Code audit, £250 + VAT