Skip to main content
Free 20-minute marketing audit
Limited spots available

Have a question?

We usually reply within 5 minutes.

WWhatsApp TTelegram

Merging Product Cards on Marketplaces in Uzbekistan: Variant Structure for Colour, Size and Volume

How to merge product cards on Uzbek marketplaces: which variants share one listing, how to set up SKUs and barcodes, Uzum and Yandex Market rules, checklist.

Merging Product Cards on Marketplaces in Uzbekistan: Variant Structure for Colour, Size and Volume

Short answer: if one product differs only by colour, size or volume, it lives in one product card. Each variant gets its own SKU and its own barcode. Items of a different type, brand or shape get separate cards. Decide on this structure before the goods ship to the marketplace warehouse. Fixing it later is hard, and on some platforms impossible.

For a foreign brand or distributor entering Uzbekistan, this matters more than it looks. Listings on Uzum Market, Yandex Market, Wildberries and Ozon drive daily stock, picking, advertising and reporting. This article is part of the guide running a marketplace store as a system. This piece covers one question only: how to group variants.

What merging product cards means and why it pays off

A common pattern in new stores: the seller creates one card for the red T-shirt, another for the blue one, and a third for black. Search results now show the same product three times. Each card has few reviews and fragmented statistics.

With a merged card, the shopper lands on one page. Colour is picked from swatches, size from a list. The seller gains order too:

  • One place to choose. Shoppers see other colours without leaving the page.
  • One place for card strength. Reviews, questions and sales history accumulate on one page. How that affects position is covered in ranking higher in marketplace search.
  • Content written once. Title, description and main images do not have to be rewritten for each colour.
  • Cleaner analytics. One table shows which colour and which size sell.

How to build the card itself — images, title, description — is covered in the product card that sells.

Variant structure: card, SKU and barcode

Think of the structure in three layers.

Also read Selling on Amazon from Uzbekistan: who can be the seller, and what it takes to reach a first profit Business · 11 min
  1. Card — the product itself. For example, "Men's cotton T-shirt, classic fit".
  2. Variant axes — what differs. Usually colour, size or volume.
  3. SKU — a combination of axes. "Black, L" is one SKU. "Black, XL" is another.

The number of SKUs equals the product of the axes. Uzum's manual gives the example of a coat in two colours and three sizes: six SKUs. An illustrative case: a T-shirt in four colours and five sizes is 4 × 5 = 20 SKUs. Each has its own stock level, its own barcode and its own line in your records.

The barcode is the critical part. If a warehouse worker swaps black L for black XL, the customer gets the wrong size and returns it. A separate code for every SKU, applied correctly to every box, is therefore mandatory. How to run a warehouse on barcodes: warehouse barcode system.

Build your internal article numbers systematically as well. A simple pattern: model code + colour code + size, for example FT01-BLK-L. Anyone in the warehouse or reading a report recognises the item at a glance. If your head office already has a global SKU scheme, map it once to the local structure rather than inventing new codes per platform.

A seller sorts identical phone cases by colour into separate bins

When to merge and when to keep separate cards

The key question: does the shopper see the difference as "another version of the same product" or as "a different product"?

  • Colour — One card: Yes; Separate card: —
  • Size — One card: Yes; Separate card: —
  • Volume or weight (250 ml / 500 ml) — One card: Yes; Separate card: —
  • Shape, cut, pattern — One card: —; Separate card: Yes
  • Product type (T-shirt vs polo) — One card: —; Separate card: Yes
  • Brand — One card: —; Separate card: Yes
  • New vs markdown item — One card: —; Separate card: Yes
  • Set vs single unit — One card: Depends on platform rules; Separate card: Usually yes

Uzum Market's official manual follows this logic. One product gets one card. Differences in colour, size or volume are reflected in one card and in separate SKUs. Placing different product names and types, or different brands, in one card is prohibited. Items that differ in shape, size or pattern are better split into separate cards.

The opposite mistake also exists: fake variants. The same product is listed as two SKUs that differ only by name. Uzum prohibits this directly: you may not create different SKUs for what is effectively the same product without objective differences in characteristics.

The shopper's choice: colour, size and volume inside the card

Merging only works if it is convenient for the shopper. On a phone, the shopper taps a colour swatch and expects the photo to switch to that colour. If it does not, they cannot tell what they are ordering.

So every colour needs its own photos. On Uzum, photos can be attached only to the "Colour" characteristic. Each colour must have its own photo, and it must not duplicate the main gallery. Sizes do not need photos, but they do need a size chart. With footwear this is critical: selling shoes on marketplaces in Uzbekistan explains why insole length should be stated in centimetres.

