Most manufacturers did not design an RMA process that lives in Outlook and Excel. They grew into one.
A partner emails a photo. Someone pastes a row into a shared sheet. Warehouse asks which case the carton belongs to. Approvals sit in a personal mailbox while the owner is on leave. Everyone is busy. Nobody has a complete return.
This page is for aftersales, warranty and warehouse leads who still run Return Merchandise Authorisation (RMA) through shared inboxes and spreadsheets. It is a problem page, not a named competitor comparison. For the definition of RMA itself, start with what an RMA is.
Why email and spreadsheets still win (until they do not)
Email feels flexible. Anyone can attach anything. Spreadsheets feel controllable. One row per case, a colour for status.
Both fail for the same reason: intake is optional.
Nothing forces a serial before you authorise a ship-back. Nothing blocks a blurry photo. Nothing checks that the unit already has an open return. Proof of purchase lives in a different thread. When volume rises, those gaps become the job.
Typical failure modes:
- Missing or mistyped serials
- Weak evidence (one dark image, no fault code, no “when did it start”)
- No proof of purchase, chased after the unit is already moving
- Duplicate cases (two emails, two spreadsheet rows, one carton)
- Status vacuum (partners chase ops because they cannot see inspection or approval)
- Approvals stranded in personal inboxes
DE / FR / NL teams use different words (RMA, Retoure, retour, Rücksendegenehmigung, autorisation de retour). The inbox problem is the same.
What breaks first in real ops
Incomplete cases become warehouse problems
If the portal (or the form) does not require serial, model, reason and usable attachments, goods-in inherits the mess. Teams quarantine cartons while someone digs through email. That is not a warehouse skill issue. It is an intake design issue.
Approvals become tribal knowledge
Chargeable repair, replacement outside cover, or goodwill needs a named approver and a recorded decision. In email, “manager said yes” is a forward with no cost estimate and no case link. When finance or a partner asks why, the trail is gone.
Status lives nowhere partners can see
Dealers and distributors will call if the only status channel is “reply all”. Ops then spends the day narrating cases instead of closing them.
Nobody owns the system of record
The spreadsheet, the inbox, and the ERP credit note each hold a partial truth. When they disagree, the loudest thread wins. That is the opposite of an auditable return.
Email / spreadsheet vs a structured RMA workflow
| Shared inbox + spreadsheet | Structured RMA workflow | |
|---|---|---|
| Serial | Optional, often wrong | Required at submit (or batch policy stated) |
| Evidence | Scattered attachments | On the case |
| Duplicate open return | Easy to miss | Flagged before authorisation |
| RMA number | Issued later by ops | Issued on a clean submit |
| Status | “Any update?” emails | Visible to the submitter |
| Approvals | Personal mailboxes | Named owner on the case |
| Ops queue | Personal inboxes | One shared case list |
| Audit trail | File history / hope | Who decided what, when |
The warehouse still inspects. Approvers still approve. Structure does not remove judgement. It stops incomplete cases becoming goods-in emergencies.
What good looks like
A workable RMA setup for manufacturers and distributors has seven traits:
- Named submitters under customer or partner accounts (not a shared password in a dealer workshop).
- Structured intake: serial (or batch), purchase reference, fault description, usable attachments.
- Authorisation before ship-back: RMA reference and return address only after required fields pass.
- Open-return checks: block or warn when the same serial already has an open case.
- Shared status: submitted, received, in inspection, awaiting approval, resolved.
- One ops queue: all cases land where ownership and next action are visible.
- Reviewable close: outcome, cost, approver and evidence stay on the case.
That is the same spine described in RMA meaning: authorise, receive, inspect, decide, close. Email is a notification channel. It is not the system of record.
Serial discipline at intake and goods-in deserves its own focus: see why serial numbers matter on warranty claims and RMAs.
Soft product note (TrackQUAL)
If you want that shape without building a custom dealer site, TrackQUAL runs returns through customer portals and partner workspaces: serials and documents at intake, then shared visibility through inspection, approval and warehouse on one auditable case. It is built for manufacturers and distributors, not as a consumer “print a returns label” tool.
Starter includes the core returns workflow and approvals if you are ready to leave optional serials in the inbox. See pricing and the product overview.
When you have outgrown email and spreadsheets
You are past the workaround when any of these are true:
- Partners submit on spreadsheets because that is still easier than your process
- Units arrive with no matching serial or RMA
- Chargeable quotes sit in an inbox while the unit sits on hold
- Two teams disagree what was approved, and the only record is a thread
- You cannot separate repair, replace and credit without opening the row
Those are workflow gaps. Adding more columns to the sheet rarely fixes them.
FAQ
Can we keep email for notifications?
Yes. Use email to tell people a case needs attention. Do not use email as the place where serials, approvals and status live.
Is a shared spreadsheet ever enough?
For very low volume and one editor, sometimes. It fails as soon as multiple partners and multiple editors share the file, or when goods-in needs a case that is not on the sheet.
Do we need to replace our ERP?
No. The ERP should still book credits and stock moves. RMA intake, evidence, inspection and approval belong on the case, then post back. (This page is about inbox and spreadsheet intake, not a full ERP comparison.)
What is the minimum to require at intake?
Account, product, serial (or stated batch rule), purchase reference, fault description, and usable attachments. If the serial is blank on a serialised product, do not issue an RMA.
How do partners see progress without chasing?
Give them portal access to the stages that matter under the same RMA reference they used to ship.
Is this the same as a consumer returns portal?
No. B2B RMA needs partner accounts, serialised intake, eligibility checks and operational status. Consumer DTC portals optimise for order lookup, labels and refunds.
Related
What an RMA is · The importance of auditable returns · Serial numbers on warranty claims · Dealer and distributor RMA networks · Pricing · TrackQUAL overview