Convert Scientific Notation Back to Full Numbers in Your CSV

Why Excel turns 12-digit numbers into E+11

A CSV file is plain text — it has no way to tell Excel "this column holds barcodes, not quantities." So when you double-click a CSV, Excel parses every cell and guesses its type. Any run of 12 or more digits is treated as a number, and under the default General format Excel displays large numbers in scientific notation: the UPC 885909457123 appears as 8.85909E+11. Almost every product identifier in circulation qualifies — UPC-A is 12 digits, EAN-13 is 13, GTIN-14 and case-level ITF-14 codes are 14, and plenty of account numbers, booking references, and carrier tracking numbers run longer still.

The display alone is harmless; the damage happens on save. Hit File → Save while the CSV is open and Excel writes what the General format shows, so the literal text 8.85909E+11 lands in the file. Your feed processor no longer sees a barcode — it sees a string containing a letter and a plus sign, and it rejects the row.

The 15-digit rule: what is recoverable, honestly

Two separate things go wrong, and only one of them is fully repairable:

• Truncation on open. Excel stores numbers as double-precision floats, which hold at most 15 significant digits. A 16-digit value such as 1234567890123457 becomes 1234567890123450 the instant Excel parses it. Those trailing digits are gone before you touch anything.
• Rounding on save. When Excel writes a General-formatted cell to CSV, it writes the on-screen form — often just six significant digits of mantissa. 885909457123 can leave the building as 8.85909E+11, carrying six real digits and losing six.

Here is exactly what that means for your data:

Every digit present in the saved mantissa is restored exactly. The zeros this tool pads with are only correct if the original digits in those positions were zeros. One useful tell: GTINs carry a check digit, so a wrongly padded barcode will usually fail check-digit validation at Amazon or Google — if a handful of rows still bounce after repair, those are the ones to re-export from your product catalog.

How this tool expands the notation

The repair engine never converts your values to floating point, so it cannot introduce new rounding errors. It treats 8.85909E+11 as pure text: it takes the mantissa digits (885909), reads the exponent (11), shifts the decimal point that many places, and pads with zeros — exact string math from start to finish. A long mantissa like 1.23456789012E+12 expands to 1234567890120 with all twelve stored digits intact. Click Analyze my CSV above and the tool lists every affected column; you choose which ones to expand, so a genuine scientific measurement column in a lab export can be left alone while the barcode column gets fixed.

Prevent it next time: import as Text

First, the thing that doesn't work: selecting the column and choosing Format Cells → Text after the file is already open. By then Excel has parsed the digits into a float — reformatting only changes how that damaged number is displayed. The Text type has to be applied before the data enters the cells:

1. Do not double-click the CSV. Open Excel with a blank workbook first.
2. Go to Data → From Text/CSV and select your file.
3. In the preview window, click Transform Data.
4. In the Power Query editor, select the barcode or ID column, set Data Type → Text, and pick Replace current when prompted.
5. Click Close & Load. The digits arrive as text and scientific notation never appears.

On older Excel versions, Data → Get External Data → From Text opens the classic Text Import Wizard: in step 3, click the ID column and set Column data format to Text. Either way, keep an untouched copy of the original export — and if you must edit, save your working file as .xlsx and only generate the CSV as the final step.

Who runs into this

Anyone whose CSV passes through Excel on the way to a marketplace. Amazon Seller Central flat-file uploads fail with "external_product_id is invalid" when the UPC field contains E-notation. Google Merchant Center disapproves items with "Invalid value [gtin]." Shopify's product importer stores whatever is in the barcode column verbatim, so 8.85909E+11 quietly becomes your live barcode. Beyond e-commerce: logistics teams with container and booking references, and finance teams with long account identifiers hit the same wall.

For the full background — including screenshots of the import flow — read our guide, why Excel converts CSV numbers to scientific notation, or browse all guides. And if Excel mangled more than the numbers: it also loves deleting the zeros from ZIP codes (our leading-zeros repair tool puts them back) and garbling accents into é sequences (fixed by the broken-characters tool).

Frequently asked questions