A WooCommerce–Odoo stock mismatch needs an explanation before it needs a new number. The store may be reading a parent product’s shared stock, a connector may have missed an order change, or a correction may have repeated a movement already recorded elsewhere.
This guide is a reconciliation method for a third-party connector or custom integration; it does not assume a native Odoo–WooCommerce connector. References cover WooCommerce REST API v3, current WooCommerce guides and Odoo 20 API documentation, reviewed on 18 November 2026. Confirm the installed versions, extensions and connector behaviour before applying the method.
Identify the exact stock record
Choose one affected item and record its WooCommerce product ID, variation ID where applicable, SKU, Odoo product identity and relevant warehouse locations. Keep the parent product separate from the sellable variation. A matching display name is insufficient evidence that both systems are updating the same record.
WooCommerce’s variable-product guide explains that stock can be managed at product level, variation level or a combination. A variation without its own enabled stock management can draw from the parent’s stock when that is enabled. Establish whether the business intends a shared pool or independent quantities before changing the mapping.
The REST API variation reference distinguishes manage_stock, stock_quantity, stock_status and backorder settings. Ask the connector maintainer to inspect the intended record through the supported API. “In stock” is a status, not a numeric reconciliation.
Compare the same quantity at the same time
Define what Odoo quantity is intended for publication: which locations participate, how reservations are treated, and whether damaged goods or an agreed safety buffer are excluded. This is a business mapping decision, not a universal formula supplied by every connector.
Capture both sides at an agreed cut-off, including movements still waiting for processing. Record the source quantity, calculation, outgoing value, last confirmed update and current WooCommerce value. Avoid comparing an earlier storefront observation with a later warehouse balance after another order.
List every system or person allowed to write stock. Another plugin, a manual edit or a second integration may overwrite an otherwise correct update. Assign one authoritative calculation and document the permitted exceptions.
Check WooCommerce’s order and restocking controls
WooCommerce’s inventory settings distinguish enabling managed stock from display options. Its Hold stock timeout applies to unpaid orders in Pending payment, not On hold. Test those states separately; do not assume all unpaid orders reserve or release stock in the same way.
For returns, the refund guide documents an optional “Restock refunded items” checkbox. Confirm whether staff, WooCommerce or the connector controls the corresponding restock operation. A financial refund and a physical return require separate decisions, especially when the returned item is damaged.
| Mismatch pattern | WooCommerce evidence to inspect | Reconciliation question |
|---|---|---|
| Several variations share an unexpected quantity | Parent and variation stock-management settings | Was an independent quantity written into a shared pool? |
| A waiting order appears to release stock unexpectedly | Order status and Hold stock setting | Was the release expected for this state and connector rule? |
| A return increases availability twice | Refund restock choice and connector processing record | Which operation owns the stock effect? |
| Updates stop arriving | Webhook status, delivery log and receiver response | Which changes remain unprocessed since the last confirmed success? |
| The numbers agree but ordering behaves differently | Stock status and backorder settings | Does the storefront follow the agreed selling policy? |
Trace delivery before repeating work
The WooCommerce webhook guide documents Active, Paused and Disabled states, automatic disabling after repeated failures, and delivery logs under WooCommerce’s status tools. Check the selected topic and receiver response. An active webhook alone does not prove all earlier events were processed.
Match the order or product event to the connector’s recorded outcome. Identify the failed step and the last successful point. Before replaying anything, determine whether the integration sends an absolute quantity or applies a change to an existing quantity. Repeating a subtraction is different from setting a verified balance.
Odoo 20’s JSON-2 API guidance explains that separate calls run in separate transactions and warns about concurrent changes. Ask the maintainer to use the appropriate business operation and recovery design; a sequence of successful requests is not proof that the whole cross-system correction is consistent.
A fictional example: nine available, six displayed
A fictional bottle shop has 12 usable blue bottles in the agreed Odoo location, with three reserved. Its chosen publication rule produces nine available units at the test cut-off. The mapped WooCommerce variation shows six.
The team discovers that its test connector published the available balance of nine and then applied the same three-unit order reduction again. The proposed fix is to correct that duplicate effect and processing rule, not to add three units blindly whenever a difference appears. The team also verifies that the blue variation has independent stock management, rather than a shared parent pool.
After the controlled correction, replay the same test input and confirm that the balance remains nine when no new business movement occurs. This is a fictional failure scenario and acceptance condition, not an observed defect in WooCommerce or a named connector.
Close with evidence and a prevention owner
Keep the before-and-after quantities, identifiers, explanation, approved correction and repeat-test result together. Reconcile a small additional sample, then assign ownership of recurring discrepancy checks and disabled-webhook alerts. Coordinate any synchronization pause with the store and warehouse teams.
For broader stock preparation, use our Odoo inventory checklist. To review a recurring mismatch, explore Lava’s Odoo services or contact us with the affected workflow and connector details.
