Between WordPress and Odoo, a Bridge Was Missing. I Built It.
WordPress runs your storefront. Odoo runs your back office. Between the two lies a no man’s land where your data gets lost, duplicated, or simply stops talking. WP4Odoo is a modular bridge between these two worlds: open source, bidirectional, and designed not to wake you up at night.
The problem everyone works around
If you run WordPress (or WooCommerce) as your front end and Odoo as your ERP, you know how this goes. A customer places an order on your store. The order lands in WooCommerce. Then someone (often you, often by hand) re-enters it in Odoo for invoicing, inventory management, and sales follow-up. Subscriptions, CRM contacts, enrollments in your online courses: same story.
Every manual entry is a chance for error. Every hour spent copying and pasting between two tabs is an hour not spent growing your business. And after a few months, your two systems quietly drift apart: WordPress shows one stock level, Odoo shows another, and you only find out when a customer calls to ask where their order is.
Commercial connectors exist, but they are often locked into a handful of use cases, and some depend on middleman platforms like Zapier or Make, which add a point of failure and one more bill. I wanted to build something different.
What WP4Odoo is
WP4Odoo is a modular WordPress plugin that creates a two-way bridge between WordPress/WooCommerce and Odoo. You enable only the modules you need, and the plugin syncs data in both directions asynchronously: no API call to Odoo is ever made while a visitor is browsing your site.
Everything goes through a persistent queue that is processed in the background in configurable batches. Automatic retries, job deduplication, detailed logs. If Odoo is temporarily unreachable, jobs simply wait and are retried automatically. Your site never slows down, and your visitors never notice a thing.
One plugin, dozens of modules
Rather than one big monolith, WP4Odoo is split into independent modules. Each module covers a functional area (e-commerce, CRM, LMS, helpdesk, events, marketplace, accounting, and more) and one or more third-party WordPress plugins. Don’t use WooCommerce Subscriptions? That module isn’t loaded. Don’t need the CRM? It stays disabled.
The functional coverage is broad and keeps growing. Each module knows which Odoo apps it requires and checks for them when you activate it. Some depend on apps that are only available in Odoo Enterprise, and others cannot work with the most recent versions of Odoo when the corresponding app has been removed (memberships, for example). The README on GitHub details compatibility, sync directions, and prerequisites module by module.
What flows, and in which direction
The sync direction depends on the module. WooCommerce is bidirectional: products, orders, stock, and categories flow both ways. Contact forms only push to Odoo. The Sales module only pulls from Odoo into WordPress. This isn’t an architect’s whim: forcing two-way sync everywhere invites data conflicts that cannot be resolved cleanly. It is better to define clearly which system is the source of truth for each type of data.
Under the hood
The heart of the plugin is its asynchronous queue. Rather than calling Odoo in real time at checkout (which is fragile and slow), every event creates a job that is processed in the background. The plugin talks to Odoo through all three of its interfaces: JSON-RPC, XML-RPC, and JSON-2, the new API that Odoo offers starting with version 19 to replace the other two, which are now deprecated. Credentials are encrypted at rest, and incoming webhooks let Odoo notify WordPress in real time, with authentication and rate limiting.
Odoo versions are not identical: from one release to the next, fields disappear or get renamed, and Odoo then rejects the entire record. The plugin compares what it sends against the actual schema of your Odoo, renames what needs renaming, and leaves out what no longer exists, instead of failing. The Health tab shows you what was left out, which Odoo version was detected, and the state of the database, which the plugin can also repair on its own if tables go missing.
You can manage everything through a tabbed admin interface, or entirely from the command line with WP-CLI: connection setup, health checks (with an exit code your monitoring can use), logs, database repair, module management, and bulk product sync. It is handy for automated deployments and quick diagnostics. The technical details are in ARCHITECTURE.md.
Odoo compatibility
The plugin works with recent versions of Odoo (17 and up) over JSON-RPC, using either an API key or a password, and can use JSON-2 starting with Odoo 19. Earlier versions (14 to 16) go through XML-RPC. The plugin is verified against real instances of Odoo 19 and Odoo 20, including Odoo Online. It is compatible with On-Premise, Odoo.sh, and Odoo Online, in both Community and Enterprise editions. The “One App Free” plan works partially: the README spells out what works depending on the app you choose.
Extensibility and multilingual support
WP4Odoo is built to be extended: hooks to register your own modules, filters to transform data in transit, and mapping of custom fields to Odoo. If your site is multilingual (WPML or Polylang), the plugin syncs translations of products, categories, and attributes in both directions. The plugin itself is translated into several languages and ready for more. Contribution guidelines are in CONTRIBUTING.md.
Quality and testing
This is a personal project, not a commercial product. But it touches invoicing, inventory, and customer data for real businesses, so the bar has to be high. The plugin is covered by thousands of automated tests in continuous integration, static analysis, and integration tests running in a real WordPress.
Unit tests alone are not enough for a connector, because the software it links together changes without warning. Every week, an automated check spins up real Odoo instances (versions 19 and 20) in Docker, replays the everyday operations (contacts, orders, invoices, stock) across all three Odoo interfaces, then installs the latest release of every supported free WordPress plugin to confirm that the matching module still recognizes it. That is how a breaking third-party update gets caught quickly.
Available as open source
The source code, documentation, changelog, and architecture guide are on GitHub. The plugin is released under the GPL v2+ license.
A compatibility feedback form
If you’re using WP4Odoo and a third-party plugin update breaks something, or if an untested version works just fine, you can let me know with the form below. It’s quick, it helps me prioritize fixes, and it keeps the project going far more effectively than monitoring things on my own.
The form is also available directly from the WordPress admin: when the plugin detects a version of a third-party plugin newer than the one it has validated, it shows a warning with a pre-filled link. All you have to do is say whether it works or not.