Skip to content
Interface language: English
Design / Signal

Product variants: changing the colour should change more than a circle

Keep variant names, images, availability and basket selections consistent across the purchase journey.

Article language: English

A dark wooden object with a metal hinge and red thread lying across pale textured samples.
In this article

A customer selects a red organiser, sees a picture of a red organiser and adds it to the basket. The basket shows a white one. It could be a small error in passing an identifier. For the buyer it is much bigger: the store has just shown that their selection cannot be trusted.

On a product page (in Polish), a variant is more than a decorative label beside an image. It is a particular item that can be ordered. Sometimes only its colour changes; sometimes dimensions, price, lead time or the contents of a set change too. The interface must show those differences and preserve them through the journey. The circle still needs to be connected to the right order.

Imagine a fictional family of organisers: two sizes, three colours and two lid versions. That is enough to expose the problem. Not every combination has to exist, and some that exist may be temporarily unavailable. Even on paper these are different situations that should not all be handled by one mysterious grey button.

Map the combinations that actually exist

First distinguish option, value and variant. Size can be an option, “wide” a value, and a wide red organiser with a solid lid a variant. These are not three names for the same thing. Shopify describes a variant as a combination of option values and notes that price and inventory may need to be managed for individual variants.

Bring a real table of combinations to the project. Record an identifier, option values and sales status for each. Do not automatically generate the entire product of possible choices if the company does not offer them all. A clickable prototype fed with fictional complete availability hides a problem until the first day the store operates.

Distinguish a combination that does not exist from an item that is out of stock. “We do not make the wide version with a perforated lid” describes a structural limit of the offer. “The wide red version will return after delivery” describes one item's stock status. Both may prevent a purchase, but they lead to different questions and next steps.

Decide what stays common to the family. Body material may be identical while dimensions are not. Put everything in a general description and the customer gets an average of several products that nobody sells. A product catalogue content model (in Polish) helps decide where information belongs and avoid manual copies.

Extras are not always variants. A separately purchased lid can be a separate order line. Engraving or entered text may be a personalisation parameter. Agree this with the people responsible for the catalogue, stock and fulfilment. The screen should not promise logic the store's operations cannot support.

The choice should explain its limits

There are two basic approaches: show all values and explain unavailable ones, or narrow later fields based on earlier choices. The first exposes the whole offer; the second reduces impossible steps. Choose according to the number of options and the condition a customer brings to the category.

If size is usually a hard constraint, put it before colour. Someone buying an item for a particular recess must first find dimensions that fit. The reverse order may encourage a long look at a finish available only in an oversized version. Do not assume this hierarchy without discussing the category.

Give a reason for an unavailable value. “Not made in this size” differs from “sold out”. A crossed-out colour swatch explains neither. If the reason appears only on hover, a touch-screen user gets no answer. Information should be accessible during ordinary phone use.

Do not silently erase an earlier choice. If changing size rules out the selected lid, explain the effect and ask for the missing option. Automatically substituting another version may keep the state formally valid, but the buyer should know the ordered item changed. A default is a design decision, not a neutral blank.

Provide a way back to all possibilities. A customer may decide that colour matters more than the previously selected size. Clearly clearing a choice or changing an earlier option lets them start comparing again without refreshing and risking the whole context.

Two possible ways through one product page

Return to the organiser. The customer selects red, then wide. The wide model comes only with a solid lid. One approach keeps both lids visible and marks the perforated one as not offered in this combination. The buyer can understand the product family and why their intention needs to change.

Another asks for size first, then shows available colours and equipment. A solid lid may be the only possibility, but say so. The absence of a visible control must not mean the contents are unexplained. A summary states that the selected model includes a solid lid and that no second version is offered here.

Either route can be useful. One shows the family's range; the other takes a narrower path. Do not decide solely on click count. See whether a participant can explain the resulting item and change priorities if their preferred combination does not exist. One fewer click does not compensate for buying on a false assumption.

Also test a temporary shortage. If the wide red organiser exists but is sold out, removing red entirely may suggest that the manufacturer never offers it. A visible status makes the situation understandable. The next step depends on what the store really supports: another colour, contact or notification if that feature exists.

Update name, image and terms together

Once selection is complete, show a short summary: wide, red, solid lid. The buyer need not reconstruct three distant controls. This helps especially with similar names or on a phone. It confirms their combined result without replacing the controls.

WooCommerce documentation describes changing price, image and availability after the required variation options are selected. Actual presentation depends partly on the theme. The design therefore needs an acceptance check of consistency, not an assumption that every platform gets it right without agreement and testing.

