How to handle refunds, replacements, and repeat defects
This guide helps a business handle a customer complaint from first message to confirmed closure, including the hard cases: refunds, replacements and defects that keep coming back. The example is a small-appliance retailer in Jaipur that sells mixers, irons and water heaters through a shop and online.
Why this matters
A refund given without a record can be claimed twice. A replacement sent without finding the cause means the next unit fails the same way. And a case marked closed that the customer still considers open becomes a bad review or a chargeback.
A clear route from complaint to closure keeps the customer informed, limits the money you lose and shows you which product or supplier is causing repeat problems. It also protects your staff, because they know what they may offer without asking.
Before you start
- A complaint register with case number, date, customer, product, batch or serial number and invoice reference.
- A written remedy policy: what is eligible for repair, replacement or refund, within which period and who can approve each.
- A service-level target for each severity, for example first reply within one working day and fix within seven days.
- A way to receive photographs or short videos from the customer.
- Named people for service, quality and operations approval, and a supplier contact for warranty claims.
Step by step
- Capture the complaint and the evidence. The service agent opens a case and records the invoice number, product serial, date of purchase, what went wrong and what the customer wants. They ask for photographs or a short video of the fault and attach them to the case.
- Triage and assign. The quality lead rates the case by severity: safety risk, product unusable, minor fault or service issue. They check the register for earlier cases on the same product or batch and assign a person with a target date.
- Give the authorised remedy. The operations manager approves repair, replacement or refund within the written policy. The remedy, its value and the approver are written on the case; a refund references the original payment and is made to the same mode of payment, never to a different account on request.
- Collect the faulty item and check it. The service agent takes back the faulty unit, tags it with the case number and notes its condition. Returned items do not go back on the shelf until the quality lead has inspected them.
- Investigate the cause. For any repeat defect, meaning the same fault on the same product or batch more than once, the service agent and quality lead trace the cause: a supplier batch, a storage problem, poor packing or customer misuse. They record a corrective action, such as holding a batch, returning stock to the supplier or changing the packing method.
- Confirm with the customer. The quality lead contacts the customer, asks whether the problem is solved and records the answer with the date. Only a customer's confirmation, or three documented attempts to reach them, allows the case to close.
- Review patterns weekly. The quality lead looks at open cases by age and at repeat products, then shares a short list with the operations manager.
Who does what
| Role | What they do | Record they own |
|---|---|---|
| Service agent | Opens the case, gathers evidence, collects the unit, investigates | Complaint case |
| Quality lead | Rates severity, inspects returns, confirms closure | Closure evidence |
| Operations manager | Approves remedy and spending, owns supplier claims | Authorised remedy |
Common mistakes
- Refunding on a phone call with no invoice or serial check, which invites duplicate claims.
- Replacing the product without recording the cause, so the defect keeps returning from the same batch.
- Closing the case as soon as the replacement ships, before the customer confirms it works.
- Letting staff offer refunds above their limit "to calm things down", with no approval trail.
- Putting returned units back into sale stock without inspection.
How to tell it is working
- Age of open cases. For every open case, count the days since it was opened. Look at the oldest five and at how many exceed your service target; both should shrink month by month.
- Repeat complaints. Count products or batches with more than one complaint for the same fault in the last 90 days, and divide by total products sold in the period. A rising figure points to a supplier or process issue.
- Unconfirmed closures. Count closed cases that have no customer confirmation on file. Divide by all cases closed in the month; aim for as close to zero as you can.
Questions people ask
Who owns complaint to resolution?
The quality lead owns the route from complaint to closure. The service agent handles customers day to day and the operations manager approves spending, but one person must answer for the case staying alive until it is truly resolved.
What is the minimum record for complaint to resolution?
The case number, customer and invoice, product serial, the fault with a photograph, the remedy and its approver, the cause for repeat defects and the customer's closing confirmation.
When should a case stop?
When the customer confirms the problem is solved, or when you have made the agreed number of documented attempts to reach them. A case also stops if the claim is declined under policy and the reason has been explained in writing.
Can a spreadsheet support this stream?
Yes, if every case gets a row with a number, a status, a due date and a link to the photographs. It becomes weak when several people edit it with no owner, so one person should check ageing daily.
What should the owner review?
Look at the oldest open cases, the products with repeat faults, total refund and replacement value for the month and any approvals made outside policy.