How to manage products with different sizes, colors, and other characteristics

What are product variations?

Product variations (product variations) are different modifications of one basic product that differ in certain parameters: size, color, material, volume, configuration, or other characteristics.

The key difference from individual products: all variations have a common description, a single product card, and are united by a common parent product, but each variation has a unique SKU, price, and balance.

Why use variations?

• UX improvements — the buyer selects the desired size/color on one page, rather than switching between dozens of cards
• SEO optimization — one page instead of many similar ones concentrates link weight and traffic
• Simplifying analytics - sales of all variations are counted as one product, it is easier to evaluate the effectiveness
• Content Saving — one description, one photo session for all sizes/colors
• Quick update — changes in description or characteristics apply to all variations at once
• Correct operation of filters — one product is not duplicated in the search results when filtering by size or color

Types of variations

1. Size variations

The most common type in fashion, footwear, furniture.

2. Color variations

Critical for clothing, shoes, accessories, electronics, furniture.

• Basic colors: Black, White, Gray, Red, Blue
• Details: "Dark Blue", "Sea Wave", "Indigo"
• Visualization: Color chips (color swatches) or photo thumbnails

3. Variations in material

Important for clothing, furniture, building materials.

• Textiles: cotton, polyester, wool, linen, cashmere
• Furniture: wood, plastic, metal, glass
• Usually affects price and characteristics (care, durability)

4. Volume/weight variations

Typical for food products, cosmetics, household chemicals.

• Cosmetics: 50 ml, 100 ml, 250 ml, 500 ml
• Products: 200 g, 500 g, 1 kg
• It is important to show the unit price (€/ml, €/kg) for comparison

5. Variations in configuration

Often found in electronics, tools, cosmetic kits.

6. Combined variations

A product can have several types of variations at the same time.

• T-shirt: size (S-XXL) × color (10 options) = 50 variations
• Sofa: size (2-seater, 3-seater) x material (fabric/leather) x color (6 options) = 24 variations

Data structure for variations

Proper data structure is critical to effectively manage variations.

Architecture: parent product + child variations

Parent Product

Contains general information for all variations:

• Name — "Men's Classic T-shirt"
• Description - detailed description of the product
• Category — "Clothing → Men's → T-shirts"
• Brand — "Nike"
• General characteristics - composition, care, country of manufacture
• Main images - a photo without reference to a specific color
• SEO data — Title, Description, URL

Child Products / Variations

Each variation has unique data:

• SKU — unique article number (for example, NIKE-FT-BLK-M)
• Attributes — Size: M, Color: Black
• Price - may differ for different variations
• Remainder — quantity in stock
• Barcode (EAN/UPC) - for accounting and sales
• Weight/dimensions — to calculate delivery
• Images — color/modification specific

Example of data structure (JSON)

 { "parent_product": { "id": 12345, "name": "Men's Classic T-shirt", "description": "Classic men's T-shirt made of 100% cotton...", "category_id": 234, "brand": "Nike", "images": ["main.jpg", "detail1.jpg", "detail2.jpg"], "attributes":{ "material": "100% хлопок", "care": "Стирка при 30°C", "country": "Турция" } }, "variations": [ { "sku": "NIKE-FT-BLK-S", "attributes":{ "size": "S", "color": "Черный" }, "price": 29.99, "stock": 15, "ean": "5901234123457", "images": ["black-front.jpg", "black-back.jpg"] }, { "sku": "NIKE-FT-BLK-M", "attributes":{ "size": "M", "color": "Черный" }, "price": 29.99, "stock": 42, "ean": "5901234123464", "images": ["black-front.jpg", "black-back.jpg"] }, { "sku": "NIKE-FT-WHT-M", "attributes":{ "size": "M", "color": "Белый" }, "price": 29.99, "stock": 8, "ean": "5901234123471", "images": ["white-front.jpg", "white-back.jpg"] } ] }

Implementation in popular CMS

WooCommerce (WordPress)

Uses the "Variable Product" product type:

• Create attributes: Size, Color
• Set possible values: S, M, L / Black, White
• Generate variations automatically or manually
• For each variation, indicate the SKU, price, and balance.

Shopify

Supports up to 3 options and up to 100 variants:

• Options: Size, Color, Material
• Variants: all combinations of options
• Each variant has an SKU, price, barcode, and image.
• Limit: maximum 100 variants per product

