Back to blog

Meesho wrong return claim: claim window conflict, description template, unboxing video practice, claim-rate rejections, auto-compensation settlement check, returns-table routine and scan-and-video app

Meesho Wrong Return Claim: Deadline, Video Proof, Rejections

Cybiqon Team
13 min read
meesho sellerwrong returnsreturn claimsunboxing videopacking appecommerce sellers
Meesho Wrong Return Claim: Deadline, Video Proof, Rejections

It is Saturday evening at a Surat kurti unit. The week's returns are piled on the packing table, and three of the packets hold the wrong thing: an old, faded kurti, a cheaper set and one empty pouch. Each one is a Meesho wrong return claim waiting to be filed. The evidence probably exists, somewhere among 4,000 clips in a packer's phone gallery. Finding the right clip before the claim window closes is the real problem.

The losses are not rare. Around one in four fashion items bought online in India comes back, according to Inc42 (23 Jan 2023). Retailers quoted by The Core (15 Feb 2024) say a share of those returns are counterfeit, damaged or missing. Meanwhile Meesho now says some wrong returns are compensated automatically, while sellers in 2025 and 2026 were still posting about claims rejected for a "claim rate higher than the platform level".

This guide separates what Meesho has said on the record from seller folklore. It covers the real deadline, what to write in the claim description, unboxing video practice, the claim-rate rejection, checking credits in your settlements, and a returns-table routine for a team of 2 to 6 packers.

How to raise a Meesho wrong return claim, step by step

A Meesho wrong return is any return where what comes back is not what you shipped: a different product, a used or older piece of similar colour, a missing item from a set, or an empty packet. The flow in the Supplier Panel, described in general terms because the screens change:

  1. Open the return in the Returns section and note the sub-order ID and the AWB number of the return packet.
  2. Raise a ticket against that return. Older seller SOPs list ticket types such as wrong return received, items missing, damaged return and used product received. Pick the one your footage actually shows.
  3. Upload evidence: the unboxing video of the return packet, photos of the label, AWB and the item, and (if you have one) the packing video of the original dispatch.
  4. Write the description (see the next section).
  5. Track the ticket and, if approved, check that the money actually lands in a settlement.

Reported cases show what is at stake. Leemboodi, a Surat apparel brand selling on Meesho, Amazon, Flipkart and Myntra, told The Core that sarees come back swapped for older used sarees of similar colour. It treats around 100 counterfeit returns as a business cost, and says reimbursement takes 15 to 30 days. Mumbai watch brand Argos reported cheap watches, dupattas and empty boxes coming back.

Remember too that a customer return is a reverse pickup, not an undelivered parcel. If your team mixes the two up, our explainer on RTO vs RVP sorts out which is which, because the claim routes differ.

Meesho wrong return claim description: what to write

There is no official Meesho template for the Meesho wrong return claim description. What follows is guide and seller practice, not a published rule. The aim is a short, factual note a reviewer can check against your video in under a minute.

A structure that works:

  • What you sent: "I dispatched [product name], SKU [SKU], colour [colour], size [size]."
  • What came back: "The return packet, AWB [number], contained [exactly what you found]."
  • The IDs: sub-order ID and return AWB, written out in full.
  • The evidence: "Unboxing video attached, packet shown sealed with label visible before opening."

An example: "Sub-order 1234567890_1. I sent one maroon rayon kurti, SKU KR-MRN-L, size L. The return packet (AWB 0000000000) contained a used blue cotton kurti with no tag. Continuous unboxing video and photos of the label and item attached." The numbers here are placeholders; use your own.

Common mistakes:

  • Picking the wrong reason. Don't choose "damaged" for an empty box, or "wrong product" for a used one. The reason must match the footage.
  • Writing emotion instead of facts. "Customer is cheating" adds nothing a reviewer can verify.
  • Bundling orders. One claim, one sub-order, one video.
  • Vague descriptions. "Wrong item received" with no detail of what was sent and what arrived is the easiest kind to reject.

What is the time limit for a Meesho return claim? The 7-day problem

This is where the top search results contradict each other, so here is what is actually known.

Source What it says How much to trust it
Meesho spokesperson, Inc42 (23 Jan 2023 and 8 Apr 2023) Claims are filed within 7 days of receiving the return The only window Meesho has confirmed on the record
Meesho's own tech blog (undated) Describes the 7-day rule as the old process Official, but no new window stated in the excerpts we found
Third-party guides (2026) Anything from 48–72 hours to 15 days Unofficial and inconsistent

