Direct answer
Checkout loses buyers who have already chosen, so every rule removes friction: show the full cost before checkout starts, put guest checkout first, keep the flow linear, name every button's next action, and never clear a field on error.

Checkout design: what to know
Each rule is listed with its source at the end of this page, read on November 12, 2026.
- The named causes of abandonment are costs that appear late, forced account creation, a flow that feels too long, and a missing payment method.
- Put shipping, tax and every fee in the cart, before checkout begins, and never add a new charge at the review step.
- Put guest checkout first, above sign in, with the same visual weight, and use the word guest.
- Offer account creation after the order is confirmed, not before.
- Never show the same page twice, and make a progress indicator match the real steps exactly.
- Remove the site navigation from checkout and leave the logo as the only way out.
- Name the next action on every button, and use place order on the last one, never continue.
- Default the billing address to the shipping address, put the second address line behind a link, and use one full name field.
- Format the card number in groups as it is typed, matching the physical card.
- Preselect the most common payment method with its fields shown, and offer at least one wallet beside cards.
- Never clear a field on error, and say what is actually wrong next to the field.
- Keep the order summary visible through checkout, and put the return policy within reach of the payment step.
Causes of cart abandonment and the fix for each
| Cause | Fix | Where it applies |
|---|---|---|
A cost that appears late | Fix Show shipping, tax and fees in the cart | Where it applies Cart |
Forced account creation | Fix Guest checkout first; offer an account after the order | Where it applies Start of checkout |
A flow that feels too long | Fix One linear path, no repeated steps, no site navigation | Where it applies Every step |
A missing payment method | Fix At least one wallet beside cards, with the common method preselected | Where it applies Payment step |
An error that wipes the form | Fix Never clear fields; say what is wrong beside the field | Where it applies Every form field |
Put Checkout design into practice
- Move every cost into the cart before checkout starts.
- Put guest checkout first and defer account creation until after the order.
- Strip site navigation and anything that interrupts the flow.
- Label each button with its next step, ending with place order.
- Test every error: no field clears, and each message says what is wrong.
Checkout design in four steps
The four steps, in the order you take them.

- Step 1: Show the full cost in the cart
- Step 2: Offer guest checkout first
- Step 3: Keep one linear path
- Step 4: Make errors recoverable
Caveats to keep in mind
- A guest option below a sign-in field can sit under the phone keyboard; top placement is what makes it reachable.
- A review step with a vague button can be mistaken for a confirmation page.
- If a button leads off site to a payment provider, say so on the button.
- Returning to a cleared form after the browser back button is an exit, so keep every entered value.
Steal this workflow
Run this guide in your own assistant. The prompt carries the guide link and the workflow summary, so the assistant can adapt it to your project.
Read the guide "Checkout design: how to cut cart abandonment, step by step" at https://better-design.com/blog/checkout-design and help me apply it to my project.
Checkout loses buyers who have already chosen, so every rule removes friction: show the full cost before checkout starts, put guest checkout first, keep the flow linear, name every button's next action, and never clear a field on error.
Start by asking what I am building and which tools I use. Then walk me through the workflow step by step, adapted to my answers.Claude and ChatGPT open with the prompt filled in. Gemini copies the prompt to your clipboard first, so paste it when the app opens.
Questions
What causes cart abandonment?
The common causes are costs that appear late, forced account creation, a flow that feels too long, and a missing payment method.
Should checkout force an account?
No. Put guest checkout first with equal weight, use the word guest, and offer an account after the order is confirmed.
What should the last checkout button say?
Place order. A vague label such as continue on the review step can be mistaken for a confirmation, and the visitor may leave thinking they have bought.
Where these rules come from
Each fact comes from Better Design's commerce guidance, the same guidance its MCP server gives coding agents, read on November 12, 2026.
Related
Build the interface in your own code instead
A coding agent such as Claude Code, Cursor or Codex can build these screens in your own code. Better Design gives that agent a design system, interface principles and review rules, so the result follows rules like these and looks designed.