By platform

Squarespace checkout not working: where it stops

A shopper fills the cart, enters an address and gets stuck on a step with no shipping option, a grey button, or an error that names nothing. Mimiq walks simulated shoppers through the store and reports the step where each one stopped, with a screenshot.

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

Why is my Squarespace checkout not working?

A Squarespace checkout usually stops at the first step that has no way forward for that shopper, and the address they typed is often the clue. Compare the same cart with a home address and an address abroad, and note which step the second one stops at. A simulated test follows one cart through each step and reports the step where it stopped.

What this looks like in a report

Who
Rhea, in Auckland, buying a candle set as a gift for a friend in Ohio
How they arrived
Opened a shop link a friend sent her in a chat message
Where they stopped
Shipping step, after entering the address in Ohio

“The page says choose a shipping method, but the box under it is empty. Continue is grey. I tried my own address back home and a method appeared, so I do not know if this shop sends to Ohio.”

The fix. In the store's shipping settings, check that the United States is among the places you ship to and has a rate, then run the checkout again with an address in Ohio. If it still stops, compare the rate for the United States with the rate for your own country.

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

A foreign address can reach a step your own address never sees

You tested the store with your own address, so the checkout you saw ran the path for your country. A shopper in another country enters an address your shipping settings may not cover. The shipping step then offers no method, and the Continue button stays grey. The page may not say which field caused it. Each screen passes the shopper on only when the screen before has what it needs, so one missing country can end every order from that country.

  • Add one item, then enter your own address. Does the shipping step offer a method?
  • Repeat with an address in another country. Does shipping still offer a method?
  • Apply a discount code. Does the total change, and does the next step still load?
  • Reach the payment step. Does the total match the cart and the shipping line?
  • Try a second item from the same shop. Does it stop at the same step?

Every screen after the cart can end the order

Once a shopper presses the checkout button, the store takes over the order. They usually enter a contact email, then a delivery address, then pick a shipping method, then reach payment. Each screen checks what it needs before it lets the shopper through, and a screen that finds nothing usable does not always say so in plain words. It keeps the next button inactive, or shows a line of red text that points at no field in particular. The shopper cannot tell which screen to blame, so they assume the store is broken and close the tab.

Why your own test order passed

Your own test probably passed because your saved address, your country and your tax setting were already in place. Nothing on your path asked the store for a rate it did not have. A shopper who types a new address brings in every rule you never had to think about, and that is why a checkout can pass your test and fail the first order from abroad. The fix is not to test harder with your own details. It is to run the same cart with details you did not choose.

Shipping and tax decide where a checkout stops

Shipping can stop a foreign order, because it depends on the address entered and on the places and rates you set up. A country left off the list gives the shopper no method at all, and a method with no rate for that address leaves them without a price. Tax works in the other direction: a total that changes between the cart and the payment step makes a shopper think the order is broken. Check the total on every screen, not only the first and the last.

Discount codes come next. A code can work for your address and fail for a shopper whose cart is below its minimum, or whose items the code does not cover. The page may then show a message about the code, and the total may stay where it was. Run the same cart with and without the code, so you can tell a code problem from a shipping problem.

Reading the step, the address and the total

Write down three things for every stop: the step name, the address you typed, and the total on screen. A stop at shipping with an address abroad points at shipping settings. A stop at shipping with your own address points at something you changed recently. A stop at payment with a total that differs from the cart points first at tax or a discount, not at the payment method. A simulated test records the same three things for each visitor, so its stops are easy to line up with your notes.

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 country or rate added later can close checkout for it

Each new shipping rate, country or discount rule can close checkout for one group of shoppers without changing anything on your own screen. Rerun the same simulated shoppers after each change, from an address abroad and with each code you publish, and see who got further. Include one address you did not plan for, since that is where a gap usually sits.

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

Your own test uses your saved address, your country and your settings, and those pass by default. A real shopper enters an address you may not have set up, applies a code you did not try, or buys an item you have not checked. Run one cart with an address in another country before you decide the checkout works.

Can a simulated visitor pay for the order?

No. A checkout test goes up to the payment step and stops there, because a simulated visitor cannot pay with a real card. It can show you the total and the payment options on that screen, but not whether a card is accepted.

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 finish the order, so take that number from your store's analytics or a live experiment.

Does a stop at shipping always mean a shipping setting?

Usually, but not always. A shipping stop can also come from a discount code, a product that ships on its own rule, or an address the browser filled in wrongly. Run the cart again without the code and with a typed address before you change the shipping settings.

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 .