Skip to Content

WooCommerce Connector

by
Odoo

$ 98.02

v 18.0 Third Party
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies • Contacts (contacts)
• Discuss (mail)
• Inventory (stock)
• Invoicing (account)
• Purchase (purchase)
• Sales (sale_management)
Community Apps Dependencies
Lines of code 11077
Technical Name woo_commerce_cx_at
LicenseOPL-1
Websitehttps://www.arure.tech
Versions 18.0 19.0
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies • Contacts (contacts)
• Discuss (mail)
• Inventory (stock)
• Invoicing (account)
• Purchase (purchase)
• Sales (sale_management)
Community Apps Dependencies
Lines of code 11077
Technical Name woo_commerce_cx_at
LicenseOPL-1
Websitehttps://www.arure.tech
Versions 18.0 19.0
For Odoo 19 · WooCommerce sync · Multi-store · HMAC webhooks

WooCommerce Connector

Two-way sync between WooCommerce and Odoo 19. Products, variants, orders, customers, inventory — all kept in lockstep through HMAC-verified webhooks and a no-code field mapping editor. Multi-warehouse stock aggregation, smart-insights dashboard, and a 5-step onboarding wizard that won't let you proceed until your store actually connects.

Built native for Odoo 19 from line one. No queue_job dependency. Verified end-to-end against a live WooCommerce store before publication.

$99
Per database
5 entities
Synced both ways
90 days
Refund window
v19.0.1.9
Live on App Store
support@arure.tech WhatsApp +1 858 463 4405

What you get

Four guarantees on every install. Your WooCommerce store and your Odoo books stop drifting apart.

Two-way sync, five entities
Products + variants, orders, customers, and inventory move both ways between WooCommerce and Odoo. Conflict rules per entity. Track exactly which side won, every time.
HMAC-verified webhooks
Order, product, and inventory changes flow into Odoo within seconds via SHA-256 HMAC-signed webhooks. Per-instance secret. Replay protection. No polling, no cron lag.
No-code field mapping
Map any WooCommerce meta-key to any Odoo field through a UI editor. Bidirectional. Survives upgrades. No Python, no XML, no consultant required for routine custom-field work.
Smart Insights dashboard
Rule-based 0–100 store-performance score with named risks, opportunities, and recommendations. Pure ORM. No external services, no LLM calls, no data leaves your instance.

Who this is for

WooCommerce-first sellers
Your store is on WooCommerce, your books are moving to Odoo, and you need orders / inventory to stop being kept in two systems by hand.
Multi-warehouse operators
You stock the same SKU across multiple Odoo warehouses and need WooCommerce to see one accurate aggregate, not the per-warehouse split.
Implementation partners
You configure WooCommerce / Odoo integrations for clients and want one connector that's onboarding-friendly without writing custom Python every time.

See it running

Real screenshots from a fresh Odoo 19 instance connected to a live WooCommerce store. Click any image to view full size.

Set it up

5-step onboarding wizard, gated until connection succeeds
5-step onboarding wizard, connection-gated
Instance form with credentials and sync settings
Instance form — credentials, sync mode, multi-warehouse
No-code field mapping editor
No-code field mapping editor

Use it daily

Multi-store instances in kanban view
Multi-store kanban — one card per WooCommerce instance
WooCommerce orders kanban grouped by status
WooCommerce orders inside Odoo, grouped by status
Smart Insights dashboard with 0-100 store performance score
Smart Insights — 0–100 store performance score
Analytics list view of synced records
Analytics — list view of synced records by status
Analytics pivot cross-tab — instance × period × status
Pivot cross-tab — instance × period × status
Orders sync graph — chronological volume per instance
Orders graph — chronological sync volume per instance

Trust it

HMAC-verified webhooks list with per-route secret
HMAC-verified webhooks, per-route secret
Background processor jobs with state, retry, and last error
Background jobs — state, retry count, last error
Per-operation sync log with request, response, latency
Per-operation sync log — full request & response

Common scenarios

Three patterns this connector ships every week.

Moving accounting from spreadsheets to Odoo
Your storefront stays on WooCommerce. Orders flow into Odoo within seconds via HMAC-verified webhook. Inventory pushes the other way every time stock moves. No double entry, no nightly sync gap.
Multi-store retailer consolidating onto one Odoo
Two, five, ten WooCommerce stores. Each is a separate connector instance with its own webhook routes and credentials. Aggregate analytics in one Odoo. One Smart Insights score per store, side by side.
Implementation partner setting up clients
5-step onboarding wizard gates each step until the prior one connects, so a junior consultant can't accidentally ship a half-configured connector. No-code field mapping handles 80% of the custom-meta requests without writing Python.

