CSV Long IDs Turn to 4.9E+12 in Excel? The Station Bakery

2026-10-30

The queue at the station bakery is six people long, and you have eleven minutes.

You are holding a coffee in one hand and your phone in the other. On the phone, a spreadsheet you opened on the train. Jonas, let's call him that, works as a virtual assistant for three small online shops. This morning's job is simple: send one client the list of last week's orders, with tracking numbers, before the 9:30 call.

He scrolls to the tracking column. It should say 400123456789012. Instead every row says 4.00123E+14.

He scrolls further. Every row. All the same. A whole column of numbers that look like something from a physics exam.

The thought that arrives before the panic

The first thought is not "how do I fix this". It is: Did I do this?

That is the quiet part nobody mentions. When a file goes wrong, you don't blame the file. You blame yourself. You wonder whether you clicked something, saved over something, whether a real professional would have noticed sooner.

The person in front of him orders two croissants and asks about the oat milk. Jonas moves one step forward and opens the original export again, just to check. In the raw file, the numbers are fine. Every digit is there. It was the spreadsheet that decided, on its own and without asking, to be helpful.

That should be a relief. Somehow it isn't. Because now he has a different problem: he has no idea which of the other files on his laptop went through the same helpful treatment.

What it quietly costs

Last month, a different client had sent him a list of customer numbers. He had cleaned it up, saved it, and sent it back. Nobody complained. But standing here, with the coffee going lukewarm, he can't remember whether those numbers survived. Or whether two of them had quietly turned into the same rounded value and nobody noticed.

This is what messy data really costs. Not the ten minutes of fixing. The doubt that comes afterwards. The small, nagging feeling that something you handed over might be slightly wrong, and that you would be the last to know.

For someone who works alone, that doubt is expensive. You are the checking department. You are also the person who sends the file, takes the call, and apologises if it goes sideways.

He pays for the coffee. Nine minutes left.

The call

The call starts at 9:30 on the dot. Jonas is at the station café table now, laptop open, earbuds in, one eye on the clock.

The client, who runs a small shop selling printed stationery, is friendly. She asks about the parcels. She asks if the tracking list is ready.

"Almost," he says. It is not a lie, but it is not quite the truth either.

He shares his screen anyway, because hiding feels worse. And there they are: the numbers that look like scientific formulas. He hears himself say, "That's just how Excel shows them, give me a moment."

She laughs. "Oh, it does that to me all the time. Honestly, I stopped trusting it."

That sentence stays with him longer than the call itself. I stopped trusting it. How many people have quietly stopped trusting their own files, and just live with a low hum of "hopefully this is right"?

The moment it doesn't have to be like this

Later, on the train home, he doesn't open a spreadsheet. He just thinks.

The problem was never that he was careless. The problem was that every messy export started from zero. Every Monday he did the same small rescue, by hand, from memory, a bit differently each time. Nothing was written down. Nothing was checked before it left the building.

What if the cleaning were something he did once, and then simply ran? What if, before anything was changed, he could see what would change, and afterwards, what did? A short list. Plain words. These rows, these fixes, nothing else touched.

Not magic. Just a calm routine with a receipt.

A different Monday

Picture the same bakery queue a few weeks later.

The export has already landed in a folder. Jonas orders his coffee without looking at his phone. By the time he sits down, the cleaned file is there, the long numbers intact, the dates the right way round, the duplicates gone, and a short change report sits beside it. He reads it the way you read a till receipt: quickly, with a small nod.

He sends the file at 9:12. The call at 9:30 is about the client's new product line instead.

The coffee is still hot. That is the whole difference, really. Not a productivity miracle. Just a coffee that is still hot, and a head that is not elsewhere.

If you recognise yourself

Maybe you don't work with tracking numbers. Maybe it's invoice references, customer IDs, barcodes, order numbers. The names change. The feeling is the same: a file that looked fine, a number that wasn't, and a few minutes of wondering what else slipped through.

You don't need to become a different kind of person to stop feeling it. You need a routine that checks the boring things for you, shows its work, and lets you get on with the part of the job that is actually yours.

If that sounds like the Monday you'd like, there is a small toolkit built for exactly this: Clean Data in Minutes – CSV & Excel Cleaning Toolkit (Python). It cleans messy CSV and Excel exports, with a dry-run first and a change report afterwards, so you can see what it did before you trust it. It comes with a 30-day money-back promise: if it doesn't help, you get a full refund, no questions.

It won't make Mondays glamorous. It might just keep the coffee warm.

An illustrative story, written with AI assistance.