Does row order matter?
Key matching and exact full-row matching ignore row order. Whole-workbook overview pairs rows by a shared key of one to three identifier columns only when it is populated and unique in both sheets; otherwise unique identical values and formulas pair across order, while edited or duplicate rows use nearest source position. Large unmatched sections use source order. Confirm a suggested key identifies stable records; ambiguous fallback matches can still show moved rows as changes.
What if my key is duplicated or blank?
All affected records remain visible as conflicts. Use a stable composite key when one field does not identify a record. Normalizing keys can create collisions; those remain conflicts too.
Are formulas recalculated?
No. Whole-workbook comparison reports saved cell-result changes and formula-expression changes separately. Selected-worksheet comparison uses saved values by default; formula-text mode compares formulas instead. Formulas are never calculated, and saved values can be stale or missing.
Where are my files processed?
On the application server. Anonymous comparisons are not saved to the database. Saving a report stores encrypted comparison evidence, including original cell values. See privacy and retention details.
Can I use the CSV as an import file?
Reports are evidence for review, not destination-specific ERP or store import templates. CSV exports neutralize formula-like text for spreadsheet safety. Use JSON when exact source strings matter.
What does a subscription change?
Pro is a proposed plan and cannot currently be purchased. It would increase saved-rule and saved-report allowances and retention for new reports. It does not add batch jobs, scheduling or team access. See current plans and availability.
Can you help with a failed comparison?
Use support. Include the file format, approximate row count, chosen matching mode and visible error. Start with a redacted example rather than sending confidential business records.