Frequently asked

Five entities, both directions: products (with variants), orders, customers, and stock levels. Direction and conflict-resolution rules are configurable per entity on the instance form. Tracking-numbers push from Odoo to WooCommerce on picking validation.

Sub-second on the network leg; the bottleneck is your Odoo instance's worker capacity. SHA-256 HMAC verified at the edge, queued, then processed by the background processor with exponential-backoff retry. No polling, no cron lag.

Yes. Each WooCommerce store is one connector instance. Each instance has its own webhook routes, credentials, conflict-resolution settings, and warehouse mapping. List view + kanban show all stores side-by-side.

Pick the Odoo warehouses whose stock should count toward the WooCommerce-visible quantity on each instance. The connector sums on-hand across selected warehouses and pushes one number to WooCommerce. Behind-the-scenes warehouse splits stay invisible to the storefront.

For the WooCommerce custom-meta and Odoo custom-field cases. If WooCommerce has a meta-key like _serial_number on each order and you want it on the Odoo sales order's x_studio_serial field, point one at the other in the mapping editor. Bidirectional. No Python.

Optional, off by default. Toggle it on per instance and every new WooCommerce order creates a CRM lead linked to the customer. Skips gracefully if the CRM module isn't installed.

A rule-based 0–100 store-performance score with named risks (e.g. failed-webhook backlog), opportunities (low-stock SKUs trending up), and recommendations. Pure ORM — no LLM calls, no external services, no data ever leaves your instance. Read the rules, audit the rules, change the rules in Odoo.

The job lands in the background processor with state=failed, the full request + response are captured in the sync log, and the operator sees it in the failed-jobs view. Exponential-backoff retry runs automatically up to a configurable cap; manual retry is one click.

Yes. Built native for Odoo 19 from line one (no ported v14 cruft). Hooks into stable public extension points only. Bug fixes and security patches are committed for 12 months after Odoo 21 ships.

No. Per Odoo's policy, third-party paid apps cannot be installed on Odoo Online. This module runs on Odoo.sh and on-premise (self-hosted Community or Enterprise) deployments.

Evaluate before you commit. Buy when you're confident.

90-day refund window. Reach us through any channel below — we reply within 1 business day.

Email
support@arure.tech
Setup questions, refund requests, anything else.
WhatsApp
+1 858 463 4405
Quick questions, same-business-day reply.
Live chat
Chat with us
Quick technical questions, no waiting on email.

What's New

Highlights from the most recent releases. The full CHANGELOG.md is included inside the module package.

v19.0.1.9.02026-05-07Latest

Package hygiene & vendor compliance

Improved
  • Module package now contains only customer-facing documentation. Internal strategy artifacts moved out.
  • All references to other vendor names removed across the package per Odoo Vendor Guidelines.
  • Module description focuses on what the connector does, not what alternatives don't.
v19.0.1.8.02026-05-07

Pricing & license alignment

Changed
  • License set to OPL-1 (Odoo Proprietary License v1.0). Per-database license; not redistributable.
  • Headline price set at $99 per database, sustainable for ongoing maintenance.
v19.0.1.6.02026-05-06

Critical fixes & foundation parity

Fixed
  • Four Odoo 19 crash paths in record creation flows fixed.
  • Foundation parity pass with the companion module so both share the same audit-log shape and queue conventions.

License

Odoo Proprietary License (OPL-1). Per-database license. Source code included; not redistributable.

Trademarks

WooCommerce is a trademark of Automattic Inc. Odoo is a registered trademark of Odoo S.A. This module is an independent extension developed by Arure Technologies and is not affiliated with, endorsed by, or sponsored by either Automattic Inc. or Odoo S.A.

Odoo Proprietary License v1.0

This software and associated files (the "Software") may only be used (executed,
modified, executed after modifications) if you have purchased a valid license
from the authors, typically via Odoo Apps, or if you have received a written
agreement from the authors of the Software (see the COPYRIGHT file).

You may develop Odoo modules that use the Software as a library (typically
by depending on it, importing it and using its resources), but without copying
any source code or material from the Software. You may distribute those
modules under the license of your choice, provided that this license is
compatible with the terms of the Odoo Proprietary License (For example:
LGPL, MIT, or proprietary licenses similar to this one).

It is forbidden to publish, distribute, sublicense, or sell copies of the Software
or modified copies of the Software.

The above copyright notice and this permission notice must be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.