PrestaShop Product Management: Connect with MicroPIM

PrestaShop powers more than 300,000 live stores worldwide — many of them operating across multiple storefronts, languages, and markets from a single installation. That multi-store architecture is one of PrestaShop’s most compelling strengths, and also one of its most demanding product management challenges. When the same product needs to be active on four storefronts with localized descriptions, different pricing tiers, and separate inventory tracking, native PrestaShop tools start showing their limits quickly.

This guide covers the complete PrestaShop product import integration with MicroPIM: obtaining webservice API credentials, connecting your stores, mapping PrestaShop-specific fields including combinations and manufacturers, targeting individual storefronts during multi-store sync, and automating daily product updates on a cron schedule. By the end, you will have a repeatable, automated product data flow that keeps every PrestaShop storefront accurate without manual CSV work.

PrestaShop’s Multi-Store Complexity

PrestaShop’s multi-store feature — called the Multi-Shop framework — allows a single PrestaShop installation to run multiple storefronts, each with its own domain, theme, product selection, and pricing. From a technical perspective this is well-architected. From a product management perspective, it multiplies your workload by the number of stores you operate.

Consider a merchant running three storefronts: a primary national store, a regional discount outlet, and a B2B wholesale storefront. A new product needs to be created in all three. The B2B store uses different pricing. The outlet store suppresses the product until clearance stock is available. Each store has its own language settings. In PrestaShop’s native admin, this means logging into the back office, selecting the appropriate shop context for each configuration, and manually ensuring every field is correct across every shop group and individual shop.

The burden compounds as the catalog grows. Product updates, new combination variants, manufacturer reassignments, and stock adjustments all require navigating the multi-store context tree in the PrestaShop admin. Teams running large catalogs across multiple PrestaShop storefronts routinely discover inconsistencies — a price updated in the main store that never propagated to the outlet, a combination that exists in one shop context but not another, a manufacturer link that is missing on the B2B storefront.

The underlying architecture is not the problem. PrestaShop’s multi-store model is powerful. The problem is the operational overhead of managing product data at that level of granularity through a single-item admin interface.

Why PrestaShop Merchants Need Robust Data Import

PrestaShop provides two native paths for bulk product data management: CSV import via the native importer and direct admin editing. Both paths have limitations that become operational problems at scale.

The CSV importer has no merge logic. When you import a CSV into PrestaShop, every row in the file rewrites the corresponding product record. If your CSV omits a column — because your source data does not include every PrestaShop field — the importer either skips that field or blanks it out depending on the configuration. There is no concept of “update only the fields that changed.” Every import is a full replacement of the product data that appears in the file.

Multi-store CSV handling is incomplete. PrestaShop’s CSV importer operates in a single shop context at a time. Importing to three storefronts means running three separate imports, managing three files, and verifying three sets of results. There is no native bulk product import path that writes to multiple storefronts simultaneously from a single source.

Combination management does not scale. PrestaShop’s product combinations — the equivalent of WooCommerce variable product variants — require individual creation or CSV import for each combination. A product with 30 combinations across three stores means 90 combination records to maintain. Bulk-editing combination-level pricing, stock, or reference codes is cumbersome in the native admin.

No structured external integration. PrestaShop exposes a webservice API that third-party tools can use to read and write product data, but it has no native mechanism to receive structured, recurring product data from a PIM, an ERP, or a supplier data feed. Every external integration has to be built and maintained as a custom implementation.

A dedicated PIM connected to PrestaShop via the webservice API solves all of these problems at once. MicroPIM manages the product model centrally and distributes data to each PrestaShop storefront according to rules you configure — once.

MicroPIM PrestaShop Integration Benefits

The MicroPIM PrestaShop connector uses PrestaShop’s XML webservice API as its transport layer. MicroPIM authenticates with a webservice key, reads your shop structure and product schema, and then pushes product updates to individual shops or all shops in a multi-store group simultaneously.

This prestashop api product sync approach delivers several concrete advantages over native import tooling:

Unified product management across all storefronts. A product record in MicroPIM is the single source of truth. Field mapping rules determine which fields go to which storefront, at what values. A price adjustment in MicroPIM propagates to every targeted PrestaShop store in the next sync run — no per-store manual updates required.

