Exporting products and combinations to CSV in PrestaShop without import mismatches

Before exporting a catalogue to CSV, decide where the file will be used. Updating prices in the same shop requires a different set of data from moving products to a new installation. Opening the file in a spreadsheet does not prove that it matches the PrestaShop importer.

First decide why you are exporting the catalogue

For a migration, check the target shop version, language, category identifiers and the relationship between products and combinations. For bulk editing, select only the fields you intend to update. A narrower scope is easier to check: a price-update file does not need descriptions or images.

Exporting your catalogue and retrieving supplier data are different tasks. If the source is a wholesaler, start with XML import without duplicates. If you only need to change prices, see updating prices from a CSV file.

Why products and combinations need separate files

The PrestaShop importer distinguishes between Products and Combinations. The first describes the product page; the second describes its variants. A product with sizes and colours therefore requires checking both files and how each combination identifies its parent product.

In the combinations file, pay particular attention to attributes, variant reference, quantity and price impact. The product price and a combination's price impact are not the same field. Confusing them can produce technically valid CSV with an incorrect variant price.

The PrestaShop version changes the available columns

A CSV Export Pro profile lets you select the target importer version. The available fields depend on the PrestaShop version, while the number of columns in a particular file also depends on the export scope. Do not compare the field count for an entire catalogue with that of a profile limited to prices.

Before importing, check the available fields in the target shop and the mapping for every column. A column heading does not replace this check. When moving between versions, also review identifier, stock and availability fields.

The product key: ID, reference or a separate mapping

An ID can be convenient when updating the same database. In another shop, however, the same number may identify a different product. Before migrating, establish an identifier mapping or a reference-based matching method and check uniqueness. Check products and combinations separately.

Do not assume that the product name is a reliable key. Similar names, different languages and variants make this matching difficult. Start with a small test on a shop copy that includes a simple product and a product with combinations.

What to check in the CSV before importing

• Encoding, field separator and multiple-value separator.
• Column count and handling of the header row.
• Product IDs or references and combination relationships.
• The distinction between tax-exclusive price, tax rule and variant price impact.
• Whether empty values should remain empty or change existing data.
• Whether a spreadsheet has altered references or codes with leading zeros.

Do not open an unknown CSV with automatic formula execution enabled. An import file may preserve values beginning with =. Viewing it in a spreadsheet and preparing it for import require a deliberate choice of how the data is read.

Our sample: products and combinations for PrestaShop 9

We prepared a local export using CSV Export Pro 2.0.0 for PrestaShop 9. The products profile used the prices field set: selected fields relating to price, stock and availability. The products file contained 25 columns and 2 data rows. The separate combinations file contained 25 columns and 3 data rows.

Both files used a semicolon separator, UTF-8 BOM and CRLF line endings. This was a sample of export preparation, not a complete import → export → import round trip. It did not test moving an entire catalogue to another shop.

What this export does not replace

CSV Export Pro covers products and combinations. It does not replace a database backup or migration of customers, orders and shop history. Nor is it an importer: reimporting is handled by the standard PrestaShop tool, with its own mapping and limitations.

When to choose CSV Export Pro

If you need separate product and combination files for the built-in PrestaShop importer, see CSV Export Pro: product and combination export to CSV (Polish product page). Before running it on the entire catalogue, establish the importer version, field scope and update key.

Data types and import settings are described in the PrestaShop 1.7 importer documentation. For a newer shop, compare this with the fields available in its back office.