Storefront error library · Requests and cart · Reviewed November 15, 2026
TypeError: Failed to fetch
on a Shopify store.
"Failed to fetch", "Load failed" and "NetworkError when attempting to fetch resource" all mean the request got no response. Why it happens on Shopify stores and when it costs sales.
The short answer
A request got no response at all: network, CORS, a blocker or a page change. Depends entirely on which request failed. A blocked analytics call costs nothing. A cart add or change that fails without a message means the product never reached the cart and the shopper may not notice until checkout. Separate the two before you spend time on it.
At a glance
TypeError: Failed to fetch in three lines.
| Who can fix it | Often nobody: the shopper’s network. Otherwise the owner of the endpoint |
|---|---|
| Does it cost sales? | Only when the failed request is a cart write or a feature shoppers need |
| What Dozenfold does with it | Kept out of the issue list; each failed request stays in its session timeline |
| Group | Requests and cart |
| Last reviewed |
What you see
The exact messages.
The same problem is worded differently by each browser and tool. Search your console and error tracker for all of them.
What it means
In plain English.
fetch() rejects with this error only when no HTTP response arrived. A 404 or a 500 is a response and does not throw. So the cause sits between the browser and the server: the connection, the browser’s security rules or something that cancelled the request.
The message never says which. Look at the failed request itself in the Network tab and at the line printed just before the error in the console.
Does it cost sales?
Which steps it can break.
When it happens on the path to purchase, look first at:
- Add to cart and cart quantity changes
- Predictive search and filters
- Back-in-stock and review widgets
Why it happens on Shopify
The usual causes.
The shopper’s connection dropped
Mobile shoppers move between networks. A request in flight when the signal goes fails this way. Usually not your bug.
The page changed mid-request
A shopper who clicks a link while a request is pending can produce it in some browsers.
CORS
A request to another host that does not allow your store’s domain fails with this message; the console prints the CORS reason separately.
A content blocker
Ad and privacy blockers cancel requests to tracking hosts and sometimes to scripts with tracking-like names.
An endpoint that is down or unreachable
An app backend or custom API with a bad certificate, a DNS problem or no server listening.
Real problem or noise?
Check this before anyone debugs.
Most stores log this error at some level. These signals tell you whether real shoppers are affected.
- RealThe same URL fails for many shoppers, across networks and devices.
- RealThe URL is /cart/add, /cart/change or your own API.
- NoiseThe URL is an analytics or ad host, or the failure follows the shopper leaving the page.
How to fix it
Reproduce, then fix.
- 01
Find the request
In DevTools → Network, reproduce and look for a red row with status (failed). The URL and the console line before the error tell you whether it was CORS, blocked or a network failure.
- 02
Test without extensions
Repeat in a private window with extensions disabled. If the error goes away, a blocker caused it.
- 03
Handle the failure in the theme
Catch the rejection, tell the shopper, and offer a retry for cart actions.
try { const res = await fetch('/cart/add.js', { method: 'POST', headers: { 'Content-Type': 'application/json' }, body: JSON.stringify({ items }) }); if (!res.ok) throw new Error((await res.json()).description); } catch (error) { showMessage('We could not add this to your cart. Please try again.'); } - 04
Fix the endpoint if it is yours
For your own API or app backend, check the certificate, DNS and CORS headers, and that it answers from the shopper’s region.
Find it automatically
Know which errors cost orders.
Most “Failed to fetch” errors are a shopper’s connection or a blocker, so Dozenfold keeps network failures out of the issue list, the same way it treats every network failure in disguise. Each failed request stays in the session timeline with its host and the stack of the code that made it.
When a cart add, change or update fails at the network and error-session replay is on, Dozenfold uploads the replay of that minute, so you can see what the shopper saw. Requests your theme makes to your own store that come back 4xx or 5xx do open an issue, ranked by estimated orders lost.
14-day trial · From $49 a month · Billed through Shopify
Questions
TypeError: Failed to fetch: FAQ.
Does "Failed to fetch" mean my server is down?
Not necessarily. It means no response reached the page. That can be your server, but more often it is the shopper’s network, a blocker or a CORS rule.
Why does Safari say "Load failed" instead?
It is Safari’s wording for the same rejected fetch. Firefox says “NetworkError when attempting to fetch resource.”
Why does a 404 not cause "Failed to fetch"?
A 404 is a response. fetch() resolves with response.ok set to false, and your code has to check it.
Should I retry failed requests?
Retry reads such as search once. For cart writes, show a message and let the shopper retry, so an add is never applied twice.
Written by the Dozenfold team, who build storefront error monitoring for Shopify. Reviewed November 15, 2026 against MDN: Using the Fetch API (checking that the fetch was successful) and Shopify: Cart API reference.