Aeneia conceptual photography

A photograph may show the exact variant or the family. If only a white version is photographed, do not arbitrarily recolour it with a filter. Establish what the material actually supports. Tell the buyer when an image is representative, and provide the appropriate separate image where construction differs materially.

Protect the transition when the image updates more slowly than the price. Do not show a new name above the old item for a moment without a loading indication. During rapid switching, make sure a delayed response from the previous choice cannot overwrite the current state. Here a microinteraction (in Polish) serves understanding, not animation alone.

Do not automatically scroll the page after every swatch tap. A customer may be comparing colours, and a jumping screen makes that harder. Communicate changes clearly while keeping the action in a stable place. Put any explanation or error near the relevant field rather than outside the visible area.

Colour needs a name and size needs meaning

A swatch speeds browsing but should not be the value's only name. “Brick red” lets someone who perceives colours differently or uses a screen reader confirm the choice. The name should match the catalogue. An inventive collection name such as “sunset over terracotta” can stay, but add an ordinary explanation of the shade.

Clearly distinguish selection, availability and keyboard focus. One thin border should not mean all three. Observe controls in dimmer light, at magnification and under a moving finger. An accessibility check (in Polish) must include an actual selection, not only a static mock-up with one active option.

Describe sizes in a system appropriate to the item. “Large” without a value works only for someone who knows the collection. For physical goods provide a route to dimensions and scale (in Polish). External width does not always answer what fits inside.

Use full names. “Set with raised lid” may be longer than a field designed for “small”. Truncating the end can remove the decisive part. Design using real names and the principles for long interface text (in Polish). Options need not all look like a row of equal capsules.

Order carries meaning too. Arrange sizes logically, colours in an agreed sequence and equipment versions so their relationship is clear. Do not let accidental import order create an apparent recommendation. If one option is recommended, state why and under what conditions.

Specify states the implementer must build

At handoff identify the initial state, partial selection and complete selection. The first says whether anything is selected by default; the second explains what is still required; the third identifies a specific variant. Without all three, the implementer must invent crucial rules from one attractive mock-up where everything is already correct.

Include separate loading and data-fetch error examples. If the store cannot confirm a selected version's price, it should not leave an old price without explanation. Decide whether to retry or refresh. The error must say confirmation is unavailable, not imply the item has definitely left stock.

Identify who supplies and approves data. The photographer can describe the visible finish, the warehouse knows stock, and the catalogue owner links the identifier to the version. The design covers their combined result. A list of colours handed to a designer alone cannot launch accurate multi-variant sales.

Also specify what happens when data changes during an open session. A customer may leave a page open and return after talking to someone else. Before an action, the store should confirm the relevant state on its side. The interface needs a clear response if conditions changed; do not pretend a page opened an hour earlier reserved the item.

Include sample variant identifiers in acceptance. They allow comparison of what is on screen with what reached the basket and subsequent handling. They need not dominate the customer-facing design. They are a tool for confirming that an appealing control passes exactly the version it describes.

Check that the choice survives the rest of the journey

A shared URL should reproduce the specified variant or clearly show that it opens the family without a selection. Agree this during implementation. The URL's appearance is not enough: copy it, open a new session and compare image, name, price and selected options. A link can be part of a conversation among people making a purchase.

For an old link, account for the choice's current validity. A variant can be withdrawn after a catalogue change. The page should explain that rather than silently activate the first available model. Recovering the meaning of the earlier intention matters even if the original purchase is no longer possible. The same variant should remain recognisable in a saved products list (in Polish) after catalogue changes too.

In the basket, show an identifiable version. A general collection name and thumbnail do not establish whether the correct lid was selected. The same applies when returning from the basket. The buyer should inspect the configuration without searching all possibilities again or accidentally adding a second, different item.

When availability changes, retain the earlier values long enough to explain. “Cannot add” should identify which variant became unavailable and what to do next. Do not immediately move the buyer to another colour. A substitute may require a new decision even if both items belong to one warehouse family.

In the final trial, reproduce a sequence: selection from a URL, size change, impossible combination, correction, basket and return. Repeat with touch and keyboard. An end-to-end acceptance check (in Polish) shows whether the variant remains the same item across screens.

Before commissioning design, gather a table of real combinations, sample photographs and information about the stock system. Aeneia Design combines experience design with an agreed store implementation. The discussion about colour controls can then concern a real product, not which shade of grey best hides missing data.

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