Troubleshooting your switch

The usual cause is a purchase order or sales order import that moved the same stock your stocktake already counted, a second time. On a purchase order, check for an order imported with Track Inventory set to true and a Received Quantity for units that were already inside your stocktake count. On a sales order, check for a row carrying a ShippedQuantity for units that had already left the shelf before you counted — that also creates and dispatches a real shipment, which reduces on-hand stock the same way. Either way, correct the affected variant’s on-hand quantity with a new stock adjustment rather than trying to undo the import, the GRN, or the shipment. See Bring in open purchase orders and stock in transit and Bring in open sale orders.

Confirm the stock is at the order’s own location (stock at another warehouse doesn’t reach it) and that your stocktake for that location was authorized before you imported the order. An order imported before its location’s stock is set will show as Awaiting Stock until the next stock increase allocates it. See When Qoblex allocates stock automatically. If instead the order genuinely shipped before your stocktake, see the next question.

This is expected when an order shipped (or was already fulfilled on a connected channel) before you counted, so your stocktake correctly excludes those units while the order still asks to allocate them. See Already-shipped orders that show Awaiting Stock for how to ship it in Qoblex.

Confirm the inventory sync dropdown (Inventory levels Synchronization) is set to Sync from Qoblex to Shopify: it defaults to that value the moment you connect a new store. Confirm too that the Sync Inventory? toggle is ticked for the location in question, in the location mapping table — it also defaults to on for a new store, but saving with Do not sync clears every location’s box, so check it wasn’t left unticked from the rehearsal. If both the dropdown and the column are set correctly and a variant is still stale, the most likely cause is sequencing: turning sync on doesn’t push anything by itself, only a variant’s next quantity or allocation change does, so a variant you counted, received, or allocated before switching sync on won’t reach Shopify until it moves again. Make a small stock adjustment for that variant with sync already on, so the change fires and pushes the correct number. A product that no Shopify product import has linked to this store is never pushed at all. The usual reason is that the import couldn’t match it by SKU. If the import skipped it because more than one Qoblex product has that SKU (you’ll see a “Multiple products with the same SKU” notification), make the SKU unique, re-run the product import, then make the adjustment. If instead the import created a separate, duplicate product for it, that duplicate is the one now linked to Shopify, and re-running the import will keep updating the duplicate, not your original. First note any stock and open orders on the duplicate. Then delete the duplicate, correct your original product’s SKU so it exactly matches Shopify’s, re-run the product import so it links the original, and make a stock adjustment on the original for any quantity you counted against the duplicate. Re-running the import also moves the fulfillment cutoff described in the next question. See Shopify sync settings at go-live.

It depends on when the fulfillment happened relative to when this store’s Shopify product import last finished (or when you connected it, if you haven’t run one since), not on whether the order looks closed or already paid. A Shopify order fulfilled before that cutoff doesn’t touch Qoblex stock at all, whether it arrives through live sync or the historical Shopify order import. One fulfilled after that cutoff does reduce your Qoblex stock once it’s brought in this way, including a closed, historical order you import later, because Qoblex decides this from the fulfillment’s own date, not from the order’s status. A CSV import of that same order is a separate path: if the row carries a ShippedQuantity, it dispatches stock regardless of this date gate (see Bring in open sale orders above). If you’re bringing in historical Shopify orders after cutover, check whether any of them were fulfilled after that cutoff before assuming they’re inventory-neutral.

It depends on whether the order’s last update in WooCommerce falls before or after this integration’s product import completed, not on whether the order looks closed. An order last updated, and already Completed, Shipped, or Delivered, before that point is brought in (by live sync or by the manual order import) with inventory tracking turned off, so it doesn’t touch Qoblex stock. That cutoff isn’t set until the first product import finishes, though — before then it’s blank, and a blank cutoff means every order is tracked, so an order that changes between connecting and that first import finishing does move your stock (see the callout in WooCommerce sync settings at go-live). Unlike Shopify, re-running the WooCommerce product import later does not move this cutoff forward: it’s set once, the first time a product import for that store finishes, and stays fixed after that. If you’re bringing in historical WooCommerce orders well after cutover, check their WooCommerce last-updated date against when you first imported that store’s products, not against today.

If your subscription happened to be billed through Shopify, disconnecting the last store paying for it cancels that billing and notifies your account’s users automatically. This is expected. If you didn’t mean to end billing, see Plans and Billing for how Qoblex subscriptions and billing work, or book a planning call before you disconnect your staging store so billing carries over cleanly to your production store.