CSV Column Names Don't Match? The Fair Booth

2026-11-03

It is 10:20 on a Tuesday, and Ines is standing behind a folding table at a trade fair, between two visitors.

Her stand is small: stacked notebooks, a card reader, a bowl of mints. Her laptop sits half hidden behind a display of pencil sets. On the screen are two spreadsheets she has been avoiding since Sunday.

One is the export from her own web shop. The other is from the marketplace where half her orders come from. Same customers, same products, same business. But one file says Order ID and the other says order_number. One has E-Mail, the other customer email. One writes the date as 03.11.2026, the other as 2026-11-03.

A wholesale buyer has asked for a combined customer and order list by lunchtime. "Just so I can see what you sell, and where," she said, smiling.

It sounded like a small thing. It always does.

The little mismatch that eats the morning

You know this feeling if you have ever tried it. You paste one file under the other, and the columns don't line up. Half the cells are empty. Some columns appear twice with slightly different names, like cousins who never met.

So you start fixing by hand. You rename a header here, drag a column there. You are sure you'll be done in ten minutes.

Then a visitor walks up and asks about the green notebooks. You answer. You turn back and can't remember which file you were in. Did you already move the email column? Was that the first file or the second?

It isn't the difficulty that wears you down. It's the doubt. The quiet question underneath every copy-paste: what did I just break, and will I notice before someone else does?

Ines had been through this before. Last quarter she spent a whole Sunday afternoon on a merge like this, and found out three weeks later that a handful of customers were listed twice. Nobody was angry. But she still felt a small, hot embarrassment each time she thought of it. It felt unprofessional, the kind of mistake that a real business with a back office wouldn't make.

What it quietly costs

The cost doesn't show up as a number. It shows up as a mood.

It's the way your shoulders rise when someone says "can you send me everything in one file?" It's the evening you meant to spend cooking, quietly traded for a spreadsheet. It's putting off a perfectly good opportunity, a buyer, a new channel, a partner, because combining the data feels like a chore with unknown edges.

And it's the small lie you tell yourself: I'll sort it out properly later. Later is where unmatched columns go to multiply.

At the fair, Ines felt every bit of it. A buyer was waiting. Her coffee had gone cold. And she was hunched over a laptop, trying to teach two files to speak the same language.

The sentence she didn't expect

During a lull, the woman at the next stand leaned over. She sold handmade candles and had watched Ines frown at the screen for twenty minutes.

"Bad news?"

"Two lists that should be one," Ines said. "Different headers. I'm going to be here all day."

The candle maker shrugged, kindly. "I used to do that by hand too. A friend who writes code showed me she just had a little script do the matching and tell her what it changed. She looked at the report, said 'fine,' and went for lunch."

It wasn't a grand revelation. It was a single sentence. But something in Ines loosened. She had assumed the only options were do it by hand and hope or become a programmer. She had never thought of a third thing: something that does the boring part, then shows you its work.

That last bit mattered most to her. Not speed. Being able to see what happened before anything is final.

A different Tuesday

Picture the same booth on another day.

The buyer asks for the combined list. You say, "Of course, I'll send it after lunch," and you mean it. You don't feel the old tightening in your chest.

Later, at a quiet moment, you open the two exports. The headers don't match, as usual. But this time you aren't hunting through columns. You glance at a short summary: which columns were treated as the same thing, which rows were duplicates, what was left alone. It reads like a receipt. You check a few lines, nod, and save the file.

The whole thing takes about as long as the mints in the bowl take to disappear. Then you go back to what you're actually good at: talking to people about notebooks.

That evening, nothing is waiting for you. The laptop stays closed. The list is already in the buyer's inbox, and you don't wonder what's wrong with it, because you saw what was done.

The feeling isn't excitement. It's quieter than that. It's the absence of a low hum of worry that you had stopped noticing until it was gone.

If you recognise yourself in Ines

Maybe it isn't a trade fair for you. Maybe it's a client who sends one export and a colleague who sends another, or a marketplace, a payment tool and a newsletter list that all insist on naming things differently. The scene changes. The knot in the stomach is the same.

If that's you, there is a small toolkit made for exactly these chores: Clean Data in Minutes – CSV & Excel Cleaning Toolkit (Python). It helps you tidy messy CSV and Excel exports: removing duplicates, fixing dates, phone numbers and encoding, splitting and merging files, and checking the result. It does a dry run first and gives you a change report, so you can see what would happen before you commit to it.

Like every Blixwerk product, it comes with a 30-day money-back promise. If it doesn't help, you get a full refund, no questions.

No rush. Next time two files refuse to line up, you'll know there's a calmer way to do it.

An illustrative story, written with AI assistance.