Shopify Scripts stopped executing on 30 June 2026. If your minimum order quantities, purchase caps or case-pack rules ran on a Script, they stopped applying that day — and nothing announced it. Orders carried on being placed, just without the rules. This is how to find out whether your store was affected, what you can still recover, and what to rebuild the rules on now.
Two dates, both now past
Shopify's changelog states it plainly:
- 15 April 2026 — Scripts could no longer be edited or published.
- 30 June 2026 — Scripts stopped executing.
The second date is the one that changed behaviour. The first is the one that makes the cleanup harder, and we will come back to it.
The failure was silent, which is the whole problem
A Script that stops running does not error. It does not appear in a log you would notice, it does not flag on an order, and it does not email anybody. The rule simply stops being evaluated, and checkout proceeds as though it had never existed.
So the symptoms are not technical, they are commercial, and they look like ordinary business until somebody counts:
- Orders for a single unit of a product sold in packs of six.
- Wholesale accounts placing orders below the minimum they agreed to.
- Quantities that are not a multiple of your case pack, arriving at a warehouse that packs in cases.
- One customer buying far more of an allocated product than your cap allowed.
Any of these individually looks like a customer doing something unusual. Together, starting from a specific date, they are a rule that stopped.
That specific date is the useful part. If your quantity rules ran on Scripts, the behaviour changed on 1 July 2026, and everything before it is clean.
Finding out in ten minutes
Three checks, in order of how conclusive they are.
1. Try to break the rule. Take a product that should carry a minimum — say six — put one in the cart and go to checkout. If you reach the payment step, the rule is not running. This is conclusive and takes two minutes.
Do it through a cart permalink as well: yourstore.com/cart/VARIANTID:1 puts one unit straight into a cart and heads for checkout, skipping any product-page logic. That is the path a Script covered and a theme customisation does not.
2. Look at orders since 1 July. Filter or export orders from that date and look for quantities your rules would have prevented. If you find none, either the rules were migrated or nobody happened to trigger them — the first test settles which.
3. Check whether Script Editor is still in your admin. Its presence tells you Scripts were in use at some point. It will not tell you what they did.
Why 15 April makes the cleanup harder
The standard migration advice was: write down what your Scripts enforce, then rebuild those rules on Functions. Sensible, and it assumed you could still read them.
After 15 April you could not edit or publish Scripts, and the tooling to inspect them went with the ability to work on them. So if nobody documented the rules while that was possible, the code is no longer a source you can consult.
Which leaves reconstruction from the business rather than from the implementation, and that is genuinely different work. The questions are:
- Which products had a minimum, and what was it? Your supplier's case-pack sizes are usually the honest source.
- Which customers had different rules? Wholesale agreements, tagged accounts, anyone with negotiated terms.
- Were there caps, and on what? Limited releases, allocated stock, anything you have ever had a reseller problem with.
- Was anything time-bound? Launch caps and flash-sale limits are the ones most likely to have been forgotten.
Ask the people who asked for the rules, not the people who built them. The commercial reason survives; the implementation did not.
What to rebuild on
Shopify Functions replaced Scripts for checkout-time logic. A cart validation Function runs inside Shopify's own checkout, evaluates when the buyer tries to proceed, and can block the order with a message you write.
The properties that matter are the same ones Scripts had, which is why it is a genuine replacement rather than a downgrade:
- It cannot be bypassed. No URL, saved cart or API path reaches an order without passing it.
- It applies on every surface — online store, dynamic checkout buttons, buy buttons, restored carts.
- It does not touch storefront performance, because it runs server-side at checkout rather than as JavaScript on every page.
Two routes: a custom Function written by a developer, or an app built on Functions. The custom route makes sense if your rules are genuinely unusual. For minimums, maximums, multipliers and per-customer caps, an app is work you can buy — Limit uses checkout enforcement on every plan including the free one.
What not to rebuild on
Two tempting shortcuts, both of which recreate the problem you just had.
Theme-level validation. A minimum in the quantity selector, or JavaScript that blocks the cart button. It stops an honest shopper using the page as designed, and nothing else. Cart permalinks, saved carts, dynamic checkout buttons and draft orders all skip it. If a Script was doing the work, a theme tweak is a downgrade, not a migration.
Waiting to see whether it matters. The failure is silent in both directions — you will not get an alert when it starts costing you, and the cost is spread across orders that each look normal.
What you cannot recover
Orders placed between 1 July and whenever you fix this were placed legitimately as far as the customer is concerned. They met the rules that were actually in force, which were none.
So there is nothing to claw back, and cancelling them would be your error being paid for by a buyer who did nothing wrong. What is worth doing is counting them — the total tells you what the gap cost, which is the number that justifies the time to rebuild properly rather than quickly.
If any of them created a fulfilment problem — a part-case that had to be repacked, a wholesale order below the economic minimum — that cost is the real one, and it is ongoing until the rules are back.
Rebuilding without repeating the mistake
- Write the rules down first, in business terms, before touching any app. This is the document that was missing in April.
- Rebuild on Functions, whether through an app or a custom Function.
- Test through a cart permalink, not the product page. That is what proves enforcement is real.
- Write the error messages properly. Name the number and the product; "Cart does not meet requirements" converts nobody.
- Put the requirement on the product page too. Enforcement belongs at checkout, communication belongs before it.
- Keep the written rules somewhere findable. The next migration will come, and a document survives a platform change in a way code does not.
Where to go next
If you are rebuilding from scratch, the MOQ guide covers choosing a scope, minimums versus multipliers, and how to test that a rule actually holds. If your rules were only ever for B2B buyers, check whether Shopify's native catalog quantity rules now cover you — they may, and a native feature beats an app where it fits.
