The question "How many of this model do we have?" doesn't have a single answer in a textile business. The right question is: how many do we have in each color and size?
Because customers buy a specific variant, not just the model. You might have fifty shirts, but if the requested size is out of stock, the sale won't happen.
In this article, we covered how to set up the variant structure, barcode and channel mapping, and variant-based reporting.
Table of Contents
What is a variant and what is it not?
A variant represents options derived from the same base product that are stocked separately. Attributes such as color, size, volume, and material generate variants.
A variant is not a different product. The same model, price, and supplier apply; only one attribute changes.
This distinction is important: creating every variant as a separate product card makes model-based reporting impossible. You cannot answer the question "How much did we sell of this model in total?"
The correct structure is to keep multiple variants under a single master product. This way, both totals and details are visible.
Which sectors require it?
Apparel and footwear are the most well-known examples; color and size combinations generate dozens of variants.
In furniture, fabric and color options create variants. In home appliances, capacity and color; in cosmetics, volume and tone are determining factors.
In building materials, dimension variants are common. Different lengths of the same profile constitute separate stock items.
The common point is this: the customer wants a specific variant and will not accept an alternative. In this case, variant tracking is mandatory.
Setting up the variant structure
The first step is to define variant attributes. Lists like color sets and size sets are created in advance and used commonly across all products.
This consistency is critical. When "Navy Blue", "Navy", and "Dark Blue" are entered as separate values, reports get fragmented. We detailed definition discipline in the color, size, and variant definitions article.
The second step is to create the variant matrix. The master product is opened, which colors and sizes will be produced are selected, and combinations are generated.
You don't need to open all possible combinations. Opening only the variants that actually exist keeps your lists clean.
Barcode and label layout
Every variant must have its own barcode. Using a single barcode at the model level eliminates variant distinction at checkout and during inventory counts.
If the labels coming from the supplier are not sufficient, you need to print your own labels. This is a common requirement especially for imported products.
We covered the details of barcode structure in the barcode and multi-barcode management article.
Variant differentiation cannot be done visually during counting; scanning is mandatory. We explained the inventory count procedure in the warehouse count article.
Channel mapping
On marketplaces, variants are usually listed under a single product page. However, stock is reported separately for each variant.
Mapping must be established at the variant level. When mapped at the model level, an out-of-stock size will still appear available for purchase, generating cancellations.
We explained the mapping sequence and its necessity in the product matching article.
Sync frequency is also more critical for products with variants; when only a single size is left, a delay directly turns into overselling. You can check out the marketplace stock sync article.
Variant-based reporting
The biggest benefit of the variant structure is on the reporting side. It becomes visible which color is selling out fast and which size is lingering in stock.
This information directly impacts purchasing decisions. Size distribution for the next order is adjusted based on past sales; end-of-season discount pressure decreases.
Dead stock analysis is also meaningful at the variant level. The model might have sold well, but a specific variant hasn't moved at all; check out the stock turnover rate article.
Variant cards and reports are maintained in the inventory module; sales and e-commerce read the same data. For manufacturing businesses, variants are also reflected in the bill of materials; you can review the bill of materials (BOM) article.
Variant-based purchasing
The most tangible benefit of variant tracking emerges on the purchasing side. How many items of which size to order is based on data, not guesswork.
The variant-based sales distribution of the previous season determines the size breakdown of the new order. Ordering with a standard distribution leads to the same sizes remaining unsold every season.
Regional differences also become visible. The size distribution of the same product can vary from city to city; store-based distribution is made according to this data.
On the color side, fashion trends are tracked. How quickly a color sells out fuels the decision for the next collection.
For this analysis, sales reports must be read in variant breakdown; you can check out the sales reports article.
End-of-season management
For products with variants, the end of the season is the period when value loss is highest. Remaining variants are usually the least demanded combinations.
The first way to reduce this loss is early intervention. Applying discounts without waiting when the sales velocity of a specific variant drops is less costly than bulk discounting at the end of the season.
The second way is inter-store transfers. A size left unsold in one store might be in demand at another; check out the transfer slip article.
The third way is changing channels. Variants that don't sell in-store can reach a broader audience on the online channel.
All these decisions rely on variant-based turnover rate data; we covered the calculation in the stock turnover rate article.
Frequently asked questions
Can variants have different prices?
Yes. Larger sizes or special colors can be priced differently; check out the price list management article.
How many variant attributes can be used?
Generally, two attributes are sufficient. Three or more make the number of combinations unmanageable.
Can variants be added later?
Yes, a new color or size can be defined later. Past transactions are not affected.
Does it work in the same system with non-variant products?
Yes. Variants are an optional structure on the card; they do not need to be used for every product.
When the variant structure is established correctly, warehouse, sales, and purchasing all speak at the same level of detail. When set up incorrectly, every report has to be re-interpreted.
When setting up the variant structure, the most critical decision is which attributes will be considered variants. This decision is one of the hardest definitions to change later.
Limiting it to two attributes is the right choice in most sectors. When a third dimension is added, the number of combinations multiplies, making card management difficult.
Standardize value sets from the beginning as well. Defining color and size lists commonly ensures that all future reports will be consistent.
By consulting with the EQLEM team, you can plan your variant structure and channel mapping.