Shopify Script Tag Deprecation: What Merchants Should Audit Before March 1, 2027

Shopify will stop loading script tags on storefronts on March 1, 2027, and apps can no longer create or update them since October 1, 2026. This guide shows merchants and agencies how to find which apps are affected, what app embeds and web pixels change, and how to time the switch around BFCM.

Yuval Tsabari עודכן ב- 25 באוק׳ 2026

If your Shopify store has a reviews widget, an upsell pop-up, a chat bubble, a loyalty badge, or an ad pixel that you installed through an app, some of that code may reach your storefront through a script tag. Shopify has set a date for that to end. On March 1, 2027, Shopify will stop injecting script tags into storefront pages, and any feature that still depends on one will stop loading.

The first step has already happened. Since October 1, 2026, apps can no longer create or update script tags on any API version. Existing script tags keep running until the March cutoff. Most of the replacement work sits with app developers, but the storefront that breaks is yours. So it's worth knowing which of your apps are affected and how the switch will happen, before it happens to you.

This guide is for ecommerce decision-makers and for agencies that manage Shopify stores for clients. It covers what's changing, how to find out whether your store is affected, what replaces script tags, and how to time the switch around the holiday season.

Short answer: Script tags stop running on Shopify storefronts on March 1, 2027. To prepare: (1) list every app that adds something to your storefront, (2) compare that list with the App embeds in your theme editor, (3) check your page source for app scripts, (4) ask each vendor whether they use script tags and when they'll switch, (5) have a developer check any custom apps, and (6) after each switch, confirm the feature works on your live theme and that tracking isn't counted twice.

What's changing, and when

Script tags are an older way for apps to load JavaScript on a store without editing theme code. Shopify introduced theme app extensions as their replacement in 2021, and has been retiring script tags in stages. These are the dates from Shopify's developer documentation and changelog:

Date	What happens	Who it affects
February 1, 2025	Apps can't create script tags for the Order status page.	All plans
August 28, 2025	Script tags stop running on the Order status page.	Shopify Plus stores
August 26, 2026	Script tags stop running on the Order status page.	All other stores
October 1, 2026	Apps can't create or update script tags on any API version. Existing storefront script tags keep running.	All stores
March 1, 2027	Shopify stops injecting script tags into storefront pages.	All stores

Shopify explains the reason in its August 24, 2026 changelog announcement: script tags run JavaScript on a storefront without appearing in the theme editor, which makes them hard for merchants to find and control. The replacements are visible in the theme editor, or, for tracking, run in a sandbox that respects customer privacy settings.

One practical detail: Shopify's documentation says that pinning an app to an older API version won't defer the October 1 change. An app vendor can't buy time that way, so every affected app needs a real replacement before March 1, 2027.

Which features could be affected

A script tag can load almost any storefront feature. Common app categories that put something on the storefront include product reviews, upsells and cross-sells, pop-ups and email capture, chat, loyalty and rewards, size guides, wishlists, currency or geolocation helpers, and analytics or ad tracking. That doesn't mean every app in those categories uses script tags. Many already use theme app extensions. The point is that you can't tell from the app's name, so you need to check.

Three situations deserve extra attention, based on Shopify's storefront script tag guide:

Admin-created custom apps. Apps created directly in the Shopify admin, rather than with Shopify CLI or the Dev Dashboard, can't use app extensions. That means no theme app extension and no web pixel. If one of these apps loads a script through a script tag, the script has to move into the theme itself, or the app has to be rebuilt.
Third-party services that asked you to create an app. If a service had you create a custom app and paste its access token into their dashboard, Shopify says that service needs to release a real app that uses a theme app extension or a web pixel.
Script tags scoped to "all" pages. Shopify notes that a script tag with a display scope of all stopped on the Order status page but keeps running on the storefront until March 1, 2027.

Scripts pasted directly into theme code aren't script tags, so this deprecation doesn't switch them off. They are still worth listing while you're auditing, because they don't show up in your app list either.

For a useful audit, separate what shoppers can see from what runs behind the scenes. A reviews widget might look fine while an older tracking integration still needs attention. Start with reviews, upsells, pop-ups, and analytics, then identify how each one loads. An app’s presence in the theme editor is useful evidence, but it doesn’t explain every script running on the store.

