H7.02.1checkout steps and abandonmentdesignresearch

Checkout step count tracks abandonment

Aliases: checkout abandonment · checkout funnel · extra checkout steps

What it is

Checkout is the stretch that turns a cart into an order: address, delivery, invoice header, payment. Each extra screen or “Continue” is another chance to leave. Step count tracks abandonment is about path length consuming commitment. It is not how many lines sit in the cart, and not the single obstacle of forced sign-up. People enter checkout having decided to buy; every later step asks “still?” again.

Why it happens

Entering checkout is escalation: the cart was a candidate set, checkout is spending. Each step retrieves information, makes a choice, waits on validation. Goal-gradient needs a visible end, yet checkout often inserts unannounced pages for shipping, tax, accounts, OTPs, so the end keeps receding. Leave happens at step boundaries—re-estimating remaining work before “Next.” More steps are not the same as more fields: one address form split across three screens adds leave points without shrinking input. Marketing, review prompts, and membership upsells stuffed into checkout add surprise outside the count; that is trust damage, not merely duration.

Studying it

Read the checkout funnel per hop, not only final payment success. Compare one-page checkout, a fixed three-step wizard, and a wizard that injects pages midstream.

Independent variables: screen count, fields per screen, injected account or promo pages, whether the progress denominator stays locked. Dependent variables: leave rate per step, cart-to-paid completion, returns to cart, time to finish.

Lab participants are usually told to buy, so abandonment barely appears; real leave needs unincentivized traffic or remote tasks. Higher conversion on a shorter path is not proof that fewer fields are better—the short path may have skipped delivery options. Code trust-break leaves from injected pages separately from long-form fatigue. Do not invent or copy industry abandonment percentages; they move with category, device, and whether guest checkout exists.

Where it stops holding

Regulated goods (prescriptions, customs) cannot drop statutory steps; merge presentation rather than pretend there are two. High-ticket and custom orders expect review; some steps are structure, not waste. Pickup and virtual goods have no delivery step; a physical-goods wizard invents a screen. Internal procurement is an approval flow; abandon rate is not the headline metric.

Applying it

  • Before checkout, name the decisions ahead (address, delivery, pay) and lock the count; never insert an unannounced last page.
  • Merge items that can share a screen without cross-field dependence; split only when validation must wait (address check, shipping quote).
  • Put marketing, membership, and reviews after paid success; they are not checkout steps.
  • Verify with a per-screen funnel; change or merge the peak-leave hop, then compare cart-to-paid completion in the same traffic window rather than store-wide GMV.

Related

  • Within the group: H7.02.2 Checkout must let people go back and edit · H7.02.3 Forced registration is a primary drop-off
  • Adjacent: H7.01 Shopping cart · H1.01 Form length and multi-step · H6.01 Registration friction
  • Search terms: checkout abandonment · checkout steps · funnel drop-off

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/H7.02.1