Connecting your store and inventory system: an automation checklist

Decide the source of truth

For each piece of data, one system should be in charge. Usually the inventory or warehouse system owns stock quantities and the store owns prices and product presentation, but your setup may differ.

Write the decision down. When two systems both think they own stock levels, each update can overwrite the other and the numbers drift.

Agree product identifiers, variants and stock definitions

Integrations match products by identifier, usually the SKU. Every sellable item, including each size and colour, needs a unique identifier that is the same in both systems.

Variants need particular care. Shopify tracks inventory per product variant (opens in a new tab), and in WooCommerce each variation can have its own price, stock settings and SKU (opens in a new tab), with a variation without its own SKU falling back to the product-level SKU. A shared or missing SKU can cause stock to update on the wrong item.

Also agree what stock means. Is it units on the shelf, units available to sell after open orders, or something else? Do bundles, pre-orders or backorders count? Ambiguity here causes most integration surprises.

Timing, duplicate events and failures

Systems often tell each other about changes using webhooks: automatic notifications sent when something happens, such as an order being placed. These can arrive late, twice or not at all, so the integration has to cope.

Shopify's developer documentation on verifying webhook deliveries (opens in a new tab) recommends verifying each notification, processing it in a way that is safe to repeat or recording delivery IDs to skip duplicates, and running periodic reconciliation. It also notes that failed deliveries are retried and that repeated failures can remove a subscription. WooCommerce disables a webhook after more than five consecutive delivery failures (opens in a new tab) and keeps logs for troubleshooting.

In plain terms: ask how the integration handles duplicates, what happens when a system is down, and how someone will know if updates have stopped.

Reconcile regularly

Even a well-built integration drifts over time. Schedule a regular comparison between systems, for example nightly, that reports differences for a person to review. Reconciliation is the safety net that catches missed or failed updates before customers do.

Separate alerts from automatic changes

Not every automation needs to change data. A low-stock alert tells a person to act; an automatic stock adjustment changes what customers see. Start with alerts where you can, and reserve automatic changes for well-tested, clearly owned data flows.

Questions to take to a specialist

Use these to start the conversation and to compare proposals.

• Which connection methods do our store and inventory system support on our current plans?
• Which system will own stock, price and product data, and how is that enforced?
• How will products and variants be matched, and what happens to items with missing SKUs?
• How are duplicate, delayed and failed updates handled, and how will we be alerted?
• How and how often will the systems be reconciled?
• Who owns the integration accounts, and what happens if you are unavailable?

Staged testing and handover

Test in stages. Start with a test store or a small set of products, check every scenario, then widen gradually. Include sales, refunds, manual stock adjustments, new products, variant changes and a simulated outage.

At handover, ask for a written description of the data flows, where logs and alerts can be found, how to pause the integration and who to contact for support. Make sure all accounts and keys are held by your business.

Common causes of stock mismatches

When stock figures disagree between systems, the cause is usually one of a few familiar problems. Knowing them helps you design tests and read reconciliation reports.

• Duplicate or missing SKUs, so updates land on the wrong variant or nowhere
• Manual edits made in the system that does not own stock
• Returns, exchanges or damaged stock recorded in one system only
• Bundles and kits that draw on component stock in one system but not the other
• Missed or repeated update notifications during an outage

Find a specialist

With these decisions made, find an ecommerce integration specialist and request a free 15-minute consultation, or browse the specialist directory. If you are still choosing between projects, see which ecommerce tasks to automate first.

Once stock data is reliable, it can also support customer-facing tools. Our guide to AI chatbots for ecommerce and human handover explains how to plan one safely.