Configuring PrestaShop Product Import/Export

When transferring a catalog from ERP to PrestaShop, the built-in importer hits PHP limits and cannot handle the volume. For production tasks with a catalog of 5,000+ products, the standard tool requires fine-tuning or replacement with a custom solution using batch processing and memory management. We have 7+ years of experience in PrestaShop integration, delivering over 300 projects. Proper import tuning reduces catalog loading time by 60% and saves up to $600 per month in manual work. A custom module is 10x faster than the built-in importer for large catalogs. Basic configuration starts at $299, custom development from $1,500. Experienced and certified specialists ensure import stability. Let's break down how to properly organize data transfer and avoid common pitfalls. Contact us for a free consultation on your catalog.

Problems solved by proper import setup

Import errors in PrestaShop often arise from mismatched CSV structure, incorrect attribute mapping, or PHP limit violations. Our engineers configure import with awareness of your catalog’s specifics, ensuring stable loading of thousands of products.

Why the standard importer falls short for large catalogs

The built-in importer works well for one-time loads up to 1,000 products. Attempting 10,000+ rows results in timeout or memory exhaustion errors. The culprit is default PHP settings: memory_limit = 128M, max_execution_time = 30 seconds. For large files, you must explicitly increase those limits or switch to batch processing via API, which is significantly faster. For example, in one project the catalog contained 50,000 SKUs with variations. The native importer couldn't even process 10% of the data. We built a custom module with batch loading via API, completing the import in 2 hours — a 5x improvement over standard methods.

CSV structure expected by PrestaShop

The importer expects a fixed set of fields. Delimiter and encoding are configurable at upload:

ID;Active (0/1);Name *;Categories;Price tax excl.;Tax rules ID;Wholesale price;On sale (0/1);Discount amount;Discount percent;Discount from;Discount to;Reference #;Supplier reference #;Supplier;Brand;EAN13;UPC;MPN;Ecotax;Weight;Quantity;Description;Short description;Tags (x,y,z...);Meta title;Meta description;URL rewritten;Image URLs (comma-separated absolute URLs);Image alt texts;Feature (Name:Value:Position:Customized);Available for order;Available date;Show price;Visibility;Additional shipping cost;Unity;Unit price;Summary;Shop (for multi-shop only) ;1;Men's winter jacket;Outerwear,Men's clothing;2999.00;1;0;0;0;0;;;ART-001;;Brand;JacketBrand;4607167430120;;;0;1.5;50;"Full jacket description...";"Winter jacket";"jacket, winter, men's";"Buy men's winter jacket";"Men's winter jacket – buy";"men-s-winter-jacket";;"Jacket view 1,Jacket view 2";"Color:Black:1:0;Size:L:2:0";1;;;1;everywhere;0;;; 

Note: Image URLs must be absolute and accessible; we recommend using a CDN. The example row omits URLs for brevity.

Configuration for bulk import

By default, the PHP import process hits memory_limit and max_execution_time. For files over 10,000 rows, we recommend increasing limits via a controller override or a dedicated PHP-FPM pool:

// override/controllers/admin/AdminImportController.php class AdminImportControllerCore extends AdminImportController { public function __construct() { parent::__construct(); @ini_set('memory_limit', '512M'); @ini_set('max_execution_time', '3600'); } const MAX_LINE_SIZE = 4096; } 

We recommend raising limits through a dedicated PHP-FPM pool: memory_limit to 1G, max_execution_time to 7200.

Recommended PHP limits by catalog size

Programmatic import via ObjectModel and WebService API

For ERP/1C integration, bypass the web importer and work directly via the PrestaShop API. PrestaShop WebService provides a REST API for export:

$client = new PrestaShopWebservice($shopUrl, 'YOUR_API_KEY', false); $params = [ 'resource' => 'products', 'display' => '[id,reference,name,price,quantity]', 'sort' => '[id_ASC]', 'limit' => '100,100', ]; $xml = $client->get($params); $products = $xml->products->product; 

Import a product with attributes via ObjectModel:

class ProductImporter { private int $defaultLangId; private int $shopId; public function importProduct(array $data): int { $product = new Product(); $product->name[$this->defaultLangId] = $data['name']; $product->description[$this->defaultLangId] = $data['description']; $product->reference = $data['sku']; $product->price = (float) $data['price']; $product->weight = (float) ($data['weight'] ?? 0); $product->active = 1; $product->id_category_default = $data['category_id']; if (!$product->add()) { throw new \RuntimeException('Failed to add product: ' . $data['sku']); } $product->addToCategories($data['category_ids']); StockAvailable::setQuantity($product->id, 0, (int) $data['qty']); Search::indexation(false, $product->id); return (int) $product->id; } } 

When to choose a custom module

A custom module is better for catalogs requiring frequent synchronization and complex update logic. Order PrestaShop import configuration from our team.

4-step configuration of PrestaShop product import

1. Data preparation — convert CSV to the required format, check UTF-8 encoding and delimiter.
2. PHP configuration — increase memory_limit and max_execution_time according to catalog size.
3. Test import — load 100–200 records on a copy of the database, verify field mapping and attributes.
4. Automation — set up cron for regular sync runs, log errors via PrestaShopLogger.

Setting up import module for cron

For regular catalog updates from an external source:

// modules/erpimport/cron.php define('_PS_ADMIN_DIR_', getcwd()); include(dirname(__FILE__) . '/../../config/config.inc.php'); $importer = new ErpProductImporter(); $products = $importer->fetchFromErp(strtotime('-1 hour')); foreach (array_chunk($products, 100) as $batch) { foreach ($batch as $productData) { try { $importer->upsert($productData); } catch (Exception $e) { PrestaShopLogger::addLog('ERP import error: ' . $e->getMessage(), 3, null, 'Product', $productData['id'] ?? 0); } } usleep(100000); } 

Cron entry: */30 * * * * www-data php /var/www/prestashop/modules/erpimport/cron.php >> /var/log/prestashop/erp-import.log 2>&1

What is included in the work

The work includes: documentation of field mapping and import run instructions; access setup with API key creation for WebService and cron permissions; training on test file upload and common error handling; technical support with bug fixes within 5 business days after delivery.

Estimated timelines

• Built-in importer configuration + test import: 4–8 hours
• Custom importer development with ERP integration: 3–7 days
• Regular sync setup with error monitoring: 2–3 days
• Catalog migration of 10,000+ SKUs with images: 3–7 days

Cost is calculated individually after assessing the data volume and integration complexity. Submit a request — our engineers will analyze your catalog and propose the optimal solution. Get a consultation on PrestaShop product import today.