Barcodes shown as 1.23E+12 in a CSV: find and fix

You open a product CSV and the barcode column shows values like 1.23E+12 instead of a full number such as 4006381333931. Different barcodes can look almost identical.

To spot it, scan the barcode column for the letter E followed by a plus sign and digits, and compare each value with the format you expect: EAN-8 has 8 digits, UPC-A has 12, EAN-13 has 13 (and GTIN-14 has 14). Do not expect one length for the whole column; a value in E form is a warning sign in any of them. Not verified: whether the file on disk is already damaged or only the on-screen view is affected.

The cause, in plain terms. Spreadsheet programs often treat a long run of digits as a number to calculate with, not as a label. To fit it in a narrow column, they may show it in scientific notation, the E form. A barcode is a label, not a quantity, so number treatment is wrong for this column. Not verified: whether the full digits survive after saving in this state; do not assume they do.

Steps to fix. 1. Work from the original export or source list, not from a file already saved with E values. 2. Open a blank sheet and set the barcode column to text format before any data goes in. 3. Paste or import the data into that column so it is read as text. Not verified: whether pasting or importing into a text-formatted column keeps every digit in every program. 4. Check each barcode against the format you expect (8, 12, 13 or 14 digits). 5. Save as CSV. 6. Verify in the saved file: open it in a plain text editor and read the raw barcode values. Not verified: whether a CSV saved this way can turn back into E form when reopened in a spreadsheet; treat the text editor view, not the spreadsheet view, as the check.

If the only copy was already saved with E values, the missing digits may not be recoverable from that file. Get the codes again from where they came from, such as the supplier list or your product records. Not verified: the exact menu names and clicks for setting a column to text; they differ between programs, so use your program's own help.

For codes that lose leading zeros, see the post "Why SKUs lose leading zeros in CSV files". This post does not repeat it.

Re-check with the free CSV check before you use the file anywhere. In a local test with a synthetic file, the check flagged values like 1.23E+12 in the barcode column as "Barcode has the wrong number of digits"; it does not name scientific notation as the cause, and it looks at the first 20 data rows only. It also flags a barcode whose check digit does not add up. Select the corrected file on the page (it stays in your browser), read the report, fix what it lists and run it again. The questions and answers on the free check page explain what it looks at. If the report shows nothing for this column, still confirm the digits in the text editor.