Why Your Myntra Products Get Rejected and How to Fix Them?

So picture this.

You’ve finally cracked the Myntra onboarding. You’re already planning what you’ll do with all that sweet marketplace revenue.

Then you sit down to upload your products.

And that’s when the nightmare begins.

Last month, I got a call from a footwear brand founder – let’s call him Rajesh (not his real name, obviously).

They uploaded 100 products four months ago. In the first week, 2-3 actually got approved and went live. They thought they had figured it out. But the remaining 97? They just disappeared. No clear rejection message. No explanation. Nothing.”

Four months. 100 products. 97% stuck in limbo.

Here’s what made it even worse – those 2-3 approved products? They were selling decently. Proving there was demand. But Rajesh and his team couldn’t figure out why the rest weren’t going live.

They had:

An in-house operations team
Professional product photography
Quality products with good margins
Proper inventory ready to ship

But none of that mattered because they couldn’t get their products live.

Here’s what actually happened during those four brutal months:

Week 1: Uploaded 100 products. Waited eagerly. 2-3 went live! Team celebrated. The rest showed status “Under Review.”

Week 2-4: “Under Review” changed to… nothing. No rejection email. No error message. Products just vanished from the upload list. Team tried to re-upload. Same 2-3 types went through. Rest? Same black hole.

Week 5-8: Sent countless emails to support. No account manager assigned yet (they’re only assigned after you hit certain GMV thresholds, which you can’t hit if your products aren’t live – classic catch-22). Got generic responses: “Please check your catalog file” or “Ensure all fields are filled correctly.”

Week 9-12: The 2-3 products that did go live were selling, but the operational overhead wasn’t worth it for such a small catalog. Shipping costs, customer service, inventory management – all for 3 SKUs? Not sustainable.

Week 13-16: Completely gave up. Started talking to other marketplaces. Contacted me as a last-ditch effort before writing off Myntra entirely.

By the time we spoke, Rajesh had:

Lost ₹18 lakhs in potential revenue (conservative estimate based on the performance of his 2-3 live products)
Spent ₹2.4 lakhs on Myntra onboarding, photography, and setup
Wasted 4 months of his team’s bandwidth
Nearly killed his brand’s entire marketplace strategy
Still had no idea what was actually wrong with the 97 rejected products

That last point is the real killer. It’s one thing to get rejected with a clear error message. It’s another to have your products stuck in some invisible queue with zero feedback.

I see this pattern constantly. Brands get 5-10% of their catalog live through pure luck, then spend months trying to figure out what’s different about those products versus the ones that fail.

The truth? Those few products that went live just happened to avoid all the common pitfalls by accident.

Now, I’m going to show you exactly what causes these silent rejections and how to fix them before you upload.

Because chances are, you’re making the same mistakes.

Why Myntra Rejections Happen (The Truth Nobody Tells You)?

Let me walk you through each one – and more Before I give you the solutions, you need to understand something fundamental about Myntra’s system.

Myntra’s catalog upload is NOT a form-filling exercise.

I know it looks like one. You see an Excel template with fields. You fill them out. You upload. Simple, right?

Wrong.

Here’s what’s actually happening when you upload that Excel file:

Myntra’s system is checking your data against five different databases simultaneously:

Master Brand Registry – Is your brand spelled exactly as registered?
Style Group Taxonomy – Do your product variations group correctly?
Size Standardization Matrix – Are your sizes in the right sequence?
Color Code Mapping – Do your color names match their system?
Category Hierarchies – Does your product fit your authorized categories?

One mismatch = silent rejection or infinite “Under Review” status.

It’s like trying to unlock a door with five locks. Get four right and one wrong? Door stays locked. And worse – the system doesn’t always tell you which lock failed.

This is why sellers get so frustrated. Sometimes Myntra’s error messages don’t tell you which of the five locks failed. Your upload just shows “Processing” or “Under Review” forever, or products simply don’t appear in your active listings.

Myntra Products Not Showing After Approval?

The pattern I see repeatedly:

In cases like Rajesh’s, those 2-3 products that went live? They happened to have zero errors across all five validation checkpoints – purely by accident. Maybe someone on the team copy-pasted values correctly for those rows, or the size sequence happened to be right, or the Style Group ID was consistent.

The other 97? Each had at least one error, but the system wasn’t clearly communicating what or where.

After working with 200+ brands on Myntra over 15 years, I’ve identified 7 fatal mistakes that cause 87% of all rejections and silent failures.

re importantly, how to avoid them.

Fatal Mistake #1: "I'll Just Type the Brand Name"

This is where most people fail on Day 1, and they don’t even realize it.

What sellers typically do:
Open Excel. See “Brand” column. Type their brand name. Maybe it’s “Nike” or “NIKE” or “nike.”

Seems logical, right?

What actually happens:

Either immediate rejection with “Invalid brand value” OR (and this is worse) – the upload appears successful, but products never go live. They just sit in eternal “Processing” status.

Why this happens:

Myntra’s brand database doesn’t store brand names as simple text. It stores them as entity IDs – unique database identifiers.

When you type “Nike,” you’re creating a text string. The system is looking for Entity ID #47291 (or whatever Nike’s actual ID is in their database).

Sometimes it can’t find a match but doesn’t immediately reject – it just keeps your products in limbo hoping for manual review that may never come. Your products sit there for days, weeks, even months.

The fix:

ALWAYS use the dropdown menu. Never type manually in the brand field.

But wait – what if your brand doesn’t show up in the dropdown?

This is where most sellers get stuck. They think “my brand isn’t there, so I’ll just type it.”

Don’t.

Here’s what to do instead:

Go to your Myntra Seller Portal
Navigate to: Catalog → Bulk Upload
Look for “Master Brand Unhide Sheet” (it’s usually a small download link at the bottom of the page)
Download that Excel file
Use Ctrl+F to search for your brand name in that sheet
Copy the EXACT spelling – every capital letter, every space, every special character must be identical
Paste it into your catalog Excel file
Go back to the upload portal and refresh your dropdown
Your brand should now appear – select it from the dropdown

Real example from a client:

A skincare brand spent 3 weeks in confusion. Their products weren’t getting rejected with error messages – they just never appeared in the active listings after upload.

Turns out, they were typing “The Derma Co” in the brand field.

