Test a page or flow
How to test WooCommerce checkout step by step
You changed a shipping rule or the theme, and the store still looks fine in your own browser. Mimiq walks a guest from the cart to the payment step and shows where the order stalls.
How do I test a WooCommerce checkout?
Place a test order as a guest, starting from a product page and stopping at the payment step, using an address in a country you ship to and one you do not. Check that the shipping options, tax and total on the last step match your settings for each country. A simulated test adds visitors who do this from their own browsers, with no saved address or login, and report the step where each one stalled.
What this looks like in a report
“I typed my address and the box just sits there with nothing under it. Either you do not deliver here or my order is already lost, and I do not want to find out with my card.”
The fix. In the WooCommerce shipping settings, add a zone for Portugal with a flat rate, or make sure the rest of the world zone has one. Then run the same guest path again and check that a delivery option appears before the payment step.
An illustration. Run a test to see your own.See a real sample report
Guest checkout stalls on the shipping step, not the payment step
WooCommerce works out shipping and totals from the address the buyer types, using shipping zones. A zone matches a country, and sometimes a state or a postcode range. If no zone matches and there is no rest of the world zone, the shipping step has no delivery option to offer. Your own test order usually uses an address your store already ships to, so it goes through while a guest typing a new country gets stuck. The step shows no options, so the buyer assumes the store cannot deliver to them and leaves.
- Enter a country that has no shipping zone and see whether the step offers any delivery option.
- Change the postcode after choosing a method and check that the total updates with it.
- Fill the form on a phone and check that no required field is hidden under a collapsed section.
- Add one product with a free shipping minimum, then test a cart just below and just above it.
What a guest passes between the cart and payment
A guest starts on a product page, adds the item and opens the cart. From the cart they go to checkout, where the form asks for contact details, a billing address and, if the order ships, a delivery address. Each change of country or postcode asks the server for new shipping options and totals, so the page changes under the buyer's hands. The payment step comes last, after the shipping and total steps. Many guest failures sit in that middle stretch, which the owner walks through quickly because they already know what it should show.
Shipping zones decide what the buyer is offered
WooCommerce checks each shipping zone in order and uses the first one that matches the address. A zone can match a whole country, a state, or a list of postcodes, and a rest of the world zone catches everything else. A free shipping rule with a minimum order amount only appears once the cart passes that amount, so a small test order sees a shorter list than a large one. If you test with a cart you built to look good, you may never see the option a small buyer gets. Run one guest for each country you sell to, with a cart above and below any minimum.
The payment step, without a real card
The test ends where the payment fields begin. A simulated visitor fills in the contact details, the billing address and the shipping choice, then stops before typing a card number. That covers the steps that set the order total, which is where a guest's order can break before payment. It does not show whether your payment gateway accepts the order. Check that path yourself, with your gateway's test mode and the test card numbers it publishes. If you place a test order on your own store, cancel it afterwards so it does not sit in your sales reports.
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 shipping zone edit can break a country that worked last week
Every change to shipping zones, tax, a free shipping minimum or a checkout plugin can empty the shipping step for one country while the others keep working. Rerun the same guest visitors after each fix, one for each country and one with a cart on each side of the minimum, and compare the step each one reached. The comparison shows whether the fix reached the buyer or only the setting you changed.
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
Do I need a real card to test a WooCommerce checkout?
No. Stop at the payment step and do not enter a real card, and do not ask a visitor to. Many payment plugins have a test mode with published test card numbers, and you run that check yourself. A simulated visitor covers the form, shipping and totals, which is most of what breaks for a guest.
Should I test as a logged-in customer too?
Yes, once the guest path works. A logged-in customer has a saved address and a saved shipping choice, so the form is already full when they arrive. A guest types every field, which is where a missing zone or a hidden required field shows up. Run both paths once the guest path passes, and keep the guest run as the one you repeat.
Why does my checkout work for me but not for my customers?
Your browser remembers your address, your cart and your login, and you already know which fields matter. A new visitor has none of that, often on a phone and sometimes from another country. Test as a guest in a private window, with an address from a place your customers live. Mimiq visitors arrive with no saved state, which is the case you cannot reproduce from your own account.
Can a test show how many buyers will finish checkout?
No. A simulated test does not predict how many real buyers will finish. It shows which step each visitor stopped at and what they said there. The finish rate comes from your own order data, or from a live experiment once real shoppers arrive.
How often should I test checkout again?
After every change that touches the cart, shipping, tax, payment or the theme, and after every plugin update that touches checkout. A shipping zone edit can break a country that worked yesterday. Rerun the same guest path each time, so the step each visitor reached can be compared with the last run.
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.