Shopify Script Tags Stop March 2027. You Won't Be Warned.
Shopify script tags stop injecting March 1, 2027. Most stores still load one, Shopify cancelled the warning, and BFCM shortens your audit window.

In late October 2026, a developer audited 45 live Shopify storefronts and found that 73% of them were still loading at least one script tag that stops working on March 1, 2027. The median store had two. One had eleven. Around the same time, one app studio with a large install base reported that 70-75% of their merchants were still on the old system.
That gives you the shape of the problem. In roughly 14 weeks, Shopify script tags stop being injected into storefronts. Review stars will blink off. Live chat buttons will disappear. Exit-intent popups will stop firing. Trust badges will go blank. Your Shopify admin will show you none of this. Orders keep arriving. Everything looks fine from the backend.
Shopify had a plan to warn merchants about this. They cancelled it on September 27, 2026.
My take: Shopify made the right call on the engineering deadline and the wrong call on the merchant warning. Those are separate decisions, and treating them as one is how most stores end up broken.
Why Shopify thinks you're covered
Here is the view from the developer docs. Script tags are a 2015-era mechanism. They inject JavaScript into every page of your store without appearing anywhere in the theme editor. You cannot find them. You cannot toggle them off. They run.
Shopify built a replacement in 2021: app embed blocks, which show up in Online Store > Themes > Customize > App embeds, where you can see them, position them, and switch them off. That is a real improvement over what came before. Developers were told in August 2026 that new Shopify script tags would be blocked from October 1, 2026 and existing ones would stop running on March 1, 2027. The docs are clear. The changelog is clear. The developer announcement thread has over 20 replies going back three months.
If you were an app developer watching that thread, you would reasonably conclude the industry is going to muddle through. From a merchant perspective, it looks different.
Why it won't be fine for most stores
The migration path has a specific shape that creates a silent failure mode.
When a developer ships an app embed block to replace their old script tag, the embed arrives on your store deactivated. The developer cannot activate it; Shopify requires the merchant to flip the switch in the theme editor, per theme, and the app is not allowed to do it for you. There is no programmatic path. Shopify Staff confirmed this directly in the developer forum: "there's no programmatic option for existing users yet."
Which means the migration isn't one step. It's two, and the second step is yours. The app developer migrates. Then every one of their merchants has to open Customize, find the App embeds panel, and toggle the embed on. For an app with twenty thousand installs, that's twenty thousand merchants doing the same small click. The LAUNCHTIP developer, reporting on their 2018-2019-era apps with a large user base, said plainly that 70-75% of their merchants had not done it yet. That report was on October 27. Six weeks before BFCM.
If you do nothing, and your installed apps still ship on Shopify script tags, this is what you can expect on the morning of March 1:
- The storefront loads normally.
- Features embedded via script tags stop appearing. Shopify shows no error.
- A customer or a friend tells you a week later that your review stars are gone.
You are then reverse-engineering which app broke, whether the developer has shipped a replacement, and whether you need to enable an embed or swap the app entirely. In January that would be annoying. In March, after BFCM has already banked whatever damage this is going to do, it gets genuinely painful.
The two things Shopify quietly removed from the plan
There were originally two mitigations in Shopify's plan. Both have been pulled.
The first was an install-time banner. When a merchant installed an app that still used script tags, Shopify was going to show them a warning that parts of the app would stop working in March 2027. On September 27, 2026, Shopify cancelled this. The official reason was that the banner misfired - it flagged apps that had already migrated years ago, which caused "confusion and panicked support emails." The developer forum had asked for the banner to be killed. Shopify agreed.
I can see why. A banner that cries wolf is worse than no banner. But the banner existed because somebody at Shopify understood that merchants were not going to find out any other way. Removing it without replacing it is the gap the audit numbers describe.
The second removal was a programmatic migration path for existing installs. App developers asked Shopify repeatedly for a way to activate app embeds on behalf of their already-installed merchants, with recorded consent. Shopify declined. The official position is that merchants own their themes and have to opt in. In a world where merchants received direct, specific notice, that would be correct. In the world Shopify just made, with no banner, no email, no admin flag, it offloads a platform transition onto store owners who do not know there is a transition.
I disagree with that call. Merchant consent is a real principle, and I take it seriously, but it's incoherent when there's no mechanism to inform the merchant.
Why BFCM makes this worse
BFCM is November 28, 2026. Six days from this post. An agency timeline for this migration suggested freezing all app changes between November 14 and December 1. The November 14 cutoff has passed. Do not change apps now.
Running an old Shopify script tags-based app alongside a new app embed at the same time creates a specific hazard: duplicate UI (two chat buttons, two sets of review stars) and double-counted analytics events. Ad platform bidding degrades against inflated conversion data. You'll notice the degradation as a vague drift between what the platform reports and what your bank receives. Harder to diagnose than an outright failure.
You cannot safely migrate in BFCM, and you should not wait until late February either, because January is partly consumed by a separate Shopify deadline: on January 1, 2027, all public apps must switch to expiring offline tokens. Apps that haven't updated their auth flow may start failing authentication a full two months before the script tag cutoff.
The practical answer: audit now, migrate in the first two weeks of January.
What to actually do this week
Here's the five-minute version. You can do this today without changing anything on your store.
- Open your storefront homepage in a browser. Right-click and choose "View page source."
- Press Cmd+F or Ctrl+F and search for
asyncLoad. - Each URL listed under that marker is a currently-active script tag. The domain in the URL tells you which app. A URL like
cdn.reviewapp.io?shop=yourstore.myshopify.compoints at your review app. - Repeat on a product page and a collection page. Some apps load only on specific templates.
- Write the list down. Do not act on it yet.
If the list is empty, you are in the clear and can stop reading. If anything shows up there, you have an action item for January, not for this week. If you want a second pair of eyes on the list before you act, the first 15 minutes with a help1 expert is free and a scan-and-list is exactly what that time is good for.
If you want background on how app embeds and app blocks differ (they are not the same thing, and the Shopify docs sometimes conflate them), the script tag vs app embed vs app block breakdown explains which replacement your specific app needs. If you are on a vintage (pre-Online Store 2.0) theme, that post also has the correction most agency blogs have not caught up to yet: app embed blocks do work on your theme, so you are not stuck.
The counterargument I owe you
The honest version of the other side: most of the apps in the Shopify App Store that matter have shipped embed replacements. The agency ecosystem has been writing about this since August 2026. By March 2027, many merchants will have been nudged into action by developer emails, newsletters, or an app forcing an update. Shopify's bet is that the market will handle it.
That bet might be right for 50-70% of stores. For the long tail, the merchant who installed a trust badge app in 2019, left it alone, and barely reads developer emails, it will not be. Those stores are the ones whose Shopify script tags silently stop firing in March. The audit numbers I opened with suggest that tail is not small.
So: open your source view, search for asyncLoad, and look at the list. Which of those features would you actually miss if it disappeared quietly in March, and when are you going to do the small January fix for that one?
Still stuck? Talk to an expert.
Our vetted Shopify experts can fix this issue for you in a live session. $39 per session. Your first 15 minutes are free.