PrestaShop

Combinations System:

• Create attributes and their values
• Generate combinations
• You can set the price impact (+€5 for XL size)

Price and inventory management

Pricing Strategies for Variations

1. One price for all variations

The simplest option: all sizes and colors at one price.

• Pros: simplicity, transparency for the client
• Cons: does not take into account the difference in cost
• Suitable for: fashion, where size does not significantly affect the cost

2. Differentiated pricing by size

Larger sizes cost more due to the higher material consumption.

3. Different prices by color

It is rare, but it does happen that certain colors are more expensive to produce.

• Basic colors (black, white, gray): €29.99
• Complex shades (burgundy, emerald): €34.99

4. Pricing by configuration

The more complete the set, the higher the price, but often with a benefit for the buyer.

Managing the remainder of variations

Problem: Uneven distribution of sales

In practice, variations sell unevenly. According to fashion retail statistics:

• Sizes M and L: 60-70% of sales
• Sizes S and XL: 25-30% of sales
• Sizes XS and XXL: 5-10% of sales

ABC analysis within variations

Analyze sales for the last 3-6 months:

Matrix purchasing

Create orders for suppliers based on your actual sales structure:

• Don't take it evenly one size of each
• Purchase in proportion to demand: if you order 100 pcs, then M - 35 pcs, L - 30 pcs, etc.
• Safety stock for popular sizes should be higher

Reorder points for different variations

Set individual thresholds for each category:

• Category A (M, L): Reorder point = 15 pcs (2 weeks of sales)
• Category B (S, XL): Reorder point = 8 pcs
• Category C (XS, XXL): Reorder point = 3 pcs or purchase to order

Displaying variations on the site

UX best practices

1. Variation selectors

Choosing the right selector type is critical to conversion.

2. Availability indication

Be sure to show the availability of each variation:

• In stock: the button is active, you can select
• Few: The "3 units left" indicator encourages buying
• Not available: crossed out/gray button + "Notify when available"
• To order: "Delivery in 7-14 days"

3. Dynamic image change

When choosing a color, automatically show the corresponding photos:

• Select "Red" → photos of the red product are shown
• Minimum 3-4 photos for each color (front, back, details)
• 360° view or video for premium products

4. Dynamic price change

If the price depends on the variation, update it instantly:

• I chose size XL → the price changed from €39 to €44
• Show the old price crossed out if there is a discount
• Update the total cost based on quantity

5. Size chart

Critical for clothing and footwear to reduce returns:

• The "Size Chart" link next to the selector
• Modal window with a detailed correspondence table
• Measuring instructions (how to measure chest circumference, foot length)
• Sizing recommendations ("This item runs small, please order one size larger")

6. Quick selection in the catalog

Don't force the user to go to the card to select a size:

• Quick View — quick view with variation selection in a modal window
• Add to cart directly from the catalog with a choice of size/color

Mobile adaptation

On mobile devices, compactness is especially important:

• Colors: horizontal scrolling chips
• Dimensions: compact grid of buttons 3-4 in a row
• Size chart: full screen mode for convenience
• Swipe to change color in photos

Importing variations from price lists

Problems importing variations

1. Different data formats among suppliers

Suppliers convey variations in different ways:

Format A: Separate lines for each variation

 SKU | Name | Price | In stock SHIRT-BLK-S | Black Oxford Shirt S | 39 | 15 SHIRT-BLK-M | Black Oxford Shirt M | 39 | 42 SHIRT-WHT-M | White Oxford Shirt M | 39 | 8

Format B: Attributes in separate columns

 Model | Color | Size | SKU | Price | In Stock Oxford | Black | S | SHIRT-BLK-S | 39 | 15 Oxford | Black | M | SHIRT-BLK-M | 39 | 42 Oxford | White | M | SHIRT-WHT-M | 39 | 8

Format B: All sizes on one line

 Model | Color | Sizes | Price | Remaining Oxford | Black | S, M, L, XL | 39 | S: 15, M: 42, L: 23, XL: 8

2. Mismatch of attribute names

• One supplier: "S, M, L, XL"
• Other supplier: "Small, Medium, Large, Extra Large"
• Third: "46, 48, 50, 52" (Russian sizes)

