Which encoding for a PrestaShop CSV?

UTF-8 without BOM. Excel saves as UTF-8 with BOM by default, which breaks PrestaShop 1.7 imports. Use LibreOffice Calc or force 'UTF-8 without BOM' via Notepad++.

Can images be included in the CSV?

Yes, via URL. Column 'Image URLs (x,y,z)' comma-separated. PrestaShop downloads images and regenerates sizes. Host images on a fast server.

What is the max size for a PrestaShop CSV?

No hard limit technically, but past 5,000 rows PHP timeout is likely. Split into batches of 2,000, or use the Seegea module for large volumes.

Can the CSV update existing products?

Yes, via ID or Reference (SKU) column. Check 'Force update of existing IDs'. Warning: empty fields in the CSV overwrite existing values on PrestaShop 8/9.

PrestaShop CSV import: format, pitfalls and best practices

CSV remains the most universal PrestaShop import format. Easy to produce from Excel, LibreOffice, or an ERP. But it is also a tricky format: a wrong separator, a broken encoding, a misplaced decimal comma, and 2,000 products import with errors.

This guide gives the exact format expected by PrestaShop 1.7, 8 and 9, common pitfalls, and methods to secure the operation.

CSV compatible with your stack

PrestaShop CSV format: basic rules

Separator: semicolon

; everywhere. If your CSV comes from a Shopify or WooCommerce export with commas, convert before importing to PrestaShop.

Encoding: UTF-8 without BOM

Avoid Excel exports saved as UTF-8 by default: they contain a BOM that breaks PrestaShop 1.7. LibreOffice Calc has a native “no BOM” option.

Decimals: dot, not comma

Prices, weights, taxes: 19.90, not 19,90. French Excel exports with comma by default. Replace before import.

PrestaShop columns: the order that works

PrestaShop does not impose an order: the mapping decides. But a consistent order limits human errors. Proposal:

ID (empty on create, filled on update)
Active
Name
Reference (SKU)
Categories (comma-separated IDs)
Price tax excl.
Tax rate (ID)
Quantity
Weight
Short description
Long description
Meta title
Meta description
Rewritten URL
Image URLs

On PrestaShop 8 and 9, a column present but empty in the CSV overwrites the existing DB value. For partial updates, remove the columns you do not modify — do not leave them empty.

The 7 errors that crash a PrestaShop CSV import

UTF-8 BOM → first field read as ï»¿ID instead of ID
Decimal comma → prices imported wrong, products in error
Category by ID not in the tree → orphan product
Slow image URL → timeout, missing images
Unescaped quotes in description → broken CSV parsing
Duplicate SKU reference → 2 products merged into one
Non-existing tax rate ID → product stuck at 0% VAT

What Seegea does differently on PrestaShop CSV import

Pre-import audit

The Seegea module v3.9.1 reads your CSV, detects the 7 errors above, and suggests auto-fixes. You correct before running the import.

Async import + rollback

The import runs in async batches of 500. If a fatal error hits at 3,000/10,000, full rollback — no half-broken catalog.

Smart partial update

Unlike native CSV, Seegea does not touch fields not passed. You do not lose existing metas or descriptions.

Critère	Shopify natif	Seegea
Pre-import audit	Manual (or none)	Automatic
UTF-8 BOM handling	Silent fail	Detect + fix
Partial update	Overwrites empty fields	Preserves non-passed fields
Max volume	~2,000 rows	50,000+ (async)
Rollback	None	Ctrl+Z + re-push

Secure your next PrestaShop CSV import

Google Meet · we audit your CSV together

Secure your next PrestaShop CSV import

Ready-to-use PrestaShop CSV template

Seegea ships an official 2026 CSV template with the 15 essential columns pre-formatted, UTF-8 without BOM, semicolon separator, and clean example rows for PrestaShop 1.7, 8 and 9. Free download from the Seegea back-office once connected.

Built in France between Annecy and Chantilly, Seegea supports PrestaShop merchants with email and Google Meet from day one.

Created in France (Annecy – Chantilly) · Email & Google Meet support

FAQ

Semicolon (;) is recommended by default. PrestaShop also accepts comma, but semicolon avoids conflicts with descriptions containing commas.