A product variant is a distinct version of an item that needs its own price, stock quantity, or ordering identity. A red shirt in medium and a red shirt in large may share a product family, but each size-and-colour combination can require a separate SKU and inventory count.
Clear variant records help staff order, pick, sell, and count the exact item. They also make sales data useful: total shirt sales do not show whether medium blue or large red is running out.
Product, option, variant, and SKU
- Product: the item or product family, such as “Classic T-shirt.”
- Option: a characteristic customers can choose, such as size or colour.
- Variant: one specific combination, such as “Classic T-shirt / Medium / Blue.”
- SKU: an internal code used to identify a particular product or variant.
- Barcode: a machine-readable symbol that may encode or reference a product identifier.
A product can have one option or several. Not every option combination needs to be stocked. If the large-red combination is not sold, avoid creating it as a sellable variant unless it has a valid price and stock process.
Create useful SKU rules
A SKU should be unique, stable, and easy for staff to distinguish. A simple pattern might encode product family, size, and colour: TS-01-M-BLU. Keep a short legend and avoid changing codes whenever a description or category changes.
Do not overload the code with details that can change often, such as supplier name, current price, or storage shelf. Those belong in separate fields. If a product changes materially, decide whether it is a new item or a revised description before reusing an identifier.
| Record | Example | Why it matters |
|---|---|---|
| Product family | Classic T-shirt | Groups related variants |
| Variant attributes | Medium, blue | Makes the exact choice visible |
| SKU | TS-01-M-BLU | Supports picking and reconciliation |
| Unit | Each | Prevents pack-versus-piece confusion |
| Cost and selling price | Current approved amount | Supports margin calculations |
| Barcode reference | Supplier or internal code | Enables scan-and-check workflows |
Keep categories simple and consistent
Categories help organize a catalog and support browsing or reporting. Start with a manageable structure based on how staff and customers search. Use consistent spelling, singular or plural conventions, and clear parent-child levels.
Do not create a new category for every attribute. Sizes and colours are usually better stored as variant options, while the category describes the product type. Review duplicates such as “Trousers,” “Pants,” and “Bottoms” before they fragment reports.
Review a new product before publishing
Test one product with several variants from catalog creation through receiving, sale, return, and stock count. Confirm that every step records the same identifier, unit, and variant description. Ask someone who did not create the catalog to find a specific size or colour using the code and the customer-facing name.
Check that the product page displays the options clearly, that unavailable variants are handled honestly, and that the sales report can distinguish them. If the test exposes duplicate codes or confusing labels, correct the catalog before adding the rest of the range.
A small review at the start prevents cleanup across hundreds of products later. Revisit the standard when new product types, suppliers, or pack units are introduced.
Set replenishment triggers by variant
Use each variant's own sales history and supplier lead time when deciding when to reorder. A basic starting point is average daily demand multiplied by lead-time days, plus a buffer for uncertainty. For example, a variant selling about two units a day with a ten-day replenishment lead time and a five-unit buffer would have a starting reorder point of 25 units. This is a planning signal, not a guarantee: check seasonality, supplier reliability, cash available, and storage capacity before ordering.
Review the calculation after promotions, stockouts, or supplier changes. A product family total can hide one variant running out while another accumulates, so keep the trigger at the same level as the quantity record. If demand is irregular, use a longer observation period and write down why the buffer was chosen.
Common product variant questions
Does every option need its own stock count?
Only when the versions are distinct sellable items or need separate stock, price, or ordering. If a choice does not change the physical or commercial item, it may not need a separate variant.
Is a SKU the same as a barcode?
No. A SKU is an internal identifier. A barcode is a machine-readable label that may carry or reference an identifier. Keep the internal product record even when a supplier provides a barcode.
Should product size be a category?
Usually not. Categories describe the type of product; size and colour are attributes or variants. Keep these fields consistent so reports and stock checks remain meaningful.
For an ecommerce catalog, use names customers understand, write specific descriptions, and assign a product to only the most useful categories for discovery. Verify that category pages do not imply availability for items that are out of stock.
Make stock units explicit
A carton may contain 12 bottles, while suppliers quote a case and customers buy one bottle. Record the purchase unit, stock unit, and conversion rule so that receiving, selling, and counting use the same basis. If units cannot be converted automatically in your process, document the conversion and train the people who handle stock.
When stock is received, counted, sold, returned, or adjusted, use the exact variant and unit. If a return is damaged, keep it separate from sellable stock until it has been checked. Do not combine different versions to make the parent product total look correct.
Example: a small apparel catalog
Imagine a jacket in two colours and three sizes. The six combinations are not interchangeable if each has a separate price, stock quantity, or barcode. Use one product family and create only the combinations you actually offer. Give each stocked combination a stable identifier, for example JK-01-BLK-M for black, medium, if the pattern is easy for staff to read.
On a physical count sheet, display the full description beside the code. Ask the counter to scan or read the code, check the colour and size on the item, and record the count in the stated unit. A code alone can be mistyped; a description alone can be ambiguous. Using both is a simple cross-check.
Before importing an existing catalog, keep a backup of the source file. Normalize spelling and units, identify duplicate codes, and map old codes to new ones in a separate table. Test a small sample first and verify that sales and stock history still point to the intended variant.
Audit a variant catalog
- Export the product list and remove duplicate codes.
- Confirm each variant has a distinct identifier where separate counts are needed.
- Compare sample records with products physically on shelves.
- Verify units and pack conversions with a supplier invoice.
- Check prices, tax settings, and barcode scans.
- Confirm that sales, receipts, and replenishment reports identify the correct variant.
- Archive discontinued items only after checking open orders and stock history.
Reconcile differences by finding the transaction or count that caused them. Avoid overwriting the quantity without a traceable explanation.
Keep the catalog maintainable
Assign one person to approve new categories, product codes, and variant attributes. Publish a short naming standard with examples so different staff members do not create “Navy,” “navy blue,” and “blue navy” as separate values. Review the catalog for duplicates and unused options at a regular interval.
If a supplier changes a product code, retain the old code as a searchable reference where your system permits it. Keep the supplier code and your internal SKU in separate fields. This helps match invoices and barcode labels without making the internal code dependent on the supplier’s naming convention.
Use permissions and review for price or stock changes where appropriate. A small catalog should still have a correction path so one accidental edit does not silently change every variant’s price or quantity.
Common variant mistakes
- Reusing one SKU for several colours or sizes.
- Creating every theoretical combination, including versions never sold.
- Putting size and colour only in free-text descriptions.
- Using a barcode as the only internal product identity.
- Mixing packs, cases, and individual units.
- Creating categories that duplicate product attributes.
- Renaming or reusing codes while open orders still reference them.
Better variant records improve stock decisions and product pricing. Continue with slow-moving inventory analysis, pricing for profitability, or a clear product categorization structure. If point-of-sale transactions update your stock, define the movement rules in this POS and inventory integration guide.