By platform

Squarespace test order: place one before launch

A test order that goes through can still hide a broken order: the wrong quantity, a total that moved, or a confirmation that never arrives. Mimiq sends simulated shoppers to the payment step and shows you what each one saw, while the order itself stays yours to place.

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

How do I place a test order in Squarespace before launch?

To place a test order in Squarespace before launch, use a browser that is signed out of your store, and order an item with a variant, using a shipping address that is not your own. Then compare the order in the store admin with the last screen you saw before paying: the item, the quantity, the total, and the shipping and tax lines should all match. A simulated visitor walks the same path from the product page to the payment step and reports what each screen showed.

What this looks like in a report

Who
Bram, a graphic designer ordering two tote bags for a conference
How they arrived
Found the shop through a newsletter link on his laptop
Where they stopped
Cart, with quantity two of the navy tote

“The cart shows two totes, but the total looks like one bag plus shipping. Then the shipping line says it is free, which I did not expect. I am not sure what I am paying for, so I start again.”

The fix. Set the quantity to two on the product page, then confirm the cart total, the shipping line and the admin order all show two totes at the same price. If the cart shows two but the total counts one, send the quantity fault to whoever maintains the store, with the exact product.

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

Your saved details can hide the order a stranger would place

When you place a test order yourself, the store already knows you. Your address is saved, and your browser is signed in, so the checkout skips the fields a stranger has to fill in. The order can still go through and look right in the admin, while the path a new buyer takes has a shipping gap or a different tax line. A test order only tells you something about the path a buyer takes if it starts from nothing.

  • Open a private window and stay signed out of the store until the order is placed.
  • Use an address you have never saved, in a country you do not normally ship to.
  • Pick a variant and a quantity above one, not the default item.
  • Match the cart total, shipping line and payment total with the order in the admin.

How it works

  1. 01

    Start signed out, in a private window

    Open the store in a private window and do not sign in. Leave out a saved address and an open owner account, since both make a test order easier than a real one.

  2. 02

    Use an address a stranger would type

    Enter an address in a country you do not usually ship to, with a postal code you have never saved. Write down what the shipping step offers, since a new address is the first thing that can change the options.

  3. 03

    Compare the order with the last screen

    Set a quantity above one on a product with a variant. Then match the item, variant, quantity, total, shipping and tax in the store admin against the last screen you saw before paying.

  4. 04

    Check the confirmation on a different inbox

    Send the order to an address on a different mail provider, and check the confirmation arrives with the same totals. If your payment provider offers a test mode you can use with the store, use it for this order so no real money moves.

What an owner's test order skips

A test order tells you the store can take an order. You place it signed in, with an address you have used before, and with a product whose price you already know. Each of those removes a step a real shopper meets. The shopper who arrives from a link has no saved address, may not be signed in, and may pick a variant the store has never shown you in a cart.

That is why a test order can finish and still hide a bug. The confirmation page loads, the admin lists an order, and the payment goes through, while the item count, a discount line or the shipping amount is wrong for the path a new buyer takes. You only see that when you compare the screens side by side, so put the two totals next to each other.

Where the order and the page disagree

Compare four things and write each one down: the item and variant, the quantity, the total, and the tax and shipping lines. The cart and the payment step show what the shopper is asked to pay. The admin shows what the store recorded. A mismatch on quantity usually starts in the cart, and a mismatch on shipping usually comes from the rule that matched the address. A mismatch on tax points at the address you used, which is why the test address matters.

Check the confirmation email the same way. It should repeat the items and totals you paid, with the same variant names, the same shipping address and the same currency. A confirmation that is missing, or that shows a different total from the page, is its own fault, and it may need its own fix from whoever sends the store's emails.

The path a simulated visitor covers, and the order it does not

A simulated visitor starts signed out, uses the address it is given, and walks from the product page to the payment step, reporting what each screen showed. It does not place a real order, so it cannot show you the admin side. Use it to cover the path a stranger takes, and use your own test order to check that the store records what the page showed.

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 product or shipping edit can change what a test order records

Adding a variant, changing a price or editing a shipping rule can change the order without changing the page you looked at. Place a fresh test order after each of those edits, from a new private window, and compare it with the last one. Rerun the same simulated visitors to the payment step after each edit as well, so the path a stranger takes gets checked too.

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

Will a test order charge my card?

It can, if the store takes a real payment. If your payment provider offers a test mode you can use with the store, use it for the test order so no real money moves. If there is no test mode, place a small order, check it, and refund it.

Can a simulated visitor place a real order?

No. It walks from the product page to the payment step and reports what each screen showed. It stops before payment, so it cannot create an order in your store, and you still need your own test order to check the admin side.

Should I test with my own address?

Test once with your own address, so you know the basic path works, then test again with an address you have never saved. Your own address is saved and familiar, so it skips the fields and rules a new buyer has to deal with.

Will a test order show how many buyers will finish?

No. A test order shows that one order can be placed and recorded. It does not predict how many buyers would finish, so take that number from your analytics or from a live experiment after launch.

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 .