Executive summary
- What: Apps that execute code on the online store must declare every outbound server in the [network_access] section of shopify.app.toml. Shopify starts rejecting deploys on December 1, 2026.
- Why: An injected storefront script can pull code from any host. A declared source list gives Shopify a baseline, so unexpected requests get spotted instead of silently served to buyers.
- Who: Merchants relying on public apps, or partner-built custom apps installed beyond the developer's organization, that use theme app extensions, script tags, app proxies, write_themes, or non-sandboxed web pixels.
What changed
Network access declaration has moved from recommendation to gate. An app in scope adds an allowed_sources list naming the APIs, CDNs, and other hosts its storefront code talks to. An optional allowed_navigation_hosts list names sites the app sends shoppers to, sparing buyers an exit warning on links the app owns. An app that contacts nothing external declares an empty list, which still counts.
Enforcement runs in two stages. From December 1, 2026, Shopify rejects deploys and App Store submissions for undeclared public apps, and merchants see an admin warning, though released versions keep running. From January 1, 2027, those apps are delisted and blocked from new installs while existing installs continue. Partner custom apps installed outside the developer's organization follow the same dates.
Out of scope: apps that only write data such as metafields or products, apps whose only surface is a checkout UI extension, custom apps installed solely within your own organization, apps built in the Dev Dashboard or admin, and web pixels in the default strict sandbox.
Why it matters
The value here is less the declaration than the inventory it forces. Most enterprise storefronts carry years of embedded scripts, and few teams can name every host those scripts reach. That list is now machine readable per app, which is useful evidence when a security questionnaire or PCI scoping review asks what third-party code loads near checkout.
The sharper risk is operational, and it lands in peak season. A vendor that misses the deadline cannot deploy, so it cannot ship you a bug fix in December. That turns a vendor's compliance lapse into your incident. The same exposure applies to agency-built integrations installed across sibling stores, since those are in scope too.
Role-specific impact
- Marketers: Personalization widgets, review apps, and theme-embedded pixels are the most likely to carry a warning. Confirm vendor readiness before committing an app to a December campaign.
- Developers: Add the [network_access] block, enumerate real egress hosts rather than wildcards, verify against the dev store network access preview, then deploy and release. The preview covers the online store only.
- Store admins: After December 1, treat each app warning in admin settings as a vendor follow-up. A flagged app still works, but it is frozen until its developer acts.
Use-case example
Real-world scenario
A home goods brand runs four regional Plus stores with 23 apps installed across them. Classifying each app by surface identified 9 in scope: 6 public apps with theme app extensions and 3 partner-built custom apps shared between stores. One round of vendor emails returned confirmations from 6 of the 9. The holdouts included the loyalty app rendering on every product page, which the brand credits with 11 percent of repeat revenue, so the team scoped a fallback: strip the embed if the vendor cannot deploy by January 1. Audit effort was about four hours.
Implementation checklist
- Export and deduplicate the installed app list across every store in the organization.
- Flag apps using a theme app extension or embed, a script tag, an app proxy, write_themes, or a web pixel with write_open_pixels.
- Separate apps you or your partner build from third-party apps, since you control the first group directly.
- For apps you control, add allowed_sources, add allowed_navigation_hosts where the app links out, and use an empty list if there is no external traffic.
- Test on a development store with the network access preview, then deploy and release.
- Request written vendor confirmation for third-party apps and record the reply date.
- For any unconfirmed storefront-rendering app, define a removal plan before January 1, 2027.
FAQ
Q: Our integrations were built by an agency and installed on three of our stores. Are they in scope?
A: Yes, if they touch the online store through any listed surface. The exemption covers custom apps installed only within the developer's own organization. An app a partner installs across your stores is treated as distributed and needs declarations.
Q: Will anything break on our storefront on December 1?
A: No. Existing installs and released versions keep serving buyers. What stops is the developer's ability to deploy, plus App Store visibility and new installs from January 1. The buyer-facing risk is indirect: an app that cannot ship cannot be fixed.
Resources
Shopify's implementation reference, with configuration examples and troubleshooting: Declare your app's network access.
Need guidance? Talk to Makro.