Returns from RMA scan to restock — every line accounted for
Scan an RMA at the returns bench, inspect each line with condition and disposition, log unexpected items, split partials, attach photos, restock or dispose. The same screen operators run, and the same audit trail every action lands on.
Returns bench · DAL-01
Scanned 1 h ago · Lauren H.
Expected lines · 3
3 of 3 received
Cybership Hoodie · L · Black
SKU-4491 · 1 of 1
Cybership Beanie · One Size
SKU-2210 · 1 of 1
Cybership Tee · M · White
SKU-8810 · 1 of 1
Unexpected items · 1
Cybership Sticker Sheet (loose · no SKU)
Workflow
Staging
L-RET-04
Hospital
L-HOSP-01
Returns queue
The same Returns table operators run from `/teams/returns`
RMA, status, customer, items received vs expected, refund amount, and date — the same row your team already triages from. Status reflects the real workflow stages (Awaiting Label → Pending → Inspecting → Awaiting Resolution → Completed) used by ReturnStateProgress.
- Filter by status, type, warehouse
- Sort by oldest awaiting inspection
- Click a row to inspect
Return activity
RMA created from order #1027
Loop integration · 3 expected items
8 h ago
Label sent to customer
USPS Ground Advantage · trk 9405511298…
7 h ago
Package received at DAL-01
Scanned at returns bench · 3 of 3 items in box
1 h ago
Inspection started · split SKU-2210
Pilling on hem · graded USED_GOOD · 1 photo attached
20 min ago
Unexpected item logged
Sticker sheet w/o RMA reference · disposition RESTOCK
Just now
Why returns are different in Cybership
Inspection isn't an afterthought — it's the bench
The returns workflow runs on the same scan-driven UX as picking and packing, with first-class support for partial receives, splits, unexpected items, and per-line condition + disposition.
Scan a tracking, RMA, or order — bench loads
The returns bench identifies the inbound from any code. Operators don't decide which screen to open — the right inspection screen loads from the scan.
Per-line condition + disposition with photo evidence
Six conditions (NEW → DEFECTIVE) and eight dispositions (RESTOCK → DISPOSE → RETURN_TO_VENDOR). Photos attach to the line, not the return.
Unexpected items recorded as first-class rows
Items shipped without an RMA reference don't disappear. They're inspected and dispositioned alongside the expected lines.
Splits — a single line, multiple outcomes
Receive 3 of one SKU, restock 2 as new, send 1 to repair. Each split keeps its own condition, disposition, photos, and reason.
Staging + hospital locations on the record
Set the staging location for restockable items and the hospital location for items needing review — both written to the return.
Restock writes to live inventory
Restock dispositions feed straight into Inventory History at the staging location — no manual transfer step, no nightly reconcile.
Walk us through your returns flow
Bring your hardest RMA — partials, exchanges, RTV, hospital — and we'll inspect it on the bench end to end.
Schedule a DemoExplore more of our features
Packing Stations
Create stations, route work to them, and manage pack/returns workflows by station.
Reports & Analytics
Run reports on demand, schedule recurring runs, and drill into report details.
MerchantOS
Self-service 3PL client portal with visibility into orders, products, billing, and fulfillment.