When the Customer Knows Before Your Team Does

A customer knew before we did. That's the sentence every Ops director dreads hearing back from their own team. Not because it's rare, but because it's common enough that most people in this role have lived it at least once.

In March 2024, McDonald's tills and kiosks went down across multiple countries. Customers were posting about it and queuing at closed counters before there was any public statement on what had happened. The next day, Sainsbury's experienced issues with contactless payments, SmartShop, and Nectar, while chip and pin continued to function. Shoppers were the ones piecing together which parts of the system were down and which weren't.

The visibility gap between the public experience and the internal knowledge is where trust erodes fastest. Once a customer is the one explaining your outage to you, you've lost the narrative, and usually the queue as well.

Here's the test I'd put to any Ops team running a distributed estate: not 'did something break?' Something will always break across enough sites eventually. The real test is: did you catch it in the signal, or did you catch it at the till?

Those are two different companies to run. One has a customer standing in front of a dead card reader, working out for themselves what's gone wrong, then telling a member of staff who has to relay it upward before anyone with the authority to fix it even knows there's a problem. The other has already seen the signal degrade, already knows which site, which system, and roughly what it's costing per hour it stays down.

The difference isn't about detection speed; it's about who's doing the noticing. A customer noticing on your behalf means your monitoring has already failed, whether or not the underlying system comes back up in five minutes or five hours. Fast detection after that point is damage control, not operational visibility.

Distributed retail estates generate a constant stream of small signals long before anything is bad enough for a customer to stand in front of it. A payment terminal that's slower than usual, a kiosk that's dropped connection twice this week, a refrigeration controller dropping off the network. None of that is dramatic, but all of it is where the story usually starts.

The operators who avoid the 'customer knew first' moment aren't the ones with fewer things going wrong. They're the ones who've built the habit of watching the estate as a whole, not waiting for a specific site to escalate a specific complaint. The customer at the till shouldn't be your alert system.

Category
Retail IT Management
Operational Visibility
Written by
Ross Palmer
CEO and Co-Founder, HelmCore
blogs and articles

Latest insights and trends

The risk inside every upgrade: an aeroplane and a floppy disk linked to a network of store technology, with one fault highlighted in amber
Retail Operations

Floppy Disks, Fibre and the Risk Inside Every Upgrade: What Multi-Site Retail Can Learn from US Air Traffic Control

As the FAA replaces floppy disk systems across 435 facilities, four lessons for retailers running old and new technology side by side.
Buyer's guide: how to choose operational intelligence software for a multi-site estate, with a scorecard of eight checks
Retail Operations

How to Choose Operational Intelligence Software for a Multi-Site Estate

Eight checks for choosing operational intelligence software across a multi-site retail estate, and what to ask each supplier to show you.
Self-checkout screen showing online, with a card not accepted for a €97.50 payment
Retail Operations

Your Self-Checkout Is Online. Your Customer Still Can't Pay.

Self-checkouts can show green on every dashboard and still fail to take a payment. The cost sits in the gap between uptime and transaction success.
Formula for IT incident cost per store: trading per till per minute × minutes down × affected tills, plus call-out cost and staff time.
Retail Operations

How to Calculate the Cost of an IT Incident per Store

Lost transactions, abandoned baskets, staff time and call-outs: a step-by-step way to put a number on what each IT incident costs a store.
HelmCore alert about a card issuer outage, showing business exposure in euro.
Retail Operations

Not Your Outage. Still Your Problem.

When Revolut cards failed at Irish tills, the fault sat outside the estate. The cost still landed in store. Count the minutes it took.
SEE IT ON YOUR ESTATE

See what's happening across your estate, in real time

Book a meeting and we'll show you what HelmCore sees across your sites, and what your incidents are costing you.