A one-page checkout is a checkout that collects everything needed to complete an order (contact details, delivery address, delivery method and payment) on a single page, rather than across a series of steps. The shopper fills it in from top to bottom and pays without the page reloading.
How a one-page checkout works
The sections sit one above another, usually with an order summary beside them on desktop and a collapsible summary on mobile. Fields are checked as the shopper types, so mistakes are flagged straight away rather than after a submit. Express payment buttons such as Apple Pay, Google Pay and PayPal normally appear at the top, because a shopper who uses one can skip most of the form.
A multi-step checkout splits the same fields into stages, typically information, delivery and payment, each on its own screen. Some “one-page” checkouts are really accordions that open one section at a time, which behaves much like a multi-step flow on a single URL.
Platform defaults change. At the time of writing (October 2026), Shopify’s standard checkout uses a one-page layout and WooCommerce’s checkout also places every section on one page, while many custom builds still use steps.
One part sits outside the page whatever the layout. When a UK shopper’s bank asks for Strong Customer Authentication, a 3-D Secure screen or a banking app prompt appears after they press pay, and the checkout cannot finish until that is approved.
Why it matters
The checkout is where you lose people who have already decided to buy, which makes it the most expensive place to lose them. A single page removes page loads and lets the shopper see the whole task at once, which can make it feel shorter. That is the real benefit.
The length of a checkout is set mainly by the number of fields, though, not the number of pages. A single page with twenty fields is still a long form, and on a phone it can feel like an endless scroll. For a UK shop, the bigger wins are often postcode address lookup, a clear delivery cost shown early, and not forcing anyone to create an account. Mandatory charges revealed only at the last moment frustrate shoppers and can also breach UK rules on drip pricing.
There is a measurement cost too. On a multi-step checkout each page view marks progress. On a single page, GA4 only sees the checkout start and the purchase unless events such as add_payment_info are fired as each section is completed. Without them you cannot tell whether people stall at delivery or at payment.
Common mistakes
- Switching to one page while keeping every field, including ones nobody needs, such as a second address line marked as required.
- Requiring an account before payment instead of offering guest checkout.
- Express payment buttons pushed below the fold on mobile.
- Error messages that appear only at the top, so a shopper at the bottom of the page never sees why payment failed.
- A large discount code box that sends shoppers off to search for codes.
- No section-level events, so the checkout funnel in GA4 is a single unexplained drop.
How to act on it
Measure your checkout abandonment rate before changing anything, so you have a baseline. Watch a sample of checkout sessions in a session recording tool, paying particular attention to phones, and note where people pause, scroll back or give up.
Then work through the fields. Remove anything you do not need to fulfil the order, add postcode lookup, show delivery options and costs before payment, and put wallets where a thumb can reach them. If your platform lets you choose between layouts, test both rather than assuming. Finally, place a test order on a real phone with a real UK bank card and complete the authentication step yourself.
Checkout layout is usually decided when a site is built or rebuilt, so I cover it in website redesign projects, along with forms, tracking and page speed.