Dedicated PrestaShop connector — two-way catalog, stock, price sync
Dedicated module for PrestaShop 1.7+ with full two-way sync. The PIM is the source of truth for the catalog, PrestaShop sends back orders and sold stock. Continuous reconciliation via the dedicated module (Celery queue prestashop).
What PrestaShop sync covers
Full two-way sync
Catalog PIM → PrestaShop (products, variants, prices, stocks, media). Orders + sold stock PrestaShop → PIM. Continuous reconciliation, conflicts logged.
Native product combinations
PrestaShop combinations are mapped 1:1 to PixeePIM Product Variants. Attribute → Group, Value → Attribute. No manual remap.
Categories & attributes
PrestaShop taxonomy synced from PixeePIM Categories Manager. Custom attributes mapped to PrestaShop features.
Multi-shop & multi-group pricing
PrestaShop multi-shop natively supported. Differentiated prices per shop, per customer group (B2B vs B2C), per currency.
Images & SEO
Images resized by PixeePIM DAM presets before upload. Meta title/description, URL slug, alt tags — all mapped from the PIM.
Dry-run reconciliation
Before a massive sync, run a reconciliation in preview mode: what will change on PrestaShop, for which product, with which before/after value. Validate before applying.
Why PrestaShop has its own module (not just a generic connector)
PrestaShop is still very popular with European distributors — often installed 5-10 years ago, deeply customized, sometimes with third-party modules that rewrite behaviors. A generic "REST/JSON" connector doesn't hold up against this diversity.
PixeePIM's dedicated module knows the PrestaShop conventions: `id_attribute_group` web service, HT/TTC price quirks per country, pack handling, multi-shop with offset IDs. The dedicated `prestashop` Celery queue is isolated so a slow PrestaShop site doesn't block the other connectors.
That's also why the sync is truly two-way: we read PrestaShop orders to decrement stock in the PIM, and push the new stock to other channels. Without that, you sell the same unit twice — a nightmare many distributors know well.
Typical use cases
Migration to the PIM
You have a product catalog in PrestaShop. The module imports it into the PIM in dry-run reconciliation, you validate, then PrestaShop becomes a distribution channel driven by the PIM.
PrestaShop + Odoo ERP
Odoo as source of truth for stocks and purchase prices, PixeePIM as source of truth for enriched product sheets, PrestaShop as distribution channel. Triangulation managed by the PIM.
Multi-country on PrestaShop multi-shop
One PrestaShop instance, several per-country shops. The module pushes the right prices, categories, attributes to each shop based on rules configured in the PIM.
PrestaShop sync is included in every paid plan
One of 17 e-commerce/marketplace connectors + 6 ERP sync modules natively in PixeePIM.