Prostor
All articles
19 October 2026

Product page anatomy for D2C brands

What belongs above the fold, which photographs answer the questions a marketplace cannot, and the fields brands consistently forget on their own store.

The decision the page exists to support

A product page is not there to describe a product. It is there so someone can reach one of two conclusions: this suits me, or this is not it. Anything that does not move them towards either takes space from something that does.

So the useful way to review a page is not block by block, but question by question — in the order the questions arrive.

Above the fold: what it is and what it costs

Four things have to fit: a legible photograph, the name, the price and the button. Everything else goes below. Obvious in principle, and regularly untrue in practice, where the top of the page holds a three-line breadcrumb, a promotion banner and a "frequently bought together" strip.

On price: if it varies by size or configuration, show the price for the current selection, not the lowest possible one. A difference that surfaces at checkout is the most expensive kind — the customer has already invested time and now feels handled.

Photography: replacing the hand

The job of e-commerce photography is to compensate for not being able to pick the thing up. That means shots that answer size, material and scale.

A set that works: overall view on a neutral background, the product next to a familiar object for scale, a macro of the texture, a use scene, and the full contents of the box. Five different shots beat fifteen similar ones.

Specifications: where an own store beats the marketplace

This is the clearest advantage of your own site. On a marketplace the field set is fixed for the whole category and you write into someone else's template. On your store you can add the attributes that actually decide your category — and those are usually the ones that close the sale.

Commonly missing: shipping weight, lead time when the item is made to order, compatibility with something widespread, care instructions, where it is made. If you are moving a catalogue across, the practical side is covered in D2C instead of marketplaces.

Description: answering "will this suit me"

The description should not repeat the table. Its job is to narrow the choice: who this is for, in which situations it is good and — more usefully — where it is not. An honest "this is not for you if…" earns more trust than a paragraph of virtues, and it reduces returns.

A quick test: read your description and ask whether it could be moved to a competitor's page unchanged. If it could, it is saying nothing.

Delivery and returns next to the button

Two questions arrive exactly at the moment of decision: when will I get it, and what if it does not fit. The answers belong right there, not in the footer and not on a separate page. One line with the lead time and one with the return terms remove more hesitation than another paragraph about quality.

Six checks on your own page

  • Are photograph, name, price and button all visible without scrolling?
  • Is there a shot that makes the real size obvious?
  • Do your specifications differ from the marketplace template?
  • Does the copy say who the product is not for?
  • Is the delivery time visible before the button is pressed?
  • What does the page do when the item is out of stock?

Each takes a minute to check. In most stores the first two already produce a sprint's worth of work.

Questions

How many photographs does a product page need?

Five to seven, each doing a different job: overall view, scale against a familiar object, material close-up, the product in use, and what is in the box. Ten shots from the same angle do not replace one that shows how big the thing is.

Do we need a description if we already have a spec table?

Yes, but not a retelling of the table. Specifications answer what it is. The description answers whether it suits me. Those are different jobs and one does not cover the other.

What should an out-of-stock page do?

Stay up. The page has already earned its search position, and deleting it throws that away. Keep it, show the status honestly and offer an action: notify me, or here is the closest alternative.

Are three reviews better than none?

Three real ones, yes — and far better than invented ones. If you have none, show a different proof: customer photographs, warranty length, the return terms.

First page of the Prostor project brief template
Resource

Project brief template

The same document we send clients before we start. Seven sections, about twenty minutes to fill in, and it removes half the questions from the first call.

What is inside
  • Company and project
  • The task and what success looks like
  • Who buys
  • What the site needs
  • Timeline, budget, constraints
  • Taste and examples
  • Materials and sign-off
PDF · 3 pages · fill it in by hand or in any editor

Tell us the task in four answers

Answer with the buttons or in your own words — that is enough for us to come to the call with thoughts instead of generic questions.

Ruslan Kochubarov
Ruslan Kochubarov
Founder, art director

Tell us about the task

Book a 30-minute call or leave a request — we reply within 30 minutes during working hours and send a brief and relevant examples.

Book a call

Projects from $3,000 · ongoing support from $1,500/mo

  1. Reply within 30 minutes
  2. A 30-minute call
  3. A scoped estimate