The registered name in Myntra’s system? “Derma Co” (without “The”).

Three weeks. Dozens of re-uploads. Countless frustrated support emails. All because of two characters that seemed insignificant.

And Myntra never explicitly said “brand name wrong” – products just silently failed to go live.

Pro tip: Create a “Brand Reference

Document” with the exact spelling from the Master Brand sheet. Make it mandatory for your team to copy-paste from this reference document – never allow manual typing.

Fatal Mistake #2: "Let Me Create Separate Listings for Each Color"

This mistake doesn’t just cause rejections – it’s also why some products randomly go live while others don’t, leaving sellers completely confused.

And this was exactly what created the 2-3 vs 97 split in Rajesh’s case.

Let me explain what happened.

What Rajesh’s team did:

They had multiple shoe designs, each available in 3-4 colors and 5-6 sizes.

For 2-3 products, by pure luck, someone on the team entered the SAME Style Group ID across all color/size variations. Those products consolidated properly into single listings and went live.

For the other 97 products? They made slight variations in the Style Group ID – sometimes adding extra characters, sometimes using different formats, sometimes just typos.

Example of what was actually in their Excel:

text

CORRECT (these 2-3 went live):

Row 1: SHOE001 | Black | 7 | SKU-SHOE001-BLK-7

Row 2: SHOE001 | Black | 8 | SKU-SHOE001-BLK-8

Row 3: SHOE001 | Brown | 7 | SKU-SHOE001-BRN-7

Row 4: SHOE001 | Brown | 8 | SKU-SHOE001-BRN-8

(All same Style Group ID – system created ONE listing with multiple options)

INCORRECT (these 97 silently failed):

Row 20: SHOE002 | Black | 7 | SKU-SHOE002-BLK-7

Row 21: SHOE002a | Black | 8 | SKU-SHOE002-BLK-8 ← Notice the “a”

Row 22: SHOE002 | Brown | 7 | SKU-SHOE002-BRN-7

Row 23: SHOE002A | Brown | 8 | SKU-SHOE002-BRN-8 ← Capital “A”

(Inconsistent Style Group IDs – system rejected as data corruption)

Rajesh’s team had no idea this was the problem. They thought they were doing everything right. After all, they were filling out all the fields!

Why this causes silent rejections:

Myntra’s system expects one product = one listing, no matter how many color or size variations exist.

When you have inconsistent Style Group IDs across what should be the same product:

System thinks you’re trying to create multiple separate listings for the same base product
Treats it as potential duplicate content or data corruption error
Silently rejects rather than creating a mess in their catalog
Doesn’t give you a clear error message because it can’t determine your intent

What the correct approach looks like:

All variations of the same product should get the EXACT SAME Style Group ID.

Here’s how it should look in your Excel:

text

Product: Premium Running Shoes

Style Group ID: PRSHOE001 (IDENTICAL for every single row)

Row 1: PRSHOE001 | Black | 6 | SKU-PRSHOE001-BLK-6

Row 2: PRSHOE001 | Black | 7 | SKU-PRSHOE001-BLK-7

Row 3: PRSHOE001 | Black | 8 | SKU-PRSHOE001-BLK-8

Row 4: PRSHOE001 | Brown | 6 | SKU-PRSHOE001-BRN-6

Row 5: PRSHOE001 | Brown | 7 | SKU-PRSHOE001-BRN-7

Row 6: PRSHOE001 | Brown | 8 | SKU-PRSHOE001-BRN-8

Row 7: PRSHOE001 | White | 6 | SKU-PRSHOE001-WHT-6

Row 8: PRSHOE001 | White | 7 | SKU-PRSHOE001-WHT-7

Row 9: PRSHOE001 | White | 8 | SKU-PRSHOE001-WHT-8

Critical rule: The Style Group ID must be EXACTLY identical for all variations. Even one character difference – one space, one capital letter vs lowercase, one extra number – creates problems.

The fix I use:

Create a master SKU naming convention document before uploading anything:

[BRAND]-[PRODUCT]-[COLOR]-[SIZE]

Example: NIKE-RUNSHOE-BLK-8

And use Excel formulas to auto-generate Style Group IDs so there’s zero room for human error:

excel

=A2&”-“&B2

This prevents typos and ensures consistency across hundreds of rows without relying on manual data entry.

Fatal Mistake #3: "Size Order Doesn't Matter, Right?"

This is another silent killer that leaves sellers completely baffled about why their products aren’t going live.

What sellers typically do:

Upload sizes in whatever order makes sense to them – maybe the order products are packed, or the order they’re popular, or just random.

Example: 8, 7, 9, 6, 10

Makes sense from an operations perspective, right?

What happens:

Myntra’s system flags it as invalid data structure. No error message. Products just don’t go live.

Why Myntra is so strict about this:

Myntra’s system expects sizes in a standardized logical order for two critical reasons:

Customer experience – When someone filters by size, results need to display consistently across all brands and categories
Warehouse automation – Their fulfillment system relies on standardized size codes for automated picking and packing

If sizes aren’t in the expected sequence, the system assumes data corruption and rejects.

Standard apparel size sequence:

XS → S → M → L → XL → XXL → 3XL → 4XL → 5XL

For footwear – this is EXTRA critical:

Myntra expects Indian sizing standards in ascending order:

6 → 7 → 8 → 9 → 10 → 11

NOT random order: 8, 7, 9, 6, 10
NOT UK half-sizes: 6, 6.5, 7, 7.5, 8
NOT US sizing conversions

The ₹3.2 lakh mistake:

Here’s what actually caused the majority of Rajesh’s specific silent rejections:

His products came with UK size labels (6, 6.5, 7, 7.5, 8, 8.5, 9…). His team uploaded them exactly as the labels showed – seemed like the honest, accurate thing to do.

Myntra’s system expected Indian sizing (6, 7, 8, 9, 10).

But here’s the frustrating part – Myntra didn’t explicitly reject with “wrong sizing format.” The products just never went live. They sat in “Processing” or “Under Review” status indefinitely.

When I audited the failed uploads:

text

What was uploaded:

Size: 6.5, 7, 7.5, 8, 8.5, 9

What Myntra’s system expected:

Size: 6, 7, 8, 9, 10

