WooCommerce Odoo Connector: Orders, Stock, Products (Miko)
by Tripster Developers https://tripsterdevelopers.com/odoo/$ 402.00
WooCommerce Odoo Connector: two-way sync for orders, products, customers and stock
Connect a WooCommerce store to Odoo and keep both sides in step, on a schedule. Built on the WooCommerce REST API v3, against your own WordPress — which is why it is careful about the things a hosted API never does to you.
Downloading the ZIP by hand? Take both: put
miko_ecommerce_core in your addons folder alongside this one, or Odoo reports an unmet dependency.Why this one
Built for a store you host
An HTML error page from a caching plugin or a firewall is detected and explained, not parsed as data. A slow site gets a generous timeout and backoff.
Refuses plain HTTP outright
The consumer key and secret go with every single request. Over http:// anyone on the network can read them, so the address is rejected rather than quietly downgraded.
Honest about fulfilment
WooCommerce has no fulfilment object. An order is shipped by moving its status, and tracking lives in meta_data under your pluginâs key — so that key is a setting, not a guess.
Stable pagination
Ordered by id ascending, because Woo pages by number and ordering by anything that changes mid-walk lets a record be read twice or skipped.
Never writes stock it will ignore
Woo silently ignores a quantity when stock management is off for an item, so those are skipped and reported rather than reported as sent.
Safe by default
Order confirmation, invoicing, stock publishing, status push and the scheduler all start switched off.
What syncs, and which way
| Records | Direction | Notes |
|---|---|---|
| Orders | WooCommerce to Odoo | Line discounts, shipping, fees and tax lines. Skips pending and failed carts. |
| Products and variations | Either way, or both | Attributes become Odoo attributes; SKU carried across |
| Customers | Either way, or both | Matched on exact email; guest checkouts handled from the billing block |
| Stock levels | Odoo to WooCommerce | Only where Woo is actually tracking stock for that item |
| Order status | Odoo to WooCommerce | Moved to completed when the Odoo delivery is validated |
| Taxes | Mapped by you | Anything unmapped stops and asks rather than under‑billing |
How it works
- 1
Create the API credentials in your store
Read and write access to products, customers, orders and inventory. The exact permission list is in Requirements below. - 2
Add the store in Odoo and press Test Connection
It verifies the credentials, names the store back to you, and says exactly what to fix if anything is wrong. - 3
Import, then look at what arrived
Products, then customers, then orders. Nothing is confirmed or invoiced yet: those switches start off on purpose. - 4
Turn on the schedule and the write-back
Once you are happy with what came in, enable the scheduled sync, stock publishing and fulfilment individually.
One store, every setting in one place
You choose which way data travels
Runs on a schedule, or right now
Stock and order status, back to the shop
Never a silent under-billing
Map any WooCommerce field to any Odoo field
When something fails, you are told what to fix
Detailed capabilities
Products and variations
- Variations come from a separate endpoint and are matched on exact option-set equality; a near match is reported and left unlinked.
- Attribute lines are only ever added, never removed, because removing one deletes variants that historical orders reference.
- Virtual products become Odoo services.
Orders
- Line discounts kept as discounts rather than folded into the price.
- Shipping and fee lines imported as their own lines.
- Pending and failed statuses skipped by default: they are abandoned checkouts, not sales.
- Guest checkouts become real contacts from the billing block.
When something fails
- Failed is transient — a dropped connection, a rate limit, a 502. Retried automatically with exponential backoff.
- Needs attention means something has to change first: a tax with no mapping, a product not in Odoo, a revoked key. Never retried on a timer, because a timer cannot fix it, and each one carries the sentence saying what to do.
- Every job keeps the exact payload that caused it, so a retry replays the failure without asking the store for the data again.
- A Retry button on every job, and a dashboard filtered to what still needs a person.
Requirements
- Odoo 16, 17, 18 or 19, Community or Enterprise.
- The free E‑Commerce Connector Engine (Miko).
- WooCommerce 3.5 or later, a consumer key with Read/Write permission, HTTPS, and permalinks set to anything other than Plain.
- Odoo Online cannot run third-party modules containing Python, so this needs Odoo.sh or a self‑hosted install.
Support
Email support for every version listed above, from the people who wrote it. Every release is certified against real Odoo images before it ships, and the test count is stated on this page rather than implied.
Questions
Where do tracking numbers go?
- Into the meta_data key your shipping plugin reads, which you name in the settings. Left empty, the order status still moves and no tracking is written somewhere nobody looks.
Why does it refuse my http:// address?
- WooCommerce sends the consumer key and secret with every request. Over plain HTTP they are readable in transit.
Which Odoo versions are supported?
- Every listed version is certified on each release by installing the module into a real Odoo image of that series and running the full test suite. A version is only listed once it passes.
Does this work on Odoo Online?
- No. Odoo Online cannot run third-party modules containing Python, which is Odoo's rule rather than ours. Odoo.sh and self-hosted installs are fine.
What does support cover?
- Installation problems, defects, and questions about how the module behaves, by email, for the versions listed on this page. Custom development and changes to Odoo core behaviour are separate work.
How do I report a problem?
- Email support@tripsterdevelopers.com with your Odoo version, the module version, and what you did. If a job failed, the job record holds the exact payload and the error, which answers most questions immediately.
Explore our other Odoo apps
E-Commerce Connector Engine
miko_ecommerce_coreShopify Odoo Connector
miko_shopifyBarcode Validator & Catalog Audit
miko_catalog_healthEmail Validation & Duplicate Contacts
miko_contact_healthMargin Control & Sold Below Cost
miko_margin_healthVendor Price Check & Supplier Audit
miko_supplier_healthMCP Server for AI
miko_mcp_serverSearch the Apps store for the technical name, or open Tripster Developers at the top of this page to see everything we publish.
Questions before you buy?
Email support@tripsterdevelopers.com and a developer who wrote this will answer, usually the same working day (New Zealand time).
Built by Tripster Developers.
WooCommerce is a trademark of Automattic Inc. Odoo is a trademark of Odoo S.A. This module is not affiliated with, endorsed by, or sponsored by either company; the names and logos are used only to say what it connects.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Inventory (stock)
• Invoicing (account) • Sales (sale_management) • Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 1963 |
| Technical Name |
miko_woocommerce |
| License | OPL-1 |
| Website | https://tripsterdevelopers.com/odoo/ |
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