Install

Article · 7 min read

Add to Cart stopped working on Shopify: why every page still says 200 OK, and how to catch it in minutes

14 October 2026 · by njX

A store can be “up” for a week and sell nothing. The home page loads, the product page loads, the uptime monitor is green, and the button under the price does nothing. Here is how that happens, what breaks most often, how to check it by hand, and how to be told within minutes instead of noticing an empty day.

Why the monitors stay green

An uptime monitor asks one question: did the server answer? It requests a URL, gets a 200 OK and moves on. Shopify almost always answers. Its servers are not the thing that breaks.

What breaks is what the customer has to do on the page: find the button, add the product, see it in the cart, reach the checkout. None of that is visible in a status code. A product page without an Add to Cart form is a perfectly healthy 200 OK. A cart that refuses the product is a 422 on a JSON endpoint the monitor never calls. A checkout with no shipping rate for the customer’s country is a page that loads fine and sells nothing.

So the question is not “is the store up?” but “can a customer buy right now?”. That is a different check, and almost nobody runs it.

The five changes that break the cart most often

From what we see across stores, the cart is almost never broken by Shopify. It is broken by a change somebody made on purpose an hour earlier.

  1. A theme published or edited. A new version of the theme, a section removed in the editor, a “buy buttons” block deleted by accident while cleaning up the product template. The page looks right, the form is gone. This is the most common one, and the theme editor does not warn you.
  2. An app that rewrites the product form. Bundles, pre-orders, subscriptions, custom fields: many apps replace the Add to Cart button with their own. When two of them fight, or one is uninstalled without cleaning its script, the button stays on the page and does nothing when clicked.
  3. A third-party script that throws. A pixel, a chat widget, a review badge with a bad update. One JavaScript error early in the page can stop the theme’s own cart code from running. Every page still answers 200 OK.
  4. A shipping profile change. A zone deleted, a rate set to the wrong product group, a market switched off. The product goes into the cart, the checkout opens, and the customer sees “no shipping method available”. You see a checkout started and no order.
  5. The storefront password. Switched on for a quick edit and forgotten. Every customer lands on the password page. The monitor sees a redirect and a 200 OK.

Notice what these have in common: each one is a change you or your team made, and each one happened at a time you could look up, if you had a list of changes.

How to check it by hand

Open a private browser window, so your admin session and cookies do not help the page along. Then walk the store the way a customer does:

  1. Open the home page. Does it load as your storefront, with products on it?
  2. Open a best-selling product. Is there an Add to Cart button, and is the variant in stock?
  3. Click the button. Does the cart show the product with the right price?
  4. Open the checkout. Does it reach the shipping step, and is there a shipping rate for your main country?

Four steps, about a minute. If you do this every morning you will catch most breakages within a day. Most people do it once, after the first empty week.

Two refinements make the check honest. Use a product that customers actually buy, not the first one in the catalogue. And check more than one page: a product page can work while the collections page or the search page returns an error, and customers land on all of them.

Finding the cause once you know it is broken

The fix is usually to undo the change. The hard part is knowing which change. The Shopify admin keeps pieces of this in different places: theme versions under Online Store, app installs under Apps, shipping under Settings, and nothing at all for scripts that an app injected into the page.

A good habit: before touching the theme, shipping or apps, note the time. When something breaks, the last two or three changes before it are the suspects, in order. A theme published at 14:02 and a cart that died at 14:12 is not a coincidence.

How to be told within minutes

The by-hand check works, but only when you remember to run it, and it tells you nothing about what changed. The automated version is a robot customer that walks the same four steps every few minutes, keeps a timeline of what changed in the store, and messages you when a step fails twice in a row, with the change that happened just before.

That is what njX Store Monitoring & Uptime does. Every few minutes it opens your home page, a best-selling product, adds it to a cart that lives only in its own request, and opens the checkout page. It never places an order and never writes to your store. When a step fails twice in a row, the alert in Telegram, Slack, Discord or e-mail names the step and what changed in the 48 hours before it: a theme published, a new script on the storefront, a shipping profile edited, the password switched on. Each cause comes with its time and a link to where it is undone.

It also loads every page a customer can land on, checks your products one by one for a missing page, a price of 0 or a cart that refuses them, and tells you when orders stop against your usual hour. The Free plan checks every hour; Pro every 15 minutes; Business every 5, with a real browser pressing the button as well.