"The style code exists in another brick"
What you see
The style code exists in another brick
What it means
Ajio has already associated the style code with a different brick, its term for a product category. Moving the same code into a new category is not treated as an ordinary correction.
Why it happens
The usual sequence starts at Manual QC:
Product Category Reject : Product vs Image Mismatch - Incorrect Brick
You then place the product into what appears to be the correct brick and upload again. The new row is refused because the original brick still owns the style code.
Style codes and barcodes are claimed independently, so repeated attempts can also create a deadlock: one feed holds the EANs while another holds the renamed style code, and each rejection points at the other.
How to fix it
There are two clean routes:
- Ask your Ajio SPOC to re-brick the existing style. This preserves the original identity and is the best route when the product should remain the same listing.
- Relist with a genuinely unused style code. Use this only when re-bricking is unavailable and you can maintain the mapping to your canonical product code.
In a feed deadlock, submit a style code that no feed has ever seen inside the feed that already owns the EANs. This is the observed route that resolves both claims in one upload.
How to avoid it next time
- Choose the brick from the garment and gallery before the first upload.
- Use recent accepted rows from the same seller as category evidence.
- Do not create a new feed merely to change category.
- Batch re-brick requests for your SPOC with style codes and target bricks.
Related: How Ajio feeds work · Choosing the right Ajio brick
Last verified 26 August 2026. Ajio can change category rules without notice.
HyndBrain resolves marketplace category and feed conflicts. Talk to us.