Shopify Scripts Are Deprecated: How to Migrate to Shopify Functions (Complete Guide)
Shopify Scripts stopped executing on June 30, 2026. What's affected, how to audit old Scripts, the three paths to Shopify Functions, and a cutover plan.

The short version: Shopify Scripts stopped executing on June 30, 2026 — permanently, with no grace period and no rollback. If your store ran discount, shipping, or payment Scripts, that logic must be rebuilt as Shopify Functions, or it stays broken at checkout. This is the complete migration guide.
We build and migrate Shopify checkout logic, so this is the exact process we run with clients. If Scripts logic stopped on your store before you replaced it, skip to "If you missed the deadline" at the end first.
The two deadlines
Two dates mattered:
- June 30, 2026 — the hard cutoff. All Shopify Scripts stopped executing. Shopify's Help Center says Scripts that were still published have been deactivated and no longer work. No grace period, no rollback.
- April 15, 2026 — the editing freeze. From this date Scripts could no longer be created, edited, or published. Existing Scripts kept running until June 30, but a bug couldn't be fixed.
So the migration was never optional. Anything that was still on Scripts after June 30 reverted to default behavior.
What's affected
Shopify Scripts powered three kinds of checkout logic, all of which need replacing:
- Line-item Scripts — custom and combined discounts, tiered/volume pricing, BOGO, cart-based promotions.
- Shipping Scripts — hiding, renaming, reordering, or re-rating delivery options.
- Payment Scripts — hiding, renaming, or reordering payment methods.
Plus the older checkout.liquid customization, which Shopify retired separately: it's unsupported for the Information, Shipping, and Payment steps, and was sunset for the Thank you and Order status pages on August 28, 2025. Any checkout.liquid customization has to move to Checkout Extensibility.
What replaces them: Shopify Functions
Shopify Functions are the official replacement. They're small pieces of custom logic (written in Rust or JavaScript, compiled to WebAssembly) that run natively on Shopify's infrastructure — faster than Scripts, with no external server, and friendly to the Built for Shopify performance bar. They cover discounts, delivery and payment customization, and cart/checkout validation, and are delivered as app extensions. (For the deeper "when is a Function the right tool vs. a full app" decision, see Shopify Functions vs Apps.)
Step 1 — Audit your Scripts (use the built-in report)
Don't guess what you're running. Shopify gives you the exact list:
- In your Shopify admin, go to Apps → Script Editor.
- In the "Replace your Shopify Scripts" banner, click Replace Shopify Scripts.
The Scripts customizations report lists every active Script, what each one does, and links to recommended replacement apps or Function API tutorials. That report is your migration checklist — export it and work through it line by line.
Step 2 — Choose a path for each Script
There are three ways to recreate each Script. Pick per use case:
| Migration path | Best for |
|---|---|
| No-code Functions-powered app | Common cases — most discount, shipping, and payment rules have an off-the-shelf app. Fastest, no build. |
| Native Shopify feature | Basic rules Shopify now handles natively (e.g., simple automatic discounts). |
| Custom Shopify Function | B2B/customer-specific pricing, ERP-driven logic, multi-condition discounts, bespoke shipping/payment rules — anything off-the-shelf can't do. |
Mapping by Script type:
- Discount Scripts → discount Functions (or a discount app). Available on all plans.
- Shipping Scripts → delivery customization Functions (Plus).
- Payment Scripts → payment customization Functions (Plus).
Step 3 — Build and test on a development store
Rebuild the logic, then validate it before touching production:
- Recreate each rule as a Function (or configure the app) on a dev store.
- Test every edge case the Script covered — combinations, thresholds, exclusions, B2B vs DTC, edge quantities.
- Heads-up: a Script and a Function targeting the same checkout logic can conflict if both are live. Don't leave them running in parallel longer than a quick verification.
Step 4 — Cut over to production, then monitor
- Deploy the Function to production.
- Disable the corresponding Script immediately once the Function is verified (to avoid the conflict above).
- Monitor checkout closely for the first days — discounts applying correctly, shipping/payment options behaving, no abandoned-cart spike.
The timeline reality
A focused migration of 5–15 scripts realistically takes 8–14 weeks — scoping, development, QA on a dev store, and a monitored cutover. That's the honest number, and it's why "we'll deal with it later" has run out of road.
If you missed the deadline
If Scripts logic stopped before you replaced it, an 8–14 week project is too slow — so triage:
- Cover what you can with no-code Functions-powered apps now — this brings back the bulk of your discount/shipping/payment logic quickly.
- Prioritise revenue-critical logic — whatever directly affects what customers pay or which options they see.
- Rebuild the complex, custom rules as Functions right after, on a proper timeline, replacing the stopgap apps where needed.
The one thing you cannot do is nothing — there's no Script to fall back on.
We run Scripts-to-Functions migrations end to end — audit, custom Functions, and the production cutover — and we move fast when checkout logic is affected. See our Shopify app development and Shopify store development work, or talk to us.
Frequently asked questions
When are Shopify Scripts deprecated?
Shopify Scripts stopped executing on June 30, 2026, a hard cutoff with no grace period. Shopify's Help Center says any Scripts that were still published have been deactivated and no longer work. Before that, from April 15, 2026, Scripts could no longer be created, edited, or published.
What replaces Shopify Scripts?
Shopify Functions, often alongside Checkout Extensibility. Functions are small pieces of custom logic (discounts, shipping/delivery customization, payment customization, cart and checkout validation) that run natively on Shopify's infrastructure — faster than Scripts and with no external server. They're delivered as app extensions, either via a no-code Functions-powered app or a custom build.
How do I see which Scripts I need to migrate?
Use the built-in report: in your Shopify admin go to Apps > Script Editor, and in the 'Replace your Shopify Scripts' banner click 'Replace Shopify Scripts'. It lists every active Script, what each does, and links to recommended replacement apps or Function API tutorials — your migration checklist in one place.
Do Shopify Functions require Shopify Plus?
Not all. Discount Functions (product, order, and shipping discounts) work on every plan. Delivery and payment customization Functions, and checkout UI extensions, require Shopify Plus as part of Checkout Extensibility. So basic discount logic is open to all stores; deeper checkout customization is a Plus capability.
What happened to stores that didn't migrate by June 30, 2026?
Any logic still running on Scripts stopped on that date — discount combinations, tiered/volume pricing, shipping rules, and payment-method customizations all reverted to default. There's no rollback and no way to fix Scripts in place. The result is broken or incorrect checkout behavior until the logic is rebuilt as Functions.
How long does a Scripts-to-Functions migration take?
A focused migration of 5–15 scripts typically runs 8–14 weeks end to end — scoping, development, QA on a development store, and a monitored production cutover. If Scripts logic stopped before you replaced it, the fastest way back is to cover what you can with no-code Functions-powered apps now, then rebuild the complex, custom logic as Functions.
Building something on Shopify?
We design, build, and maintain Shopify apps, stores, and AI products — to the standard this article describes.