Incremental updates, not full replacements. MicroPIM tracks which products have changed since the last successful sync and only pushes those records. A catalog of 5,000 products where 40 changed overnight generates 40 API calls, not 5,000. This keeps your PrestaShop server load minimal and your sync times fast.

Full combination support. MicroPIM maps your product variant model directly to PrestaShop combinations, including combination-level pricing, stock references, images, and attribute values. All combinations for a product are created or updated in a single sync pass.

Multi-store selective targeting. Each sync job in MicroPIM can be configured to target specific shops within your PrestaShop multi-store setup. A catalog update for the B2B storefront runs independently of the retail store sync, with different field mapping rules applied to each.

Error isolation and retry. Failed records are logged with the specific API error returned by PrestaShop. MicroPIM retries transient failures automatically and flags persistent errors for review without blocking the rest of the sync.

For teams already using MicroPIM to manage data for other channels, the PrestaShop connector slots into the same hub-and-spoke architecture. If you also operate a WooCommerce store, see Sync Your WooCommerce Store with MicroPIM for the parallel WooCommerce setup. For Shopware, see Shopware Product Import with MicroPIM.

Setup Steps: Webservice Key and Store Connection

Enabling the PrestaShop Webservice

Before connecting MicroPIM, you need to enable PrestaShop’s webservice feature and generate an API key. This requires admin access to your PrestaShop back office.

Enable the webservice:

1. Log into your PrestaShop admin panel.
2. Navigate to Advanced Parameters > Webservice.
3. Set Enable PrestaShop’s webservice to Yes.
4. Set Enable CGI mode for PHP based on your server configuration — most shared hosting and VPS setups do not require this.
5. Click Save.

Generate a webservice key:

1. On the Webservice page, click Add new webservice key.
2. In the Key field, click Generate to create a cryptographically random key, or enter your own 32-character alphanumeric string.
3. Enter a Description such as “MicroPIM Integration” to identify this key’s purpose.
4. Set Status to Enabled.
5. In the Permissions section, assign Read and Write access to the following resources:

6. Click Save.

[SCREENSHOT: PrestaShop webservice API key configuration in MicroPIM]

Copy the generated key. PrestaShop displays the full key on this screen. Store it securely — the key is masked in the PrestaShop admin after you navigate away, and regenerating it invalidates the existing key.

Connecting MicroPIM to PrestaShop

Log into MicroPIM and navigate to Integrations in the left sidebar. The Integrations panel lists all available channel connectors with their current connection status.

[SCREENSHOT: MicroPIM integrations page with PrestaShop connector showing active connection]

Locate the PrestaShop connector card and click Connect. The PrestaShop connection settings panel opens. Enter the following values:

