EN
Marketplace

How Do You Manage Products with Variants on a Marketplace? A Guide to Size, Color, SKU, Barcode and Variant Matching

How do you manage products with variants on a marketplace? What a variant is, SKU and barcode structure, variant matching, variant-level stock tracking and 7 common mistakes, with examples.

Contents 11 sections
  1. What is a variant, and what is a product with variants?
  2. Which attributes should be variants, and which should be separate products?
  3. How is the number of variants calculated, and why does it grow so fast?
  4. How are SKUs and barcodes assigned for products with variants?
  5. How is variant matching done on a marketplace?
  6. Why is stock tracked per variant for products with variants?
  7. How are variant images and price differences managed?
  8. How do you create a product with variants step by step?
  9. The 7 most common mistakes in managing products with variants
  10. How do you manage products with variants with NetKasam?
  11. Frequently Asked Questions About Managing Products with Variants

A business that sells a T-shirt in three colors and four sizes is actually selling not one product but twelve separate products. Each has its own stock, barcode and sometimes price; all are shown on the same product page according to the buyer's choice. When this structure is set up correctly, the buyer finds the size they want right away, stock drops correctly and the order is matched to the right product. When it is set up incorrectly, a sold-out size gets sold, returns increase and products look scattered on the marketplace. The answer to how do you manage products with variants on a marketplace is to set up this structure correctly from the start.

In this guide, we explain managing products with variants step by step: what a variant is, which attributes should be variants and which separate products, how the number of variants is calculated, how SKUs and barcodes are assigned, how variant matching is done with different marketplaces' color and size lists, why stock should be tracked per variant and what the 7 most common mistakes are. The products, codes and stock figures in the examples were chosen only to illustrate the method.

What is a variant, and what is a product with variants?

In short: A variant (variation) is a sub-version of a product distinguished by an attribute such as size, color, dimensions, volume or pattern. A product with variants is a product structure in which these sub-versions are sold not as separate products but as options of a single product.

In a variant structure, there is a parent product (product group, model) and the variants linked to it. The parent product carries the information common to all variants: product name, description, category, brand and general attributes. A variant carries only the information specific to itself: the selected color and size, SKU, barcode, stock quantity and, if needed, price and image. The buyer sees a single product on the product page and picks the variant to buy by choosing a color and size.

This structure has two benefits for the seller. First, all reviews, sales history and views build up on a single product page, which helps the product appear stronger in marketplace searches. Second, stock and order tracking is done at the variant level; you know exactly which size in which color sold. We have separately covered placing products neatly in the catalog under product management in e-commerce and category management.

Which attributes should be variants, and which should be separate products?

In short: Attributes that a buyer would naturally choose on the same product page and that do not change the product itself (size, color, dimensions, volume) become variants. Differences that change the product's model, material or purpose are created as separate products.

A simple test works: "Are the description, attribute list and category of these two options the same?" If yes, it is a variant; if not, it is a separate product. The white and black versions of the same T-shirt are variants; the same brand's T-shirt and sweatshirt are separate products. A cotton T-shirt and a polyester T-shirt should be created as separate products if their descriptions and care instructions differ.

FeatureVariant?Why?
Size (S, M, L, XL; 36, 38, 40)YesSame product, the buyer picks their own size
ColorYesSame product, the image changes
Dimensions and volume (50 ml, 100 ml; 160×220 cm)YesSame product, quantity or size changes; price may differ
Pattern or printUsually yesCreated as a variant as long as the description stays the same
Different model or cutNoDescription, attributes and images are completely different
Different material qualityMostly noShould be a separate product if care and usage information changes
Set or multipack (2-pack, 3-pack)Depends on the caseCheck the marketplace's rules; tracking it as a separate product in stock is safer

Marketplaces have their own rules about which attributes can be variants in each category. In some categories only size and color can be variants, while in others volume or dimensions can also be selected. Checking the category's variant attributes before creating the product saves you the trouble of deleting and recreating it later.

How is the number of variants calculated, and why does it grow so fast?

In short: The number of variants is the product of the number of values for each attribute. 3 colors and 4 sizes make 12 variants; adding one more attribute multiplies the count. That is why every new attribute also multiplies the number of SKUs, barcodes and images to manage.

FormulaFour basic calculations for managing products with variants
  1. Number of variants = Number of values of attribute 1 × Number of values of attribute 2 × …
  2. Total stock of the product = Sum of the stock of all variants
  3. Available stock (per variant) = Physical stock − Stock reserved for pending orders − Buffer stock
  4. Barcodes needed = Number of variants (the parent product is not given a barcode)

Available stock is calculated separately for each variant, and this number is sent to marketplaces.

For an example T-shirt, when color (white, black, navy) and size (S, M, L, XL) are chosen as variants, 3 × 4 = 12 variants are created. Adding two fabric options brings it to 24; adding two sleeve types brings it to 48 variants. A product with 48 variants means 48 SKUs, 48 barcodes and 48 separate stock counts.

