Ecommerce

Product Variant

Also called Option, child product, SKU variant

A version of the same product differing by size, colour or another option, usually with its own SKU.

Quick facts: Product Variant

Category
Ecommerce
Also called
Option, child product, SKU variant
Level
Intermediate
Affects
Stock accuracy, feed approval, product rankings, returns
Where to see it
Your platform's product editor, Merchant Center item list, GA4 item variant reporting
In this article4
  1. How product variants work
  2. Why variants matter
  3. Where variants go wrong
  4. How to act on it

How product variants work

Most shop platforms treat a variant as a child of a parent product. The parent holds the name, the description and the shared images. Each child holds the combination a customer actually buys — small in black, a metre length in copper — along with its own code, price, stock level and often its own photograph. WooCommerce calls these variable products, Shopify calls them variants; the idea is the same.

What differs between platforms is what happens to the address. Some keep every combination on a single page and swap the content with a selector. Some give each variant an address of its own. Some do both, appending a parameter when an option is chosen. That one decision drives most of the search and reporting consequences that follow, so it is worth knowing which your shop does before anything else is changed.

Why variants matter

They are where stock and money actually live. Reporting at product level hides that one size sells out constantly while another never moves, that a colour is being discounted into loss, or that returns are concentrated in a single option. Reordering, ad budgets and discounting are all guesswork until the numbers are read variant by variant.

They also decide what shoppers can find. If somebody searches for a particular size or finish and no page of yours mentions it, the shop is invisible for that search even though the item is sitting on the shelf.

Where variants go wrong

Giving every combination its own indexable page is the usual error. The pages differ by a single word, so they compete with each other, split the links between them and read as duplicate content. In most catalogues the right shape is one page per product with the options selectable, a canonical tag pointing at it, and a separate page only where a version has demand of its own.

The second problem is the default. A page that opens on a sold-out or most expensive option loses shoppers who assume the whole product is unavailable or overpriced. The third is disagreement between systems: a feed that submits variants as unrelated products, or analytics that reports only the parent, makes it impossible to join what was advertised with what was actually sold.

How to act on it

Give every variant its own stock keeping unit and use that same code everywhere — website, feed, invoice, courier label, analytics — so one thread follows the item through every system you own. In a product feed, submit each variant as its own item and group them so the platform understands they belong to one product.

On the page itself, show the options without making the shopper hunt for them, mark unavailable combinations rather than hiding them, and update image, price and stock as the selection changes. Then review sales and returns by variant on a regular cycle, because that is where most catalogue decisions are genuinely made. Tidying this up is ordinary, unglamorous ecommerce SEO work, and it usually pays back faster than chasing new keywords.

Do and do not

Do

  • Give every variant its own stock keeping unit
  • Default to an option that is actually in stock
  • Read sales and returns at variant level

Do not

  • Publish a separate indexable page per colour
  • Hide unavailable options instead of marking them
  • Submit variants as unrelated items in a feed

Questions people ask about this

Should each colour have its own page?

Usually not. Colours of the same product are best kept on one page with a selector, because separate pages differ by a word and end up competing with each other in search. The exception is a version people genuinely search for by name, such as a distinctive finish or a special edition, which can justify a page and a description of its own.

How should variants appear in a product feed?

Each variant is submitted as its own item, with its own identifier, price, availability and, where they differ, its own image. They are then grouped so the platform knows they belong to one product and does not treat them as duplicates. Getting the grouping wrong is a common cause of items being disapproved or shown against the wrong search.

Why do my ads say a product is out of stock when it is not?

Availability is usually read at variant level, not product level. If the specific size or colour submitted in the feed has run out, the item stops serving even though the product page still shows plenty of other options in stock. Check the availability field on that exact variant rather than on the parent product.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.