Connecting WooCommerce to Holded or Odoo: what each one actually syncs

1. The decision that comes before choosing a tool

Before looking at connectors there is one question to answer. When you change a product's price, where do you change it? And stock, who holds the correct figure, the store or the ERP?

This is what defining a source of truth means. Every piece of data needs a single system that owns it, while the other simply receives. When both can write the same field, sooner or later one overwrites the other and you end up with stale prices or negative stock.

2. WooCommerce with Holded, how it really works

Holded has its own WooCommerce integration. It installs as a WordPress plugin and connects with an API key. It needs nothing special from your hosting, and that is its great advantage.

The three details that change the project

1. 01Two-way stock is not included. You need Holded's inventory add-on, which is paid separately. This is the detail that wrecks the most budgets, because many people assume stock syncs on the base plan.
2. 02Only «Completed» orders get invoiced. If you configure orders to arrive as invoices or receipts, Holded imports them only once you mark the order as completed in WooCommerce. An order sitting in «Processing» generates nothing.
3. 03The catalogue only flows one way. Whatever you change in Holded does not reach the store. Edit a product there and the site keeps showing the old version.

For a store selling finished products from a single warehouse, with a team working in WordPress that mainly wants to stop writing invoices by hand, this integration covers the case with very little setup.

3. WooCommerce with Odoo, and the requirement that rules many people out

This is not a minor detail, it is an infrastructure and cost decision. To connect Odoo with WooCommerce you have to be on Odoo.sh, Odoo's platform for projects with development, or on your own server. Both mean a higher plan and someone to administer the environment.

So which connector do you use

You use third-party modules published on Odoo's Apps Store. The two most widely used are Emipro's connector, covering Odoo versions 8 through 19, and VentorTech's, covering 16 through 19 in both Community and Enterprise. Both are paid and come on top of your licence.

What you get in return

• Forecast stock, not just what is on the shelf. You can publish the quantity you will have, counting what is already reserved and what is arriving on a purchase order.
• Bundles and kits calculated for you. Odoo looks at the scarcest component and publishes how many kits you can genuinely sell.
• Several warehouses. Consolidate stock or assign a warehouse to each store.
• The order runs the whole chain. It arrives as a sales order, reserves stock, generates the delivery note, issues the invoice and records the payment, with nothing done by hand.
• Tracking flows back to the store. When you prepare the shipment in Odoo, the tracking number and the status change reach WooCommerce and the customer sees them.
• Price lists by customer type. Different prices for wholesale and retail, managed from the ERP.

It is far more powerful, and it is also far more of a project. If your operation needs none of the above, you are paying for complexity you will never use.

4. Side by side

5. Which one suits you

Choose Holded if…

• You sell finished products you buy ready-made, with no assembly.
• Your team creates and edits products in WordPress and wants to keep doing that.
• You work with one warehouse, or two without complicated rules.
• What hurts is invoicing and reconciling the books, not logistics.
• You do not want to administer servers or take on a long project.

Choose Odoo if…

• You sell bundles or kits, or manufacture part of what you sell.
• You have several warehouses, or traceability by batch or serial number.
• You sell across several channels at once and need genuinely unified stock.
• You have different prices for wholesale and retail.
• You want to know your real margin per product and per channel.

6. The tax side, which is where it usually hurts

An integration that syncs products beautifully but taxes badly will create more work than it saves. These are the points to settle before connecting anything.

1. 01Set up your taxes in the ERP first. If an order arrives with a VAT rate the ERP does not have configured, it will assign whatever it can and you will be fixing invoices by hand.
2. 02Add a tax ID field to checkout. WooCommerce does not include one, so you need a plugin. Then check with a test order that the number genuinely reaches the customer record in the ERP, because that is where most failures happen.
3. 03Decide when invoicing happens. With Holded, the invoice is issued when you mark the order complete, which usually means on despatch rather than on payment. If days pass between the two, or worse, a month boundary, talk it through with your accountant before you build it.
4. 04Review sales outside your country. Intra-EU sales and exports need their own configuration, and that is defined in the ERP, not in the store.

7. The mistakes that break an integration

Almost every problem that reaches us comes from the same five things, and all of them are avoidable before connecting.

1. 01Empty or duplicated SKUs. This is cause number one. A product without a SKU does not sync and says nothing. A duplicate makes two products share stock and you end up selling what you do not have.
2. 02Syncing stock both ways without thinking. If the store and the ERP can both write the same figure, a simultaneous sale in both places leaves the number wrong. Decide who owns it and stick to it.
3. 03Not planning for returns. A sale syncs by itself, but a return needs the original invoice to exist in the ERP. Skip that and your credit notes end up orphaned.
4. 04Creating duplicate customers. Without a shared key, the same customer arrives three times with three different emails. Decide whether you match on email or tax ID and be consistent.
5. 05Logging nothing. If the integration leaves no trace of each sync, the day an order goes missing there will be no way to find out what happened. A reviewable error log is not optional.

8. How to set it up without breaking the store

You never connect straight onto the live store. This is the order we follow.