🏪SellerComplete ExamplesRecentUpdated Jul 12, 2026·Verified against the app Jul 12, 2026

Worked Example: Selling a T-Shirt in 2 Colors × 2 Sizes

#example#variants#colors#sizes#products
Complete Examples · Products

Ahmad expands into basics: a Classic Cotton T-Shirt in Blue and Black, sizes M and L. On Fawran, each sellable combination needs its own product — there is no variant matrix. Here is how he sets up all four correctly, with a naming convention that keeps his inventory sane.

Starting point

State: verified store. Goal: four sellable combinations (Blue-M, Blue-L, Black-M, Black-L), each with its own stock and price. The platform rule: one product = one offer. The colors and sizes fields inside the product Description step are descriptive text only — they do not create separate stock lines.

Where this happens

CatalogAdd Product, repeated once per combination (4 times here).

UI guide
CatalogAdd Product
Add Product — Identity
Product name (English)*Classic Cotton T-Shirt — Blue, M
Product name (Arabic)*تيشيرت قطني كلاسيكي — أزرق، مقاس M
SKUGenerated automatically on save
KeywordsTS-CLS-BLU-M, t-shirt, blue, medium
Next
Structural diagram of the real page — not a screenshot.
One product per combination — the color and size live in the product name.

Step by step with Ahmad’s values

  1. Decide the naming convention once: <Item> — <Color>, <Size>, plus an internal reference per combination: TS-CLS-BLU-M, TS-CLS-BLU-L, TS-CLS-BLK-M, TS-CLS-BLK-L. The platform SKU is generated automatically — keep your internal codes in the keywords and in your own records.
  2. Create product 1: “Classic Cotton T-Shirt — Blue, M” / «تيشيرت قطني كلاسيكي — أزرق، مقاس M». Photograph the blue shirt for its images.
  3. Repeat for Blue-L, Black-M and Black-L. Each gets its own images, price and description.
  4. In the Description step you may also fill “Available colors” / “Available sizes” as informative text for buyers — but remember these fields are descriptive only.
  5. Add inventory per product (each row in Inventory & WarehousesInventory is one product × one fulfillment model). Blue-M stock does not cover Blue-L.

What you should see

4 products created4 inventory rowsEach sells & counts separately

Four rows in ProductsAll Products and four inventory rows. Orders arrive per combination, so “Blue, M sold out” never blocks selling “Black, L”. Reports also count each combination separately — which tells Ahmad which color/size actually sells.

A common mistake on this journey

🚫Common Mistake

Creating one t-shirt product, listing all colors and sizes in the description, and expecting buyers to choose a variant at checkout. That variant matrix does not exist on Fawran: the buyer just buys “the product”, and you cannot tell which color/size they meant, nor track per-variant stock. Recovery: create the missing combination products, move the descriptive product’s stock to the correct combination rows, and deactivate the ambiguous product.

When to contact support

Contact support (category Catalog & Products) if you already received orders on an ambiguous multi-variant listing and need help contacting buyers about which variant they intended, or if two of your combination products were accidentally merged in the catalog.

Related guides

Was this article helpful?