Skip to content

Ecommerce web design: product pages, catalogs and checkout that sell

Better Design

Direct answer

Ecommerce web design arranges three surfaces around one decision: a catalog that moves a visitor from whether to buy to which one, a product page that answers their objections, and a checkout that adds no friction.

A hand-drawn browser window with Ecommerce web design written in it and a short list of what it does.

Ecommerce web design: what to know

Each rule is listed with its source at the end of this page, read on November 12, 2026.

  • A product page should answer four questions in order: is this for me, will it work, can I trust it, and what happens if it does not work.
  • On every screen of a product page, only the product image, the price and the primary button should dominate when you squint at it.
  • Give the product image roughly 40% of the hero, and make the price the largest number on the page, one eye-jump from the button.
  • Put the guarantee, returns and warranty where the buyer decides, not only in the footer.
  • Grid density signals price: tighten the grid for a value offer and open it for a premium one.
  • Give each item in a catalog grid its own border or filled background, so the eye stays on one product long enough to see what is specific about it.
  • Lay out browsing sets horizontally and known-item results vertically.
  • Show the total item count above and below a list, give every filter option a checkbox, and keep a sale filter in the main filter set.
  • Prefer a load-more control over numbered pages or endless scroll, and return the visitor to where they left when they come back from a product.
  • Show a rating average together with its count, and keep critical reviews visible.
  • Show shipping, tax and every fee in the cart, before checkout starts.
  • Make guest checkout the first option, with the same weight as signing in, and use the word guest.

The three surfaces of an ecommerce site

Catalog
Its job

Move the visitor from whether to buy to which one

Rule that matters most

Match grid density to the price position

Product page
Its job

Answer the buyer's objections

Rule that matters most

Product image, price and button dominate every screen

Cart and checkout
Its job

Keep the motivated buyer moving

Rule that matters most

Show the full cost before checkout starts

Reviews
Its job

Make the positive reviews credible

Rule that matters most

Show the average with its count, and keep critical reviews visible

Filters
Its job

Let a visitor narrow instead of scroll

Rule that matters most

A checkbox on every option and a sale filter in the main set

Put Ecommerce web design into practice

  • Decide the price position first: value or premium sets the grid density.
  • Build the product page around the four buyer questions, in order.
  • Squint-test each screen: only the product image, the price and the button should stand out.
  • Build checkout with the full cost in the cart and guest checkout first.
  • Screenshot the rendered pages at desktop and mobile widths before launch.

Ecommerce web design in four steps

The four steps, in the order you take them.

A hand-drawn four-step path for Ecommerce web design: Set the price position, Design the catalog grid, Answer objections on the product page, Remove friction from checkout.
  1. Step 1: Set the price position
  2. Step 2: Design the catalog grid
  3. Step 3: Answer objections on the product page
  4. Step 4: Remove friction from checkout

Caveats to keep in mind

  • A discount brand in a spacious grid argues against its own positioning.
  • A section that answers none of the four buyer questions is filler; cut it or move it below the decision point.
  • Flat design systems give no hierarchy for free; reserve one emphasized surface per screen for the buy box.
  • Code review alone passes pages that render flat, so check the rendered page.

Steal this workflow

Run this guide in your own assistant. The prompt carries the guide link and the workflow summary, so the assistant can adapt it to your project.

Read the guide "Ecommerce web design: product pages, catalogs and checkout that sell" at https://better-design.com/blog/ecommerce-web-design and help me apply it to my project.

Ecommerce web design arranges three surfaces around one decision: a catalog that moves a visitor from whether to buy to which one, a product page that answers their objections, and a checkout that adds no friction.

Start by asking what I am building and which tools I use. Then walk me through the workflow step by step, adapted to my answers.

Claude and ChatGPT open with the prompt filled in. Gemini copies the prompt to your clipboard first, so paste it when the app opens.

Questions

What makes a good ecommerce product page?

It answers four questions in order (is this for me, will it work, can I trust it, what if it does not work), and on every screen only the product image, the price and the main button dominate.

How should an ecommerce catalog be laid out?

Match grid density to the price position, give each product its own border or filled background, run browsing sets horizontally and known-item results vertically, and show the item count above and below the list.

Can a coding agent build an ecommerce site that follows these rules?

Yes. Put these rules in the agent's instructions before it builds, then ask it to check the rendered screen against each one.

What do the best ecommerce websites get right?

They give each surface one job: a catalog that moves the visitor from whether to buy to which one, a product page that answers the buyer's objections, and a checkout that shows the full cost and puts guest checkout first.

How should ecommerce sites lay out their catalog?

Match grid density to the price position, give each product its own border or filled background, run browsing sets horizontally and known-item results vertically, and show the item count above and below the list.

Where these rules come from

Each fact comes from Better Design's commerce guidance, the same guidance its MCP server gives coding agents, read on November 12, 2026.

Build the interface in your own code instead

A coding agent such as Claude Code, Cursor or Codex can build these screens in your own code. Better Design gives that agent a design system, interface principles and review rules, so the result follows rules like these and looks designed.