Skip to content
UX Atlas
Case studyCraft conventionFoundational

Whether to Require an Account at Checkout

A retailer required registration before purchase to build its customer database, and lost the sales it was trying to capture data about.

Definition

A decision case about forced account creation in checkout: the commercial argument for it, the usability evidence against it, and the resolution that satisfied both.

Craft convention. True because the industry converged on it. Breaking it costs familiarity, not correctness.

On this page
  1. Definition
  2. How to run this analysis on your own flow
  3. Sources
  4. Continue from here

A composite scenario assembled from situations that recur across teams. It is written to teach reasoning rather than to report on a named company, and outcomes are stated directionally rather than as invented measurements.

Problem

Checkout abandonment was concentrated at a single step: the account creation screen that appeared before payment.

Context

A mid-sized retailer with a growing repeat customer base. The marketing team had a target for registered accounts, and registration was placed before payment because that was where it captured the most people.

Constraints

  • The commercial target for registered customers was fixed for the year.
  • Order history and returns both required an identifiable customer record.
  • The existing checkout was a four-step flow that could not be rebuilt quickly.
  • Fraud rules required a verified email address before dispatch.

Decision

Allow purchase to complete with an email address alone, and offer account creation on the confirmation page, prefilled from the order details, requiring only a password.

Rationale

The account was needed for order history, returns and fraud checks. All of those are satisfied by an email address plus an order record. The password was the only additional thing registration provided, and it was being demanded at the moment of highest commitment and highest anxiety. Moving it after payment removed the barrier without removing the capability.

Evidence used

  • Funnel analysis isolating the drop to the registration step rather than to payment.
  • Session recordings showing users reaching registration, pausing, and leaving.
  • The Baymard Institute's long-running checkout research, which consistently identifies forced account creation as a leading cause of abandonment.
  • Support tickets from customers who had created duplicate accounts because they could not remember whether they had one.

Trade-offs accepted

  • Fewer passwords captured at the point of purchase, so some customers remain guests.
  • An additional record type to reconcile when a guest later registers with the same email.
  • The marketing team lost the ability to claim every purchaser as a registered user.

Outcome

Abandonment at the registration step disappeared because the step no longer existed. A meaningful share of customers created an account on the confirmation page, where the only remaining action was choosing a password. Total registrations were comparable, and purchases completed increased.

Alternatives considered

Keep registration but make it shorter

Why not: The number of fields was not the barrier. The barrier was being asked to make a commitment before receiving anything, which a shorter form does not address.

Social sign-in as the primary route

Why not: It helps some users and excludes others, adds a third-party dependency in the critical path, and raises data sharing questions that were not worth resolving for this problem.

Offer guest checkout as a small secondary link

Why not: This is the common compromise and it works, but it leaves the barrier in place for anyone who does not notice the link. Making guest the default and registration the offer inverts the friction correctly.

How to run this analysis on your own flow

  • List every field and step, and name the internal requirement each one serves.
  • For each, ask what the minimum is that would satisfy that requirement.
  • Ask whether it must happen before the user gets value, or whether it can happen after.
  • Move everything that can move to after the value moment.

Sources

Where a source establishes something narrower than the popular reading of it, the note says so.

  • Checkout usability research

    Baymard Institute

    Ongoing research programme identifying forced account creation among the leading causes of checkout abandonment.

Each link says what the connection is, so you can tell a principle from an alternative from a thing people mix this up with.

Concepts behind this decision

What the reasoning in this case rests on.