The practical rule: read the deadline shown against the return in your Supplier Panel, and treat that as the authority. If you cannot see one, work to 7 days from receiving the return as the safe assumption for every Meesho return claim time limit. A team that files within 48 hours is never caught out by any of the versions above.

The window is the reason gallery-and-WhatsApp evidence fails. The clip is usually there. Finding the one 40-second video for one AWB among a week of footage, across three phones, on day six, is what does not happen. Most sellers who miss the window do not lack evidence; they lack a way to find it.

Meesho unboxing video rules for a claim: practice, not policy

Search for Meesho unboxing video rules for claim and you will find confident lists. Be clear about what they are: seller and guide practice, not a published Meesho rule. We found no official Meesho specification for file size, length or format. The "25 MB limit" you will see quoted is unverified, so check what the upload screen accepts rather than relying on it.

What experienced sellers do anyway, because it makes a claim hard to argue with:

  • Start recording before the packet is touched, with the sealed packet, shipping label and AWB clearly readable.
  • One continuous take. No cuts, no pause, no re-recording after opening.
  • Keep the packet and item in frame the whole time, on a plain table, in good light.
  • Show the product closely at the end: tags, colour, size label, any wear, or the empty inside.
  • Keep the packaging until the ticket is closed.

For an empty box return claim on Meesho, the video matters even more: show the packet's weight or seal intact, then the empty inside. Pick the items missing style reason, not damaged.

Do you need a packing video for dispatch too? Meesho has not published an outbound packing-video requirement that we could find. Record it anyway: a dispatch clip showing the right item going into the packet is the other half of the story. Unicommerce documents Meesho branded packaging with a QR code mapped to the AWB; it is recommended, not mandatory, but it links the packet to the order. The same evidence habit helps when you dispute courier weight discrepancy charges.

Meesho claim rejected: "claim rate higher than the platform level"

This rejection deserves its own section, because it has nothing to do with the evidence in front of the reviewer.

Two dated public complaints show the pattern:

  • ConsumerComplaints.in, 8 July 2025: a Meesho seller reported receiving the wrong product and having the compensation claim rejected even though proper details were provided.
  • Voxya, 7 February 2026: a seller with photos, a continuous unpacking video, a QR-coded courier packet and the AWB had a wrong-return claim rejected because their claim rate against returns was higher than the platform level.

In other words, a seller can do everything right on one order and still be refused because of the ratio of claims to returns across the account. Meesho has not published what the platform level is or how it is calculated.

What to do next:

  1. Reply on the same ticket. Don't open a fresh one; keep the history together.
  2. Argue per order. State that this sub-order has complete evidence, and ask for it to be assessed on that evidence.
  3. Re-attach the evidence with a factual description, as above.
  4. Check the reason matches the footage. A mismatch makes a re-review easy to refuse.
  5. Keep your own log of every claim, outcome and date, so you can show the pattern if you escalate.

The long-term fix is fewer, better claims: file only where the footage is clean, and fix the packing errors that cause genuine wrong-item complaints on your side.

Does Meesho compensate wrong returns automatically now?

According to Meesho's engineering blog (undated), some wrong returns are now detected and compensated automatically: product value plus shipping, with no claim, no evidence and no waiting. The same post says claim rates fell nearly 30% in key cohorts, and that money used to be stuck for around 15 days. Separately, Meesho told Business Minutes (17 Jan 2025) it had approved 3.4 million "genuine claims" and cut resolution time by 70% for the majority of cases since May 2024. No period was given for that figure.

That is welcome, but treat it with healthy scepticism:

  • Eligibility is not published. You cannot know in advance which returns will be auto-compensated.
  • Payout basis is unclear. An old seller SOP mentions "fair value"; one third-party guide says full value; Meesho's blog says product value plus shipping for automatic cases. Nothing official settles full price or fair value for manual claims.
  • "Approved" is not "paid". Only a settlement line proves the money arrived.

So check. Each week, match every return you flagged (auto or claimed) against the settlement report, sub-order by sub-order, and list anything approved but not credited. If you sell on more than one marketplace, the same job is covered in our guide to marketplace seller reconciliation.

A returns-table routine for 2 to 6 packers

