How the damage happens
When a spreadsheet opens a CSV, it may infer that a column containing digits is numeric. A value such as 001234567890 can display without its leading zeros, and a long identifier can appear as 1.23457E+11. If the workbook then saves that inferred value, the original identifier may no longer exist in the file.
Shopify defines the Barcode field as the variant’s barcode, ISBN, or UPC. Treat the contents as exact text. See the official product CSV column reference.
Preserve barcodes while editing
- Keep the untouched Shopify export as the reference copy.
- Import the CSV through your spreadsheet application’s text/CSV import flow instead of opening it by double-click.
- Set the Barcode and SKU columns to text before loading the data.
- After saving, inspect several raw values in a text editor—especially values that begin with zero or contain many digits.
- Compare the saved file against the untouched export and stop on any lost zero, exponential notation, or unexpected identifier change.
If the spreadsheet has already discarded digits, restore the exact value from the original export or another authoritative source.
What a preflight can detect
A two-file comparison can catch a leading zero present in the original but missing in the edited file. It can also reject values written in exponential notation. It cannot reconstruct digits that were already lost before the original reference file was saved.
Compare identifiers as exact text
ImportProof flags spreadsheet-damaged barcodes and unintended SKU changes before you touch the live catalog.
Check two CSVs