Putting stock levels back after a bad sync

The accident

A supplier feed runs with the wrong column mapping. A stocktake app pushes yesterday's counts. A CSV lands with an extra zero. In minutes, thousands of stock levels across every location are wrong, and the damage is immediate in both directions: you oversell what you do not have, or you go out of stock on what is sitting in the warehouse.

Unlike a broken description, this one costs money the same day.

What StoreVault stores

On paid plans, stock levels are captured daily: the physical count per item per location. Not the reserved or committed quantities - those belong to orders in flight and are Shopify's to manage, and an app that overwrites them would break fulfilment rather than fix inventory.

On the free plan stock levels are not captured at all, so there is nothing to put back later. That is stated in the app rather than discovered during the accident.

How the restore works

You pick the moment before the bad sync. StoreVault builds a plan that lists every location and item it would touch, with the value now and the value it would write. You read it, and only then approve it.

The write itself is conditional: each change is sent with the quantity we expect to find, and Shopify refuses it if the stock moved after the plan was built. So a sale that happened while you were reading the plan does not get quietly undone - that item is reported as skipped instead.

Items or locations that no longer exist are skipped and counted, not silently dropped.

Why the plan is not optional

Stock is the one thing in a store where a wrong write is worse than no write. A restore that fired straight from a backup could take a warehouse that has genuinely sold through and refill it on paper, producing oversells for days. Showing every line first, and refusing any line that moved since, is what makes this safe to offer at all.

The same principle covers the rest of the product: nothing is written to your store without a plan you approved, and every restore can be undone. Details on the how it works page.