One page checkout is often sold as a counting exercise: fewer fields, fewer clicks, more sales. Stores then hide fields with toggles, pre expand sections, and compress forms until one page holds everything a three page flow did, only denser.
Shoppers do not count fields. They feel effort. A page that presents every question at once looks like work even if it is technically short, while a calm sequence of small steps can carry the same fields with less perceived load.
Perceived effort beats raw count
The first screen of a checkout sets the effort estimate. Twenty fields visible at once tells the shopper this will take a while, and some leave before discovering half the fields are optional or auto filled. Staged disclosure keeps the estimate low and honest.
That said, one page has a real advantage: no step transitions, no waiting, and the total visible throughout. The design task is keeping those advantages while hiding complexity until the moment each field becomes relevant.
Which fields earn their place
Every field should pass a simple test: is it needed to take payment, deliver the order, or meet a legal duty? Marketing questions, account creation demands, and nice to have data fail that test and belong after the order, if anywhere.
Optional fields should be rare, clearly marked, and collapsed where possible. Each optional field shown costs attention from every shopper, including the majority who will never fill it. That is a bad trade for data only a few provide.
Errors on a crowded page
Long single pages make errors expensive. A shopper sent scrolling to find one flagged field, on a phone, with the error summary out of view, is a shopper rehearsing abandonment. Inline messages, a summary that links to each problem, and preserving every correct entry are essential.
Test the error path, not just the happy path. Most checkout testing walks through a perfect order. Real shoppers mistype, and the recovery experience decides whether a dense one page layout survives contact with them.
Deciding between layouts with data
Compare layouts on completion rate for new shoppers, time to complete, error recovery rate, and support contacts, not on clicks alone. A layout that wins clicks but loses error recovery is losing money quietly.
Segment by device before deciding. One page often performs differently on desktop, where density is manageable, than on mobile, where the same page becomes a long scroll of forms. Many stores rightly end up with different answers per device.
Related reading
These earlier guides go deeper on connected questions: Guest Checkout vs Accounts: What the Conversion Data Usually Shows, Gift Options at Checkout: The Small Step That Carries a Lot of Emotion, and The Coupon Field Problem: A Box That Invites Shoppers to Leave.
Frequently asked questions
How many fields should a checkout have?
There is no magic number. Most physical goods checkouts need contact, delivery, and payment information, which lands roughly in the low teens of fields. The test is whether each field is necessary, not whether the total hits a target.
Is one page checkout always better than multi step?
No. One page wins on visibility of the total and lack of transitions. Multi step wins on perceived simplicity and focus. Well built versions of both beat badly built versions of either, so test with your own shoppers.
Should optional fields be removed or hidden?
Remove them if the data is not used. If it is genuinely useful, collapse it behind a clear toggle so most shoppers never pay attention to it. Account creation and marketing questions usually belong after purchase.
Why do shoppers abandon long one page checkouts?
Usually a mix of perceived effort at first sight and painful error recovery later. The page looks like work before they start, and one mistake sends them hunting through a dense form to fix it.