Skip to content

Structuring size and colour variants for a clothing store: SKUs, barcodes, stock and reports

Variants are the backbone of a fashion shop’s data. Name them consistently, give each its own barcode, and your stock counts, exchanges and best-seller reports start telling the truth. Here is the structure that works.

By Wameed field teamOnboarding and support

5 min read

In short: model each garment asone style (product) with variants for size and colour, never as separate products. Give every variant itsown barcode and SKU, recordcost and price at style level with variant overrides only where needed, and count stockby variant. Name consistently so reports group correctly, print labels when stock arrives, and review sell-throughby size curve, not just by style. In Wameed, product variants are on the Professional plan and above; on Starter each size and colour would be its own item.

If the data is messy, every later step (exchanges, counts, markdowns, online sales) is slower and less accurate. Ten minutes of structure per style saves hours later.

The model: style, variant, SKU, barcode

LevelExampleHolds
Style (product)Cotton thobe, classic collarName (AR/EN), category, brand, description, base price, cost, tax category, images
VariantWhite / 56Size, colour, its own barcode and SKU, stock, optional price override
SKUTHB-CLS-WHT-56A human-readable code
BarcodeEAN-13What the scanner reads

Create thestyle once, then add theoptions (size, colour) and generate the combinations. Delete the combinations that do not exist (a size you never ordered).

Naming rules that keep reports clean

  1. One spelling per colour (Navy, not Navy Blue, Dark Blue and Midnight).
  2. One size scale per category (S, M, L, XL; or numbers). Don’t mix.
  3. Style name without size or colour in it; the options carry those.
  4. A SKU pattern you can read: CATEGORY-STYLE-COLOUR-SIZE.
  5. Arabic and English names for the style, and Arabic colour names for customer-facing screens.
  6. Season or collection tag to support markdowns by collection.

Barcodes and labels

  • One barcode per variant. Scanning the label opens the exact size and colour.
  • Print labels when the delivery arrives, before the garment goes on the rail. Seebarcode and label printing guide.
  • Label content: style name, size, colour, price, barcode. Optionally the SKU for the stockroom.
  • Supplier barcodes: if the supplier prints them, record them as extra barcodes so you do not relabel.
  • Hang-tag and shelf: keep the barcode on a tag that survives trying-on.

Pricing

  • Set the price at style level. Most variants of a style cost the same to the customer.
  • Override per variant only where the price truly differs (plus sizes, a limited colour).
  • Use offers and collection discounts instead of editing prices for markdowns, so you can restore the price. Seepromotions and coupons.
  • Branch overrides if one branch prices differently.

Stock by variant

The size curve

A buyer’s best tool is thesize curve: how many of each size to buy. If you buy 10 of every size but customers buy mostly M and L, you will sell out of M and be left with XS and 3XL.

  1. Record sales by size for a season.
  2. Express each size as a percentage of the style’s sales.
  3. Order next season in that proportion, with small tails for the ends.
  4. Review per category; the curve for a thobe differs from a dress.

Exchanges and returns

At the till:

  1. Scan the receipt or find the sale by phone.
  2. Choosereturn orexchange and the reason (size, defect, changed mind).
  3. The returned variant goesback to stock (or to a damaged location).
  4. For an exchange, scan the new variant; the system calculates the difference.
  5. The system issues acredit note for the original invoice. SeeZATCA credit and debit notes.

Record the reason: if “too small” is the commonest, your size labels or fit may be the issue. Seereturns and refunds policy.

Reports to watch

ReportQuestion it answers
Sales by styleWhich designs sell?
Sales by sizeWhat does the size curve look like?
Sell-throughWhat share of what we bought has sold?
Stock coverHow many weeks of stock remain?
Slow moversWhat should be marked down? Seeslow-moving stock clearance
Returns by reasonAre sizing or quality causing returns?

Common mistakes

  • Creating each size as a separate product.
  • Reusing one barcode for all sizes.
  • Free-text colours and sizes.
  • Editing prices for a sale and forgetting to restore them.
  • Counting at style level only.

Frequently asked questions

Do I need variants?

If you sell a style in more than one size or colour, yes.

Can I have a different price per size?

Yes, with a variant override, but use it sparingly.

Which plan has variants in Wameed?

Professional and above.

Can I import variants in bulk?

Yes; prepare a clean spreadsheet and import in a batch, then check twenty items by hand.

  • #متغيرات المقاس واللون
  • #مخزون الملابس
  • #باركود للملابس
  • #كاشير ملابس
  • #size and colour variants
  • #apparel inventory
  • #fashion SKU structure

Share this article

Ask about your own shop

Thirty minutes on your products, your tax setup and your hardware — not a slide deck.

Keep reading