Returns Receiving & Disposition: Stop Letting Returned Goods Rot on the Dock

The problem this kills

Returns are where warehouses quietly bleed money. A box comes back to the dock, somebody sets it on a pallet "to deal with later," and weeks go by. Was there an RMA for it? Is it sellable, or is the box crushed? Does it go back on the shelf, get refurbished, dumped into B-stock, scrapped, or shipped back to the vendor for credit? Nobody's sure, so it sits. Meanwhile your on-hand counts are wrong, customers wait on credits, and good inventory ages into junk.

The usual fixes are a clipboard, a shared spreadsheet, and a lot of "ask Maria, she knows." That doesn't scale, it has no photos when a dispute lands, and the worst-case is the one that hurts most: a damaged unit gets restocked as A-grade and ships straight back out to the next customer. You don't need a six-figure WMS module to fix this, and you don't need to be a developer.

What you'll build

A simple internal web tool for the returns dock. A receiving associate opens it, enters (or scans) the RMA number on an arriving return, and the tool matches it to the open RMA — pulling the expected item, quantity, and customer — or flags it loudly if there's no matching RMA so it doesn't slip through. The associate grades the condition against your own rules and snaps a few photos (stored safely, timestamped). The tool then proposes a disposition — restock as A-grade, send to refurb, move to B-stock, scrap, or return-to-vendor — based on the grade. Your returns lead reviews each item and approves the disposition. Only on approval does the tool record the move and produce a clean inventory-move CSV (restock / scrap / RTV) you can hand to your system of record, with the rule that only A-grade returns go back to sellable on-hand.

What's inside the Implementation Plan

The downloadable plan is a step-by-step file you paste into an AI coding agent. It opens by interviewing you about your business — how returns reach your dock today, where your open RMAs live and exactly how they're named, your real SKU and warehouse-location conventions, your condition-grading scale, which disposition each grade maps to, your typical and peak return volumes, and the messy edge cases (no-RMA returns, partial returns, wrong-item-back, missing accessories) — and then it tailors the data model, the grading logic, and every later step to your answers. This is not a generic template; the agent reflects a short spec back to you and waits for your thumbs-up before it builds anything. From there it walks the agent through RMA import, the receive-and-match screen, condition grading with photo capture, the disposition proposal, the lead's review-and-approve gate, and the inventory-move CSV export — each step with a ready-to-copy prompt. There's also a fallback so you can build and run the whole thing today with no integration to your WMS or ERP.

The governance it includes (this is the point)

This touches your sellable inventory, so it ships with the controls a real operation needs: login so only your team can use it, row-level security so you only ever see your own organization's returns, a complete audit trail of who received, graded, and approved each item and when, a hard human-approval gate so nothing posts to sellable stock or records a scrap/RTV until your returns lead signs off, and duplicate guards keyed on RMA plus receipt so the same return can't be processed twice. Returns with no matching RMA are flagged and held instead of silently restocked, and only A-grade ever flows back to sellable on-hand.

Who it's for

Returns receiving associates, inventory control specialists, and QC leads who own the returns dock and are tired of pallets of limbo. If you can describe how your warehouse decides what to do with a returned item, you can build this.

You've got this — start with the plan, paste the first prompt, answer the interview, and you'll see your first return matched, graded, and routed the same afternoon.