Keep the source CSV unchanged
Make a reviewed copy for Excel or an import. Keep the original until you have checked the result. This gives you a clean place to return to if a column is parsed unexpectedly.
1. Identify columns that Excel should treat as text
SKUs, barcode values, phone numbers, postal codes, and account identifiers can begin with zero or look like scientific notation. They are identifiers, not calculations. Review only the columns you know need protection rather than changing every cell automatically.
Use the right tool for identifier columns
CSV Barcode & Leading Zero Protector lets you select barcode, SKU, phone, and postal-code columns. It keeps questionable values for review instead of inventing missing digits.
2. Check the file structure before the spreadsheet opens it
A comma inside a quoted name, a mismatched quote, or the wrong delimiter can shift every later column. A clean-looking file can still have a bad row that changes how an import reads it.
Columns do not line up
Review the file with CSV Repair & Dialect Normalizer. Verified rows and rows that need review are kept separately, with the original row text and reason.
Review CSV rowsYou need a different format
Use CSV ↔ JSON Converter when the next system needs structured JSON. Review nested values and spreadsheet-formula protection before downloading.
Convert CSV and JSON3. Treat formula-like cells as review items
Values beginning with =, +, -, @, a tab, or a carriage return can be interpreted differently by spreadsheet software. Do not assume a value is harmless just because it appears in a CSV. Use an Excel-safe export when you are preparing a file for someone else to open.
- Check the first and last record after opening the reviewed copy.
- Compare an identifier with its source value, including leading zeros.
- If a row was quarantined, review it before adding it back by hand.
A clean export is not a guarantee about its next destination
Import rules vary by spreadsheet, marketplace, CRM, and database. Check the destination's column requirements and open the final copy before you send or import it.
Common questions
Can a CSV store a leading zero?
Yes. A CSV stores text. The risk appears when an application interprets the value as a number. Keep a reviewed CSV copy and check the identifier after opening it.
Should I repair every CSV before opening it?
No. Use repair when column counts, quotes, or delimiters look inconsistent. For an ordinary well-formed CSV, inspect the columns that contain identifiers or formula-like values.
Does this guide replace import documentation?
No. It helps you prepare a safer source file. Always follow the current requirements of the system receiving the import.