
The question
The stock in the shop does not match the inventory management software and we sold products we no longer had. How do I synchronise them?
The problem usually appears as the shop grows: you also sell in a physical store, on a marketplace or by phone, and WooCommerce stock is updated manually, with delays. The result is cancelled orders, unhappy customers and hours lost on corrections.
Proper synchronisation does not just mean “a plugin”. It means a few clear decisions about where the correct stock lives, what is transferred, how often, and what happens when something fails.
If you want us to handle this for you, see our service Stock sync or our service Software integrations.
Establish the source of truth
The first step is a decision: in which system is the stock correct? Most often it is the inventory management software or ERP, where goods receipts, transfers and stocktakes are recorded. The shop receives the quantities from there and reports sales back.
If two systems change stock independently, without a clear rule, no synchronisation will stay correct for long.
A shared code for every product
Synchronisation links products between systems through a shared identifier, usually the SKU or the product code from the inventory system. Without it, matching is done by name, which causes errors the first time a product is renamed.
- Every product and every variant (size, colour) has a unique code, identical in both systems.
- Codes are not reused for new products.
- Products that exist in only one system are flagged and handled explicitly.
Technical connection options
The choice depends on what the inventory management software allows. Ask the software provider what it offers and on what terms:
- Existing integration (official plugin or connector): the fastest, if it is maintained and does exactly what you need.
- API connection: the inventory management software and WooCommerce communicate directly; it is the most flexible option, but requires development and maintenance.
- Scheduled file exports and imports: a practical solution for software without an API, with longer delays.
- An intermediate layer (for example n8n, Make or custom code) that connects several systems and centralises rules and alerts.
Synchronisation frequency and direction
Stock can flow in one direction (inventory → shop) or both (shop orders reduce stock in the inventory system). Updates can be near-instant, triggered by events, or scheduled at a fixed interval.
The faster products sell and the lower the stock levels, the shorter the interval needs to be. Also bear in mind the call limits of the APIs involved and the fact that no synchronisation is instantaneous.
Special cases that break synchronisation
Discuss these situations before implementation, not after the first errors:
- Products with variants, where stock is kept per variant.
- Bundles and sets made up of several products.
- Cancelled orders, returns and products reserved for unpaid orders.
- Several warehouses or physical stores with separate stock.
- A safety buffer: you show “unavailable” before stock reaches zero.
Monitoring and errors
Any synchronisation will fail sometimes: an unavailable API, a product without a code, an expired authorisation. What matters is finding out immediately, not from an unhappy customer.
- An email or message alert when an update fails.
- A log of what was synchronised, when and with what result.
- A periodic check of the differences between the two systems.
- A person responsible for alerts.
Implementation steps
- You list the sales channels and establish the source of truth.
- You clean up the product codes and check the matching between systems.
- You choose the technical option based on what the inventory software allows.
- You set the rules: direction, frequency, buffer, special cases.
- You test on a few products, then on the whole catalogue, with alerts active.
- You monitor the first weeks and adjust the rules.
