Customer Return & RMA Tracker

What this tool does

CM8-294 is a working returns register. One row is one return authorisation: what is coming back, from whom, how much, why the customer says so, when it was asked for and when it arrived, what you found when you inspected it, where it ended up, who caused it, and what it cost in credit. From that it shows how long returns stay open, how many units come back each month, which customers cost the most in credit notes, and — the number most people find uncomfortable — how many returned items had nothing wrong with them.

Everything runs inside this single file. No account, no upload, no network request of any kind, so customer names, credit values and defect findings never leave this computer.

Returns are not complaints

They overlap, and they still need separate registers, because they are different kinds of object. A complaint is an opinion: a customer telling you something was wrong. It needs acknowledging, investigating and answering, and the Customer Complaint Tracker is built for that loop. A return is physical material — authorised before it moves, transported, received, counted, inspected, dispositioned, put back into or out of stock, and settled with a credit note or a replacement. None of that is opinion; all of it has a location, a quantity and a date.

Most returns generate a complaint and most quality complaints generate a return, so cross-reference them in the notes — but keep the registers apart. A complaint closed with an apology is finished; a return is not finished until the material has gone somewhere and the money is settled.

The RMA discipline

One rule matters more than every other here: authorise the return before it ships back.

Without an RMA number issued in advance you receive mystery boxes. Something arrives at goods-in with no paperwork, nobody knows which customer it came from or what was agreed, it sits in a corner for three weeks, and by then the customer has been chasing a credit for a fortnight. Every one of those is a process failure that started before the goods left the customer.

Authorisation is also the chance to make good decisions cheaply: do the goods need to come back at all, who pays the freight, which site receives them. The authorisation target on the Settings tab measures the wait between asking and getting an answer — two working days is a common standard, and returns sitting unauthorised past it are flagged. Rejecting a return is a legitimate outcome too: record it with the rejected status and a note, so the decision exists in writing rather than in memory.

Inspect before you decide

The tool will not let you set a disposition on a return still at requested or authorised. A disposition is a conclusion, and a conclusion drawn before anyone looked at the goods is a guess wearing a status. Receive them, look at them, write what you found, then decide.

Write the finding so someone else could re-verify it: what was examined, how many, what was measured. "Twenty-two plates of sixty out of position by 1.5 to 2.1 mm" survives a disagreement with a customer. "Some plates were out" does not. That field is also what makes an attributed fault defensible — particularly when the answer is that the customer caused it.

The no-fault-found rate

This is the most useful number in the register and it usually surprises people. Of the returns you actually inspected, what share had nothing wrong with them? In the sample register two of the four returns reported as defective were conforming — one corroded from being stored outdoors under a tarpaulin, the other a belt tracking off because the customer's drive roller was out of square.

A rate of a fifth to a third is common, and it means something specific: a meaningful part of your returns cost is not a quality problem at all. It is an instruction, expectation or fault-finding problem at the customer's end, and no amount of process improvement in your factory will reduce it. Better fitting instructions, clearer storage guidance, or a call from a technical person before the RMA is issued will. The rate covers inspected returns only, so it does not swing as goods arrive.

Choosing a disposition

Disposition is a technical decision about the material, and there is a natural cost order. Work down it:

• Use as is — cheapest. The goods conform, or the deviation does not matter for their use. Back into stock, or straight back out.
• Rework and return to stock — recoverable at the cost of the labour. Be honest about that labour: rework costing more than a new part is scrap with extra steps.
• Return to supplier — the material came in faulty. Needs evidence to make the claim stick, which is why the strip-down report matters.
• Return to customer — no fault found — nothing is wrong. Send it back with the evidence.
• Replace — a new item goes out; the returned one still needs its own disposition.
• Scrap — the most expensive outcome and, once chosen, unarguable.

Attributing fault honestly

Every inspected return should end with an attribution: us, the supplier, the carrier, the customer, or genuinely undetermined. Undetermined is excluded from both sides of the our share calculation — an honest holding answer, not a hiding place, and a register where half the returns stay permanently undetermined is not being inspected properly.

