Know when the self-serve route has ended

Repeated uploads do not solve every Ajio problem. For several states, another file only creates more feed collisions.

Releasing rejected SKUs from their owning feed is not one of those states. Download the feed's rejection file, clear the rows for the SKUs you want to release, and re-upload that file under a new filename.

Re-brick an existing style

If Manual QC rejects the category and the original brick already owns the style code, your SPOC can move the existing style. A fresh upload into another brick usually produces The style code exists in another brick.

Amend a size that is already live

Upload cannot overwrite an existing style, colour and standard-size combination. If a live measurement is wrong, your SPOC must amend it. One observed catalogue had eleven styles where size M was shorter than size S and no self-serve correction was available.

Explain an undocumented size-chart requirement

IQC-Size chart not available identifies the problem but not a confirmed self-serve mechanism. Your SPOC must tell you how the chart is expected for that brick.

Confirm HSN and tax expectations

An HSN problem can stall at System Processing after QC. Source the code from the brand's finance team first. If the finance-approved eight-digit code still stalls, ask your SPOC to confirm Ajio's expected treatment.

Send one useful message

Batch related products and include:

feed ID
style codes and affected barcodes
exact rejection or stalled stage
current Is SoftDeleted state where relevant
requested action: re-brick, amend or confirm
verified replacement value when asking for an amendment

One complete request is easier to action than a sequence of partial messages.

Last verified 31 August 2026. Ajio's support responsibilities can change without notice.

HyndBrain separates self-serve fixes from marketplace-owned actions. Talk to us.