Returns process map
A swimlane map of a return from the customer's request through authorisation, receipt, inspection and disposition to the refund or replacement, across the customer, customer service, the returns area, quality and finance. The disposition phase is where the branches multiply, and it is the reason this needs to be a map.
Opens a copy in the editor and saves it in this browser. No account, nothing sent anywhere.
What is in this map
20 steps across 5 swimlanes and 5 phases, with 4 decision points.
- Swimlanes (who does the work)
- Customer, Customer service, Warehouse / Returns, Quality and Finance
- Phases (left to right)
- Return request, Authorisation, Receipt and inspection, Disposition and Remedy and closure
Why map this process
A return is three processes wearing one name: a customer service interaction, a physical goods movement, and a financial transaction. Each is owned by a different team, each can complete without the others, and the customer's experience is determined by whichever finishes last. That is a textbook case for lanes: the map's job is to show that the refund cannot be issued until quality has looked at the item, and that the customer is waiting through all of it.
The disposition decision is what separates a working returns process from a warehouse full of unresolved boxes. Restock, repair, scrap, return to supplier: four outcomes with four different downstream paths and four different financial consequences. If your process has a single 'process the return' step, you have no way of knowing which of those four is happening, and no way of costing them.
Every step in the map
This is the spreadsheet behind the diagram. The numbers in “Goes to” are row numbers, which is exactly what the editor’s “Line to” column holds — so you can read the flow here and retype any part of it.
| # | Step | Shape | Swimlane | Phase | Goes to |
|---|---|---|---|---|---|
| 1 | Request a return | Start | Customer | Return request | 2 |
| 2 | Log return reason and order | Process | Customer service | Return request | 3 |
| 3 | Within **returns policy**? | Decision | Customer service | Return request | 5 (Yes), 4 (No) |
| 4 | Return declined with reason | Reject | Customer service | Return request | End |
| 5 | Issue *RMA* and return label | Process | Customer service | Authorisation | 6 |
| 6 | Pack and send goods back | Process | Customer | Authorisation | 7 |
| 7 | Book in and inspect goods | Process | Warehouse / Returns | Receipt and inspection | 8 |
| 8 | Condition assessment? | Decision | Warehouse / Returns | Receipt and inspection | 9 (Resaleable), 10 (Faulty), 15 (Not as described), 14 (No fault found) |
| 9 | Restock into sellable stock | Process | Warehouse / Returns | Disposition | 15 |
| 10 | Raise quality complaint | Exception | Quality | Disposition | 11 |
| 11 | Repair or scrap? | Decision | Quality | Disposition | 12 (Repair), 13 (Scrap) |
| 12 | Repair and return to stock | Process | Quality | Disposition | 15 |
| 13 | Scrap and record *write-off* | Process | Quality | Disposition | 15 |
| 14 | Return goods to customer | Process | Warehouse / Returns | Disposition | 19 |
| 15 | Which remedy applies? | Decision | Customer service | Remedy and closure | 16 (Refund), 17 (Replacement), 18 (Credit note) |
| 16 | Refund to original payment method | Compensation | Finance | Remedy and closure | 19 |
| 17 | Despatch replacement item | Process | Warehouse / Returns | Remedy and closure | 19 |
| 18 | Issue **credit note** to account | Document | Finance | Remedy and closure | 19 |
| 19 | Notify customer of outcome | Customer service | Remedy and closure | 20 | |
| 20 | Return closed | Success | Customer | Remedy and closure | End |
The decision points
Every branch in the map, with the label on each outgoing line. These are the questions the process has to be able to answer.
-
3. Within **returns policy**?
Owned by Customer service · Return request
- Yes → step 5
- No → step 4
-
8. Condition assessment?
Owned by Warehouse / Returns · Receipt and inspection
- Resaleable → step 9
- Faulty → step 10
- Not as described → step 15
- No fault found → step 14
-
11. Repair or scrap?
Owned by Quality · Disposition
- Repair → step 12
- Scrap → step 13
-
15. Which remedy applies?
Owned by Customer service · Remedy and closure
- Refund → step 16
- Replacement → step 17
- Credit note → step 18
Notes on specific steps
These notes travel with the map. In the editor they live in the Notes column and appear when you open a box.
- 2. Log return reason and order
- Capture the order number, item, quantity and a reason code from a fixed list. Free-text reasons cannot be counted later, and reason data is what tells you whether returns are a product problem or a listing problem.
- 7. Book in and inspect goods
- Book the parcel in against its RMA number on arrival and photograph the condition before anyone opens or tests it. Unbooked returns are the main reason customers chase a refund that has already arrived in the building.
- 8. Condition assessment?
- Write down what each grade means and who is allowed to apply it. **No fault found** needs a defined test rather than an opinion, because it is the grade that sends goods back to an unhappy customer. Not as described is a seller error, so raise a correction to the listing or specification as well as settling the remedy.
- 15. Which remedy applies?
- Decide who owns this call and up to what value. Consumer refunds normally go back to the original payment method; credit notes suit trade accounts with an open ledger, and should not be offered where a refund is legally owed.
Making it yours
Authorise before you receive. The map is drawn that way deliberately (the RMA decision sits before the goods arrive) and it is the single most useful thing to keep when you adapt it, because an unauthorised return is a box on the dock with no owner. Then expand the disposition phase to match your actual outcomes; each one is a row plus a branch label naming the condition that leads to it.
What to watch out for
- Refund and replacement are not the same path and should not share a box. A replacement re-enters fulfilment; a refund goes to finance. Merging them means the map cannot show that a replacement has a second delivery to fail.
- Returns received without an RMA happen constantly. Give them a route (usually a hold step and a lookup) rather than leaving them off the map, or the informal handling becomes the actual process.
- The quality lane is not optional if you ever restock returned goods. Restocking without inspection is how a returned faulty item gets shipped to the next customer, and the map should make the inspection step impossible to skip by drawing it as the only route to restock.
Frequently asked questions
What does RMA mean on this map?
Return merchandise authorisation: the reference issued when a return is approved, before the goods are sent back. It matters structurally: it is what lets the receiving step match an arriving box to a known, approved return, which is the difference between a returns area and a pile.
How do I handle returns that are out of warranty or outside the returns window?
As a branch on the authorisation decision, ending either in a refusal or in a goodwill path with its own approval step. Companies almost always make exceptions; mapping the exception with an approver attached is far better than leaving it to whoever answers the phone.
Should supplier returns use this map too?
The shape is similar but the counterparty flips: you are the one requesting authorisation, and the financial outcome is a credit note rather than a refund. It is close enough to adapt from and different enough that it should end up as its own map rather than a branch on this one.
Open the map and start editing
The editor loads this chart with the spreadsheet underneath it. Change a cell and the diagram redraws — no drawing, no signup.