Shopify Scripts stopped working on June 30, 2026. Here's what to do now.
If your store had a custom discount, BOGO, or bundle Script, it stopped executing on June 30, 2026, silently. No error, no alert, nothing in your logs. Here's exactly what happened, what migrating to Shopify Functions actually involves, and an honest answer on what Stackable can rebuild for you.
- Shopify Scripts stopped executing on June 30, 2026, for every store still running them.
- Any custom discount, BOGO, or bundle logic that lived inside a Script stopped applying on that date.
- The failure is silent by design: a Shopify Function whose conditions don't match a given cart simply never fires. It doesn't throw an error, and Shopify doesn't notify you.
Merchants working through this migration describe the same danger on the Shopify community forums:
“My old Script quietly stopped applying a discount and I only found out because a customer complained about being charged full price. There was no error, no alert, nothing in the order logs. I'd been running on a broken setup for weeks before I noticed.”
That's the core risk of moving from Scripts to Functions: a Function is either well-formed and running, or it's misconfigured and silent. There's no visible in-between state, so a mismatched condition, a typo in a threshold, a rule scoped to the wrong collection, produces exactly the same silence as a Function working correctly. The only way to catch it is to deliberately test both directions before you trust it live.
Four things worth knowing before you start
It's three separate migrations, not one
A single Script file could touch discount logic, shipping rates, and payment customization all at once. Functions split that into three separate Function types, discount, delivery, and payment, each configured and deployed independently. Migrating "my Script" usually means migrating up to three different things.
No-code builders usually cover discounts and BOGO only
If your Script also touched shipping rates or payment methods, a no-code discount-Function builder, Stackable included, does not reach those. Delivery and payment customizations need a developer to write that Function directly.
Keep your old Script source now
Once the Script Editor is fully retired, its stored code becomes unrecoverable. Export or copy your old Script source today, even if you are not ready to migrate yet, so you have a reference for whatever replaces it.
Test a should-fire cart and a should-not-fire cart
Before trusting a new Function, build two test carts: one that should trigger it, and one that deliberately should not. A Function that fires when it should not is just as costly as one that silently never fires.
An honest answer on scope
Stackable rebuilds rule-based discount logic on native Shopify Functions. It does not run arbitrary custom code.
Stackable rebuilds this
- Tiered / volume discounts (e.g. "buy 3+, save 15%")
- Buy X Get Y and BOGO logic, including repeat tiers
- Explicit discount stacking rules between offers
- Scheduled start, end, and instant pause on any campaign
You'll still need a developer for this
- Arbitrary custom code your old Script ran (bespoke pricing formulas, one-off conditions no builder covers)
- Shipping / delivery customizations (a separate Function type)
- Payment customizations (a separate Function type)
- Anything that does not reduce to a rule-based discount configuration
If your old Script did something in this list, a no-code builder, Stackable included, can't reach it. That's a developer-written Function, not a config screen.
Common questions
Are my old Scripts gone?
Scripts stopped executing on June 30, 2026, but that isn't necessarily the same moment the Script Editor's stored source is deleted. Export or copy your old Script code now regardless: once Shopify fully retires the editor, it becomes unrecoverable.
Will I get an error if a Function is misconfigured?
No. A Function whose conditions don't match a cart simply never fires, silently, with no error and no alert. Always test with a cart that should trigger it and one that should not before you trust it in production.
Does Stackable replace everything my old Script did?
Only the rule-based part: tiered and volume discounts, BOGO, discount stacking, and scheduling, all rebuilt on native Shopify Functions. Stackable does not run arbitrary custom code. If your Script did something genuinely bespoke, a custom pricing formula or a condition no builder covers, that still needs a developer to write the Function directly.
What about the shipping or payment logic my Script handled?
Those are separate Function types (delivery and payment) that Stackable does not touch. A developer needs to migrate those independently of your discount logic.
Where can I read the full migration write-up?
Our first blog post walks through the Scripts deprecation and the migration path in more detail.
Related features
Discount Stacking
How to stack discounts in Shopify comes down to settings the platform hides by default: every discount belongs to a class (product, order, or shipping), and whether two discounts combine is decided per offer, per class. Stackable puts those combine switches on every offer, so a volume tier, a spend goal, and free shipping add up exactly the way you configured them, every time.
BOGO / Buy X Get Y
Running BOGO beyond the 100-product cap isn't possible with Shopify's native Buy X Get Y discount: it stops letting you add eligible products once you pass 100, and it only applies once per order. Stackable removes both limits and adds cheapest-item-free logic on top.
Scheduled Sales
Shopify scheduled sales fail two ways in the wild: campaigns that silently never start, and live campaigns with no pause button. Stackable's scheduler runs on the same reliability guarantee as its checkout math, and pausing takes effect storefront-wide in under a minute.
Install Stackable and rebuild your rule-based discounts
Volume tiers, BOGO, stacking, and scheduling, running on native Shopify Functions from day one.
Free plan available. No card required.