Square Online checkout page: what buyers see

You approved the checkout from a laptop, signed in, with an address you have used many times. That view hides what a new buyer meets first: the layout on a small screen and the fields a stranger must fill in. On a phone, the order summary may sit folded away, so the buyer sees a total they cannot match to the cart. A required line you never use, such as a company name, can stop a buyer who has nothing to type there. Each screen waits for the one before it, so the first thing that stops a stranger is usually the thing you never saw.

• Open the checkout on a phone in a private window. Can you read the total without opening anything?
• Enter an address you have never used. Does every required field fit a buyer who has no company?
• Change the quantity on the cart. Does the summary on the next step follow the change?
• Reach the payment step and compare its total with the cart, line by line.
• Go back one step and forward again. Does the address you typed survive the trip?

A typical checkout runs in a fixed order: the cart, the contact details, the delivery method, the address, and then payment. Each screen passes the buyer on only when the one before has what it needs, so one required field can stop the order with no message anywhere near it. The buyer does not know the layout is the problem. They see a page that asks for something they do not have, and they close the tab. Walk the path in order, and write down the screen name and the first field that made you pause.

When you check the checkout as the owner, you are usually signed in and your saved details fill the form. You never type the fields a buyer types, so a field you ignore can look correct to you and stop a stranger. A delivery option that depends on the address, or a total that changes when a line is added, can work for your address and fail for the next one.

Phones make this worse. The on-screen keyboard can cover the button a buyer needs next, and a tall order summary can push the fields below the fold. A laptop shows neither problem, so the layout you approved may never have been seen on a phone at all. Open the live address on a phone in a private window, with nothing saved, and read each screen before you tap anything.

The total is the number a buyer watches most. Write it down on the cart, on the delivery step and on the payment step, then compare. If the delivery step adds a charge the cart did not show, the buyer feels misled even when the charge is correct. If the total drops after an address change, the buyer wonders what they left out of the cart. A total that moves between screens is a reason to leave.

A checkout run stops at the payment step, because a simulated buyer cannot pay with a real card. Stopping there does not mean the rest works. Whether the payment step accepts a particular card is a question for a real order. What the run does show is every screen up to that point, the field it stopped on, and a screenshot of that screen, so you know which step to fix first.

Every new delivery area, tax rule, discount or theme change can move a stop onto a screen you already passed. Run the same cart with a new address after each change, on a phone and on a laptop. Keep the first run's screenshots, so you can see which step moved and when.