How Do You Classify and Reduce Customer Complaints? A Course on Complaint Rate, Root Cause, Cost and a Correction Plan
How do you classify and reduce customer complaints? Complaint rate, category, root cause, cost and correction plan: an 8-lesson e-commerce guide.
Contents 15 sections
- What will you be able to do by the end of this training?
- Lesson 1: Why should complaints be read together rather than one by one?
- Lesson 2: How is the complaint rate calculated?
- Lesson 3: What categories can complaints be divided into?
- Lesson 4: How do you find the root cause?
- Lesson 5: What does a complaint cost?
- Lesson 6: Which problem is fixed first?
- Lesson 7: How are complaints reduced?
- Lesson 8: How do you monitor complaint management regularly?
- How do you write a reply to a complaint?
- What are the most common mistakes in complaint management?
- How does NetKasam make complaint analysis easier?
- Mini quiz: Test what you have learned
- Conclusion: Read a complaint as a process to fix, not a case to close
- Frequently Asked Questions About Customer Complaints
Complaints are usually handled one by one: a customer writes, you reply, you compensate, and the matter is closed. At the end of the month, if you ask how many complaints came in, there is no clear number, and you never know which ones keep repeating. Yet a complaint is the cheapest data that tells you which process in your business is failing. When it is not classified, it stays only a cost item.
This post is not a narrative but an 8-lesson hands-on course. We will answer the question how to classify and reduce customer complaints using a sample e-commerce store that receives 3,000 orders a month: the complaint rate, separating category from root cause, cost per complaint, priority order, a reduction plan and regular monitoring. At the end there is a mini quiz and an answer key. All figures are sample values chosen to demonstrate the method; use your own complaint records.
What will you be able to do by the end of this training?
In short: You will calculate the complaint rate, split complaints by category and root cause, find their cost and decide which problem to fix first.
- 01CollectPut the complaints from all channels into a single list.
- 02CategorizeGive each complaint one category.
- 03Find the root causeWrite down which process the complaint came from.
- 04ValueCalculate the cost per complaint.
- 05PrioritizePick the problem that costs the most.
- 06ReduceFix the process and monitor the result.
The 8 lessons of the course: (1) why complaints count, (2) the complaint rate, (3) categories, (4) root causes, (5) complaint cost, (6) priority order, (7) the reduction plan, (8) regular monitoring.
Recommended ReadingHow Do You Find and Close Account Reconciliation Differences? A Course on Letters and Statements, Types of Differences, Difference Analysis, Correcting Entries and Unanswered AccountsLesson 1: Why should complaints be read together rather than one by one?
In short: A single complaint is an incident, a repeated complaint is a process failure; the failure becomes visible only when it is counted.
When one customer writes that a parcel arrived late, you may take it for a problem specific to that customer. If ten customers write the same thing in the same week, the problem is in the warehouse, the carrier or the order flow. Reading complaints together does three things: it shows which problem is frequent, which one is expensive, and whether a fix is working.
A complaint and a customer message are not the same thing. Most messages are questions or information requests; a complaint is a message saying that an expectation was not met. To measure message response time, see the post how to measure and shorten customer message response time. In this post we work only with records marked as complaints.
Lesson 2: How is the complaint rate calculated?
In short: Divide the number of complaints in the period by the number of orders in the same period; the rate lets you compare regardless of order volume.
- Complaint rate = Number of complaints ÷ Number of orders
- Cost per complaint = Resolution time cost + Compensation cost
- Monthly complaint cost = Number of complaints × Cost per complaint
- Category share = Complaints in the category ÷ Total complaints
In the sample store, 150 complaints come in on 3,000 orders: the rate is 150 ÷ 3,000 = 5%. One in every 20 orders ends in a complaint. Track this rate weekly and break it down by channel; the marketplace and your own site may not be the same. For how it relates to the general indicators on the seller scorecard, see the post how to track marketplace seller performance.
Lesson 3: What categories can complaints be divided into?
In short: Give each complaint one main category; keep the number of categories at 6–8 so they stay countable.
- Late delivery₺4530%
- Damaged or defective product₺3020%
- Wrong or missing item₺2416%
- Product not as described₺2416%
- Return and refund delay₺1510%
- Communication and no reply₺128%
| Category | Count | Share |
|---|---|---|
| Late delivery | 45 | %30 |
| Damaged or defective product | 30 | %20 |
| Wrong or missing item | 24 | %16 |
| Product not as described | 24 | %16 |
| Return and refund delay | 15 | %10 |
| Communication and no reply | 12 | %8 |
| Total | 150 | %100 |
The top two categories, with 75 complaints, make up 50% of the total. Keep categories short and mutually exclusive; if the "other" category grows, open a new one. To dig into the causes of return-related complaints, see the post how to analyze return reasons.
Lesson 4: How do you find the root cause?
In short: The category tells you what the complaint is, the root cause tells you which process it came from; the fix is applied to the root cause.
| Category | Likely root cause |
|---|---|
| Late delivery | A delay in handing the parcel to the carrier, or a carrier delay |
| Damaged product | Insufficient packaging or transit damage |
| Wrong/missing item | Picking error, or code or label mix-up |
| Not as described | Product page incomplete or wrong |
| Return/refund delay | Delay in the product reaching and being processed at the warehouse |
| No reply | No order or ownership in the message flow |
- Shipping and delivery60 complaints
- Warehouse and picking30 complaints
- Product page and content24 complaints
- Supplier and product quality21 complaints
- Customer service and the return process15 complaints
The root cause breakdown differs from the category breakdown: shipping-related problems are spread across both the late delivery and damage categories and in total make up the largest share (60 ÷ 150 = 40%). To measure the shipping side, see the posts how to measure carrier performance and how to measure and shorten handover-to-carrier time. Make the root cause a mandatory field when recording a complaint; filling it in later by guesswork will not be reliable.
Lesson 5: What does a complaint cost?
In short: Add the resolution time cost and the compensation cost per complaint; multiplying by the number of complaints gives the monthly cost.
In the example, resolving one complaint takes an average of 25 minutes and a minute costs ₺2, so the resolution time cost is 25 × 2 = ₺50. If compensation (a resend, a partial refund or a coupon) averages ₺120, the cost per complaint is 50 + 120 = ₺170. The monthly cost of 150 complaints is 150 × 170 = ₺25,500.
| Item | Account | Amount |
|---|---|---|
| Resolution time | 25 min × ₺2 | 50 ₺ |
| Compensation | Average | 120 ₺ |
| Cost per complaint | 50 + 120 | 170 ₺ |
| Monthly cost | 150 × 170 | 25.500 ₺ |
This calculation covers direct cost only; it does not include the effect of a lost customer or a negative review. In reality cost varies by category (a resend is more expensive than a partial refund); working out a per-category average from your own compensation records gives a more accurate result. To see the effect of a customer buying again, see the post how to calculate and increase the repeat purchase rate.
Lesson 6: Which problem is fixed first?
In short: Start with the problem that is highest in count and cost and easiest to fix; the top two categories often make up half.
| Category | Count | Monthly cost (₺170) | Ease of fixing |
|---|---|---|---|
| Late delivery | 45 | 7.650 ₺ | Medium |
| Damaged product | 30 | 5.100 ₺ | Medium |
| Wrong/missing item | 24 | 4.080 ₺ | High |
| Not as described | 24 | 4.080 ₺ | High |
| Refund delay | 15 | 2.550 ₺ | Medium |
| No reply | 12 | 2.040 ₺ | High |
Wrong/missing items and mismatches with the description are fewer in number but easier to fix: a picking check and a product page correction give quick results. Late delivery and damage are bigger but depend on the carrier and the packaging. Planning the three together is balanced. To reduce picking errors, see how to measure the order fulfillment rate, and for the product page, how to measure product listing quality.
There is no single rule for prioritizing, but one test helps: for each candidate, write down the question "If I fix this problem, how many complaints and how many ₺ go away, and how many days and people does the fix need?" The problem with the best answer goes first. For problems that cost a lot but whose fix depends on the carrier, add a conversation with the carrier to the plan, and start the part within your control (packaging, picking time, notifications) without waiting.
Lesson 7: How are complaints reduced?
In short: Choose one fix for each priority category, set a target reduction rate and measure the result after 2–4 weeks.
| Category | Correction | Target reduction |
|---|---|---|
| Late delivery | Set a fixed handover-to-carrier time, notify late orders early | 40% (18 complaints) |
| Damaged product | Packaging standard for fragile products, damage photo record | 40% (12 complaints) |
| Wrong/missing item | Second check at packing, code scanning | 25% (6 complaints) |
- Monthly complaint cost (150 × ₺170)₺25,500
- Late delivery: 18 fewer complaints−₺3,060
- Damaged product: 12 fewer complaints−₺2,040
- Wrong/missing item: 6 fewer complaints−₺1,020
- Monthly cost after the fixes₺19,380
Prepared with sample values. Calculation: 25,500 − 3,060 − 2,040 − 1,020 = ₺19,380. The reduction rates are targets, not guarantees.
The three fixes remove 18 + 12 + 6 = 36 complaints; the number of complaints becomes 114 and the rate 114 ÷ 3,000 = 3.8%. The monthly saving is ₺6,120, or ₺73,440 a year. Notifying customers of order status in advance is the cheap way to reduce late delivery complaints; for details, see the post how to keep customers informed about their orders. For the damage and loss process, the post how to track lost and damaged shipments is useful.
Lesson 8: How do you monitor complaint management regularly?
In short: Track the complaint rate weekly and the category and root cause breakdown monthly; compare 2–4 weeks after every fix.
| Frequency | What happens |
|---|---|
| Every complaint | Write the category and root cause on the record |
| Every week | Calculate the complaint rate by channel and look for unusual increases |
| Every month | Pull the category and root cause breakdown, the cost and the fix results |
| Every quarter | Review the category list and the cost assumptions |
| Indicator | How it is calculated | Sample value |
|---|---|---|
| Complaint rate | Complaints ÷ Orders | %5 → %3,8 |
| Share of the top two categories | (45 + 30) ÷ 150 | %50 |
| Monthly complaint cost | Complaints × ₺170 | 25.500 → 19.380 ₺ |
| Resolution time | Minutes per complaint | 25 min |
- 5%starting complaint rate
- 50%share of the two largest categories
- ₺25,500monthly complaint cost
- ₺6,120monthly saving from targeted fixes
To add the results to the management summary, you can use the layout in the post how to prepare a weekly management report. To tie it into the daily operations check, see the post how to build an e-commerce daily operations checklist.
How do you write a reply to a complaint?
In short: The reply should be short, take responsibility and state the resolution step clearly; classification is done after the reply.
- Acknowledge first. Say in one sentence that you understand the problem; do not get defensive.
- Solution and timing. Write what you will do (resend, refund, exchange) and when it will happen.
- One touch. Do not ask the customer for the same information twice; ask for the order number and a photo in the first message.
- Record. After replying, record the category and root cause; otherwise the count stays incomplete.
- Follow-up. Ask about satisfaction a day after the solution; close the complaint once the outcome is confirmed.
A short response time also affects the number of complaints; you can use the methods in the post on customer message response time for ready-made reply templates and assigning owners. Decide in advance who can grant compensation up to what amount; that way you do not wait for approval on every complaint, and resolution time gets shorter.
What are the most common mistakes in complaint management?
- Not counting complaints. Without numbers, a recurring problem goes unnoticed.
- Opening too many categories. The more categories there are, the less reliable the count.
- Confusing category with root cause. What the complaint is and where it came from must be recorded separately.
- Not calculating the cost. Priority is then set by gut feeling.
- Trying to fix everything at once. Scattered work makes the result impossible to measure.
- Not measuring after the fix. You never know whether it worked.
- Treating complaints as only a customer service problem. The root cause is mostly the warehouse, shipping and the product page.
How does NetKasam make complaint analysis easier?
- Single-screen order management. You see the order behind a complaint, its channel and its status in one place (order management).
- Marketplace integration. Marketplace orders are collected on a single screen and invoiced automatically (marketplace integration).
- Shipping integration. You track shipment status together with the order record (shipping integration).
- Inventory management. Product- and variant-level inventory tracking makes it easier to check for wrong-item shipments (inventory management).
- Saved reports. You can save order and return reports and export them to Excel; you can combine your complaint table with this data (reports).
- 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 there are 150 complaints on 3,000 orders, what is the complaint rate?
- If late delivery has 45 complaints and damaged product has 30, what share of total complaints do these two make up?
- If resolution time per complaint is 25 min, the cost per minute is ₺2 and compensation is ₺120, what is the cost per complaint?
- What is the monthly cost of 150 complaints?
- If complaints fall by 36, what are the new number of complaints and the new rate?
Answer key:
- 150 ÷ 3.000 = %5.
- (45 + 30) ÷ 150 = %50.
- 25 × 2 + 120 = 170 ₺.
- 150 × 170 = 25.500 ₺.
- 150 − 36 = 114; 114 ÷ 3.000 = %3,8.
Frequently Asked Questions About Customer Complaints
How is the complaint rate calculated?
The number of complaints is divided by the number of orders in the same period. For 150 complaints on 3,000 orders, the rate is 5%.
Is a complaint the same as a customer message?
No. Most messages are questions or information requests; a complaint is a message saying that an expectation was not met.
What is the difference between a category and a root cause?
The category shows what the complaint is (such as late delivery); the root cause shows which process it came from (such as a delay in handing the parcel to the carrier). The fix is applied to the root cause.
How many categories are enough?
Usually 6–8 categories. More than that makes counting harder; if "other" grows, open a new category.
How do you find the cost of a complaint?
Resolution time cost and compensation cost are added together. In the example, 50 + 120 = ₺170, and for 150 complaints a month it is ₺25,500.
Which problem should I fix first?
Start with the one that is high in both count and cost and relatively easy to fix. The top two categories often make up half of all complaints.
What should the complaint rate be?
There is no single right rate; it varies by product and industry. What matters is that your own rate falls over time.
How do I know a fix worked?
Compare the 2–4 weeks before and after the fix in the same category. Use the rate rather than the count, because order volume changes.
Conclusion: Read a complaint as a process to fix, not a case to close
The most useful thing you can do today is collect last month's complaints into a single list and split them into six categories. Write a root cause for each complaint, calculate the cost per complaint and pick the two problems that cost the most. Make the fix, then pull the same table four weeks later and check that the rate has fallen.
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.