Start with the customer decision
The customer arrives with a product to buy, not a plan to join a membership programme. At the cart or first checkout screen, make the immediate decision plain: continue as a guest, or sign in if an existing account would help. Registration can be offered after the order is complete. Baymard’s checkout research describes how early account prompts can distract users and how a guest choice can be overlooked when it is visually buried. Treat that research as design evidence, not a forecast of your own conversion rate. A Hong Kong shop still needs to test its own customers, devices and products. Write down what an account actually adds: saved addresses, order history or repeat ordering, for example. If there is no concrete benefit to this purchase, do not imply that a password is necessary. If a product genuinely requires an account for ongoing access, explain that requirement before checkout rather than springing it on the final step.
Separate three routes clearly
A returning customer may sign in; a new customer may pay as a guest; a guest may later choose to create an account. These are three distinct states, even if the same email address appears in all of them. Use action labels that describe the next step, such as “Continue as guest” and “Sign in”, rather than ambiguous categories such as “New customer”. Keep the guest action visible on a narrow mobile screen before a keyboard opens, and do not ask guests to reject registration a second time mid-checkout. Signing in should return the shopper to the same cart and preserve choices already made. A failed sign-in must still leave the guest path available unless a disclosed product requirement prevents it. Avoid silently turning a guest purchase into an account; the customer should know whether they will later need a password or a verification method. A designer can sketch these states before coding, then trace every button to the next screen.
Keep contact details tied to the order
Guest checkout does not mean anonymous fulfilment. A shop still needs the details required to deliver the goods, send a confirmation and handle a problem with that order. Explain the purpose of each required contact field in the context of the chosen delivery method. Do not use the presence of an email address as proof that an account already exists, or assume that the address owner has asked for marketing. Shopify’s current checkout settings illustrate that a merchant can choose an email contact method or allow phone or email, and separately decide whether sign-in is required. Those are platform controls, not a universal rule for every store. If using Shopify, check the current store settings before copying any flow; requiring sign-in can also change which accelerated checkout options appear in the cart. For a custom build, keep the same conceptual separation in its own data model and interface.
Preserve the order across identity changes
An account prompt must never be able to place an order twice, change a price or make a completed purchase appear incomplete. Keep the order’s reference, payment state, delivery choice and contact method authoritative in the order record. Treat account creation as a separate action after that record is confirmed. If the customer leaves the account prompt, the order remains visible in the confirmation page and recoverable through the shop’s chosen contact channel. If the customer is already registered under the same email, do not merge records merely because the strings match; provide a controlled sign-in or verified linking journey. Conversely, a returning customer who signs in during checkout should be able to review any saved address before it is applied. The decision test is simple: could a person change identity route without accidentally buying a different basket? If the answer is uncertain, stop the launch and inspect the handoff between cart, order and account components.
Invite registration after confirmation
A confirmation page can offer an optional account without putting it between the shopper and the sale. Explain the benefit in one sentence, then offer a clear “Create account” action beside an equally clear way to finish or leave. Avoid copy that suggests registration is needed to receive the already placed order. If the shop will attach the guest order to the new account, explain how the customer proves control of the contact address and what order information becomes visible. Never display a prefilled password or expose payment details to a newly created session solely because it shares an email address. The invite should be absent or adjusted when a customer is already signed in. Baymard specifically recommends delaying the invitation until confirmation; that finding supports the placement, while the security and data linking details need deliberate implementation in each shop. Ask whether a new account has enough ongoing value to justify the prompt at all.
Walk through a realistic purchase
Consider a first-time buyer ordering a household item for delivery. On a phone, she sees “Continue as guest” beside the sign-in option and proceeds without creating a password. She enters only the contact and delivery data needed for this order, checks the total and submits once. The confirmation page shows an order reference and explains where future updates will arrive. It then offers an optional account for easier repeat shopping. She closes the page without registering. The order must still exist and the support team must be able to find it using the agreed contact and order reference. Now repeat the exercise with a buyer whose email matches an old account, a buyer who chooses sign-in but forgets the password, and a buyer using an accelerated payment button. Each path should reach a coherent confirmation, or clearly explain a genuine restriction before money is committed. This scenario is a test script, not a claim about measured customer behaviour.
Turn the design into acceptance checks
Test with real devices and keyboard navigation, including a narrow phone viewport, because a visible option on a desktop mockup can be hidden below a mobile sign-in form. Record which route was selected, but do not treat a button click as a completed order. Check that the cart, prices and delivery choice survive sign-in, failed sign-in, back navigation and a refresh. Place a test guest order and verify the confirmation, notification and later order lookup without an account. Place a signed-in order and verify that no guest prompt appears. Place a guest order using an address that also belongs to an existing account, and confirm there is no automatic takeover or disclosure. Shopify merchants should inspect the actual checkout settings and accelerated payment behaviour in their own store rather than infer them from documentation alone. Use support tickets and observed sessions to revise wording; analytics alone cannot explain why a shopper hesitated.
Handle exceptions without coercion
Some shops sell subscriptions, regulated services or digital products whose later use depends on an identity. In that case, the account requirement may be part of the product, not merely a checkout preference. State exactly what access requires and at which point the customer must verify it, so the requirement is a considered purchase condition. For ordinary shipped goods, do not use a desire for repeat marketing as a reason to call registration mandatory. Keep marketing choice distinct from order contact, and give a guest a practical route to request help later. If a payment provider returns the buyer to a different page, preserve the same identity choice and order reference rather than opening a second registration funnel. If the order is not actually confirmed yet, say so plainly; do not invite account creation on a page that only proves a payment attempt began. Clear distinctions between guest, account and order states reduce both customer confusion and support investigation time.
Review the route after launch
After launch, look separately at how many shoppers reach the account-choice screen, choose guest or sign-in, reach payment, and receive a confirmed order. Keep those events distinct: a guest click is not a sale, and an abandoned session does not reveal the person’s reason. Compare support contacts about account confusion with observed tests on a small phone and with returning customers. If many shoppers try to sign in and fail, investigate the sign-in experience before hiding the guest choice. If guests later cannot find an order, improve the confirmation and lookup route before making registration compulsory. Review any proposed change against the original customer question: can a person buy the item with a clear understanding of what identity, contact details and future access they are choosing? Document the route and its exceptions for support staff so they do not tell customers that an account was created when only an order was recorded. Recheck the whole path when a checkout plugin, payment method or account system changes, because an apparently small setting can alter the visible choice.
Before you proceed
- Can a first-time buyer complete an ordinary order without making a password?
- Does signing in preserve the cart and return the customer to checkout?
- Can a guest find the completed order later without an account?
