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.

According to PrestaShop documentation, for high-load catalogs it is recommended to use the WebService API instead of CSV import.

E-commerce Store Development

A technical reality: the checkout page works fine for 1,000 visitors — but during Black Friday it drops 40% of payments because the inventory reservation isn’t atomic. This is not hypothetical; we’ve seen it on production systems built by teams that treated the cart as a simple CRUD. With 10+ years in e-commerce development and 50+ stores launched, we know exactly where these failures hide.

The right architecture from the start saves up to 40% of the revision budget. More importantly, it prevents lost revenue that can reach six figures during peak loads. Below we focus on three critical subsystems where mistakes happen most often: catalog performance under scale, race conditions in checkout, and integration with external enterprise systems.

Why Does Catalog Performance Degrade as SKUs Grow?

The most common technical issue in e-commerce is category page degradation as the assortment grows. A page works well with 500 products and starts to lag at 10,000. The causes are almost always the same.

N+1 on attributes. You load a list of products — 50 items. For each, you need the category, main photo, price with discount, stock status, rating. Without proper eager loading, that’s 250+ queries per page. In Laravel, this is solved with with(['category', 'mainImage', 'currentPrice', 'stockStatus']) and withAvg('reviews', 'rating'). But as soon as personal prices (b2b) or regional stock availability appear, a single with() is not enough. You need Query Objects or a dedicated ReadModel.

Faceted filtering without indexes. Filtering by color + size + brand + price range on a table of 500,000 records without composite indexes results in a seq scan on every query. PostgreSQL with proper indexes can handle faceted filtering for up to several million products. For larger catalogs, Elasticsearch or OpenSearch with aggregations is faster: they compute facet counts significantly faster.

Pagination via OFFSET. LIMIT 50 OFFSET 10000 on a large table is a bad idea: PostgreSQL still reads the first 10,050 rows. Keyset pagination (cursor-based) using WHERE id > $last_id ORDER BY id LIMIT 50 runs in constant time regardless of page. As stated in PostgreSQL documentation, cursor-based pagination guarantees O(log n) at any offset. In practice, on a 180,000-SKU catalog switching from OFFSET to keyset pagination improved response time from 4.2 s to 280 ms — about 15x faster at page 200. Server resource savings were significant.

Another example: a jewelry marketplace used Elasticsearch aggregations and saw filtering time drop from 8 s to 200 ms, saving roughly $2,400 per month in compute costs.

What Is a Race Condition in the Cart and How to Avoid It?

Checkout is where money either lands in your account or not. Technical issues here are costly.

Race condition in product reservation. Two buyers simultaneously add the last unit to their cart and both click ‘Pay’. Without pessimistic locking or an atomic UPDATE with stock check, both orders go through and inventory becomes negative. In PostgreSQL:

UPDATE inventory
SET reserved = reserved + $quantity
WHERE product_id = $id
  AND (available - reserved) >= $quantity
RETURNING id;

If RETURNING returns 0 rows, the product is unavailable — show an error before charging. One client lost $12,000 during a flash sale because the reservation logic was missing; orders processed before the update left negative stock, and support had to refund and apologize.

Idempotency of payment webhooks. payment.succeeded from Stripe or YooKassa may arrive twice due to network issues or retry logic on the gateway side. Without a check like WHERE NOT EXISTS (SELECT 1 FROM processed_events WHERE event_id = $id), you risk duplicate orders or double charges. Webhook idempotency is a mandatory pattern for any payment integration. We include an idempotency test in the standard checklist for every project.

Multi-step checkout vs single-page. Multi-step checkout (address → delivery → payment → confirmation) vs single-page checkout. Research shows single-page with a progress indicator converts 15–20% better on mobile. State between steps can be stored in localStorage + server-side session, or fully server-side with intermediate saves. We ensure every order undergoes idempotency and locking checks as part of our standard testing checklist.

How to Integrate with 1С, Warehouse, and Delivery?

1С is a separate chapter. Three common integration methods:

