In sectors like textiles and footwear, a product is not a single record. If the same model is sold in five colors and six sizes, there are thirty different sellable units.
Each of these thirty units holds separate stock, carries a distinct barcode, and is ordered separately. When the structure is set up incorrectly, stock data becomes unreliable from the start.
In this article, we explained the variant structure, color and size sets, matrix configuration, barcode generation, and channel mapping.
Table of Contents
What is a variant?
A variant is a sellable version of the same product that differs based on specific attributes. Color and size are the most common variant dimensions.
Each variant has its own stock balance; the inventory of the red and blue products must be kept separately.
In contrast, the price, description, and images are usually shared. This sharing reduces the management load.
The correct setup is to define the shared information once and keep only the differences on a variant basis.
Opening each variant as an independent product, on the other hand, creates an unmanageable catalog.
Color and size sets
Color and size values should be kept as defined sets rather than free text.
When free text is used, the same color is recorded with different spellings, and filtering fails.
Size sets vary according to the product group; clothing and footwear do not use the same set.
Therefore, multiple size sets must be definable, and the one suitable for the product must be selected.
It is also important that the sets are ordered; sizes should appear in logical order, not alphabetical.
Variant matrix
When color and size sets are selected, the system generates a matrix containing all combinations.
In this matrix, each cell is a variant and carries its own stock balance. It also visually shows the stock status at a glance.
It is not necessary to generate all combinations; some color-size combinations may never be produced.
Deactivating unused cells keeps lists clean and reduces the risk of erroneous orders.
The matrix view can also be used during order entry, making row-by-row entry unnecessary.
Coding structure
Variant codes must be generated by deriving from the main product code. This ensures both readability and consistency.
The common structure is to add color and size suffixes to the main code. Code length should be kept reasonable.
Color and size abbreviations must be standard; using different abbreviations for different products creates confusion.
Automatic code generation eliminates errors caused by manual entry.
It is difficult to change the code afterwards; therefore, the structure must be determined correctly from the beginning.
Barcode generation
Each variant must have its own barcode; a common barcode makes stock tracking impossible from the start.
The barcode scanned at the cash register must determine which color and size were sold. Otherwise, stock deviation is inevitable.
The ability to generate barcodes in bulk via the matrix significantly shortens the setup time.
Barcodes from the supplier should also be recorded; these barcodes are scanned during goods receipt.
We discussed the multi-barcode structure in the barcode management article.
Stock tracking
Variant-based stock tracking is the most critical operational need for textile businesses.
Total stock information alone is meaningless; it must be known which sizes the hundred units of products are in.
Products with a disrupted size distribution become unsellable even if the total stock is high.
Therefore, defining critical levels on a size basis is much more meaningful than on a product basis.
Inventory counts must also be performed on a variant basis; a total count masks distribution issues.
Order and shipment
Order entry for variant products is significantly accelerated with a matrix view.
Dealer orders are usually placed as size series; series definitions facilitate this entry.
During shipment, however, a variant-based picking list is required; sending the wrong size is the most common mistake.
Barcode verification almost entirely eliminates this error.
We explained shipment preparation in the shipment preparation article.
Channel mapping
The variant structure in marketplaces may be configured differently from your own systems.
Each platform has its own color and size value list, and these must be mapped.
A mapping error leads to the sale of the wrong size and results in returns. This is one of the most expensive integration errors.
Stock synchronization must also operate on a variant basis; main-product-based synchronization generates overselling.
We covered the mapping process in the product matching article.
Reporting
Variant data generates highly valuable analyses for textile businesses.
Size-based sales distribution is the foundation of the next production or purchasing plan. A wrong distribution means unsellable stock.
Color-based analysis also feeds seasonal planning; data shows which color is performing well.
Differences in size distribution by region can also be tracked; this information optimizes inter-branch distribution.
The size distribution of remaining stock guides discount decisions.
Things to consider
Opening each variant as an independent product is the most common and costly setup error.
Keeping colors and sizes as free text also makes filtering and reporting impossible.
Using a shared barcode renders inventory tracking useless from the start.
Failing to deactivate unused matrix cells bloat the lists unnecessarily.
Definitionsare managed in the definitions moduleand linked to stock cards.
Frequently asked questions
How many variant dimensions can be defined?
Color and size are the most common pair; if you need a third dimension, we evaluate it together during setup.
Can variants be sold at different prices?
Yes, they can; defining different prices for larger sizes is a common practice.
Can new colors be added later?
Yes, they can; the matrix is expanded and barcodes are generated for the new variants.
Can the production bill of materials be variant-based?
Yes, it can;bill of materialswe covered the structured approach with variants in the article.
The variant structure directly determines the reliability of inventory data in textile and similar sectors. When set up incorrectly, it is almost impossible to fix.
Keep colors and sizes in defined sets; free text kills filtering and reporting from the start.
Assign a separate barcode to each variant; a shared barcode completely renders inventory tracking useless.
Define the critical level on a size basis as well; even if total stock is high, a broken distribution halts sales.
Perform marketplace mapping on a variant basis as well; selling the wrong size is one of the most expensive integration errors.
By consulting the EQLEM teamYou can set up your variant structure.