An app put scripts on my storefront. What happens when Shopify retires script tags?
Ask developers which storefront apps need replacement embeds enabled. Analytics-only scripts move to web pixels without merchant action.
· Updated September 21, 2026
- When this applies
- An installed app adds storefront functionality, such as chat, reviews, upsells, banners, or SEO markup, and you need to know whether it still uses an online-store script tag. [1] [2]
- When this does not apply
- No embed activation is needed for a feature supplied by the theme itself or an app embed already active in the relevant theme. For scripts used only for analytics or conversion tracking, Shopify directs the developer to web pixels with no merchant migration action. [1]
- Why this matters
- On March 1, 2027, Shopify stops injecting online-store script tags. A feature still loaded through one loses that loading path unless its developer has replaced it. [1]
- What to do
- Ask every storefront app developer about affected scripts and their purpose. For a replacement embed, get its name and release date, then enable it in the relevant theme. Analytics-only scripts need no merchant embed action. [1] [2]
- Sources checked
- October 12, 2026
- Changed
- August 24, 2026
- Deadline
- March 1, 2027
Paid help and free options
- When paid help makes sense
- Paid help is worth it for custom storefront JavaScript your own developer maintains in a script tag. That developer must choose an app embed or web pixel according to the script’s purpose. [1]
Ask each storefront app developer whether you must enable a replacement app embed. Shopify stops loading online-store script tags on March 1, 2027. The developer owns migration; merchant action depends on the script’s purpose.
Two cutoff dates
Shopify’s deprecation notice separates:
| Date | Effect |
|---|---|
| October 1, 2026 | Apps cannot create or update script tags in any API version. Existing tags still run. |
| March 1, 2027 | Shopify stops injecting online-store script tags, so their JavaScript stops loading. |
Developers can still query and delete tags. The notice covers online-store display scope; order-status scripts had an earlier deprecation.
Separate functionality from tracking
- Analytics-only scripts: the developer moves them to web pixels. Shopify says no app-user action is needed; this does not prove migration is complete.
- Other storefront functionality: the developer supplies app embed blocks through theme app extensions. They may be visible widgets or hidden code.
- Both: ask for separate replacements.
Theme app extension guidance says embeds are off after installation. Enable each required replacement under App embeds in the relevant theme editor. Installation or release alone is insufficient.
Get an answer for every app
List all installed apps providing storefront functionality, including hidden code. Request a dated answer identifying whether each uses an affected tag, its purpose, and its replacement. For an embed, get its name, release date, and relevant theme.
Finish when every app has an answer and each required embed is enabled. Missing answers and unreleased replacements stay unfinished, even after the deadline. Separately test feature behavior or analytics events if those outcomes matter.
A separate migration service is unnecessary merely to ask and enable supplied embeds. Your own developer has paid work when custom script-tag code must move and its replacement must be verified.