Storefront error library · Reviewed November 15, 2026
Storefront errors,
explained for Shopify.
The errors Shopify teams find in the browser console, explained: what each one means, why it happens on a Shopify store, whether it costs sales and how to fix it.
Before you start
Most console errors on a Shopify store never cost an order: blocked pixels, dropped connections, browser extensions. A few break Add to cart for a whole browser. Each page below says which kind an error usually is, which shopper steps it can break, and how to reproduce and fix it.
JavaScript
Code in your theme or an app threw. These are the errors most likely to break a button.
Requests and cart
A request failed, was refused or never left the browser. Some cost orders; most are noise.
TypeError: Failed to fetchA request got no response at all: network, CORS, a blocker or a page change.Causes, sales impact and fix →cart/add.js 422 (Unprocessable Entity)Shopify’s Cart API refused an add: stock or an unknown variant.Causes, sales impact and fix →ERR_BLOCKED_BY_CLIENTA browser extension or built-in blocker cancelled the request.Causes, sales impact and fix →CORS errorA request to another host that does not allow your store’s domain.Causes, sales impact and fix →
Domain and DNS
The store, or a script on it, could not be reached at all.
Side by side
Which errors cost orders, and who fixes them.
| Error | Does it cost sales? | Who can fix it | In Dozenfold |
|---|---|---|---|
| Script error. | Sometimes: when an app on the product or cart page throws | The owner of the script that threw, usually an app or tag vendor | Catches the real stack for errors in callbacks; filters the bare message as noise |
| Cannot read properties of undefined (or null) | Often, when thrown in the product form, variant picker or cart | Your theme developer, or the app whose file is in the stack | Opens an issue with the stack mapped to theme source and the orders lost per day |
| TypeError: Failed to fetch | Only when the failed request is a cart write or a feature shoppers need | Often nobody: the shopper’s network. Otherwise the owner of the endpoint | Kept out of the issue list; each failed request stays in its session timeline |
| cart/add.js 422 (Unprocessable Entity) | When the theme shows nothing after the refusal | Your theme developer for the message; merchandising for stock and variants | Opens an issue for 422s your theme sent, with the sessions and whether they still ordered |
| ERR_BLOCKED_BY_CLIENT | Rarely; yes when a pixel call sits in front of Add to cart | Nobody, unless your own code depends on the blocked script | Ignores known tracker requests; a theme error caused by a missing pixel opens an issue |
| CORS error | When the blocked request feeds stock, prices or cart features | The owner of the server being called | Seen as a failed request without a status; kept out of the issue list |
| ERR_TOO_MANY_REDIRECTS | Always, for every shopper on the affected hostname | Whoever manages the domain: DNS, Cloudflare or the redirect app | Not visible to any browser script; use an external uptime check |
| ERR_NAME_NOT_RESOLVED | Always for your own domain; rarely for a leftover script | Whoever manages DNS, or the theme developer for dead script tags | Your own domain: not visible. Dead script hosts: in session timelines and page performance |
Stop reading the console
See which errors cost orders.
Dozenfold groups your store’s errors into issues, keeps blocker and network noise out of the list, and ranks each issue by the orders it is estimated to cost, with the theme line, the browsers and the sessions behind it.
Install on Shopify14-day trial · From $49 a month · Billed through Shopify