Description
Sync WooCommerce and Odoo automatically — orders, products, inventory, customers, invoices and payments, in both directions, with no CSVs and no manual re-keying.
This WooCommerce Odoo integration connects your storefront to your back office. Set it up once and every order, customer, product and payment reaches Odoo’s Sales, Inventory and Invoicing apps on its own. Read the setup guide.
Built for stores that cannot afford synchronization errors, this connector runs on an asynchronous background queue. This means a slow Odoo server will never slow down your WooCommerce checkout.
Fully compatible with Odoo 16, 17, 18, 19, and 20, WooCommerce HPOS, and block-based checkouts.
Automated Order Management (Bi-Directional)
- Triggered on Checkout: Orders export to Odoo before the customer even sees the thank-you page.
- Status-Based Rules: Choose exactly which orders export. (e.g., Send “Processing” orders automatically, but hold “Pending Payment” or “COD” orders).
- Quotation or Sales Order: Draft incoming WooCommerce orders as Odoo Quotations for manual review, or push them straight through as confirmed Sales Orders.
- Custom Numbering: Keep your exact WooCommerce order numbers in Odoo (with optional prefixes/suffixes) so your referencing stays clean.
- Discount & Shipping Mapping: Shipping costs and coupon codes land on their own specific Odoo order lines, keeping your accountant happy and reporting accurate.
- Odoo to WooCommerce Import: Pull Odoo sales orders down into WooCommerce on a schedule or on demand.
- Built for Volume: Orders travel to Odoo in batches of 25 rather than one at a time, which is what turns a backlog of several thousand orders into a job of hours rather than days.
Smart Invoicing & Payment Routing
- Automated Financials: Odoo invoices are created automatically based on the order statuses you define.
- Payment Journal Mapping: Route funds correctly. Stripe payments, PayPal funds, and Cash on Delivery can each land in their own dedicated Odoo payment journal — eliminating month-end reclassification.
- Automated Credit Notes: Processing a refund in WooCommerce automatically generates the corresponding credit note in Odoo.
- Invoice State Control: Separate your triggers. Choose one status to mark an invoice in payment and another to mark it fully paid.
Complete Product & Inventory Sync
- Two-Way Product Sync: Import and export products, including complex variations, attributes, nested categories, and high-res images.
- Intelligent Stock Rules: Sync Quantity Available or Quantity On Hand based on what your fulfillment team actually trusts. Limit stock sync to specific Odoo warehouses.
- Field Mapping: Carry custom data between systems. Map WooCommerce standard or custom fields directly to Odoo custom fields (
x_...), in either direction, including fields on variants. - Barcode & SKU Matching: Prevent duplicates. Link your existing Odoo catalog to your store via Internal Reference (
default_code) or Barcode matching. - Safe Updates: On re-import, choose to update everything, update price/stock only, or leave existing WooCommerce product details untouched.
- Images on Their Own Terms: Import images on a dedicated Media tab, at the size you choose (thumbnail through to the full 1920px), and an image is downloaded again only when Odoo’s copy has actually changed.
Customer & CRM Alignment
- Flexible Customer Handling: Create a unique Odoo contact for every buyer, log guest checkouts, route orders by tag, or map all B2C retail orders to one single “Web Sales” customer account.
- Role-Based Export: Choose which WordPress user roles sync to Odoo, keeping your ERP contacts free of store administrators and subscribers.
Built for Enterprise Reliability
We know what happens when a sync fails during a busy sales event. We built this connector to be transparent, resilient, and honest.
- Asynchronous Background Queue: Every sync runs through a background queue with automatic retries. Your site performance is completely isolated from Odoo’s uptime.
- Human-Readable Logs: No cryptic error codes. Get plain-language messages (e.g., “Odoo returned a temporary error — retrying automatically”). Full technical payloads are one click away for debugging.
- Secure Webhooks: Authenticated webhook callbacks confirm every synchronization result.
- Honest Dashboards: Live progress reporting. See exactly how many records synced and how many failed. Failures never quietly disappear from the total.
- Multi-Company Odoo Support: Explicitly pick which Odoo company your store synchronizes with.
Pricing & Transparency
Every single feature listed above is fully functional in the plugin itself. There are no disabled code paths, trialware gates, or hidden “Pro-only” toggle switches inside WordPress. The connection runs through the OdooConnector service.
- Free Plan: Currently 25 orders, 25 products, and 25 customers synced per month, free forever — enough for testing and very low-volume setups. The plugin’s Features tab always shows your store’s current allowance.
- Paid Plans: Removes the volume limits for growing stores. Cancel at any time, and the plugin shows the price and any free trial a plan carries before you subscribe.
- Real Support: Live-chat support is built directly into the plugin settings page — and yes, we provide support to Free plan users, too.
Technical Requirements
- WooCommerce 7.0 or higher
- Compatible with WooCommerce High-Performance Order Storage (HPOS)
- An active Odoo instance (URL, database name, username, password)
- Compatible with Odoo versions 16, 17, 18, 19, and 20
- Network access to the OdooConnector service
Ready in 3 Minutes
- Install and activate the plugin.
- Enter your Odoo URL and credentials, then click “Test Connection.”
- Place a test order in WooCommerce and watch it appear in Odoo instantly.
Installation
- Upload the plugin folder to
/wp-content/plugins/erp7-solutions-sync-for-odoo-and-woocommerce/(or install via WordPress admin) - Activate the plugin through the ‘Plugins’ screen in WordPress
- Navigate to WooCommerce → Odoo Connector and enter your Odoo URL, database, username, and password, then test the connection
- Configure sync preferences and save
- Optionally subscribe to the OdooConnector service from the Features tab for unlimited middleware order sync
FAQ
Is this plugin free? Does it require a paid service?
The plugin is free and every feature in it is fully functional. Synchronization runs through the OdooConnector cloud service, whose free plan currently includes 25 order, 25 product, and 25 customer syncs per calendar month — enough to run a small store or evaluate everything. Paid service plans remove the limits and add inventory/price sync; the plugin shows the price and any free trial before you subscribe.
How do I sync WooCommerce orders to Odoo?
Install the plugin, enter your Odoo URL and credentials, and enable “Export on checkout”. From then on every order is created in Odoo automatically — customer, order lines, invoice, and payment included. You can also export on specific status changes or with one click from the Orders tab.
Can I import products from Odoo to WooCommerce?
Yes. Product sync works in both directions: import your Odoo catalog into WooCommerce (variations, attributes, categories, and images included) or export WooCommerce products to Odoo, manually or on a schedule.
Are any features locked behind a paid upgrade in the plugin?
No — everything is built into this one plugin, with no license check, feature gate, or add-on to install. Here is what each plan of the OdooConnector service provides:
Free:
- Order export to Odoo — automatic on checkout, on status change, and manual
- Order import from Odoo, invoice creation, payment registration, and refund sync (credit notes)
- Product import and export, customer export
- 25 orders, 25 products, and 25 customers synced per month
- Dashboard, sync logs, and live-chat support
Paid:
- Everything in Free, with unlimited syncs
- Inventory and price sync (scheduled and on-demand, per warehouse)
- Scheduled automation with background processing
- Priority email support
- Cancel at any time — no contract
The Plans tab in the plugin shows the full comparison, and the Features tab shows your store’s current monthly allowance.
Does it work with Odoo Online (odoo.com) and Odoo.sh?
Yes. Any Odoo instance the OdooConnector service can reach over the internet works: Odoo Online (odoo.com), Odoo.sh, and self-hosted Odoo Community or Enterprise.
Which Odoo versions are supported?
Odoo 16 through 20 are supported. For Odoo 16–18 the service communicates with your Odoo instance over XML-RPC; for Odoo 19 and later it uses Odoo’s modern JSON-2 API. Your Odoo version is detected automatically when you connect — there is nothing to select or configure, and the detected version is shown in the API Connection bar.
How do I create an Odoo API key?
In Odoo, open Preferences → Account Security → New API Key, copy the generated key, and paste it into the Password / API Key field on the API Settings tab. The key is shown only once. An API key is required on Odoo 19 and later; on Odoo 16–18 your account password also works. Full step-by-step guide, including where to find your server URL, database name and username: https://odooconnector.cloud/docs/odoo-api-credentials
Is HPOS supported?
Yes, this plugin is fully compatible with WooCommerce High-Performance Order Storage (HPOS).
How do I sync WooCommerce stock with Odoo inventory?
Turn on Inventory sync in Settings → Products. Stock levels are read from Odoo on a schedule you choose and written to the matching WooCommerce products, matched by SKU. The inventory sync owns quantities on its own — no field mapping is needed for it, and a mapping rule cannot write stock, so the two can never fight over the same number.
How do I sync WooCommerce refunds as Odoo credit notes?
Both directions work. A refund made in WooCommerce is sent to Odoo as a credit note against the invoice for that order. A credit note raised in Odoo is imported back as a WooCommerce refund, matched to the order it belongs to — line by line when the note names lines, and as a total otherwise.
Does it work with Odoo Community edition?
Yes. The plugin reads and writes Odoo’s standard models — products, sale orders, contacts and invoices — all of which are in Community. You need the Sales and Inventory apps installed for product and order sync, and Invoicing if you want invoices and payments.
How do I connect WooCommerce to Odoo 17, 18, 19 or 20?
The same way for every version: paste your Odoo URL, database name, username and API key on the API Settings tab, then press Test Connection. Your Odoo version is detected for you — XML-RPC is used for Odoo 16 to 18 and Odoo’s JSON-2 API for 19 and later — so there is nothing to choose.
What is the difference between the free and paid versions?
Every feature is in the plugin itself, free. The paid plan governs how much you sync, never what works: the free plan currently includes 25 order, product and customer syncs per month, and Pro removes the limits. Nothing is disabled, no feature is held back, and your settings keep working if a plan lapses.
Screenshots






