Shopify script tags deprecation: what breaks on March 1, 2027

The dates are simple. According to Shopify's developer documentation, from October 1, 2026 the create and update calls for script tags return a permission error on every API version. Existing tags keep running. On March 1, 2027 Shopify stops loading them, and "any dependent features stop for that store."

Here is what makes this different from a normal deprecation. Shopify planned a warning banner for app users and then dropped it. In a September post on the Shopify developer community, a Shopify staff member said the install warning would not ship on October 1, that an earlier email had been overstated, and that the dates had not changed. Shopify said it would watch script tag usage through the fourth quarter and revisit the question in January.

Read that as a merchant. The platform will not tell you which of your apps still depend on the old mechanism. The developers who wrote those apps are complaining in public that they cannot reach their own customers. One developer in the thread said 70 to 75 percent of their users still rely on script tags. I can't verify that number, but even if it is half right, a lot of stores will hit March with live features that quietly stop.

Your analytics will not flag it either. A missing review widget is not a 500 error. It is a page that looks slightly emptier, and the conversion rate drifts down over a few weeks.

Script tags were the easy way for an app to put JavaScript on every page of a store without touching the theme. That makes them common in the parts of a storefront that sit on top of the design rather than inside it. Think review stars on product cards, exit-intent popups, free-shipping progress bars, countdown timers, currency or language switchers, cookie banners, size guides, chat bubbles and cross-sell drawers.

These are also the features that carry conversion weight. Reviews are the clearest case. Northwestern's Spiegel Research Center report found that a product with five reviews is 270 percent more likely to be purchased than one with none. Treat that number carefully. It comes largely from one retailer's data and is higher for expensive products. The same report says nearly all of the lift arrives within the first 10 reviews. So the loss from a vanished review widget depends on how many reviews you have, how pricey the product is, and whether shoppers can still find the reviews anywhere else on the page.

Few stores will lose anything like 270 percent. The risk is that these features are ones a design review never checks, because they live in the browser, injected after load, not in the theme code.

A related shutdown has already happened at checkout. A vendor write-up from Aimerce reports that Additional Scripts on the Thank You and Order Status pages stopped for non-Plus stores after August 26, 2026, and that conversion pixels for Meta, Google or TikTok stop firing with no error in the admin. It is a vendor blog selling its own fix, so weigh its advice accordingly. Its audit trick is still good. Compare conversions reported in each ad platform against orders in Shopify, and a growing gap means lost tracking.

Shopify's documented replacement is an app embed block, shipped inside a theme app extension. For tracking only, the replacement is a web pixel. The two behave very differently for you.

A web pixel needs no action from the merchant. You approve permissions when you install or update the app, and it runs. An app embed block is the opposite. In Shopify's words, "app embed blocks are inactive until an app user turns them on." The developer is supposed to send you to the theme editor with the embed switched on, and confirm it is active on the published theme before deleting the old script tag. Otherwise, as the docs put it, "you leave a gap where neither works."

That creates three failure modes you can plan for.

First, the app updated, but nobody told you to flip the toggle. The developer thread says there is currently no programmatic way to enable an embed for existing merchants, so some developers are relying on emails that merchants don't read. Second, embeds are per theme. If you duplicate your theme for a holiday redesign and publish the copy, the embed has to be turned on again. Third, both versions can run at once. Shopify warns that doing so loads the script twice, which can double-count analytics or show a popup twice.

Stores on legacy themes have a further problem. App blocks need JSON templates, though Shopify says embed blocks work on vintage and Online Store 2.0 themes. Developers in the thread asked what happens to merchants who cannot move, and the thread shows no Shopify commitment to an exception. If your theme is more than a few years old and heavily edited, this is the most likely place for surprises.

You do not need a developer to find out how exposed you are. You need a list of apps, a browser and a few hours.

Start in Shopify admin and list every installed app. For each one, write down what it shows shoppers and where. If an app has no visible storefront element, such as a pure back-office tool, cross it out. What remains is your risk list.

Next, open your live store in a private window with the browser's developer tools on the Network tab, and load the home page, a collection page, a product page and the cart. Filter requests to JavaScript. Files served from cdn.shopify.com with an app's name in the path, or from the app vendor's own domain, tell you which apps inject code. Write down the app, the page and the visible feature it controls. This gives you a map from feature to app, which is the document most stores don't have.

Then contact each vendor on the risk list with one precise question. Ask whether the app still uses script tags on your store, and if so, what you need to do and by when. Ask them to confirm in writing that the app has moved to an app embed block or a web pixel. If the answer is vague, treat it as a no.

Finally, work out your fallback. For any feature that drives revenue, such as reviews, upsells or shipping thresholds, decide now what you will do if it disappears in March. That might be a different app that already uses theme extensions, or a native theme section. Shopify also describes a route for admin-created custom apps. Move the script into the theme itself, ideally as a custom Liquid block. The catch is that the script stays after the app is removed, and Shopify notes that editing theme code takes the theme out of automatic upgrades.

Treat the deadline as a release date for your own store. Work backward from March 1 and leave a buffer, because app vendors will be answering the same question from thousands of merchants at the same time in February.

In November, build the feature-to-app map and email vendors. In December, avoid redesigns and new theme publishes if you can, since each one resets the embed activation question. In January, check the Shopify developer changelog, because Shopify has said it will revisit the situation then and may announce targeted notices. Between mid-January and mid-February, have each vendor activate its embed on a staging copy of the theme, then do the same on the published theme, with a before-and-after screenshot of every template that carries an app feature.

After each change, compare the page with your screenshots. Watch for a doubled popup, a missing badge, a layout shift where a widget used to load, and a conversion pixel that fires twice. Compare ad platform conversions against Shopify orders for a week afterward.

One habit for later. At every app demo, ask whether it runs through a theme app extension and web pixel, or still injects a script tag.