The three terms
These words are used loosely, so it helps to pin them down.
- Product: the item as a shopper thinks of it, such as a cotton T-shirt in a particular style.
- Option: a choice a shopper makes about that product, such as color or size. A product may have one, two or three options.
- Variant: one specific combination of option choices, such as “Blue, Medium.” Each variant is something you can actually pick, pack and ship.
- SKU (stock keeping unit): an internal code that identifies one variant, so you and your tools can refer to it without ambiguity.
If a shirt comes in 3 colors and 4 sizes, there is one product, two options and 12 variants (3 times 4). Each of the 12 normally has its own SKU, its own stock count and sometimes its own price, weight or photo.
Why this structure matters
If you create 12 separate listings instead, shoppers see a cluttered catalog, reviews are split across pages and the same description is repeated many times, which can create duplicate content problems for search. Combining them in one product with options keeps the page tidy, lets reviews collect in one place and makes it easy for shoppers to compare choices.
Behind the scenes, variants are what make stock accurate. If you sell “the shirt” but only track one total, you can oversell Medium while Large sits unsold. Tracking at the variant level lets inventory tracking match reality, which also supports decisions like when to set a reorder point for each size.
When something should be an option, and when not
A good test is: would a shopper regard these as the same thing in a different form? If yes, it is probably a variant. A T-shirt in several sizes and colors fits that. If the items are really different products, such as a T-shirt and a hooded sweatshirt, create separate products, even if they are similar.
Some practical limits:
- Platforms usually restrict the number of options and variants per product, and the limits differ. Check yours before planning a large range.
- Too many options make the page hard to use. If combinations multiply into a long list, consider whether some should be separate products.
- Custom or engraved items often need a text field, not a new variant for every possible entry.
- Add-ons such as gift wrapping may be better handled as a separate product or an option field, depending on your tools.
Naming options consistently
Use the same option names and values everywhere: “Color” and “Size,” not “Color” on one product and “Shade” on another. Keep value names consistent too, so “Navy” is always “Navy.” This matters for filters, since inconsistent values produce confusing filter lists, and it matters for clean reports. Using a fixed vocabulary also aligns with how you name products in titles.
Show the shopper what is available. Mark out-of-stock combinations clearly, so they do not select something and find it unavailable only at the last step. Display swatches for colors where possible, and let the product image change when a color is chosen, so the picture matches the selection. Each color should have its own set of photos if it looks different.
Building a SKU system
SKUs do not have to be clever, but they should be consistent and unique. A readable code often combines a few parts:
Product code + option codes
For example, using made-up codes: a crew neck T-shirt might be “TSH,” the color blue “BLU” and size medium “M,” giving TSH-BLU-M. Large would be TSH-BLU-L, and the gray version TSH-GRY-M.
Some guidelines:
- One SKU for one variant. Never reuse a code for a different item, even after you stop selling something.
- Keep them short and readable. People will type them, read them aloud and see them on packing lists.
- Use letters and numbers, with hyphens as separators. Avoid spaces and special characters, which can cause errors in spreadsheets and imports.
- Avoid ambiguous characters. The letter O and the number 0, or the letter I and the number 1, are easily confused.
- Do not put changing information inside the code. A price or a supplier name might change; the SKU should not.
- Keep a master list. Record what each code stands for, so you do not have to guess later.
Your SKUs are internal. They are different from barcodes or manufacturer part numbers, though you may store those alongside them. If you resell goods from a supplier, keep the supplier’s code in a separate field and use your own SKU for your records, so that a change on their side does not disrupt your catalog. If you sell on other channels, a single consistent SKU across them makes it much easier to keep stock in sync.
Stock, price and weight at the variant level
Each variant can carry its own details:
- Stock quantity. Needed to avoid selling what you do not have.
- Price. Some variants cost more, such as a larger size. If prices differ, make that visible on the page. Note that shoppers dislike discovering costs late, a point covered under unexpected fees.
- Weight and dimensions. These can affect shipping rates.
- Cost. Recording what each variant costs you helps you understand your profit margin.
- Images. A photo for each color helps avoid mismatched expectations.
Fill in these fields carefully when you create variants. Mistakes tend to spread: a wrong weight can mean wrong shipping charges on every order of that variant.
Maintenance and cleanup
Review variants periodically. Slow sellers, like a rarely chosen size or color, may be tying up money as dead stock; look at whether to discount, bundle or stop reordering them. When you discontinue a variant, mark it unavailable instead of reusing its code. Before major changes, such as a platform migration, export your product and SKU list and check that codes stay unique, since this data is hard to rebuild.
A tidy structure takes some time at the start, but it pays back through fewer picking errors, cleaner stock numbers and a product page that is easier for shoppers to use.