Shopify Scripts Are Officially Gone. What Now?

It’s the second week of July. A customer writes to support: the “buy three, get 10% off” deal on your homepage didn’t work at checkout. Support rebuilds the cart. No discount, no error, nothing in the admin that looks broken. The banner still makes the promise. The checkout simply stopped keeping it.

If that sounds familiar, your store is probably one of the Shopify Plus stores where Shopify Scripts stopped working on June 30, 2026, before every rule had been moved over. On that date Scripts stopped running for everyone, and checkout fell back to Shopify’s default behavior. The good news is that everything a Script did can be rebuilt, and usually in a form that breaks less often.

This guide is for owners and managers of Shopify Plus stores who want to know what went missing, how to find it, and what to replace it with. [link: Shopify services page]

What changed when Shopify Scripts stopped working

Shopify set the timeline in its developer changelog [ext link: shopify.dev changelog, Shopify Scripts deprecation]. Two dates mattered:

• April 15, 2026: Scripts could no longer be edited or published.
• June 30, 2026: all Scripts stopped running.

Scripts were small pieces of Ruby code, available only on Plus, that ran during checkout. They came in three kinds:

• Line item scripts changed prices in the cart: tiered discounts, buy-one-get-one deals, wholesale pricing.
• Shipping scripts hid, renamed or reordered shipping methods, or discounted shipping rates.
• Payment scripts hid, renamed or reordered payment methods.

When they stopped, nothing crashed. That is exactly the problem. A missing Script doesn’t show an error at checkout. The rule disappears, and customers see standard prices, every shipping option and every payment method.

How to check if your store lost a Script

Three checks, from least to most effort.

1. Start with what Shopify shows you. Shopify added a Scripts customizations report to the admin to help merchants map each Script to a replacement. If you can still open it, it’s the fastest inventory you’ll get.

2. Compare orders from June and July. Look for discount codes or automatic discounts that showed up regularly in June and then vanished. Check whether average shipping cost jumped. Look for orders paid with methods you used to hide.

3. Make a test purchase for every promise on your site. Every banner, every “free shipping over $100,” every B2B price tier. Build the cart the way a real customer would and watch what checkout does.

The third check catches the quiet failures. Say your store had a payment script that hid “pay later” options on orders over $2,000 because of fraud risk. Since July that option is back on every order, and nobody notices until the first chargeback arrives.

[IMAGE: a short checklist graphic with the three checks | alt: “Checklist for finding Shopify Scripts that stopped working after June 30, 2026”]

What Shopify Functions are, in plain words

Shopify’s replacement for Scripts is called Shopify Functions. Here is how they work, without the jargon.

A Function is a small program that Shopify calls at one specific moment, for example when it calculates the cart total or when it shows shipping options. Shopify hands the Function the data it needs: what’s in the cart, who the customer is, where the order ships. The Function decides what to change and sends back its answer. Shopify applies it.

Under the hood, Functions are written in JavaScript or Rust and compiled to WebAssembly, a compact format that runs very fast. They run on Shopify’s own infrastructure with strict time limits. For you as a merchant, this changes two things.

First, checkout stays fast during traffic spikes. A Function can’t take its time, so it can’t slow down a Black Friday checkout.

Second, settings can live in the admin. A Function always ships inside an app, and a well-built app gives your team settings to change. Raising a discount threshold from $100 to $120 becomes a form field, not a ticket for a developer.

There is a trade-off. Functions are narrower than Scripts. Each one does one job through a dedicated API: discounts, cart transforms, delivery customization, payment customization, cart validation and a few others. One large Script that did five things at once usually becomes several Functions.

Which Function replaces which Script

Each type of old Script has a direct replacement. Some Scripts split in two, because Functions separate jobs that Scripts used to mix.

Old Script	Replaced by	What it does	Example
Line item script	Discount Function	Discounts on products and on the order total	“Buy 3, get 10% off,” wholesale prices for customers tagged B2B
Line item script (bundles)	Cart Transform	Groups cart lines into a bundle or splits a bundle into items	A gift box of three products sold as one item
Shipping script	Delivery Customization	Hides, renames or reorders delivery options	Hide express shipping for oversized items
Shipping script (shipping discounts)	Discount Function	Discounts on delivery rates	Free shipping for VIP customers on orders over $150
Payment script	Payment Customization	Hides, renames or reorders payment methods	Hide “pay later” on orders over $2,000
No Script equivalent	Cart and Checkout Validation	Blocks checkout when a rule isn’t met	Limit a launch product to five units per customer

Shopify runs these Functions in a fixed order during checkout: first changes to cart lines, then discounts, then delivery options, then payment methods, and validation last. That order matters when you rebuild several rules at once. A validation rule, for example, always sees prices after discounts have been applied.

