Same records. Different order? No problem.
Match by ID, SKU or a composite key. Reordered rows and columns do not create false changes.
Compare CSV files by key or exact full rows. Add CSV files or .xlsx, .xls and .ods workbooks, match by ID or SKU, and review changed cells, duplicate keys and supplier price moves before the next import.
File handling: Uploaded files are sent to our server for processing. Anonymous comparisons are not saved. If you save a report on Free, encrypted comparison evidence is kept for 7 days. See the privacy details for the proposed Pro plan’s 90-day retention; paid subscriptions are not available. Do not upload sensitive production data to this beta. Privacy details
Server decoding & comparison · CSV / TSV / XLS / XLSX / ODS · 20 MiB per file
Key mode pairs records by one to three selected identifiers. In full-row mode, every mapped cell must match exactly; changed rows appear as a removal and an addition.
Exact column names match automatically. Case-only variations are mapped only when the match is unambiguous; review mappings before comparing.
Key normalization applies to every selected key. Any records that collide after normalization are retained together as conflicts for review. Use SKU formatting only when those characters are insignificant in every selected key column.
Optional unit-cost review divides package price by quantity. Both quantity columns must use the same unit; currencies, measurements and tax are not converted.
Null-like values: empty or whitespace-only text, NULL, undefined, N/A, NA and none, in any letter case. This optional rule applies to values only; match keys remain exact. NaN, zero, false and dash remain distinct.
Add an original and an updated file, review the matching rules, then compare. You will see changed values, new and removed rows, and any keys that need review.
Excel report export supports reports under 8 MiB; use JSON for larger evidence.
Changed-row CSV includes only uniquely matched changed records; additions, removals and conflicts are excluded. Exports require review before use in another system. Optional unit-cost normalization divides package price by a positive quantity on each side; both quantities must use the same unit. No currency, measurement or tax conversion is performed. JSON preserves exact values; CSV neutralizes formula-triggering strings. Excel export includes summary, records, conflicts, schema and rules for reports under 8 MiB.
Built for supplier updates, catalog checks and recurring exports. A clear review before you make a change.
Match by ID, SKU or a composite key. Reordered rows and columns do not create false changes.
Every duplicate and missing key goes into conflicts. No silently chosen winners. No hidden discarded records.
Sort the largest percentage moves to the top, flag zero-price baselines, and optionally compare package prices per unit when pack quantity changes.
Export exact JSON evidence and input fingerprints. An account adds reusable profiles and encrypted saved reports.
A worked example, composite keys, and the duplicate-key trap.
Read the guide ↗FIELD GUIDE / 02Price thresholds, zero baselines, currencies and pack sizes.
Read the guide ↗FIELD GUIDE / 03Match product records across reordered worksheet exports.
Compare workbooks ↗Free beta access is available now. Paid plans are proposed and cannot be purchased.
$0 / month
$12 / month · proposed
Plan pricing is not yet available.
Yes. Parsing and comparison run on the application server, not in browser storage. Anonymous comparisons are not saved to the database. Verified Free accounts can explicitly save encrypted reports for seven days. The proposed Pro retention is 90 days; paid subscriptions are not available. No file contents are sent to AI services.
All affected records are retained in the conflicts section. A duplicate key or normalization collision is never resolved by choosing the first or last occurrence. Choose a composite key when one field is not unique.
Yes. Match renamed columns in the mapping controls and select one to three keys. Row order is ignored. Unmapped columns are listed as schema differences.
Yes. Upload an .xlsx, .xls or .ods workbook alongside CSV or TSV files, the first usable table is selected when an opening tab is empty or title-only, and you can change the worksheet on either side. The selected worksheet uses stored display strings and number formats when available. When both inputs are workbooks, you can also compare all usable worksheets. Sheets pair by exact name first, then by a unique match after normalizing punctuation and spaces or removing year tokens; ambiguous names remain separate. A shared key of one to three identifier columns is used only when it is populated and unique in both sheets; otherwise unique identical values and formulas pair across row order. Edited or duplicate rows use nearest source position, and large unmatched sections use source order. Confirm any suggested key represents stable identity. Choose saved workbook results or formula text; formulas are never recalculated. A formula without a saved result needs formula-text mode. Each workbook is limited to 20 MiB. XLSX and ODS archives may expand to 32 MiB; legacy XLS does not use ZIP compression. .xlsm and PDF files are not supported. CSV/TSV also supports UTF-8, UTF-16 LE/BE, Windows-1252 and Latin-1.
No integrations or automatic writes are included. Downloadable reports are for human review and are not destination-specific import templates.
Paid subscriptions remain disabled. The proposed Pro plan has not launched, and there is no automatic conversion from the free beta.