At 50 to 500 orders a day, the routine matters more than any single claim. One that works for a small packing team:

  1. One returns table, one camera. A fixed phone on a stand, not whichever packer's phone is free.
  2. Scan or type the AWB first, then record. Name each file with the AWB and sub-order ID, never "VID_2026...".
  3. Open returns daily, not at the end of the week. A Saturday pile is where the 7-day window dies.
  4. Sort into three trays: good (back to stock), damaged-genuine, and wrong/used/empty (claim).
  5. File claims the same day for the claim tray, with the description template.
  6. Keep a claims register: sub-order, AWB, reason, filed date, deadline, status, amount, settlement date.
  7. Weekly settlement check: every approved claim must appear as a credit.

Wrong returns sit next to undelivered COD parcels on the same table. Meesho's prospectus shows 22.30% of its COD orders went undelivered in FY25, against 2.72% for prepaid (via ClickPost). That is RTO, not customer returns, and the fixes are different; our hub on how to reduce RTO in ecommerce covers that side.

When a scan-and-video app beats phone gallery and Excel

A return unboxing video app for Meesho sellers is not worth it for everyone. If you pack 30 orders a day with one person, a phone stand, careful file names and a spreadsheet will do.

It starts to pay when the volume and the number of hands grow. Here is an illustration, not a measurement. If 25% of 300 daily orders come back and 3% of those returns are bad (the share UCB India quoted to The Core), that is about 2 bad returns a day, or roughly 60 a month. Say the average item is worth ₹400: about ₹24,000 a month depends on finding the right clip in time.

Phone gallery + Excel Owned scan-and-video app
Finding a clip Scroll by date, across phones Search by AWB or sub-order
Starting a recording Packer remembers to AWB scan starts it
Claim deadline Someone counts days Days-left countdown per return
Claim and credit status Separate sheet, often stale Logged against the same order
Works with 6 packers Breaks quickly Built for it

A packing video app with AWB scan for ecommerce sellers in India does not guarantee approval; nothing does, as the claim-rate rejections show. What it removes is the most common failure: a good claim never filed because the video could not be found.

FAQs

What should I write in the Meesho wrong return claim description?

State what you sent (product, SKU, colour, size), exactly what came back, the sub-order ID and return AWB, and that a continuous unboxing video is attached. Keep it factual and choose the reason that matches the footage.

What is the time limit to raise a wrong return claim on Meesho?

Meesho confirmed 7 days from receiving the return on the record in 2023, but its blog calls that the old process and other guides quote 72 hours to 15 days. Follow the deadline shown on the return in your Supplier Panel; otherwise file within 7 days, ideally within 48 hours.

Why was my Meesho claim rejected for a claim rate higher than the platform level?

Meesho compares your claims against your returns across the account. If the ratio is above a level it does not publish, claims can be refused even with good evidence. Reply on the same ticket and ask for the order to be judged on its own evidence.

What can I do if an empty box comes back on Meesho?

Record the sealed packet and label before opening, then the empty inside in one continuous video. File under an items-missing style reason, not damaged, with the AWB and sub-order ID.

Do I need a packing video for dispatch on Meesho too?

No published Meesho rule requires one, as far as we could find. Record it anyway; it proves the right item left your table.

What Cybiqon would build for your returns table

If you pack 50 to 500 Meesho orders a day, Cybiqon would build an Android app for your packing and returns table. A packer scans the AWB, recording starts, and the video is saved against that sub-order. Each return shows how many days are left to claim. Claim status and the credit from your settlement are logged on the same order, so nothing approved goes unpaid unnoticed.

It is written for your packers, your volume and your SKUs, not configured from a template. The founders build it, and you own the code. Our Android app development starts at ₹29,999 and is scoped per build. Book a 30-minute call, call +91 9250711473 or write to [email protected].

Conclusion

A Meesho wrong return claim is won or lost before you fill in the form. Read the deadline on the return and treat 7 days as the ceiling. Record one continuous unboxing video per packet, write a short factual description, and pick the reason your footage proves. If a good claim is refused on claim rate, reply on the same ticket with per-order evidence. Then check every credit in your settlements. If your returns table has outgrown phone galleries and spreadsheets, Cybiqon can build the scan-and-video app that runs it.

Want this set up for your business?

Book a free call — no tech jargon, no sales pressure. Just honest answers.

WhatsApp us

What we build for this: Custom websites

Chat with us!