What Bad Customer Service (And Systems) Actually Cost You
Imagine this…
You're an FMCG ecommerce business running Shopify. An order comes in on a Monday: a single product, sitting in your warehouse, 2-4 business days to dispatch. Pretty standard.
On the Wednesday, the customer emails asking about Express shipping. It wasn't offered at checkout, but they need the product quickly and they're happy to sort it out manually. They're offering to give you more money. How hard can this be?
It's now two weeks later and you've just issued a refund.
Here's how it unravelled.
Your support team took 24 hours to reply and didn't actually answer the Express question. The customer replied immediately and asked again. Another 24 hours. Yes, it's available. Another $5. The customer replied instantly and asked for a payment link. It was Friday.
No response before the weekend.
Monday night, 7pm, your agent sends a message saying the link had been sent by separate email. It hadn't. The customer asked for it to be forwarded to a different address. Nothing that night. Nothing Tuesday either.
Throughout all of this, the customer was calling your business phone number. Multiple times a day. Nobody picked up. Not once.
I know exactly how this story ends. Because the customer in this scenario was me. Maybe the business I bought from was yours. And because I work in this industry, I know why it happened.
The email problem nobody knows they have.
I should mention: I never received an order confirmation either. My card was charged successfully (of course that part worked fine), but nothing landed in my inbox.
This happens more often than businesses realise. When transactional emails don't arrive at iCloud addresses, a misconfigured email security certificate is almost always the reason. SPF, DKIM, or DMARC records set up incorrectly, or not at all, get quietly rejected by Apple's mail servers. The business never finds out. The customer just assumes something's wrong and starts getting anxious.
The only platform I touched as a customer was Shopify. That's the whole picture, and that's kind of the point.
Shopify is great. It's not a warehouse management system.
Shopify is excellent at what it's built for. But a lot of small and medium FMCG businesses treat it as their end-to-end operations platform: take an order, pick it, pack it, ship it, all managed from the orders screen.
For low volumes, you can get away with it. But it's fragile. There's no real structure for prioritising orders. Little visibility into what's sitting in the queue. No workflow that tells your warehouse team what to do when something unusual lands, like a customer who needs urgent dispatch and is trying to pay you an extra $5 to make it happen.
Running pick/pack/ship purely out of Shopify is a recipe for eventual disaster. Not maybe. Eventually. A proper warehouse management setup gives your team structure, flags the right orders at the right time, and means an urgent request doesn't just disappear into a list.
The support problem is the same problem.
Even with a solid warehouse setup, this situation fell apart because nobody had oversight of an open thread. When your support tool talks to your order management platform, agents can see the full picture: dispatch status, shipping options, and outstanding payment requests. The conversation and the order exist in the same place.
When they don't talk to each other, you get what I got. Slow responses, missed follow-ups, and a phone that rings out. That's not a people problem. It's a systems and process problem, and it's a fixable one.
The 2% hypothetical.
Here's the bit that should make you uncomfortable.
Say your average order value is $100. And say just 2% of your orders go badly enough that you lose the sale.
At 500 orders a month, that's 10 lost sales. $1,000 gone. Every month.
At 1,000 orders a month, that's $2,000. Per month. $24,000 a year — from a 2% failure rate.
In my case, the business didn't just lose a sale. They spent staff time across two weeks on a support thread, missed multiple phone calls, and left someone who works in this industry with a story worth writing about. The $5 Express shipping upgrade cost them considerably more than $5.
The fix isn't expensive relative to what the problem costs. Connected systems, a proper warehouse process, someone with oversight of open support requests. That's it. For a business doing real volume, it pays for itself fast.
The short version.
Get your systems talking to each other. Give your warehouse team a real process, not just an orders screen. Make sure someone can see what's open and what's been waiting. And check your email deliverability settings, because if your order confirmations aren't arriving, neither is the trust that comes with them.
Nearly two weeks for one order of an in-stock item is a long time. Your customers notice. And so should you.
About Misadventures in Retail
We spend a lot of time helping businesses sell and ship things better. But we're also customers, and sometimes the experience on that side of the counter is illuminating in ways a client brief never could be. Misadventures in Retail is an ongoing series where we write about real shopping experiences that went wrong, and what the businesses involved could have done differently, systematically, not just operationally. If you recognise your business in any of it and want help getting it sorted, we'd love to hear from you.
