+91 98414 81435Free diagnosis
OdooBots
Loading
Integration · WooCommerce

Odoo WooCommerce integration

WooCommerce is a plugin on a WordPress site, which is both its advantage and the thing that makes integration need care. The store can be changed by anyone with admin access, plugins alter how orders and taxes behave, and the database is yours to read.

That flexibility is why a WooCommerce integration works best when the rules are explicit: one owner per field, a stock figure that accounts for reservations, and a queue for the records that will not go through.

Suresh BabuOdoo Solution Architect, 7+ years| Reviewed by Arun Kumar| Updated 20 October 2026| Covers Odoo 16–19, Community & Enterprise
Book a free Odoo diagnosis +91 98414 81435
0Odoo projects delivered
0Consultants & developers
One cataloguePublished from one side
ChennaiAmbattur, Tamil Nadu

Businesses running Odoo with OdooBots

Dhanalakshmi Industries logo Sanjeev Autoparts logo Electro Flux Equipments logo Anchor Marine Equipment Company logo NEXG logo PV Constructions logo SESS logo
Definition

What is Odoo WooCommerce integration?

Odoo WooCommerce integration keeps one catalogue, stock figure, customer and order record across the store and the ERP. Products and variations publish from whichever side owns them, forecast available stock is pushed as it changes, paid orders arrive as Odoo sales orders with their tax and shipping lines intact, gateway transactions attach to the invoice, and refunds raise matching credit notes.

WooCommerce tax behaviour depends on the plugins installed. Before mapping anything, we check what actually lands on an order rather than what the settings page says should.

Variation
A WooCommerce variable product option. Maps to an Odoo product variant, not to a separate product.
Order status
processing, completed, on-hold, refunded. Mapping these is where most WooCommerce integrations are left vague.
Gateway record
The payment reference from Razorpay, PayPal or another gateway, attached to the invoice for reconciliation.
Error queue
Records the sync could not place, held with their reason so a person can fix them.
What syncs

What moves between WooCommerce and Odoo

Six things move between a WooCommerce store and Odoo, and each needs an owner before it needs a connector.

Products and variations

Simple and variable products with attributes, images, SKUs, categories and price, published from the side that owns the catalogue.

VariationsCategoriesSKU

Stock

Forecast available quantity pushed to the store as it changes, per warehouse where you sell from more than one, with an optional buffer.

ForecastBufferWarehouse

Orders

A paid order becomes an Odoo sales order with its line items, coupons, shipping method and tax exactly as WooCommerce calculated them.

CouponsShippingTax

Customers

Billing and shipping addresses matched to existing Odoo contacts before a new one is created, including guest checkouts.

GuestAddressesDedupe

Payments

Gateway transaction references attached to the invoice so reconciliation has something to match on, whichever gateway the store uses.

ReferencesGatewaysReconciliation

Fulfilment and refunds

Despatch from Odoo moves the order to completed with its tracking detail, and a WooCommerce refund raises the credit note.

CompletedTrackingCredit notes
How it works

How a record travels between WooCommerce and Odoo

An order is paid on the store and arrives in Odoo as a sales order against a matched customer, with the tax and shipping lines WooCommerce calculated rather than recalculated. Stock reserves, the storefront quantity drops, and the warehouse picks. On despatch the order moves to completed with its tracking, the invoice posts, and the gateway reference sits on it for reconciliation.

Because WooCommerce behaviour depends on which plugins are installed, the mapping is built against real orders from your own store rather than against the documentation.

  • Orders arrive shortly after payment, with coupons and tax as calculated
  • Stock published as forecast available, with an optional safety buffer
  • Guest checkouts matched to contacts rather than creating duplicates
  • Despatch moves the order to completed and sends the tracking detail
  • Failed records held with their reason for a named owner to clear
Odoo woocommerce integration showing synchronised records between the two systems
Connected systems — how woocommerce and Odoo share one set of records.
Expertise · how we work

What we settle in week one of an Odoo WooCommerce integration

These are the decisions that are cheap to make now and painful to reverse once two systems have been exchanging records for a month.

  1. Which system owns the catalogue

    Decided per field. Price and stock usually belong in Odoo; images and descriptions often stay with whoever maintains the site.

  2. The SKU matching key

    Every product and variation needs a unique reference present on both sides. Missing or duplicated SKUs is the most common reason a first sync fails.

  3. Which stock figure is published

    Forecast available rather than on hand, and from which warehouse. This is what stops the store selling stock already reserved.

  4. Tax behaviour as it actually is

    We read real orders to see what your plugins produce, then map that. Trusting the settings page is how GST reporting goes wrong in month one.

  5. Order status mapping

    What processing, on-hold, completed and refunded each mean in Odoo, including partial fulfilment and cancelled-after-payment.

  6. Guest checkout handling

    Whether a guest becomes a contact, and how repeat guests with the same email are matched rather than duplicated.

  7. Who owns the error queue

    A named person and an alert. WooCommerce sites change when plugins update, and an unwatched sync diverges quietly.

Trust · honest advice

Where an Odoo WooCommerce integration needs work

