7 Common Product CSV Import Errors and How to Fix Them

Bulk product imports rarely fail because of a catastrophic catalog failure. In most cases, a platform rejects an entire upload because a single tiny formatting error was repeated across thousands of rows. Whether you are importing an inventory file into Shopify, WooCommerce, Amazon, or a regional marketplace like Trendyol, import parsers enforce strict validation rules.

When a parser encounters an unexpected character, a dropped digit, or a broken tag, it either halts the entire import or silently skips rows. Here are the seven most common product CSV import errors, how to identify them, and how to fix them before uploading.

Free toolTrendyol → ShopifyConverts your Trendyol product export into the Shopify import template: columns are mapped, barcodes and variants stay intact. Free, no signup.Open the tool

1. Missing leading zeros in barcode columns

Barcodes (such as UPC, EAN-13, and GTIN-14) look like numbers, but ecommerce systems treat them as text strings. When you open a raw CSV file directly in Microsoft Excel, the program automatically interprets long numerical strings as numeric values and removes any leading zero.

For example, an EAN barcode like 08501234567890 becomes 8501234567890. When you import this modified file, Shopify or WooCommerce flags the barcode as invalid because a 13-digit EAN only contains 12 digits.

How to fix it:

• Never double-click and save CSV files in Excel without importing them as text.
• When opening files in spreadsheet editors, explicitly format the barcode column as Text rather than Number or General.
• If you need to edit your catalog in spreadsheet software, learn the difference between raw text files and formatted workbooks in our guide on Excel vs CSV for product uploads.

2. Inconsistent decimal and thousand separators

Price columns often contain mixed formatting, particularly if your catalog combines exports from multiple warehouse feeds, ERP systems, or international marketplaces. Continental European formats use commas for decimals (19,90), while standard US and UK formatting uses points (19.90).

If your target platform expects a point and receives a comma, it will either reject the line or strip the punctuation completely, turning a 19.90 price into 1990.

How to fix it:

• Standardize all price columns to a single decimal separator (usually a period) before uploading.
• Remove all thousand separators (such as commas or spaces in 1,250.00) entirely, leaving clean numerical values like 1250.00.
• Remove currency symbols (like $, €, or £) from numerical price columns unless the specific platform template requires them in a dedicated header.

3. Duplicate SKUs and mismatched variant handles

Every product variation must have a unique Stock Keeping Unit (SKU). A common mistake when duplicating rows to create size or color variants is leaving the parent SKU identical across all options.

When an importer encounters a duplicate SKU on a separate line, it usually executes one of two unwanted actions:

1. It overwrites the original item, leaving only the last row in your catalog.
2. It throws a validation error and aborts the entire row, leaving your variant matrix incomplete.

In platforms like Shopify, all variants belonging to the same product must share the exact same Handle and Title, but each option row must carry its own distinct SKU and Option Value.

If you are migrating product feeds between platforms—such as adapting regional marketplace catalogs using Trendyol → Shopify or Trendyol → WooCommerce—ensure that variant structures are mapped correctly to match the target schema.

Free toolTrendyol → ShopifyConverts your Trendyol product export into the Shopify import template: columns are mapped, barcodes and variants stay intact. Free, no signup.Open the tool

4. Missing required fields on inactive rows

Every ecommerce platform mandates a core set of required columns. For Shopify and WooCommerce, this typically includes the product title, handle, SKU, price, and published status. Marketplace templates often require categorical attributes like brand, weight, or tax class.

A common source of rejection is blank cells hiding in discontinued or out-of-stock items at the bottom of your sheet. If an old product row is missing a title or price, the importer marks the row as invalid.

How to fix it:

• Filter your spreadsheet column by column to search for blank cells in required fields.
• Either populate the missing data or delete incomplete placeholder rows before running your bulk import.
• Ensure header names match the platform specification letter-for-letter, including capitalization.

5. Broken HTML tags in product descriptions

Copying descriptions from old web pages, supplier portals, or WYSIWYG editors often pulls hidden styling and unclosed HTML elements into the CSV. An unclosed <div>, broken <span>, or stray inline CSS rule can break the storefront layout on your product pages.

Some strict CSV parsers will fail immediately if a description field contains unescaped quotation marks or raw line breaks that split a single product across multiple spreadsheet rows.

How to fix it:

• Strip non-standard styling and inline style tags from your description column.
• Keep only standard, clean HTML markup (such as <p>, <ul>, <li>, and <strong>).
• Make sure multi-line text fields are properly wrapped in standard CSV text qualifiers (double quotes).

6. Inaccessible or password-protected image URLs

Ecommerce importers do not upload raw image files from your local computer; they read external image URLs from your CSV and download the assets to their own content delivery network (CDN). If the target platform cannot reach the URL during the import process, the product is either created without photos or rejected.

Frequent causes include:

• Image links pointing to a staging site or staging server protected by a login or basic authentication.
• Images hosted on an old store that was shut down before the migration was completed.
• Insecure http:// URLs blocked by modern HTTPS-enforced servers.

How to fix it:

• Test 4 to 5 random image URLs from your spreadsheet in a private browsing window to ensure they load without logging in.
• Keep your source image host active until the entire import and CDN caching process is complete.

7. Character encoding corruption (non-UTF-8 files)

If your catalog contains special characters, accented letters, currency symbols, or non-Latin alphabets, saving your file in an encoding other than UTF-8 (such as Windows-1252 or ANSI) causes character corruption known as mojibake. For example, accents and symbols turn into strings like é or ?.

Corrupted text looks unprofessional to shoppers and breaks storefront search indexing and filtering.

How to fix it:

• Always export and save your CSV files using CSV UTF-8 (Comma delimited).
• If you must edit your data in Excel, perform your data manipulation in standard XLSX format first, then export to UTF-8 CSV as the final step.

How to catch CSV errors automatically in your browser

You do not need to audit thousands of spreadsheet cells by hand. AREM Labs converters and validation tools parse your catalog client-side to detect issues before you upload.

Our converters preserve leading zeros on barcode fields, normalize decimal points, identify duplicate SKUs, clean up messy HTML, and provide a clear summary report detailing every correction made. Because all processing happens directly in your web browser, your catalog data, customer details, and pricing sheets are never uploaded to an external server.

More guides on this topic

This article is part of the E-commerce product files topic cluster. Other guides in the same cluster:

• How to Prepare a Product CSV File: Complete Guide — the pillar guide
• Excel vs CSV: Best File Format for Product Uploads
• Export Trendyol Products to Excel: Step-by-Step Guide

Frequently asked questions

Why does Excel keep removing the leading zero from my barcodes? Excel automatically detects long numerical sequences as standard numbers rather than text strings, dropping the initial zero. To prevent this, format your barcode column as Text or import the CSV using the Data Import Wizard rather than double-clicking the file.

Can I use commas for decimal prices in a Shopify CSV? No. Shopify requires prices in standard decimal notation using a period (e.g., 29.99). Commas should never be used as decimal points or thousand separators in Shopify price fields.

Why did my products import successfully without their images? This happens when the image URLs listed in your CSV are inaccessible to the platform importer. Check that your image links use HTTPS, are publicly accessible without passwords, and remain hosted until the migration is finished.