ExampleEvery new attribute multiplies the number of variants to manage
  1. Size only (4 sizes)4 variants
  2. Size × color (4 × 3)12 variants
  3. Size × color × fabric (4 × 3 × 2)24 variants
  4. Size × color × fabric × sleeve type (4 × 3 × 2 × 2)48 variants

Prepared with sample values.

The speed at which the number of variants grows leads to two practical decisions. First, combinations that do not sell should not be created; rather than creating a color–size pair that is never produced with "stock 0," not creating it at all keeps the catalog tidy. Second, for products whose variant count grows very large, management becomes easier if one attribute (for example, fabric) is created as a separate product.

How are SKUs and barcodes assigned for products with variants?

In short: The parent product is given a model code, and each variant is given its own SKU, containing this model code and the variant values, and its own barcode. The same barcode is never used for two variants; marketplaces link an order to the right variant through the barcode or SKU.

A good SKU tells you, at a glance, which product and which variant it is. The most common method is to append color and size abbreviations to the end of the model code. This way, the same code appears in the warehouse, on the order list and on the invoice, and confusion decreases. We covered the general rules of code structure in our article what you need to know about SKUs.

LevelExample codeColorSizeBarcodeInventory
Parent product (model)TSH-001——Not assignedSum of the variants
VariantTSH-001-BYZ-SWhiteSIts ownIts own
VariantTSH-001-BYZ-MWhiteMIts ownIts own
VariantTSH-001-SYH-MBlackMIts ownIts own
VariantTSH-001-LCV-XLNavyXLIts ownIts own

The most important rule for barcodes is uniqueness: each variant's barcode must be the same across all sales channels and belong to that variant alone. If you link your barcode to one variant on one marketplace and to a different variant on another channel, stock and order matching breaks down. You can find ways to obtain and create barcodes in our article barcode creation guide.

How is variant matching done on a marketplace?

In short: Variant matching is linking the color and size values you use to their equivalents in each marketplace's own value list. If matching is done correctly once and saved, new products are transferred automatically under the same rule.

Each marketplace has you choose color, size and other variant attributes from its own list. The color you call "Navy" may appear as "Navy" on one marketplace and "Dark Blue" on another; a size may be requested as "XL" on one channel and "XL / 44" on another. Products sent without matching are either rejected or appear under the wrong filter, and the buyer cannot find the product in the color they are looking for.

Your valueMarketplace AMarketplace BYour e-commerce website
NavyNavyDark BlueNavy
WhiteWhiteWhiteWhite
TerracottaOrangeRedTerracotta
XLXLXL / 44XL
StandardOne SizeStandardStandard

The values in the table are examples. Pay attention to three points when matching:

  1. Fix your own value list. If you write the same color sometimes as "Navy" and sometimes as "Nvy," each one needs separate matching. Your internal list should be single and fixed.
  2. Choose the closest equivalent; do not make one up. A color with no exact equivalent in the marketplace's list (such as terracotta) is matched to the closest main color, and the real color name is written in the product name or description.
  3. Check by category. On the same marketplace, shoe sizes and clothing sizes are different lists. Matching is done per category.

The technical side of matching runs through the API the marketplace provides; you can find the details of the concept on the page using APIs in marketplace integration.

Recommended readingHow Do You Sync Inventory Across Multiple Marketplaces? A Guide to Preventing Overselling

Why is stock tracked per variant for products with variants?

In short: Because the buyer purchases a variant, not the product. While total stock shows 120 units, the best-selling size may have dropped to 4 units; stock that is not tracked per variant leads both to the sold-out size going unnoticed and to selling products you do not have.

There are 120 units of the example T-shirt in navy in the warehouse. Because the product list says "120 units in stock," everything looks fine. But when you look at the sizes, the picture is different:

Stock breakdownTotal stock looks sufficient while the best-selling size is about to sell out
  • XL52 units43.3%
  • L38 units31.7%
  • S26 units21.7%
  • M (best seller)4 units3.3%

Prepared with sample values.

If size M sells a few units a day, it will sell out within two days, while XL sits in stock for weeks. Without a per-variant stock report, this difference only surfaces through "out of stock" cancellations. That is why reorder decisions should be based not on the product total but on each variant's sales speed. We explained how to manage sold-out products on a marketplace in our article out-of-stock products.

Key numbersFour numbers from the example T-shirt's variant structure
  • 12variants: 3 colors × 4 sizes
  • 12separate barcodes and SKUs: the parent product is not given a barcode
  • 120units: total stock of the navy color
  • 4units: stock left in size M, the best seller in the same color

Prepared with sample values.

How are variant images and price differences managed?

In short: Variants that change the appearance, such as color, get their own images; variants that do not change the appearance, such as size, share the parent product's images. For variants with different costs (large sizes, large volumes), price is defined separately at the variant level.

When the buyer selects navy, they want to see a photo of the navy product. That is why images are uploaded by color group: all sizes of a color use the same images. Uploading a separate photo for every size is unnecessary work, while not uploading images for colors is a cause of returns. For shooting and editing tips, see the page how to take product photos.