How to check whether your store is affected

Shopify's admin lists your installed apps, but it doesn't give merchants a list of which apps use script tags. These checks get you most of the way there. The first three need no developer.

1. List what each app does on your storefront

Go to Settings > Apps and write down every installed app. Next to each one, note what it shows or does on the storefront, if anything. Apps that only work in the admin, such as some inventory or reporting tools, can usually be set aside. This list becomes your audit sheet.

2. Compare your list with the theme editor's App embeds

In the theme editor, open the App embeds panel. According to Shopify's Help Center guide to app embeds, this is where app-provided elements such as chat bubbles, overlays, and tracking code are switched on and off. Note which apps appear there and whether each one is active. An app that adds something to your storefront but has no app embed and no app block in the theme editor is a candidate for a script tag, or for code in the theme.

3. Look at the page source and the Network tab

Open your storefront in a private browser window and view the page source. On stores that still have storefront script tags, the script addresses are commonly listed inside a block of Shopify-generated code called asyncLoad, usually with your myshopify.com domain in each address. This is an informal check that developers use, not an official Shopify audit tool, and Shopify can change that output at any time. You can also open your browser's developer tools, go to the Network tab, filter by JavaScript, and reload. Check the home page, a product page, a collection page, and the cart, because different pages can load different scripts. Match each unfamiliar domain to an app on your list.

4. Ask each vendor directly

For every storefront app you can't rule out, send a short question through the app's support channel:

"Shopify will stop loading storefront script tags on March 1, 2027. Does your app use a script tag on our store? If so, when will you switch to an app embed block or a web pixel, and will we need to do anything on our side, such as turning on an app embed in the theme editor?"

A clear answer with a date is what you're looking for. If a vendor can't tell you, start looking at alternatives early rather than in February.

5. Have a developer check custom apps

For custom apps, a developer can run Shopify's scriptTags query with that app's own access token. Shopify notes that the query only returns the script tags of the app making the request, so it has to be repeated for each app and each store. It can't audit apps from the Shopify App Store. Shopify kept read and delete working after October 1, so this audit is still possible.

What replaces script tags

Shopify's documentation names two replacements, depending on what the script does:

If the script...	Replacement	What it means for you
Loads JavaScript or shows something on storefront pages	App embed block (part of a theme app extension)	Inactive until it's switched on in the theme editor, and active only on the theme where it was switched on.
Places visible content inside a page section	App block	Added and positioned in the theme editor. Only works on themes that support JSON templates.
Only collects analytics, conversion, or behavior data	Web pixel	Managed in the Customer events section of the admin. Runs in a sandbox with known limits.

Two details are easy to miss.

App embeds are switched on per theme. Shopify's migration guide says app embed blocks are inactive until a merchant turns them on, and the app can't turn them on for you. An embed is also only active on the theme where it was enabled. If you later publish a new theme, for example after a redesign or a major theme update, each app embed needs to be switched on again there. If you sell in several markets, Shopify's Help Center adds that app embeds can be configured per market, so check the settings for each market you use.

Web pixels don't behave exactly like page scripts. Shopify's pixels overview lists the sandbox's limits. Pixels can't render buttons, forms, banners, or pop-ups. They can't automatically detect events or customer details by reading the page, and they can't capture page scrolling, or the clicks and mouse movement used for heatmaps. In markets configured to require consent, pixels only run when visitors have given the required permissions. If a tool you rely on for conversion research or ad attribution moves to a web pixel, ask the vendor what data it will and won't collect afterwards.

Risks to plan for during the switch

A gap where nothing works. Shopify warns developers not to delete a script tag until the replacement is confirmed running. On your side, that means switching on the new app embed when the vendor asks, and checking that the feature appears on your live theme.
Double loading. Until March 1, 2027, a script tag and its replacement can run at the same time. Shopify says this loads the script twice, which can double-count analytics events or show an app's UI twice. After each switch, check for duplicate widgets and compare your purchase and add-to-cart counts with your orders.
Measurement changes that look like behavior changes. If conversion rate, add-to-cart rate, or ad-reported revenue moves around the time an app switches, that's an observation, not a diagnosis. Check tracking first: whether events fire once, whether consent settings changed what's collected, and what else changed that week, such as campaigns, traffic mix, or other releases. Then decide whether shopper behavior actually changed.
Leftover code and speed. An audit is a good moment to remove apps nobody uses. Shopify's Help Center notes that the more scripts a store runs, the slower it can get. For related fixes, see our guide to Shopify store speed and UX.

