To Fit vs garment measurements
Measurements cause more Ajio rejections than anything except feed collisions, and most of them trace back to a single convention that Ajio never states anywhere.
The convention
For every measurement, Ajio's template has two fields:
| Field | What it means |
|---|---|
*To Fit Bust | the body it is meant to fit |
*Bust | the garment, as measured flat |
They must never be equal. On rows Ajio accepts, the size chart value sits in the middle, with the body measurement about 2″ under and the garment about 2″ over:
| Size | Your size chart | *To Fit Bust (body) | *Bust (garment) |
|---|---|---|---|
| S | 36 | 34 | 38 |
| M | 38 | 36 | 40 |
| L | 40 | 38 | 42 |
| XL | 42 | 40 | 44 |
| XXL | 44 | 42 | 46 |
Set both fields to your chart value — the natural thing to do — and you have described a garment with zero ease that also fits a body one size larger. Every size fails.
We watched this fail an entire style run. The bust series graded perfectly, 36 through 44, and every single row was rejected. The numbers were right; the two columns were the same.
The two different measurement errors
Ajio runs two independent checks, and they mean different things.
"not in the allowed incremental limit"
This is about the sequence across sizes. It fires when a value dips below a smaller size or jumps several inches. A real failing series:
S=44 M=42.8 L=45 XL=45.5 XXL=46 3XL=50.8 4XL=47 5XL=54.8
M is below S, and 3XL and 5XL spike. Accepted rows in the same file ran a clean +0.5″ per size.
A flat series is legal. Ajio accepted Front Length 28″ unchanged from S to 3XL. Many brands genuinely cut one length per style, and the length does not grade. This check is not complaining that a value repeats — it is complaining that it moves the wrong way.
"not in the allowed size range limit"
This is an absolute check, per size, against a band. Independent of the sequence. A series can rise perfectly and still fail every row — that is the signature of the To Fit/garment mix-up above.
Before you argue with the numbers, check for a column-copy bug
Lay one full row out side by side and read it across.
On one catalogue, a co-ord set's *Hips had been filled from the waist series — every size had hip equal to waist. The rejection text never revealed that. One row printed across showed it instantly.
This is worth doing first, every time. It is the cheapest check available and it catches a class of error that no amount of chart discussion will.
Where to get measurements you can defend
In order of preference:
- Ajio's own accepted rows for the same category and seller. Ajio's verdicts define what Ajio considers legal, so continuing an accepted series is evidence rather than inference. Require at least three accepted points with a consistent step before interpolating — two points cannot distinguish a real grade from one bad number.
- Your QC-approved file for the same garment on another marketplace. The same products are listed on Myntra, Nykaa, Flipkart and Amazon, and those files went through the brand's own QC.
- The brand's published size chart, as corroboration.
- Ask the brand. A wrong measurement causes returns, which cost far more than another upload cycle.
When you compare channels, show every channel's value rather than averaging them. A disagreement between channels is a finding — usually one file was filled from the wrong chart — not noise to be smoothed away.
The one that cannot be fixed
Duplicate: This style code, colour & standard size combination is already present in system.
Please do not upload again.
If a size went live with a wrong measurement, there is no self-serve correction path. Only your Ajio SPOC can amend a live size.
We have seen a catalogue with eleven styles live where size M is shorter than size S, for exactly this reason. It cannot be repaired by upload.
Which makes the point: measurements are the area where prevention matters most, because it is the one area where being wrong is permanent.
Pre-upload checks
*To Fit <X>is the body,*<X>is the garment, and they are never equal- roughly 2″ of ease either side of the chart value
- the series never dips below a smaller size and never jumps
- flat across sizes is fine when the garment genuinely has one measurement
- every column reads across correctly on a full printed row
- cross-checked against your QC-approved file for the same batch on another channel
Related: How Ajio feeds work · Is my barcode free?
Last verified 26 August 2026.
HyndBrain lists apparel catalogues across seven marketplaces, which is how we ended up knowing this. Talk to us.