For Flipkart sellers facing a non-delivery or lost-return dispute. Updated September 2026.
Direct Answer
A Flipkart seller return not received claim covers three distinct scenarios: buyer claiming non-delivery despite "delivered" status on tracking, returned parcel never reaching the seller warehouse, and RTO parcels never arriving back. Each scenario has different evidence requirements and uses different SPF reason codes. The 14-day standard SPF window applies to most of these, but the 120-day product-missing window applies when the parcel is confirmed lost in the courier network.
What Does "Return Not Received" Actually Mean on Flipkart?
The phrase covers more ground than most sellers realize. It can mean the buyer claims the forward shipment never arrived at their end, or it can mean a returned parcel initiated by the buyer never reached your warehouse, or it can mean an RTO parcel that bounced from the buyer never came back to you. Three different scenarios, three different evidence requirements, three different Flipkart SPF reason codes. Filing the wrong one for the wrong scenario is the single most common rejection cause for this claim type.
What Are the Three Flipkart Return Not Received Scenarios?
Every flipkart seller return not received dispute falls into one of three categories. The scenario decides the reason code, the evidence standard, and the claim window.
| Scenario | What Happens | Evidence Focus | Typical Window |
|---|---|---|---|
| Buyer claims non-delivery | Tracking shows delivered but buyer disputes receipt | Courier POD, delivery proof, GPS where available | 14 days from dispute, extendable |
| Return parcel lost on return leg | Buyer-initiated return never reaches your warehouse | Return tracking, non-receipt confirmation | 14 to 120 days depending on confirmation |
| RTO parcel never arrived | Refused or undeliverable parcel never comes back | RTO tracking, courier escalation | 14 to 120 days product-missing |
What If the Buyer Claims They Did Not Receive the Order?
This flipkart seller return not received scenario fires when Flipkart tracking shows the parcel as delivered on a specific date, with a timestamp and sometimes a signature or OTP confirmation. The buyer opens a complaint claiming they did not receive the order and demands refund.
Who typically pays: this falls into the gray zone between buyer-side fraud attempt and genuine misdelivery by the courier (wrong address, delivered to a neighbour, package taken from a doorstep).
Evidence that wins the claim:
- The courier POD (Proof of Delivery) with signature, OTP, or photo evidence of the delivery
- GPS coordinates of the delivery location if the courier captured them
- The buyer's delivery address versus the GPS coordinates if there is any mismatch
- Delivery timestamp with any photo of the handover
Reason code family: falsely-claimed-non-delivery or buyer-not-received, depending on your current Flipkart Seller Dashboard reason code list.
Window: 14 days from the buyer complaint being logged, with potential extension if the courier escalation runs long.
The success rate on this claim type is highly dependent on which courier handled the delivery and whether their POD includes photo evidence. Ekart deliveries on Flipkart orders typically have better POD evidence than third-party courier deliveries.
What If a Return Parcel Never Reached Your Warehouse?
This scenario fires when the buyer initiated a return, the Flipkart reverse logistics system picked up the parcel from the buyer, but the parcel never arrived at your warehouse. Tracking may show it as in transit indefinitely, or it may stop updating entirely.
Who typically pays: the courier network, which is the responsible party when a return parcel is lost between buyer and seller.
Evidence that wins the claim:
- The return tracking showing pickup from buyer but no delivery to your warehouse
- Your warehouse scan logs showing no receipt of the parcel for the specific AWB
- Date-stamped confirmation that the expected arrival window has passed
- Any courier escalation reference number if you have raised a ticket with Ekart or the third-party courier
Reason code family: return-not-received or lost-in-transit-return, verify in your current Flipkart Seller Dashboard.
Window: standard 14 days from the expected return arrival date, with the 120-day product-missing window applying once the courier confirms the parcel is lost rather than delayed.
The hardest part at scale: detecting a return went missing in the first place. Returns that stop tracking do not alert, they just disappear from the dashboard view. Monthly reconciliation of expected returns against warehouse receipts catches them systematically.
What If an RTO Parcel Never Came Back?
The third scenario fires when the parcel was dispatched to the buyer, could not be delivered (refused, undeliverable address, buyer unavailable after multiple attempts), was marked for Return to Origin, but never actually arrived back at your warehouse.
Who typically pays: again the courier network, which is responsible for completing the RTO journey.
Evidence that wins the claim:
- The forward tracking showing the parcel reached buyer-end and was marked RTO
- Return leg tracking showing partial or no movement after RTO initiation
- Your warehouse scan logs showing no receipt for the specific AWB
- Timeline analysis showing the RTO is overdue by more than the expected transit time
Reason code family: RTO-not-received or similar, verify in your current Flipkart Seller Dashboard.
Window: this scenario most commonly qualifies for the 120-day product-missing window, because an RTO that does not arrive within 60 to 90 days is usually confirmed lost rather than delayed.
How Does the 120-Day Product-Missing Window Work?
Most flipkart seller return not received claims use the 14-day SPF window. The product-missing window is the exception, applying specifically when a parcel is confirmed lost in the courier network rather than disputed on condition or content.
The 120-day window applies when:
- A forward shipment is confirmed lost in transit, before reaching the buyer
- A return parcel never arrives at your warehouse and the courier confirms it as lost
- An RTO parcel never arrives back and the courier confirms it as lost
- Any scenario where the parcel is physically missing from the courier network, not disputed on delivery
The 120-day window does not apply when:
- Tracking shows delivered but buyer disputes receipt (14-day falsely-claimed-non-delivery)
- Return arrives at warehouse but in disputed condition (14-day wrong-return)
- Any scenario where the parcel is accounted for in the network
The practical implication: the longer window gives you time to work with the courier on escalation and confirmation before filing. But if the dispute is actually about buyer-claimed non-delivery of a confirmed-delivered parcel, you only have 14 days, and waiting for the longer window will miss the actual claim deadline.
Why Do Flipkart Not-Received Claims Get Rejected?
Four common patterns.
Wrong reason code for the scenario. Filing a claim as lost-in-transit on a buyer-claims-non-delivery dispute when tracking shows delivered gets rejected as a code mismatch. The three scenarios need three different codes.
No courier escalation reference. For return-lost and RTO-not-received claims specifically, Flipkart often wants evidence that you have raised the issue with the courier network before claiming SPF. A claim filed with no courier ticket number attached is weaker than one with escalation evidence.
Expired window because you waited for the longer one. Sellers assume the 120-day window applies and file after the 14-day window has already expired for scenarios that did not actually qualify for product-missing. The default should be filing inside 14 days and relying on the longer window only when the courier has confirmed loss.
Missing warehouse scan logs. For return-not-received claims, Flipkart wants proof the parcel did not arrive at your end, not just absence of positive confirmation. Warehouse scan logs showing active checking for the AWB are stronger than silence.
Where TrackVid Fits
TrackVid is used by 1,100+ Indian sellers and is officially authorised by Snapdeal, with the same automation operating across Flipkart SPF, Myntra PPMP, AJIO, Meesho and Amazon SAFE-T.
What applies specifically to flipkart seller return not received claims:
- Return reconciliation that cross-references expected returns against actual warehouse receipts and surfaces not-received parcels before the window expires. This addresses the single hardest part of this claim type: knowing it happened in the first place
- Automated SPF filing via robotic process automation on your Flipkart Seller Dashboard access, with scenario-specific reason code selection so a lost-return claim does not get filed under a non-delivery code
- Order-linked video capture provides the dispatch-side evidence that confirms the parcel was packed and handed to the courier, which supports both not-received and wrong-return claims from the same recording
- Courier escalation tracking keeps the ticket history attached to the claim
Pricing is a flat fee per claim processed on prepaid recharge, quoted against your monthly claim volume. No commission on recovery, and none from marketplaces.
Related Reading
- Flipkart Seller Wrong Return Claim Process 2026, for when the parcel did arrive but with wrong contents
- Flipkart Seller Return Charges 2026, the five fee categories a completed return triggers
- Marketplace Packing Video Requirements 2026, the dispatch-side evidence standard
- Every Marketplace Claim Window in India, Compared, the full window comparison across platforms
Frequently Asked Questions
What is a flipkart seller return not received claim?
It is an SPF claim covering three scenarios: buyer claims non-delivery despite delivered tracking status, a return parcel initiated by the buyer never reaches the seller warehouse, or an RTO parcel never arrives back after being bounced from the buyer. Each scenario uses a different reason code.
How long do I have to file a flipkart return not received claim?
The standard SPF window is 14 days, but the 120-day product-missing window applies specifically when a parcel is confirmed lost in the courier network. Buyer-claims-non-delivery disputes on confirmed-delivered parcels use the shorter window.
What evidence do I need for a Flipkart return not received claim?
It depends on scenario. For buyer non-delivery claims, courier POD with signature or photo evidence. For lost-return claims, return tracking plus warehouse non-receipt logs plus courier escalation reference. For RTO not received, forward and return tracking plus warehouse logs.
What is the Flipkart product-missing window?
Up to 120 days from the lost-event date, applying when a parcel is physically missing from the courier network rather than disputed on delivery or condition. This is distinct from the standard 14-day SPF window.
My buyer says they did not receive the order but tracking shows delivered. What do I do?
File a falsely-claimed-non-delivery SPF claim inside 14 days, attaching the courier POD with signature or photo evidence. Success depends on POD quality, which varies by the courier handling the specific delivery.
My return parcel never came back. How do I file a claim on Flipkart?
Raise an escalation with the courier network first and get a ticket reference. Then file an SPF lost-return claim within 14 days of expected arrival, attaching return tracking showing pickup but no delivery, warehouse non-receipt logs, and the courier escalation reference.
Does Flipkart pay for parcels lost by the courier?
Yes, through SPF when the courier is confirmed as the responsible party. The 120-day product-missing window applies specifically to this scenario. Success depends on evidence of non-receipt at your warehouse and courier confirmation of loss.
Why did my Flipkart return not received claim get rejected?
Most commonly for using the wrong reason code, filing after the actual window expired because you waited for the longer product-missing window that did not apply, or missing courier escalation reference for lost-parcel scenarios.
Sources: Flipkart publicly stated SPF framework as of September 2026, TrackVid platform data across 1,100+ Indian sellers, cross-platform claim scenario analysis.
Flipkart SPF rules, reason codes, and claim windows change periodically. Verify current terms from your Flipkart Seller Dashboard before relying on this guidance for a specific claim.
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