Changelog
2.3.8
- Fixed – Variable products import with variations the shopper can actually choose, on Odoo 19 and newer. A product arrived as a variable product with its variations underneath, but the parent had no attribute on it at all, so every variation read as “Any Size” and nothing could be put in the basket — which looks from the catalogue like the variations were never created. Odoo returns a template’s attribute lines as a list of ids and nothing more, and the import expands them with a second call; when that call was refused, answered with nothing, or — on a busy store Odoo is rate-limiting — answered “Too Many Requests”, every option was dropped and the parent was saved without any. The import now rebuilds the attributes from the variants themselves, which carry the same values and were already being read, so the parent gets its attribute and each variation keeps its own value. A product already imported in the broken shape is repaired the next time the import actually writes it — which, on a store with “Update existing products” switched off, or when nothing about the product has changed in Odoo since the last run, does not happen on its own; deleting the product and importing it again does. Products that imported correctly are unchanged, and no connector update is needed
- Fixed – Importing a variable product asks Odoo for its attribute values once instead of once per attribute. A product with three attributes made four calls where one would do, and on a store Odoo is already answering “Too Many Requests” every extra call is another that can be refused — which is how a product lost its attributes altogether. The values for every attribute line are now read together. Nothing about what is imported has changed, and no connector update is needed
- Fixed – Variable products import with their variations on the free plan. Working out which value each variation carries needs one lookup in Odoo, and the plugin asked for it with a search the service classes as a paid catalogue read, so a free store was refused with “an active plan is required” and every variation arrived with nothing selected. The lookup now reads the records by the ids it already has, which is the same records in one call and is allowed on every plan. Stores on a paid plan were never refused and are unchanged
- Fixed – The log says when Odoo would not answer for a product’s attributes. The call that expands a template’s attribute lines could fail without writing a single line to the sync log, so a store whose Odoo refuses that read saw variations that could not be chosen and had nothing to go on. The failure is now recorded as a warning naming the product, at the default logging level
2.3.7
- Fixed – The free plan’s monthly allowance is quoted from the service instead of always being printed as ten. Ten screens said it in so many words — the upgrade banner above the settings tabs, the banner on the WordPress dashboard, the upgrade card on the plugin’s Dashboard, the upgrade sidebar, the Free plan card and the Free-vs-Pro comparison on the Features tab, the usage block, the Upgrade to Pro card, the monthly-limit notice and the “limit reached” dialog all read “10 orders, 10 products and 10 customers” whatever the service was actually allowing, so a store given a larger allowance was told it had ten, and a store given a smaller one was promised ten it did not have. Each screen now names the allowance the service last reported, per sync type, and a store that has never had an answer is told the free plan has a monthly allowance rather than being quoted a number nobody has given it. The counters beside those sentences were always the service’s own figures and are unchanged, and no connector update is needed: the allowance has always travelled with them.
- Fixed – The order-sync callback checks who is calling before it writes anything to the sync log. A caller that did not know the store’s webhook secret was refused, as it always was, but the refusal was recorded first — so on a store with debug logging switched on, repeated calls from anywhere on the internet could fill the Sync Logs screen and bury the lines that matter. Nothing is written now until the secret matches. Stores on the default logging level were never affected
- Fixed – Customer export asks Odoo far less and finishes sooner. Each batch of customers now asks once which of them Odoo already knows and what addresses they already have, instead of asking twice over for every customer in turn — a batch of ten went from ninety Odoo calls to thirty-two. Exports are limited by how fast Odoo will answer, so fewer questions is the whole of the saving: a run of a thousand customers that took an hour and a half should now take a fraction of it. Nothing about what reaches Odoo has changed, and a store syncing one customer at a time works exactly as before
- Fixed – An order that reached Odoo without its tax now says which of the two reasons it was. The log warned “Line 163 has tax_ids but tax amount is 0. Check if tax IDs are valid in Odoo.” for every line whenever Odoo returned no tax — including lines carrying no tax at all, where the list of ids came out empty and the advice sent you looking for ids that were never sent. A line with no tax now says so, and says to set a default tax or add the matching tax in Odoo; a line whose ids Odoo would not apply still asks you to check those ids. Only the wording changed, so an order already exported is unaffected
- Fixed – Customer export stops asking Odoo for the same country list over and over. The country a contact belongs to was looked up once per batch, but the export starts a fresh connection for every batch of ten — so a run of a thousand customers asked Odoo which countries it has around three hundred times, for an answer that does not change. The list is now read once and kept for a day, on the Cache tab beside the other Odoo lookups, where Refresh clears it. A country code the list does not cover is still looked up directly, so a country you add in Odoo is found on the next sync rather than after the cache expires. Nothing about what reaches Odoo has changed, and no connector update is needed
- Added – A one-off invitation to review the plugin on WordPress.org, shown on the Dashboard once a store has had the plugin for a while and has seen it sync something — never on a store whose syncs have not worked, and never more than once however you answer it. Whether it is shown at all, and how many days a store must have had the plugin first, are set on the service side, so nothing is asked until we turn it on. A permanent “Leave a review” link also sits in the footer of the plugin’s own screens, for anyone who dismissed the card and later changed their mind. Needs the matching connector update
- Added – Deactivating the plugin now asks why, so a problem we could have fixed does not leave with you. One list of reasons and a box for anything else; it can be skipped or closed and the plugin deactivates either way, exactly as the link always did. Nothing is asked on a store that has not connected Odoo, because the answer travels on the same notification the plugin has always sent when it is switched off — there is no new connection and nothing extra is sent. The reasons come from the service, so they can change without you updating the plugin; a store that cannot reach it, or has not connected, sees the list the plugin ships, in its own language. Needs the matching connector update
- Fixed – Products import from an Odoo that has no Inventory app. The quantity fields are not part of Odoo itself, they come with the Inventory app, so on a database without it every product read was refused with “Invalid field ‘qty_available’ on ‘product.template'” and the whole batch was lost — on one store, every import batch for days. The connector now asks the Odoo once whether it has those fields and leaves them out when it does not, so products, prices, images and categories all import as usual and only the stock figures are missing. Stores that do have Inventory are unaffected and nothing extra is asked of them. Needs the matching connector update
- Fixed – An inventory sync now says why it brought no stock. The connector has always been able to explain a batch it could not answer fully — warehouses that no longer exist in Odoo, or an Odoo keeping no stock figures at all — and the plugin discarded every one of those messages, so the merchant saw quantities silently arrive as zero. The explanation now appears in the sync log, once per run rather than once per batch. Needs the matching connector update
- Added – The subscribe button, the plan badges and the WordPress dashboard banner show whatever free trial the plan on offer carries — including none at all, where the trial wording disappears rather than advertising days the plan will not give. A trial changed on the service side reaches the store within five minutes, with no plugin update needed, so the length a store is shown is always the length it would actually get. A store already part-way through a trial keeps the days it was given; a change applies to new subscriptions only. Needs the matching connector update
- Fixed – The Plans card no longer calls a finished subscription “Active”. When a cancellation is never closed off at the service, the stored record keeps reading “active”, and the card printed that word straight out — so a store saw a green Active badge, and a “Next billing date” already weeks in the past, directly above a button offering it a free trial. The card now goes by the date, as the rest of the screen already did: a subscription whose paid period has ended reads “Ended” and shows when access stopped. A store that is genuinely subscribed sees no change
- Fixed – The Plans card quotes the price of the plan you can actually buy. A store whose subscription had been ended by the service, or whose cancellation had run past the period it paid for, was shown the price of the plan it used to have — $9.00 a month, say — directly above a button charging $15.00 for the plan now on offer, with that plan’s trial length beside it; price and button disagreed about what was being bought. The card now describes the plan on offer the moment a store has no paid access, and goes on describing the store’s own plan for as long as it does — including a plan that is no longer sold to anyone, which the service now sends back for the stores still paying for it. A paying store whose record did not carry its own price or billing period was quoted the first plan in the list instead, and could be offered a switch to the yearly billing it was already on; both now follow the plan that store is really on. Needs the matching connector update for a retired plan to be named; the price a store is quoted is corrected either way
- Fixed – A store whose subscription the service ended is told when there is nothing for it to buy. The Plans card said “Subscribe again to continue using the paid service” and then, whenever the connector could not be reached or had no plan for that store, showed no button and no explanation at all — the “Pricing is unavailable right now” message the rest of the screen has always used could not be reached once a subscription was terminated. It now appears there too, saying which of the two reasons it is, with the Try again button beside it. A terminated store that does have a plan to buy sees exactly what it saw before, and no connector update is needed
- Fixed – Products with a single-value attribute import with their variation, price and SKU. A product whose Odoo template carried an attribute with one value — Size: Unica, say — arrived in WooCommerce as a variable product with no variations, no price and the rest of its import missing, and failed the same way on every run after that. Odoo reports a one-variant template’s internal reference as the template’s own, so the import put it on the parent product, and WooCommerce then refused the variation that needed it: a reference belongs to one product or variation, never two. The reference now goes to the variation, where stock and price already live, and the parent is left without one, which is how WooCommerce expects a variable product to be built. Products with two or more variants were never affected and are unchanged. A product already stuck in the broken shape repairs itself on the next import of it — the parent lets go of the reference and the missing variation is created, with its price arriving from the next inventory sync. A store that wants its own reference on the parent can set one with the new erp7sync_import_parent_sku filter
2.3.6
- Added – Move your settings from one store to another. Health → Move settings downloads a file of everything that can travel, and applies one downloaded from another store — so a configuration tested on a staging site does not have to be typed again on the live one. Your Odoo address, database, username and API key are never in the file, and neither is the connector the store talks to; those stay with the store they belong to. Settings that name a record inside one Odoo — the invoice journal, warehouse, taxes, sales team — are checked against the Odoo you are importing into and left for you to set when that record is not there, with a list saying which. Nothing is written until you have seen what would change The screen is available before Odoo is connected, which is when a new store is most likely to be applying a file; settings that name an Odoo record are applied as they came, and the preview says to check them once Odoo is connected
- Fixed – Stopping a sync no longer reports it as completed. Stop set the “Last … completed at” time, so an inventory sync stopped at 0 of 40 products read “Last inventory sync completed at” the moment of the Stop, and the same went for the other syncs. Stop now leaves the last real completion time alone. A time already overwritten by an earlier Stop stays as it is until the next completed run
- Fixed – Export Orders with nothing left to export no longer shows “Status: Failed 0 / 0”. When every order had already gone to Odoo, the button said “No orders to export” and the progress panel then reported a failed run. The panel is now left as it was, and the message still says there is nothing to export
- Fixed – Import Products says when product import is switched off. With “Enable Product Import” saved as off, the button searched Odoo, imported nothing and answered “No products to sync”, which looked like the import could not see new products. It now says the import is switched off and names the setting to turn on, without searching Odoo first
- Fixed – Export Orders no longer queues refunds as orders. WooCommerce stores a refund as an order of its own, so the button picked refunds up with the orders, and each one then failed with “Order not found” and counted as a failed order in the run’s progress. Only orders are picked now; refunds are still sent by the refund sync, when it is on, as before. The “sync recent orders” action had the same gap and is fixed too
- Fixed – Customer export spends less time on large customer lists. Every contact written to Odoo looked its country up again — three times for each customer, since a customer is written along with its billing and delivery contacts — so an export of a thousand customers spent a third of all its Odoo calls re-asking for the same country. A country is now looked up once for each batch the export works through, and a country code this Odoo has no country for is not searched for again either. The saving applies anywhere an address goes to Odoo, order export and order import included. Needs no connector update
- Fixed – A finished order export stops looking like a running one. The panel settled at “Progress: 2 / 3 (100%)” with a full bar, “Status: Completed” and the log reporting all three orders saved: the count was left at whatever was last read while the run was still going, and the last order to finish was missed every time. It now ends at the run total. The “Export Running…” button is also handed back when the run ends — opening the Orders tab while an export was going left it greyed out and labelled that way until the page was reloaded, with no way to start another export meanwhile
2.3.5.1
- Added – The dashboard can show a message written for your store as well as the general service news, instead of only one of them. A store the service has written to directly used to see that message and nothing else, so a general notice — scheduled maintenance, for instance — never reached it while the other was running. Both are now shown, yours first. Needs the matching connector update; with an older connector one message is shown, exactly as before
- Fixed – A Completed order of virtual products is invoiced. Products invoiced in Odoo on delivered quantities were never invoiceable when they were services, because a service has no delivery order and its delivered quantity stays 0 until someone types it in; the order reached Odoo and the log said “nothing to invoice yet (delivered quantities may be required)”. A Completed order now counts as delivered: the connector sets the delivered quantity on those lines only, then invoices. Products that ship through an Odoo delivery still wait for it to be validated, and an order invoiced on Processing still waits until something is delivered. Needs the matching connector update
- Fixed – Exporting products no longer creates the same Odoo product tag over and over. A tag that already existed was matched only by exact spelling and case, so every product carrying it added another copy, and Odoo filled with near-duplicate tags that split the products between them. An existing tag is now found and reused whatever its case, and only a genuinely new one is created
2.3.5
- Added – Shipment tracking reaches Odoo. With “Send shipment tracking to Odoo” on (Orders tab, off by default), the tracking number and status a shipping plugin stores on an order go to that order’s delivery in Odoo, with a note on the delivery and on the sales order naming the carrier, number and status. It reads WooCommerce Shipment Tracking, Advanced Shipment Tracking, AfterShip, YITH Order Tracking and Germanized, the fields many smaller plugins use, and any field you name under “Custom tracking fields”; the same number from two plugins is sent once. Only news is sent: a new number or a changed status. A private note on the WooCommerce order says what went where. “Tracking as a note line” also puts each new number on the Odoo sales order as a line. Where Odoo has no Delivery app the number goes in the delivery’s notes. Needs the matching connector update
- Added – “Get shipping status from Odoo” (Orders tab, off by default). Once an order’s deliveries are validated in Odoo, the WooCommerce order gets their tracking numbers — through WooCommerce Shipment Tracking or Advanced Shipment Tracking when installed, otherwise in the order emails — and a note naming the delivery, and is marked Completed unless “Complete shipped orders” is off. Open orders are checked once an hour in one request. Needs the matching connector update
- Added – “Mark the Odoo delivery done” (shown with shipment tracking, off by default). When every package on an order reports Delivered, the Odoo delivery is validated with its full quantities, once per order. This takes the stock out in Odoo. A delivery Odoo will not validate as it stands (a back order, lot or serial numbers) is left alone and the order notes why. Needs the matching connector update
- Added – “Odoo tax for each WooCommerce rate” on the Orders tab: map each WooCommerce tax rate to the Odoo sales tax it means. Matching by percentage cannot tell two Odoo taxes of the same rate apart — goods and services both at 20%, a reverse-charge 0% — and took the first. A mapped rate gets the tax you chose on product, shipping and coupon discount lines; a rate left on “Match by rate”, and every store that never fills the table, works as before. Needs the matching connector update
- Added – A Health check under Health → Overview. One button checks the site address (HTTPS, not a local address), WordPress’s scheduler, the OdooConnector service and, through it, Odoo access with your address, database and key, the chosen company, and whether results from Odoo can reach this site — and says how to fix each problem it finds. Needs the matching connector update; without it the Odoo checks show as not checked
- Fixed – Export Orders respects the export date range. The scheduled export and live orders kept to it, but the Export Orders button queued every unsynced order, so orders outside the range were sent to Odoo anyway. The button now picks only orders dated in the range, and the queue checks the range before sending, so an order queued before the range was set is skipped too
2.3.4
- Fixed – Orders sent to Odoo as they happen go into the sales team chosen under Sales Team Mapping. Only orders sent with Export Orders carried it; every other order landed in Odoo’s default team, so a store that picked “Website” found its orders under “Sales” (or its translation). Orders already in Odoo keep their team, and with no team chosen Odoo still picks one
2.3.3
- Added – Customer import (Odoo → WooCommerce) has controls you can find. The flow existed but had no screen: its switch and frequency were on a tab that is not in the menu, there was no way to start it, and nothing said whether it had ever run. It now has a card on the Customers tab with a switch, a frequency, an Import Customers button and the time of the last run. Addresses are optional: off, only the name, email and phone come over and WooCommerce’s own addresses are left alone. A run queues every customer Odoo has, instead of the same arbitrary 500 every time while the rest stayed unreachable. Contacts are read in batches rather than one at a time, so a thousand customers take a minute instead of eight. An Odoo too large for one run carries on from where it stopped. A run shows its progress and names each contact as it arrives — customer import was missing from the list the sync widget reads, so it reported nothing anywhere
- Added – Field mapping for Orders and Customers. The tabs said “Coming soon” for something three-quarters built: the sync paths already applied a mapping and only the editor was missing. Order export, order import, customer export and customer import now all map custom fields
- Added – Your settings are sent to support, redacted. An Odoo password, username, API key or webhook secret is never included — only whether one is set — so a configuration question can be answered without handing over admin access to your site
- Added – “Publish Odoo internal notes”, off by default. See the fix below for why it exists
- Added – “Update price on existing products”, on by default, under Products → Export to Odoo. Turn it off where Odoo owns pricing: an export then carries names, SKUs, categories and stock as usual but never changes the price of a product Odoo already has. A product being created is still given its price, because there is nothing to preserve. The mirror of “Update prices” on the import side, which has governed the other direction all along
- Added – “VAT from WooCommerce on each line” under Orders → Shipping and discounts, off by default. Each exported order line, shipping included, gets the Odoo sales tax matching the rate WooCommerce charged — a 5.5% book and a 20% gift card each get theirs, and an untaxed line stays untaxed — ahead of the Sync defaults order tax. A rate with no matching Odoo tax keeps the tax it would have had, and the log says so. The Orders tab now explains which tax a line gets with it on and off. Needs the matching connector update
- Added – The Odoo order shows the coupon codes used and the customer’s note from checkout. Neither reached Odoo before. Coupon codes on orders sent with Export Orders need the matching connector update
- Added – An exported order’s total is checked against WooCommerce’s. A few cents of rounding are covered by one untaxed “Rounding (WooCommerce total)” line on a service product, so Odoo’s total matches; a larger difference is logged and left as it is, not hidden. Needs the matching connector update
- Added – A warning under Export Stock while order export is on too. Each exported order already creates a delivery in Odoo, so writing WooCommerce’s quantity as on-hand takes sold items off twice
- Fixed – A product sync no longer attaches a category the product does not belong to. Products filed under one category came back from every sync with an unrelated one as well — women’s vests also under footwear, men’s windbreakers also under t-shirts — the same products and the same wrong pairing on every run, and correcting them by hand was undone by the next sync. The plugin records which Odoo category each WooCommerce category stands for, and nothing kept that one to one; where two of them claimed the same Odoo category, the import took whichever had been recorded first, which was not the right one. That record is now kept one to one, a category is identified by its name and its place in the tree rather than by whichever row answered first, and an import can take back a category it assigned and no longer sends. A category you added in WooCommerce yourself is left alone
- Fixed – Refunding part of an order no longer credits all of it in Odoo. A refund entered as an amount — the ordinary way to refund part of an order — arrived with no lines, which read as “refund everything”: a 25.00 refund against a 110.00 invoice raised a 110.00 credit note and marked the invoice reversed, crediting the customer 85.00 nobody had given them. An amount smaller than the invoice now credits that amount. A refund for the whole invoice still reverses it line by line, which keeps the invoice’s own tax treatment
- Fixed – Editing a customer’s billing address no longer adds another contact to them in Odoo every time. One customer reached six, and the oldest — the one Odoo displays and earlier records point at — held the address they had moved away from. The customer save was using the matcher written for order addresses, which keeps a separate contact for each distinct address because an order already shipped has to keep the address it went to. A customer’s own address book is now one invoice and one delivery contact, kept current
- Fixed – A refund imported from Odoo is no longer sent straight back to Odoo as a second credit note. Nothing asked where a refund had come from, so an imported credit note was raised again — crediting the order twice, once by whoever raised it in Odoo and once by this
- Fixed – An invoice whose reply was lost can be found again. When the call that creates an invoice timed out on the way back, Odoo had created it but the store never learned its number, and every retry was told the order was already invoiced and treated that as a failure. Refund export for that order then failed for good with “No invoice found in Odoo for this order”. A retry now returns the invoice that already exists
- Fixed – An imported product is not put on sale without a price. A new product was created published and out of stock with no price at all, and stayed that way until the separate inventory and price sync ran — on a daily schedule, a day of shop a customer could neither buy from nor judge. It is created as a draft now and published as soon as it has a price. This only happens where “Update prices” is on, because the price sync is what publishes it; with that …
