When a Simple Check Turned Into a Serious Data Problem
It started with what seemed like a routine task: verify that the EANs we had assigned to roughly 1,200 products were accurate before uploading them back to the licensing authority. EANs — European Article Numbers — are unique product identifiers issued by a licensing body, and any error in our submission would mean inaccurate records on their end. Not something we could afford.
We had three Excel files to work with. One was the master list of approximately 11,000 EANs supplied by the authority. Another was our internal product allocation file. The third was a working sheet that had been updated over time by different people. Together, these files held the answer to whether our 1,200 product assignments were correct — but getting to that answer was harder than I expected.
Why Manual Comparison Wasn't Going to Work
My first instinct was to handle it with Excel formulas. I started building VLOOKUP-based comparisons to cross-reference the allocated EANs against the master list. That part worked reasonably well for catching obvious mismatches. But the real complexity showed up quickly.
Because the EANs are random, non-sequential numbers, there was no logical pattern to spot anomalies by eye. I needed to confirm three things simultaneously: that every EAN we assigned actually existed in the master list, that no EAN had been accidentally used for more than one product, and that no product had been assigned an EAN from outside our allocated batch. On top of that, the final output couldn't just be a report — it needed to be formatted as a batch upload file ready for the authority's system.
I got partway through before realizing that the formula logic I had built was getting fragile. One wrong reference and the whole comparison would produce false positives. With 1,200 records and a hard submission deadline, I couldn't afford to trust a half-built solution.
Bringing in Specialist Support
After hitting that wall, I reached out to Helion360. I explained the full picture — the three files, the 11,000 EAN master list, the 1,200 allocated numbers, and what I needed checked. Their team understood the problem immediately and took over the Excel work from there.
They structured the comparison properly from the ground up. Using a combination of Excel functions and structured logic, they built a clean cross-referencing system that matched our product assignments against the master EAN list, flagged any EAN that didn't appear in the allocated batch, and identified every instance of a duplicated EAN across different products. Each issue was categorized clearly so I could see exactly what was wrong and why.
What the Clean-Up Revealed
Once the comparison was fully run, a small number of errors surfaced — a few EANs that had been entered incorrectly and one case of a duplicated number assigned to two different products. None of these would have been obvious without a systematic check. If we had uploaded the data as-is, those errors would have been registered with the authority and required a formal correction process.
The team also built the batch upload files in the exact format required for submission, which saved another round of reformatting work on my end. Everything came back structured, labeled, and ready to use.
What I Took Away From This
The core lesson here was about the difference between a task that looks like data entry and one that is actually data integrity work. Comparing EAN product files across multiple sources, at this scale, requires a consistent and testable method — not just a quick formula pass. The more files involved and the more people who have touched the data, the higher the chance that small errors have crept in.
For anyone managing product databases tied to regulatory or licensing systems, this kind of pre-upload audit is worth doing carefully and completely. Errors in EAN registration can create downstream compliance issues that are time-consuming to unwind.
If you're working through a similar Excel data comparison problem — whether it's EAN validation, product file reconciliation, or batch file preparation — Helion360 handled exactly this kind of work and delivered a clean, verified result. For related examples, explore how I collected and organized CEO contacts into a structured Excel sheet and how I turned PDFs into PowerPoint and Excel workbooks. They're worth contacting if the complexity has outgrown what a manual check can reliably catch.