Skip to content
Interface language: English
Design / Signal

Product comparison: first choose what is worth comparing

Help customers compare the right variants, understand prices and missing values, and change their selection.

Article language: English

In a garden at night, a woman examines an illuminated white petal beside a sleeping cat.
In this article

A customer chooses three table lamps. The first costs 280 zł, the second 390 zł and the third 460 zł. The difference looks clear until the customer notices that the last one is labelled “set of two”. All three prices sit neatly in one row of the comparison table. What is being compared has somehow been lost.

This is a hypothetical example, but it shows the order of the work. Before drawing columns, decide what goes into them. A lamp model, a variant with a particular cable, one product or a package? Each answer can be right. Mixing the answers in one unexplained row creates a carefully designed misunderstanding.

A comparison should help someone decide between a few selected items on a particular difference. It does not need to contain the whole catalogue. If a customer still has to open three product pages after ten minutes to establish what they are actually buying, a shared frame has helped little.

The set begins before the comparison view

On a product list, “Compare” can mean two things: add an item to a set or open the view already prepared. Separate these actions. After a lamp is selected, show that it has joined the set and allow it to be removed in the same place. A separate “Compare 3 lamps” button leads onward. The count shows the effect of the choices before the user changes screens.

A selected item should remain recognisable after changing the sort order or moving to the next results page. If the set will be cleared, explain that before it is lost. Also show a summary with model names so the customer does not have to reconstruct the choices from memory.

Decide whether the comparison contains the model or the selected variant. A lampshade colour may change no important parameter, while arm length may. If the customer chose the version with a shorter arm, the comparison heading should name it. Automatically returning to the catalogue's first variant swaps the subject of the decision.

If a variant can be changed within the comparison, refresh the entire affected column. A longer arm may change dimensions, price and availability together. Do not leave new pictures beside old specifications. Mark the column while fetching data and keep the other models readable. After an error, retain the previously confirmed variant and explain that the change failed, rather than presenting a random mixture of two versions.

Some items cannot be usefully compared in the same fields. A table lamp and a replacement shade share a colour but answer different needs. Instead of allowing any choice and displaying mostly empty cells, define comparison groups. For an incompatible item explain why: “This shade is a replacement part. This comparison is for complete lamps.”

Choose the item limit for the view and task, then test it in a prototype. When the limit is reached, show the selected products and a way to replace one. A greyed-out “Compare” control alone leaves a puzzle: is there no space, an error or an unavailable offer? The customer came to choose a lamp, not an escape room.

A set of candidates can be prepared from your own saved product list. A separate article discusses designing a list for later (in Polish) (in Polish). Keep the functions distinct. A “save for later” list may contain a lamp, a bookcase and a gift for a colleague. The comparison action should include only compatible items and leave the rest in place.

Returning to the catalogue should restore the place where the customer added models and the current selection. Separate removing a column from emptying the whole set. After a longer break, fetch current data again but preserve the identity of the previously selected items. If one can no longer be found, name it and allow it to be removed or replaced. The other two lamps need not disappear with it.

The hardest row is not always the longest

Return to the three lamps. For a meaningful comparison, establish the price basis. You can show the offered package price and the number of items it contains, while clearly distinguishing any per-item price. In our example, a set of two lamps at 460 zł works out at 230 zł each. This is our calculation using hypothetical data, not a real offer.

That figure does not mean the shop sells one lamp for 230 zł. If the minimum purchase is two, the customer must still see 460 zł as the cost of the set. Otherwise the comparison rewards the most attractive arithmetic and hides the order condition. The chosen price basis should be consistent across the row and explained beside it.

Dimensions present a similar problem. Product height and box height cannot share a row labelled “Height”. Cable length in metres can be converted to centimetres, but a folded dimension does not become the dimension of the unfolded product through a change of unit. Name the characteristic first, then standardise its notation.

A working description of each field helps: what it concerns, its unit and when it applies. The person responsible for the catalogue confirms its meaning. A designer should not guess whether “52” is height with the shade, without it or a distance recommended by the photographer. The product catalogue content model (in Polish) (article in Polish) develops this work.

Distinguish missing data, absence of a feature and non-applicability. “Not provided” for cable length describes an incomplete description. “No cable” describes the lamp's construction. “Not applicable” might fit a cable parameter for a battery-only model, if that is the product offered. One dash standing for all three does not help someone decide.

Agree on precision too. When one description says 51.8 cm and another 52 cm, rounding may conceal a difference that matters in a tight recess. Values may look equal only after a particular rule has been applied. If the shop does not know the dimensional tolerance, do not add an assurance that the product will definitely fit. Show the precision available and explain how the customer can confirm the fit before ordering.

