FIELD NOTES
Read a change report before you update anything.
A difference report describes the exports. It does not decide which version is correct.
Before importing an updated catalog, use the comparison as a review step. The tool does not connect to your store, rewrite a file or decide whether a new price or stock value is intended.
Records and changed values are different counts
A record whose product name, price and stock all change counts as one changed record and three changed values. The on-screen summary counts records; the report has one line per changed field. A longer CSV report does not necessarily mean more products changed.
Read each status in the right direction
- Added: the chosen key exists only in the latest export.
- Missing: the key exists only in the previous export.
- Changed: the key exists in both files and one or more selected fields differ.
- Unchanged: the key exists in both and all selected comparison fields match.
Unselected columns are outside the conclusion. If you compare only stock, a price-only change leaves that record unchanged in this comparison.
Inspect export scope before drawing conclusions
Hundreds of missing records can result from a narrower export filter. Check warehouse, product status, category and time filters before treating missing records as deletions. Also confirm that previous and latest files are in the correct slots.
Columns present in only one file are listed but not compared. A renamed header is not automatically mapped. Align the column names in a working copy when you know they mean the same thing.
Understand row references
The report's previous and latest row references count data records from 1 after the header, not physical text lines. A quoted description may contain line breaks inside one record. Parse errors instead report source line numbers to help locate malformed text.
CSV quoting is described by RFC 4180. Our pilot also accepts explicitly selected semicolon, tab and pipe separators. It requires headers, unique column names and consistent field counts.
Pick a report format
The CSV report is convenient for review, with status, key components, row references, field names and before/after values. Added and missing records carry JSON-formatted full-row values in the final columns. Filters and search on the page do not reduce the download.
The exact JSON report includes comparison rules, selected fields, summary counts and changes. Use it when you need exact parsed strings rather than spreadsheet-oriented prefixes.
Formula-like values receive an apostrophe prefix in the CSV download. This helps reduce accidental evaluation but is not reliable for every spreadsheet or save-and-reopen workflow. OWASP explains CSV injection and the trade-offs. Do not enable formulas or external links in untrusted data.
Make a final spot-check
Check at least one added record, one missing record and one changed value against both original exports. Confirm the comparison rules, then decide separately how to update your source system. A report showing no changes is useful only when the keys, scope and selected fields match the task you intended.