WoluTools
Find a tool

Purchasing guide

How to audit a supplier price increase

A useful audit does more than calculate an average. It identifies exactly which items changed, what disappeared and which exceptions need a decision.

From guidance to a reviewable result

Use the method when it fits. Use the tool when repetition begins.

  1. The problemA headline percentage can hide which SKUs changed and which products disappeared.
  2. Concrete exampleKeep the original files, validate the key column and document every exception in one review register.
  3. Matching toolPrice List Compare produces xlsx and csv.
Inspect a supplier-update example

Published by WoluTools · Updated 28 August 2026

1. Preserve the source files

Save the previous approved list and the new supplier list with clear dates. Do not overwrite the old file. The audit should always be reproducible from the original inputs.

2. Confirm the matching key

Use the supplier SKU or another stable item number. Product descriptions alone are not reliable. Check duplicates, blanks and formatting differences before interpreting price changes.

3. Separate every status

A complete report needs at least five groups: increased, decreased, unchanged, new and removed. Looking only at matched increases hides catalogue changes that may affect ordering or availability.

4. Review absolute and percentage changes

A small percentage on a high-volume product may matter more than a large percentage on a rarely purchased item. Keep both the currency difference and percentage change visible. Apply review thresholds only after the raw result is preserved.

5. Check commercial context

  • Did the pack size, unit or currency change?
  • Is a discount now shown separately?
  • Were freight, minimum quantities or payment terms changed?
  • Are new SKUs replacements for removed products?

Price-list comparison cannot answer these commercial questions automatically. It creates the structured exception list that a buyer can investigate.

6. Keep an approval record

Export the reviewed changes, record exceptions and retain the approved output according to your internal policy. The result should show the source dates and the values used for each decision.

Use a consistent comparison structure

The WoluTools example shows the fields used for increase, decrease, new and removed statuses.

Open the example