QC error in Meesho: why your listings keep failing, and how to stop the cycle.
Every catalog you upload to Meesho passes through quality control before a buyer ever sees it, and a rejected catalog earns nothing while it sits in the failed pile. This guide breaks down the rejection types behind most QC errors, how to find and fix failed listings in the supplier panel, and why a pattern of failures quietly puts the whole account at risk.
QC error in Meesho means the catalog quality check rejected your listing for an image, title, attribute or pricing rule, so it stays invisible to buyers until you act. The rejection notice names the failed check. Fix that exact issue in the panel and resubmit once; a resubmission is typically reviewed within 48 hours.
- QC is a checklist, not a judgement. Most failures come from a handful of checks, image standards, attribute mismatches, brand and IP flags, duplicates, restricted items, and the rejection notice tells you which one you failed.
- Failed catalogs sit in their own view in the supplier panel, invisible and earning nothing. Review that view weekly, fix the exact flagged issue plus anything else off, and resubmit once, every sloppy retry costs a full review cycle.
- One rejection is noise. A pattern of rejections is a signal that follows your account, slower reviews, stricter scrutiny, catalog blocks. A ten-minute pre-upload checklist is the cheapest account protection you will ever run.
Every catalog is guilty until the checks pass
When you upload a catalog, Meesho runs it through quality control before it goes live: automated checks plus review against listing standards, covering the images, the attribute fields, the category placement, brand usage and policy restrictions. A catalog that clears everything goes live. A catalog that trips any check lands in a failed state with a rejection reason attached, and stays there, invisible to buyers, until you act on it.
The part sellers underestimate is the silence. A QC failure does not phone you; it waits in a panel view you may not be checking. On a store uploading in batches, it is normal to discover, weeks late, that a third of a batch never went live. If each failed catalog would have done even two or three orders a day at a ₹120 margin (illustrative), a month of not noticing is thousands of rupees of margin that vanished without appearing on any report. The first fix is not better images. It is a weekly appointment with the failed-catalog view.
Seven checks that fail most catalogs
Match the rejection notice on your catalog to the check below, apply the fix, and resubmit once, with everything else corrected in the same pass.
- 01
Image standards
The biggest bucket by far: busy or wrong backgrounds, blur, poor lighting, watermarks, text or price overlays, collage-style images, and photos lifted from other listings. Fix: clean single-product shots on the prescribed background, sharp and unedited except for crops. Reused internet images also walk you straight into the next bucket, IP flags.
- 02
Attribute and category mismatch
The fields say cotton, the photo shows satin; the category says kurti, the product is a gown. QC compares your declared attributes against the images and the category tree, and contradictions fail the check. Fix: fill attributes from the physical product in front of you, not from a template copied off the last upload.
- 03
Brand and IP flags
A brand name in the title, a logo visible in a photo, or a design associated with a protected brand triggers the IP check. Without authorization documents on file, the catalog fails, and repeated IP flags are the fastest route from catalog problem to account problem. Fix: list only brands you can document, and keep third-party logos out of frame.
- 04
Restricted or prohibited products
Some categories are gated or banned outright, the lists change, so check the current policy on the panel before investing in inventory. A restricted-product rejection is one of the few that can escalate on its own, so treat it as a category decision, not an image problem to retry.
- 05
Duplicate catalog
Uploading the same product again, same images, same details, to get a fresh shot at ranking reads as duplication and fails QC. Fix: one product, one catalog. If a listing underperforms, improve the existing catalog instead of cloning it; clones dilute reviews and attract exactly this rejection.
- 06
Incomplete details and size charts
Apparel and footwear without a size chart, missing mandatory fields, one-word descriptions, incompleteness fails checks and, even when it squeaks through, produces the returns that hurt you later. Fix: treat every mandatory field as mandatory, and fill the optional ones a buyer would actually use to decide.
- 07
Pricing and MRP field errors
A selling price above the printed MRP, an MRP that contradicts the product label in the photos, or obviously misplaced digits will bounce a catalog. Fix: enter MRP from the physical label, sanity-check the price against it, and re-check both after every bulk-edit, spreadsheet slips are the usual culprit here.
QC failures are counted, not just corrected
Each rejection is recoverable on its own. What sellers consistently report is that the marketplace also watches the rate: an account that keeps failing the same checks, or trips brand and IP flags more than once, starts getting treated differently. Reviews slow down. Uploads that used to clear in hours sit for days. Catalogs get blocked instead of merely rejected. In persistent cases the account itself comes under review. None of this is published as a formula, and Meesho does not owe you one, which is exactly why the safe strategy is keeping the failure rate boring.
The tool for that is a pre-upload checklist, run on every catalog before it leaves your desk: images against the standards, attributes against the physical product, category against the tree, brand usage against your documents, size chart present, MRP against the label. Ten minutes per batch, and QC stops being a lottery.
Fix the images before QC sees them. Keep the rest of the account clean.
Robnu is not a listing tool, and your catalog stays yours. But look at where QC failures actually come from: the single biggest bucket is images. Robnu's AI Catalog Studio turns your source shots into marketplace-grade product images and videos, clean backgrounds, consistent framing, no watermarks or overlays, with credits included to start. Catalogs that walk into QC with compliant images have already dodged the most common rejection.
The other half is what QC failures sit next to. Account health is one ledger: listing quality, dispatch performance, returns handling, all counted against the same account. Robnu runs the operational side, orders, labels, SLA deadlines, returns, reconciliation, on AJIO and Meesho without misses, so a rough QC week lands on an account with an otherwise spotless record instead of stacking onto breach flags and pickup failures.
“Your product is under QC. Please expect an action within 48 hours”: what happens now
This message means your catalog is sitting in Meesho’s review queue. Nothing has failed yet, and there is nothing for you to do: the 48-hour window is the queue time Meesho gives its checkers, and the catalog moves to QC pass or QC failed on its own. Do not upload the same product again to hurry it along. A second copy typically fails as a duplicate, and that duplicate rejection lands on your account record while the original is still waiting. If the window passes with no change, check the catalog view once more and raise a support ticket only after that; category load can stretch the queue. One thing this message is not: the separate line “your application is currently under QC review” refers to a new supplier onboarding application, not a catalog, and is handled in the registration flow rather than the catalog panel.
QC in progress, QC pass, QC failed redressal: the statuses
QC in Meesho is the quality check every catalog passes through before it goes live, and the panel shows where a catalog is in that check with a small set of statuses. Here is what each one means and the action it asks of you.
| Status | Meaning | Your action |
|---|---|---|
| QC in progress (under QC) | The catalog is in the review queue and has not been checked yet. | Wait for the window. Do not re-upload the product. |
| QC pass | The catalog cleared every check and is live or about to go live. | Open the live listing and confirm price, stock and images look right. |
| QC failed | One or more checks failed; the rejection reason is attached to the catalog. | Read the reason, fix that issue plus anything else off, resubmit once. |
| QC failed redressal | A failed catalog you have contested or corrected is being looked at again, typically a review of your resubmission or of a ticket against the rejection. | Track it in the panel, attach proof if asked, and do not upload a duplicate while it is open. |
How to fix QC error in Meesho, step by step
- Open the failed catalog in the supplier panel and read the rejection reason word for word. It names the check that failed.
- Match the reason to one of the seven checks above: image standards, attribute mismatch, brand or IP flag, restricted product, duplicate, incomplete details, pricing or MRP.
- Fix that exact issue at the source: reshoot or replace the image set, correct the attribute from the physical product, attach the brand authorization, add the size chart, or fix the MRP.
- Re-check every other field while you are in there, because a resubmission that fails on a different check costs another full review cycle and another mark on the record.
- Resubmit once and note the date. Expect an action typically within 48 hours; the status moves to QC pass or back to QC failed with a fresh reason.
- If it fails again on the same check and you believe the catalog is compliant, use the redressal or support path in the panel with your proof attached rather than uploading a new copy.
Meesho QC errors, answered
Almost every QC failure lands in one of a few buckets: images that break the standards (wrong background, blur, watermarks, text overlays, borrowed photos), attributes that do not match the images or the category, brand names or logos that trigger an IP check without authorization documents, products from restricted categories, duplicate catalogs that repeat an existing listing, or incomplete fields like a missing size chart. The rejection notice in the supplier panel names the failed check, read it literally before changing anything, because fixing the wrong thing earns you the same rejection twice.
In the desktop supplier panel, open the catalog or inventory section and filter by QC status, failed and pending listings sit in their own views, separate from live ones. Each failed catalog carries a rejection reason against the specific check it did not clear. The panel layout shifts between updates, so if a filter has moved, search the catalog section rather than assuming failures are gone. Make reviewing this view a weekly habit: sellers routinely discover listings that failed silently weeks ago and have been earning nothing since.
Meesho does not commit to one public turnaround, and sellers report anything from a few hours to a few days depending on category and load, new-seller uploads and flagged categories tend to sit longer. Resubmissions after a failure go through the same review, so a careless fix costs you a full extra cycle. That is the practical argument for getting it right before upload: one clean pass through QC beats three fast-but-sloppy attempts. Check the current processing expectations on your supplier panel rather than trusting screenshots from seller groups.
Yes, QC failure is a correction loop, not a dead end. Open the failed catalog, read the exact rejection reason, fix that specific issue (replace the image set, correct the attribute, attach the brand authorization, complete the size chart), and resubmit for review. Fix every flagged issue in one pass, and re-check the fields the notice did not mention while you are in there, a resubmission that fails on a second, different check costs another full review cycle and adds one more failure to your account's record.
Sellers consistently report that they do. A pattern of rejections, especially repeat offences on the same check, or anything touching brand and IP, marks the account as one that needs watching, which can mean slower reviews on future uploads, stricter scrutiny, catalog-level blocks, and in persistent cases action against the account itself. One failure is routine and costs you nothing but time. A failure rate is a signal you are training the marketplace to distrust your uploads, and that trust is slow to rebuild once lost.
Robnu is not a listing tool, you still own your catalog. Where it helps is the two ends of the problem. The AI Catalog Studio produces marketplace-grade product images and videos from your source shots (credits included to start), which attacks the single most common rejection bucket before upload. And Robnu runs your daily operations, dispatch, returns, reconciliation, cleanly in the background, so your account health rides on catalog quality alone instead of catalog quality plus operational misses stacking against the same account.
QC in Meesho is the quality check every catalog goes through before buyers can see it. Meesho checks the images against its standards, the attributes against the photos and category, brand usage against your documents, and the listing against policy and pricing rules. A catalog that clears every check goes live; one that trips a check is marked QC failed with the reason attached.
It means the catalog is in Meesho's review queue and has not been checked yet. Nothing has failed and nothing is needed from you. The 48 hours is the typical review window; the status then moves to QC pass or QC failed on its own. Do not upload the same product again while you wait, because the second copy typically fails as a duplicate.
QC in progress means the quality check on your catalog has started but has not concluded. It is the same waiting state as 'under QC': the checkers are working through the queue, and the catalog is not yet visible to buyers. There is no action to take until it becomes QC pass or QC failed.
QC failed redressal is the state a rejected catalog enters when you have contested or corrected the failure and Meesho is looking at it again. It typically covers both a resubmission after your fix and a ticket you raised because you believe the rejection was wrong. Track it in the panel, attach your proof if asked, and do not upload a duplicate while it is open.
Read the rejection reason on the failed catalog, match it to the check that failed, and fix that exact issue at the source: replace the image set, correct the attribute from the physical product, attach brand authorization, add the size chart, or correct the MRP. Re-check every other field, then resubmit once. Expect an action typically within 48 hours. If it fails again on the same check and you believe the catalog is compliant, use the redressal or support path with your proof attached.
Where this comes from
- Meesho supplier documentation on catalog quality standards, image guidelines and listing policy: supplier.meesho.com learning hub, standards change, so check the current version before every upload batch.
- Recurring seller reports of QC rejection reasons, review turnarounds and failure-pattern consequences: public seller community threads (Reddit r/IndiaBusiness, seller Facebook and Telegram groups), 2025 to 2026.
Sources & further reading
Charges, policies and processes vary by marketplace and category and change over time. Confirm current specifics against your own seller panel and the official documentation:
Related seller guides
More on the operations, money and claims that decide whether a marketplace catalogue actually makes money.
Meesho "Supplier Not Found" After Login: What It Means (2026)
Meesho says supplier not found after your password is accepted. What the error does and does not mean, what to check, and how to protect your dispatch SLA while you are locked out.
Meesho Bank Verification Pending or In Progress: Causes, Time and Fixes
Meesho bank verification pending or in progress? What each status means, how Meesho verifies the account, how long it takes, why it fails and how to fix it.
Meesho IPO Explained for Sellers: What Listing Means for You (2026)
Meesho listed on NSE and BSE in December 2025. What the IPO and listing actually mean for a seller, and what does not change about your fees, payouts, or day-to-day selling.
Meesho Password Reset Email Not Received: The Fix and the Workaround
The Meesho supplier reset link goes only to the registered email. What to check, how long to wait, and the OTP login route on the same screen that skips the password.
Meesho Seller Login Not Working? Password, OTP and Every Fix (2026)
Meesho supplier login is password first, not OTP. The real login form, the hidden OTP route under Forgot password, why there is no Meesho seller app, and a fix for every failure.
Meesho Supplier Login: Panel Access and Troubleshooting (2026)
How to log into the Meesho Supplier Panel, why supplier and seller mean the same thing on Meesho, and how to fix panel-access problems like a blank panel or incomplete onboarding.
Myntra Partner Account Problems and How to Fix Them
Approval delays, brand authorization rejections, QC and listing suspensions, inventory sync errors, payment holds, SLA warnings, login and GST mismatches, the common Myntra partner account issues and the practical steps to resolve each one.
Meesho QC Fail on a Return: Your Claim Window and How to Use It
When a returned Meesho parcel fails quality check, the outcome and your money are decided in a short window. What QC-fail means, the evidence that holds, and the claim path that recovers a wrongly-failed return.