Aeneia conceptual photography

If a missing value is necessary for a correct purchase, show how to establish it. That might be a verified technical sheet or a question containing the model and parameter. Do not fill the cell with a guess from a photograph. For fit in an interior, showing product dimensions and scale (in Polish) (article in Polish) remains useful; equal numbers in a table do not replace information about where measurements were taken.

Aeneia Design

If a comparison is to help customers choose between specific models, Aeneia Design can develop its structure, views and presentation of specifications. The starting point is the purchase decision and confirmed catalogue data. Design a comparison of specific models

The customer should know which lamp a number belongs to

In a long comparison, a user reads one parameter and checks another many rows below. The model name must remain easy to find. In research described by Baymard, headings disappearing during scrolling made it harder to assign values to products; the authors identify keeping headings visible as a way to preserve that context. This is a specific observation from comparison-view research, published in 2022, not a test of your shop.

Test the model name and parameter name together in the prototype. A visible column heading helps less if sideways scrolling loses whether the customer is looking at lamp weight or cable length. On a phone, you can limit the number of visible columns or design scrolling that retains product identification. The behaviour should be clear without instructions buried in the footer.

A fixed service-package comparison provides some useful solutions, described in comparison tables for services on a phone (in Polish) (article in Polish). Here, however, the set of columns can change. A user may remove the middle model, add a fourth or return from elsewhere in the catalogue. Identification must still work in each state.

Not every specification needs the same width of explanation. Beside a simple weight there might be mounting instructions with two conditions. A shortened description should expand without losing the model and row. Name the part shown in a detail photograph. Enlarging a picture alone does not answer whether a bracket is included or shown only as an example of use.

Headings also need meaning in the code. MDN describes the scope attribute, which associates a header cell with the relevant row or column. It does not change appearance but carries semantic information. This is a narrow property of an HTML table header, not a promise that the entire comparison is accessible. Making names bold does not establish these relationships.

When a column is removed, plan where focus, the active position in the interface, moves. Someone using a keyboard should not have to return to the top of the page after each removal. In a two-model view, removing one may leave the other's specifications beside a button for adding another. There is no need to throw the customer straight back to the results list and erase their work.

Show the difference without inventing a winner

A “Show differences only” switch can shorten a long comparison, but requires agreement on what counts as equal. “2 m” and “200 cm” can mean the same length. “Warm white” and “white, warm” may be different labels for one confirmed attribute. Conversely, the same word “cotton” does not establish whether it describes the entire product or only the cover.

Organise the data first, then detect differences. A rule based only on comparing text may highlight a changed abbreviation while missing a change in meaning. Have the person responsible for the product approve value normalisation rather than accepting a long automatically found list of similarities.

A missing value should not disappear merely because the remaining columns contain the same number. If two lamps have a two-metre cable and information is missing for the third, the row still contains an unresolved difference. Hiding it would suggest more certainty than the catalogue provides.

A larger number is not always better. A heavier base may be desirable on a table but less convenient when moved often. A longer arm may help on a large desk and get in the way on a narrow shelf. Instead of automatically colouring the highest result green, show the value and what the parameter means. The final preference belongs to the person choosing.

Treat customer ratings in the same spirit. An average from a few comments on a different variant is not an equivalent technical measurement of a lamp. If you include it, add the number of reviews and explain which versions they cover. We discuss the context around product stars (in Polish) separately (article in Polish): user experience may help a choice, but should not masquerade as a laboratory measurement.

What to check with three real product pages

Before implementation, choose a set from the catalogue that is awkward for the design: a similar product sold in a package, a version with a missing parameter and a model with an unusual variant. Someone familiar with the offer prepares verified data and task conditions; a test participant receives a buying goal. For example, choose one lamp that fits on a shelf of a stated depth and has a cable reaching a specified socket.

Observe where the answer comes from. If the participant chooses on per-item price, check whether they understand the package size. If they reject a model with a dash, ask after the task how they interpreted the symbol. If they open a product page to identify the variant, check which information was missing from the heading. A correct answer alone does not show whether it came from understanding or a lucky guess.

Then change one product and repeat the key sequence: remove a model, return to the results, add a replacement. A comparison should support a change of mind. A design that works only with three carefully selected demonstration pages is a slideshow with buttons.

This work can be combined with website and interface design at Aeneia Design. The result should let a customer recognise what is compared, understand a blank and change the set. If they choose a more expensive lamp because it fits the shelf better, the comparison has done its job. A choice suited to their conditions matters more than an automatic medal for one column.

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