The half sizes (6.5, 7.5, 8.5) don’t exist in Indian footwear sizing standards for most categories. The system couldn’t map them to its standardized size database, so it just… rejected silently.

No error. No explanation. Just crickets.

The costly fix:

Returning all inventory from Myntra’s warehouse: ₹45,000
Re-labeling all 150 SKUs with Indian size stickers: ₹85,000
Re-shooting product photos showing correct size labels: ₹1,20,000
Re-creating entire catalog with proper sizing
Re-uploading everything
Re-sending inventory to warehouse

Total damage: ₹3.2 lakhs + 6 weeks of lost time + 4 months of missed sales opportunity

What should have been done:

30 minutes of research into Myntra’s category-specific size requirements BEFORE manufacturing product labels.

Cost: ₹0 + 30 minutes.

The prevention system:

Create a size reference template:

text

Product Category: Footwear – Men’s Casual Shoes

Myntra Standard: Indian Sizing Only

Acceptable Sizes (in order):

Size_Order | Size_Display | Notes

1 | 6 | Upload first
2 | 7 | Upload second
3 | 8 | Upload third
4 | 9 | Upload fourth
5 | 10 | Upload fifth
6 | 11 | Upload sixth

NOT Acceptable:

× 6.5, 7.5, 8.5 (UK half-sizes)

× US size conversions

× European sizes

Before uploading any catalog, sort your entire product list by the “Size_Order” column. This ensures sizes always appear in the correct sequence that Myntra’s system expects.

One seller I know had this printed out and laminated next to their operations desk. Zero size-related rejections in 18 months.

Fatal Mistake #4: "Capitalization? Does That Really Matter?"

Short answer: Yes. Absolutely, frustratingly, yes.

And most sellers don’t realize this until they’ve wasted weeks.

What sellers typically do:

Mix capitalization randomly because “it’s just text, right?”

Brand: “NIKE” or “nike” or “NiKe”
Title: “premium cotton t-shirt” or “PREMIUM COTTON T-SHIRT” or “Premium Cotton T-Shirt”
Color: “red” or “RED” or “Red”

What actually happens:

Myntra’s system is case-sensitive. It’s looking for exact matches against its database.

“Nike” ≠ “NIKE” ≠ “nike”

They’re treated as three completely different values in the database.

Sometimes you’ll get an explicit rejection. More often? Silent failure. Products just don’t go live.

The strict rules:

For Brand Names:
First letter capital, rest lowercase

✓ Nike
✗ NIKE
✗ nike
✗ NiKe

3. For Product Titles:
4. First letter of each major word capitalized (like a book title)

✓ Premium Cotton T-Shirt
✗ premium cotton t-shirt
✗ PREMIUM COTTON T-SHIRT
✗ Premium cotton t-shirt

5. For Colors:
6. First letter capital, rest lowercase

✓ Red
✗ red
✗ RED

Exception to watch for:

Some brands are actually registered in ALL CAPS in Myntra’s master registry (like FCUK, USPA, DNMX).

Always check the dropdown to see the exact registered format. Don’t assume.

Real scenario:

An apparel brand had 45 products. 12 went live, 33 didn’t.

The 12 that worked? Someone on their team had used “Nike” (correct capitalization).

The 33 that failed? Same person had typed “NIKE” in all caps – maybe they hit caps lock by accident, who knows.

Same brand. Same products. Different capitalization. 33 silent rejections.

They spent 2 weeks trying to figure out what was wrong with those specific 33 products – checking images, dimensions, descriptions. Everything looked fine.

The culprit? Four characters in the wrong case.

The Excel hack that prevents this:
Use the PROPER function for titles:

excel

=PROPER(A2)

This auto-converts “premium cotton t-shirt” to “Premium Cotton T-Shirt”

For brand names, don’t use formulas – copy-paste EXACT spelling from the Master Brand dropdown. Every single time.

Fatal Mistake #5: "Let Me Write a Detailed, Descriptive Product Title"

Details are good. Too detailed gets you silently rejected.

The hard rule:

Product title (called “Vendor Article Name” in Myntra’s system) must be 85 characters or less.

Not 86. Not 90. Not “approximately 85.”

Exactly 85 or less.

And yes – spaces count, punctuation counts, everything counts.

What sellers do:

Write descriptive titles trying to include every feature:

“Premium Quality 100% Pure Organic Cotton Round Neck Half Sleeve Casual Regular Fit T-Shirt for Men Summer Collection 2024 Breathable Fabric”

Character count: 156

What happens: Silent rejection or truncation that breaks the listing.

The frustrating part:

Myntra doesn’t always tell you “title too long.” Sometimes the upload appears successful, but the product never goes live. You’re left wondering what’s wrong.

What works:

“Premium Organic Cotton Round Neck Half Sleeve Men’s Casual T-Shirt Summer 2024”

Character count: 83

Gets approved. Ranks well. Converts.

The strategic approach:

The first 60 characters carry the most weight in Myntra’s search algorithm.

Structure your titles like this:

[Primary Keyword] [Material] [Style Descriptor] [Product Type] [Use Case/Season]

Example: “Premium Cotton Round Neck T-Shirt Casual Summer 2024”

Excel formula to check character count:

excel

=LEN(A2)

Add this in a column next to your product titles. If any show >85, you must shorten before uploading.

Pro tip: Set up conditional formatting in Excel:

text

If LEN(A2) > 85, highlight cell in RED

If LEN(A2) <= 85, highlight cell in GREEN

Visual validation before you even attempt to upload.

Fatal Mistake #6: "I'll Upload Men's Products Under My Women's Category Agreement"

This one gives you the most cryptic, unhelpful error message in Myntra’s entire system:

“BU Validation Failed”

What does that even mean? Most sellers have no clue.

What’s actually happening:

When you are onboard on Myntra, you sign a Category and Type Agreement (CTA). This legal document specifies exactly which product categories you’re authorized to sell.

Example CTA might say:

Women’s Western Wear ✓
Women’s Ethnic Wear ✓
Women’s Accessories ✓

That’s it. That’s all you’re authorized for.

Now, if your team tries to upload a Men’s T-Shirt (maybe by mistake, maybe thinking “it’s all apparel”), here’s what happens:

Myntra’s system checks: “Does this seller have authorization for Men’s Apparel category?”

