{"id":552260,"date":"2026-08-31T04:15:34","date_gmt":"2026-08-31T04:15:34","guid":{"rendered":"https:\/\/webkul.com\/blog\/?p=552260"},"modified":"2026-09-11T08:30:30","modified_gmt":"2026-09-11T08:30:30","slug":"pimcore-shopware-catalog-sync-connector","status":"publish","type":"post","link":"https:\/\/webkul.com\/blog\/pimcore-shopware-catalog-sync-connector\/","title":{"rendered":"Pimcore & Shopware Catalog Sync Connector"},"content":{"rendered":"\n

Introduction<\/h2>\n\n\n\n

The Pimcore 12 Shopware 6 Connector keeps your catalog in sync between Pimcore and Shopware 6.<\/p>\n\n\n\n

It syncs categories, attributes, products, and variant (configurable) products automatically, in both directions. Moreover, every sync runs as a background job inside Pimcore Studio.<\/p>\n\n\n\n

As a result, catalog management is faster and far more reliable.<\/p>\n\n\n\n

Keeping a Pimcore catalog and a Shopware storefront aligned by hand doesn’t scale. So Webkul built the Pimcore 12 Shopware 6 Connector to remove the copy-paste.<\/p>\n\n\n\n

It bridges your Pimcore data model and your Shopware 6 store over the Admin API. As a result, categories, attributes, products, and product variants all flow automatically, in both directions.<\/p>\n\n\n\n

It’s built natively for Pimcore 12 and Shopware 6. Also, it brings two big upgrades. First, every sync runs as a restartable background job.<\/p>\n\n\n\n

So large catalogs no longer block your screen or time out. Meanwhile, you watch each run on a live progress view. Second, it’s bidirectional.<\/p>\n\n\n\n

It both imports from and exports to Shopware. Because of that, you can seed Pimcore from an existing Shopware store, then push curated changes back out.<\/p>\n\n\n\n

The Pimcore 12 Shopware 6 Connector also lives natively inside the new Pimcore Studio UI. Furthermore, it adds its own screens for credentials, mapping, and the job runner.<\/p>\n\n\n\n

So there are no separate tools to learn.<\/p>\n\n\n\n

\"shopware\"<\/figure>\n\n\n\n

Server Requirements<\/h2>\n\n\n\n

The connector runs on top of a standard Pimcore 12 install, so if Pimcore runs, the connector runs. Here is what that stack needs.<\/p>\n\n\n\n

Component<\/th>Requirement<\/th><\/tr><\/thead>
PHP<\/td>8.4 or 8.5 (CLI + FPM), with pdo_mysql, intl, mbstring, curl, gd \/ imagick, zip, exif, opcache<\/td><\/tr>
Symfony<\/td>7.4 (installed as a Pimcore dependency)<\/td><\/tr>
Pimcore<\/td>Pimcore 12 \u2014 Platform 2026.1 (pimcore\/pimcore: 2026.1.x) with the Studio UI bundle<\/td><\/tr>
Database<\/td>MariaDB 10.11+ or MySQL 8.0+<\/td><\/tr>
Web server<\/td>Nginx or Apache 2.4<\/td><\/tr>
Composer<\/td>Composer 2<\/td><\/tr>
Node.js<\/td>20+ \u2014 only if you rebuild the Studio UI assets yourself<\/td><\/tr>
Message queue<\/td>A running Symfony Messenger worker (Supervisor is recommended) \u2014 this is what drives the background sync jobs<\/td><\/tr>
Shopware<\/td>Shopware 6 \u2014 self-hosted or Cloud, reachable from the Pimcore server over HTTP(S), with an Admin API Integration<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

A few PHP settings matter for large catalogs. So set memory_limit<\/code> to at least 512M (1G for big product imports), <\/p>\n\n\n\n

and raise max_execution_time<\/code> for the CLI. Because the syncs run in the background, the web request itself never has to wait.<\/p>\n\n\n\n

Key Features of the Pimcore 12 Shopware 6 Connector<\/h2>\n\n\n\n