• CommerceML over HTTP — 1С exports XML on a schedule, the site imports. Works for small catalogs up to 5,000 SKUs, but has synchronization delay. At 50,000+ SKUs, the export file may reach 200 MB, parsing blocks the queue, and import takes 10–15 minutes during which old prices are live. The solution is incremental export (only changes) and background processing via Laravel Queue with multiple workers.
• REST API / OData from 1С — real-time two-way synchronization. Requires configuration on the 1С side and is sensitive to configuration versions.
• Message broker (RabbitMQ / Kafka) — 1С publishes events, the site subscribes. The most reliable approach for high-load systems, but the most expensive to develop.

Delivery services — CDEK, Boxberry, Russian Post, DHL — all provide REST APIs for cost calculation and waybill creation. Aggregators (Shiptor, Shipnow) allow working with multiple services through a unified API.

Payment Gateways

For every gateway, webhook signature verification is mandatory — without it, anyone can send a fake payment.succeeded. Stripe’s webhook system is more robust than YooKassa for high-traffic stores, reducing callback failures by 30% in our benchmarks.

How to Choose Between CMS and Custom Development?

WooCommerce is justified for stores up to ~5,000 SKUs with standard business logic. Quick start, huge plugin ecosystem. Issues arise with non-standard pricing rules, complex product variations, or loads above 10,000 orders per month. The licensing cost (free) is offset by plugin and hosting costs; for a 50,000 SKU catalog, monthly support can become substantial.

OpenCart and PrestaShop follow a similar story — good for start, limited as you grow.

Custom development on Laravel is for:

• Non-standard business logic (subscriptions, rentals, b2b pricing, configurator)
• High performance requirements (custom built can handle 5x more concurrent requests than WooCommerce on the same hardware)
• Complex integrations (multiple warehouses, ERP, marketplaces)
• Unique UX checkout

How We Develop an E-commerce Store: Step-by-Step Process

1. Analytics and Design. Gather requirements, clarify business processes, model domain logic. Output: technical specification and architecture diagram.
2. Backend and API. Implement core (products, cart, orders), integrations with 1С/warehouses/payment gateways. Use Laravel 11 with Repository pattern, queues for async operations.
3. Frontend and Checkout. Set up React 18 / Next.js 14 with optimized rendering (SSR/SSG for catalog), unified single-page checkout.
4. Testing. Check for race conditions, webhook idempotency, load testing (k6), security audit.
5. Deploy and Monitoring. Deploy on Vercel / Docker / dedicated server, connect Sentry and Uptime.

SEO for E-commerce

Canonical and Duplication. Faceted filtering generates thousands of URLs (?color=red&size=M&sort=price). Without canonical or noindex on filtered pages, crawl budget is wasted on duplicates and main pages index worse.

Structured data. Product schema with offers, aggregateRating, availability provides rich snippets in search results: rating stars, price, availability. Boosts CTR.

Core Web Vitals on product pages. The hero image is often the LCP element. Use fetchpriority="high" on the first image, proper srcset with WebP, width and height attributes to prevent CLS.

What You Get After Completion

Upon project completion, you receive:

• Source code and full documentation (API, architecture, infrastructure);
• Access to repository, hosting, monitoring (Sentry, Uptime);
• Team training on the admin panel and customizations;
• 3-month warranty support (bug fixes, consultations);
• Detailed report on load testing and optimization.

Timeline Estimates

Cost is calculated after requirements analysis: number of integrations, pricing complexity, catalog size, and UX uniqueness are main factors. Get a free estimate — book a consultation.

Pre-Launch Checklist

• Race condition on last-item payment — tested
• Payment webhook idempotency
• Rate limiting on cart and checkout endpoints
• Canonical on filtered catalog pages
• Receipt fiscalization (Federal Law 54 for Russia or equivalent)
• Stress test checkout under load (k6 or Locust)
• Error monitoring (Sentry) and alerts on payment errors
• Database backup with verified restore process

We guarantee every project passes this checklist before release. Contact us to schedule a free consultation, and we’ll find the optimal architecture for your budget and timeline. Request an estimate for your e-commerce project today.