Ecommerce UX Examples: Annotated Product Page, Cart and Checkout Screens

published on 16 November 2026

By Nick Babich

These eight ecommerce UX examples follow one shopper from product page to cart to checkout, and each note names the doubt the screen removes.

The stores are fictional and drawn for this article, so you can judge the pattern instead of the brand. Prices, dates and reviews in the screens are made up. If you want people who design these screens for a living, see the ecommerce UX design teams we compare for online stores and DTC brands.

Key Takeaways

  • One question per screen: the product page answers "Is this the right one, and when will I have it?", the cart answers "What will I pay in total?", and the checkout answers "How much is left, and is my card safe?"
  • Dates beat speeds: "Arrives Thu, Nov 19" is easier to act on than "3-5 business days", so show a date on the product page and on every shipping option.
  • Show the full cost before checkout: large-item delivery, assembly, tax estimates and return fees belong in the cart, not on the last step.
  • Edit in place: shade, size and quantity changes should happen inside the cart, without a trip back to the product page.
  • Ask for an account last: guest checkout first, and an optional account on the confirmation screen, where only a password is missing.

Ecommerce UX Examples at a Glance

Three examples cover the product page, two cover the cart and three cover checkout and confirmation, across eight store categories and both desktop and mobile. When I read the US Google results for "ecommerce ux examples" on November 16, 2026, four of the top five results were screen galleries and one was a forum thread asking for good examples. None of them walked the product page, the cart and the checkout in order, which is what this table and the sections below do.

#StoreScreen and platformCategoryPattern to look for
1FernwayProduct page, desktopOutdoor apparelFit note, size worn by the model, delivery date by ZIP code
2Kettle & CrumbProduct page, iOSKitchenwareScale photo, review summary, stacked spec sections, sticky bar
3Voltgrid SupplyProduct page, desktopIndustrial partsSpec table, fit check, quantity pricing, stock by warehouse
4Lumen SkinCart drawer, AndroidBeautyEdit shade in place, quantity buttons, estimated total
5Hollis HomeCart page, desktopFurnitureLarge-item delivery fee and window, return terms by the total
6Petal & PostCheckout, mobileFlowers and giftsGuest first, recipient apart from billing, gift message
7Northline AudioOne-page checkout, desktopElectronicsExpress pay, autocomplete, delivery dates, fixed summary
8Grocer LaneOrder confirmation, mobileGrocery deliveryEdit cutoff, substitutions, account offer after payment

Each example has the same four labels: who the shopper is, what the screen shows, why it works and what to watch for. The annotations are about design decisions, not about visual taste. For a broader view of how we look at product work, start with the UX design teams we review, with the criteria we use.

How to Read These Examples

Read each screen against the one question the shopper has at that step: if the screen answers it without a scroll or a new tab, the shopper moves on. Over years of participating in redesigns and observing user behavior, I have found that you can evaluate any ecommerce flow by asking one specific question per screen.

  • Product page: "Is this the right one for me, and when will I have it?" Size, fit, scale, compatibility, the delivery date and the return terms answer it.
  • Cart: "What will I pay in total, and can I still change my mind?" An estimated total with delivery and tax, edits in place and a save-for-later option answer it.
  • Checkout: "How much is left to do, and is my card safe here?" Guest checkout, few fields, clear required and optional labels, express pay and a summary that stays in view answer it.
Three money screens of an online store, product page, cart and checkout, each with the one shopper question it must answer and four things it should show
One shopper question per money screen, and what each screen should show to answer it.

The confirmation screen gets a fourth question: "What happens next, and can I still fix it?" Example 8 shows it.

Product Page Examples

A good product page removes the two doubts that stop the add-to-bag click: whether the item fits the shopper's need and when it will arrive. The three pages below do it for clothing, a countertop appliance and an industrial part.

1. Fernway: outdoor apparel product page, desktop

Fernway desktop product page for an insulated jacket: a fit note saying it runs small, the model height and size worn, a size chart on the page, a delivery date for a ZIP code with an order-within countdown, and free returns next to the Add to bag button, annotated with five numbered callouts
Fernway, apparel product page: fit help sits on the page, and the delivery date sits next to the button. Illustrative example with fictional data.

Shopper: Someone buying a winter jacket from a brand they have not worn before.