Stores with several warehouses also get two Functions that Scripts never had: Fulfillment Constraints and Order Routing Location Rule, which control which location ships an order.

Three ways to replace a Script

1. A ready-made app from the Shopify App Store

Plenty of apps are built on Functions and cover the common cases: tiered discounts, free gifts, hiding payment methods by country. Public apps built on Functions work on any Shopify plan.

This is the right choice when your rule is standard. Setup is quick and the upfront cost is low. You pay a monthly fee and accept the app’s way of doing things.

2. A custom Function

A developer writes a Function for exactly your rule and ships it inside a custom app installed only on your store. Custom apps with Functions are a Shopify Plus feature.

This makes sense when the rule is specific to your business: pricing that depends on customer tags and product metafields, wholesale logic, combinations of conditions no app supports. It costs more upfront, but you own the logic and don’t pay per-app fees for it.

3. Rethink the rule

Some Scripts were written years ago for a campaign nobody remembers. Before rebuilding one, ask whether it still makes you money. It’s common to find that two or three old Scripts can be replaced by a single native Shopify discount, or dropped altogether.

Most stores end up with a mix: native discounts for the simple cases, an app or two, and one custom Function for the logic that actually sets them apart.

How we approach a Scripts to Functions migration

We’ve moved Plus stores from Scripts to Functions. The work follows the same five steps every time.

1. Recover the logic. We gather the old Script code if it’s still available, a sample of orders, and whatever your team remembers about each rule.

2. Write the rules down in plain English. This is where working with AI saves the most time. We give the old Ruby code to an AI model and ask it to describe every rule and every exception in plain language, for example: “if the customer is tagged wholesale and the cart has more than 10 units from the Bulk collection, take 15% off those lines only.” A developer then checks that description against the code line by line. Untangling a Script with years of patches by hand is slow and easy to get wrong. With this step it becomes a review instead of an excavation.

3. Agree on the rules with you. You approve the plain-English list before any code is written. This is the moment to cut rules you no longer need.

4. Build and test. We build the Functions and create a test cart for each rule and each exception. AI helps draft the test cases, and a developer decides which ones matter. Everything runs on a development store first.

5. Release and watch. After launch we compare a week of real orders against the expected behavior, so anything the tests missed shows up quickly.

When you don’t need a custom Function

If your Script did something standard, such as “10% off orders over $100” or free shipping above a threshold, native Shopify discounts or a public app will handle it. Paying for custom development there makes no sense, and we’ll say so on the first call.

Custom Functions earn their cost when the rule is tied to how you make money: wholesale tiers, complex bundles, payment rules that protect you from fraud, shipping logic driven by product data. If you’re not on Shopify Plus, custom Functions aren’t available at all, and a public app is your route.

FAQ

Do Shopify Functions require Shopify Plus?
Not always. Public apps built on Functions work on any plan. Custom apps with Functions require Plus.

Can I still edit my old Scripts?
No. Editing stopped on April 15, 2026, and Scripts stopped running on June 30, 2026.

What does my checkout do now that Scripts are gone?
It uses Shopify’s default behavior. Any discount, shipping or payment rule a Script handled no longer applies until you rebuild it.

How long does a migration take?
It depends on how many rules you had and how tangled they are. A standard rule covered by an app can be live the same day. A custom Function for one specific rule typically takes several days to two weeks, testing included. Stores with many interlocking Scripts need longer.

My conversion tracking went quiet too. Is that related?
Probably, but it’s a neighboring change. Shopify also retired Additional Scripts on the thank-you and order status pages, and tracking events now go through Web Pixels. If your ad platforms stopped receiving purchases, check that first.

Start with the three checks

Shopify Scripts stopped working more than three months ago, and many Plus stores still don’t know which rule went missing. Run the three checks above, list what’s broken, and decide for each rule: app, custom Function, or let it go. [link: related article on Shopify custom apps]

Not sure what your old Scripts used to do? Send us your store URL and the rules you remember. We’ll map what broke and how to bring it back.

Sources:

What is a Shopify Script (Wholesale Helper)

Shopify Scripts will be deprecated on June 30, 2026 (shopify.dev changelog)

Migrating from Shopify Scripts to Shopify Functions (shopify.dev)

Transitioning from Shopify Scripts to Shopify Functions (Shopify Help Center)

Shopify Scripts deprecation: editing ends April 15 (Shopify changelog)

Shopify Scripts sunset June 30 (Nova Data)

Shopify Scripts to Functions Migration (Sherocommerce)

Shopify Checkout Extensibility (Vercel)