• Store URL: Your PrestaShop installation’s base domain (for example, https://yourstore.com). Use the primary domain, not a subdirectory path unless PrestaShop is installed in a subdirectory.
• Webservice Key: The key generated in your PrestaShop admin.
• API Version: MicroPIM detects your PrestaShop version automatically after a successful connection test. Leave this at Auto unless you need to force a specific API version.

Click Test Connection. MicroPIM sends an authenticated request to your store’s webservice endpoint and confirms that the key is valid and has the required permissions. If the test fails, the most common causes are:

• The webservice feature is not enabled in PrestaShop’s Advanced Parameters.
• The key was copied with leading or trailing whitespace.
• Your server has a .htaccess or security module blocking XML API requests. Check your server error log for 403 or 401 responses.
• The key’s resource permissions do not include products with Read access.

Once the test passes, click Save Integration. MicroPIM retrieves your store’s shop group structure, individual shop list, product categories, features, and manufacturers — all of which are used in the field mapping steps below.

Mapping PrestaShop-Specific Fields

PrestaShop’s product schema has several concepts that are specific to the platform and require deliberate mapping: product features, manufacturers (brands), tax rules, and the multi-language field structure. The MicroPIM field mapping editor handles all of these.

Navigate to Integrations > PrestaShop > Field Mapping to open the mapping editor.

Core Product Fields

Note on PrestaShop multilang fields: PrestaShop stores translatable fields — name, description, link_rewrite, meta fields — as language-specific values attached to each product. In the MicroPIM field mapping editor, multilang fields show a language selector. Map each MicroPIM locale field (for example, name_en, name_de) to the corresponding PrestaShop language ID. MicroPIM fetches your store’s configured languages during the connection setup and lists them by name.

Product Features

PrestaShop’s product features are key-value attribute pairs visible on the product page (for example, Material: Cotton, Country of Origin: France). They are distinct from combination attributes — features describe the product itself, not its purchasable variations.

In the Features section of the field mapping editor:

1. Map each MicroPIM product attribute that represents a feature to the corresponding PrestaShop feature name.
2. Enable Create missing features to allow MicroPIM to create new PrestaShop features and feature values it encounters but that do not yet exist in your store.
3. For features with a controlled vocabulary — values that should only come from a predefined list — disable auto-creation and map feature values explicitly.

Manufacturers

PrestaShop has a dedicated Manufacturers resource that links products to brand records. Each brand in PrestaShop is a separate entity with its own page, logo, and SEO fields.

Map your MicroPIM brand or manufacturer field to the PrestaShop manufacturer field in the core product mapping section. When MicroPIM encounters a brand value that exists in PrestaShop, it links the product to that manufacturer record. When Create missing manufacturers is enabled, MicroPIM creates a new manufacturer record for any brand not yet in PrestaShop.

Tax Rules

PrestaShop applies tax through tax rule groups assigned at the product level. Map your MicroPIM tax classification field to the appropriate PrestaShop tax rule group ID. If your products span multiple tax classes — standard rate, reduced rate, exempt — create a mapping row for each classification.

Multi-Store Sync: Single Import to Multiple PrestaShop Stores

PrestaShop’s multi-store architecture presents a specific synchronization challenge: the same product can have different prices, availability, and presentation settings across different shops within the same installation. MicroPIM’s multi-store sync handles this through per-store field mapping overrides and shop targeting in sync job configuration.

[SCREENSHOT: Multi-store selection interface for targeting specific PrestaShop storefronts]

Configuring Shop Targets

When you add a sync job in MicroPIM (Automation > New Automation > PrestaShop Product Sync), the shop targeting section lists every shop and shop group detected in your PrestaShop installation.

You can configure sync scope at three levels:

• All shops: The product is created or updated in every shop in the installation. Use this for catalog-wide updates where all storefronts share identical product data.
• Shop group: Targets all shops within a specific group. Useful for regional groupings where the same rules apply across a cluster of related stores.
• Individual shops: Precisely targets one or more specific storefronts. This is the correct setting for B2B versus B2C pricing separations or regional market launches where not all products are available in all stores.

Per-Store Field Mapping Overrides

For each shop target, MicroPIM supports field mapping overrides — rules that modify specific field values before they are written to that shop’s product record.

Common use cases for per-store overrides:

• Price multiplier: Multiply the base price by a factor (for example, 1.25) before syncing to a wholesale storefront that sells at markup.
• Field substitution: Use a different MicroPIM attribute as the value for a given field on a specific store. For example, map description_b2b instead of description when syncing to the B2B shop.
• Availability suppression: Set active to 0 for a specific shop to keep a product visible in the main store but hidden on a secondary storefront.

Override rules are configured in Integrations > PrestaShop > Shop Overrides and apply whenever a sync job targets the corresponding shop. This prestashop multistore product sync approach means you define the logic once — not re-configure it for every import run.

Handling PrestaShop Combinations

PrestaShop’s combinations are the equivalent of product variants in other platforms. A combination represents a specific purchasable version of a product defined by a set of attribute values — for example, Size: L and Color: Red. Each combination has its own reference code, EAN, price modifier, stock quantity, and optionally its own images.

MicroPIM maps its variant model directly to PrestaShop combinations. When a product in MicroPIM has variants, the sync process:

1. Creates or updates the parent product with product-level fields.
2. Registers the variant dimensions as PrestaShop attribute groups (for example, Size, Color) with the correct attribute values (L, XL, Red, Blue) if they do not already exist.
3. Creates or updates each combination with its specific attribute value set, reference, EAN, price modifier, and stock.

Combination Field Mapping

Default Combination

PrestaShop requires exactly one combination to be marked as the default combination — the version shown to shoppers when they first land on the product page. In MicroPIM, mark the intended variant as the default using the Is Default Variant toggle in the product editor. MicroPIM passes this flag to PrestaShop during sync.

Minimum Quantity and Out-of-Stock Behavior

PrestaShop supports per-combination minimum order quantities and configurable out-of-stock behavior (deny orders, allow orders, or use the default store configuration). Map these settings from MicroPIM’s variant fields if your product data includes them. For a simpler setup where all combinations use the store default, leave these unmapped and PrestaShop applies its global settings.

Testing the Integration

Before activating automated sync across your full catalog, validate the integration with a controlled test to confirm field mapping is correct and combination data is handled as expected.

Test with a representative product set. Select three to five products that together cover the main data patterns in your catalog:

• A simple product (no combinations) with features and a manufacturer
• A product with combinations across two attribute dimensions
• A product that exists in multiple shops with different prices
• A product with multilang descriptions if your stores are multilingual

Create a test catalog filter. In MicroPIM’s product list, use a saved filter that targets only these test products. Assign this filter to a manual sync job rather than your full catalog automation.

Run the sync manually. Navigate to Automation > New Automation, configure the PrestaShop sync with your test filter, and click Run Now instead of scheduling. MicroPIM processes only the filtered products and returns a result log.

Verify in PrestaShop. In your PrestaShop back office, open each synced product and confirm:

• Core fields (name, description, reference, price) match the MicroPIM source values
• Product features are listed with correct values
• Manufacturer is correctly linked
• Combinations are present with correct attribute combinations, references, and prices
• Stock quantities match MicroPIM’s variant stock values
• Multi-store: open each targeted shop context and confirm the product is present with the correct shop-specific values

Test a partial update. Modify a single field on one of the test products in MicroPIM — for example, update the price — and run the sync again. Confirm that only the changed field was updated in PrestaShop and that no other fields were altered.

Resolve any field mapping discrepancies before proceeding to full catalog activation. The most common issues at this stage are multilang field mis-mapping, combination attribute groups not found in PrestaShop, and tax rule group ID mismatches.

For a broader guide to validating your first MicroPIM catalog setup before pushing to any channel, see Getting Started with MicroPIM.

Automating Daily Syncs with Cron Scheduling

A tested integration is only as useful as its automation. MicroPIM’s Automation feature uses a cron-based scheduler to run prestashop bulk product import and inventory sync jobs at configured intervals without manual execution.

Navigate to Automation in the MicroPIM sidebar and click New Automation. Select PrestaShop Product Sync as the job type.

Sync Scope Options

For daily operations, Changed Products scope is the correct choice. It keeps sync runs fast and API usage low because only genuinely changed records are transmitted.

Recommended Cron Schedule

Separating Product and Inventory Syncs

Best practice is to configure two separate automation jobs:

1. Product data sync — runs once daily with Changed Products scope. Covers all product fields: descriptions, features, combinations, images, manufacturers, categories, and multi-store assignments.
2. Inventory sync — runs every 30 minutes. Covers only stock_availables quantities. This job is lightweight because it only touches stock records, not full product payloads.

Separating these jobs means your PrestaShop server is not processing full product updates every 30 minutes. The frequent inventory sync stays fast because it touches only one resource type. The daily product sync runs during low-traffic hours when the API load is acceptable.

Failure Notifications

Configure an email notification address on each automation job. A failed overnight sync that is not detected until customers report stale prices or incorrect stock can result in lost orders and customer service overhead. MicroPIM sends an alert immediately when a scheduled job fails so the issue can be diagnosed and resolved before the next business day.

For a deeper look at MicroPIM’s full automation capabilities — including chaining jobs, triggering syncs from webhook events, and scheduling export jobs alongside product syncs — see Automate Imports and Exports with MicroPIM.

PrestaShop’s multi-store architecture gives merchants powerful channel flexibility. The operational cost of maintaining product data across that architecture manually is what MicroPIM eliminates. A single product record in MicroPIM, with field mapping rules configured per storefront and a daily sync schedule running in the background, replaces the cycle of per-store CSV imports, manual combination updates, and cross-store consistency checks.

The setup covered in this guide — webservice key generation, connector configuration, feature and manufacturer field mapping, combination sync, multi-store targeting, and cron-scheduled automation — gives you a complete prestashop product import integration that scales with your catalog and your storefront count without adding proportional manual effort.

Ready to connect your PrestaShop stores? Start your free 14-day MicroPIM trial and have your first products syncing across your storefronts today. No credit card required.

Looking for more MicroPIM integration guides? Explore Sync Your WooCommerce Store with MicroPIM, Shopware Product Import with MicroPIM, Automate Imports and Exports with MicroPIM, and Getting Started with MicroPIM for the full integration series.