When an inventory export changes, a row’s position is not a reliable signal. A product can move because the file was sorted differently, while a quantity can change without the SKU moving at all. Compare records by SKU, then review the differences before changing another system.
This is a file-to-file workflow. It does not connect to an ERP, reserve stock, or decide which quantity is correct.
Start with comparable snapshots
Keep both exports and label their dates. Confirm that they use the same warehouse, product status, unit of measure, and reporting filters. If one export excludes discontinued products or uses a different stock location, a missing row may be expected.
Treat SKU as text when leading zeroes matter. Check for blank or repeated SKUs before comparing. If a supplier or system uses one SKU for multiple variants, use a more specific composite key, such as SKU plus location or variant code.
Match by SKU, not row number
For a short table, a COUNTIF or lookup formula can check whether each SKU appears in the other export. Run the check in both directions: Before-to-After identifies records absent from the newer file, and After-to-Before identifies new SKUs. For a repeated workflow, Power Query’s merge operation supports different join types, including a full outer join that includes rows from both inputs. Microsoft explains the join options here.
After matching records, compare the fields that matter: on-hand quantity, unit cost, status, or location. Keep the result separate from the source export so a reviewer can inspect it before updating stock records.
Fictional SKU example
| SKU | Before quantity | After quantity | Review |
|---|---|---|---|
| A-104 | 12 | 10 | Changed: quantity decreased by 2 |
| B-210 | 30 | 30 | No reviewed change |
| C-019 | 22 | — | Missing from After; check filters or status |
| D-006 | — | 15 | New in After; confirm product setup |
This example is fictional and only demonstrates the comparison. It does not describe a real warehouse, seller, or customer result.
Do not confuse file differences with stock truth
A comparison reports what differs between two files. It cannot tell whether the physical shelf matches the export, whether a shipment arrived after the report was generated, or whether a missing item was filtered out. Check the export timestamp and source rules before making an adjustment.
For a handful of SKUs, Excel formulas may be fastest. For a recurring process, Power Query can save the steps. Both still require someone to validate the key and decide what action is appropriate.
Where Change Check fits
Change Check compares two CSV or XLSX files by an identifier you choose. A SKU can be that identifier when it uniquely represents the record in both files. The app groups evidence as Changed, Missing, or New and can export a separate report. The current release supports up to 10,000 data rows per selected sheet.
Change Check does not import the result into an ERP, synchronize live inventory, resolve duplicate SKUs, or decide which stock number is authoritative. Your original files remain unchanged.
See Change Check for supported file types and product details. If you need a longer comparison walkthrough, continue with the spreadsheet export comparison guide.
Frequently asked questions
Can I compare two inventory files with a different row order?
Yes. Match the rows on a stable SKU or composite key instead of row position.
Does a missing SKU mean it was deleted?
Not necessarily. Check dates, locations, filters, product status, and export rules before treating a one-sided row as a deletion.
Does Change Check connect to my ERP or inventory system?
No. It compares files you select; it is not an ERP integration or live stock system.
What if one SKU appears more than once?
First determine why the key repeats. Add another field to make the key unique or group the records deliberately. Do not rely on a first-match lookup for duplicate keys.