For variants with price differences, there are two approaches: giving all variants the same price, or selling higher-cost variants at a higher price. If you choose the second, you need to define each variant's price separately and check that discounts in campaigns are applied to the variant price. You can check the effect of variant pricing on profitability with the formulas in our article profit margin calculation.

Recommended readingHow Do You Manage Trendyol, Hepsiburada and n11 Orders on One Screen? A Guide to the Order, Stock, Invoice and Shipping Flow

How do you create a product with variants step by step?

In short: First the category's variant attributes are determined, then the parent product and code structure are set up, each variant is given an SKU and barcode, images and prices are added, values are matched to the marketplace lists and stock is entered before the product goes live.

Step by stepSix steps to creating a product with variants correctly on every channel
  1. 01
    Determine the attributesCheck which attributes can be variants in the category.
  2. 02
    Set up the parent productEnter the name, description, category and model code once.
  3. 03
    Create the variantsCreate only the color–size pairs you will actually sell; give each an SKU and barcode.
  4. 04
    Add images and pricesUpload images per color group, and define the price on the variant if it differs.
  5. 05
    Match the valuesLink colors and sizes to each marketplace's list and save the rule.
  6. 06
    Enter stock and publishEnter variant stock, send the product to the channels and check the matching on the first order.

Once the matching rules are saved, step 5 completes itself for subsequent products.

The 7 most common mistakes in managing products with variants

In short: The most common mistakes are creating each variant as a separate product, giving two variants the same barcode, tracking stock as a product total and writing color and size values differently across channels.

  1. Creating each variant as a separate product. Reviews and sales history are split, the buyer does not see the other colors and the catalog gets cluttered.
  2. Giving two variants the same barcode. The order is linked to the wrong variant, the wrong product is shipped and stock is corrupted in both variants at once.
  3. Tracking stock as a product total. The best-selling size sells out while total stock looks sufficient; only cancellations reveal it.
  4. Writing values inconsistently. If "Navy," "Nvy" and "Dark Navy" are used for the same color, filters and matching break down.
  5. Creating combinations that do not sell. Color–size pairs that are never produced appear as "sold out" and create a trust problem for the buyer.
  6. Not uploading images for color variants. The buyer purchases without seeing the selected color; when the product differs from expectations, a return follows.
  7. Deleting and recreating a variant. The deleted variant's sales history and its matching on the marketplace are lost. To stop sales, set the stock to zero or deactivate the variant.

How do you manage products with variants with NetKasam?

In short: In NetKasam, you create your products with unlimited variants, track each variant's stock separately, upload separate images for color groups and send your products to all channels from one place with marketplace integrations.

NetKasam inventory management supports the variant product structure: you can create unlimited variants for a product, track each variant's stock separately and upload different images for different variant groups. The detailed stock movements report shows which variant sold when and through which channel; with branch and warehouse management, you track your stock by warehouse and make transfers.

With marketplace integration, you send your products to marketplaces and gather the resulting orders in a single panel; you can also transfer your products to other sales channels via XML. Bookkeeping and the e-Invoice system are always free; you can find the marketplace integration plans on the pricing page.

Frequently Asked Questions About Managing Products with Variants

What is a variant?

A variant is a sub-version of a product distinguished by a selectable attribute such as size, color, dimensions or volume. For example, a white size M and a black size L of the same T-shirt are two separate variants of the same product.

Are variant and variation the same thing?

Yes. Some marketplaces and e-commerce platforms use the term "variation," others "variant" or "option." They all describe the selectable sub-versions of the same product.

Does every variant need its own barcode?

Yes. Every variant should have its own barcode, because marketplaces link an order to the right variant through the barcode or SKU. The parent product is not given a separate barcode.

How is the number of variants calculated?

The number of values for each variant attribute is multiplied. 3 colors and 4 sizes make 3 × 4 = 12 variants; adding two fabric options brings it to 24 variants.

What is variant matching?

It is linking the color and size values you use to their equivalents in each marketplace's own value list. If matching is not done, the product may be rejected or appear under the wrong filter.

How do I remove a size I don't sell?

Rather than deleting the variant, it is safer to set its stock to zero or deactivate it. A deleted variant's sales history and its matching on the marketplace are lost.

Should a color be a separate product or a variant?

As long as the description, attributes and category stay the same, a color is created as a variant. This way, the reviews and sales history of all colors build up on a single product page.

How is stock tracked for products with variants?

Stock is kept separately for each variant and sent to marketplaces per variant. The product's total stock is only summary information; reorder decisions are made based on each variant's sales speed.

Managing products with variants is work that rewards a structure set up from the start with every order. Today, open your best-selling product and check three things: does every variant have its own barcode, are color and size values written the same on every channel, and is your stock report per variant? If the answer to all three is yes, you are ready to roll the same structure out across your whole catalog.

Bookkeeping Is Now Completely Free

Manage your bookkeeping and e-Invoice operations with NetKasam without paying a thing. Customer and supplier accounts, inventory, collections and more in one panel, completely free.

Start FreeMarketplace Integration

Read similar articles

19 free tools

Commission, shipping, VAT and profit calculations in your browser, no sign-up needed.

All tools