What the screen shows: A fit note built from reviews ("runs small, most reviewers size up"), the model's height and the size he wears, a size chart in the page instead of a pop-up, and a delivery line next to the Add to bag button: "Deliver to 94110: arrives Thu, Nov 19 if you order within 3 h 12 min." Free 30-day returns sit under the button.

Why it works: Clothing returns start with size doubt, so the page answers it with three kinds of evidence: other buyers, a real body and the measurements. The delivery date and the countdown answer "when will I have it" at the moment of decision. In its 2026 checkout benchmark, Baymard Institute found that 83% of sites do not show the order cutoff as a countdown (Baymard: Checkout UX 2026, 10 Pitfalls and Best Practices, updated Nov 3, 2026).

Watch for: The ZIP code lookup must not slow the page down. Load the date after the page renders, and show a fallback ("arrives in 2-4 days") if the lookup fails.

2. Kettle & Crumb: kitchenware product page, iOS

Kettle and Crumb product page for a stand mixer on iPhone in three screens: a gallery photo with a mug for scale and height and depth marked, a review summary with what buyers mention, then specs in vertically stacked sections with a sticky Add to bag bar, annotated with five numbered callouts
Kettle & Crumb, mobile product page: a scale photo, a review summary and specs that open in place. Illustrative example with fictional data.

Shopper: Someone on a phone checking whether a stand mixer fits under the kitchen cabinets.

What the screen shows: A gallery photo with a coffee mug next to the mixer and the height and depth marked on it, a review summary with the three things buyers mention most, specs in vertically stacked sections that open in place (dimensions open, power, in the box and care closed), and a sticky bar with the price and Add to bag.

Why it works: A photo with a common object answers the size question faster than a spec line. Vertically stacked sections keep every spec in one scroll, while a row of horizontal tabs hides all but one section. Horizontal tabs perform poorly on mobile devices because users accidentally swipe back or forward in their browser when trying to navigate them. The sticky bar keeps the main action in reach while the shopper reads.

Watch for: A sticky bar takes vertical space on a small screen. Keep it to one line of price and one button, and hide it when the keyboard is open.

3. Voltgrid Supply: industrial parts product page, desktop

Voltgrid Supply desktop product page for a stainless hex bolt: a dense spec table, a part number compatibility check with a fits result, unit prices for three quantity breaks, stock by warehouse with a restock date, and a ship-today cutoff, annotated with five numbered callouts
Voltgrid Supply, industrial parts page: specs, fit check, quantity pricing and stock in one view. Illustrative example with fictional data.

Shopper: A maintenance buyer ordering 500 replacement bolts for a production line.

What the screen shows: A dense spec table (thread, length, material, standard, head size), a "Will it fit?" box that takes the buyer's part number and answers "Fits VG-4410 bracket", unit prices for three quantity breaks, stock by warehouse with a restock date for the empty one, and "Ships today if ordered by 4 PM ET".

Why it works: Professional buyers need exact data, not mood photos. The fit check turns a spec comparison into a yes or no, and the quantity breaks show the real unit price for the order size. Stock by warehouse lets the buyer predict delivery before the cart.

Watch for: Do not hide specs behind a "read more" link for this audience. Dense is fine if the table is aligned, labeled with units and readable at 100% zoom.

Product pages on phones follow the same logic with less room. For more single phone screens, see ten mobile app screens explained one by one.

Cart Examples

A good cart shows an honest estimated total and lets the shopper change the order without leaving it. The two carts below do it for a small beauty order and a large piece of furniture.

4. Lumen Skin: beauty cart drawer, Android

Lumen Skin cart drawer on Android in three screens: a foundation with its shade shown and quantity buttons, a shade picker opened in place, then an estimated total with shipping and tax for a ZIP code, a free-shipping progress bar and a save-for-later link, annotated with five numbered callouts
Lumen Skin, cart drawer: change the shade without leaving the cart, and see the estimated total before checkout. Illustrative example with fictional data.

Shopper: Someone checking a foundation shade before checkout.

What the screen shows: The item with its shade name and swatch, minus and plus buttons for quantity, a shade picker that opens inside the drawer, a free-shipping bar ("$8 away from free shipping"), an estimated total with shipping and tax for ZIP 60614, and a Save for later link under each item.

