Skip to main content
Technical

Shopify Cart or Checkout Validation Error Not Showing? 9 Causes and Fixes

Jahangir AlamNovember 21, 2026Facts checked November 21, 20269 min read

When a Shopify validation rule shows no message, one of four things is usually happening: the validation is switched off, the Function failed and checkout carried on without it, the rule only runs at checkout, or the theme received the error and didn't show it. Test the product page, the cart and checkout one at a time to find which.

This guide covers checkout validation built with Shopify Functions, which is how order limit, minimum order and store hours apps (OrderRules included) block orders. If you're new to it, start with how Shopify checkout validation works.

Where Shopify shows validation errors

Where the message appears depends on where the customer is.

Where the customer isWhat happensWho shows the message
CheckoutThe error blocks the step. An error on the whole cart shows on the current checkout page; an error on a field shows by that field.Shopify
Product page or cart (adding or changing items)The cart request fails and returns the error.Your theme β€” if it reads the error
Headless storefrontErrors appear on the Storefront API cart.Your front end
Express checkout (Shop Pay, Apple Pay, Google Pay, PayPal, Buy it now)Validation runs as in checkout.Shopify

The middle row is where messages go missing. Shopify sends the error back; whether the shopper sees it is up to the theme's JavaScript.

The 9 causes, by symptom

SymptomLikely causeFix
No rule ever fires, anywhere1. Validation not activeTurn it on in Checkout rules
Works on small carts, not big ones2. Function crashed or ran out of instructionsReport it to the app developer with the time and cart size
Nothing on the cart page, blocked at checkout3. Rule runs at checkout onlyExpected; tell customers up front
"Sold out" or a generic error instead of your message4. Theme hides or replaces the cart errorTest in Dawn; fix the theme's error handling
Works from the cart, not from Buy it now5. Express checkout skipped cart attributesStore the choice per line item, or require it at checkout
First order after the limit still went through6. Counts hadn't updated yetLeave headroom; counts refresh after each order
A different message shows7. Another rule or app failed firstCheck the order rules are checked in
Message shows ' or other code8. Message escaped twiceReport it to the app developer
Order arrived with no check at all9. Order came from a channel that skips validationPOS, renewals, edits and API orders aren't validated

1. The validation isn't active

Installing an app with a validation Function doesn't always switch it on. Go to Settings β†’ Checkout β†’ Checkout rules and check that the app's rule is listed and turned on. If it's off, no rule from that app runs on any surface. In OrderRules, the rules not applying checklist walks through this first.

2. The Function crashed, timed out or ran out of instructions

A validation error always blocks checkout. A failed run doesn't. If the Function throws an error or exceeds Shopify's limits, checkout continues without that validation by default, and the customer sees nothing. The app can change this with a blockOnFailure setting when it creates the validation.

The limit that bites in practice is 11 million instructions per run for carts up to 200 lines. Cost grows with every cart line, so a rule that works on a 3-item cart can fail on a 40-item one. If your limit holds on small carts and fails on large ones, this is the likely cause. Merchants can't see Function run logs; the app developer can, in their Partner Dashboard. Send them the time of the order and the number of cart lines. The full list of limits is in Function resource limits.

3. The rule only runs at checkout

Shopify tells the Function where the buyer is: changing the cart, or in checkout. Many apps check some rules only in checkout, so that adding to cart never fails on, say, a delivery date the customer hasn't chosen yet. Those rules show nothing on the cart page and block at checkout instead.

In OrderRules, store closed, order caps, product and variant caps, minimum and step quantities, and tag and collection limits are checked when items are added. Per-customer limits and delivery and pickup checks run at checkout only, because the customer may not have logged in or picked a date yet. If you want customers to know before checkout, show the rule on the page with a storefront message.

4. The theme hides or replaces the error

When a rule rejects an add-to-cart or a quantity change, the theme gets back a failed request with the message in it. What happens next is theme code:

  • Dawn (16.x) shows the message under the add-to-cart button. It can also switch the button to "Sold out", so the product looks unavailable when it isn't.
  • Quick-add buttons on collection pages often show only "Sold out" or a short generic error.
  • Custom cart drawers may ignore the error entirely and simply not add the item.

To confirm it's the theme: open the browser's developer tools, go to the Network tab, and add the product again. A failed /cart/add.js or /cart/change.js request whose response contains your message means the rule worked and the theme didn't show it. Try the same action in an unedited Dawn preview. If Dawn shows the message, ask your theme developer to show the error from the failed cart request.

5. Express checkout skipped a cart attribute

