Return rate: formula, causes and how to reduce it
The return rate shows what share of sold goods or revenue is returned after purchase. The metric directly affects margin, cash flow, and service reputation: excessive returns "eat up" profit, overload logistics, and signal problems with the product, descriptions, or customer expectations.
Why the Metric Matters
Monitoring returns helps identify defects, size/specification mismatches, weak points in delivery or packaging, as well as inconsistencies in pricing and promotional strategy. A balanced return policy increases customer trust but must remain manageable in terms of costs.
Calculation
- By units: Return rate (units), % = (Returned units / Sold units) × 100
- By orders: Share of orders with a return, % = (Orders with any return / All orders) × 100
- By revenue: Return rate (₴), % = (Amount of returns / Revenue) × 100
A cohort approach is recommended: match returns with sales from the same cohort (for example, "all May orders and their returns within 30 days") to avoid time shifts. Separate cancellations before shipment from actual returns. For accurate economics, account for reverse logistics, repairs/markdowns, and payment system fees.
Calculation example
2,000 units were sold in a month and 90 returned. Return rate = 90 / 2,000 × 100 = 4.5%. If one product group has 12% and the rest 3%, the problem lies in the description, quality or sizing of that group.
Data Sources
ERP/1C, warehouse accounting and RMA system, online store CMS, marketplaces, billing and payment providers, delivery services. Consistent reference lists of return reasons, statuses, and SKUs are required.
Interpretation
- Rising returns with unchanged demand signal problems with quality, descriptions, or expectations
- High returns by channel are often related to promo policy, the storefront, or traffic quality
- Asymmetry by SKU/size/batch points to production or supply failures
- Return processing time affects loyalty and repeat purchases: slow refunds reduce retention
Useful Breakdowns
- Categories/brands/SKUs/sizes
- Channels: online, offline, marketplaces, distributors
- Reasons: size/color, defect, "not as described," damage in delivery, "changed my mind"
- Managers/regions/delivery services
- Cohorts by purchase month and return window (7/14/30 days)
Dashboard Visualizations
- Trend of the return rate over time with year-over-year comparison
- Distribution of returns by reason and channel
- Heat map of SKU × size/batch
- Waterfall of the impact of returns on gross profit
- Processing SLA: median time from request to refund
Approaches to Reduction
- Better content: accurate size charts, real photos/videos, honest descriptions, UGC reviews
- Packaging quality and pre-shipment checks; reliable delivery services
- Preventive scenarios in the cart: size comparison, recommendations of alternatives
- Post-sale support: quick consultations, exchanges instead of returns
- Anti-fraud for suspiciously frequent returns; separate rules for high-risk segments
How to Set Goals
Set threshold return levels by category/channel (e.g., ≤5% for electronics, ≤12–15% for fashion), a processing SLA (N days to refund), and targets for the share of "genuine" returns (where the reason is an actual malfunction) versus "manageable" ones (description/size/expectations).
Common Mistakes
- Mixing cancellations and returns
- Comparing unequal periods without accounting for the return window
- Ignoring partial returns within an order
- Not accounting for reverse logistics and markdowns
- Different VAT/currency rules across channels
Questions for Discussion
- Which 10 SKUs contribute the most to returns, and why?
- Which reasons dominate in each channel?
- How many days does a standard return take until refund?
- Is the growth in returns linked to specific campaigns or changes in product pages?