Checkout must let people go back and edit
Aliases: edit checkout · checkout review · back in checkout
What it is
Once checkout is paged, address, delivery slot, and invoice details leave the screen. Back-and-edit means returning to any completed step, changing one field without wiping the rest, and still knowing one is inside checkout. It is edit rights on the path—not how many steps drive abandon, and not forced registration. Without return, checking relies on memory; a spotted typo leaves only abandoning the order.
Why it happens
Checking needs related fields visible together. After paging, comparison moves to working memory, which is lossy. Spatial anchors (“that field was at the bottom”) die with the route. If going back reloads, clears the card, re-quotes shipping, and reshuffles the selected slot, audit cost jumps from a glance to a redo; most people submit wrong or leave. Dependencies make it worse: changing address should reprice shipping, but wiping a gift-card balance at the same time makes a correction feel like punishment. Return must keep the checkout frame; dumping someone on a product page is ejecting them from the funnel.
Studying it
Use tasks that must stay consistent across steps (address vs shipping, slot vs stock). Compare return-with-keep, return-as-wipe, and cancel-the-whole-order as the only edit.
Independent variables: can return to completed steps, values persist, quotes recompute on return, in-checkout summary editing. Dependent variables: cross-step inconsistency, voluntary returns, leave after return, post-submit address-change requests.
Lab participants told to audit over-use Back. Real users rarely flip for consistency, so the better question is whether a spotted error can still be fixed. A summary “Edit” that jumps to login or a product page is a navigation failure, not an edit test.
Where it stops holding
Issuer pages typically forbid the merchant from “going back” while keeping PAN data; finish review on a merchant summary before the handoff. Some legal-attestation steps intentionally cut review so the current text is read. A true one-page checkout uses scroll and in-page anchors; do not add a wizard back-stack. After a stock-hold timeout, return may find nothing to restore—treat it as a change event, not a rewind.
Applying it
- Give an explicit back on every checkout step that does not clear other already-valid steps; if address change must reprice shipping, label that recomputation alone.
- Before paying, show a read-only summary with per-group “Edit this”; after the edit, return to the summary, not the start of the funnel.
- Browser Back should land on the previous checkout step, not a product page or an empty cart.
- Verify by changing a postcode after the address is filled: shipping updates, tender and offers remain. Then use system Back and confirm checkout was not exited.