For sellers on Amazon, Flipkart, AJIO, Myntra, Nykaa, Meesho and Snapdeal. Updated September 2026.
Direct Answer
Most sellers measure claim performance by approval rate, and miss unfiled marketplace claims entirely as a result: the percentage of filed claims that get approved. That number hides the bigger loss. The claims that were never filed at all do not appear in any report, do not lower your approval rate, and do not show up anywhere in your dashboard, because a claim that was never filed leaves no record of having existed. For most sellers running real return volume across multiple marketplaces, the money lost to claims that were eligible but never filed is larger than the money lost to claims that were filed and rejected. This is invisible by definition, since it requires comparing what you filed against what you were actually eligible to file, a comparison most sellers have never run. The rest of this guide is a self-audit for unfiled marketplace claims you can run in about fifteen minutes with data you already have, to find out what your own number is.
Quick Answer: Why Does This Loss Stay Invisible?
Because nothing forces it into view. A rejected claim generates a rejection notice, a status you can see and react to. A claim that was never filed generates nothing: no notice, no line item, no prompt. It simply becomes a return that was processed, refunded, and forgotten. The only way to see unfiled marketplace claims is to deliberately compare your total claim-eligible events against your total filed claims for the same period, which almost no seller does as a routine practice, because there is no report that does it automatically unless you build one.
Why Is Approval Rate the Wrong Number to Watch?
Approval rate answers a narrow question: of the claims I filed, how many did I win. It is a real and useful number, but it only describes performance on the claims that made it into the system in the first place.
The number nobody watches is the filed rate: of the claims I was eligible to file, how many did I actually file. This is a completely different measurement, and for most sellers it is far worse than their approval rate. A seller winning 80 percent of filed claims sounds healthy. A seller winning 80 percent of filed claims while only filing 30 percent of eligible ones is recovering roughly a quarter of what they are actually owed, and their dashboard shows none of it.
Why filed rate stays low without anyone deciding it should. Filing a claim manually takes time, typically 15 to 20 minutes per claim once evidence is located, formatted and submitted. Under time pressure, sellers and their teams naturally triage: the largest, most obvious claims get filed, and the rest get left. This is not a mistake anyone makes on purpose. It is what happens by default when filing has a real labour cost and no one is tracking what did not get filed.
The industry context worth knowing. Publicly available seller research puts unrecovered losses from return fraud and disputes at roughly 8 to 15 percent of monthly revenue for sellers without a structured claim process. That range is wide because the gap between eligible and filed varies enormously by operation, which is exactly why a personal self-audit matters more than an industry average.
Which Claim Types Are Most Likely to Go Unfiled?
Some claim types are far more likely to be missed than others, because they are less visible in day-to-day operations than an obvious wrong-item return.
Return marked delivered that never physically arrived. The system shows the return as received. Nobody checks whether the box actually reached the warehouse. This is one of the most commonly missed claim types because it looks, at a glance, like a completed return rather than a loss.
Partial returns with missing items. A multi-item order is returned, but the return package contains fewer items than were shipped. If nobody weighs or itemises the return against the original order, the shortfall is silently absorbed as a normal return.
Refunds issued without a physical return. Some marketplaces process a refund to the buyer without requiring the item back at all, under specific conditions. If this is not flagged separately from a standard processed return, it looks identical in most reporting.
Claims where the window is technically still open on an older return. Some marketplaces allow claim windows measured in weeks or months, not days. Returns from earlier in the month, or even the prior month, that were never actioned are often still filable and simply forgotten as time passes.
Rejected claims never appealed with new evidence. A rejection is not always final. Most platforms allow a follow-up with additional evidence. A claim rejected once and never revisited counts as a loss even though a second attempt was possible.
The Self-Audit: Find Your Number in 15 Minutes
Five steps, using data you already have in your seller dashboards. No tool required for this version.
Step 1: Pull your total return count for last month, across every marketplace you sell on. Most seller panels show this directly.
Step 2: Estimate your claim-eligible share of those returns. Not every return is claim-eligible; a genuine change-of-mind return with the correct item in good condition is not a claim. The claim-eligible categories are wrong item, damaged in transit, empty box or missing contents, non-delivered return, and disputed refund. A reasonable starting estimate, absent your own data, is that these categories together account for a meaningful minority of total returns rather than a rare exception, though this varies significantly by category and by how much cash-on-delivery and Tier 2/3 volume you carry.
Step 3: Pull your actual filed claim count for the same period, from each marketplace's claims or SPF section.
Step 4: Subtract. Eligible estimate minus actual filed equals your unfiled claim count for the month. This is the number that does not appear on any dashboard.
Step 5: Multiply by your average claim value. If you do not know your own average, a reasonable reference point from claim data across Indian marketplace sellers puts typical individual claim value in the low hundreds of rupees, with meaningful variation by category and product price point. Multiply your unfiled count by a conservative average to get a monthly figure, and again by twelve for an annual one.
Run this audit with us using your actual data instead of estimates. 15 minutes. No commitment.
A Worked Example
Illustrative only, using round numbers to show the mechanism, not a specific seller's real figures.
A seller processes 3,000 orders in a month across five marketplaces, with a 12 percent return rate, roughly 360 returns. If claim-eligible categories account for a conservative 20 percent of those returns, that is 72 potentially claimable events. If the seller's team, working manually under time pressure, actually filed 25 of them, that is 47 unfiled claims for the month. At an average claim value of ₹800, that is roughly ₹37,600 in a single month, not reflected anywhere in the seller's approval rate, because these claims never entered the system at all.
The part of this that surprises most sellers. None of those 47 unfiled claims would show up as a problem anywhere. The seller's filed claims might have a perfectly healthy 80 percent approval rate. The dashboard would look fine. The loss exists entirely outside what gets measured.
Why Do Unfiled Marketplace Claims Compound at Multi-Marketplace Scale?
Running this audit on one marketplace understates the real number for most sellers, because the unfiled rate does not stay constant across channels.
Attention concentrates on whichever marketplace is easiest to work. A seller with one dominant channel and several smaller ones typically files diligently on the dominant channel and lets the smaller ones slide, precisely because the smaller channels do not feel urgent individually. Five channels each quietly leaking a smaller amount adds up to a larger total than the number on any single channel suggests.
Shorter windows lose more silently. AJIO's dispute response window can run as short as 24 to 48 hours from notification. Nykaa requires disputes within 7 working days of receiving a return, by email, to specific addresses. A claim missed by a day on a short-window platform is not a delayed claim, it is a permanently lost one, and it disappears from view exactly the same way a longer-window miss does.
The self-audit above should be run per marketplace, not in aggregate, precisely because the channel with the worst filed rate is often not the channel a seller would guess without checking.
What Changes Once You Can See Your Unfiled Marketplace Claims?
Finding the number is the first step. What a seller does with it depends heavily on the economics of actually filing everything found.
Under manual filing, finding a large unfiled number is genuinely bad news with no easy fix. Fifteen to twenty minutes per claim at real volume is a staffing decision, not a quick adjustment, and most operations that run this audit and find a large gap still cannot close it by working harder within existing capacity.
Under a flat per-claim pricing model, the same discovery is actionable immediately. If processing a claim costs roughly ₹1 to ₹2 regardless of its size, a ₹150 claim that was previously not worth anyone's manual time to chase becomes worth filing the moment the cost of filing it is negligible next to its recovery value. This is the direct, practical link between finding invisible losses and a pricing model built to let you act on what you find, rather than just quantify it.
Where TrackVid Fits
TrackVid is a video proof and claim management platform used by 1,100+ ecommerce sellers, automating evidence-based claim filing across Flipkart, AJIO, Myntra, Nykaa, Amazon, Meesho, Snapdeal and other channels.
What closes the specific gap this audit surfaces:
- Return reconciliation, which is built specifically to surface claims that would otherwise expire unfiled, including the return-marked-delivered-but-never-arrived and partial-return categories described above, without requiring a manual monthly audit
- Order-linked video capture at packing and on return, providing the evidence the claim-eligible categories in this audit actually require
- Automated claim filing via robotic process automation, cutting filing time from 15 to 20 minutes to under a minute per claim, which is what makes filing every eligible claim, not just the obvious ones, operationally realistic
- Prepaid recharge pricing at roughly ₹1 to ₹2 per claim processed, no commission on recovered funds, which is what makes the small, previously-ignored claims this audit finds worth filing at all
An anonymised deployment example: a single enterprise operation captured 94,904 packing videos across 95,836 tracked orders, filing 868 claims against that evidence, with approval moving from 42.3 percent to 60.3 percent within a month of switching to systematic capture and filing, a shift driven largely by claims that would previously have gone unfiled entirely.
Bring your own numbers from the self-audit above and we will show you what closing that gap looks like operationally. 15 minutes. No commitment.
Read Next
- SPF Claim Automation in India: The Complete Guide, the category overview this self-audit sits inside
- Claim Automation vs Reimbursement Software, which category actually recovers the losses this audit finds
- Flipkart SPF Claim Automation, platform-specific detail for Flipkart sellers
Frequently Asked Questions
How do I know if I am missing marketplace claims?
Compare your total claim-eligible returns for a month, wrong item, damaged, empty box, non-delivered, disputed refund, against your actual filed claim count for the same period on the same marketplace. The gap between them is your unfiled claim count, and it does not appear in any standard dashboard report.
Why is my claim approval rate low?
Approval rate only measures claims you actually filed. A low approval rate on filed claims is a different problem from a low filed rate on eligible claims, and the second is usually the larger, less visible loss. Check both separately rather than assuming approval rate tells the whole story.
How much money am I losing to unfiled claims?
Varies by operation, but publicly available seller research puts unrecovered return-related losses at roughly 8 to 15 percent of monthly revenue for sellers without a structured claim process. Running the self-audit in this guide against your own numbers gives a figure specific to your operation rather than an industry average.
What is claim leakage?
The gap between claims you were eligible to file and claims you actually filed. Unlike a rejected claim, which generates a visible record, claim leakage is invisible by default because an unfiled claim leaves no trace in standard reporting.
How do I audit my unfiled claims?
Pull your total return count, estimate what share is claim-eligible using the categories in this guide, pull your actual filed count for the same period, subtract, and multiply by your average claim value. Run this per marketplace rather than in aggregate, since the worst-performing channel is often not the one you would guess.
Why do sellers lose money on returns without knowing it?
Because filing takes real time per claim, and under time pressure, smaller or less obvious claims get triaged away without anyone deciding to skip them deliberately. The result accumulates silently across a month without ever appearing as a specific, visible loss.
Which claim types are most likely to go unfiled?
Returns marked delivered that never physically arrived, partial returns with missing items, refunds issued without a physical return, older claims still technically inside their window, and rejected claims never appealed with new evidence. All five are less visually obvious than a straightforward wrong-item return.
Does this loss show up differently across marketplaces?
Yes. Attention tends to concentrate on whichever marketplace is easiest or most urgent to work, so smaller channels often have a worse filed rate than the seller's main channel, and shorter claim windows on some platforms mean a missed claim there is lost permanently rather than delayed.
Can I close this gap without software?
At low volume, yes, with disciplined manual tracking. Once eligible-claim volume outpaces the time available to file each one within its window, which happens faster than most sellers expect across multiple marketplaces, manual tracking alone typically cannot keep the filed rate close to the eligible rate.
Why does per-claim pricing matter for closing this gap specifically?
Many claims this audit finds are individually small. Under a flat per-claim fee, a ₹150 claim becomes worth filing. Under percentage-of-recovery pricing or manual labour cost, that same small claim usually is not worth chasing.
Sources: publicly available Indian ecommerce seller research on return fraud and unrecovered losses; Flipkart, AJIO, Myntra, Nykaa, Meesho and Snapdeal seller documentation, 2026; TrackVid platform data across 1,100+ ecommerce sellers; anonymised enterprise deployment data (94,904 packing videos, 95,836 tracked orders, 868 claims filed, average claim value ₹800)
The self-audit in this guide provides an estimate based on your own inputs, not a guaranteed figure. Actual eligible and recoverable claim counts depend on your specific product mix, return patterns and marketplace policies.
TrackVid is a video proof and claim management platform for ecommerce sellers, providing order ID-linked evidence capture, return reconciliation and automated claim filing across major marketplaces on a prepaid per-claim pricing model. Learn more at trackvid.in.
Get the Marketplace Claim Recovery Checklist
A 12-point checklist used by 1,100+ sellers to recover 85-90% of marketplace claim losses. Free, instant access.
- Marketplace-specific evidence formats (AJIO, Flipkart, Amazon, Myntra)
- Claim window deadlines for every major platform
- The 6-step process that pushes approval from 85-90%
- Common rejection reasons and how to avoid them
No spam. Unsubscribe anytime. Used by sellers at Rare Rabbit, HRX, Da Milano + 1,100 more.
Stop Losing Money to Fake Returns
Join 1,100+ sellers who recover lakhs every month with TrackVid



