Myntra size chart validation errors usually occur when measurements are missing, entered in the wrong unit, mapped to the wrong size, arranged in an invalid order, or inconsistent with the selected article type. A catalogue may contain correct images and descriptions but still fail validation when size information does not follow the required category structure.

Accurate sizing is especially important for fashion, footwear, innerwear, kidswear, accessories, and selected home products. Incorrect measurements can lead to catalogue rejection, customer confusion, size-related returns, negative ratings, and repeated quality-check failures.

This guide explains how to prepare, validate, and upload Myntra size charts. It covers garment measurements, body measurements, unit conversion, ascending-order errors, size mapping, footwear length, kidswear age groups, bulk-upload checks, and common correction workflows.

Myntra may update templates, mandatory fields, accepted values, and article-type rules. Sellers should use the current DIY Cataloguing screen, Partner University guidance, support communication, or category template available in their Partner Portal as the final source for the exact upload format.

What Is Myntra Size Chart Validation?

Size chart validation checks whether the measurement information submitted for a product is complete, logically ordered, correctly formatted, and suitable for the selected article type and size variation.

The system may validate:

Required measurement fields
Size labels
Measurement units
Numeric format
Minimum and maximum values
Ascending measurement order
Age and size relationships
Variation mapping
Article-type relevance
Consistency across all SKUs in a style

Why Accurate Size Charts Matter

They help customers select the correct size
They reduce size-related returns and exchanges
They improve product-page clarity
They support catalogue quality checks
They prevent incorrect size variation mapping
They improve consistency across colours and styles
They help customer support resolve sizing questions

Garment Measurements vs Body Measurements

Measurement type	Meaning	Example
Garment measurement	Measurement taken from the finished product	Actual shirt chest, top length, sleeve length
Body measurement	Customer body range intended to fit the product	To fit chest, to fit waist, to fit bust
Foot measurement	Customer foot length or related fit measurement	Foot length for footwear sizing
Product dimension	Physical size of an accessory or non-wearable article	Belt length, bag dimensions, mat size

Do not mix garment measurements with body-fit measurements. For example, a garment chest measurement is usually larger than the body chest it is designed to fit because the product may include ease.

Common Myntra Size Chart Fields

The required fields depend on category and article type. Examples may include:

Across shoulder
Bust
Chest
To fit bust
To fit chest
Waist
To fit waist
Hip
To fit hip
Front length
Top length
Bottom length
Sleeve length
Inseam length
Outseam length
Rise
Foot length
Heel height
Belt length
Age group

Only use fields that apply to the selected article type and current template. Do not force unrelated values into mandatory-looking columns without checking the category rule.

Correct Size Chart Preparation Workflow

Step 1: Confirm the Article Type

The article type controls the relevant attributes and measurements. Verify whether the product is a shirt, top, kurta, dress, trousers, jeans, night suit, footwear, bra, belt, or another category before preparing the chart.

Step 2: Collect Physical Samples

Measure actual production samples rather than relying only on estimated patterns or supplier descriptions.

Step 3: Define the Measurement Method

Create a standard measurement guide for the team. For example:

Chest measured flat from underarm to underarm, then doubled where required
Shoulder measured seam to seam
Top length measured from high shoulder point to hem
Sleeve measured from shoulder seam to cuff
Inseam measured from crotch seam to bottom hem
Foot length measured heel to longest toe

The method must match the field definition expected in the current Myntra workflow.

Step 4: Select One Unit System

Use the unit requested by the template. Do not mix inches and centimetres inside one measurement column.

Step 5: Map Every SKU to the Correct Size

Each seller SKU, barcode, colour, and size variation should map to the correct chart row.

Step 6: Check Ascending Order

When sizes progress from smaller to larger, applicable body-fit and garment measurements should normally increase or remain logically consistent.

Step 7: Validate Before Upload

Check all values, units, decimal formatting, size labels, and variation relationships before submitting the file.

Understanding the Ascending Order Validation Error

A common message states that measurement attributes should be filled in ascending order. This usually means that a larger size contains a smaller value than the preceding size for an attribute that is expected to increase.

Size	To fit waist	Validation result
S	28	Valid starting value
M	30	Valid increase
L	32	Valid increase
XL	31	Likely error because the value decreased

How to Correct It

Sort rows in the actual size sequence.
Verify the physical sample measurement for every size.
Check whether inches and centimetres were mixed.
Check whether two size rows were swapped.
Check whether a body-fit value was entered in a garment-measurement field.
Correct the inaccurate value using verified source data.
Re-upload and review the processing result.

Do not simply increase a number to pass validation. The corrected value must match the product.

Inches and Centimetres Conversion

Use the conversion:

1 inch = 2.54 centimetres

