Skip to content
Interface language: English
Design / Signal

Product pages: what a customer needs to know before adding an item to the basket

Organise product information, images and selection around real questions about use, contents and limitations.

Article language: English

A woman beside three circular pieces mounted on a supported axle.
In this article

A beautiful lamp stands in the photograph. Beside it are the collection name, three sentences about timeless elegance and an “Add to basket” button. The buyer still does not know whether a light source is included, how much space the base takes or whether the cord reaches the socket. The page has done a decorator's job. The seller's work is still waiting.

A product page helps someone decide about a particular item. It need not persuade everyone. Sometimes its best outcome is a correct recognition that this model does not fit the customer's use. That saves both sides a misunderstanding. Design therefore starts with questions people should not have to answer by guessing, zooming into a photograph or contacting support at night.

First name what is being bought

A collection name helps people remember a product, but rarely explains what it is. “Forma 02” could be a lamp, a planter or a chair range. Place an ordinary description of the type and its most important distinction next to the proper name. A buyer arriving from search should recognise the item without first visiting the category page.

The same applies to what is included. A styled photograph may show two modules, a base and an additional organiser. If the price covers one module, say so at the selection. A tiny asterisk after six paragraphs does not repair the first impression. Give a short answer: what arrives in the parcel, what must be bought separately and what appears in the photograph only to demonstrate use.

Do not try to replace this information with a stock identifier alone. A code identifies an item unambiguously; a name supports a conversation with a person. Both have their place. The customer should be able to copy the code without retyping it, but should not need to understand the manufacturer's internal naming logic to distinguish a shelf from a whole shelving unit.

A principle from service-page structure and evidence (in Polish) helps here: a promise should have a visible scope. In a store that scope includes quantity, equipment and the chosen model. Copying a service page's layout and changing “enquire” to “buy” is not enough.

Customer questions lead to descriptions of features

Before outlining sections, ask for several real questions from conversations, email and store support. Remove customer data while retaining the problem. If people ask whether a lamp fits behind a monitor, they need its dimensions, base and cord routing. Another paragraph about exceptional design does not answer that concern.

Match the questions to material the store can substantiate. Record an owner for each answer: manufacturer, warehouse, catalogue manager or support. Missing information is also a result. It is better to identify a gap before the shoot and design than during approval of a finished page, when each extra photograph delays publication.

Do not use frequency as the only criterion. A rarely asked question about what is included may strongly affect whether a purchase is correct. Conversely, a frequent question does not always need a new block. Sometimes an existing parameter needs an ordinary name or a position closer to the start of selection. Supplement conversations with reviews of specific variants and uses (in Polish), without reducing them to an average star rating.

For a catalogue with different kinds of products, collect questions separately by category. A shared visual grid does not mean identical information needs. A container, lamp and textile can use the same components but have different conditions for assessment. The template should accommodate differences without adding an improvised “other” section to every page.

“180 cm cord” is concrete. A sentence about convenient placement may help explain it, but cannot guarantee a fit in every room. A useful description connects the feature, its meaning and a condition. The buyer can assess their own situation instead of receiving an assurance that the product meets every expectation, including those not yet expressed.

Choose a few purchase-defining features. For a container these might be usable capacity, closure and stackability. For a shelf: dimensions, fixing construction and the manufacturer's load recommendations. The latter must come from the appropriate source. A designer does not establish safe values from a photograph or competitors' product names.

Arrange remaining data so people can return to it. A short description explains use, a specification supplies values and instructions explain operation. Entering the same width manually in three places creates three opportunities for disagreement. A separate product-catalogue content model (in Polish) helps decide which information belongs in fields and which remains edited prose.

The description should not force customers to learn an entire industry's vocabulary. Keep a technical term if needed, then briefly explain its effect. The explanation should be proportionate: nobody needs a lecture on hinge history to buy a box. But the distinction between a removable lid and one that opens on a hinge can change how it fits on a shelf.

The first screen should help people begin choosing

Not every page needs the same order. Before arranging the view, identify the dominant decision in that category: recognising the model, selecting a variant, checking dimensions or understanding the contents. Order the information accordingly. A large image is not automatically a mistake, but it should not cut people off from information needed to understand what it depicts.

Near the price and action, show enough of the selection state. Is the buyer viewing a particular version or just the cheapest option in a product family? Does the displayed availability apply to their variant? Shopify's product-object documentation distinguishes, among other things, minimum and maximum variant prices and product availability. Availability of a product family does not therefore confirm availability of each specific version.

