If you run a Shopify Plus store, today is a hard deadline you may not have planned around. As of April 15, 2026, the Shopify Script Editor is effectively frozen — merchants and their developers can no longer create new Shopify Scripts or edit existing ones. Existing scripts keep running for now, but on June 30, 2026, the legacy runtime shuts off for good, taking every unmigrated script with it.
The changelog notice is terse. Shopify's official post confirms the two-stage sunset: read-only today, fully retired at the end of Q2.
Why this is a bigger deal than it sounds
Shopify Scripts have been the invisible plumbing behind a lot of Plus checkouts since 2016. Wholesale Helper catalogs what merchants have been doing with them: automatic discount stacking, tiered pricing for wholesale accounts, hide-this-payment-method-for-gift-card-orders logic, custom shipping rules, BOGO promotions, minimum-order enforcement, and a long tail of one-off business rules that didn't fit anywhere else.
All of that code is written in Ruby and lives in a legacy runtime Shopify has been steadily deprecating in favor of Shopify Functions, a newer WebAssembly-based extension system. Functions are faster, more portable, and work with the new checkout extensibility model — but they are not a drop-in replacement. Every script has to be rewritten, tested, and deployed as a Function before the June cutoff.
The part that's going to hurt
The Shopify community forum has been full of developers asking the same question for weeks: what happens if something breaks after today? The answer is not great. A merchant whose BOGO script silently stops matching the right items, or whose tiered wholesale pricing glitches at checkout, can no longer push a hotfix. Ruby Digital Agency makes the point bluntly: the Script Editor is still technically visible in the admin, but any attempt to save a change is now blocked.
In practical terms, that means any script-driven logic that breaks between now and June 30 has to be ripped out and replaced with a Function under pressure — or with a third-party app. It is the kind of forced migration that tends to surface the scripts everyone forgot existed. Huptech recommends running a customizations report from the Plus admin today to get a full inventory of what is in production before the deadline turns into an incident.
What retail operators should be doing today
There are three things. First, pull the Scripts customizations report out of your Shopify Plus admin right now — before something breaks — and confirm that every active script has an owner and a migration plan. Second, prioritize checkout and payment logic over promotional logic; a broken BOGO is annoying, but a broken payment-method filter at checkout is revenue loss. Third, decide what gets rewritten as a Function and what can be retired. Most merchants have accumulated more checkout scripts than they actually need, and June 30 is a forcing function to clean them up.
For the broader ecommerce market, today's cutoff is a reminder of how much of the Plus ecosystem still runs on infrastructure that was built almost a decade ago. Shopify has been very public about its platform modernization roadmap, but the Scripts retirement is the first deadline where the cost of not migrating becomes real. Merchants who miss June 30 will be running a checkout with pieces missing, and there will be nothing in the admin to turn back on.