WooCommerce Stock Not Updating: Find Where the Sync Breaks
If WooCommerce stock is not updating, first separate order stock reduction, storefront display and an external sync mismatch. Then trace the affected product or variation through the process that owns it.
Read the guide
Search Field Notes
A useful next read.
36 field notes
No matching guide yet. Try “checkout”, “shipping” or “catalog”.
All Field NotesSeparate order stock, storefront display and external sync
If quantities do not fall after an order, check WooCommerce > Settings > Products > Inventory and the affected product’s stock-management settings. With quantity tracking disabled, the store keeps a stock status rather than a counted inventory. Compare the order state, notes and purchased variation before manually reducing stock.
If the admin value is correct but the product page is stale, review the displayed record and cache behaviour. If WooCommerce differs from a warehouse or POS, follow the external sync checks below. These are different starting points; changing the connector will not fix stock tracking that was never enabled.
Choose which system owns saleable stock
Decide whether WooCommerce, the warehouse or the ERP is the source of stock available to buy. Agree which system may send adjustments back. If both systems overwrite quantities independently, a staff correction can disappear after the next automated run.
Describe the exact mismatch: a new count never arrives, a changed value returns to its old value, or the store shows an item available that the warehouse cannot supply. Start with one item and its expected result. That is easier to trace than a screenshot of the whole inventory dashboard.
Choose which system owns stock
Use the same product identity and stock definition on both sides.
Stock owner
Choose the system that controls saleable quantity.
Source item
Identify the warehouse or ERP record being updated.
Check its stock definition and timestamp.Store item
Match the actual product or sellable variation.
Review identifiers and stock-management level.Applied result
Confirm the correct value and buying state after sync.
Recheck after the next controlled refresh.
Match the sellable variation, not just the parent
Check the source item code against the WooCommerce product or variation being sold. A clothing parent can represent several sizes while the warehouse holds each size separately. Updating the parent may leave the child the customer orders unchanged.
Compare a failing item with a working one. Look for duplicate SKUs, changed identifiers and newly imported records using a different code. Ask the catalog and connector owners to approve the mapping before changing it in bulk, and keep the old-to-new reference for later reconciliation.
Compare the meaning of the stock values
Physical units, available units and reserved units may be different fields. Agree which value reaches WooCommerce and how returns, pending orders and warehouse reservations affect it. Equal labels in two dashboards do not guarantee equal definitions.
Review the product’s stock-management level, status and backorder policy. Storefront availability may be wrong because the connector updates a quantity while another setting determines whether the variation can be bought. Check the complete buying state rather than forcing a manual stock status.
Trace the actual update mechanism
Find out whether the connector pushes events, polls on a schedule or imports a file. For one controlled update, check the source timestamp, delivery attempt, processing result and target record. Use a common time zone in the timeline.
If WooCommerce webhooks are involved, delivery evidence still needs the receiving system’s processing record. Ask who notices a disabled connection, expired permission or missed scheduled run. Keep credentials and raw customer/order payloads out of the shared report.
Test one safe change from end to end
Use a dedicated test item or isolated copy whose stock changes cannot affect customer orders. Record the starting state on both sides and change one approved value in the authoritative system. Check the target child record and the storefront after the update.
Then check whether a reverse sync or the next scheduled run overwrites it. Where the connector supports it, rehearse a delayed update and recovery. The point is to prove the route and identify the owner of a failure, rather than to make both screens agree for a moment.
Reconcile discrepancies before a bulk correction
Create an exception list with item references, source value, target value and reason for difference. Decide which value is authoritative before applying changes. Take a verified backup and define how catalog corrections can be reversed without rolling back current orders.
Give staff a procedure for a delayed sync and specify which manual edits are allowed. Recheck mapping when new variations, SKUs or warehouses are introduced. A stable stock operation depends on those rules and a reconciliation route as much as on the initial connection.
Common questions
Why is stock not reduced after an order?
Check quantity tracking at store and product/variation level, then compare the purchased item and order notes/state. If tracking is disabled, the store keeps stock status without counting units.
Why does a manual stock correction disappear?
An automated connector may overwrite it from the inventory source. Check ownership and the next sync record before changing the value again.
Why is the parent correct but a variation still wrong?
The connector may target the parent while stock is managed on the child, or the child’s identifier may not match. Trace the actual sellable variation.
Does a successful webhook prove the stock update worked?
No. Check the receiver’s processing result and the final mapped product state. Delivery and application are different stages.
Should we bulk-set products in stock to fix the mismatch?
No. Reconcile the affected records and stock definitions first. A blanket change can make unavailable inventory purchasable without solving the sync fault.