November 16, 2026

How to Review a Cart or Checkout Layout

Keep a cart or checkout layout that makes the progress, the order, and the commitment clear, without completing the purchase.

A chrome wire shopping basket with a pink handle holding a black clarinet case, with a paper receipt in front whose total line is underlined in blue, on an orange background.
In this guide

A visitor in the fictional music school Reed & Meter’s small shop has a rental clarinet in the cart. They need to see, together, what is in the order, what the total represents, and what the next step will do. On the checkout page, the total is no longer visible, and a second action, “Create an account to save this rental,” sits beside “Continue.” It is no longer obvious what they are committing to.

Reed & Meter is a teaching example, not a test result. This guide starts at the cart. What a shopper needs on a product page, including the decision to add an item, is already covered in What Shoppers Need on a Product Page.

The useful question is whether the visitor can understand the order, the total, and the next action before making a commitment.

Before you review a cart, checkout, payment, or login path, agree on a safe test path with the team first, including the page and cart or checkout state you will look at, and where you must stop. Do not complete a purchase, and do not submit a payment or login form, in a preview. Review those pages on the live site, along the agreed path.

Use these questions as a way to think, not as a score:

  • Can the visitor tell what is in the order?
  • Can they tell what the displayed total represents?
  • Can they tell where they are in the process?
  • Can they tell what the next action means?

Review the Layout, Don’t Complete the Purchase

Online Website Previewer previews one address at a time. Paste a page address and press Preview, and that address opens in all three frames: phone 390 by 844, tablet 820 by 1180, and desktop 1920 by 1080 CSS pixels. The previewer is a visual check of layout in your current browser, not a test of a particular device.

Because actions on the live page are real, treat the preview as a way to look at layout only. If you need to move through checkout, do that on the live site, on the safe test path, and stop before anything is submitted or paid. Before you judge the layout, check that the preview actually shows the agreed cart or checkout state. If the order you expected is not in view, do not treat that as a layout defect, and do not count it as a checkout-layout check. Go back to the agreed live-site path, or ask the team for a safe way to view the populated state. Then, at each width, look at the order, the total, the progress, and any competing actions.

Keep Progress, Order, and Exits Understandable

web.dev’s payment and address form guidance (Google, last updated October 22, 2026) advises making guest checkout the default and making account creation simple once checkout is complete, and showing progress through the checkout process in clear steps with clear calls to action. That is platform guidance, not a comparative study of marketing shops.

Apple’s Human Interface Guidelines on entering data tell designers to minimize the amount of data people need to supply, and to get information from the system whenever possible. That is app guidance, useful as corroboration, not as a web test.

This guide’s reading check is simpler still: the visitor should be able to see the order, understand the total, and tell the next step from any competing action. Extra exits and extra fields make that harder when they hide the task.

Baymard’s 2024 article on checkout form fields is usable here only in qualitative terms. It argues that the number of form fields affects overall usability more than the number of steps. This guide does not print field-count or step-count figures, and it does not turn that observation into a threshold. The disagreement between counting fields and counting steps is real, and the fuller discussion of single-page versus multi-step forms for non-checkout tasks belongs in One Long Form, or Split Into Steps?.

On Reed & Meter’s checkout, the missing total and the competing “Create an account” action are the kind of layout problems a visual review can catch. Check whether the page makes clear if an account is needed to continue. Whether a later confirmation message is unmistakable is a different check, in What a Confirmation Should Tell the Visitor.

The GOV.UK check-answers pattern is one government system’s default for showing a single check page immediately before confirmation, so people have a second chance to notice and correct errors. Use it as a prompt that a review of the order should still be possible late in the path, not as a requirement to copy that pattern.

Hand Transaction Safeguards to the Team

WCAG 2.2 Error Prevention (Legal, Financial, Data), at Level AA, applies to pages that cause legal commitments or financial transactions, and requires that the submission be reversible, checked, or confirmed. WCAG 2.2 Redundant Entry, at Level A, asks that information already entered in the same process not have to be typed again, with listed exceptions. Neither criterion can be settled in a visual preview. Ask the team to confirm how the checkout handles error prevention for a financial transaction, and whether information already entered in the same process has to be typed again.

Listing-page comparison and empty filter results stay in Product Listing Page Best Practices. A wider pre-launch pass, including agreeing a safe test path, is already part of How to Test Your Website Before Launch: A Checklist.

Send a Keep or Rework Note

A useful note might say: “On the live checkout, along the agreed test path, at [page or step], in the [view and size checked], the rental clarinet was visible in the cart, but the total disappeared on the next step, and ‘Create an account to save this rental’ sat beside ‘Continue.’ I could not tell what I was committing to, or what the total would be. Please keep the order and the total visible, and make the primary next step unmistakable. I did not complete a purchase.”

For how to phrase the note, see How to Give Useful Feedback on a Website Design.