Answer: No.

Result: “BU Validation Failed” error.

But here’s the problem – the error message doesn’t explain WHAT validation failed or WHY. You’re just stuck with this cryptic message.

Real scenario:

A multi-brand seller had authorization for Women’s categories. They hired a new operations person who started uploading their entire catalog – including men’s products.

Women’s products: Went live fine.
Men’s products: “BU Validation Failed”

The new employee had no idea what this meant. Spent a week checking Excel formatting, brand names, everything. The error message gave zero clues.

Finally someone thought to check the original CTA document. Realized men’s categories weren’t authorized.

One week was wasted because the error message was useless.

The prevention system:

Download your CTA document (check your onboarding email or request from account manager)
Create a simple, clear reference sheet that anyone on your team can understand:

text

OUR AUTHORIZED CATEGORIES:

✓ Age Group: Women

✓ Category: Apparel

✓ Sub-categories: Tops, Dresses, Jeans, Kurtas, Ethnic Wear

NOT AUTHORIZED (will get “BU Validation Failed”):

✗ Men’s anything

✗ Kids’ anything

✗ Home & Living

✗ Beauty & Personal Care

Before uploading ANY catalog, have someone cross-check every product against this reference sheet
Train your team: “If it’s not explicitly on the authorized list, DON’T upload it”

Want to expand into new categories?

You need to formally request it:

Raise a support ticket: Category “Category Addition Request”
Provide business justification (sample product catalog, projected sales volumes, market demand data)
Wait 7-10 business days for review and approval
Only AFTER approval, upload products in that category

Don’t try to upload first and hope it works. It won’t.

Fatal Mistake #7: "I'll Fill in Keywords Later" (The Permanent Visibility Killer)

This is the mistake that haunts sellers for months or even years after their products go live.

Here’s what most sellers don’t know:

Myntra has a backend field called “Tags” or “Search Terms” where you can add keywords that determine whether customers can find your product.

The devastating catch:

You can ONLY add these keywords during initial catalog creation.

Once your listing goes live, you cannot edit or add keywords – not through the portal, not through support tickets, not ever – without completely delisting and relisting the entire product (losing all your reviews, sales history, and ranking in the process).

Where this field is located:

In the catalog creation form, scroll down to “Additional Information” section.

There’s a field labeled “Tags” or “Search Terms.”

It’s usually below the fold. Easy to miss. Most sellers scroll right past it.

What happens when you leave it blank:

Your product goes live. Looks fine. All the visible information is there.

But when customers search, your product barely appears.

Real impact:

Product WITHOUT backend keywords: Shows up in 15-20 customer searches
Product WITH optimized keywords: Shows up in 150-200 customer searches

That’s a 10x difference in visibility.

Real scenario:

A men’s casual wear brand uploaded 45 products. All went live successfully. They were excited.

Month 1: ₹80,000 GMV (disappointing, but “it’s early days”)
Month 2: ₹95,000 GMV (barely any growth)
Month 3: ₹1,10,000 GMV (still underwhelming)

Meanwhile, their competitors with similar products were doing ₹5-8 lakhs monthly.

Why?

They’d left the “Tags” field blank during upload. Their products were invisible in most customer searches.

By the time they discovered this (month 4), they faced a horrible choice:

Option A: Keep products live with terrible visibility, accept slow growth
Option B: Delist all 45 products, lose all sales history and the few reviews they’d gotten, relist with proper keywords, start from scratch
They chose Option B. Lost 4 months of momentum.

How to optimize this field (you get ONE shot):

Character limit: Approximately 250 characters (varies slightly by category)

What to include:

Spelling variations (20% of characters):
- T-shirt, Tshirt, Tee, Tee-shirt
Material variations (20% of characters):
- Cotton, pure cotton, 100% cotton, organic cotton
Use case keywords (30% of characters):
- Casual wear, office wear, party wear, gym wear, daily wear, sports
Style descriptors (20% of characters):
- Round neck, V-neck, half sleeve, full sleeve, slim fit, regular fit
Regional/vernacular terms (10% of characters):
- This is what most brands miss completely
- Example: For ethnic wear, include “kurta” plus “traditional wear” plus “Indian wear”

Example for Men’s Cotton T-Shirt:

text

men tshirt, mens tee, cotton tshirt for men, round neck tshirt, half sleeve tshirt, casual tshirt, summer tshirt, daily wear tshirt, gym tshirt, sports tee, plain tshirt, solid tshirt, comfortable tshirt, breathable fabric, premium cotton, branded tshirt, regular fit, men casual wear, summer collection

Character count: 247 (within limit)

How to research the right keywords:

Don’t guess. Do this:

Open Myntra website/app
Search for products similar to yours
Note the top 20 results
Look at what terms appear in their titles
Check the “Related Searches” section
Use those exact terms in your tags field

Takes 20-30 minutes per product category. Worth every second.

CRITICAL WARNING:

Once you click “Submit” on your catalog, these keywords are PERMANENTLY LOCKED.

I’ve worked with brands that had to relist products worth ₹50+ lakhs in GMV just to fix keyword optimization they’d missed initially.

Don’t be that brand.

Fill this field completely and strategically BEFORE your first upload.

The Master Pre-Upload Checklist (Print This and Use It Every Single Time)

Here’s the checklist that’s prevented thousands of rejections across the brands I work with:

Before You Upload – Validate These Points:

Brand & Basic Info:

Brand name selected from dropdown (NEVER typed)
Brand spelling matches Master Brand sheet exactly
Product title ≤ 85 characters (use =LEN formula to verify)
Product title follows capitalization rules (first letter of each word)

Style Group & SKU:

Style Group ID IDENTICAL across all color/size variations of same product
No typos in Style Group ID (use copy-paste, not manual typing)
SKU codes follow consistent naming convention
SKU codes are unique (no duplicates)

Size & Color:

Sizes in correct sequential order (use Size_Order reference sheet)
No sizes skipped in the sequence
Size format matches category standards (Indian sizing for footwear, etc.)
Color names selected from dropdown
Color capitalization correct (first letter capital only)

Category Authorization:

Age Group matches your CTA (don’t upload Men’s if authorized for Women’s)
Category matches your CTA
Sub-category matches your CTA
Cross-checked against authorized categories reference sheet

