By platform

WooCommerce checkout not working: where it stops

The cart fills and the shopper reaches checkout, then the order stalls. Simulated visitors walk the same steps and show the field, shipping choice or payment box where each one gave up.

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

Why is my WooCommerce checkout not working for shoppers?

A WooCommerce checkout stalls at one of a few places: a required field that cannot be completed, a shipping choice that never appears for the shopper's address, or a payment option that does not load at the last step. Each place gives a different symptom, so note where the shopper stops before you change any settings. Shipping zones that do not cover the shopper's country and payment methods that are switched off for it are the usual gaps, and a cached checkout page can show stale content. A simulated test walks the cart into checkout with a delivery address and records the step where it stalls, with a screenshot.

What this looks like in a report

Who
Callum, buying a leather wallet as a birthday present for his brother
How they arrived
Tapped a product link from a social post on his phone
Where they stopped
Shipping section, after entering his delivery address

“The shipping box is empty, so no total appears. Either they do not deliver here or the store is broken. I cannot tell which, so I am buying the wallet elsewhere.”

The fix. Add a shipping zone that covers the shopper's country, with at least one shipping method in it, and check that a payment method is enabled for that country. Then open checkout in a private window, enter a delivery address in that country, and confirm the shipping choices and the payment box both appear before the place-order button.

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

The shopper reaches checkout, then one step refuses to move on

Checkout is a short chain: the contact and address fields, a shipping choice, a payment box and the place-order button. The shopper only sees the step in front of them. When no shipping method covers their address, the shipping section is empty and the total never settles. When the payment box loads blank, the button stays grey and the shopper cannot tell whether the problem is the card or the store. Your own test order can pass every step, because your address and your settings are the ones that work. The gap sits in the address the shopper types, not in the cart.

  • Enter a delivery address in a country you ship to, then one you do not. Compare the shipping choices.
  • Check that the payment box shows at least one method before you press place order.
  • Try checkout as a guest with no account. Does the form still ask for a password?
  • Confirm the items in the cart are in stock and can ship to the same address.
  • Open the console on the checkout page and look for a red error when the shipping or payment box loads.

The address is the input your own test skips

Most owners test checkout with their own address, their own saved details and a product they already know works. That is the easy path through the store. A shopper arrives with a different country, a different postal format, a coupon, or a cart whose items are out of stock for that destination. Each of those can change what the store offers at the shipping step, and the owner's test never reaches that branch.

Guest checkout adds another difference. If the store asks for an account before checkout, a shopper who only wants one item may leave at that form rather than create one. Check the store's account setting, then run one guest visit in a private window, so the test begins where a stranger begins, at the same form and with the same choice of whether to sign up.

Empty shipping, empty payment, or a silent button

An empty shipping section means no zone or method covers the address, so the total never settles. An empty payment section means no enabled method is available for the shopper's country or cart, which is a settings gap rather than a shipping one. A button that stays grey with both sections filled usually points at a required field that is still invalid, often one the shopper cannot see on a phone. Each symptom has a different fix, so reading the empty section tells you which setting to open first.

What a simulated shopper reaches

A simulated shopper walks the cart into checkout with a delivery address, reads the shipping choices and the payment box, and records the step where it stopped. It stops at the payment step. It does not enter a real card or place an order, so the final step still needs a test order from you. The walk tells you whether a shopper can reach payment at all, which is the question the owner's own test cannot answer for a different address.

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 shipping rule added for one country can empty the next one

Shipping zones are edited by hand, so a rule added for one country can leave a neighboring country with no shipping choice. After each change, run the same simulated shoppers with a delivery address in every country you sell to, and compare the step where each one stopped. Protected previews, such as a staging store behind a site password, need that password in the run, which comes with paid credits. A saved run shows which country lost its option.

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

Your address, your saved details and your account are the easy case. A shopper's address, a coupon or a stock level for their address can change the shipping choices and the payment box. Test with a delivery address you do not own, in a private window, so the test matches a stranger's path.

Can a simulated shopper finish the payment?

No. It walks checkout up to the payment step and records what the payment box showed. It cannot pay with a real card, so it cannot tell you whether a charge goes through. Use the payment provider's test mode and its published test card numbers for that last step.

Will the walk show an order confirmation?

No. The walk stops before an order is placed, so there is no confirmation to read. Once the walk reaches payment, place one test order yourself and check the confirmation at the address you typed.

What if shipping shows but the payment box is empty?

That points at payment setup rather than shipping. Check that a payment provider is connected and switched on for the country the shopper chose. The walk records an empty payment box as the step where it stopped, which tells you where to look first.

Does a clean walk mean the store will sell?

No. A clean walk shows that a shopper can reach payment from the address you tested. It does not predict how many shoppers will pay, and it does not replace the first real orders, which show what your shoppers do at the last step.

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 .