Returns management process flowchart (reverse logistics)

What the returns management process flowchart (reverse logistics) process is

Returns management is reverse logistics run as an operational function. It begins on the dock, when goods that were already sold come back, and it ends when the stock record, the ledger and the customer account all agree on what happened to them. The unit of work is not one unhappy customer; it is a stream of returned goods that has to be received, graded, dispositioned and accounted for, day after day, without contaminating sellable stock or losing recoverable value.

This is not the customer-facing returns journey. The request, the policy check, the authorisation issued to the customer, the choice between refund and replacement and the message telling the customer what happened all sit in the returns process, which hands over to this one at the goods-in door. This is also not inventory management, which covers routine receipt, put-away and counting of stock that was never sold, and it is not the quality investigation itself: this process raises the returns-reason evidence that a quality complaint or corrective action then works from.

Two decisions carry the chart. The first is whether the goods can be matched to a returns authorisation, because an unmatched parcel has no owner, no reason code and no route to a credit, and it will sit in the returns area until someone gives it one. The second is the disposition: restock, refurbish, return to the supplier or scrap. That single choice sets the value recovered, the stock movement, the ledger posting and whether a supplier claim is ever raised, and in most operations it is the step with the least written-down rule behind it.

What this flowchart covers

In this template

• Five lanes (Returns desk, Warehouse, Quality, Finance and Supplier) across five phases: receipt, inspection, disposition, adjustment and credit, and analysis. There is deliberately no customer lane; the customer conversation belongs to the returns process that precedes this one
• A "Matched to a returns authorisation?" decision at goods-in, with unmatched consignments quarantined and put through a "Sender identified?" check that either raises an authorisation retrospectively or ends in disposal of unclaimed goods
• Inspection and testing in the Quality lane, followed by a grading step that records condition and a separate return reason code: the grade drives the disposition, the reason code drives the analysis at the end
• A four-way "Which disposition applies?" decision: return to sellable stock, refurbish and re-grade before restocking, raise a supplier claim, or scrap under controlled disposal
• The supplier route (a claim raised for defective stock, the supplier authorising the return and issuing credit) rejoining the main line at the stock adjustment, so recovered value lands in the same records as everything else
• Scrap passing through a disposal evidence record, then a stock adjustment, a ledger cost adjustment, a "Credit due to the customer?" decision and a credit note, with every route passing through a return-reasons review with the product team before the record is closed

When to use this template

• You handle returns at volume and need reverse logistics documented as an operational function, with named owners for grading, disposition and write-off, rather than as a customer-service script
• Returned goods sit in the returns area for weeks because nobody owns the disposition decision, or because parcels arrive that cannot be matched to an authorisation
• Recoverable value is leaking: defective stock is scrapped or quietly restocked without a supplier claim ever being raised, so the cost stays with you
• Stock figures and the ledger drift apart after returns, because the physical disposition and the record are updated by different people at different times
• You are configuring a returns module in a WMS or ERP and need the returns desk, warehouse, quality and finance split agreed before anything is built

How it works

1. Confirm where this process starts

   Fix the handover. The trigger here is goods arriving, not a customer asking to return something. If your customer-facing returns process already issues an authorisation, this chart begins the moment that consignment reaches goods-in. Write the handover onto the first step so the two processes are not maintained as one sprawling diagram.

2. Define your condition grades and reason codes

   Keep them as two separate lists. Grades describe the state of the goods and decide the disposition — for example as-new, opened, damaged, faulty. Reason codes describe why the item came back — wrong size, arrived damaged, not as described, changed mind, fault in use. Collapsing them into one field is what makes returns data useless for analysis later.

3. Set the disposition rules

   Write a rule behind each branch of the disposition decision rather than leaving it to judgement: the condition grades that permit a restock, the recovery value that justifies refurbishment against the labour it costs, the supplier agreements that allow goods to be sent back, and who may authorise a scrap. Note against the scrap branch what evidence the disposal route requires.

4. Decide the unauthorised returns rule

   Unmatched parcels need a written answer, not an improvised one: where they are held, how long, who attempts to identify the sender, who may raise the authorisation retrospectively, and who authorises disposal once the holding period expires. Keep unmatched goods out of sellable locations for the whole of that period.

5. Name the adjustment and credit authority

   Record who posts the stock adjustment, who approves a write-off and above what value it needs a second signature, and who may issue a credit note. Decide whether returned stock re-enters at full value or at a reduced one, because that choice determines whether the return shows up as a stock movement or as a cost.

6. Put the analysis on a cycle

   The last step is only useful if it is scheduled. Set who reviews reason codes, how often, and where the output goes: listing and instruction problems to the product team, repeating batch faults to quality, supplier-caused defects into the supplier review. Then walk the chart against a fortnight of real returns and correct the steps people actually skip.

Frequently asked questions

How is returns management different from the returns process?

They are two halves of the same story with different scopes. The returns process is customer-facing and transaction-shaped: a request, a policy check, an authorisation issued, and a refund, replacement or credit note, ending when the customer is told what happened. Returns management is the operational function behind it: what happens to the goods themselves once they arrive, how they are graded and dispositioned, how value is recovered from suppliers, and how stock and financial records are corrected. If you are writing a returns policy, start with the returns process. If returned stock is piling up, value is leaking or the records do not reconcile, this is the chart you need.

What are the disposition options for returned goods?

This chart uses four: return to sellable stock, refurbish and re-grade before restocking, return to the supplier under a claim, and scrap. The choice should be driven by a written rule rather than judgement, weighing the recoverable value against the handling and refurbishment cost, what the supplier agreement actually allows you to send back, and any regulatory constraint on reselling the item at all. Some goods cannot be restocked whatever their condition — perishables, and items where safety or hygiene rules out resale — so those categories are worth listing explicitly against the decision.

How should unauthorised returns be handled?

Quarantine them first, physically separate from sellable stock, so an unidentified item cannot be picked and shipped to someone else. Then try to identify the sender from the packaging, the item serial or batch number, or a recent despatch to that address. Identified senders get an authorisation raised retrospectively and the goods rejoin the normal route with a reference attached. For the remainder, agree a holding period and a disposal authority in advance. The failure mode here is not disposal, it is drift: goods held indefinitely because no one is allowed to decide.

When should a supplier claim be raised?

When the fault sits with the goods as supplied rather than with the customer or with your handling — a manufacturing defect, a short or wrong delivery, or a batch failing on arrival. Raise it while the evidence still exists: the batch or serial number, the inspection result and photographs are all captured at grading, which is why the claim step in this chart sits immediately after it. Check the claim window and the return conditions in your supplier agreement, since many limit how long after delivery a defect can be claimed and require the goods to be returned rather than destroyed.

How do returns show up in inventory and financial records?

As two postings, in this order: a stock adjustment for the physical disposition, then a cost adjustment in the ledger for the value effect — a restock at full or reduced value, a refurbishment cost, a write-off for scrap, or a recovery when a supplier credit arrives. A credit note to the customer is a separate decision, because not every return earns one. Keep the evidence attached to each: the inspection and grading record, and for scrapped goods the disposal documentation your route requires. This supports the general expectation in quality standards such as ISO 9001 that nonconforming outputs are controlled and their disposition recorded, though using a template does not by itself make a process compliant.