Compare two product CSV files by SKU or ID
Load an older catalog export and a newer one, choose a stable shared key, and download added products, removed products, and a field-by-field change report.
Choose the original product CSV
Configure the result
Choose the newer export. It stays in this browser.
Preview
From source file to checked output
- 1
Load the original and updated product CSV files.
- 2
Choose a shared SKU, ID, EAN, Handle, or other stable key.
- 3
Review and download added rows, removed rows, and cell-level changes.
Row order is not product identity
Supplier exports and ecommerce platforms reorder rows, add columns, and change stock independently. A line-by-line text diff turns those harmless moves into noise. This tool matches records by one stable identifier, compares only shared columns, and preserves the original values in its downloads.
Use a field that is stable and unique in both files. If one system changes SKUs, map both exports to a shared ID or EAN before comparing.
Audit price and stock changes without a row-order diff
Input
original.csv
sku,price,stock
A-1,10.00,5
B-2,20.00,2
updated.csv
sku,price,stock
A-1,12.00,3
C-3,16.00,7Expected result
changed → A-1 price 10.00 → 12.00
changed → A-1 stock 5 → 3
removed → B-2
added → C-3Boundary: The comparison matches exact key values after the selected normalization. Duplicate or blank keys stop the comparison because they make row identity ambiguous.
Useful before it becomes a workflow
These tools target repetitive catalog and operations tasks. Today each action is free and local. Reusable mappings, batch execution, automation, and APIs will only be built when repeated demand is proven.
Always validate output against the destination system’s current specification. This site is independent and is not certified by a marketplace.
Before you process a file
Which key should I use?
Use a stable unique identifier that exists in both files, such as SKU, product ID, EAN, UPC, or Handle. Names and row numbers are usually poor keys.
What counts as a changed product?
A matched key is changed when at least one shared non-key column has a different value after the selected whitespace and case normalization.
Why does the tool stop on duplicate or blank keys?
One key must identify one product in each file. Continuing with ambiguous keys could attach changes to the wrong product, so the tool reports the rows that must be fixed first.