The Double Price

The stand said three euros.

Four Duracell batteries. A large wholesale store. By current prices, a good deal. I picked them up and walked to the register.

The cashier scanned them the way she would scan anything else.

Six euros appeared on the screen.

I said the price should be lower. A cashier from the next register came over and explained quietly that these batteries had been entered into the system twice. Normal scan gave the wrong price. You had to choose a different row in the system — a second step that was not obvious to her.

And then the first cashier said something I couldn't stop thinking about.

She looked at her colleague and said: how am I supposed to know which row I need to choose?

There was no good answer to that.

From my side of the counter, nothing looked unusual.

One product. One stand. One price. One pack in my hand.

But inside the system, there were already two realities.

In one, the batteries cost three euros. In the other, six. The difference between those two realities was not visible to me. It was not reliably visible to the cashier either. It depended entirely on whether the person at the register happened to carry a piece of hidden knowledge in their head.

That is the part I couldn't unsee.

This is what makes some system failures dangerous.

They do not look like failures. The cashier scans. The number appears. The process continues. Everything looks routine.

And routine is exactly what makes the wrong number credible.

Sometimes customers get the wrong result not because anyone decided to cheat them — but because the system quietly makes honest people produce dishonest outcomes. The person in front of you looks like the source of the error. Often they are only the carrier.

Intent matters morally. Operationally, the money still leaves the wallet.

There is one more layer worth naming.

It is easy to say "it's not their fault" and stop there. But that sentence can hide something important.

If a system repeatedly creates situations where the customer can be charged the wrong amount unless an employee remembers a secret exception — the confusion is no longer random. It becomes part of how the system operates. Not always by design. Sometimes by neglect. Sometimes because the friction lands on the customer, not on the process itself.

That is usually enough for broken logic to survive for a very long time.

You see this pattern far beyond retail.

A service desk agent knows which button not to trust. A project coordinator knows which approval path actually works. A finance person knows that one code means the displayed number is wrong unless you override it manually.

The system looks clean from the outside. Inside, it survives on private memory.

And when the person who holds that memory is not there — the wrong number appears. Not because someone failed. Because no one fixed the thing that was broken.

Training someone to work around a broken signal is not fixing it. The signal stays broken for the next person. And the one after that.

The most dangerous system failures are not always dramatic.

Sometimes they look like a cashier doing her job.