Why it works: Changing the shade in place keeps the shopper in the cart instead of sending them back to the product page. Buttons for quantity are easier to hit than a small text field; Baymard found 95% of sites do not use buttons, or buttons plus a text field, for cart quantity. The estimated total answers "what will I pay" before the checkout asks for anything.

Watch for: A drawer fills up fast. Keep Checkout as the strongest element, and keep the free-shipping bar factual: the amount left, not a pushy message.

5. Hollis Home: furniture cart page, desktop

Hollis Home desktop cart page for an oak dining table: a delivery fee and delivery window for a large item, an optional assembly add-on, return terms including the pickup fee next to the total, and a gift option, annotated with five numbered callouts
Hollis Home, cart for a large item: delivery, assembly and return costs are visible before checkout. Illustrative example with fictional data.

Shopper: Someone buying a 72-inch oak dining table and worried about getting it into the house.

What the screen shows: The table with a large-item delivery line ($149 white-glove delivery, window Dec 3-7, a call two days ahead to set a 4-hour slot), an optional assembly add-on ($79), a gift option in the cart, and return terms next to the total: 30 days, with a $99 pickup fee for large items.

Why it works: Large items carry costs that small items do not, and shoppers find them late. Here the delivery fee, the window and the return fee are visible before checkout, next to the number they change. Baymard found 68% of sites do not let users mark an order as a gift in the cart.

Watch for: Do not show "Free delivery" in the header if large items pay for delivery. The cart is where a hidden fee turns into a lost order.

Checkout and Confirmation Examples

A good checkout asks only for what the order needs and tells the shopper how much is left. The same Baymard benchmark rated 59% of leading US and European desktop sites "mediocre" or worse and only 2% "good". It also found that 48% of sites show a delivery speed instead of a delivery date. The three screens below show the patterns that the benchmark keeps finding missing.

6. Petal & Post: flowers and gifts checkout, mobile

Petal and Post mobile checkout in three screens: guest checkout as the main option with sign-in below, a delivery date picker with the recipient address kept apart from billing and a note on why the recipient phone is asked for, then a gift message with a character count and a hidden-prices note, annotated with five numbered callouts
Petal & Post, gift checkout: guest first, the recipient kept apart from the buyer, and a phone field that explains itself. Illustrative example with fictional data.

Shopper: Someone sending anniversary flowers from a phone, on the way to work.

What the screen shows: Continue as guest as the main button, with sign-in as a quieter link; a delivery date picker; a recipient address kept apart from the billing address; a recipient phone field that says why it is needed ("only for the courier, if no one answers"); and a gift message with a character count and "prices are not printed on the card".

Why it works: A first-time gift buyer does not want an account. Keeping the recipient apart from the buyer stops the common mix-up of shipping to the wrong address. Explaining the phone field answers a privacy doubt on the spot; Baymard found 47% of sites do not explain why a phone number is required.

Watch for: Date pickers on phones need large touch targets. Show the next available date first, and grey out the days the shop cannot deliver.

7. Northline Audio: electronics one-page checkout, desktop

Northline Audio dark one-page desktop checkout: express wallet buttons at the top, an address field with autocomplete suggestions, optional fields marked as optional, an email field with a confirmed check, shipping options with arrival dates and prices, and an order summary column, annotated with five numbered callouts
Northline Audio, one-page checkout: express pay first, arrival dates on every shipping option, and the summary always in view. Illustrative example with fictional data.

Shopper: Someone buying a $1,499 home theater receiver.

What the screen shows: Express wallet buttons at the top, then contact, address and shipping on one page. The address field offers autocomplete suggestions, the optional field says "(optional)", the email field shows a check once it is valid, each shipping option shows an arrival date and a price, and the order summary stays in a fixed column on the right.

Why it works: Express pay skips most of the typing for returning wallet users. Autocomplete cuts keystrokes and address errors. Labeling optional fields stops shoppers from filling in what they could skip; Baymard found 50% of sites do not mark both required and optional fields. Arrival dates on every option answer "when", and the fixed summary answers "for what".

Watch for: Run inline validation after the shopper leaves a field, not while they type. An error that appears mid-word reads like an accusation.

8. Grocer Lane: grocery order confirmation, mobile