We would rather say this before you buy licences than after. These are the areas where we scope real development, recommend a different tool, or tell you the connector will not reach.

Plugin-specific fields

Fields added by a third-party plugin are not in the standard mapping. They can be carried across; it is development and it is scoped.

Live stock at checkout

Stock is published rather than queried at checkout. A buffer absorbs the gap, which is how both systems are designed to work.

Subscriptions plugins

WooCommerce Subscriptions keeps its own billing schedule. Reconciling it against Odoo subscriptions is separate work.

Multisite and multi-store

Several stores on one WordPress multisite each need their own mapping and rules rather than sharing one.

Bundles and composite products

A bundle that must consume components in Odoo needs explicit modelling before it will cost correctly.

Site performance

A slow WooCommerce site slows the sync with it. Hosting problems show up as integration problems and are worth fixing first.

Our services

Our Odoo WooCommerce integration process

Connecting WooCommerce to Odoo is less about the connector than about agreeing what is true where, and what happens when a record will not go through.

  1. What you are connecting

    Understand your catalogue, which plugins affect orders and tax, how many warehouses you ship from, and whether guest checkout is used.

  2. Field and direction mapping

    Agree the owner of each field, the SKU key, the published stock figure and the status mapping, built against real orders from your own store.

  3. Build and configure

    Connect WooCommerce to Odoo using the standard connector where one fits, and build only what the connector genuinely cannot reach. See Odoo customization.

  4. Test with your own data

    Your records, in a test database, including the awkward ones — the cancelled order, the partial refund, the product that exists on one side only.

  5. Error handling and alerts

    A queue for failed records with a named owner and an alert, because an integration nobody watches diverges quietly and the divergence is found at audit.

  6. Go-live and monitoring

    Cutover with a reconciliation on both sides, then hypercare, then ongoing support and AMC.

Trust · what it costs

What an Odoo WooCommerce integration costs

We do not publish one integration price, because the same connector costs very differently depending on the factors below. We do publish what moves the number, and the price is fixed in writing before work starts.

  • Catalogue sizeVariable products with many attributes take real preparation.
  • Plugin complexityEach plugin that changes orders or tax adds mapping work.
  • SKU data qualityDuplicate or missing references are usually the biggest single task.
  • Number of storesEach store is its own mapping and its own rules.
  • Gateway countSeveral payment gateways means several reconciliation paths.
  • Historic ordersImporting past orders is optional and priced separately.
Why us

Why choose OdooBots for your Odoo WooCommerce integration

We map a WooCommerce store from its real orders, not from its settings page, because plugins change what actually lands on an order. That is why GST on our WooCommerce clients reconciles in the first month rather than the third.

Based inAmbattur, ChennaiTamil Nadu 600053, India
Phone+91 98414 81435Mon–Sat, business hours IST
Delivered630+ Odoo projects30+ consultants and developers
Versions supportedOdoo 16 – 19Community and Enterprise
FAQ

Odoo WooCommerce integration: frequently asked questions

Why integrate WooCommerce with Odoo ERP?
So the store and the business work from one catalogue, one stock figure and one customer record. Without it, stock is maintained twice, orders are re-keyed into the ERP, and the two systems disagree about what is available — which is how a store oversells and how month-end reconciliation becomes manual.
Can WooCommerce inventory update automatically in Odoo?
Yes, and it should run the other way too: Odoo publishes forecast available stock to the store as it changes, so quantities reserved for other orders are not offered again. Publishing on-hand stock instead is the usual cause of overselling.
How are WooCommerce taxes handled?
They are mapped from what your store actually produces on a real order, because plugins change tax behaviour. We read live orders before mapping rather than trusting the settings page, which is what keeps GST reporting correct from the first month.
Are guest checkouts supported?
Yes. A guest order is matched against existing contacts by email or phone before a new contact is created, so a repeat guest buyer does not end up as four separate customers in your ERP.
Does the integration handle refunds?
Yes. A refund in WooCommerce raises the matching credit note in Odoo, including partial refunds, with the gateway reference attached so the bank reconciliation has something to match against.
Is WooCommerce integration suitable for a growing business?
Yes, and the growth question is mostly about discipline rather than capacity. More stores, more warehouses and more gateways each add their own mapping, so the structure is worth agreeing while the catalogue is still small.
What happens when a record fails to sync?
It goes to a queue with the reason, an alert fires, and a named person clears it. This matters more on WooCommerce than elsewhere because plugin updates change behaviour without warning, and an unwatched sync diverges quietly.
Can OdooBots build a custom WooCommerce integration?
Yes. We use the standard connector where it fits and build only what it cannot reach — plugin-specific fields, bundles that consume components, or unusual tax treatment. See Odoo customization.
References

Sources and official documentation

Product capabilities stated on this page are documented by Odoo. The mapping advice, failure handling and limitations come from our own integrations.

Ready to connect WooCommerce to Odoo?

Tell us which plugins affect your orders and taxes, and how many warehouses you ship from. Those two answers shape the mapping, and the diagnosis call is free.

Book a free Odoo diagnosis +91 98414 81435