Attributing to ourselves is the one that gets avoided, and the one that pays. A register attributing nothing to its own process describes a company that has never made a mistake, which nobody believes. Equally, attributing a genuine storage failure to yourself to keep the peace buries a real finding about your instructions and pays for the privilege.

Credit and replacement are commercial decisions

Keep the technical disposition and the commercial settlement separate. What happens to the material is a matter of fact; whether the customer gets a credit note, a replacement, both or neither is a decision about the relationship and the contract.

They come apart in both directions: a wrong item shipped might be replaced with no credit at all, and a conforming batch credited anyway because the account is worth keeping. The tool asks for a note whenever a credit is raised against a return attributed to the customer, because that is exactly where the commercial reasoning needs to exist in writing.

Days open

Days open runs from the date the customer asked to the date the return was closed — or to today while it is still open. It is measured from the request, not from receipt, because the customer's experience starts the moment they ask: the days in transit, and the days the box sat unopened in goods-in, are part of that wait whether or not they feel like your responsibility. Set a closure target on the Settings tab and returns over it are flagged. Transit days are recorded separately so you can see which part of the delay is yours.

Feeding corrective action

A confirmed defect return is evidence: dated, quantified, with physical material to examine. That is worth more than most internal findings, and it should not stop at a credit note. Raise the recurring ones into your corrective action system — the CAPA Tracker to carry the action to verified closure, and the 8D Report tool where a customer expects a structured problem-solving response. Put the reference in the notes so the records point at each other.

The charts choose what to escalate. The reason donut shows what customers say is wrong; the fault and disposition chart shows what was actually wrong. A reason that keeps appearing and keeps being attributed to your process is a corrective action waiting to be written.

The formulas

Inspected returns are those with a disposition other than "pending"; attributed returns exclude "undetermined", so neither rate is diluted by returns nobody has finished looking at. Credit values are summed only where you entered them — a blank credit box contributes nothing rather than counting as zero, which matters because most returns are settled without one. The monthly chart counts returns on the date received, so goods still in transit do not yet appear.

The spreadsheet workflow

Returns often start life on a despatch or goods-in sheet, and retyping them is wasted effort.

• Spreadsheet template saves a CSV whose headings are exactly this tool's column names, with a guidance row explaining what each expects — the date format and the accepted values for the reason, disposition, fault and status lists.
• Fill it in, one row per RMA, then delete the guidance row and save as CSV.
• Import spreadsheet reads it back. Columns match by heading, so order does not matter and extra columns are ignored. Rows failing validation — a closed return with no closing date — are skipped and reported by row number.

The file is read in your browser: nothing is uploaded, and importing adds to what is already here.

FAQ

One RMA covering several part numbers — one row or many? One row per part number, sharing the RMA number. Quantities, dispositions and fault attributions differ by part, and one row would force you to average them into something meaningless.

Should I log returns that were rejected? Yes — that is the record of the decision, and the rejected status keeps them out of the open list without deleting them. A register holding only the returns you accepted cannot say how many you turned down.

Gross or net of a supplier or carrier recovery? Gross — what the customer received. What you recovered is a separate transaction; netting them hides both.

What counts as closed? The material has a final home and the money is settled. A return whose parts are scrapped but whose credit note has not been raised is not closed.

Saving your work

Returns, settings and the report header are written to this browser's local storage as you type, and the toolbar shows the time of the last save. That storage belongs to one browser on one computer: another browser, a private window or a clean-up tool that clears site data will not have it.

Treat Export .json as the real save — one file containing everything, which Import .json restores anywhere. Export CSV gives you the register for spreadsheet work. Reset asks twice, then erases everything stored. There is no undo. The register names customers, credit values and defects — treat exports as confidential.

Accuracy & disclaimer

The arithmetic here is simple and shown in full. The limit is what reaches the register at all: it measures returns that were authorised and recorded. Material handed back at a site visit, carried away on a van, swapped informally or credited without paperwork never appears — and in most organisations that is where the real number hides. If your recorded returns look low, check the paperwork discipline before the process.

Dispositions, fault attributions and credit values are your own judgements, and warranty terms, return rights, statutory guarantees and record-retention expectations differ by country, contract and industry. This is an internal record-keeping and analysis aid, not an accounting record, not a warranty determination, and not legal advice.