By platform

Shopify cart not working: why items vanish

A shopper adds an item, sees the count go up, then opens the cart and finds it empty or with a different total. Mimiq adds items as a simulated shopper on your live store and checks the count, the cart page and each address the store answers to.

5 visitors try to .
First test free with an accountRun it from your coding agent

Why does my Shopify cart lose items for shoppers?

A Shopify cart usually looks empty because the shopper is on a different address of the store from the one where they added the item. Browsers save cookies per address, so each version of the store's address can hold its own cart. The count in the header and the cart page can also show different copies of the cart, so the two disagree. A simulated test adds an item, then checks the count, the cart page and each address the store answers to.

What this looks like in a report

Who
Kaveh, buying a cast iron skillet as a housewarming gift
How they arrived
Clicked a skillet ad that opened the plain store address on his phone
Where they stopped
Cart, after following the store's own link to the cart page

“I added the skillet and the header said one. The cart link opened the other web address, and the cart was empty with a total of zero. Did it get lost, or never get added?”

The fix. Redirect every address for the store to one main address, so a shopper keeps one cart, and check the header count matches the cart page after each add. Then add an item from each address the store answers to, open the cart from a link on the page, and confirm the item shows on both.

An illustration. Run a test to see your own.See a real sample report

The same store at two addresses keeps two carts

Many stores answer to more than one address: the plain domain, the version with www, or an older domain that still redirects. A browser saves cookies per address, and the cart is kept in one of them. A shopper who starts at the ad's address and then follows a link to the other address begins with an empty cart, while the item sits saved on the first one. Nothing on the screen says so. The shopper sees the header count drop to zero or the cart page open empty, and they assume the store lost the item.

  • Add an item from the plain address, then open the www address. Is the item still in the cart?
  • Note the count in the header, then open the cart page. Do the two show the same number?
  • Add an item, then open the cart in a private window. Does the item appear?
  • Follow an ad link and a menu link to the store. Do both addresses show the same cart?
  • Remove an item on the cart page, then check the header count. Does it update at once?

Each address keeps its own cart

A shopper rarely types the store's address themselves. They arrive from an ad, a search result, a social post or a bookmark, and each one can use a different version of the address. The first visit saves the cart in a cookie for that version. The next visit, to the other version, reads a different cookie and finds nothing there. If the store then sends the shopper across to its main address, the redirect carries the page but not the old cart, so the shopper starts over. The owner rarely sees this, because the owner's own bookmark always uses the same version of the address, and that version keeps one cart.

Three reads of the same cart, and where they disagree

A store can show the cart in several places: a count in the header, a cart drawer or page, and a total near the checkout button. Each one can be drawn from a separately loaded copy of the cart. The header count is the easiest to check. When the count rises after an add but the cart page is empty, the page read a different cart, which usually means a different address. When the count stays at zero but the page lists the item, the header read a stale copy. Note the address in the bar each time a number changed. An address that changed between the add and the cart page is the first thing to check.

Check each address before a shopper does

The check is to add an item from every address that serves the store, then open the cart from a link on the page, not from the browser's history. Run it on a phone as well as a laptop, since each browser keeps its own saved cart. A simulated test does the same. It arrives through the addresses you point it at, adds an item, and reads the count and the cart page at each one.

The report gives the step and a screenshot for each address, so you can see which one lost the item. Compare the screenshots from the add and from the cart page, since the address in the bar on each one is the clue. It does not say how many shoppers come in on each version, so use your analytics to decide which address to fix first.

Mimiq is independent and not affiliated with the platforms it names. Names belong to their owners.

What you get with Mimiq

  1. 01

    Run it by hand, or on every pull request

    Paste a link and a task in the app and watch the visitors work. Or run them on every preview deploy: the GitHub Action comments on the pull request, any other CI can call the MCP endpoint, and your coding agent can run it too.

  2. 02

    Bugs and usability problems in one report

    The browser records errors and failed or slow requests on the step they happened. The visitors say where the wording or the steps confused them, and where they left.

  3. 03

    Visitors that behave like your audience

    Each visitor is a different profile with a reason to be there, matched to who the page is for, described by you, or built from your own customers.

  4. 04

    A prompt to fix each problem

    Every problem comes with a fix to paste into Cursor, Claude Code, Lovable or any coding agent, and one prompt hands over the top problems at once. Then send the same visitors through again.

  5. 05

    Follow every visitor

    See each visitor's whole path, step by step with screenshots, and what it was thinking at every step. Ask any visitor a question.

The browser records relevant JavaScript errors and failed or slow app requests encountered during the run, attached to the step where they occurred. The visitors are simulated: they find problems, they do not predict how many real people will convert.

A new domain or redirect can split the cart again

A new domain, a changed www setting, a preview address or a redirect rule can start a second cart for everyone who arrives on the other address. After any domain or redirect change, add an item from each address that serves the store, and open the cart from a link on the page. Run the same check on each preview address your team shares, since a shopper may land there from a review link.

Starter

Try it on one launch

$9 once
120 credits, never expire

About 4 tests of 5 visitors

  • Visitors on your landing page, signup and checkout
  • Where they left and why, with a fix to copy for each problem
  • Run it in the app or on every pull request
  • Ask any visitor a question, included
  • Test accounts and protected previews
Buy 120 credits

Builder

Test every build

$19 a month
500 credits every month

About 20 tests of 5 visitors

  • Everything in Starter
  • Credits refill each month, and what is left rolls over once
  • Cancel anytime
Choose Builder

Pro

Test every release, as a team

$49 a month
1,500 credits every month

About 60 tests of 5 visitors

  • Everything in Starter
  • Credits refill each month, and what is left rolls over once
  • Cancel anytime
Choose Pro

Scale

Test at scale, every day

$149 a month
6,000 credits every month

About 240 tests of 5 visitors

  • Everything in Starter
  • Credits refill each month, and what is left rolls over once
  • Priority support
  • Cancel anytime
Choose Scale
$0for your first test, with a free account (Google sign-in, no card). It includes 50 credits, enough for 10 visitors. After that a visitor uses 5 credits, and packs start at $9 for 120 credits.
See a sample report

Questions

Why does the cart count go up but the cart page is empty?

The header count and the cart page can read the cart from different places, and the count may change before the page does. Note the address in the bar when each one changed. If the address changed between the add and the cart page, the two saw different carts. If it did not, reload the cart page in a private window and compare.

Do shoppers lose the cart when they close the browser?

A saved cart can last between visits, but only while the browser keeps its cookies. Private windows and privacy settings clear them. To check, add an item, close the private window, and open the store in a new one. A new private window starts with an empty cart, which is expected, so compare that with what a returning shopper sees in a normal window.

Will the test show how many shoppers will check out?

No. The test shows whether a simulated shopper's item stays in the cart across the addresses and pages it visits. It does not predict how many real shoppers would check out. Use your store analytics or a live experiment for those rates.

Can the test check a cart on a preview address?

Yes, if the preview has a public address. If it is protected, you can give the test its password on a run with paid credits. Give the test the preview address as its starting point, and the screenshot at each step shows whether the cart stayed the same.

Does the test check discount lines and shipping bars in the cart?

It reads what the cart shows, including a discount line or a shipping bar. The screenshot at each step shows the total, so you can see a change between steps. It does not judge whether a price or discount is right for your margins.

Keep reading

Send visitors and see what breaks first.

Your first test is free: sign in with Google and it starts right away. Last checked 2026-11-02.

5 visitors try to .