How to Analyze Return Reasons: Reason Codes, Reason Distribution, Return Rate by Product, Return Cost and Action Plan Tutorial
How do you analyze return reasons? Reason codes, reason distribution, return rate by product and return cost: an 8-lesson guide with worked calculations.
Contents 14 sections
- What will you be able to do by the end of this training?
- Lesson 1: Why is the return rate not enough on its own?
- Lesson 2: How are return reasons coded?
- Lesson 3: How is the reason distribution produced?
- Lesson 4: How is the return rate by product found?
- Lesson 5: How is the cost of a return calculated?
- Lesson 6: Which reasons are controllable and what action should be taken?
- Lesson 7: How is the effect of the actions calculated?
- Lesson 8: How are return reasons monitored?
- What are the most common mistakes when analyzing return reasons?
- How does NetKasam make return reason analysis easier?
- Mini quiz: Test what you have learned
- Conclusion: Manage returns by reason, not by percentage
- Frequently Asked Questions About Return Reason Analysis
Knowing the return rate as a percentage is not enough to reduce returns. An 11% return rate may come from size mismatch in one business, from parcels arriving damaged in another, and from a product description creating the wrong expectation in a third. The fixes for the three cases are completely different. Return reason analysis finds the real reason behind the same percentage and shows you what you lose the most money on.
This article is not a narrative but an 8-lesson hands-on tutorial. We will answer how to analyze return reasons through a sample business that receives 2,000 orders a month and sees 220 returns: coding the return reasons, the reason distribution, the return rate by product, the cost of a return, separating controllable from uncontrollable reasons, the effect of the actions and tracking indicators. At the end there is a mini quiz with an answer key. All figures are sample values chosen to demonstrate the method; follow the same steps with your own data.
What will you be able to do by the end of this training?
In short: You will code the return reasons, rank the reasons and products by return rate, calculate the cost of a return and choose the three actions that pay off the most.
- 01CodeGive each return a single reason code.
- 02CountRank the reasons by count and percentage.
- 03Drill downFind the return rate by product.
- 04PriceCalculate the unit cost of a return.
- 05SeparatePick the controllable reasons.
- 06PreventTake action and monitor the rate.
The 8 lessons of the tutorial: (1) why the return rate is not enough, (2) reason codes, (3) reason distribution, (4) return rate by product, (5) the cost of a return, (6) controllable reasons and actions, (7) the effect of the actions, (8) tracking indicators.
Lesson 1: Why is the return rate not enough on its own?
In short: The return rate shows how big the problem is, not its cause. An action taken without knowing the cause solves the wrong problem.
The return rate is found by dividing the number of returned orders by total orders. In the sample business it is 220 ÷ 2,000 = 11%. This figure does not answer whether it is high or low; it varies by sector, product and sales channel. What matters is the direction of your own rate over time and how its parts are distributed. For general ways to reduce returns, see how to lower the return rate; this article is a step before that: it answers with data the question of which action for which reason.
Analyzing reasons has three benefits. First, it directs the action to the right place: a size chart for size returns, packaging for damage returns. Second, it shows where the cost comes from. Third, it lets you measure whether an action worked, because the rate by reason can be compared before and after. We explained the monetary cost of a return in detail in how to calculate return cost.
Lesson 2: How are return reasons coded?
In short: Give each return a single reason code from a predefined list. The list should be short, mutually exclusive and make clear which party is responsible for each reason.
Do not leave the reason list as free text from the start; free text cannot be analyzed. A list of six to eight codes is enough for most businesses. Next to each code, write who can fix it:
| Reason code | Meaning | Who can fix it |
|---|---|---|
| Wrong size or measurement | The product did not fit the customer | Product content (size chart) |
| Product differs from description | Color, material or feature did not match expectations | Product content (image, description) |
| Arrived damaged or defective | Package or product arrived with a problem | Packaging, shipping, quality control |
| Late delivery | Customer did not wait for delivery | Shipping, preparation time |
| Changed mind | Customer changed their mind | Mostly outside your control |
| Other | Does not fit the above | Reviewed separately |
If the share of "other" exceeds 10%, review the list again; an "other" that grows too large makes the analysis meaningless. Entering the reason code when the return record is opened is far more reliable than guessing afterward. In marketplace returns, the reason chosen by the customer and your code may differ; keep the two separate and assign your own code after you receive the product. Consider the return of the returned product to stock together with how to put a returned product back into stock; the condition of the product (sellable, damaged) is reason data.
Lesson 3: How is the reason distribution produced?
In short: Count the reasons as numbers, convert them to percentages by dividing by total returns and sort from largest to smallest.
- Return rate = Returned orders ÷ Total orders
- Reason share = Orders returned for the reason ÷ Total returns
- Monthly return cost = Number of returns × Unit cost of one return
In the sample business, 220 returns came from 2,000 orders in a month. The distribution by reason is as follows:
| Reason | Return | Share |
|---|---|---|
| Wrong size or measurement | 77 | %35,0 |
| Product differs from description | 44 | %20,0 |
| Arrived damaged or defective | 33 | %15,0 |
| Changed mind | 30 | %13,6 |
| Late delivery | 22 | %10,0 |
| Other | 14 | %6,4 |
| Total | 220 | %100 |
- Wrong size or measurement₺7735%
- Product differs from description₺4420%
- Damaged or defective₺3315%
- Changed mind₺3013.6%
- Late delivery₺2210%
- Other₺146.4%
Prepared with sample values. Total: 77 + 44 + 33 + 30 + 22 + 14 = 220 returns.
The first three reasons make up 77 + 44 + 33 = 154 of total returns, that is 70%. These three relate to product content and packaging and are under the business's control. The "changed mind" and "other" items are largely outside your control. This distinction is the basis of the action plan (Lesson 6).
Lesson 4: How is the return rate by product found?
In short: Divide each product's number of returns by its own number of orders. A few products with high return rates carry a large share of total returns.
The overall rate hides the differences between products. The sample business's table by product:
| Product | Order | Return | Return rate |
|---|---|---|---|
| Product A | 400 | 60 | %15,0 |
| Product B | 300 | 21 | %7,0 |
| Product C | 250 | 40 | %16,0 |
| Product D | 600 | 48 | %8,0 |
| Other products | 450 | 51 | %11,3 |
| Total | 2.000 | 220 | %11,0 |
- Product C16.0%
- Product A15.0%
- Other products11.3%
- Product D8.0%
- Product B7.0%
Prepared with sample values. Rate: product's returns ÷ product's orders.
Products A and C make up (400 + 250) ÷ 2,000 = 32.5% of orders but produce (60 + 40) ÷ 220 = 45.5% of returns. Starting the action list with these two products is far more efficient than work spread across the whole catalog. Cross each product with its own reason distribution: A's returns may be size-driven, C's description-gap-driven. To see product-level profitability and the effect of returns together, see how to analyze profitability by product.
Lesson 5: How is the cost of a return calculated?
In short: The unit cost of one return is the sum of return shipping, handling labor, repackaging and the loss in value of the product that cannot be sold.
| Cost item | Example amount |
|---|---|
| Return shipping fee | 45 ₺ |
| Receiving, inspection and repackaging labor | 20 ₺ |
| Customer communication and record keeping | 10 ₺ |
| Product value loss share (average of damaged or non-resellable returns) | 20 ₺ |
| Total unit cost | 95 ₺ |
The monthly return cost is 220 × 95 = ₺20,900. This amount does not include lost sales; the revenue of the returned order is already deducted. The unit cost can also vary by reason: a damaged return is more expensive because it cannot be resold, while in a "changed mind" return the product is usually resold. For a more precise analysis, use a separate unit cost per code. To calculate shipping cost correctly, see how to calculate desi. For issuing the return invoice, the steps in how to issue a return invoice apply.
Recommended readingHow Do You Calculate Return Cost?Lesson 6: Which reasons are controllable and what action should be taken?
In short: Separate the reasons into controllable and uncontrollable. Plan actions on the controllable ones, starting with the largest count and cost.
| Reason | Returns (units) | Action | Expected impact |
|---|---|---|---|
| Wrong size or measurement | 77 | Add a size chart, model measurements and a "size up/down" note to the product page | 30 returns prevented (77 → 47) |
| Product differs from description | 44 | Fix the true-color image, material and size information, and cover frequently asked questions in the description | 15 returns prevented (44 → 29) |
| Arrived damaged or defective | 33 | Strengthen packaging, run a quality check at dispatch, review the problematic carrier | 11 returns prevented (33 → 22) |
| Late delivery | 22 | Monitor carrier performance, shorten preparation time | Separate effort |
| Changed mind, other | 44 | Outside your control; only monitor | Not included in the calculation |
The action list should be short and owned: write each action's owner, date and the indicator it will be measured by. When fixing product content, use the content checklist in how to prepare a product card. For keeping damage and loss records, see how to track lost and damaged shipments, and to measure the carrier, see how to measure carrier performance.
Lesson 7: How is the effect of the actions calculated?
In short: Multiply the number of prevented returns by the unit cost and calculate the new return rate.
With three actions, total prevented returns are 30 + 15 + 11 = 56. The new number of returns is 220 − 56 = 164, and the new return rate is 164 ÷ 2,000 = 8.2%. The prevented cost is 56 × 95 = ₺5,320.
- Monthly return cost (220 returns)₺20,900
- Cost of prevented returns (56 returns)−₺5,320
- Monthly return cost after actions (164 returns)₺15,580
Prepared with sample values. Calculation: 20,900 − 5,320 = ₺15,580.
The yearly effect is 5,320 × 12 = ₺63,840, and the calculation does not include the effect on customer satisfaction, negative reviews and ratings. Be sure to account for the actions' own costs (the labor of preparing a size chart, the unit price of reinforced packaging). For example, if the packaging improvement adds ₺2 per order, then for 2,000 orders it brings a monthly cost of ₺4,000 and exceeds the 11 × 95 = ₺1,045 gained from damage returns; this action does not pay for itself. Calculate the gain separately for each action. For the packaging side, see how to calculate and reduce packaging cost.
- 70%share of returns caused by product content and packaging (154 ÷ 220)
- 45.5%return share of two products (A and C)
- ₺20,900monthly return cost
- 8.2%expected return rate after the actions
Lesson 8: How are return reasons monitored?
In short: Track five indicators monthly: return rate, reason shares, rate by product, monthly return cost and the effect of the actions.
| Indicator | How it is calculated | Sample value |
|---|---|---|
| Return rate | Returns ÷ Orders | %11,0 → %8,2 |
| Reason share | Returns for the reason ÷ Total returns | Size 35%, description 20%, damage 15% |
| Product-level rate | Product's returns ÷ Product's orders | A 15%, C 16% |
| Monthly return cost | Returns × unit cost | 20.900 ₺ → 15.580 ₺ |
| Share of other | Returns coded other ÷ Total returns | 6.4% (target: below 10%) |
Keep the indicators as a saved report and compare them in the same format every month. An action's effect is proven only when the share and count of that reason fall; the overall rate can fluctuate because of season and campaigns. Returns usually behave differently during campaign periods; evaluate the period separately, as in how to measure the sales drop after a campaign. To bring the report into the weekly meeting, see how to prepare a weekly management report.
Recommended readingHow to Measure and Shorten Time to Ship: Time Distribution, Cost of Delay, Causes of Delay, Rating Threshold Effect and Improvement TutorialWhat are the most common mistakes when analyzing return reasons?
- Leaving the reason as free text. It cannot be analyzed and the "other" pile grows.
- Taking the customer's chosen reason as is. Customers often say "the product is not what I wanted"; the real reason is found when you inspect the product.
- Looking only at the overall rate. You cannot see the differences between products.
- Trying to fix every product with the same action. Packaging work is done for a product with a size problem.
- Not counting the cost of the action. An improvement that costs more than the gain results in a loss.
- Not measuring the effect. The action was taken but the reason share was not monitored.
- Spending effort on an uncontrollable reason. The effort spent on reducing "changed mind" returns is the lowest-return work.
How does NetKasam make return reason analysis easier?
- Orders on one screen. You see marketplace and e-commerce orders in a single panel and filter them by status (order management).
- Return invoice and stock. You issue the invoice for the returned product and track stock movements in the detailed stock movements report (inventory management).
- Variant tracking. Because you track the stock of variants such as size and color separately, you can see size-driven returns at the variant level.
- Saved reports. You save the monthly return report and export it to Excel (reports).
- Shipping integration. You track shipping status and keep damage and late-delivery records (shipping integration).
- Bookkeeping is free. e-Invoice, customer and supplier accounts, inventory, cash, bank and expense management are free in every plan; see the pricing page for details.
Mini quiz: Test what you have learned
In short: Answer the 5 questions below, then compare with the answer key. 4 or 5 correct shows you have completed the training.
- If 220 of 2,000 orders were returned, what is the return rate in percent?
- If 77 returns come from size mismatch, what percentage of total returns is that?
- If the unit cost of a return is ₺95, what is the monthly cost of 220 returns?
- If 56 returns are prevented, what is the new return rate in percent?
- What is the monthly saving from the 56 prevented returns?
Answer key:
- 220 ÷ 2.000 = %11.
- 77 ÷ 220 = %35.
- 220 × 95 = 20.900 ₺.
- (220 − 56) ÷ 2.000 = 164 ÷ 2.000 = %8,2.
- 56 × 95 = 5.320 ₺.
Frequently Asked Questions About Return Reason Analysis
How do you analyze return reasons?
Each return is given a single reason code from a predefined list. Reasons are ranked by count and percentage, then the return rate is calculated per product and actions are planned for the reasons you can control.
How should return reasons be coded?
Use a mutually exclusive list of six to eight codes: wrong size, different from description, damaged, late delivery, changed mind and other. Write down who can fix each code.
Is the reason chosen by the customer enough?
Usually not. Customers often choose a generic reason. After you receive the product, confirm or correct the code with your own inspection.
Why does the return rate by product matter?
The overall rate hides the differences between products. A small number of products generate most of the returns; it is more efficient to start taking action there.
How is the cost of a return calculated?
The return shipping, handling and repackaging labor, customer communication and the loss in value of a product that cannot be resold are added together. The unit cost can vary by reason.
Which return reasons are controllable?
Those arising from product content (size, description, image), packaging and shipping performance are controllable. A customer changing their mind is largely outside your control.
How do I know the action worked?
The count and share of the targeted reason should fall. Because the overall rate is affected by season and campaigns, compare by reason.
How often should return reasons be reviewed?
Monthly. Campaign periods are evaluated separately, and products with high returns can also be monitored weekly.
Conclusion: Manage returns by reason, not by percentage
The most useful thing you can do today is to assign reason codes to the last month's returns and count the reasons. Then find the two products with the highest return rate, set a single action for the dominant reason of those products and re-measure the reason share a month later. A small but correctly targeted change prevents more returns than a general improvement effort.
Bookkeeping Is Now Completely Free
Manage your bookkeeping and e-Invoice operations with NetKasam without paying a thing. Customer and supplier accounts, inventory, collections and more in one panel, completely free.