By platform

Shopify checkout not working: settings first

A shopper adds an item, reaches checkout, then hits a shipping gap, a code that will not apply or a payment screen that offers too little. Mimiq runs simulated shoppers through the same checkout and shows the step where each one stopped.

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

Why is my Shopify checkout not working?

Shopify draws the checkout pages itself, so a checkout failure usually traces back to a store setting rather than to your theme's code. The usual suspects are a market or shipping rate that does not cover the shopper's address, a discount rule the cart does not meet, a payment provider not active for that country, or a store password that keeps shoppers out before checkout. Run the same cart with one input changed each time to see which one moves the result. A simulated test does that with several shoppers and shows the step where each one stopped.

What this looks like in a report

Who
Ivan, buying wool socks for his brother with a code from a newsletter
How they arrived
Clicked a product link from a friend's message on his phone
Where they stopped
Discount code box, after the cart total

“The newsletter code says it works, but the total does not drop, and a red line says it cannot be used here. I cannot tell if I chose the wrong item, so I start over.”

The fix. Check the code's minimum and the products it covers, then run the same cart with and without it. If it fails only with the code, fix the discount rule; if it fails without the code, check the shipping rate for the country on the address.

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

Your theme code is not the checkout a shopper sees

The theme you edit controls the product page, the cart and the navigation. The checkout a shopper reaches after that is hosted separately, and it applies rules from the admin: which countries the store sells to, what each shipping rate costs, which payment providers are active, and which discounts apply. When you change a theme file, the checkout does not move. A shopper who fails there has hit a rule in the admin, so the fix lives in the admin too. Find the step first, then the rule that governs it.

  • Check out with an address in your home country. Does the cart reach payment?
  • Repeat with an address in a country you ship to, then one you do not. Which one stops?
  • Apply each discount code on its own. Does the total change, or does a message appear?
  • Open checkout on a phone in a private window. Does it stop at a different step?
  • Confirm the product is offered in the market that matches the shopper's address.

What a shopper hits, in the order they hit it

A shopper arrives at checkout with a cart that already holds an item, a country and, often, a payment method they like. The checkout checks the market and country first, then offers shipping rates for the address, applies any discount, and shows the payment providers active for that market. A stop at the first step usually means a country or market problem. A stop at a later step can mean a rate or a payment option that depends on the choices made before it.

Why the stop does not name the rule

The stop itself does not say which rule fired. A shipping gap can look like an empty list, and a discount that cannot apply can show a red line. A payment provider that is not active for the market may show fewer options, with no note explaining the missing ones. That is why one cart tested with changed inputs tells you more than a single screen read once from the admin.

The settings that govern each checkout step

Markets decide which countries the store is open to, and a product not offered in the shopper's market can stop them before checkout. Shipping rates decide whether a method appears for their address. Discount rules decide whether a code applies to this cart and whether it meets the minimum. Payment providers decide which buttons appear for their country, and a provider not yet active there shows fewer options or none. A store password page is a separate gate, and a shopper who hits it never reaches the cart.

Check each one from the admin side, then from the shopper's side. Open the shipping and payment settings and confirm the address's country is covered. Then run the same checkout in a private window to see what the shopper sees. A setting that looks right in the admin can still fail for the shopper when the product is missing from that market.

One cart, one change at a time

Run a single cart through checkout, and change only one input between runs: the country, the discount code, the device, or whether you are signed in. Write down the step where it stops each time. If changing the country moves the stop, the rule is in shipping or markets. If removing the code clears it, the rule is in discounts. If a phone stops where a laptop does not, look at the device-specific parts first, such as a wallet button that only some devices show.

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 market or shipping change can close checkout for one country

Adding a country, changing a rate or switching payment providers can close checkout for one group of shoppers without anything changing on your own screen. Rerun the same simulated visitors after each change, with an address from a country you sell to, and see who got further. If the store is behind a password while you build, the visitors need that password, which needs paid credits.

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 Shopify checkout work for me but not for shoppers?

You test with your own address, your own country and a cart you know, and those rules pass by default. A shopper may bring an address in a country you have not set up, a code you have not tried, or a device with a different payment button. Run the cart from another country and on a phone before you decide checkout works.

Can a simulated visitor pay at the end of checkout?

No. The test stops at the payment screen, because a simulated visitor has no real card to enter. It reports which payment options appear, and it cannot say whether a real card would go through.

Will a checkout test show how many shoppers finish?

No. It shows the step where each simulated visitor stopped and what the screen showed them. It does not predict how many real shoppers would finish, so take that rate from your store reports or a live experiment.

Does a discount code stop checkout, or only change the total?

It can do both. A code with a minimum or a product limit may refuse to apply and show a message, while a code that does apply can leave a shipping method out. Run the cart with and without the code before you change anything else.

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 .