AmazonSKUs & IDsImport blocker
Barcode mangled by a spreadsheet
A product-id looks like 1.23457E+11: a spreadsheet converted the barcode to scientific notation.
What is this issue?
A product-id looks like 1.23457E+11: a spreadsheet converted the barcode to scientific notation.
Affected field:
Barcode mangled by a spreadsheetImport blocker: your file will fail to import until this is resolved.
Upload your CSV to check for this issue and export a clean file.
Fix nowWhy Amazon rejects this
The digits after the first few are lost, so Amazon cannot match the product.
Fix in StriveFormats
Upload your CSV to StriveFormats to detect this issue across all rows, with clear line-by-line reporting.
Fix in Excel
- 1Review the Barcode mangled by a spreadsheet column for incorrect values.
- 2Fix any cells that do not match the expected format.
- 3Save as CSV (Comma delimited).
Fix in Google Sheets
- 1Review the Barcode mangled by a spreadsheet column for incorrect values.
- 2Correct any cells that do not match the expected format.
- 3Go to File > Download > Comma Separated Values (.csv).
Prevent it next time
- ✓Start from the official platform template to avoid structural issues.
- ✓Run your file through StriveFormats before every import.
- ✓Test with a small sample file first to catch errors before they affect your full catalog.
How StriveFormats detects this
StriveFormats parses every row of your CSV and applies Amazon-specific validation rules to the Barcode mangled by a spreadsheet field. Any row that violates the rule is flagged with the row number and the specific value that caused the issue.
►Technical detail
Amazon's importer validates the Barcode mangled by a spreadsheet field against its official import specification. Values that do not meet the expected format are flagged to prevent silent data corruption -- an invalid value that slips through import might appear as a blank field, a zero, or incorrect text in your storefront without any error message after the fact.