Shopify script tags: what changed on October 1, 2026, and what breaks on March 1, 2027

Two days ago, scriptTagCreate started returning a user error. Nothing visibly broke, which is exactly why this one is easy to miss. The breakage is scheduled for March 1, 2027, and between now and then every app that still injects JavaScript into your storefront with a script tag has to be rebuilt or replaced. Here is what the documentation actually says, what it does not say, and how to find out in two minutes whether your store is affected.

The short version

Shopify published the change on August 24, 2026, under the title Script tags are deprecated and will stop running on March 1, 2027, flagged Action required. There are two dates and they do very different things.

• October 1, 2026, which has now passed: you can no longer create or update a script tag. Existing ones keep running.
• March 1, 2027: Shopify stops injecting script tags into storefronts. This is the date something actually stops working for your shoppers.

The gap between the two is the migration window, and it is about five months.

What changed on October 1

From the changelog, verbatim:

October 1, 2026: scriptTagCreate and scriptTagUpdate will return an user error. Existing script tags will keep running.

Shopify, Script tags are deprecated and will stop running on March 1, 2027, published 24 August 2026

Shopify's own developer documentation now states it in the past tense, which is the clearest confirmation that the milestone has landed:

Script tags are deprecated. You can't create or update script tags after October 1, 2026, and Shopify will stop adding them to storefronts on March 1, 2027.

Shopify, Build for the online store

The REST Admin API is covered too: the ScriptTag resource rejects POST and PUT from the same date. So there is no older, quieter endpoint to fall back on.

Pinning an API version does not help

This is the detail that catches teams who assume a pinned version freezes behaviour. The changelog is explicit that the deprecation applies to all API versions, including older ones. Pinning defers schema changes. It does not defer this.

What still works, and why it matters

The scriptTags query and the scriptTagDelete mutation keep working. That is deliberate: you can still audit what is installed and clean it up. You simply cannot add anything new. For anyone doing an inventory before March, those two are the tools you have.

The confusion worth clearing up: this is not the order status change

If you remember a script tag deadline that already passed, you are thinking of a different one. Shopify has been retiring script tags on two separate tracks, and they have separate timelines.

• Order status pages (display_scope of order_status or all): apps could not create them from February 1, 2025; they stopped running on Plus stores on August 28, 2025, and on all remaining stores on August 26, 2026. That track is finished.
• The online store (display_scope of online_store): this is the one that just entered its first phase on October 1, 2026, and ends on March 1, 2027.

So the storefront track is not a surprise announcement. It is the last step of a wind-down that has been running for nearly two years, and it is the step that touches product pages rather than the post-purchase page.

How to check your store in two minutes

If you have Admin API access, the scriptTags query still answers the question directly:

query {
  scriptTags(first: 50) {
    edges {
      node {
        id
        src
        displayScope
        createdAt
      }
    }
  }
}

Anything that comes back with a displayScope of ONLINE_STORE is a script that will stop being injected on March 1, 2027. The src tells you which app or which agency put it there.

If you do not work with the API, the practical version is to ask your app vendors directly, one question each: does your app inject anything into my storefront with a script tag, and if so, when does your theme app extension ship? A vendor who has already migrated will answer immediately. A vendor who has to check is a vendor to keep an eye on.

What replaces it, and the catch nobody mentions

The replacement is a theme app extension, usually an app embed block. For anything listed publicly, this is not a recommendation but a requirement:

Every new app that you submit to the Shopify App Store needs to use theme app extensions to integrate with online store themes.

Shopify, Build for the online store

Here is the part that makes this migration harder than it looks. A script tag was installed by the app, silently, with no merchant involvement. An app embed block has to be switched on by the merchant, in the theme editor, one store at a time. Asked in the developer forum whether there was a way to enable them programmatically for existing installs, a Shopify staff member answered:

there's no programmatic way to enable them for existing users. Let me go back to the team, see what's possible here.

Shopify staff, community.shopify.dev thread on the deprecation, September 2026

No bulk activation has been confirmed since. So for an app with a large installed base, the work is not only engineering. It is persuading thousands of merchants to click a toggle, and the ones who do not click it lose the feature in March without necessarily understanding why.

One more edge case raised by developers in the same thread and worth knowing if it is yours: on frozen or paused stores, API credentials do not work, so an app cannot even delete its own obsolete script tag. There is currently no published answer for that case.

What this means if you are a merchant, not a developer

Nothing on your storefront changed on October 1 and nothing will change tomorrow. The risk is concentrated on a single day, March 1, 2027, and it is binary: an app that still relies on script tag injection goes dark, on every theme, at once.

Two things are worth doing before then, and both are cheap. Run the audit above, or ask your vendors. And when an app asks you to enable its embed in the theme editor between now and March, treat that email as maintenance rather than marketing, because that toggle is very likely the migration.