Skip to content

Practical guide

Keep product identifiers intact before a spreadsheet changes them

SKU, UPC, EAN, phone, and postal-code values may look like numbers, but they are often identifiers. Treat them as text, review questionable values, and preserve the source before you generate a barcode or send a CSV elsewhere.

Updated October 24, 2026 · Prepared and reviewed by Got A Tool

Keep the source export before opening or rewriting it

A spreadsheet can interpret a value as a number, date, or formula when you only intended to keep its characters. Save the original export and prepare a reviewed working copy so you can compare a suspect identifier later.

1. Decide which columns are identifiers, not quantities

A quantity can usually be calculated. An identifier needs its exact original characters. Before you open an import in a spreadsheet, mark barcode, SKU, account-like, phone, and postal-code columns as text fields in your process.

  • Leading zeroes can be meaningful, so 001234 is not necessarily the same identifier as 1234.
  • A value such as 1.234E+11 may be a spreadsheet display of an identifier, not evidence that the original contained scientific notation.
  • Do not invent missing digits from a shortened or reformatted value; return to the source export when the exact value matters.

2. Review possible spreadsheet damage before you export again

If a file has already passed through Excel or another spreadsheet, compare suspicious values with the source when possible. A quoted text value or an apostrophe protection can stop a receiving spreadsheet from interpreting a field, but it cannot restore digits that were already lost upstream.

A checksum rule can validate a complete UPC-A or EAN-13 value. It cannot determine the correct original when a spreadsheet has removed or changed characters, so a failed value belongs in review rather than automatic repair.

3. Prepare the reviewed data before you make barcodes or labels

Protect the columns you selected, then validate each barcode value against the appropriate format. Only rows that pass your review should become an image or printed label.

Protect CSV columns

Choose the identifier columns and create an Excel-safe CSV without guessing lost digits.

Protect identifiers

Create one barcode

Validate a single EAN, UPC, or other supported value before downloading an image.

Generate one barcode

Create a label sheet

Review CSV rows and quantities before producing a printable label PDF.

Create label sheets

Check a sample of the final output

Before an import, scan, or print run, compare a few identifiers from the beginning, middle, and end with the source. Keep the original export and the reviewed copy until the receiving system or physical labels have been checked.

Common questions

Does formatting a cell as text restore a leading zero that is already gone?

No. It helps protect future input or export handling, but it cannot reconstruct an original character that has already been removed. Check the source file or system of record.

Can a barcode checksum recover a mistyped code?

No. A checksum can flag many invalid values, but multiple possible changes may produce a valid code. Use it as a validation signal and compare with the source.

Should every numeric-looking column be treated as text?

No. Quantities, prices, and measurements need numeric behaviour. Select only columns whose characters are identifiers and should not be recalculated or reformatted.