Compare old and new supplier CSV structure
Compare supplier CSV headers, column positions, blank rates and numeric-to-text changes before reusing a saved mapping.
What should I check when a supplier CSV changes?
Compare column names, positions and simple value profiles before reusing a saved process. Feed Drift reports missing and new columns, moved columns, higher blank rates and columns that changed from entirely numeric-looking values to mixed or text values.
Input requirements and report limits ↓Inputs
Copy a table from Excel or Google Sheets, including its header row, and paste it below. CSV/TSV files also work. Keep the original headings: this check compares column names, positions and blank rates. No column mapping is required.
Free: UTF-8 CSV/TSV · 200 KB / 500 rows per input · 5 successful reviews per browser per day. CSV calculations run locally.
Need larger files or repeat batches? View editions →
Reuse a column profile
A profile stores column names only. It does not store your file contents.
Review report
Before you use this review
| Bring | Previous and latest CSV tables with unique nonempty headers and at least one data row. |
|---|---|
| Match | Exact header text; changed header names appear as missing and new columns. |
| Read the result | Missing/new/moved columns, increased blank rates and numeric-looking columns that became mixed or text. |
| Cannot establish | That a renamed column has the same meaning, that product rows match, or that an import is safe. |
Required inputs
Provide the previous and latest CSV, each with unique nonempty headers and at least one data row. No particular business column names are required. Shared columns are matched by their exact header text, not by position or a guessed meaning.
Interpret the findings
If the previous file has 1 blank in 10 rows and the latest has 3 in 10, the blank rate increased. A moved column can break a position-based process, while a name-based mapping may remain valid. Numeric-looking identifiers can intentionally become text, so a type warning is a prompt for review.
This comparison does not check product identity, source freshness or every data type. No findings is not proof that an import is safe. Use SKU Bridge separately to review explicit supplier-to-store identifiers.
Can I detect renamed columns before importing a supplier CSV?
A renamed header appears as a missing old column and a new column. Feed Drift does not infer that the two columns mean the same thing. Confirm the meaning before changing your saved mapping.
Does this compare prices or match changed product rows?
No. It compares file structure and column profiles. For old and new case prices matched by supplier and SKU, use Pack Audit to compare unit costs. For an existing supplier-to-store cross-reference, use SKU Bridge to review mapping gaps.
Prepared by Supplier Desk Team · Updated . Examples are synthetic.
Who this is for
Small retail and wholesale operations teams reviewing supplier exports before changing catalog, stock or purchasing records. This is a focused review worksheet; it does not connect to your store or post transactions.
Related background
Read the source discussion or documentation. This describes the broader workflow. Use the input requirements and calculation rules above to decide whether this particular check fits your task.
Free tools with optional offline batch editions. Higher file limits, saved batch configurations and grouped report exports. No automatic store changes.