Typical conversion killers:

  • Vague colour names. "Mocha", "Cappuccino", "Latte" — shoppers cannot tell them apart. Pick the colour from the platform's list.
  • Empty variants. Ten sizes listed, one in stock. The shopper clicks through, finds nothing and leaves. Hide or restock variants that stay out of stock for long.
  • Illogical variant prices. If the small volume costs more than the large one, shoppers assume an error.
  • Sizes typed by hand. Uzum requires sizes to be chosen from its standard list. A manually typed size may not be recognised, and the product goes to manual review.
A shopper picks a product colour within one card in a marketplace app

Platform rules to know in advance

Rules change. The points below come from official seller help pages as of November 2026. Check the current version in your seller account before you start.

Uzum Market.

  • A card can have up to 5 characteristic groups, 3 of which can be custom.
  • Groups can be added or removed only until the first shipment to the warehouse. After that, you can only add new values to existing groups, such as a new colour under "Colour".
  • In clothing, footwear and accessories, colour and size (where applicable) are mandatory.
  • SKUs created in different cards cannot be merged into one later.

Yandex Market.

  • Variants in a group must share the category and brand.
  • Up to 500 variants in one card.
  • The variant group name must be unique within the category.
  • New and markdown items cannot be in the same group. Before publishing, the platform checks that required fields are filled in and that no variants are duplicates.

Wildberries and Ozon. Both platforms let you merge variants into one card and split them again if needed. On Wildberries, merged cards share a common group identifier. Merge conditions vary by category, so check the instructions in your seller account.

The main takeaway from Uzum's rules: plan the structure up front. After the first shipment, you cannot add a new group such as "Material". And two separate cards cannot later be combined into one.

What to do if your cards are already fragmented

Many stores reach this point halfway: five separate cards for one model, each with stock. There is no need to delete everything in a hurry. Work in this order:

  1. Build a list. Put every card for each model in one table: colour, size, stock, last 30 days' sales and number of reviews.
  2. Choose the main card. Usually the one with the most reviews and sales.
  3. Check what the platform allows. On Yandex Market, existing products can be added to a variant group from the catalogue. On Uzum, SKUs from different cards cannot be merged.
  4. Ship the next batch in the right structure. If merging is unavailable, add the needed variants to the main card as new SKUs with the next delivery.
  5. Sell through the old cards. Once their stock runs out, do not restock them and move them to the archive.

This takes one or two replenishment cycles. During that time, point advertising at the main card, not the old ones.

Pre-launch checklist for variants

Run through it for every new model.

Structure

  • ☐ Variants differ only by colour, size or volume.
  • ☐ Brand and product type are the same across all variants.
  • ☐ All required characteristic groups are added before the first shipment.
  • ☐ No fake variants without real differences.

SKUs and barcodes

  • ☐ Every SKU has its own article number following one pattern.
  • ☐ Every SKU has its own barcode.
  • ☐ Box labels are checked against SKUs.

For the shopper

  • ☐ Every colour has its own photos.
  • ☐ Colour names are taken from the platform's list.
  • ☐ Sizes are taken from the standard list, and there is a size chart.
  • ☐ Variant prices follow a logical order.
  • ☐ Out-of-stock variants are monitored.

Control

  • ☐ Sales and returns are tracked by colour and size.
  • ☐ Once a month, review which variants are returned most often.

Conclusion

Merging product cards is not a technical setting. It is an assortment decision. Colour, size and volume of one product share one card. A different type, brand or shape gets its own card. Every SKU gets its own article number and barcode, every colour its own photos. Map the structure before the first batch. Changing it afterwards costs considerably more.

Frequently asked questions

Should colours and sizes share one product card or get separate ones?

If one product differs only by colour, size or volume, it belongs in one card with separate SKUs. Uzum Market's seller rules say exactly this: one product, one card. Items that differ in shape, pattern or product type go into separate cards.

Can two existing cards on Uzum Market be merged later?

No. Uzum's seller manual states that SKUs created in different cards cannot be combined into one. Plan your variant structure before the first shipment to the warehouse.

How many variants can one card hold on Yandex Market?

According to Yandex Market's seller help, up to 500 variants per group. All variants must share the category and brand, have stock and pass validation. New and markdown (discounted defective) items cannot sit in the same group.

Does every variant need its own barcode?

Yes. Each SKU is a separate unit in the warehouse. Uzum assigns a unique system barcode to every SKU automatically, and you can enter the manufacturer's EAN-13 manually if no other supplier has reserved it. Correct barcodes are what keep colours and sizes from being mixed up at picking.

Bringing a multi-variant range to Uzbekistan?

Let's map your catalogue into a variant structure that fits local marketplace rules: which items share a card, and how SKUs and barcodes should be set up before the first shipment.

Discuss your variant structure →

Let's work out where to start

Free consultation with a DORA specialist

Message on Telegram

Let's discuss your project

Leave your number and a specialist will get in touch.

Send a request via Telegram

Your details are used only to contact you.