Two dates matter. On the first, the repair mechanism goes away. On the second, five months later, the damage shows up in your storefront. Most merchants will meet the second date without knowing the first one passed.
Last checked against Shopify's developer changelog: 17 September 2026
Script tags can no longer be created or changed. scriptTagCreate and scriptTagUpdate start returning errors, and the REST ScriptTag resource rejects POST and PUT. Existing script tags keep running, so your store looks exactly the same.
Shopify stops injecting script tags into storefronts altogether — across all API versions, whether or not an app has pinned an older one. Anything that reached your storefront this way stops loading.
You do not have to take our word for any of this.
Type your shop address and see which scripts on your own storefront are on the clock. Free, nothing to install.
The gap between those two dates is the whole problem. From October, an app that has not already moved cannot patch its own injection — the API refuses the write. Nothing breaks that day, so nobody looks. The breakage arrives in March, by which time a dead app has had no way to fix itself for five months.
Script tags were how apps got JavaScript onto your pages without touching your theme. Anything an older app injected that way is at risk. In practice that means the visible furniture of the shop:
Shopify has published no list of affected apps and no figure for how many stores are involved. Analytics and conversion tracking are a partly separate case: those move to web pixels, which need no action from you.
The fast way: put your shop address into the free check and read the result. It loads your storefront the way a customer does and tells you which scripts arrive the way script tags do. The rest of this section is the same job done by hand, in the Admin API.
You do not have to wait for your app vendors to tell you. The audit query survives the shutdown — Shopify is keeping scriptTags and scriptTagDelete alive precisely so stores can be cleaned up. If you have a developer or a partner agency, this takes them ten minutes.
{
scriptTags(first: 50) {
edges {
node {
id
src
displayScope
createdAt
}
}
}
}displayScope: ONLINE_STORE is on the clock. The src host usually tells you which vendor owns it.App embeds do not switch themselves on. Shopify's own documentation is explicit: an app embed block stays inactive until a person turns it on in the theme editor, and the app cannot activate it on your behalf. So a vendor can ship a perfect replacement and your storefront still loses the feature — because nobody clicked. Vendors are expected to hand you a deep link into the theme editor with the block ready to enable.
It is tempting to treat this as a one-off chore: audit the store in February, fix the list, move on. That underrates the new arrangement. Once storefront features live in app embed blocks, they can be switched off by something as ordinary as a theme change — a redesign, a duplicated theme published without the embeds enabled, a new seasonal template. The block goes quiet, the app keeps reporting itself as installed and billing normally, and the only evidence is a feature missing from a page nobody is looking at.
That failure mode is not new. What is new is that from March 2027 a much larger share of your storefront depends on it.
Type your shop address. We load the page a customer sees and list every script on it — which ones come from an app embed and survive 1 March 2027, which ones arrive the way script tags do and stop, and which app each one belongs to.
Check my storeNothing to install, no permissions, no account. If you would rather we went through every template and talked to your vendors, that is a paid report — the check page explains it.