Three Real Spare Parts Projects: What SpareCompare Actually Found

It's one thing to argue, in the abstract, that most companies are sitting on unrecognized spare parts savings. It's another to show the actual numbers from real projects. Here are three, each run against a different kind of challenge, with the specific figures each one turned up.
Case One: Protecting a 70 Million Euro After-Sales Business
The starting point here wasn't a cost problem. It was a visibility problem on a business that was already profitable and worth protecting.
The challenge. The customer's after-sales spare parts business represented more than 70 million euros in value, a genuinely significant, profitable operation. But the parts catalog behind it had grown to more than 15,000 items, an unmanageable range to track manually. On top of that, staying competitive meant monitoring thousands of web shops for pricing intelligence, far beyond what any team could realistically watch by hand.
The approach. The project combined web scraping and crawling to pull pricing data at scale, product matching and enriching to connect that external data to the customer's own catalog, and ongoing monitoring to keep the picture current rather than static.
What it found. Price leakage worth more than 1 million euros was identified- revenue the business was losing simply because pricing wasn't being tracked closely enough against a fast-moving market. The project brought more than 5,000 relevant web shops under active monitoring, turning an impossible manual tracking task into a running system. And spare parts master data improved by more than 90 percent, closing a data-quality gap that had been sitting underneath the pricing problem the whole time.
Case Two: Turning 1,000 Invoices Into a Savings Roadmap
This case started from the opposite direction, not a monitoring gap, but a data format problem. The customer's spare parts data existed almost entirely in non-digitized form, and nobody had a reliable way to see what was actually being spent, or where it overlapped.
The challenge. Data overview was hindered by non-digitized formats across the board. Overlaps between different data sets were going unidentified, quietly creating redundant purchasing. And more than 24 million euros in spare parts spend was potentially affected by margin erosion, a category large enough that even a modest percentage gap represented real money.
The approach. The project centered on PDF scanning to digitize the underlying documentation, followed by the same product-matching and enrichment process, and ongoing monitoring once the baseline was established.
What it found. More than 1,000 PDF invoices got scanned and converted into structured, usable data. That process surfaced more than 4,000 overlapping items, parts being purchased more than once under different descriptions or SKUs, sitting invisible in the original format. Altogether, the project identified a savings potential of more than 2.4 million euros.
Case Three: Scaling the Same Problem Across Six Countries
The third case took a similar starting problem, non-digitized, messy data, and applied it at a genuinely larger scale: six countries, each with its own data set, its own purchasing patterns, and its own version of the same underlying issue.
The challenge. Data overview was hindered by non-digitized formats and messy data, consistent with the pattern in case two, but now multiplied across geography. Spend on items purchased directly by technicians in the field had low visibility and low control. And the processing cost of handling PDF invoices manually was disproportionately high compared to total spend, in this case, more than 15 percent, meaning a meaningful share of the value in each invoice was being consumed just by the cost of processing it.
The approach. This project combined all three core capabilities: PDF scanning, web scraping and crawling, and product matching and enriching, run country by country.
What it found. Six countries' worth of datasets got digitized. The team scanned more than 15,000 PDF invoices across the full engagement. The total potential savings identified came to more than 1 million euros, uncovered because the data could, for the first time, be compared and analyzed as a single, coherent picture rather than six separate, disconnected messes.
What These Three Cases Have in Common
Despite starting from different problems- an after-sales business worth protecting, a single large spend category, a multi-country rollout- all three cases converge on the same underlying pattern. In every case, the savings or the risk being addressed weren't caused by bad negotiating or bad decisions. They were caused by data that existed but wasn't usable: locked in PDFs, scattered across web shops nobody had time to check, or duplicated across systems that didn't talk to each other.
And in every case, the fix followed the same basic sequence: get the data out of whatever format it was trapped in, match it against a reliable external reference, and keep monitoring so the picture doesn't go stale again. None of the three projects required the customer to change suppliers, restructure their procurement process, or migrate systems before starting.
The Range of Outcomes Is the Point
These three cases span a fairly wide range, from a single business unit's after-sales pricing to a six-country, multi-currency rollout. What stays consistent across that range is the size of what turns up relative to the size of the problem: a percentage or two of a large spend category, applied at scale, adds up to real money almost every time the underlying data actually gets looked at properly.
Every project starts the same way: a look at your actual data, whatever format it's currently in, to see what's realistically sitting in your own catalog.





Kommentarer