Concrete takeaway
Management dashboards often show returns as a percentage of orders and stop there. A 5% rate can look manageable: 95 orders succeeded and only five came back. But the P&L doesn't experience returns as percentages — it experiences one successful order as positive contribution and one returned order as a negative contribution event. When the successful order is thin-margin and the return is expensive, five returned orders can erase the contribution from far more than five successful orders.
A worked example: 100 orders
Consider a personal-care product's contribution on a successfully delivered order, and the loss on a returned one. All figures are net of GST and discounts where relevant. In this example, 70% of returned units are assumed to be opened or otherwise unsuitable for resale as new, creating expected inventory impairment of 70% × INR 390 = INR 273.
The 70% non-resellable assumption is specific to this worked example. Sealed, durable categories may see much lower impairment; opened beauty, food, hygiene or damaged products may see much higher impairment.
The 5% return-rate calculation
| Scenario | Calculation | Contribution |
|---|---|---|
| No returns | 100 successful orders × INR 140 | INR 14,000 |
| 95 successful orders | 95 × INR 140 | INR 13,300 |
| 5 returned orders | 5 × −INR 543 | −INR 2,715 |
| Contribution after returns | INR 13,300 − INR 2,715 | INR 10,585 |
A 5% return rate has reduced contribution by 24.4% in this example. The result isn't a universal benchmark — it follows directly from the product's INR 140 successful-order contribution and INR 543 return loss.
The formula every brand should use
The term C + L is the full economic swing — a returned order doesn't merely create a loss of INR 543, it also replaces an order that would have generated INR 140. The swing is INR 683.
| Interpretation | Calculation | Result |
|---|---|---|
| Successful orders needed to fund direct return loss | INR 543 ÷ INR 140 | 3.88 orders |
| Successful-order contributions erased by full swing | INR 683 ÷ INR 140 | 4.88 orders |
| Return rate at which expected CM reaches zero | INR 140 ÷ INR 683 | 20.5% |
This is why a small return-rate movement can have a disproportionate impact on thin-margin SKUs.
Return rate is not one metric
Before calculating the economics, define the denominator — different teams frequently use different return rates while believing they're discussing the same number.
| Metric | Formula | What it reveals |
|---|---|---|
| Order return rate | Returned orders / delivered orders | Customer-order frequency of returns |
| Unit return rate | Returned units / delivered units | Impact of multi-unit orders and partial returns |
| Value return rate | Returned sales value / delivered sales value | Whether high-value products are overrepresented |
| RTO rate | Undelivered returned orders / shipped orders | Pre-delivery failure, operationally distinct from customer returns |
| Non-resellable return rate | Impaired returned units / returned units | Inventory-value destruction |
RTO and post-delivery customer returns should be shown separately — different causes, different cost stacks, different interventions.
Build the return loss from actual cost components
The return loss shouldn't be a generic percentage of selling price. Build it from the order ledger and warehouse disposition data:
Outbound cost incurred
Reverse movement
Non-recovered charges
Return processing
Inventory impairment
Working-capital time
The return waterfall management should see
| Stage | Orders from 10,000 shipped | Rate | Economic treatment |
|---|---|---|---|
| Delivered | 9,200 | 92.0% | Eligible for customer-return analysis |
| RTO | 800 | 8.0% of shipped | Forward + reverse + processing; no completed sale |
| Customer returns initiated | 460 | 5.0% of delivered | Separate from RTO |
| Received back | 430 | 93.5% of initiated | Check leakage and pending returns |
| Resellable as new | 150 | 34.9% of received | Return to available inventory after QC |
| Markdown/secondary sale | 80 | 18.6% of received | Record recovery value and margin loss |
| Non-resellable | 200 | 46.5% of received | Write-off, vendor claim or disposal |
Illustrative waterfall. The key is connecting customer-return reasons to physical warehouse disposition and financial recovery.
Why aggregate return rate hides the real problem
Prioritise return reduction by rupee impact
Return projects shouldn't be ranked only by number of returns. Rank them by expected contribution recovered:
| SKU | Avoidable returns | Economic swing per return | Opportunity value |
|---|---|---|---|
| SKU A | 120 | INR 683 | INR 81,960 |
| SKU B | 250 | INR 240 | INR 60,000 |
| SKU C | 60 | INR 1,050 | INR 63,000 |
SKU B has the most avoidable returns, but SKU A creates the largest contribution opportunity in this example.
A disciplined return-reduction loop
Standardise reason codes
Link reason to disposition
Calculate SKU-level economic swing
Fix the highest-value cause
Run a post-fix cohort
The operating principle
Returns are not a reverse-logistics statistic. They are a product, catalogue, fulfilment and financial outcome compressed into one event. A brand that knows only its return percentage knows how often the problem occurs. A brand that knows the economic swing by SKU knows where to act.
Methodology note
Want to see your own economic swing by SKU? SuperNode can build the return-loss and reconciliation model from your order ledger and warehouse disposition data.
