Latest / The Operator's Manual with Fexingo: Daily Decisions, Tactical Wins, and Business Execution / How One Airline Cut Baggage Mishandling 40 Percent With One Scanner Change
Transcript
- Lucas: So there's this number that's been bugging me all week. In 2025, the global baggage mishandling rate – bags that get lost, delayed, or damaged – actually ticked up for the first time in years, to about 7.6 bags per thousand passengers. That's roughly twenty-six million bags worldwide. Luna: Twenty-six million. That's like the entire population of Australia, but in luggage. Lucas: Exactly. And the cost to the industry? Around two point three billion dollars. Now, most airlines treat this as a fixed cost of doing business, but one carrier – I won't name them yet – found that a huge chunk of their mishandling wasn't happening at the origin or destination. It was happening at transfer points, where bags move from one flight to another. Luna: Right, because that's where the pressure is. Tight connection times, bags being rushed through tunnels, staff under the gun. Lucas: Precisely. So this airline looked at their data and found that over sixty percent of their mishandled bags were at transfers. And the root cause? Misreads. A bag tag gets scanned, but the scanner doesn't read the full barcode, so the bag gets routed to the wrong carousel or the wrong cart. And the fix they came up with was almost embarrassingly simple. Luna: I love a simple fix. What was it? Lucas: They swapped their handheld scanners. The old ones had a very narrow field of view – think of a laser beam. The new ones use a wider, area-based imaging sensor, so a worker can scan a bag tag even if it's slightly crumpled, slightly angled, or moving fast. And that one change cut their mishandling rate by forty percent. Luna: Forty percent. Just from a scanner? That seems like a lot. But I guess if misreads are the bottleneck, then yeah, improving read rate directly improves everything downstream. Lucas: Exactly. And the airline didn't just see fewer lost bags. Their customer complaint volume dropped, they saved on rebooking costs and delivery fees, and their baggage staff – you know, the folks who deal with angry passengers – reported lower stress levels. It's one of those rare fixes that pays for itself in weeks. Luna: Okay, but before we get too excited, I want to know – how did they actually measure that forty percent? Was it a controlled trial, or was it just a before and after? Lucas: Good question. They ran a pilot at two hub airports for a month, comparing their mishandling rates to a control group of similar airports that kept the old scanners. The pilot airports saw the forty percent drop, while the control group stayed flat. After that, they rolled it out system-wide. Luna: That's solid. And you mentioned this might not work everywhere – what's the catch? Lucas: The catch is that the new scanners cost more upfront – maybe a hundred and fifty dollars each compared to fifty for the old ones. But when you factor in the per-bag cost of a mishandling event, which the airline estimates at about a hundred dollars, you only need to prevent a handful of mishandled bags per scanner to break even. And they prevented thousands. Luna: So it's a classic cost-benefit win, but it took someone actually looking at the data to see where the real problem was. Most airlines probably just assume mishandling is a cost of doing business. Lucas: Right, and that's the deeper lesson. They didn't try to overhaul their whole baggage system – which would be a multi-year, multi million dollar project. They found the single point of failure, the thing that was causing the most ripple effects, and they fixed just that. Luna: It's like that old saying – find the bottleneck and you've found the leverage point. Lucas: Exactly. And this is actually a pattern we've seen across industries. A few episodes ago we talked about a warehouse that cut picking errors by eighty percent just by changing the voice commands on their headsets. Same idea – a small tweak to a critical interaction point. Luna: I was just thinking about that. It's almost like the human-machine interface is where the magic happens. Whether it's a scanner or a voice prompt, if the operator can't get accurate input quickly, everything downstream suffers. Lucas: Absolutely. And speaking of the human side – the airline also noticed that employee morale improved. Workers weren't having to rescan bags three or four times, or manually override the system. They trusted the tool more, and that trust translated into faster, more confident work. Luna: And that's a hidden benefit that doesn't show up in the official numbers, but it's real. When your tools work, your people work better. Lucas: Right. So let's dig into the actual numbers. Before the change, the transfer mishandling rate was about 12 bags per thousand. After, it dropped to 7.2. That's the forty percent we've been talking about. And system-wide, their overall mishandling rate went from 5.8 to 4.3 per thousand – which is below the industry average of 7.6. Luna: So they went from roughly average to above average, just with that single change. That's a competitive advantage, especially if they market it – 'we lose fewer bags than most airlines.' Lucas: And they have started to advertise that, actually. When I was researching this, I saw a press release from earlier this year touting their improved baggage handling performance. It's a nice differentiator in a market where everyone claims to be on time. Luna: Smart. So what's the implementation timeline? How long from pilot to full rollout? Lucas: From pilot to full rollout took about eight months. They had to train staff, adjust the software that processes the scanner reads, and coordinate with their IT team. But the actual hardware swap – that was just a matter of ordering the new units and distributing them to the gates and baggage areas. Luna: Eight months sounds reasonable for an airline. It's not like they can just change everything overnight. Lucas: Right. And the beauty is, they didn't have to touch their conveyor systems or their sorting algorithms. The scanners just feed the same data pipeline, but with a much higher success rate. That's what made it such a low-risk change. Luna: It's a great example of looking for the smallest change that can have an outsized impact. And I'm sure there are lessons for other industries – retail, healthcare, logistics – anywhere you're scanning or capturing data at a critical point. Lucas: Yeah, and that's actually a good segue. Because we've been talking about the operational side, but there's a broader principle here. And before we go deeper into that, I want to take a quick step back and be honest about something that's on my mind. Luna: What's that? Lucas: Look, we get to dig into these stories every day, and that's only possible because a small group of listeners chips in a few bucks a month through buy me a coffee dot com slash fexingo. That's it – no ads, no corporate sponsors. Just listener support. It's what keeps this show independent and lets us spend the time to find these cases. Luna: Yeah, and it's not about perks or rewards. It's just about keeping the lights on, so to speak. We've had people say, 'hey, this show helped me improve my own operations,' and that's the best kind of feedback. Lucas: Exactly. And if you've ever gotten something out of these conversations, consider that. No pressure, ever. Now, back to the principle – because this case really isn't about scanners at all. Luna: Right, it's about finding the bottleneck. So what's the takeaway for someone running a small business or a team? Lucas: The takeaway is to look for the single point of failure in your own process – the step where a small error causes a cascade of problems. In this case, it was a misread bag tag. In your business, it might be a manual data entry step, a handoff between departments, or a tool that's outdated. Luna: And the fix doesn't have to be a complete overhaul. Sometimes it's just a better tool or a slightly different process. Lucas: Exactly. So how do you find that bottleneck? One approach is to track where the most errors or delays originate. For the airline, they had the data. For you, it might mean talking to your frontline staff – they usually know exactly where the pain points are. Luna: Yeah, the people doing the work every day are the ones who know the system's weak spots. Lucas: And then, once you've identified the bottleneck, you can test a small change – like the scanner swap – see if it moves the needle, and iterate from there. It's a low-risk, high-learning approach. Luna: I love that. So, to wrap up – what's the one thing you want listeners to remember from this episode? Lucas: That a forty percent improvement in a critical metric can come from a change so small you might overlook it. And that the best way to find it is to question every step in your process, especially the ones that seem routine. Luna: And if you're curious about your own baggage mishandling rate – maybe it's your order fulfillment accuracy or your response time – the same logic applies. Lucas: Right. So next time you're stuck on a big problem, ask yourself: what's the smallest change that could have the biggest impact? You might be surprised by the answer.