Shopify Scripts Stopped Running on June 30: The Functions Migration Guide for Canadian Merchants (2026)

01. What Happened on June 30, 2026

Shopify Scripts was the Ruby-based customization tool available to Shopify Plus stores through the Script Editor app. It powered three categories of checkout logic: line item scripts (automatic discounts and price changes), shipping scripts (renaming, reordering, and repricing shipping rates), and payment scripts (hiding, reordering, and renaming payment methods).

The retirement happened in two steps, both announced in Shopify's changelog and developer documentation:

• April 15, 2026. Merchants could no longer create, edit, or publish scripts. Existing published scripts kept running.
• June 30, 2026. All Shopify Scripts stopped executing. The deadline had already been extended once, from August 28, 2025, and Shopify confirmed it would not move again.

The replacement is Shopify Functions. The critical operational fact: there is no automatic conversion. Shopify did not port your scripts. Logic that mattered has to be deliberately rebuilt, and until it is, your checkout runs without it.

02. How to Tell If Your Store Is Affected

If you are on Shopify Plus and your store has been live for more than a couple of years, assume you are affected until proven otherwise. The audit takes an hour:

1. 1. Open the Script Editor app. Every script that existed is listed there, even now. This is your inventory of lost logic. Export or document each script: what it did, which customers or products it touched, and roughly how much revenue depended on it.
2. 2. Test checkout like a customer. Run through checkout with the carts your scripts targeted: a wholesale account, a stacked-discount cart, an oversized item, an order shipping to a province with special payment rules. Compare against how it behaved in June.
3. 3. Watch the symptoms. Automatic discounts that no longer apply, shipping rates that reappeared or repriced, payment methods showing where they were hidden, and a spike in support tickets or abandoned checkouts starting July 1 are the classic signs.
4. 4. Check your apps too. Some older apps depended on Scripts under the hood. If a discount or shipping app instructed you to paste script code during setup years ago, that pathway is dead even though the app is still installed.

Not on Plus? You never had Scripts, and nothing broke for you on June 30. But the Functions ecosystem this migration created matters to you anyway, because it brought checkout-grade customization to standard plans for the first time. More on that below.

03. Scripts vs Functions: What Actually Changed

Functions is not Scripts with a new name. It is a different architecture with different trade-offs.

The honest trade-off: Scripts let a technical merchant paste twenty lines of Ruby and ship. Functions require an app, which raises the floor for one-off tweaks but gives you version control, testing, and logic that survives staff turnover. For businesses where checkout rules encode real revenue policy, that is a better place to be. The migration cost is the price of getting there.

04. The Three Replacement Paths, in the Right Order

Most stores should not rebuild every script as a custom function. Evaluate each rule against three options, in this order:

Path 1: Native Shopify features.

Shopify's native discounts have improved enormously since most scripts were written. Combinable discounts, automatic discounts with customer segment conditions, and B2B price lists cover a large share of what line item scripts used to do. A script that gave wholesale customers 15 percent off is now a price list. A stacking rule is often just combinable discount settings. Zero code, zero apps, zero maintenance. Check this path first for every single rule.

Path 2: Functions-based apps.

The App Store now has mature apps built on Function APIs for discount logic, shipping rules, and payment customization. If your rule is common (hide COD over a threshold, rename a shipping rate by region, tiered volume discounts), a configurable app is faster and cheaper than a custom build, and the vendor maintains it as Shopify's APIs evolve.

Path 3: Custom functions.

Reserve custom development for logic that is genuinely yours: pricing driven by ERP data, complex B2B terms by account tier, freight logic tied to pallet configuration, rules that combine customer history with cart contents. This is where manufacturers and wholesalers usually land, because their checkout logic encodes trading terms no app anticipates. A custom function lives in a custom app, gets tested on a development store, and deploys like real software.

05. Scoping the Rebuild: Effort, Cost, and Timing

Plan the work in three tiers:

• Days: rules that map to native discounts, price lists, or a configurable app. Most stores can restore the majority of lost behaviour this way in the first week.
• Weeks: a custom function for one or two mid-complexity rules, including scoping, development, testing on a development store, and a monitored production rollout.
• Months: a full portfolio rebuild where layered discount, shipping, and payment scripts interacted with each other. These need a staged plan, because rules that interacted in Scripts can conflict when rebuilt independently.

Two scoping mistakes to avoid. First, rebuilding scripts nobody could explain: if the inventory turns up a rule with no owner and no measurable revenue impact, retire it deliberately instead of paying to port it. Second, skipping the test store: functions execute during checkout, and a bug there costs real orders. Test against the same carts you used in the audit before anything reaches production.

06. Why This Matters for Canadian Merchants Before BFCM

The timing is the real risk. BFCM planning for Canadian stores starts in late summer, and promotion mechanics are exactly the logic Scripts used to run: stacked discounts, gift-with-purchase thresholds, shipping promotions. A store that patches July's gaps manually and defers the rebuild will hit October with untested promotion logic in the highest-revenue weeks of the year. The window to rebuild and test calmly is now, in July and August.

There is also an upside worth taking. Because Functions run on standard plans through apps, some Plus stores that were only on Plus for Scripts can now re-evaluate their plan. And for wholesalers and manufacturers, the same custom app that hosts your checkout function is a natural home for deeper B2B logic. If you are weighing that kind of scope, our guide to migration vs integration projects covers how to keep the scope honest, and the Shopify B2B features guide shows what native B2B now covers before you write code.

Zoom out and this retirement is part of a bigger platform direction: Shopify is moving all checkout customization onto governed, app-based APIs, the same foundation that powers checkout extensibility and the agent-readable storefronts we covered in our agentic commerce guide. Stores that rebuild on Functions properly are not just fixing July's breakage. They are on the architecture Shopify is building toward.

07. Frequently Asked Questions