The Killer Fields (Most Often Missed):

Backend Keywords/Tags field completely filled (250 characters used)
Keywords researched from competitor listings
Regional/vernacular terms included
Spelling variations included

Final Checks:

All mandatory fields filled (absolutely zero blanks)
Ran character count formula on titles
Sorted by Size Order before finalizing
Double-checked Style Group consistency
Saved master copy before uploading

Time investment: 20-25 minutes for a 100-SKU upload

Time saved: 2-4 weeks of rejection cycles, re-uploads, and support tickets

The ROI is obvious.

Problem: Lot Rejections - When Excel Uploads But Products Still Don't Go Live

So you’ve fixed all the Excel issues I mentioned above. You’ve been careful. You’ve validated everything.

You hit upload.

System says: “Upload Successful”

You breathe a sigh of relief.

Then 6-8 hours later, you check the status.

“Lot Not Accepted” or worse – no status at all, products just don’t appear.

Welcome to the second layer of Myntra rejection hell.

What's Actually Happening (The System Architecture)

When you upload a catalog, Myntra’s system processes it in multiple stages:

Stage 1: File format validation

Is it actually an Excel file?
Is file size within limits?
Does it have the required columns?

Stage 2: Data syntax validation

Do dropdown values match the database?
Are character limits respected?
Is the data in the correct format?

Stage 3: Lot validation (this is where most “successful” uploads fail)

Duplicate SKU checks
Inventory system compatibility checks
Brand authorization verification
Image file validation

Stage 4: Image processing and product activation

Here’s the frustrating part:

Your upload can pass Stages 1 and 2 (so the system says “Upload Successful”), but fail at Stage 3.

You think everything worked. But your products never go live.

Let me show you the 5 most common lot rejection reasons – and how to fix them.

Lot Rejection Reason #1: "Duplicate SKU Found"

What the error means:

Another product in Myntra’s system (could be yours from a previous upload, or rarely, another seller’s) is already using this exact SKU code.

How this typically happens:

Scenario A: You uploaded products before, they got rejected, now you’re re-uploading with the same SKU codes

The problem? Myntra’s system doesn’t automatically delete rejected products immediately. They stay in the database for 30-90 days. So when you re-upload with the same SKUs, the system sees “duplicate.”

Scenario B: You’re using generic, simple SKU codes

Like “RED-M-001” or “TSHIRT-001”

Chances are, another seller already used these exact codes. Myntra’s SKU database is shared across all sellers in some cases.

Scenario C: You uploaded the same product twice by mistake

Maybe different team members uploaded the same catalog, or you uploaded, didn’t see products go live, assumed it failed, and uploaded again.

Real example:

An apparel brand uploaded 80 SKUs. Got a lot of rejection on all 80.

Error: “Duplicate SKU Found”

They were confused – “This is our first upload ever!”

Turns out, two weeks earlier, someone on their team had done a “test upload” of 10 products. Those SKUs were still in Myntra’s system (in a rejected state). When they uploaded the full catalog, 10 SKUs were flagged as duplicates.

The other 70? Also rejected because Myntra’s lot validation is all-or-nothing. One duplicate = entire lot rejected.

How to check if SKUs already exist:

Go to Myntra Seller Portal
Navigate to: Catalog → Manage Inventory
Use the search function to check each SKU
If it shows up (even with status “Rejected” or “Inactive”), it’s already in the system
You need to either:
- Delete the old entry (if it’s yours), OR
- Use completely new SKU codes

The permanent fix:

Create unique SKU codes using this formula:

[Brand Code]-[Product Code]-[Color Code]-[Size Code]-[Date Code]

Example: NIKE-TSHRT-RED-M-052024

The date code (May 2024) makes it unique even if you upload similar products later.

Or use this approach:

[Brand Code]-[Random 6-digit number]-[Color]-[Size]

Example: NIKE-847362-RED-M

The random number ensures you’ll never have duplicates, even across different uploads.

Lot Rejection Reason #2: "Image Not Found or Image Error"

This is one of the most common lot rejections, and it’s completely preventable.

What triggers this:

Problem A: Image file names don’t match SKU codes in your Excel

Your Excel says: SKU-NIKE-TSHRT-RED-M

Your image file is named: nike_tshirt_red_m.jpg

They don’t match exactly → Rejection

Problem B: Images not uploaded to the correct folder path

Myntra expects images in a specific folder structure. If you just dump all images in one folder, the system can’t map them to products.

Problem C: Image format doesn’t meet requirements

You uploaded PNG files. Myntra only accepts JPEG/JPG for most categories.

Problem D: Image file size outside acceptable range

Too small (<100 KB) or too large (>10 MB) → Rejection

Myntra’s exact image requirements:

