Return Disposition Codes: Giving Every Returned Item a Next Step
Direct answer: A disposition code is the decision made at grading, recorded in one field, that tells the item where it goes next: back to stock, refurbish bench, return to vendor, liquidate, or scrap. The systems that work keep the list short, five to seven codes, tie each code to a physical location in the building, and review the code mix weekly, because a rising scrap or liquidate share is a product or policy problem reporting itself.
Every returns operation has a moment where an item sits in a tote with no decision attached to it. The tote fills, then a cage fills, and somewhere a manager authorizes a bulk clear out at pennies because nobody can say what is in there or why.
Disposition codes exist to kill that moment. Not with software. With a short list of decisions, made once per item, at the bench, by the person holding it.
Keep the code list short enough to memorize
Five core codes carry most operations: restock as new, restock as open box, refurbish, return to vendor, and exit, split into liquidate and scrap only if both routes genuinely exist in your building. Every code beyond that needs a reason, because each extra code slows the grader and blurs the reporting.
Grade condition separately from disposition. A grade says what the item is, A stock, B stock, damaged, incomplete. The disposition says where it goes. Conflating the two is how code lists balloon to twenty entries that nobody applies consistently, and inconsistent codes produce reports nobody can act on.
A code must point at a physical place
If restock as open box does not correspond to a specific cage, shelf zone, or pallet position, it is a wish, not a disposition. Graders route items in seconds, and they route them accurately when the code, the label color, and the location all say the same thing.
The same applies digitally. The code should trigger the next workflow automatically where the system allows it: refurbish creates the work order, return to vendor joins the vendor accumulation report, liquidate joins the lot building count. A code that a supervisor has to interpret later has just moved the undecided tote into a spreadsheet.
Read the code mix like an early warning
Weekly, the disposition mix is one of the cheapest diagnostics in the building. Scrap share climbing on one SKU is a product quality or packaging signal. Return to vendor share climbing is a supplier conversation with evidence attached. Open box share climbing in one category is often a sizing, description, or expectation problem on the product page.
Report it next to return rate, not instead of it. Return rate says how much comes back. Disposition mix says what the returns are worth when they land, which is the number that decides whether a category's returns are an annoyance or a margin leak.
Related reading
Related reading: The Return Exception Queue: Giving Weird Returns a Lane of Their Own, Return Data Cleanup: Fixing the Reason Codes Your Team Stopped Trusting, and Flagging Serial Returners Without Punishing Your Best Customers in Disguise.
Frequently asked questions
How many disposition codes should a returns operation have?
Five to seven for most operations: restock as new, restock as open box, refurbish, return to vendor, liquidate, and scrap, with condition graded separately. More codes than that usually means the list is encoding explanations instead of destinations, and graders apply long lists inconsistently.
Who should assign the disposition code?
The grader handling the item, at the bench, at the moment of grading. That person has the evidence in hand. Moving the decision to a supervisor or a later review recreates the undecided tote problem and doubles handling on every item.
What is the difference between liquidation and scrap?
Liquidation means the item leaves through a bulk resale channel for some recovery value. Scrap means it has no resale route and goes to recycling, donation where permitted, or disposal. If your operation has no liquidation channel, do not keep the code; it becomes a parking lot.
How often should disposition data be reviewed?
Weekly at the operations level, by SKU and category, watching for movement in scrap, refurbish, and vendor return shares. The review is cheap and the signals, failing products, bad packaging, supplier defects, mis-set customer expectations, arrive weeks earlier here than in margin reports.