A one-page checkout puts the order summary, every field and the pay button on a single screen. A multi-step checkout splits the same work into stages, typically contact, delivery, payment and review. One page suits a short form and a simple order. Steps suit a long form where one answer, such as the delivery country, changes what comes next.
Neither layout wins by default. Below: both layouts described, a counting test you can run in five minutes, a decision table and the four things that affect sales more than the layout does.
What each layout looks like
One-page checkout
Everything sits on one screen that the buyer scrolls: what they are buying, the total, their details, the payment form and one button. Nothing loads between sections. A common variation is the accordion, a single page where each section folds away once it is filled in.
Multi-step checkout
The form is cut into screens, usually with a progress bar across the top. A store that ships usually runs three or four:
- Contact: email, sometimes a phone number.
- Delivery: name, address and shipping method.
- Payment: card or another method.
- Review: the final total, then the button. Some stores fold this into the payment step.
Each screen is short. The price is more taps, more loading and more chances for the total to change after the buyer has started.
Count your fields first: a worked example
The layout question is mostly a question about length, so count before you choose. Write down every box, picker and choice a buyer must complete. Here are two made-up sellers.
| What the buyer fills in | Seller A: a $12 digital planner | Seller B: a ceramics shop that ships abroad |
|---|---|---|
| 1 | 1 | |
| Name | 1 | 1 |
| Address (two lines, city, region, postal code, country) | 0 | 6 |
| Phone number for the carrier | 0 | 1 |
| Shipping method | 0 | 1 |
| Gift note | 0 | 1 |
| Card number, expiry, security code | 3 | 3 |
| Total inputs | 5 | 14 |
Seller A's whole checkout fits on one phone screen. Spreading five inputs over three steps would add taps and remove nothing.
Seller B has 14 inputs, and the shipping cost depends on the country, so the total cannot be final until the address is in. That is the classic case for steps, or for one page with clearly separated sections.
Here is a rule of thumb for your own count. It is ours, a starting point and not a research finding. At about 8 inputs or fewer, use one page. At about 12 or more, with a choice that changes the total, use steps or sections. In between, either works, so go with what your platform does well by default.
When each layout wins
One page tends to win when
- You sell one product or a small basket.
- The form is short: name, email, perhaps one or two questions, then payment.
- The price is settled before the buyer starts typing, as with a download, a service or a product with shipping included.
- Buyers arrive on phones from a link, a bio or a QR code and want to finish in one go.
Steps tend to win when
- The order needs a delivery address and a shipping choice.
- An early answer changes later ones: the country sets the shipping options, and shipping sets the total.
- The cart holds many lines and the buyer wants a review screen before paying.
- You send cart reminder emails and want the email address saved at step one, even if the buyer stops at step two.
Decision table by what you sell
| What you sell | Better fit | Why |
|---|---|---|
| A digital download or template | One page | Email and payment are the whole form |
| A coaching call or session | One page | A date and time, one or two questions, payment |
| A donation or tip | One page | An amount and a button are all it needs |
| One physical product with flat shipping | One page | The total is known up front |
| A mixed cart shipped to several countries | Multi-step | Shipping options and the total depend on the address |
| Made-to-order goods with many options | Steps or sections | Options, then delivery, then payment keeps each screen readable |
| Large or wholesale orders | Multi-step | Buyers want to check every line before paying |
Getting the chosen layout right
Whichever way the count points, a few rules keep the layout from working against you.
If you go with one page
- Group fields under plain headings such as "Your details" and "Payment".
- Keep the total next to the pay button and update it the moment an option changes.
- Put optional fields last, or remove them.
If you go with steps
- Name the steps in a progress bar, so buyers can see how much is left.
- Show the running total on every step, and the shipping cost as early as you can work it out.
- Let buyers go back a step without losing what they typed.
Four things that matter more than the layout
A short, clear, fast one-page form does well. So does a short, clear, fast three-step form. What hurts is a long, vague or slow form in either shape. Check these before you spend time on layout.
- Field count. Test: for each field, name what you do with the answer. If you cannot, delete it.
- Clarity of the total. Test: can the buyer see the final amount before typing payment details? If a cost appears later, move it earlier.
- Trust. Test: does the page carry your name, logo and color, and say who handles the payment?
- Speed. Test: open the link on a phone on mobile data and count the seconds until you can type.
The full list is in our 15 checkout page best practices, with a pre-launch checklist. To see how short forms are arranged in practice, the six checkout page examples list every element in order.
How to judge your own checkout without a big test
Advice on this topic often leans on split tests run by large stores. A small seller rarely has the traffic to repeat them, and a little arithmetic shows why. With 200 visits and 6 orders in a month, 3 in every 100 visitors buy. One extra order makes it 3.5 in every 100. A single order can come from luck, so one month tells you almost nothing about a layout.
These work better at small scale:
- Watch three people buy on their own phones. Friends count. Note where they pause, scroll back or ask a question.
- Time it. From opening the link to tapping pay, how long does a first-time buyer take?
- Compare views with paid orders over months, not days. Small numbers swing widely week to week.
- Change one thing at a time. If you alter the layout and the price together, you will not know which one moved the result.
Where Chargedeck fits, and where it does not
Pages made with the Chargedeck checkout page builder are single-page and mobile-first. The product, any variant, date or amount choice, your custom fields, an optional order bump and the pay button sit on one screen, and the money goes straight to your own Stripe, PayPal or Square account. That suits Seller A and most rows in the top half of the table. You can look around the builder in the live demo.
It is not built for Seller B. Chargedeck has no multi-step flow, does not calculate sales tax or VAT and does not send abandoned-cart emails. A large catalog with shipping rules by destination is better served by a full store platform with its own stepped checkout.
There is a middle route if you run WooCommerce. Keep WooCommerce's own cart and checkout for the address and shipping, and use the Chargedeck plugin as the payment method: it sends the cart total to a Chargedeck checkout for the payment step. The plugin is free to download, and taking payments with it needs a Chargedeck plan. The WooCommerce guide explains the setup, and WooCommerce checkout optimization covers the rest of that form.
The cost is a flat monthly fee with 0% of your sales taken (see pricing). Card fees from your own processor are separate and still apply.
