How to export your Stocky data before it's gone

Shopify removed Stocky from the App Store on 2 February 2026, and the app stopped working on 31 August 2026. What's left is read-only access so merchants can export their data, and that access is only promised for a limited time. If you haven't pulled your purchase history out yet, this is the week to do it.

The good news is that the export is simple. The bad news is that it's slow, it's one file per purchase order, and some of the data you'll want most can't be exported at all. This guide walks through the whole job in the order we'd do it.

Key takeaways

• Stocky exports one CSV per purchase order: Apps → Stocky → Purchases → open the PO → Download → CSV. There's no bulk export.
• Suppliers can't be exported. Rebuild the supplier list by hand from your POs and your inbox.
• Export open purchase orders first, then received orders from the last 12–18 months. Older history is nice to have.
• Product costs, SKUs and barcodes live in Shopify itself, so export them from Shopify's product CSV rather than relying on Stocky.
• Check every file opens and its totals match the PO before you lose access.

What you can and can't get out

Before you start clicking, be clear about what each source holds.

Anything else you relied on in Stocky that doesn't have a download button, such as notes on purchase orders or supplier settings, should be copied into a spreadsheet or captured as screenshots while you can still see it.

Step 1: make a list of every purchase order

Open Apps → Stocky → Purchases and write down every PO before you download anything: number, supplier, status, and the date it was raised or received. A simple spreadsheet with one row per PO is enough.

This list does three jobs. It tells you how much work there is, it lets you prioritise, and at the end it's your checklist for confirming nothing was missed.

Step 2: prioritise

You might not have time to export everything, so work in this order:

1. Open purchase orders. These are stock you've paid for or committed to and haven't received. Your next system needs them as stock on order, or it will tell you to buy the same goods again.
2. Received purchase orders from the last 12–18 months. These give you real supplier lead times (the gap between ordering and receiving) and recent unit costs.
3. Older history. Useful for long-term cost trends and audits, but rarely needed for planning.

Here's why prioritising matters. If you have 180 purchase orders and each one takes about a minute to open, download and file, that's 180 minutes, or three hours of clicking. If 20 are open and 70 were received in the last 18 months, the first two groups are 90 files, about an hour and a half. Do those today and the rest when you can.

Step 3: download each purchase order

For each PO on your list:

1. In Shopify admin, go to Apps → Stocky → Purchases.
2. Open the purchase order.
3. Choose Download → CSV.
4. Save the file into a dedicated folder and rename it consistently, for example PO-1042_Acme-Packaging_received.csv.
5. Tick it off on your list.

Consistent names pay off later. When you're checking files or importing them, you can see the PO number, supplier and status without opening anything. Keep open and received orders in separate subfolders if your next system imports them differently.

Step 4: check the files while you still can

A file that won't open, or that's missing lines, is only fixable while Stocky is still readable. Spot-check as you go, and fully check every open PO.

The quickest check is the total. Suppose PO-1042 has three lines:

120 × 4.50 = 540, 60 × 7.25 = 435 and 200 × 1.10 = 220, so the lines add up to 540 + 435 + 220 = 1,195. If the PO total shown in Stocky is also 1,195, the file is complete. If it isn't, re-download it.

Also check that SKUs in the files match SKUs in Shopify. Lines that refer to products you've since deleted or renamed will need mapping by hand during import, and it's easier to note them now.

Step 5: rebuild your supplier list

Because Stocky can't export suppliers, you need to recreate them. Start from the supplier names in your PO list, then fill in the details from emails, invoices and contracts. One row per supplier, with these columns:

• Supplier name, spelled exactly as it appears on your POs
• Contact name and email for purchase orders
• Currency
• Payment terms (for example 30% deposit, balance before shipping)
• Quoted lead time in days
• Minimum order quantity or minimum order value
• Notes: shipping terms, holiday closures, anything a new buyer would need to know

Watch out for the same supplier under two names, such as "Acme Packaging" and "ACME Packaging Ltd". Pick one and use it everywhere. Most import tools match suppliers by name, so inconsistent spellings create duplicates.

Step 6: export products and costs from Shopify

Unit costs, SKUs and barcodes are stored on your Shopify products, not in Stocky, so they survive Stocky's shutdown. Export your products from Shopify admin to CSV anyway. The export includes the cost per item for each variant, which gives you a dated snapshot of costs to compare against what your new system imports.

Importing your Stocky data somewhere else

Whatever you move to, the same rules make an import go smoothly.

Combine the files if you need to

Some tools accept many files at once. Others want a single CSV. If all your PO files have identical columns, you can combine them on a Mac or Linux terminal from inside the folder, keeping one header row:

head -n 1 PO-1042_Acme-Packaging_received.csv > ../all-pos.csv
for f in *.csv; do tail -n +2 "$f" >> ../all-pos.csv; done

Writing the combined file to the parent folder stops the loop from reading its own output. Open the result and check the row count equals the sum of the lines across your files.

Import open orders as stock on order, not stock on hand

An imported purchase order should never change your on-hand quantities. On-hand stock comes from Shopify. Open POs should show up as stock on order so reorder suggestions account for them, and received POs should be stored as history.

Do a dry run

Import into a test, or use a validation step if your tool has one, and read every warning. The usual problems are dates in an unexpected format, SKUs that no longer exist, and supplier name mismatches.

Make re-imports safe

You'll probably import twice: once to find problems and once after fixing them. Make sure your tool matches POs by number so a second import updates rather than duplicates.

How Stokrio handles Stocky exports

Stokrio's Stocky import was built around exactly these files. You select every per-PO CSV at once and Stokrio combines them, matches the column names automatically, and creates suppliers from the supplier names on your POs, since Stocky can't export them. A dry run lists every error and warning by file and row before anything is saved, and purchase orders match by number, so re-importing a fixed file never duplicates data. Imported POs don't move stock: open ones count as stock on order, and received ones with dates become measured supplier lead times. There's more on the move itself on our Stocky alternative page and in our migration checklist.

After the import

Once your data is in, run one buying cycle and compare the suggestions with what you'd have ordered by hand. Differences nearly always trace back to a missing open PO, a supplier lead time that wasn't entered, or a product cost that didn't carry over. Fix those and you'll have a cleaner purchasing setup than you had in Stocky.