WooCommerce Variable Products: Organizing Sizes, Colors and Stock Before Launch

Use a variable product when customers choose a specific version of the same item, such as a size and colour. Before building the product page, agree which combinations you actually sell, how each is identified, where its stock is counted and what the buyer should see. A list of attribute values is not, by itself, a complete sellable catalogue.

You may already have photographs and a supplier spreadsheet, yet still be unsure whether “navy, medium” is a separate stocked item or simply an option on one shared product. Resolve that question before entering hundreds of records. Otherwise the page can look finished while the choices offered to customers do not match what your business can fulfil.

Start with the combinations you can fulfil

Make a simple working list for one representative product. Write each valid combination on its own line. Include the supplier reference, the approved customer-facing name, the inventory source and any photograph needed to explain the choice. Keep an unchanged copy of the supplier material so later corrections can be traced.

For an illustrative example, two colours and three sizes allow six possible combinations. Your supplier might actually supply only four. Do not treat the mathematical total as permission to offer the other two. Mark whether each missing combination is unavailable permanently, awaiting information or expected later. Those are different business decisions.

This example is a planning exercise, not a report from a client store. The purpose is to give the shop owner and implementer the same definition of “complete” before the product is released.

Attributes describe choices; variations represent the sellable versions

WooCommerce uses attributes to describe options, and variations to define the corresponding product versions. Its official product guide explains that a variation can have its own price, stock and image. Separate the vocabulary in your brief: “Colour” is an attribute, “navy” is a value, and “navy / medium” is a combination to review.

Global attributes can be reused across products; custom attributes belong to an individual product. Prefer a shared vocabulary when several items use the same size or colour system. A one-off dimension or specialist finish may need a product-specific description instead. See WooCommerce’s guide to product categories, tags and attributes for the supported options.

Choose names that help the customer decide

Avoid sending one person “Blue”, another “Navy” and a third a supplier code for the same approved option. Agree the naming convention, size order, units and explanatory text. If a size requires a measurement guide, prepare that information rather than expecting an abbreviation to answer the buyer’s question.

Do not use an attractive image as a substitute for a clear label. Check that the photographed version corresponds to the selected item and that any differences the customer needs to understand are described. A catalogue review should consider the question “What exactly will arrive?” as well as how the page looks.

Decide what stock means for this product

WooCommerce supports shared product-level inventory, separate variation-level inventory and a mixture. The right choice depends on the physical stock pool. Ask whether two different options consume the same item or whether each option is separately counted. Do not assume a shared parent quantity represents the stock of every size and colour.

Consider a shop with separately stocked finished shirts. Its team needs to know which specific size and colour is available, not merely the total number of shirts. By contrast, two purchase options that genuinely draw on the same underlying physical item may need a shared quantity. Have the person responsible for fulfilment confirm the intended behaviour.

Record who updates quantities, which system is authoritative and how exceptions are handled. If an external inventory service is involved, agree its mapping and update process separately. A well-organized WooCommerce product does not automatically prove that an external stock integration is correct.

Build a small sample before the full catalogue

Choose one ordinary product and one awkward example: perhaps an unavailable combination, a different image or an option with distinct fulfilment requirements. Ask the implementer to show the completed sample against the approved list. This is more useful than approving a large batch from a single screenshot.

Does every intended combination exist, and are unintended combinations absent?
Are product identifiers consistent with the approved catalogue?
Does each selectable version show the appropriate information and image?
Does availability agree with the inventory decision?
Can a shopper understand and change the selection on a phone?
Is the chosen version clearly identified after it is added to the basket?

Use an agreed test process for any purchase checks. Do not create real charges, misleading orders or customer messages merely to demonstrate a product page.

When an option is missing, inspect the record before blaming the design

First establish whether the combination exists in the product’s variation list. Adding an attribute value does not automatically create every new combination. WooCommerce’s troubleshooting guidance also identifies missing prices, stock visibility rules and attributes not enabled for variations as possible causes.

Separate “not offered”, “not available” and “not created”. If the business deliberately does not sell a combination, generating it is not a fix. If it should exist, compare the approved list with the saved product data before investigating theme or caching behaviour.

Agree the handover, not just the launch

A catalogue needs an owner after development. Decide who can introduce a new option, who approves its name and image, and who checks availability. Keep a short procedure for adding a new colour or changing a supplier reference so the same questions are not reinvented each time.

If you are preparing data for an import, use the separate WooCommerce CSV preparation checklist. Product planning and file mapping are connected tasks, but a correctly formatted file cannot decide which combinations your business should sell.

Frequently asked questions

Do I need a separate page for every size?

Not necessarily. Start with how customers understand the item and select its versions. A variable product can group related choices; unrelated products should not be combined merely to reduce the number of records.

Should I generate every possible combination?

Only when every combination is genuinely intended. Review the approved list first. More combinations mean more records to verify and maintain, not automatically a better customer experience.

Can a successful import replace a product review?

No. An import result confirms a technical operation, not that the names, images, availability and choices are commercially correct. Review representative products against the agreed catalogue.

Your next step

Prepare one product’s valid combinations, naming rules and inventory responsibility before preparing the entire catalogue. Then review a sample product on desktop and mobile. If you need help defining the structure, explore our WooCommerce store development service or discuss your catalogue and launch requirements with The Web Designer.