Shopify Scripts Stopped on June 30, 2026: How to Restore Checkout Logic with Functions
What happened to Shopify Scripts?
Shopify Scripts stopped executing on June 30, 2026. Line Item, Shipping, and Payment Scripts no longer run. To restore that checkout logic, recreate it with Shopify Functions: Discount Function API for discounts, Cart Transform for bundles, Delivery Customization for shipping options, and Payment Customization for payment methods. Shopify’s Scripts customizations report lists what used to run.
This is an August 2026 refresh of our January guide. The mapping still holds. The deadline does not: Scripts already stopped, and Shopify will not turn them back on.
Shopify confirmed the dates in its developer changelog and merchant changelog:
| Date | What changed |
|---|---|
| April 15, 2026 | Editing and publishing Scripts stopped. Live Script Editor code was frozen. |
| June 30, 2026 | All Shopify Scripts stopped executing. Checkout ignores that logic. |
Shopify Plus merchants used Scripts (Ruby in Script Editor) for cart discounts, shipping option rules, and payment method gating. Those rules now need a Function-based app or a custom Function on Plus.
What broke when Shopify Scripts stopped?
If a Script was still live on June 30, Shopify no longer runs it. Customers see default checkout behavior. Typical fallout:
| Old Script type | What merchants often see now |
|---|---|
| Line Item Scripts | Custom discounts stop, bundle pricing disappears, cheapest-item or VIP deals revert to list price |
| Shipping Scripts | VIP “free shipping” labels vanish, hidden rates reappear, region or cart rules stop filtering options |
| Payment Scripts | COD or other gated methods show for carts that used to be blocked, preferred method order resets |
Shopify did not migrate the logic for you. The Scripts customizations report is a record of what used to run, plus app and Function API links. You still rebuild each rule you want to keep.
If checkout UI still depends on checkout.liquid, treat that as a separate project. Backend rules move to Functions. Checkout UI moves to Checkout Extensibility. We cover the UI side in the Checkout Extensibility migration guide.
Shopify Scripts vs Shopify Functions
| Shopify Scripts | Shopify Functions | |
|---|---|---|
| Status | Stopped executing June 30, 2026 | Current Shopify platform for this logic |
| Who could use it | Shopify Plus, Script Editor | Public Function apps on any plan; custom Function apps on Plus |
| Where it ran | Ruby in Script Editor | App extensions Shopify runs at checkout |
| Discount logic | Line Item Scripts | Discount Function API (product, order, and shipping discount classes) |
| Bundles / line changes | Often mixed into the same Script | Cart Transform, kept separate from discount math |
| Shipping options | Shipping Scripts | Delivery Customization |
| Payment methods | Payment Scripts | Payment Customization |
| Checkout blocks | Cart error messages in Scripts | Cart and checkout validation functions |
| Day-to-day edits | Edit Ruby, publish in Script Editor | Many apps expose admin settings; custom logic ships with an app deploy |
| Testing | Limited live/editor testing | Test on a development store before you publish |
Bottom line: Scripts are a historical record. Functions (or a Function-based app) are how you put the same business rules back on checkout.
How to replace Shopify Scripts with Shopify Functions
You cannot patch Script Editor. Recreate the rules, then prove them on checkout.
- Open the Scripts customizations report. In Shopify admin, go to Apps, then Script Editor, and open the report. Shopify’s transitioning to Functions help article describes this report as listing customizations that were active before June 30, 2026. Click each script name, then save or export what it did.
- Decide which rules to keep. Drop dead Scripts (old campaigns, unused VIP tags, duplicate shipping hides). Every rule you keep becomes an app install or a Function to build and test.
- Map each script to the right Function. Discounts go to the Discount Function API. Line merges and splits go to Cart Transform. Shipping option changes go to Delivery Customization. Payment method changes go to Payment Customization. “Customer cannot check out if…” rules go to validation functions.
- Recreate with an app or a custom Function. If a public app matches the rule, install it and configure it in admin. If the rule is store-specific, Plus merchants can ship a custom app that contains Function APIs. Stores on any plan can use public App Store apps that include Functions. Only Plus can use custom apps with Function APIs.
- Test checkout, then publish. Scripts are gone, so there is no live side-by-side with the old Ruby. Reproduce the old carts on a development store: VIP customer, bundle, high-value COD, restricted product. When discounts, rates, payment methods, and error messages match the old intent, publish to live checkout.
Need a second pair of eyes on the report? Get a Scripts-to-Functions audit.
What replaces Line Item Scripts?
Line Item Scripts used to walk the cart and change prices: spend thresholds, BOGO, “cheapest item 50% off,” VIP discounts.
Discounts: use the unified Discount Function API. Shopify retired the separate Product, Order, and Shipping Discount Function APIs. One Discount Function can apply savings across product, order, and shipping discount classes.
Bundles that change line items: use Cart Transform to merge lines into one presented item or expand a bundle into components. Keep that separate from discount math. Mixing both in one Script was common. Splitting them is the usual Functions design.
Example: “If cart total is over $100, take 50% off the cheapest item.” That is a Discount Function that reads the cart subtotal and targets the lowest-priced line. It is not Cart Transform, unless you also change how lines are grouped.
What replaces Shipping Scripts?
Shipping Scripts renamed rates (“Standard” to “Free VIP Delivery”), hid expensive options, or filtered methods by region or cart contents.
Use Delivery Customization to rename, reorder, or hide delivery options from cart contents, customer tags, or similar checkout context.
Example: “Hide Express Shipping when the cart includes a product tagged Hazardous.” A Delivery Customization function checks those tags and hides the Express option.
What replaces Payment Scripts?
Payment Scripts hid or reordered gateways: no COD over $1,000, preferred methods first for returning customers, blocked methods for certain groups.
Use Payment Customization to rename, reorder, or hide payment methods. Shopify documents hide, rename, and reorder as supported operations. Some extras (such as payment terms and hiding specific placements) are Plus-only.
Example: “Hide Cash on Delivery when the order total is over $1,000.” A Payment Customization function reads the cart total and hides COD above that threshold.
Other Script jobs that need their own Function
One Script file often did several jobs. On Functions, split them:
- Discount Functions: product, order, and shipping discount classes through the unified Discount Function API
- Cart Transform: bundle presentation and line merge/expand
- Validation functions: block checkout (for example, max 5 units of a limited product)
- Delivery Customization and Payment Customization: option lists, not price math
Shopify publishes Function tutorials for discounts, delivery options, payments, validation, and bundles in the Functions documentation. Use those when you are building rather than installing an app.
App Store app or custom Function?
| Path | Best when | Plan notes |
|---|---|---|
| Public Function app | The rule is common (hide a method, simple discount, standard bundle) | Any plan can install App Store apps that include Functions |
| Custom Function app | The rule is specific (multi-tag VIP stack, unusual bundle math, mixed market exceptions) | Custom apps with Function APIs are Plus-only |
Start with the report’s recommended apps. Build custom only when no app matches the rule, or when an app would fight another checkout app.
After deploy, many Function apps let merchants change thresholds and labels in Shopify admin. Custom Functions only get that if the app exposes settings. Otherwise a developer ships a new version.
How long does a post-sunset migration take?
You no longer have a “migrate before June 30” buffer. The work is restore-and-QA.
| Phase | Typical duration | What you actually do |
|---|---|---|
| Audit | 3–10 days | Read the customizations report, match it to live checkout, drop dead rules |
| Build or install | 1–6 weeks | Configure apps or build Functions for the rules you kept |
| QA | 1–4 weeks | Replay VIP, bundle, high-value, and restricted carts on a development store |
| Publish | A few days | Release to live checkout, watch the first real orders, keep a rollback plan for the new app |
Straightforward stores with a handful of rules often finish in 2–6 weeks. Heavy Plus checkouts with bundles, payment gating, and several markets often take 8–16 weeks, mostly in QA.
Black Friday and other peak events still matter. Functions run on Shopify’s checkout infrastructure instead of Script Editor Ruby, which is why Shopify moved this logic. Do not cut QA to “get something live” the week before a sale.
Frequently Asked Questions
Did Shopify Scripts stop working?
Yes. Shopify Scripts stopped executing on June 30, 2026. Shopify froze editing and publishing on April 15, 2026, then turned execution off on June 30. Checkout now ignores Script Editor logic and falls back to standard discounts, shipping rates, and payment methods.
What replaced Shopify Scripts?
Shopify Functions replaced Shopify Scripts. Use the Discount Function API for discounts, Cart Transform for bundles, Delivery Customization for shipping options, Payment Customization for payment methods, and cart validation functions for checkout blocks. Recreate the logic with an App Store app or a custom app.
Where is the Shopify Scripts customizations report?
In Shopify admin, open Apps, then Script Editor, and open the Shopify Scripts customizations report. Shopify’s help center says the report lists customizations that were active before the June 30, 2026 deprecation, plus recommended apps and Function API guides. You still have to rebuild each rule you want to keep.
Do I need Shopify Plus to use Shopify Functions?
Stores on any plan can install public App Store apps that include Functions. Only Shopify Plus stores can use custom apps that contain Shopify Function APIs. Some Function capabilities are Plus-only. Scripts themselves were a Plus feature, so most stores in this migration are Plus.
What replaces Line Item Scripts for discounts?
Use Shopify’s unified Discount Function API. One function can apply product, order, and shipping discount classes. It replaces the older Product, Order, and Shipping Discount Function APIs. If the script also merged or split cart lines, add Cart Transform for that part and keep discount math in the Discount Function.
What replaces Shipping Scripts and Payment Scripts?
Shipping Scripts map to Delivery Customization, which can rename, reorder, or hide delivery options. Payment Scripts map to Payment Customization, which can rename, reorder, or hide payment methods. Neither API copies your old Ruby file automatically. You rebuild the rule, then test it on checkout.
Can I still edit Shopify Scripts?
No. Shopify stopped editing and publishing Scripts on April 15, 2026, and stopped executing them on June 30, 2026. There is no Script Editor patch path. Use the customizations report as a record of what used to run, then recreate the rules with Functions or an app.
How long does a Shopify Scripts to Functions migration take?
A store with a few clear rules can often finish in 2 to 6 weeks. A Plus checkout with bundles, VIP shipping, payment gating, and several markets often takes 8 to 16 weeks, mostly in QA. After June 30 you cannot run Scripts in parallel, so test on a development store before you publish live.
Restore the rules that still make you money
If discounts, free-shipping labels, or payment gating dropped after June 30, the customizations report is the inventory. Functions (or a Function app) are the rebuild.
At Agam Tech we help Shopify Plus brands:
- Audit the customizations report against live checkout
- Map each kept rule to a Discount Function, Cart Transform, Delivery Customization, Payment Customization, or validation function
- Build or configure, then test on a development store before publish
Ready to Build Something Amazing?
Let's discuss your project. From ecommerce stores to custom web apps, we bring your vision to life.