Summary
A fresh sizing based on 3.3k SF claims was done where all images in the RVP leg were present (Pickup, RPC, ICSD, Evidence) This was split between our Product team (1.5k) and Agent audits (1.8k) Both audits converged to a similar result, thereby building conviction in the sizing Of 16% CR-CAS, sellers abuse is the leading cause with 7.5pp (47% of claims) contribution Specifically, 2 use-cases of Sellers abuse: Swap Product Claims - 6.5 pp (~40.5% of claims) | Cases where the Seller received the correct product, but swapped It with a completely different product to raise a claim (Evidence <> ICSD) Same Product Claims - 1 pp (~6.5% of claims) Cases where Sellers received a correct product and raised a claim on that same product (Evidence =Catalog) Remaining 8.5pp of CR-CAS is composed of: WFR - 4.4p (27% of claims) 3P swaps - 1.8pp (11% of claims) Incorrect pickups - 1.4pp (9% of claims) Subjective cases - 1pp (6% of claims) Subjective cases contribute 1pp to CR CAS. These are cases where the product that was picked was delivered and shown in the claim evidence. While, the product is very similar to catalog, it is not an exact match. These were classified as Seller Abuse in previous sizing exercises. This is line with the done during R2R where Seller-side issues accounted for 43% of total claims. Following are 2 key call-outs:
For Seller-abuse (7.5 claims pp), focus will be to double-down & scale identified WIP levers: One key difference we see from previous sizing is that Seller side fraud MO has shifted from Same Product Claims to Swap Product Claims. This shift was expected due to graded penalty running on EvsC flagged cases. Hence, we remain confident on our seller side claim reduction levers that were presented at start of R2R to tackle both these problems (ICSD for Swap Product Claims detection; EvC for Same Product Claims detection; Graded Penalty as the uber-penalty lever)
2. For WFR (4.4 pp) reduction, focus is on better instrumentation/deterrent experiments for right attribution & actioning:
We have started a sizing exercise from a WFR claims perspective to understand where the problem lies: Seller, FE, User. Post sizing, we will work on the following three pillars
Full list of Initiatives for each problem type are detailed
Details
Methodology
We conducted two separate audits to understand where abuse happens in RVP (customer) returns on the platform. These audits were conducted on claims raised under “I have received wrong return”. Audits were conducted by Product team (1.5k cases) and Agents (1.8k cases) separately. During these audits we separated out subjective cases—where the product received by sellers closely matches their catalog—from other types of returns. This separation is intended to ensure that subjective cases are not misclassified as seller abuse, as occurred in previous sizing exercises. Audits were done by utilizing images available from various stages in the supply chain to understand where abuse occurs. The images used for this audit included: Customer Doorstep Pickup Image RPC Image (taken by the hub manager at the seller's RTS hub) Image at Seller Doorstep (ICSD) (taken by the field executive at the seller's doorstep) Evidence Image/Video (provided by the seller during the claim raising process) In addition to categorizing claims by customer return type (Param and Smart QC), we also differentiated based on the type of product received by the seller (as compared to the Catalog Image). For sizing purposes, we split them into
Completely different category Major Design/Color change Subjective cases (Slight design/colour change) - called out separately (previously part of Seller Abuse) Same Product (attributed to Seller Abuse) Results
Next Steps
WFR solutioning levers
An overall image-triangulation data layer that will run on top of these accountability levers to compare- and assign attribution to right stakeholder.
Samples (Optional)
Cases of seller swap:
Seller Swap was verified as Pickup Image = RPC image = ICSD Image BUT ICSD Image is != Claim/Evidence Image. Further be verified the Packet ID and Timestamp to make sure the FE had delivered the correct shipment
Type of Product received by seller (as compared to Catalog Image)