Latest / The Operations Podcast with Fexingo: Process, People, and Profit in Modern Business / How One Warehouse Cut Returns Processing by Half
Transcript
- Lucas: So there's this stat that's been rattling around my head for a while now. During the peak holiday season last year, one large e-commerce fulfillment center saw its returns volume spike by nearly 60 percent week-over-week. And the backlog got so bad that some items sat in the returns area for over two weeks before anyone even touched them. Luna: Ouch. And that's not just a storage problem, right? That's money sitting still, plus customers waiting on refunds. Lucas: Exactly. And the worst part is, the typical response to that is to throw more bodies at it. Hire seasonal staff, mandate overtime, push people to work faster. But this particular operation took a different route. They decided to redesign the entire returns process from the ground up. And they managed to cut their processing time by half. Luna: Fifty percent is huge. What was the first thing they looked at? Lucas: So the first thing they did was separate triage from processing. Before, every returned item went through the same sequence: unpack, inspect, decide, restock or dispose. The problem was that this created a massive bottleneck at the inspection stage, because every item got the same level of scrutiny, whether it was a brand-new, never-opened gadget or a clearly worn pair of shoes. Luna: So not all returns are created equal. Lucas: Right. And before I get too deep into the mechanics, I want to take a quick beat here. You know, this show is ad-free, and that's thanks to listeners who chip in a few bucks here and there. Honestly, if today's episode moves your thinking forward in some small way, that's the link — buy me a coffee dot com slash fexingo. No pressure, it just helps us keep doing this. Luna: Yeah, and every little bit genuinely helps us keep the lights on and the episodes coming. Lucas: So back to the triage. They set up a dedicated triage lane where staff would sort each return into one of three buckets in under 30 seconds: restockable as-is, needs inspection, or damage and defective. That simple sorting step meant that the high-value, high-touch items got the attention they needed, while the easy ones moved straight to restocking. Luna: And that's where the time savings came from, because they weren't doing a full inspection on a sealed box that just got returned because the customer changed their mind. Lucas: Exactly. And the numbers back that up. Before the change, roughly 40 percent of returns were actually in perfect condition and could be restocked immediately. But they were being processed the same way as everything else, which meant they were clogging up the system. By pulling those out early, they freed up capacity almost overnight. Luna: Interesting. So the triage was step one. What was the second structural change? Lucas: The second change was introducing dynamic work zones. Instead of having a single returns department where everyone did every task, they split the floor into four zones: triage, inspect, restock, and dispose. And here's the key — the staffing in each zone was adjusted every two hours based on real-time demand. Luna: So they were actually moving people around based on where the backlog was forming, not just letting everyone stay in their usual spot. Lucas: Right. And they used a simple whiteboard at first, but quickly moved to a digital dashboard that showed the queue depth in each zone. The team lead would look at it and shift two or three people from restock to inspect if that's where the pile was growing. It sounds simple, but it meant they were always applying labor where it mattered most. Luna: I love that they started with a whiteboard, though. It shows you don't need fancy software to start improving. Lucas: Totally. And the third change was probably the most interesting from a human perspective. They changed how they trained their staff. Instead of training everyone to be a generalist who could do any task, they created specialist roles within the returns process, but they cross-trained people in pairs. So someone who was an expert in inspection could also step in to help with restocking if needed, but they weren't expected to be an expert at everything. Luna: So they were building flexibility without losing the efficiency that comes from specialization. Lucas: Exactly. And they found that this actually reduced errors too, because people weren't constantly switching between complex tasks. The error rate on returns processing dropped by about 30 percent, which meant fewer items got sent to the wrong place and had to be re-processed. That's a hidden cost that most people don't even think about. Luna: So the three changes were triage, dynamic zones, and this paired cross-training. How long did it take them to implement all of this? Lucas: They did it in about ten weeks. And they saw incremental improvements from the first week. The triage lane alone cut the average processing time from 15 minutes down to about 11. Then the dynamic zones brought it down to around eight. And the training piece, once they got that fully in place, pushed it down to the seven-and-a-half minute mark. That's where they hit the 50 percent reduction. Luna: That's a really nice progression. And it wasn't one big dramatic change, it was a series of small, smart tweaks. Lucas: Yeah, and I think that's the key lesson. The biggest mistake most operations make when dealing with returns is they treat it as a single monolithic process. But it's really three or four distinct sub-processes, each with its own bottleneck and its own optimal staffing level. Once you break it down like that, the improvements become much more obvious. Luna: And there's a metric for spotting the bottleneck, right? Something simple that any ops person can look at? Lucas: Yeah, it's called the returns cycle time, and it's the average time from when a return arrives at the warehouse to when it's either restocked, disposed of, or sent back to the vendor. The industry average is around five to seven days, but this facility got it down to under two days after the changes. And within that, they tracked the time spent in each zone individually. That's what let them see that inspection was the bottleneck, not unpacking or sorting. Luna: So if you're an operations manager listening and your returns are piling up, the first thing to check is which zone has the longest queue. Lucas: Exactly. And the fix might not be more labor. It could be a triage step, or a dynamic staffing model, or just better training. In this case, it was all three, but each one on its own would have helped. The combination is what got them to the 50 percent reduction. Luna: That's a great example of how process design can turn a cost center into a competitive advantage. Customers notice when their refund shows up in two days instead of two weeks. Lucas: Absolutely. And the financial impact was significant too. They calculated that reducing the returns processing time by half saved them about $1.2 million annually in labor costs alone, because they didn't need as many seasonal workers during peak periods. And that's not even counting the revenue from getting products back on the shelf faster. Luna: So the next time you return something online and get your refund quickly, there's a good chance some ops team behind the scenes is doing this kind of work. Lucas: Right. And I think the broader takeaway is that returns are not just a necessary evil. They're an opportunity to build customer loyalty and save money at the same time. The companies that figure that out are going to have a real edge. Luna: Well, and on that note, I think we've got a good blueprint here. Thanks for walking us through it, Lucas. Lucas: Thanks, Luna. And if you're thinking about your own returns process, the first step is just measuring the cycle time. You can't improve what you don't measure.