By platform
Checkout isn t available Shopify: find the item
A shopper sees a message that checkout is unavailable, while your own test cart goes through. Simulated shoppers start with a new cart and show whether it reaches checkout, and where it stops.
Why does my Shopify checkout say it is not available?
The likely cause is one item in the cart that the store no longer sells to this shopper: a product that was unpublished, a variant with no stock at the location the order ships from, or a product not offered in their country. A new cart built in a private window often passes, which is why your own test looks fine. A simulated test starts with a new cart, so it shows where checkout stops for an item that is still for sale, but it cannot rebuild a cart saved earlier.
What this looks like in a report
“Checkout says it is not available, and nothing says which item is the problem. My cart still shows the candles, so I wonder if the store is closed to me. I leave.”
The fix. Open the candle set's product page and check that it is published, in stock at the location the order uses, and offered in the shopper's market. Then have the shopper remove the candles and add them again, and check that checkout opens.
An illustration. Run a test to see your own.See a real sample report
The cart keeps a line item that the store no longer sells
A shopper's cart keeps the product and variant they picked when they added it. When checkout starts, the store has to match each line against what it sells today. If you unpublish a product, empty its stock in one location or take it out of a market after a shopper added it, their saved cart can still hold that line. The mismatch shows up at checkout, not on the product page, and the message may name checkout rather than the one item. Your own cart is new and clean, so it passes.
- Open the cart in a private window and add the item fresh. Does checkout open?
- Open the product page for each item in a saved cart. Is it published and still listed?
- Check the stock for the location the order would ship from. Is any quantity left?
- Check whether the item is offered in the country on the shopper's address.
- Write down the exact message the shopper sees and the step just before it.
Why a fresh cart passes and a returning one fails
Your test is almost always a new cart, built with a product you have just checked, in a browser with nothing saved. That cart is clean. A shopper who added an item last week carries an older line, and that line refers to a product that may have changed since. The store does not show that difference on the product page. It shows up at checkout, where every line has to match what is sold today, and one mismatch is enough to stop the whole cart.
Three changes that close checkout for one item
The first is publishing: an item taken off the sales channel can stay in a saved cart while it disappears from the store. The second is stock: an item sold out at the location the order would ship from can close checkout for a buyer who only picked that line. The third is market: an item left out of the shopper's country can stop checkout for one address, even though the rest of the cart is fine.
Check each cause by its own look. A removed product shows as a dead link or an empty product page. A stock cause shows as a product page with no quantity available for the shopper's location. A market cause shows as an item the shopper can add but cannot take into checkout for their country. Write down which one you find before you change anything.
The saved cart is the one a simulated visitor cannot rebuild
A simulated visitor starts a new cart each time, so it can show where checkout stops for an item that is still sold. It can reach a product, add it and report the step where checkout refuses it, with a screenshot. It cannot recreate a cart a shopper saved last month, because it has no history to bring back. For that case, build the cart yourself in your own browser, change the product in the admin, reload that cart, and open checkout the way the shopper would.
Mimiq is independent and not affiliated with the platforms it names. Names belong to their owners.
What you get with Mimiq
- 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.
- 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.
- 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.
- 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.
- 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 stock or market change can close checkout for a saved cart
Restocking, moving an item between markets or unpublishing a product changes what checkout accepts, while a cart saved before the change keeps its old line. After each change, run the same new visitors through a product and into checkout, and repeat the saved cart you prepared by hand. Compare where each one stopped, so the difference comes from the change and not from the visitor.
Starter
Try it on one launch
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
Builder
Test every build
About 20 tests of 5 visitors
- Everything in Starter
- Credits refill each month, and what is left rolls over once
- Cancel anytime
Pro
Test every release, as a team
About 60 tests of 5 visitors
- Everything in Starter
- Credits refill each month, and what is left rolls over once
- Cancel anytime
Scale
Test at scale, every day
About 240 tests of 5 visitors
- Everything in Starter
- Credits refill each month, and what is left rolls over once
- Priority support
- Cancel anytime
Questions
Will a fresh cart show me the broken item?
Only if the item is still sellable. A fresh cart holds whatever you add now, so it passes when the item is live and fails when it is not. If your fresh cart passes, check the items a shopper might have saved, one at a time, against the live product.
Can a simulated visitor finish the order?
No. The test goes up to the payment step, because a simulated visitor has no real card to enter. It can show whether checkout opens and what it shows at each step, but not whether an order would complete at payment.
Does this tell me how many shoppers hit the message?
No. It does not predict how many shoppers will see the message or how many will leave at checkout. Count the messages from your order and support records, and use a test only to find which item and step cause them.
Do I need to clear a shopper's cart to fix it?
You usually cannot clear a saved cart for someone else, so the fix is in the product. Make the item sellable again, or remove it from the store, then ask the shopper to add it again if they still want it. Check the item once more with a fresh cart before you tell them.
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.