Home / Insights / Product Design and Discovery
Product Design and Discovery
One-Page Checkout or Multi-Step? Designing and Testing a Checkout That Converts
Checkout is where intent turns into revenue, and where many shoppers give up. This guide compares one-page and multi-step designs, sets out the details that matter more than layout, and gives a QA checklist and testing approach for safe changes.
TopicsProduct Design and DiscoveryQA and Software TestingWeb and SaaS Development
Key takeaways
- Baymard Institute’s average of 50 studies puts documented cart abandonment at about 70%; many causes — unexpected costs, forced account creation, complex forms — are fixable.
- One-page checkout suits simple orders and returning customers; multi-step suits complex orders, B2B purchasing and mobile screens with many fields.
- Field count, guest checkout, transparent costs, trusted payment options and clear errors matter more than the layout choice.
- Payment security and compliance — PCI DSS scope, strong customer authentication where required — must be designed in.
- Treat checkout changes as high-risk releases: thorough QA across devices and payment methods, and controlled A/B tests.
On this page
Checkout is the most valuable page in an online store and one of the most fragile. Baymard Institute, which aggregates 50 studies published between 2006 and 2025, puts the average documented cart abandonment rate at 70.22%. Some abandonment is unavoidable — people browse and compare — but much is caused by checkout design.
Why shoppers abandon during checkout
Baymard’s research on US shoppers who abandoned during checkout lists, among the top reasons:
| Reason | Share of shoppers |
|---|---|
| — | — |
| Extra costs too high (shipping, tax, fees) | 40% |
| Delivery was too slow | 20% |
| Did not trust the site with card details | 19% |
| Site wanted me to create an account | 18% |
| Too long or complicated checkout process | 17% |
Source: Baymard Institute. Excludes shoppers who were “just browsing”.
Baymard also found the average US checkout displays about 23 form elements by default, against an ideal of 12 to 14.
One-page versus multi-step
| Factor | One-page checkout | Multi-step checkout |
|---|---|---|
| — | — | — |
| Speed for simple orders | Faster; everything visible | More clicks |
| Overview | Easy to review all details | Requires summary step |
| Complex orders | Can become long and overwhelming | Breaks complexity into manageable steps |
| Mobile | Long scroll; needs careful design | Natural fit for small screens |
| Error handling | Errors may be far from the button | Errors handled per step |
| Analytics | Harder to see which section causes drop-off | Clear step-by-step funnel |
| Best for | Returning customers, few fields, digital goods | New customers, B2B, many delivery options |
An accordion or “one-page with sections” layout often combines the advantages.
Details that matter more than layout
- Guest checkout: offer it prominently; invite account creation after purchase.
- Transparent costs early: show shipping and taxes before checkout where possible.
- Minimal fields: remove optional fields, combine name fields, use address lookup and sensible defaults.
- Smart inputs: correct keyboard types on mobile, autofill support, inline validation and clear error messages.
- Trusted payments: familiar payment options, wallets and local methods; visible security cues.
- Delivery clarity: dates rather than vague ranges, and clear costs for each option.
- Order summary: always visible, editable without losing entered data.
- Performance: fast loading, especially on mobile networks.
Security and compliance
- Payment data: use hosted payment fields or redirects from your payment provider to minimise PCI DSS scope; never store card data yourself unless you are prepared for full compliance.
- Strong customer authentication: in regions that require it, such as the European Economic Area, handle authentication challenges smoothly.
- Fraud controls: provider risk scoring, velocity limits and address verification without blocking legitimate customers.
- Privacy: collect only what is needed and handle consent for marketing separately and clearly.
QA checklist for checkout changes
| Area | Checks |
|---|---|
| — | — |
| Devices and browsers | Major mobile and desktop browsers; small screens; landscape and portrait |
| Payment methods | Cards, wallets, local methods, authentication challenges, declined and timed-out payments |
| Order types | Single and multiple items, discounts, gift cards, subscriptions, international addresses |
| Errors | Invalid inputs, network loss, back-button use, session expiry, double submission |
| Accessibility | Keyboard navigation, screen readers, labels, error announcements, contrast |
| Performance | Load time on slow networks; behaviour under peak traffic |
| Integrations | Tax, shipping rates, inventory, order management, confirmation emails |
| Analytics | Each step and error tracked correctly |
Automate the most common paths end to end; test unusual payment cases manually and with provider sandboxes.
Our guide to test automation frameworks covers building reliable end-to-end tests.
Testing changes safely
- Baseline first: conversion by device, step-level drop-off and error rates.
- A/B test one significant change at a time, with enough traffic and duration to cover weekly cycles.
- Monitor guardrails: payment failures, fraud rates, support contacts and average order value.
- Roll out gradually with feature flags and the ability to revert instantly.
- Avoid peak seasons for large redesigns unless thoroughly tested.
B2B checkout considerations
Business buyers have different needs from consumers:
- Purchase orders and invoicing as payment methods, with credit limits.
- Approval workflows where a buyer’s order must be approved by a manager before submission.
- Saved carts and reorder lists for repeat purchases.
- Account-specific pricing and delivery locations.
- Tax exemptions and VAT numbers captured and validated.
These often justify a multi-step or role-aware checkout, with clear status for orders awaiting approval.
Mobile-specific details
- Thumb-friendly controls: large buttons, adequate spacing, primary actions within easy reach.
- Wallet payments that avoid typing card details.
- Address autocomplete and correct input types for phone numbers, postcodes and email.
- Persistent order summary that does not cover form fields.
- Resilience: keep entered data if the connection drops or the app moves to the background.
Worked example
A hypothetical homeware retailer sees high mobile drop-off at the address step. A UX review — see our UX audit guide — finds 19 visible fields, forced account creation and shipping costs revealed only at the final step. The team introduces guest checkout, address lookup, an estimated shipping cost on the cart page and a three-section accordion layout. Each change is tested separately against a control. The largest improvement comes from showing shipping costs earlier; the layout change has a smaller but positive effect on mobile.
Frequently asked questions
Is one-page checkout always better?
No. It suits simple purchases; complex orders and mobile users often do better with clear steps. Test with your customers.
Should we force account creation?
Generally no. Offer guest checkout and invite account creation after purchase, when the benefit is clear.
How many payment options should we offer?
Enough to cover your customers’ preferred methods in each market, without cluttering the page. Analyse usage and remove rarely used options.
How do we reduce abandonment from unexpected costs?
Show shipping, taxes and fees as early as possible, ideally on product and cart pages.
Sources and methodology
Facts in this article were checked against the sources below on 6 November 2026. Directory data (ratings, review counts, rate bands and team sizes) changes over time and is shown as published on the date accessed. Illustrative examples are labelled as such and are not quotes.
- Baymard Institute: Cart abandonment rate statistics — accessed 6 November 2026. 70.22% average documented abandonment across 50 studies (2006–2025); top abandonment reasons; average 23.48 form elements versus 12–14 ideal
Related reading
Continue your research
Losing customers at checkout?
Share your checkout flow and analytics. We will review it, propose improvements and help you test them safely.