top of page

The Procurement KPI Nobody Tracks: Price Leakage

  • Skribentens bild: Laura Andersson
    Laura Andersson
  • 14 aug.
  • 4 min läsning

Uppdaterat: 18 aug.

procurement

Walk into any procurement function and ask what gets measured, and you'll hear a fairly consistent list: cost savings, contract compliance, supplier on-time delivery, spend under management. All good, all worth tracking. What's conspicuously absent from that list, at almost every organization, is price leakage on spare parts and MRO categories, the slow, unmeasured gap between what you're currently paying and what the market would actually charge for the same part today.


This isn't an oversight born of carelessness. It's a measurement gap, and it exists for a structural reason: price leakage is hard to see without the right tooling, so it never becomes a KPI in the first place.


What Price Leakage Actually Is


Price leakage is distinct from the savings leakage that procurement teams do track. Vendor spend analysis research from Varisource describes savings leakage in terms of maverick buying, purchases made outside negotiated contracts that forfeit volume discounts and price protections already secured. That's a real and measurable problem, and it's one procurement KPI dashboards generally do capture.


Price leakage on spare parts is a different, quieter phenomenon. It doesn't require anyone to buy off-contract. It happens even when every purchase order follows the correct process, through the correct supplier, at the price on file. The leakage is in the price itself: a rate that was competitive when it was negotiated but has since drifted out of line with the market, on a part nobody has re-benchmarked since.


Why This Gap Exists in the First Place


Procurement KPI research consistently points to the same root cause: measurement follows visibility, and spare parts pricing is one of the hardest categories to see clearly. A guide to procurement KPIs from Precoro notes that without defined metrics, every procurement initiative produces an outcome you can't verify, you assume it worked or assume it didn't, but you don't actually know.


Realized savings research from Suplari makes a related point that applies directly here: most organizations track savings in spend analysis spreadsheets updated quarterly, if at all, and by the time leakage is identified, it's too late to intervene, the category has already moved on to the next budget cycle. More detail at


Spare parts and MRO categories are especially vulnerable to this blind spot because of how spend is structured. High-value, strategic categories get scrutinized closely because the dollar impact of any single negotiation is large and visible. Spare parts spend, spread thin across tens of thousands of low-unit-cost SKUs, doesn't produce that same urgency line item by line item, even though the aggregate leakage across the full catalogue can be substantial.


Why It's Worth Tracking Anyway


A KPI list from Sievo notes that Kearney's study of 260 companies found price reduction through sourcing and negotiation had a high impact according to 100 percent of the procurement leaders surveyed, underlining just how central pricing is to what procurement is judged on.


If pricing performance genuinely matters that much, it follows that a category where pricing drift goes completely unmeasured deserves the same scrutiny as any strategic category. The absence of a price leakage KPI for spare parts doesn't mean the leakage isn't happening. It means it's happening without anyone knowing the size of it.


What Makes Price Leakage Different to Measure


Unlike contract compliance, which can be checked against a known baseline, price leakage requires an external reference point: what the market is actually charging for a given part right now, across suppliers you may not currently use. That's exactly why it's historically gone untracked. Building that reference point manually, part by part, across a large spare parts catalogue, has never been a realistic use of a procurement team's time.


An SAP guide to procurement cost savings strategies notes that machine learning can now flag anomalies, duplicate invoices, and off-contract purchases automatically, detecting waste and enforcing compliance in ways manual review can't scale to. The same principle applies directly to price leakage detection: it's a category-wide comparison problem that's only practical to solve with automation.


Building Price Leakage Into Your Procurement Dashboard


Adding price leakage as a tracked KPI doesn't require overhauling your existing dashboard. It requires a periodic, systematic spare parts price comparison run against your active catalog, with the output expressed the same way any other KPI is: a number, tracked over time, with a clear baseline.


A practical approach looks like this:

  1. Run a spare parts audit against current market pricing, not historical purchase prices, to establish where each part in your catalog

  2. actually sits relative to what's available.

  3. Quantify the gap in aggregate, not just part by part, so leadership sees a single, trackable leakage figure alongside existing procurement savings metrics.

  4. Re-run the comparison on a regular cadence. Annual reviews, as several procurement KPI guides point out, are too infrequent to catch pricing drift before it compounds.

  5. Feed flagged gaps back to buyers as concrete, actionable items, not a static report that gets filed and forgotten.


The Real Cost of an Untracked KPI


The uncomfortable truth about price leakage is that it doesn't announce itself the way a missed delivery or a contract dispute does. It just sits there, part by part, quietly eroding margin in a category that was never designed to be scrutinized this closely. Procurement teams that add price leakage to their KPI set aren't inventing a new problem. They're finally measuring one that was always there, just previously invisible.


SpareCompare runs a spare parts price comparison against your active catalog, turning price leakage from an invisible cost into a trackable, actionable number.

 
 
 

Kommentarer


bottom of page