What actually happens to your Stocky data on 31 August 2026

Shopify retires Stocky on 31 August 2026. Most of the advice going around right now is about picking a replacement app. That is the second question. The first one is narrower and has a deadline attached: which of your numbers live in Stocky, and which live in Shopify?

They are not the same set, and only one of them disappears.

What stays where it is

Your products, variants, SKUs, barcodes and inventory levels are Shopify records. Stocky reads them. They are unaffected by the shutdown, and you do not need to export them to keep them.

If the worry is “will I lose my stock counts”, the answer is no.

What leaves with Stocky

The numbers Stocky added on top are the ones with a deadline:

• Bin and location codes — where a thing lives in your stockroom.
• Minimums and maximums — the thresholds you set per product.
• Purchase order history — suppliers, costs, receiving records.
• Stocktake history — past counts and their variances.

None of these exist anywhere in Shopify. If they are not exported before the date they are gone, and rebuilding bin codes for a few thousand SKUs by walking the stockroom is a job measured in days.

Export first, decide later

The useful order is: export everything now, choose a replacement afterwards. An export costs you twenty minutes. Choosing badly under time pressure costs considerably more, and you cannot go back for the data once the app is off.

Take the CSV exports Stocky offers, keep the raw files, and do not reformat them. Whatever you move to will want the original columns.

Checking an export is actually usable

An export that downloaded successfully is not the same as an export that will import successfully. The usual problems are dull and fixable: the same SKU appearing on two rows, two products sharing a barcode, rows carrying neither a minimum nor a maximum, rows with no bin at all, and columns that were renamed at some point and no longer match what an importer looks for.

Our Stocky sunset readiness check reads a CSV in your browser, names those specific problems and scores the file out of 100. Nothing is uploaded and nothing is stored — it is JavaScript on the page reading a local file.

Bin codes are a separate question. A code that reads fine to a person can still be one a scanner will not return cleanly, and that is worth catching before you print a sheet of labels rather than after. The bin label generator checks each code and tells you which ones it rejected and why.

The part nobody exports

There is one thing no export contains: the order your staff walk the stockroom in. It lives in the head of whoever does the refill run each morning.

Write it down this week. It is the cheapest thing on this list to capture and the most annoying to reconstruct, whichever app you end up in.