A practical way to validate the switch is to repeat the same buying journey before and after it: open a product, select a variant, add it to the cart, and continue to checkout. Record which widgets appear and which tracking events fire at each step. If the reported numbers change afterwards, that baseline helps you investigate whether the migration changed measurement or the shopping experience.

Timing: BFCM first, then the switch

In 2026, Black Friday falls on November 27 and Cyber Monday on November 30. Existing storefront script tags keep running until March 1, 2027, so the deprecation itself doesn't force a change during peak season. A sensible order for many stores is:

Now: run the audit above and send the vendor questions. Reading and listing changes nothing on the storefront.
Before peak season: decide which switches can wait and which can't, for example if a vendor's switch is already scheduled. Agree with your team or development partner what gets tested and when.
After the holidays: schedule the remaining switches with enough time to check each one before March 1, 2027.

Shopify has also said, in a September 27, 2026 developer forum update, that it will watch script tag usage through Q4 and look at it again in January, and that the rest of the timeline hasn't changed. Plan for the published date.

From a UX and CRO perspective, I would prioritize anything that helps a shopper choose a product or complete a purchase. Check variant selection, size guides, reviews near the purchase controls, add-to-cart behavior, and the cart drawer first. Then check product recommendations and promotional overlays. Validate tracking alongside these features: a working storefront and reliable measurement are both necessary to judge what happened after the switch.

For agencies managing client stores

If you look after many Shopify stores, the audit multiplies. Shopify's own advice for developers who maintain a custom app per client is to check them one at a time, using the token each app already holds for each store. A shared sheet per client store with the app, what it does on the storefront, whether it uses a script tag, the vendor's answer, the planned switch date, and who confirmed it afterwards keeps the work visible. If you bring in a white-label partner for this kind of work, agree access, client communication, and confidentiality per engagement. Our guide to vetting a white-label Shopify development partner covers what to ask.

Script tag audit checklist

List of every installed app and what it does on the storefront
Comparison with the theme editor's App embeds and app blocks
Page source and Network tab checked on home, product, collection, and cart pages
Vendor answer, with a date, for every app that might use a script tag
Custom apps checked by a developer with each app's own token
Admin-created custom apps and token-based services identified, with a plan for each
Scripts in theme code listed, even though this deprecation doesn't remove them
Switches scheduled around BFCM and finished before March 1, 2027
After each switch: feature visible on the live theme, settings checked per market, no duplicate widgets, events firing once
App embeds re-checked whenever a new theme is published

Keeping this list current is a natural part of ongoing development. Our guide to Shopify retainer scope covers how to put platform changes like this one in scope.

FAQ

What happens to script tags on March 1, 2027?

Shopify will stop injecting them into storefront pages. Any feature that still loads through a script tag will stop working on your store. Leftover script tag records won't do anything after that date.

Do I need to do anything if my apps are up to date?

Possibly. Updating an app doesn't always switch it to an app embed automatically. Because app embeds are inactive until you turn them on, you may need to enable them in the theme editor. Ask each vendor, and check the App embeds panel.

Does this affect my checkout?

Storefront script tags don't run in checkout. The related Order status page changes already took effect: August 28, 2025 for Shopify Plus stores and August 26, 2026 for all other stores.

Is this the same as the end of Shopify Scripts?

No. Shopify Scripts were checkout customizations for discounts, shipping, and payments, which stopped running on June 30, 2026 and are replaced by Shopify Functions. Script tags are an app API for loading JavaScript on the storefront. The names are similar, but they are different changes.

Need help with your script tag audit?

Dominatecom is a Shopify Select Partner. We provide Shopify and Shopify Plus development, including app and theme audits, alongside UX/UI design and CRO. Dominatecom is led by Yuval Tsabari, a UX designer who combines analytics and consumer psychology, so a technical change like this one can be checked against the buying experience and your measurement, not only the code.

We work with merchants directly and, on a white-label basis, with agencies. Scope, timing, and support coverage are agreed as part of each engagement.

Talk to us about a Shopify app and script audit →