Grocer Lane mobile order confirmation in three screens: the delivery slot with an edit cutoff time, substitution choices for each item, then an optional account created from the order with only a password to add, annotated with five numbered callouts
Grocer Lane, order confirmation: the slot, the edit cutoff and substitutions, with the account offer saved for last. Illustrative example with fictional data.

Shopper: Someone who just paid for a weekly grocery order and wants to know what happens if an item is out of stock.

What the screen shows: The delivery slot (Tue, Nov 17, 4-6 PM) with "You can edit until Tue, 10 AM", substitution choices per item (similar, no swap, or call me), and only then an optional account: "Save your details for next time. Add a password."

Why it works: The confirmation is the last screen that can prevent a support ticket. A clear cutoff and substitution choices answer "can I still fix it". Offering the account after payment respects the guest choice and asks for one field only; Baymard found 56% of sites do not save account creation for the confirmation step.

Watch for: Edit windows complicate picking in the store. State the cutoff as a clock time, and send it again in the confirmation email.

What the Eight Screens Have in Common

All eight screens put the answer next to the decision it affects: the delivery date by the button, the full cost by the total, the reason by the field. Four habits repeat across the categories.

  • Dates, not ranges: Fernway, Northline Audio and Grocer Lane show a day and a time. A date is something the shopper can plan around.
  • Costs where they happen: Lumen Skin estimates tax and shipping in the cart, and Hollis Home shows the large-item fees there. Nothing new appears on the last step.
  • Edits without detours: shade, quantity, substitutions and the gift option all change in place.
  • Reasons next to requests: the phone field explains itself, the optional fields say so, and the account offer waits until after payment.

Baymard's survey of more than 1,000 shoppers, reported in the same benchmark article, found that 17% had abandoned an online purchase in the last three months because the checkout was too long or complicated. Each habit above removes a step, a field or a surprise.

How to Review Your Own Product Page, Cart and Checkout

You can run this review in one hour with a product manager, a designer and one person who drives the screen as a shopper. Use a real product from your top sellers and a phone as well as a laptop.

  1. Product page (15 minutes): ask out loud, "Is this the right one for me, and when will I have it?" Point to the exact place on the screen that answers it. If the answer needs a scroll past the reviews or a new tab, write it down.
  2. Cart (15 minutes): ask, "What will I pay in total, and can I still change my mind?" Change the size or shade and the quantity without leaving the cart. Check that tax, delivery and any large-item fee are estimated.
  3. Checkout (20 minutes): ask, "How much is left to do, and is my card safe here?" Count the fields, mark which ones the order does not need, and check that every optional field says so.
  4. Confirmation (10 minutes): ask, "What happens next, and can I still fix it?" Look for a date, an edit cutoff and a way to reach a person.

Write each gap as "screen, question, what is missing". That list is your brief. If the gaps go beyond these screens, read what a full UX audit covers and what it delivers.

Where to Find More Ecommerce UX Examples

Galleries are the fastest way to see many real stores, but they rarely explain why a screen works, so read them with the questions above. The Awwwards e-commerce gallery collects award-judged store sites, and the Dribbble ecommerce UX tag shows concept screens from designers. Treat concept screens as ideas, not as proof that a pattern converts.

Frequently Asked Questions

What is ecommerce UX?

Ecommerce UX is how an online store helps a shopper find a product, decide and pay. In practice it is the product page, the cart, the checkout and the confirmation, plus search and navigation before them.

What makes a good ecommerce checkout?

A good checkout offers guest checkout, asks only for the fields the order needs, labels optional fields, shows delivery dates and the full cost, and keeps the order summary in view. Baymard's 2026 benchmark found most leading sites still miss several of these.

Where can I find more ecommerce UX examples?

Use screen galleries such as Awwwards and Dribbble for volume, and annotated examples like the eight above for the reasoning. Review any example with the one-question-per-screen method before you copy it.

Conclusion

Good ecommerce UX answers the shopper's question on the screen where it comes up: fit and delivery on the product page, the full cost in the cart, the effort and safety in the checkout, and the next step on the confirmation. Use the eight examples and the one-hour review to find where your store makes shoppers search for an answer, and fix those places first. When you are ready to bring in outside help, compare the ecommerce UX teams on our list against the same four questions.

Read more