Shopify's validation reference notes that accelerated checkout from a product page skips cart attributes. If a rule depends on something the customer chose on the cart page and saved as a cart attribute, such as a delivery date or a gift note, a Buy it now or Shop Pay button on the product page never sends it. Depending on how the app is built, the rule either can't see the choice or blocks the order with a "choose a date" message.

The fix is in the app: save the choice on each line item, which product-page buttons do carry, or require the choice in checkout. OrderRules stores a delivery date chosen on the product page on the line item, so Buy it now orders keep it. Test this button on your store before a busy day.

6. The counts hadn't caught up

A Function can't call the app's server during checkout. It reads counts the app saved earlier, and the app updates them after each order. So the first checkout after a limit is reached can pass, and two checkouts at the same moment for the last unit can both pass. No message is missing here; the rule saw the old count. Leave a little headroom on a cap you can't exceed, and see per-checkout vs per-customer limits for how customer limits count.

7. A different rule or app answered first

Shopify runs every active validation Function, up to 25 per store, and any one returning an error blocks checkout. Inside one app, rules are often checked in a fixed order. In OrderRules, a closed store shows only the closed message even if the cart is also under the minimum. The customer fixes one thing, then sees the next. See which message the customer sees for the full order.

If the message isn't from your app at all, another app's validation is blocking. Check the list under Settings β†’ Checkout β†’ Checkout rules.

8. The message shows code

An apostrophe that shows as ', or an ampersand as &, means the message was HTML-escaped twice somewhere between the app and the page. It's a display bug in the app or theme, not in your settings. Report the exact page and message to the app developer.

9. The order never went through checkout validation

Some orders don't run cart and checkout validation at all, so there's no message to show:

  • Shopify POS sales
  • Subscription renewal orders (the first subscription checkout is validated)
  • Order edits after purchase
  • Orders made by other apps or integrations through the Create Order API
  • Pre-order and try-before-you-buy purchases

Draft orders paid through the invoice checkout are validated. In OrderRules, orders from the channels above aren't blocked, but they still count toward your limits. The full table is on compatibility and limitations.

Test every surface in 10 minutes

Use a development store or a test product, and set a rule you can break on purpose, such as a maximum of 2.

  1. Product page: add 3. Note what the button and message do.
  2. Collection quick-add: add the product from a collection page.
  3. Cart page and drawer: change the quantity to 3.
  4. Checkout: go to checkout with 3 in the cart. You should see the message and be unable to pay.
  5. Buy it now and Shop Pay: buy 3 from the product page with each button.
  6. Logged in and logged out: repeat checkout both ways if you use per-customer limits.
  7. A big cart: add 40 or more lines if your store sells many small items.

Keep the Network tab open while you test. Any step that blocks without a message on screen is a theme problem (cause 4). Any step that goes through when it shouldn't is causes 1, 2, 5 or 9.

Sources

Frequently asked questions

The most common causes are: the validation isn't turned on under Settings β†’ Checkout β†’ Checkout rules; the Function crashed or ran out of instructions, so checkout continued without it; the rule only runs at checkout, so nothing shows on the cart page; or the theme catches the cart error and shows a generic message or "Sold out" instead. Test the product page, the cart and checkout separately to see which one it is.

In checkout, an error aimed at the whole cart shows on the current checkout step, and an error aimed at a field shows next to that field. On the online store, an error returned while items are added or changed comes back to the theme as a failed cart request. The theme decides whether and where to show it. Headless storefronts read the errors from the Storefront API cart.

If a validation rule rejects an add-to-cart request, some themes treat any failed add as sold out. Dawn, for example, shows the error message under the button and can also switch the button to "Sold out". The product isn't out of stock; the rule blocked that quantity or that cart. Check which rule applies to the product.

Not by default. If a Function run fails, for example by timing out or running out of instructions on a large cart, Shopify lets checkout continue without that validation unless the app created it with blockOnFailure turned on. The customer sees no message and the order goes through.

Validation runs on Shop Pay, Apple Pay, Google Pay, PayPal express and Buy it now. One catch: express checkout from a product page skips cart attributes, so a rule that depends on something the customer chose on the cart page, such as a delivery date stored as a cart attribute, can't see it there.

POS sales, subscription renewal orders, order edits, orders created through the API, and pre-order or try-before-you-buy purchases don't run cart and checkout validation, so they can't show its message. Draft orders paid through the invoice checkout do run it.

Comparing apps?

See how OrderRules stacks up against every other Shopify app in this category.

Ready to take control of your orders?

Try OrderRules Free