Needed normalization system to bring them to a uniform format.

Automating Variation Imports

Step 1: Recognizing the structure

The system should automatically determine:

• Where are the variation attributes (color, size) located?
• How are variations related to the parent product?
• Format for recording balances

Step 2: Grouping Variations

The algorithm combines individual lines into a single product with variations:

• By matching the model/article of the base product
• By similarity of names (text similarity >85%)
• According to the rules specified by the user

Step 3: Attribute Normalization

Bringing to a single reference book:

• "S" = "Small" = "Small" → standardized as "S"
• "Black" = "Noir" → "Black"
• The system learns based on previous imports

Step 4: Updating balances and prices

• Data synchronization for each variation separately
• Saving revision history
• Notifications about critical changes (out of stock, sudden price change)

Setting up import rules

Rule 1: Create new variations

• Automatically: If a new size/color appears in the price list → add a variation
• With confirmation: notify the manager for verification
• Ignore: do not create new variations, only update existing ones

Rule 2: Remove Missing Variations

• Hide: If the variation is not in the price list → set the remainder to 0, leave it in the database
• Delete: completely remove a variation from the catalog
• Leave: Do not touch, the supplier may not be supplying this size at the moment.

Rule 3: Content Management

• Update descriptions: yes/no (usually no, so as not to erase your content)
• Upload images: only for new variations / always / never
• Update characteristics: only technical (weight, dimensions) / all

Tools for importing variations

System automatic processing of Elbuz price lists allows:

• Download price lists from any suppliers in various formats
• Automatically recognize and group variations
• Configure attribute matching rules
• Synchronize balances and prices in real time
• Create product cards with variations automatically
• Export to any CMS (WooCommerce, Shopify, PrestaShop, OpenCart)

Best practices for variation management

1. Don't create excessive variations

Badly: 15 different shades of blue

Fine: 3-4 basic blue shades (Light blue, Blue, Dark blue, Denim)

Too many variations complicate the choice and reduce conversion (paradox of choice).

2. Group similar variations

If the difference is minimal (for example, different styles of the same jeans model), it is better to make them separate products rather than variations.

3. Optimize your SKU structure

Use a logical SKU system:

 BRAND-MODEL-COLOR-SIZE NIKE-FT001-BLK-M NIKE-FT001-WHT-L ADIDAS-SH023-RED-XL

This simplifies identification of goods in the warehouse, in the accounting system, and upon return.

4. Monitor metrics by variation

Track for each product with variations:

• Conversion rate by variations — what sizes/colors are chosen most often
• Bounce rate — Do users leave without finding the size they need?
• Out-of-stock rate - How often are popular variations out of stock?
• Return rate — percentage of returns by size (a sign of a problem with the sizing chart)

5. Clean inactive variations regularly

Once a quarter, analyze:

• Variations with no sales for 6+ months → candidates for deletion
• Sizes with constant zero balance → either reorder or remove
• Colors with minimal conversion → replace with more popular ones

6. Test the visualization

Run A/B tests:

• Color chips vs. color dropdown
• Size chart position (above button / below selector)
• Availability indicator ("3 units left" vs. just "In stock")

7. Use smart recommendations

• "Customers who bought size M also ordered size L" (for gifts)
• "90% of buyers choose size M for this model"
• "This item runs small. We recommend ordering a size larger."

8. Manage SEO for variations

• URL: one page for all variations (/product/mens-shirt-oxford)
• Title and H1: general for the product, without mentioning a specific color/size
• Structured Data: use schema.org/Product with an "offers" field for each variation
• Breadcrumbs: Do not duplicate categories for different colors

Conclusion

Proper product variation management is a balance between customer convenience, inventory efficiency, and technical implementation. Key findings:

• Data structure: Use the parent-child variation model for flexible management
• Pricing: differentiate prices where it is justified (sizes, configurations), but keep it simple
• Remaining: Apply ABC analysis within variations, purchase in proportion to actual demand
• UX: Choose the right selectors, show availability, update photos and prices dynamically
• Import: Automate loading variations from price lists to save time and reduce errors
• Optimization: Regularly analyze metrics, remove ineffective variations, and test the display

Effective variation management increases conversion by 25-40%, reduces content costs, improves SEO, and simplifies analytics. Modern automation tools make managing thousands of variations a simple and quick task.