Forced registration is a primary drop-off
Aliases: guest checkout · account wall · forced sign-up
What it is
People have already pushed goods into checkout when the UI demands an account before address or payment. Forced registration swaps “pay” for “become a member,” and it is a recurring leave point on the path. It is not step count, and not back-and-edit: even a one-screen checkout dies if an account wall sits in front of pay. Guest checkout, a post-purchase invite to register, and “you cannot buy without an account” are not the same design.
Why it happens
Commitment at checkout points at the goods and the price, not at a long-term relationship with the site. Registration asks for email, password, OTP—each a new risk: marketing, a password to invent, a code that may not arrive. None of that is the purchase goal, yet it is made a precondition. The wall also reads as a trap: harvest identity, then talk money. People who already have an account and are pushed to register rather than sign in experience the friction as insult. Counting “account created” as funnel success hides unpaid orders: the account exists, the payment does not.
Studying it
Compare three paths with the same goods and the same tender: must register to check out, guest checkout with a success-page invite, optional account to prefill during checkout.
Independent variables: wall placement (entry / before pay / after success), guest path present, login vs register distinguished. Dependent variables: entry-to-paid, registered-but-unpaid, leave at the wall, register after success.
Do not glue registration conversion to payment conversion. Industry write-ups often list forced registration among the main checkout leave reasons; the share moves with existing accounts, device, and category, so no single percentage is a design target. Lab accounts handed to participants erase the wall.
Where it stops holding
Goods that legally require identity (some medicines, controlled proxy buys) can make verification a purchase condition, but verification is not a marketing account. When digital goods must be delivered to an account, money can still be taken first and the account bound before delivery. Enterprise buying already sits inside a login; there is no guest. If member price or points are the offer, show guest vs member price before checkout rather than locking the door after entry.
Applying it
- Default to guest checkout: email is for the receipt; password and marketing consent wait until after paid success.
- Existing accounts get “Sign in,” not “Register”; failed sign-in can offer create, and sign-in must not wipe cart or checkout draft.
- If compliance forces a wall, keep fields to the verification minimum and say they are for fulfillment, not membership.
- Verify by splitting the funnel into “reached the wall” vs “paid after the wall,” and by walking the guest path to confirm success-page register is optional. If post-wall pay is far below wall reach, the account is the drop-off.