{"id":546547,"date":"2026-08-20T09:54:51","date_gmt":"2026-08-20T09:54:51","guid":{"rendered":"https:\/\/webkul.com\/blog\/?p=546547"},"modified":"2026-08-20T09:54:59","modified_gmt":"2026-08-20T09:54:59","slug":"pimcore-odoo-catalog-sync-connector","status":"publish","type":"post","link":"https:\/\/webkul.com\/blog\/pimcore-odoo-catalog-sync-connector\/","title":{"rendered":"Pimcore & Odoo Catalog Sync Connector"},"content":{"rendered":"\n

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

The Pimcore 12 Odoo 19 Connector keeps your catalog in sync between Pimcore and Odoo 19.<\/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 an Odoo instance aligned by hand doesn’t scale. So Webkul built the Pimcore 12 Odoo 19 Connector to remove the copy-paste.<\/p>\n\n\n\n

It bridges your Pimcore data model and your Odoo database. 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 Odoo 19. 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 Odoo. Because of that, you can seed Pimcore from an existing Odoo database, then push curated changes back out.<\/p>\n\n\n\n

The Pimcore 12 Odoo 19 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

\"odoo<\/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<\/strong><\/td>8.4 or 8.5 (CLI + FPM), with pdo_mysql<\/code>, intl<\/code>, mbstring<\/code>, curl<\/code>, gd<\/code> \/ imagick<\/code>, zip<\/code>, exif<\/code>, opcache<\/code><\/td><\/tr>
Symfony<\/strong><\/td>7.4 (installed as a Pimcore dependency)<\/td><\/tr>
Pimcore<\/strong><\/td>Pimcore 12 \u2014 Platform 2026.1 (pimcore\/pimcore: 2026.1.x<\/code>) with the Studio UI bundle<\/td><\/tr>
Database<\/strong><\/td>MariaDB 10.11+ or MySQL 8.0+<\/td><\/tr>
Web server<\/strong><\/td>Nginx or Apache 2.4<\/td><\/tr>
Composer<\/strong><\/td>Composer 2<\/td><\/tr>
Node.js<\/strong><\/td>20+ \u2014 only if you rebuild the Studio UI assets yourself<\/td><\/tr>
Message queue<\/strong><\/td>A running Symfony Messenger worker (Supervisor is recommended) \u2014 this is what drives the background sync jobs<\/td><\/tr>
Odoo<\/strong><\/td>Odoo 19 \u2014 self-hosted or Odoo.com, reachable from the Pimcore server over HTTP(S)<\/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<\/strong> (1G for big product imports), 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 Odoo 19 Connect<\/strong><\/h2>\n\n\n\n

Bidirectional sync<\/strong> \u2014 import and export for Categories, Attributes, Products, and Variant Products.<\/p>\n\n\n\n

Asynchronous job engine<\/strong> \u2014 syncs run in the background, so they never block your work.<\/p>\n\n\n\n

Live Job-Execution view<\/strong> \u2014 real-time status, read \/ created \/ updated counts, a run-history grid, and a one-click Stop.<\/p>\n\n\n\n

Multi-language aware<\/strong> \u2014 maps your localized Pimcore content to Odoo’s translated fields.<\/p>\n\n\n\n

Config-driven mapping<\/strong> \u2014 point the connector at your Pimcore classes; nothing to hard-code.<\/p>\n\n\n\n

Reliable matching<\/strong> \u2014 a shared link between records keeps Pimcore and Odoo in step, so re-runs update instead of duplicating.<\/p>\n\n\n\n

Variant support<\/strong> \u2014 Pimcore variant products map to Odoo product templates and their variants.<\/p>\n\n\n\n

Connecting the Pimcore 12 Odoo 19 Connector to Odoo<\/h2>\n\n\n\n

The connector talks to Odoo over JSON-RPC. It supports two ways to authenticate, so it works with both self-hosted and Odoo.com (SaaS) instances.<\/p>\n\n\n\n