"Measurement is not in the allowed size range limit"
What you see
Measurement is not in the allowed size range limit
What it means
Ajio is checking an absolute band for each size. This differs from the incremental-limit error, which checks whether the sequence rises sensibly.
A series can increase perfectly from S to XXL and still fail every row because each value falls outside the permitted band.
Why it happens
The strongest observed signature is a To Fit/garment mix-up. Ajio treats:
| Field | Meaning |
|---|---|
*To Fit Bust | The body the garment is intended to fit |
*Bust | The garment measurement |
They should not be equal. On accepted rows, the published chart value commonly sits between them, with body roughly 2″ below and garment roughly 2″ above.
Setting both columns to the size-chart value is intuitive but describes zero ease. We watched that reject every size in an otherwise clean sequence.
How to fix it
- Check whether the paired
*To Fit Xand*Xcolumns contain identical values. - Confirm which source value describes the body and which describes the garment.
- Compare with accepted rows for the same seller and brick.
- Cross-check the same garment's QC-approved marketplace file or the brand's published chart.
- Correct all sizes together inside the owning feed's rejection workbook.
If the wrong value is already live, upload cannot amend it. Your Ajio SPOC must make the correction.
How to avoid it next time
- Treat To Fit as body and the plain field as garment.
- Never populate the paired fields with identical values.
- Validate absolute values and size progression as separate checks.
- Escalate uncertain measurements to the brand rather than guessing.
Related: To Fit vs garment measurements · Sourcing measurements you can defend
Last verified 26 August 2026. Ajio can change size-range limits without notice.
HyndBrain prepares marketplace-ready measurement data. Talk to us.