Online Store and Odoo Synced with n8n

n8n use case · E-commerce

How to connect your online store to Odoo using n8n: every paid order lands in Odoo instantly with its customer, taxes and shipping costs; stock flows back to the store; the tracking number reaches the customer, and returns follow the same path in reverse. It works with Shopify, WooCommerce, PrestaShop and marketplaces.

Information reviewed on 7 November 2026. Use case implemented with n8n by Binovo FutureAI, Certified n8n Expert Partner.

The problem

When the online store and the ERP run separately, someone copies orders by hand, the website stock doesn’t match the warehouse, and customers ask about their shipment because nobody sent them the tracking number. Closed connectors help, but they tend to fall short as soon as you have special pricelists, several warehouses, bundles or one more marketplace.

Common symptoms

  • Orders keyed in twice.
  • Sales of out-of-stock products.
  • Duplicate customers in the ERP.
  • Invoices that don’t match what was charged on the website.

What we’re aiming for

  • A paid order is in Odoo within seconds.
  • A single set of stock and prices, managed from Odoo.
  • The customer informed at every step.
  • Your own business rules, not the connector’s.

How n8n solves it, step by step

Scroll through the steps: on the right, the workflow node that is working at each moment lights up, along with the data it handles (sample data).

n8n workflow · Online store and OdooExample
  • WStore webhookTrigger: paid order
  • CCustomerFind or create in Odoo
  • OSales orderLines, taxes and shipping
  • SStockFrom Odoo to the store
  • TShippingTracking sent to the customer
  • €Invoice and returnsClosing the cycle
event: orders/paid
order: #10482
amount: 189.90 EUR
signature: verified
search: email = cliente@ejemplo.es
result: found (id 2391)
action: new shipping address
sale.order: S04821
lines: 3 (1 bundle itemised)
shipping: 4.90
fiscal position: Mainland Spain
status: confirmed
product: REF-2210
odoo stock: 14
shopify: 14 (updated)
amazon: 14 (updated)
delivery order: WH/OUT/03312
carrier: shipping carrier
tracking: ES000000000
store: order marked as shipped
invoice: FV/2026/01877
verifactu: registered
return #10399: credit note created
Step 1 of 6

The store notifies n8n

Shopify, WooCommerce or PrestaShop call the n8n webhook as soon as an order is paid. The workflow verifies the notification’s signature, so that only authentic notifications are accepted, and stores the original order in case it needs to be reprocessed.

Step 2 of 6

The customer is searched for before being created

n8n looks up the customer in Odoo by email and tax ID. If they exist, it reuses the record and updates the shipping address; if not, it creates them with their tax details. This puts an end to duplicate customers, one of the most common problems in these integrations.

Step 3 of 6

The sales order is created in Odoo

The order enters Odoo with each product identified by its reference, bundles itemised, discounts, shipping as its own line and the right fiscal position (mainland Spain, Canary Islands, EU or export). It is confirmed automatically and sends the delivery order to the warehouse.

Step 4 of 6

Stock flows back to the store

Every inventory movement in Odoo updates the available stock in the store and in the connected marketplaces. That way you don’t sell what you don’t have, and Odoo is the single source of truth for inventory and prices.

Step 5 of 6

The customer receives their tracking number

When the delivery order is validated, n8n requests the label from the shipping carrier, sends the tracking number back to the store, which notifies the customer, and records it in Odoo.

Step 6 of 6

Invoice and returns

The invoice is generated in Odoo with the amount actually charged and, where regulations require it, registered with Verifactu or TicketBAI. A return in the store creates the return and the credit note in Odoo by the same path.

Applications involved

Application Role in the workflow
Shopify, WooCommerce or PrestaShop Source of orders, customers and returns via webhooks and API.
Amazon and other marketplaces Orders and stock through their own APIs.
Odoo Sales, Inventory and Accounting Customers, orders, warehouse, invoices and credit notes.
Shipping carriers Labels and tracking numbers via API.
Payment gateway Payment verification and reconciliation (see the payments with webhooks use case).

Do you use other applications? n8n has more than 2,000 integrations and connects to any software that has an API. We cover it in n8n integrations.

Variants of the same use case

Multiple warehouses

The workflow decides which warehouse fulfils the order based on stock and destination.

B2B with pricelists

Business customers with their Odoo pricelist also applied in the store.

Catalogue from Odoo

New products, prices and images published to the store from Odoo.

Physical stores

The POS and the website share stock and customers in the same Odoo.

Control, security and human in the loop

  • Safe reprocessing: each order is stored exactly as it arrived, and if something fails it is reprocessed without duplicating.
  • Authentic notifications: the signature of every webhook is verified before acting.
  • A single source of truth: stock and prices are governed from Odoo.
  • Visible exceptions: products without a reference or questionable addresses go to a review queue with a notification to the person in charge.

What we measure to know it works

Before we start, we take a snapshot of the current process and, once the pilot is running, we compare:

  • Time from payment until the order is in the warehouse.
  • Orders that have required manual intervention.
  • Stockouts or sales without available stock.
  • Customer enquiries of the “where is my order?” kind.

How we implement it

  1. Process assessment. Volume, applications, usual exceptions and who approves what.
  2. Workflow design in n8n together with you, with the business rules in writing.
  3. Pilot in controlled production, with human review of everything at the beginning.
  4. Go-live with error alerts, secure credentials and documentation.
  5. Maintenance and training so that your team understands and can adjust the workflow.

Frequently asked questions

Can Shopify, WooCommerce or PrestaShop be connected to Odoo using n8n?

Yes. n8n receives orders via webhook and creates them in Odoo with their customer, taxes and shipping costs, and sends stock and the tracking number back to the store. It works with the main platforms and marketplaces that offer an API.

What advantage does it have over a closed connector?

The workflow is visible and adapts to your rules: bundles, multiple warehouses, B2B pricelists, fiscal positions or additional marketplaces. And if something fails, you can see at which step and reprocess it.

How are duplicate customers and orders avoided?

The workflow searches for the customer by email and tax ID before creating them, and stores the identifier of each store order so it is never created twice, even if the notification arrives repeatedly.

Is stock updated in real time?

Yes. Odoo inventory movements update the store and the connected marketplaces as soon as they occur, or at short intervals if the platform limits it.

What about invoicing with Verifactu or TicketBAI?

The invoice is generated in Odoo, which in Binovo implementations is already set up for Verifactu and TicketBAI.

Do your online store and your ERP talk to each other?

Tell us which platform you use and how you currently manage orders and stock, and we’ll propose the workflow.

Request information943 569 206

More n8n use cases

Shall we talk about your n8n automation?Request information