Choose the brick before the first upload

A wrong Ajio brick is close to a self-serve dead end. Manual QC can reject the product-image match, while a correction in a new category can fail because the original brick already owns the style code.

Observed apparel mapping

Garment shown	Ajio brick
Full-length kurta	Kurtas
Short kurta or tunic	Kurtis & Tunics
Kurta + pant, with or without dupatta	Kurta Suit Sets
Dress	Dresses & Gowns
Co-ord set	Co-ord Sets

Use the product and full image gallery, not only the brand's source category. Retail naming is not always the same as Ajio's classification.

Sets need a second check

The visible components should agree with the catalogue fields. For a kurta, pant and dupatta:

Field	Value pattern
Net Quantity	`3 N`
Package Contains	`1 kurta, 1 pants, 1 dupatta`
Dupatta Fabric	populated
Component Count	`3`

IQC compares this description with the photographs.

Where confidence ends

Co-ord Sets has not worked for one observed seller: 57 rows across three attempts produced zero live products and two different rejection reasons. The account had no accepted co-ord product to establish seller-specific precedent, while Kurta Suit Sets had 78 live.

That does not prove Co-ord Sets is universally wrong. It means the correct route for those styles remains unresolved and should be confirmed with the Ajio SPOC.

If you already chose the wrong brick

Do not keep creating feeds. Ask your SPOC to re-brick the existing style. The alternative is a genuinely unused style code, which creates reconciliation work and should not be the first choice.

Pre-upload brick check

inspect the garment length and silhouette
count every set component shown
compare with recent accepted products for the same seller
make quantity fields agree with the gallery
escalate uncertain co-ord classification before uploading

Last verified 26 August 2026. Ajio can change brick definitions without notice.

HyndBrain maps apparel products to marketplace-specific categories. Talk to us.