Last week, I ordered a pair of shoes online from a reputable Canadian clothing retailer. The whole point of ordering online was convenience—skip the store, have them delivered to my door, done. When the box arrived, I opened it to find my new shoes. Along with a Black Friday bonus I hadn't ordered: an anti-theft security tag, firmly attached. Now I get to make a trip to the store anyway.
The Funny Part (Sort Of)
There's an irony here that's hard to miss. An anti-theft device—designed to prevent someone from walking out of a store with unpaid merchandise—was carefully packaged and shipped directly to a paying customer's home. The tag did its job perfectly: it prevented theft. It just also prevented me from wearing shoes I'd already paid for.
Mistakes happen. But as someone who spends her days helping companies build better operational systems, I couldn't help but see this for what it is: a process gap with a visible symptom.
What Actually Went Wrong
Somewhere between the warehouse shelf and the shipping box, a step got skipped. Maybe there's no checklist. Maybe there's a checklist that doesn't include "verify security tags removed." Maybe there's a checklist that nobody uses because they're rushing to meet fulfillment targets.
Whatever the root cause, here's what we know for certain: the system—or lack of one—allowed a tagged item to reach a customer. This isn't a one-off human error. When something like this happens, it reveals a structural vulnerability. The question isn't "who made the mistake?" It's "why did our process allow this mistake to happen?"
The Real Cost
That little plastic tag probably costs less than a dollar. But let's add up what this single incident actually costs the retailer:
- Customer service time to handle my inquiry
- Store associate time to remove the tag when I come in
- My goodwill and trust, slightly diminished
- Potential lost future revenue if I decide online ordering isn't worth the hassle
- Social proof damage if I post about it here
Multiply this across every customer who receives a tagged item—because if it happened to me, I'm certainly not the only one—and you're looking at a meaningful operational cost. All because of a missing checkbox.
What Good Looks Like
Effective fulfillment processes don't rely on people remembering things. They build verification into the workflow:
- Visual inspection as a discrete step, not bundled with "pack the item," but its own action that must be completed
- Physical workflow design, where items pass through a security tag detection point before entering the shipping area
- Checklists that are actually used. Simple, visible, and integrated into the work rather than posted on a wall and ignored
- Feedback loops, when a customer reports this issue, it triggers a process review, not just an apology
The goal isn't to add bureaucracy. It's to make the right outcome easier than the wrong one.
The Bigger Picture
I share this story not to criticize one retailer, but because it's such a clear illustration of something I see constantly: organizations that have grown faster than their systems.
When you're small, you can rely on institutional knowledge and careful people. When you scale, those careful people are now training new hires, managing increased volume, and working under time pressure. Without documented, enforced processes, quality becomes inconsistent.
The security tag on my shoe isn't a training problem. It's not a personnel problem. It's a systems problem. And systems problems require systems solutions.
The Question Worth Asking
Every business has their version of the security tag—some visible breakdown that customers see, and others that stay hidden internally but cost money, time, or reputation.
What's yours? And more importantly: does your current process make that mistake possible, or does it make that mistake nearly impossible?
The difference often comes down to a checklist, a verification step, or a simple workflow adjustment. Sometimes, it really is that simple.