Inches	Centimetres
10	25.4
20	50.8
24	60.96
28	71.12
30	76.2
32	81.28
34	86.36
36	91.44
40	101.6

Conversion Mistakes to Avoid

Entering centimetres in an inches column
Rounding every value too aggressively
Using different rounding rules across sizes
Converting an already converted value again
Copying the same value into both unit columns without conversion

Recommended Numeric Format

Use plain numeric values unless the template requests text
Do not include unit labels such as cm or inch inside numeric cells
Avoid special symbols
Use a consistent decimal format
Do not use ranges unless the field accepts ranges
Do not use commas as thousands separators in measurement cells
Avoid formulas in the final upload file unless supported

Size Label and Variation Mapping

The size chart row must match the variation size shown to the customer.

Common errors include:

SKU labelled M but mapped to L measurements
Age group 9-12 months mapped to a 12-24 months chart row
UK footwear size mapped to an incorrect foot length
One colour variant missing a size-chart relationship
Size labels written differently across files
Free size products uploaded with multiple conflicting measurements

Kidswear Size Chart Validation

Kidswear sizing may use age groups, numeric sizes, height ranges, or a combination of labels.

Check:

Age sequence is correct
Measurements increase logically
Top and bottom measurements belong to the same set
Size labels match the SKU variation
Chest, waist, inseam, and length values are not interchanged
Measurements reflect the product rather than only the child's age

Example size sequence	Validation check
9-12 M	Should normally precede 12-24 M
12-24 M	Should normally precede 2-3 Y
2-3 Y	Measurements should be checked against the next age group
3-4 Y	Should not contain smaller values without a verified design reason

Footwear Size Chart Validation

Footwear catalogues may require UK, US, EU, or other size labels and a related foot-length measurement.

Validate:

Size system
Gender or age group
Foot length
Inner length where required
Heel height
Width or fit information where applicable
Left and right pair consistency

Do not use a generic internet conversion chart without checking the actual product last and fit.

Innerwear and Body-Fit Products

Innerwear, shapewear, swimwear, and fitted products may use specialized size fields.

Review:

Bust or chest range
Underbust
Cup size
Waist and hip range
Stretch characteristics
Product-specific fit notes

Use the exact category template and avoid converting specialized sizes into general clothing sizes without approval.

Common Myntra Size Chart Errors and Solutions

Error	Likely cause	Recommended solution
Measurement not in ascending order	Larger size contains a smaller value	Verify row order, unit, and physical measurement
Mandatory measurement missing	Required field is blank	Enter the verified value requested for the article type
Invalid numeric value	Text, symbol, range, or unsupported decimal format	Use the accepted numeric format
Size chart does not match variation	Incorrect SKU-to-size mapping	Map each SKU to the correct size row
Measurement outside accepted range	Unit mismatch or data-entry error	Check inches vs centimetres and remeasure
Duplicate size row	Same size submitted more than once	Remove duplicate or correct the intended label
Incorrect size sequence	Alphabetical or age order is wrong	Arrange rows in the required commercial size sequence
Existing SKU measurement conflict	New chart differs from an existing mapped SKU	Verify the correct product version and request support if necessary
Wrong article type fields	Incorrect category or template selected	Use the correct article type and size-chart structure

Existing SKU Measurement Conflict

A validation message may indicate that measurements should be checked against already existing SKUs of the product. This can happen when a style or variation family already contains approved size data and the new SKU introduces inconsistent values.

Correction Workflow

Identify all existing SKUs in the style.
Download or record the currently approved size chart.
Compare the new SKU's size label and measurements.
Check whether the product design or fit has genuinely changed.
Use consistent measurements when the product is the same.
Keep a separate style or catalogue relationship when the fit is materially different and the platform workflow permits it.
Raise a Partner Support ticket with evidence when approved data is incorrect or locked.

Bulk Upload Format Checklist

Use the latest category template
Do not rename sheets
Do not remove mandatory columns
Do not change header names
Preserve the supported file format
Use one unit per measurement column
Use consistent size labels
Validate numeric cells
Check SKU and barcode mapping
Review all rows before upload
Download the processing report
Correct only failed rows

Excel Validation Rules for Internal Use

Before uploading, teams can create internal spreadsheet controls.

Highlight blank mandatory cells
Flag non-numeric characters
Compare each size with the previous size
Flag repeated SKU or barcode values
Validate allowed size labels
Check conversion differences between inches and centimetres
Flag extreme measurement changes
Compare related colour variants

Internal spreadsheet checks do not replace Myntra's live validation, but they can reduce avoidable upload failures.

Measurement Quality-Control Process

First-Level Check

The person measuring the product records the values and measurement method.

Second-Level Check

