Read the portal for state and exports for evidence
Ajio's Upload History looks like one progress table. In practice, each column answers a different question, and the files you download can preserve failures long after they have cleared.
What each status column means
| Portal column | What it tells you |
|---|---|
Uploaded S(n) | The number of rows accepted into the feed |
Auto QC | Automated checks for formats, measurements, allowed values and duplicates |
Manual QC | Human review of category choice and product-versus-image fit |
System Processing | Post-QC ingestion; tax and HSN problems can stall here |
Success S(n) | The number of rows that are live |
Upload Failed | The whole file was refused; no usable feed was created |
An Upload Failed row may display a feed UUID, but it is a dead entry. It created nothing and owns nothing. Do not build a recovery plan around it.
A downloaded export is a snapshot
A rejection export records what failed when the file was generated. It is not a live report. One feed we reviewed continued to show rejected rows in its downloaded export after the portal itself showed zero rejected.
Use the two sources differently:
- Portal: current state and counts.
- Rejection export: the exact historical error text.
If the two disagree, trust the portal about whether the row is still failing.
Success exports are the only positive evidence
A rejection file can prove that something failed. A style's absence from it proves nothing. A feed that succeeds outright may never produce a rejection file at all.
Download the Success export before marking a style “not found”. On one account, this moved 70 styles from “no record” to confirmed live in a single pass.
A practical tell: an export with product rows and zero values in Remark is a Success export.
Read the whole remark
This combined remark describes a product that is already moving through another feed:
Cannot process this ean, it is present in different feed --> id: 8f3c21ab-...
| Duplicate: This SKU is already in under processing in system. Please do not upload again
The second clause matters. The referenced feed is processing normally. Stop resubmitting and let it finish.
Resolve to the product, not the feed
“Held by feed X” is plumbing, not a final status. Follow the pointer:
- Feed X succeeded → the product is live.
- Feed X has a genuine rejection for the style → that rejection is the real problem.
- Feed X is clean but unfinished → the product is in flight.
Applying this method to one catalogue reduced “held by another feed” from 29 styles to zero. Every product was either already live or already progressing.
Related: How Ajio feeds work · Is my barcode free?
Last verified 26 August 2026. Ajio can change portal behaviour without notice.
HyndBrain audits marketplace upload histories and catalogue status. Talk to us.