Do not leave people with two contradictory signals. If the price or availability changes when an option is selected, update the information where the decision is made. The product-variant selection guide (in Polish) discusses keeping image, name and status consistent.

Aeneia conceptual photography

On a phone, also check the return journey after scrolling. A customer may read parameters, return to the image and forget which variant was selected. If using a sticky purchase bar, identify the item it acts on. A button suspended over content should not cover information or imply that an unmade choice has already been resolved.

Photographs should answer different questions from text

Photography is strong where a name alone cannot convey meaning: texture, proportion, how parts join or appearance when opened. It should not pretend to be dimensional documentation if perspective distorts scale. When preparing your own product photographs, separate mood from evidence of a particular product feature. The guide to brand photography for a website (in Polish) discusses the roles images can play on a site.

Plan the set before the shoot. Write the question for each frame: what does the whole look like, what is at the back, how does it close, what is inside? This avoids discovering after implementation that you have eight versions of the same elegant view and no photograph of the feature customers ask about most.

If an image shows an optional element, label that relationship beside it. If it shows another colour version, say so. A concept illustration or visualisation of a room should also be recognisable in its role. Presentation can build brand character without persuading someone that the furniture comes with a bay view.

A caption need not repeat alternative text. One explains a relationship visible on the page; the other helps someone who cannot perceive the image. Both depend on the role of the specific photograph. A generic store-name formula does not describe a hinge, while a multi-sentence advert in place of alternative text makes essential information harder to reach.

Show limitations where they matter

“For indoor use” should not live only in the care section if the photograph shows the item on a terrace. A required separately purchased base belongs near the set selection. An installation condition must not appear for the first time after the parcel arrives. Putting a limitation beside the relevant decision is clearer and fairer than a single block of caveats at the end.

An ordinary product does not need an atmosphere of warning. A short sentence is enough if it answers the right question. “The module does not include a lid” says more than “images are illustrative” because it identifies what is in the order. A broad disclaimer passes interpretation to the customer instead of explaining a specific difference.

When confirmed information is missing, hold the promise and obtain data from the product owner. Do not turn a blank field into “fits most models”. That sounds mild, but still makes a compatibility claim. The workshop on writing a service page (in Polish) applies here too: specificity requires material, not just better style.

Separate product features from the store's current service. Dispatch time, delivery methods and collection points may change at a different pace from construction material. Establish owners and data sources in the design. An editor should not have to revise a material description every time the warehouse schedule changes.

Read the page with three different intentions

Return to the lamp and three hypothetical situations. One person knows the model through a recommendation and wants exactly that version. Another seeks light for a small desk. A third is buying a gift and does not know whether the recipient needs to buy anything else. They do not need three pages, but each should find a different, concrete answer on the same page.

The first checks the identifier and variant. The second needs dimensions and a placement example. The third reads the contents and conditions for first use. If the design shows only an atmospheric image, all three must reconstruct missing context. A short product-type description and clearly labelled sections allow people with different prior knowledge to enter the content.

This trial can be done with text alone. Print or display the page without the decorative background and check that each answer exists. If not, the problem is not the button colour. If an answer exists but is hard to find, examine hierarchy and labels. Only then assess whether image and typography reinforce the right information.

Do not add details to personas that you do not know. A hypothetical scenario helps prepare a design; it does not pretend to be customer research. After launch, return to actual support conversations to check which questions remain unanswered. Changes to the page should follow an observed gap rather than a need to rearrange every element for the season.

The same item must exist outside the beautiful view too

A customer may first see the product in search, then on the page. Google describes product structured data that can enrich presentation with price and availability, among other details. This does not promise a particular search-result appearance. Implementation should nevertheless keep information shown to people consistent with information sent to systems.

Check consistency in several states: a single product, a family with variants, unavailability and a price change for a particular version. Another slogan about quality is not needed. A shared definition of the data is. If the product has different names on the page, in the basket and in confirmation, customers must establish for themselves whether they are still buying the same thing.

Retain meaning on a slow connection too. The name, selected option and main information should not disappear because a decorative module did not load in time. During acceptance, view the page on your own phone with a longer name and a missing additional photograph. These are ordinary store conditions, not exotic cases to consider after launch.

The final criterion can be a simple task: identify what you are ordering, for which use, in which version and with what limitations. Then go to the basket and compare the result. This path is part of website acceptance (in Polish). The scope connecting content, screens and implementation can be agreed through the Aeneia Design offer, starting with a real catalogue rather than an empty mockup.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear