Returns & RMA: request to disposition and credit

Interviewer: Quick note before we start — I'm recording this, and I've got Sapeum running alongside, so it's mapping the process flow live on screen as you walk me through it. We're just capturing how returns actually work today. Sound good?

Manager: Yeah, works for me. Let's get into it.

Interviewer: So start at the top — what kicks off a return?

Manager: A return starts when a customer reaches out wanting to send something back. Most of that comes in by email or a phone call to our support line — "this unit's defective," "I ordered the wrong part." The first thing we capture is the basics: the order reference, which item and how many, and a reason category — defective, wrong item, buyer's remorse, damaged in transit.

Interviewer: And then you check if they qualify?

Manager: Right, the eligibility check. Are they inside the return window — that's thirty days — do they have a proof of purchase, and is the item even returnable, because some things, like opened consumables, are final sale and we can't take them back.

Interviewer: What happens if they don't qualify?

Manager: Then we decline it, with a templated response explaining why — outside the window, final-sale item, whatever it is. It's quick, but it's where we get the most pushback, so the wording has to be clear and not feel like a brush-off.

Interviewer: And if they do qualify?

Manager: Then I classify it by reason, because that sets the cost path. If it's a warranty defect, we cover the return freight. If it's a buyer's-remorse thing — they ordered the wrong part — there's a restocking fee and they pay the return shipping. Then I issue the RMA, the authorization number, and we send them a return label and instructions.

Interviewer: Okay, the unit's on its way back. Then what?

Manager: We track it inbound, and when it lands, receiving scans it against the RMA to confirm it's the unit we authorized — right model, right serial. If it doesn't match — wrong serial, or something we never authorized — it drops into an exception queue for someone to chase down. Assuming it matches, it goes to inspection, where someone physically looks at it: condition, is it complete, are the accessories all there.

Interviewer: And inspection decides where it goes next?

Manager: Right, that's the disposition decision, and honestly that's the heart of the whole thing. Based on condition, the unit goes one of a few ways. If it's basically new — resealable — back into sellable stock. Minor issues, it goes to refurb to be cleaned up and re-boxed. If it's a supplier defect, we send it back to the vendor as a return-to-vendor for credit. And if it's genuinely trashed, it gets scrapped or recycled.

Interviewer: Who makes that disposition call?

Manager: Right now, mostly me or one of my leads, item by item. We eyeball it and decide. And that's one of the spots that really kills us on time — we're making the same judgment call hundreds of times a week, and a lot of it is pretty rules-based. This SKU in this condition always goes to refurb. If we had something like Optoro doing the disposition decisioning, or even just smarter rules in the system, the routine ones would route themselves and we'd only touch the genuine edge cases.

Interviewer: Let me jump back to intake for a second — you said most returns come in by email and phone. Still true?

Manager: Yeah, so — let me actually correct that, because I was describing how it used to be. We launched a returns portal last year, so a good chunk come through self-serve now. It's closer to half portal, half email-and-phone at this point. I undersold the portal.

Interviewer: And the portal helps with that eligibility check?

Manager: It does, and that's the other big opportunity, honestly. When a return comes through the portal, it can pull the order and check the window and the eligibility automatically — the customer gets an instant yes or no. The phone and email ones, we still do that by hand, pull up the order, look up the purchase date. If everything moved through a portal that validated against the order data, that whole manual eligibility step basically disappears for most returns. A platform like ReverseLogix is built around exactly that.

Interviewer: Got it. So once it's dispositioned, how does it close out?

Manager: We handle the financial side — a credit or a refund, or a replacement if that's what they wanted, minus the restocking fee if one applies. Then we update inventory to reflect wherever the unit actually landed — back in stock, in refurb, shipped to the vendor, scrapped. And we close the RMA and log the return reason.

Interviewer: One thing — earlier you said every returned unit goes to inspection. Always?

Manager: Hmm — actually, let me walk that back a little. It's not every unit anymore. The receiving scan flags the obviously-damaged ones, and the sealed, clearly-unopened ones can skip the full inspection and go straight back to stock after the scan. So I overstated it — it's really the in-between condition units that get the full hands-on inspection.

Interviewer: Good distinction. And that return-reason data you log — does it go anywhere?

Manager: It feeds our quality and supplier reporting, in theory. But honestly that data's gold and we underuse it. If a particular vendor's defect returns spike, I'd love that to surface on its own and trigger a supplier conversation, instead of me catching it three months later in a spreadsheet.

Interviewer: Last thing — what do people get wrong about returns?

Manager: That it's just a cost to minimize. Everybody fixates on the front end — tightening the policy, the restocking fee. But the money's actually in the disposition. The same unit restocked as new versus scrapped is a massive swing in what you recover. Get the back-end disposition right and returns stop being pure cost and start clawing real value back. That's the part nobody pays attention to.

Interviewer: That's a great place to wrap. Thanks for walking me through it.

Manager: Anytime. Seeing it mapped out actually makes the manual spots pretty obvious.