A separate reviewer rechecks a sample and compares sizes in sequence.

Catalogue Check

The catalogue team maps the measurements to the correct SKU, article type, and variation.

Upload Check

The processing report is reviewed for row-level success and failure.

Live-Page Check

The approved product page is checked to confirm that the size chart is readable and mapped correctly.

Use accurate physical measurements
Explain whether values are body or garment measurements
Use a consistent fit description
Show model measurements where allowed and useful
Add product-specific fit notes
Review return reasons by article and size
Correct recurring size-chart problems
Keep charts consistent across colour variants
Update charts when product patterns change

Daily Catalogue Checklist

Check new size-chart failures
Check ascending-order errors
Check variation mapping
Check missing measurements
Check processing reports
Check Partner Support responses
Verify newly approved product pages

30-Day Size Chart Improvement Plan

Days 1-7: Audit

Download current product and size data
Identify repeated validation errors
Group products by article type
Identify high-return sizes and styles

Days 8-14: Standardize Measurements

Create measurement guides
Train the measurement team
Define rounding rules
Standardize size labels
Create verified master sheets

Days 15-21: Correct Catalogues

Fix ascending-order errors
Correct unit mismatches
Repair SKU mapping
Update incomplete charts
Review processing reports

Days 22-30: Prevent Recurrence

Add spreadsheet validation
Introduce second-level QC
Track size-related return reasons
Maintain version-controlled master data
Create a weekly catalogue-health dashboard

Common Mistakes to Avoid

Guessing Measurements

Measure actual production samples.

Mixing Inches and Centimetres

Use the unit requested by the template.

Copying One Size Across All Rows

Each commercial size should use verified product data.

Entering Body Measurements as Garment Measurements

Confirm the field definition before upload.

Changing Values Only to Pass Validation

The catalogue must remain accurate for customers.

Ignoring Existing SKU Data

Review approved measurements in the style before adding new SKUs.

Using an Old Template

Download the current format from the Partner Portal.

How DigiCommerce Supports Myntra Sellers

DigiCommerce helps fashion, footwear, accessories, kidswear, beauty, and home brands prepare and correct Myntra catalogue data.

Size chart creation
Garment and body measurement mapping
Inches and centimetres conversion
Ascending-order validation
Kidswear size chart preparation
Footwear size mapping
SKU and variation correction
Bulk upload files
Processing report analysis
Catalogue QC correction
Partner Support ticket preparation
Return-reason analysis

Related DigiCommerce resources include Myntra catalogue QC errors and solutions, ecommerce catalogue services, and ecommerce listing services.

Frequently Asked Questions

1. Why does Myntra show an ascending-order validation error?

The system may have found that a larger size contains a smaller value than the preceding size for a measurement expected to increase.

2. Should Myntra size charts use inches or centimetres?

Use the unit requested by the current article-type template or cataloguing screen. Do not mix units in one column.

3. What is the difference between chest and to fit chest?

Chest may refer to the garment measurement, while to fit chest normally refers to the customer's body measurement range. Confirm the field definition in the template.

4. Can I use the same size chart for every product?

No. Use the same chart only when the products have the same article type, pattern, fit, and verified measurements.

5. Why does the new SKU conflict with existing SKUs?

The style may already contain approved measurements that differ from the newly submitted values. Compare the complete variation family.

6. Can decimals be used?

Use the numeric and decimal format accepted by the current template. Keep the format consistent across all rows.

7. How should kidswear sizes be arranged?

Arrange age or commercial sizes in the required sequence and verify that applicable measurements progress logically.

8. Should flat chest measurements be doubled?

Only when the field definition requests full circumference. Follow the measurement method specified for the article type.

9. How do I correct a locked or already approved size chart?

Prepare the correct measurements and evidence, then use the available edit workflow or raise a Partner Support ticket.

10. Can DigiCommerce prepare a Myntra size chart file?

Yes. DigiCommerce can prepare size charts, convert units, validate measurement order, map SKUs, correct bulk files, and analyse upload errors.

Conclusion

Myntra size chart validation should be treated as a product-data and customer-experience process, not only as a file-upload task. The correct workflow is to select the right article type, measure actual products, separate garment and body measurements, use the requested unit, arrange sizes correctly, map each SKU, and review the processing result.

Most errors are caused by unit mismatch, missing values, incorrect row order, inconsistent size labels, wrong article-type fields, or conflict with existing SKU measurements. A verified master sheet and a two-level measurement check can prevent repeated catalogue rejection and reduce size-related returns.

For Myntra size chart creation, measurement validation, bulk catalogue correction, QC support, and return-reduction analysis, connect with DigiCommerce Solutions.

Myntra Size Chart Validation: Correct Upload Format

In This Article