Check the route before you check the cells
The most expensive Ajio errors come from uploading a correct row through the wrong feed. Start with ownership, then validate the workbook and product data.
1. Choose the right upload route
| Situation | Correct route |
|---|---|
| Correcting a live row in an existing feed | Edit that feed's rejection workbook |
| Releasing rejected SKUs for a new feed | Clear their rows in the owning rejection file and re-upload it under a new filename |
Row is DELETED in Catalogue Report | Correct it in a fresh feed |
| Product is already under processing | Stop and wait |
| Live product needs amendment | Ask the Ajio SPOC |
Work oldest-first. The earliest feed owns the products, even though Upload History lists newest first.
2. Check the workbook
sellerIdis present and unchangedfeedIdis present when amending an existing feed- the file is a real template for a new feed, not a rejection export
- there are no empty declared category sheets
- shared strings and hidden workbook parts are preserved
- the filename has never been used in that feed
3. Check category and gallery
- the brick matches the garment shown
- full-length kurta, short kurti/tunic, sets and dresses are separated correctly
- every set component appears in the gallery
- Net Quantity, Package Contains and Component Count agree with the images
- a distinct back view is present and gallery images are not duplicates
4. Check measurements
*To Fit Xis the body and*Xis the garment- the paired values are not equal
- size series do not dip or jump without evidence
- flat length is allowed when the garment genuinely uses one length
- one full row has been read across for copied-column mistakes
5. Check compliance and copy
- India as Country of Origin includes verified Manufactured By details
- HSN is a finance-approved eight-digit tariff code
- required size-chart expectations are confirmed for the brick
6. Use the portal validator
Ajio's pre-submit validator names the row, brick, SKU, field and issue. Run it before submission; it is faster than waiting for Auto QC.
Current allowed-value casing matters. Both V-Neck and V-neck may exist on live products, but the observed current validator accepts only V-neck. Historical acceptance does not guarantee present acceptance.
Related: How Ajio feeds work · File-format rules
Last verified 31 August 2026. Ajio can change validation behaviour without notice.
HyndBrain runs these checks before preparing marketplace upload files. Talk to us.