Shopify Scripts are expiring – here’s what to do before June 30
Shopify Scripts stop working on June 30, 2026. Here's what's changing, what replaces it, and how to migrate your checkout customisations to Shopify Functions before the deadline.
If you’re running a Shopify Plus store with custom checkout logic, this one’s worth your attention.
Shopify Scripts migration is now urgent – the Ruby-based tool that’s been powering custom discounts, shipping rules, and payment customisations for Plus merchants since 2019 is being permanently shut down on June 30, 2026. And while that might sound like plenty of runway, the Script Editor already went read-only on April 15, which means if you haven’t migrated yet, you’re working with whatever you’ve got and a countdown that’s already ticking.
The replacement is Shopify Functions, and the good news is that if you start now, there’s still time to get across without disruption. Here’s what you need to know.
What Shopify Scripts actually did
For a lot of Plus merchants, Scripts have been quietly running in the background for years – the kind of thing that nobody touches because it just works. Specifically, Scripts gave you a way to write custom Ruby code directly inside the Script Editor in your Shopify admin, which then ran at key points in the checkout flow.
There were three main areas they covered:
- Line item scripts – custom discount logic like BOGO offers, tiered pricing, or percentage discounts tied to specific cart conditions
- Shipping scripts – hiding, reordering, or renaming shipping methods based on cart contents, customer tags, or order value
- Payment scripts – hiding or reordering payment methods based on similar conditions
It was a genuinely useful tool. The problem was always under the hood.
The two dates you need to know
April 15, 2026 – the Script Editor went read-only. You can still see your Scripts and they’re still running, but you can no longer create new ones or edit existing ones. They’re frozen as-is.
June 30, 2026 – all Shopify Scripts stop executing entirely. After that date, if your checkout relies on Scripts and you haven’t migrated, you’ll be serving customers standard pricing, standard shipping, and every payment method your store has enabled, whether you intended that or not.
June 30 is the date to be working backwards from.
Why Shopify is making this change
This isn’t Shopify removing a feature for the sake of a roadmap cleanup. Scripts had a fundamental architecture problem: they ran in a sandboxed Ruby environment that had to be provisioned and maintained separately from Shopify’s core infrastructure, which created inconsistent performance, cold-start latency, and a hard ceiling on what was actually possible at checkout.
Shopify Functions are the rebuilt version of the same idea, rebuilt from the ground up on WebAssembly (WASM). They run inside Shopify’s own infrastructure, execute in under 5ms with no cold-start overhead, and extend to more parts of the commerce lifecycle than Scripts ever could.
Functions are genuinely better, the migration is the annoying part.
What Shopify Functions look like in practice
Functions are compiled WebAssembly modules, written in Rust or JavaScript, that run at defined extension points in the Shopify platform. The biggest day-to-day difference: instead of writing Ruby in a browser-based editor, you’re writing JavaScript or Rust locally in your own IDE, managing it like any other codebase with version control, testing, and CI/CD, and deploying via the Shopify CLI.
The capabilities map across like this:
| What your Script did | Shopify Functions equivalent |
|---|---|
| Line item discounts | Discount Functions |
| Shipping method customisation | Delivery Customization Functions |
| Payment method customisation | Payment Customization Functions |
| New: Cart validation | Order Validation Functions |
| New: Cart transforms | Cart Transform Functions |
Those last two rows are worth noting – Scripts couldn’t do any of that. Functions give you more leverage over the checkout experience, not less. And while Scripts were Plus-only, Functions are available across all Shopify plans (with some nuances around custom vs. public apps), so if you’ve been living without checkout customisation on a non-Plus plan, this actually opens things up.
How to migrate: a practical walkthrough
Step 1: Audit what you've got
Start in Shopify admin under Settings → Checkout → Customisations Report. This lists every active Script in your store, what it does, and Shopify’s recommended Function equivalent. Most merchants find they have more Scripts running than they thought – especially on stores that have been live for a few years.
Step 2: Map Scripts to Functions
For each Script, work out whether it maps directly to a Function equivalent (most do) or whether you’ll need an app from the Shopify App Store to replicate the functionality. Shopify’s own documentation covers feature parity in detail.
Step 3: Build and test
Functions are developed locally using the Shopify CLI (shopify app generate extension). Each Function has a query file that pulls in cart and checkout data, and a logic file in Rust or JavaScript that returns the required operations. You test locally with shopify app dev and preview links before anything goes near production.
Step 4: Deploy before June 30
Deploy with shopify app deploy and activate via Shopify admin. Because your logic lives in version control, rolling back if something breaks is straightforward – which is one of the genuine improvements over the old Scripts setup.
If your Shopify Scripts migration is complex or the right path isn’t obvious, that’s worth getting eyes on sooner rather than later. The stores that will struggle with this deadline will be the ones that leave it until mid-June.
The bottom line
The Script Editor is already locked. June 30 is the hard stop. But the migration is well-documented, the tools are solid, and Shopify Functions are a genuinely better foundation for what comes next – so this isn’t change for its own sake, it’s Shopify retiring old architecture and giving merchants something more capable in its place.
What you shouldn’t do is treat it as a next-quarter problem, because it isn’t.
Restive is a Shopify Plus Partner and helps Australian businesses plan and execute Shopify platform work – from unified commerce strategy to technical migrations. If you need support with your Shopify Scripts migration before the June 30 deadline, get in touch.
Related articles
