Checkout page: the fields, signals and steps that decide the sale

The checkout page is where a shop stops persuading and starts asking. Everyone who reaches it has already decided; every field, delay or surprise from that point is a reason to stop. That is what makes it the highest-leverage page in a store — small fixes there are worth more than a redesign anywhere else.

Most of the damage is done by three things: unexpected costs, forced account creation, and a form that is longer than the purchase justifies.

What belongs on a checkout page

• The order summary, visible without scrolling: items, quantities, and the total including shipping and tax. Not a link to it — the numbers themselves.
• Contact: email, and phone only if delivery genuinely needs it.
• Delivery address, with the fewest fields your carrier accepts, and a country selector that reorders the rest sensibly.
• Delivery options with real dates rather than "2–5 business days", and the cost of each shown at the point of choice.
• Payment methods people in your market actually use — cards plus the local wallets and bank methods that matter where you sell.
• Trust signals near the payment button: return policy, secure-payment indication, and a support contact that is a real channel.
• One primary button, labelled with what happens — "Pay 49.00" rather than "Continue".

Show the total cost as early as you can, ideally in the basket. Unexpected shipping and tax at the final step is consistently the single largest cause of abandonment — and it is a decision you can change today, not a design problem.

Guest checkout, and the account question

Forcing account creation before payment is the second-largest self-inflicted loss. It asks for effort in exchange for a benefit the customer has not experienced yet. Offer guest checkout, and offer the account afterwards — once the order is placed, the same person will happily set a password to track it.

If you need the account for a subscription or a licence, say why, in one line, at the point of asking. A reason turns a demand into a step.

Fixing the drop-offs

1. Walk your own checkout on a phone, on mobile data, with a real card. Most problems are visible in three minutes and invisible in analytics.
2. Count the fields. Remove every one you do not use — a company field, a second address line, a title dropdown.
3. Show shipping and tax before the last step, and show a total in the basket.
4. Enable the payment methods your market expects, and put the most-used one first.
5. Turn errors into help: keep entered data, mark exactly which field failed, and never clear the card entry on a validation error.
6. Send the confirmation immediately, with what was ordered and when it arrives. Silence after payment generates support tickets and doubt.

In Ettex Sites, store templates and 70+ sections cover the storefront and the pages around checkout, a live canvas edits them visually, and theme controls keep fonts, colours and spacing consistent across the flow. Custom domains connect with certificates issued automatically — a checkout on your own domain rather than a stranger's subdomain is itself a trust signal — and built-in analytics show visits, referrers and page stats, so you can see where people stop. Forms feed a built-in leads inbox, which is where pre-purchase questions land.

Checkout mistakes that quietly cost money

• A discount code box more prominent than the pay button, which sends people off to hunt for a code they never come back from.
• Address forms that assume one country's format, so international customers cannot complete a valid address.
• Recalculating the total after the card is entered.
• No visible return policy at the moment of payment, which is exactly when people look for it.
• A confirmation page that says "thank you" and nothing about what happens next.

A checkout page does not need to persuade. It needs to be honest about the total, short about what it asks, and clear about what happens after the button.