Format: JPG or JPEG only (not PNG, not WEBP, not BMP)
Background: Pure white (#FFFFFF – will explain why this matters in a minute)
Resolution: Minimum 1000 x 1400 pixels
Aspect Ratio: 5:7 preferred (but system accepts some variation)
File Size: Between 500 KB and 5 MB per image
File Naming: Must EXACTLY match the SKU code from your Excel

Critical naming example:

text

Excel SKU code: XYZBRAND-TSHRT-RED-M-001

Image files MUST be named:

XYZBRAND-TSHRT-RED-M-001_1.jpg (front view)
XYZBRAND-TSHRT-RED-M-001_2.jpg (back view)
XYZBRAND-TSHRT-RED-M-001_3.jpg (side view)
XYZBRAND-TSHRT-RED-M-001_4.jpg (detail shot)

NOT acceptable:

xyz_brand_tshirt_red_m_001.jpg
XYZBRAND-TSHRT-RED-M-001.JPG (capital JPG extension)
XYZBRAND-TSHRT-RED-M-001 (1).jpg (space before number)

Upload folder structure:

text

Main Upload Folder

Style_Group_ID_STYLE001 (folder name must be Style Group ID)

├── SKU001_1.jpg
├── SKU001_2.jpg
├── SKU001_3.jpg
├── SKU001_4.jpg
├── SKU002_1.jpg
├── SKU002_2.jpg
└── (etc.)

Real scenario that cost ₹45,000:

A footwear brand uploaded their catalog. Everything looked good in the Excel.

Lot rejection: “Image Error“

They checked – images were uploaded. File names matched SKUs. What was wrong?

After investigation: Their images were 800 x 1000 pixels.

Myntra’s minimum requirement: 1000 x 1400 pixels.

They had to:

Re-shoot all 120 products at higher resolution
Re-edit images to proper dimensions
Re-upload everything

Cost: ₹45,000 for photography + 2 weeks delay

What they should have done: Checked image requirements BEFORE the photoshoot.

Pro tip for bulk image renaming:

If you have 500 product images with wrong names, don’t rename manually.

Use a bulk renaming tool:

Windows: Use PowerToys (free Microsoft tool)
Mac: Use Automator or NameChanger (free)
Online: Bulk Rename Utility websites

Create a CSV mapping file:

text

Old_Name,New_Name

IMG_001.jpg,NIKE-TSHRT-RED-M-001_1.jpg
IMG_002.jpg,NIKE-TSHRT-RED-M-001_2.jpg

Bulk rename in 2 minutes instead of 2 hours.

Lot Rejection Reason #3: "Style Group Conflict"

This error is cryptic and confusing, but here’s what it actually means:

What triggers it:

You’re trying to add variations to a Style Group that already exists in the system with different product attributes.

Common scenario:

Previous upload (2 months ago):

Style Group: TSHRT001
Product: Cotton T-Shirt
Material: 100% Cotton
Color: Red, Blue

New upload (today):

Style Group: TSHRT001 (same ID)
Product: Polyester T-Shirt
Material: 100% Polyester
Color: Red, Blue

System rejects because: “You’re using the same Style Group ID for two fundamentally different products (Cotton vs Polyester). This is a data conflict.”

The rule:

Use UNIQUE Style Group IDs for DIFFERENT products

Reserve the SAME Style Group ID ONLY for color/size variations of the IDENTICAL product

What’s considered “different products”:

Different materials (cotton vs polyester)
Different styles (round neck vs V-neck)
Different fits (slim fit vs regular fit)
Different product types entirely (t-shirt vs shirt)

What’s considered “same product” (can share Style Group ID):

Different colors of the exact same design
Different sizes of the exact same design
That’s it. Nothing else.

Example of correct Style Group usage:

text

Product 1: Premium Cotton Round Neck T-Shirt

Style Group: PCTS-RN-001

Colors: Red, Blue, Black

Sizes: S, M, L, XL

(All these 12 variations use the same Style Group ID)

Product 2: Premium Cotton V-Neck T-Shirt

Style Group: PCTS-VN-002 (DIFFERENT Style Group ID)

Colors: Red, Blue, Black

Sizes: S, M, L, XL

(All these 12 variations use this new Style Group ID)

Product 3: Premium Polyester Round Neck T-Shirt

Style Group: PPTS-RN-003 (DIFFERENT Style Group ID)

Colors: Red, Blue, Black

Sizes: S, M, L, XL

Real scenario:

A brand uploaded 60 products. 30 went live perfectly. 30 got “Style Group Conflict” error.

Confusion: “Why did half work and half fail?”

Turns out: The 30 that worked were using new Style Group IDs (STYLE001, STYLE002, etc.)

The 30 that failed were using Style Group IDs they’d used in a previous upload 6 months ago for different products.

Myntra’s system remembered those old Style Group IDs and rejected the new upload as conflicting data.

The fix:

Always use fresh, unique Style Group IDs for new products. Never recycle old IDs unless you’re genuinely adding color/size variations to an existing product.

Tracking system I recommend:

Maintain a “Style Group Registry” spreadsheet:

text

Style_Group_ID | Product_Description | Date_Created | Status
PCTS-RN-001 | Cotton Round Neck Tee | 05/01/2024 | Active
PCTS-VN-002 | Cotton V-Neck Tee | 05/01/2024 | Active
PPTS-RN-003 | Poly Round Neck Tee | 05/15/2024 | Active

Before creating a new upload, check this registry to ensure you’re not reusing IDs.

Lot Rejection Reason #4: "Missing Mandatory Attributes"

This rejection is sneaky because the mandatory fields vary by category.

What’s mandatory for t-shirts might be optional for jeans. What’s mandatory for footwear is different from home furnishing.

Common mandatory fields that sellers miss:

For Apparel (Tops/T-Shirts):

✗ Sleeve Length (Short Sleeve, Long Sleeve, Sleeveless, 3/4 Sleeve)
✗ Neck Type (Round Neck, V-Neck, Collar, Boat Neck)
✗ Pattern (Solid, Printed, Striped, Checked, Embroidered)
✗ Fit Type (Slim Fit, Regular Fit, Loose Fit, Oversized)
✗ Fabric (Cotton, Polyester, Blend, Silk)

For Footwear:

✗ Sole Material (Rubber, PU, TPR, Leather)
✗ Upper Material (Leather, Canvas, Mesh, Synthetic)
✗ Closure Type (Lace-up, Slip-on, Velcro, Buckle)
✗ Heel Height (for women’s footwear – in cm)
✗ Toe Shape (Round, Pointed, Square)

For Home Furnishing (Bedsheets):

✗ Thread Count (mandatory – can’t leave blank)
✗ Fabric Type (Cotton, Polyester, Silk, Blend)
✗ Sheet Type (Flat Sheet, Fitted Sheet, Elastic)
✗ Bed Size (Single, Double, Queen, King)
✗ GSM (fabric weight)
✗ Number of pieces (1 bedsheet + 2 pillow covers = 3 pieces)

The frustrating part:

If you leave even ONE mandatory field blank, the entire lot gets rejected.

And Myntra’s error message often just says “Missing Mandatory Attributes” without specifying WHICH attributes.

Real example:

An ethnic wear brand uploaded 75 kurtas. All rejected.

Error: “Missing Mandatory Attributes”

They checked their Excel – every visible field was filled!

After hours of investigation: They’d left the “Sleeve Length” field blank.

For kurtas in the “Women’s Ethnic Wear” category, sleeve length is mandatory. They didn’t know.

How to find category-specific mandatory fields:

Go to Myntra Seller Portal
Navigate to: Catalog → Bulk Upload
Download the category-specific template for your exact product category
Open the template Excel
Look for column headers with red asterisks (*) or bold text – these are mandatory
Fill ALL of them, even if they seem unimportant

Pro tip:

Different categories under the same age group can have different mandatory fields.

Example:

Women’s T-Shirts: Sleeve Length is mandatory
Women’s Jeans: Sleeve Length is not applicable, but Rise (Low Rise, Mid Rise, High Rise) is mandatory

Always download the specific template for your exact sub-category.

Prevent this rejection:

Before uploading, run a “blank cell check” in Excel:

Select your entire data range
Press Ctrl+G (Go To)
Click “Special”
Select “Blanks”
Click OK

All blank cells in your selection will be highlighted.

If any are in mandatory columns → Fill them before uploading.

Lot Rejection Reason #5: "Manufacturer/Packer Address Issue"

This is a legal compliance requirement that many sellers don’t take seriously – until their entire lot gets rejected.

What’s required by Indian e-commerce law:

Every product listing must display:

Complete manufacturer name and address
Packer name and address (if different from manufacturer)
Country of origin
Importer details (for international products)
Customer care contact information

Common mistakes:

Mistake A: Incomplete address

❌ “ABC Garments, Delhi”

✓ “ABC Garments Pvt Ltd, Plot No. 45, Sector 18, Industrial Area, Gurugram, Haryana – 122015, India”

Mistake B: Using seller address instead of actual manufacturer address

If your brand is manufactured by a third party, you must use their address, not your office address.

Mistake C: Vague or generic addresses

❌ “Manufactured in India”

✓ Specific factory location with PIN code

Mistake D: Missing PIN code

The PIN code is mandatory. Without it, rejection.

The correct format:

text

Manufacturer Name: XYZ Garments Pvt Ltd

Address: Plot No. 45, Sector 8, IMT Manesar, Gurugram, Haryana – 122050

Country of Origin: India

Packer: Same as Manufacturer

(or if different:)

Packer Name: ABC Packaging Solutions

Address: Unit 12, Industrial Estate, Okhla, New Delhi – 110020

Customer Care: +91-1234567890

Email: care@xyzbrand.com

Where to include this information:

Option 1: In the dedicated “Legal Information” or “Manufacturer Details” fields in your Excel template

Option 2: In the product description (but must also be in dedicated fields if they exist)

Option 3: As text overlay on one of your product images (small print at bottom is acceptable)

Category-specific strictness:

High strictness (rejections are common):

Baby products
Personal care & cosmetics
Food & nutrition
Innerwear

Medium strictness:

Apparel
Footwear
Accessories

Lower strictness (but still required):

Home décor
Electronics accessories

Real scenario:

A home furnishing brand uploaded 90 bedsheet sets.

Manufacturer address field: “Made in India”

Result: 100% lot rejection for “Incomplete Legal Information”

They had to:

Contact their manufacturer for complete address
Update all 90 product entries
Re-upload
Wait another 48 hours for review

Lost: 5 days

The prevention system:

Create a “Legal Information Template” document and use it consistently:

text

LEGAL INFO – BRAND XYZ

Manufacturer:

XYZ Textiles Manufacturing Pvt Ltd

Plot No. 78, Phase 2, Industrial Area

Bhiwadi, Rajasthan – 301019

India

Packer:

Same as Manufacturer

Country of Origin: India

Customer Care:

Phone: +91-9876543210

Email: support@xyzbrand.com

Working Hours: Mon-Sat, 10 AM – 6 PM IST

Importer (if applicable):

Not Applicable (Domestic Product)

Save this as a text file. For every catalog upload, copy-paste this EXACT text into the manufacturer/legal fields.

Zero typos. Zero variations. Zero rejections.

Pro tip: If you work with multiple manufacturers for different product lines, create separate templates:

text

LEGAL_INFO_MANUFACTURER_A.txt
LEGAL_INFO_MANUFACTURER_B.txt
LEGAL_INFO_MANUFACTURER_C.txt

Before uploading a catalog, identify which manufacturer made those products, then copy-paste the correct template.

How to Actually Find Rejection Details? (Most Sellers Don't Know This)

Here’s the problem: Myntra’s system shows “Lot Not Accepted” but doesn’t always show you WHY.

Most sellers give up at this point. They don’t know where to look for the actual error details.

Here’s the exact navigation path:

Step 1: Log into Myntra Seller Portal

Step 2: Navigate to: Catalog → Catalog Activity

Step 3: Find your uploaded lot (usually shows with status “Processing” initially, then changes to “Not Accepted” or “Rejected”)

Step 4: Click on the lot name/number

Step 5: Look for a button/link that says “View Details” or “Download Error Report”

Step 6: Click it – this downloads an Excel file with SKU-level rejection reasons

What this error report contains:

text

SKU_Code | Status | Rejection_Reason | Suggested_Action
SKU001 | Failed | Duplicate SKU | Use unique SKU code
SKU002 | Failed | Image not found | Upload image with exact SKU name
SKU003 | Failed | Missing attribute: Sleeve Length | Fill mandatory field

This report is GOLD. It tells you exactly what’s wrong with each specific SKU.

The fix workflow:

Download the rejection report
Filter by “Status” column to see only “Failed” items
Create a new Excel tab called “FIXES_NEEDED”
Copy all failed rows to this tab
Add a column called “Action_Taken”
Fix each issue one by one, documenting what you did
Create a fresh upload with ONLY the corrected rows
Use a NEW Lot ID (don’t reuse the rejected lot ID)

Example of tracking your fixes:

text

SKU | Original_Issue | Action_Taken | Status
SKU001 | Duplicate SKU | Changed to SKU001-V2 | Ready
SKU002 | Image missing | Uploaded image SKU002_1.jpg | Ready
SKU003 | Sleeve Length blank | Added “Half Sleeve” | Ready

Once all show “Ready,” create your corrected upload.

Important: Don’t try to re-upload the ENTIRE original lot with fixes. Upload ONLY the failed SKUs after correcting them. The ones that were already accepted don’t need to be touched.

The Re-Upload Strategy That Actually Works

Most sellers make this mistake:

They fix the errors, then immediately re-upload using the same Lot ID or same file name.

Why this fails:

Myntra’s system sometimes “remembers” rejected Lot IDs. It sees the same Lot ID coming back and may auto-reject without even re-checking your fixes.

The correct re-upload process:

Step 1: Create a completely NEW Excel file (don’t just edit the old one)

Step 2: Copy ONLY the corrected rows from your fix tracker

Step 3: Generate a NEW Lot ID

Step 4: Use a different file name

Step 5: Upload as a fresh submission

Example:

text

Original Upload:

File: Myntra_Catalog_May2024.xlsx
Lot ID: LOT001
Result: Rejected
Corrected Upload:
File: Myntra_Catalog_May2024_V2_Corrected.xlsx
Lot ID: LOT001-R1 (or completely new: LOT015)
Result: Much higher acceptance rate

Why this works:

You’re giving the system a fresh validation run instead of triggering any cached rejection flags.

Timeline expectations:

Upload new corrected file
Wait 24-48 hours for processing
Check Catalog Activity for status
If still issues, download new error report and repeat

Pro tip: Don’t upload corrections late Friday evening or on weekends. Myntra’s QC team operates primarily Monday-Friday. Weekend uploads often sit in queue until Monday, delaying your feedback by 2-3 days.

Your Action Plan: What to Do Right Now

If you’re reading this and haven’t uploaded yet:

Step 1: Print out the “Master Pre-Upload Checklist” from earlier in this blog

Step 2: Download Myntra’s category-specific Excel template for your exact product category

Step 3: Research size standards for your category (especially important for footwear and apparel)

Step 4: Create your “Brand Reference Sheet” with exact spelling from Master Brand list

Step 5: Create your “Legal Information Template” with complete manufacturer address

Step 6: Do a test upload of 5-10 products before uploading your full catalog

If you’ve already uploaded and facing rejections:

Step 1: Download your rejection error report (Catalog → Catalog Activity → View Details)

Step 2: Create a “FIXES” tracker spreadsheet to document issues and corrections

Step 3: Fix issues systematically – don’t rush

Step 4: Create a completely NEW upload file with corrected data only

Step 5: Use a fresh Lot ID for the corrected upload

Step 6: Wait 48 hours before raising support ticket (give the system time to process)

If you’re completely stuck:

Don’t keep trying the same thing expecting different results.

Reach out to someone who’s done this before. Whether it’s me or another Myntra consultant, get expert eyes on your catalog before you waste more weeks.

The difference between 3% success rate and 95% success rate isn’t your products. It’s knowing these systems.

In the next blog, I’ll cover:

PMR Issues – The rejection that happens AFTER your products are approved

This is even more frustrating than lot rejections because your products show as “Active” in your dashboard, inventory is uploaded, everything looks live… but customers can’t actually see or buy your products.

I’ll show you:

The 8 most common PMR rejection reasons
Why home furnishing (especially bedsheets) has 68% PMR rejection rate
The exact image requirements that most sellers get wrong
How to fix PMR issues without delisting and losing your sales history
The PMR resolution workflow that actually works

Because getting products past the Excel and Lot stages is just the beginning. PMR is where the real complexity starts.

Stay tuned.

Screenshot plan (4–6 images for E‑E‑A‑T)
Capture these screens (blur IDs/emails/brand names):

Catalog → Bulk Upload: where to find Master Brand list and category templates
Catalog → Catalog Activity: where to download the Error Report
Lot details modal: “View Details / Download Error Report” button
Manage Inventory: searching a SKU to check duplicates
Upload image structure example: folder named as StyleGroupID with SKU_1.jpg, SKU_2.jpg
Category template snippet: showing mandatory columns (asterisks)

Answer Engine Optimization (AEO): quick‑answer block for top queries
Add this “Quick answers” section right under the H1 for featured snippets and AI overviews:

What does “BU Validation Failed” mean on Myntra?
You tried to upload a product outside your approved Category & Type Agreement (CTA). Upload only within authorized categories or request category addition, then re‑upload.
Why are my Myntra products stuck “Under Review ” or vanishing?
A database mismatch in brand, style group, size order, color mapping, or category authorization. Validate brand from dropdown, identical Style Group IDs, size sequence, mandatory fields, and image rules.
How do I fix “Lot Not Accepted”?
Download the error report (Catalog → Catalog Activity), fix duplicate SKUs, image naming/size, style group conflicts, and missing attributes. Re‑upload as a new lot/file name.
What is a Style Group ID on Myntra?
The ID that groups every color/size of the same product. It must be identical for all variations; never reuse it across different products.
Title length rule on Myntra?
Vendor Article Name ≤85 characters. Keep key terms in the first 60 characters.

Search

Categories

Latest Posts

Increase Sales on Myntra in 2026 | Sale Calendar & Seller Guide

How to Sell on Blinkit? Complete Seller Registration & Onboarding Guide 2026

Myntra Products Not Showing After Approval? Fix PMR Holds & Visibility Issues

Why Your Myntra Products Get Rejected?(and How to Fix Them)?

How to Sell on Myntra 2026? Fast Registration & Approval Guide

Quick Enquiry

Why Your Myntra Products Get Rejected and How to Fix Them?

Why Myntra Rejections Happen (The Truth Nobody Tells You)?

Fatal Mistake #1: "I'll Just Type the Brand Name"

Fatal Mistake #2: "Let Me Create Separate Listings for Each Color"

Fatal Mistake #3: "Size Order Doesn't Matter, Right?"

Fatal Mistake #4: "Capitalization? Does That Really Matter?"

Fatal Mistake #5: "Let Me Write a Detailed, Descriptive Product Title"

Fatal Mistake #6: "I'll Upload Men's Products Under My Women's Category Agreement"

Fatal Mistake #7: "I'll Fill in Keywords Later" (The Permanent Visibility Killer)

The Master Pre-Upload Checklist (Print This and Use It Every Single Time)

Problem: Lot Rejections - When Excel Uploads But Products Still Don't Go Live

What's Actually Happening (The System Architecture)

Lot Rejection Reason #1: "Duplicate SKU Found"

Lot Rejection Reason #2: "Image Not Found or Image Error"

Lot Rejection Reason #3: "Style Group Conflict"

Lot Rejection Reason #4: "Missing Mandatory Attributes"

Lot Rejection Reason #5: "Manufacturer/Packer Address Issue"

How to Actually Find Rejection Details? (Most Sellers Don't Know This)

The Re-Upload Strategy That Actually Works

Your Action Plan: What to Do Right Now

Contact info