Returns & RMA Workflows That Keep Stock Accurate
Short answer: A returns and RMA workflow needs to update stock quantities, record return reasons, trigger quality inspection where required, and generate a credit note — automatically, in the right sequence, without relying on staff to patch multiple systems manually.
Why Returns Break Inventory Records
Returns are a high-friction edge case in most inventory setups. The main stock flow — in from supplier, out to customer — is usually well-automated. Returns go in the opposite direction and involve conditions the standard flow doesn't: damaged goods, wrong items, partial returns, warranty replacements, and stock that can't go back to general inventory.
When returns aren't handled properly in the system, the typical result is:
- Stock physically back in the warehouse but not reflected in the system
- Credit notes raised without verifying the return was actually received
- Returned items mixed back into sellable stock when they should be in quarantine
- Return reasons not captured, so repeat failures aren't visible
For car parts trading and similar distribution businesses with high SKU counts and regular returns from garages or workshops, these gaps compound quickly.
The RMA Process: Step by Step
A Return Merchandise Authorisation (RMA) is the controlled process for managing a return before the goods come back.
| Stage | Action | System Event |
|---|---|---|
| Return request | Customer raises return | RMA number generated, original invoice referenced |
| Authorisation | Return approved (or rejected) | Approval recorded, customer notified |
| Goods receipt | Items received at warehouse | Stock received into quarantine or inspection location |
| Inspection | Quality check on returned items | Pass: return to stock. Fail: scrap or supplier claim |
| Resolution | Credit note or replacement issued | Credit note linked to original invoice and RMA |
| Closure | RMA marked complete | Return reason recorded for analysis |
Each step generates a record. The credit note only issues after goods are received and inspected — not when the customer calls to say they're sending something back.
Stock Location for Returns
Returned goods should go into a dedicated returns location or quarantine bin, not directly back to sellable stock. This matters because:
- Uninspected returns might be defective, damaged, or wrong items
- Batch and expiry integrity needs to be verified before stock is reshelved
- Some returns will become supplier claims rather than customer credits
The inventory warehouse system needs to support this by treating the returns location as a separate stock category — visible in inventory but not available-to-promise until cleared.
Partial Returns and Multi-Line Orders
An order for 10 line items where 2 items are returned is common. The workflow needs to handle partial returns at the line level: one RMA against an invoice, covering specific lines, in specific quantities. Credit note value should calculate from the returned lines only.
Systems that only support full-order returns create workarounds — split orders at the time of sale to make future partial returns cleaner — which adds complexity upstream to solve a downstream problem.
Return Reason Tracking
Return reasons are operational data, not just compliance records. If 15% of returns in a month are attributed to "wrong item sent," that's a picking accuracy problem. If "damaged in transit" spikes, that's a packaging or carrier problem. This information is only useful if it's captured consistently at the time of return processing — not reconstructed from WhatsApp conversations later.
FAQ
How do returns affect COGS and inventory valuation?
When a returned item is accepted back into stock, cost of goods sold reverses for the returned quantity. If the item is scrapped, the cost is absorbed as a loss. The credit note affects revenue. Getting all three right — stock, COGS, and revenue — requires the RMA to link back to the original sales transaction.
Can the same RMA system handle both customer returns and supplier returns?
Customer returns (RMA) and supplier returns (purchase return or debit memo) are different workflows with different accounting entries. They can be managed in the same system but should be separate processes — the stock flow, the document type, and the financial entries are all different.
What's the minimum an RMA system needs to do for a small trading company?
At minimum: generate an RMA reference number, receive the goods against that reference, record the return reason, and create a credit note against the original invoice. Even a simple workflow with these four steps is substantially better than managing returns through phone calls and manual adjustments.
Book a System Audit