Return Rate and Reasons

The return rate is one of the most important KPIs in e-commerce fulfillment. It shows how many shipped orders come back as returns – and thus how well product, content and logistics match customer expectations. If you only know the rate but not the reasons behind it, you optimize blindly: High return rates without root cause analysis lead to wrong measures, wasted labels and strained margins.

This guide explains how to correctly calculate and assess the return rate, which return reasons dominate in which industries, and how to derive concrete improvements for assortment, shop and warehouse from the data.

What the return rate tells you

The return rate measures the proportion of orders or items that are sent back by the customer. It is not a quality judgment of your fulfillment alone, but a reflection of the entire shopping experience: product description, size guidance, packaging, delivery speed and return friendliness all play a role together.

Formulas and calculation variants

Depending on your analysis goal, you use different formulas:

001. Return rate on order basis
Number of returned orders divided by number of shipped orders in the same period. This variant is suitable for management reporting and industry comparisons.

002. Return rate on item basis
Number of returned items divided by number of shipped items. Useful for multi-item orders, bracketing (ordering multiple sizes) and detailed SKU analysis.

003. Value-based return rate
Return value divided by revenue. Shows the financial burden – especially relevant for premium assortments with high product value.

Return rate vs. returns trend – clarifying terms

In everyday use, the terms are often used synonymously. More precisely: The return rate usually refers to the percentage share, while the returns trend can additionally describe temporal developments or seasonal fluctuations. What matters is that you define a uniform definition internally and use the same formula in reports, WMS and BI dashboards.

Typical return rates by industry

Return rates depend on the industry. A value of 15 percent is high for electronics, but normal for fashion. Therefore always compare your rate with your own historical trend and industry-specific benchmarks – not with the overall market average.

The most important return reasons at a glance

Return reasons can be divided into three categories: customer-driven, product-driven and process-driven. Systematic capture in the returns portal is the foundation for every optimization.

Customer-driven reasons

These reasons arise from buying behavior or subjective expectations – not necessarily from an error in the shop:

• Bracketing: Order multiple sizes or colors, keep one
• Impulse purchase regretted: Item does not appeal after trying on
• Budget adjustment: Customer wants money back, not the item
• Gift does not fit: Recipient has different expectations

Product-driven reasons

Here the improvement potential often lies directly in the assortment or product presentation:

• Size does not fit – most common reason in fashion; see Sizes and variants
• Color or material differs – product photos not representative
• Quality does not meet expectations – check reviews and description
• Defect or flaws – warranty case, not withdrawal

Process-driven reasons

These reasons arise in fulfillment or shipping – and are directly influenceable:

• Wrong delivery – picking error or wrong SKU
• Damage in transport – packaging or carrier problem
• Delivery too late – customer already bought a replacement
• Incomplete delivery – missing parts or accessories

Systematically capturing return reasons

Without structured reason capture, the return rate remains a number without actionable guidance. Professional shops capture reasons already during return registration – not only during warehouse inspection.

Mandatory fields in the returns portal

1. Order number and item SKU – unique assignment
2. Return reason from dropdown – standardized categories, no free text as primary source
3. Optional free text – for details not covered by the dropdown
4. Quantity and condition – pre-selection by customer, confirmation in warehouse
5. Timestamp – for turnaround time analyses

Reconciliation customer statement vs. warehouse inspection

In practice, customer statements and warehouse findings occasionally differ: The customer selects "Does not appeal", but inspection in the warehouse reveals a defect. A reconciliation process improves data quality:

1. Customer reason is saved during registration
2. Employee confirms or corrects the reason during inspection
3. Deviations are evaluated monthly – recognize systematic miscategorizations

From return rate to concrete measures

A high return rate alone does not yet say what needs to be done. The combination of rate, reasons and affected SKUs provides the roadmap.

Analysis workflow in five steps

001. Determine baseline
Evaluate return rate of the last 12 months by month, category and top 20 SKUs. Consider seasonal peaks after sales and Christmas separately.

002. Identify top 3 reasons
Which three reasons together account for more than 60 percent of all returns? Focus your first measures on these.

003. Form SKU clusters
Isolate items with above-average rate. Patterns often emerge: one size group, one color, one supplier.

004. Prioritize measures
Sort by effort and impact: content updates are quick, assortment changes take longer, process optimization in the warehouse has immediate effect on wrong deliveries.

005. KPI review after 90 days
Has the rate improved for affected SKUs? If not, test the next hypothesis.

Measures by main reason

For fit problems, detailed size charts, model measurements, customer reviews with size notes and virtual try-on help. For expectation deviation, consistent product photos, 360-degree views and honest material descriptions are central. For wrong deliveries, you increase pick accuracy through scanners, pick-by-voice or double-check for critical SKUs.

Lowering return rate – without worsening the customer experience

Many shops try to lower the rate through restrictive return policies. This can work short-term, but harms conversion and repeat purchase rate in the long run. More sustainable are measures that prevent returns before they occur:

• Optimize product pages – fewer expectation gaps
• Size guidance and filters – less bracketing needed
• Quality control before shipping – fewer defect and wrong delivery returns
• Appropriate packaging – fewer transport damages
• Fast delivery – fewer "too late" returns

Checklist: Professionally managing return rate and reasons

• Uniform formula for return rate defined internally
• Monthly reporting by category, SKU and channel set up
• Standardized return reasons stored in returns portal
• Reconciliation of customer statement and warehouse inspection anchored in process
• Top 20 SKUs by return rate analyzed quarterly
• Measures log with responsible persons and review date maintained
• Return cost per return shown alongside rate
• Seasonal peaks considered in capacity planning

Return reasons dashboard – central KPIs

Practical example: Return rate from 38 to 29 percent

An online shoe retailer had a return rate of 38 percent with 120 orders per day. Reason capture showed: 47 percent "Size does not fit", 22 percent "Does not appeal", 9 percent "Damaged".

Measures over six months:

1. Size chart with cm measurements and last info per model
2. Customer reviews with size note ("Runs small") prominently placed
3. Reinforced padding in shoe boxes, carrier change for damages
4. Return reason "Last unknown" as new category – revealed gap in description

Result: Return rate dropped to 29 percent, restocking rate increased from 71 to 81 percent. Cost per return decreased by 12 percent due to fewer transport damages.

Related topics

• Returns basics
• Return processing with DHL
• Returns portal and labels
• Storing return goods and B-grade stock
• Right of withdrawal and returns