RMA process: getting the unit back with the fault attached

An RMA process — return merchandise authorization — is what stands between a customer saying "it is broken" and a unit arriving on your bench with no paperwork, no serial number and a note saying "does not work". The authorization is not bureaucracy for its own sake: it is the point at which you decide whether the return is accepted, what it is being returned for, and what happens when it lands. Skip that step and the shelf fills with units nobody can identify and nobody will pay for.

What the RMA process has to capture before a unit ships

• Serial or batch number, checked against your own records rather than taken on trust — this is what tells you whether the item is in warranty at all.
• The fault in the customer’s words, and separately the conditions under which it appears; "intermittent under load" and "dead on arrival" go to different queues.
• The original order or invoice reference, so the commercial terms are known before anyone opens the box.
• Whether the customer wants repair, replacement or credit — decided at authorization, not argued about after the unit arrives.
• Who is paying for the freight in each direction, which is the single most common source of the follow-up argument.
• The RMA number itself, quoted on the outside of the box, because an unlabelled parcel in goods-in is indistinguishable from a delivery.

What happens when it lands

1. Book it in against the RMA number the same day, so the clock the customer is watching matches the clock you are watching.
2. Inspect before diagnosing, and photograph anything that looks like transit or misuse damage — that conversation is impossible to have later without a picture.
3. Record the diagnosis against the serial, not against the customer, so a repeat failure of the same unit is visible.
4. Decide and communicate: repair, replace, credit, or reject as out of warranty, with the reason stated.
5. Close the case with the outcome and the date, and let the goods received note or the credit follow from it rather than being raised separately.

Refusing an unauthorised return is a policy decision, not an administrative one. If your team quietly accepts them anyway, the authorization step is theatre and you will keep receiving unidentifiable boxes. Decide which it is and say so on the returns policy page.

What the RMA data is worth once you have it

The individual case matters to one customer. The pattern matters to the business, and it is the only part that pays for the process.

• Failure rate by product and by batch, which turns a run of returns into a supplier conversation with evidence behind it.
• Time from authorization to resolution, which is the number customers actually judge you on.
• Proportion rejected as out of warranty, which usually says more about how the warranty was explained than about the customers.
• Repeat returns of the same serial, the clearest signal that a repair did not work.
• Faults that recur across batches, which should be raised as a non conformance report rather than fixed one unit at a time.

Where the case lives

Ettex Forms handles the front of this: a structured return request with the serial, the fault and the order reference as required fields, so an incomplete request cannot be submitted and the authorization number is issued against real data. Each submission becomes a dated record you can filter by product, batch or outcome. Ettex is not a repair-shop system and does not manage stock or issue shipping labels — what it gives you is the case trail from request to decision, which is the part that usually exists only in an inbox.