Blixwerk

CSV Full of Duplicates Every Week? The Friday 11:00 Call

2026-10-15

Friday, 10:52. Your video call starts in eight minutes.

You have the weekly customer export open on the left screen and the report you promised on the right. The export came in this morning, the way it does every week. You already know what is in it before you scroll.

Some customers appear twice. Some appear three times, once as "Anna Weber", once as "anna weber " with a space at the end, once as "WEBER, ANNA". The dates are a mix: 03/10/2026, 2026-10-03, 3.10.26. One phone number begins with a plus, the next with two zeros, the next with nothing at all. Somewhere a name that should say "Müller" says "Müller".

You tell yourself it will take ten minutes. It never takes ten minutes.

The number that didn't match

Let's call her Mara. She is not a real person, just someone you may recognise. She works alone, doing marketing support for a small garden-supply shop. Every week she turns the shop's raw export into a tidy summary: new customers, repeat customers, who to include in the next mailing.

Last Friday she sent the summary with a quiet, hopeful feeling. Then the owner joined the call, looked at the screen, and said, kindly, "That seems like a lot of new customers. Didn't we have about this many last month?"

Mara felt the heat start at her collarbones.

She knew what had happened. A handful of people had been counted twice, and she had missed it. It was Friday, she had been tired, and the file had been long. She said, "Let me check that and send a corrected version this afternoon." Her voice was steady. Her stomach was not.

Nobody was angry. The owner said, "No rush." That almost made it worse. Mara is the person who is supposed to be the careful one.

What it quietly costs

The file was never the real problem. The cost was everything around it.

It was the hour on Thursday evening that was supposed to be free. It was the small dread when the export email arrived, and the habit of opening the file, sighing, and closing it again until later. It was the private worry that one day a mistake would slip through into a mailing, and a customer would get the same email twice and wonder who is running this place.

It was the feeling of not being a real business. Real businesses, she thought, surely don't sit and delete rows by hand.

That afternoon she fixed the report. It took fifty minutes. She sent it with a short, slightly over-apologetic note. Then she closed the laptop and stood at the window for a while, looking at nothing in particular.

She thought: I have done this every week for a year. I am going to do it every week for another year.

The small turn

Nothing dramatic happened. There was no breakthrough at 3 am.

What happened was smaller. Mara noticed that the mess was not random. It was the same mess, every week. The same trailing spaces, the same three date styles, the same name written in capitals. The export was not surprising her. She was just meeting the same old problem again, as if for the first time.

And if the problem is the same every week, it doesn't have to be fixed by hand every week.

That thought loosened something. It wasn't about being cleverer or more careful. The work could simply be set up once, so that a tired Friday-afternoon version of her didn't have to hold all the details in her head.

She also wanted to see what was about to change before it changed. Deleting rows and hoping was what had hurt her. She wanted a list she could read, saying: these two were merged, these dates were rewritten, these rows were left alone.

A different Friday

Picture the same Friday a few weeks on.

The export arrives at 9:30. Mara opens her tea, not the file. She runs the cleanup and reads the short summary of what it found: duplicates merged, dates made consistent, phone numbers tidied. Nothing has been changed without her seeing it first.

The summary takes four minutes to read. She spots one pair of names she isn't sure about, checks them herself, and decides. That is the part that should be hers: the judgement, not the janitorial work.

At 10:52 she is not scrolling and sweating. She is refilling her water glass.

On the call, the owner glances at the numbers and nods. Maybe they ask a question, maybe they don't. Either way Mara can answer it, because she knows where each number came from. She closes the laptop at lunchtime and the afternoon is hers.

It is a very ordinary change, and ordinary is exactly the point. A quiet Friday is a good Friday.

If this sounds like your week

Maybe your file isn't a customer list. Maybe it's orders, invoices, a client export or a mailing list. The shape is the same: a CSV that shows up messy on a schedule, and an hour you'd rather not give it.

If you recognise yourself in Mara, we built Clean Data in Minutes – CSV & Excel Cleaning Toolkit (Python) for exactly this. It handles duplicates, dates, phone numbers and encoding, and it works as a dry run first, so you see a change report before anything is touched. It is a Python toolkit, so it suits you if you're comfortable running a script. Like all our paid products, it comes with a 30-day money-back promise: if it doesn't help, you get a full refund, no questions.

You don't have to love data cleaning. You only have to stop doing it by hand every Friday.

An illustrative story, written with AI assistance.

Sounds familiar? Clean Data in Minutes – CSV & Excel Cleaning Toolkit (Python) – Clean messy CSV/Excel exports in minutes: dedupe, fix dates, phones, encoding, split, merge, validate. Dry-run + change report.

Take a look