The Stocky Export Checklist: What to Pull Before August 31, 2026

Stocky stops working after August 31, 2026. Purchase orders, stocktake history and cost data export cleanly. Suppliers do not export at all. Here is the order to do it in.

4 min read

Exporting is the only part of the Stocky shutdown that is genuinely irreversible. Everything else is a decision you can revisit; this is a file you either have or you don't.

Work down this list in order. The order matters — the last two steps depend on the first three.

What can you actually export from Stocky?

Three things, per Shopify's own migration documentation:

WhatFormatWhy you want it
All completed purchase order reportsCSVSupplier performance, order cadence, and the raw material for rebuilding supplier records
Stocktake historyExportShrink analysis, and evidence for how a count reconciled
Historical cost dataExportLanded cost by SKU over time. Reconstructing three years of this later is miserable

Pull all three even if you cannot imagine needing them. The files are small and the alternative is a reconstruction project.

One thing to do before you export: close out what you can. Anything sitting in a draft or partially received purchase order is in a state the export was not designed around. Receive what has arrived, cancel what is dead, then export.

What can't be exported, and what that costs

Two hard limits, both worth planning around rather than discovering.

Suppliers cannot be exported from Stocky. This is the one that catches people. It is not a format problem you can work around with a clever query — there is no supplier export. Everything you know about a supplier lives either in your head, in your email, or implicitly in the purchase order history you just downloaded.

What you actually have to rebuild, per supplier:

  • Contact details and the person you actually deal with
  • Lead time, and how much it really varies from the quoted number
  • Minimum order quantities and case-pack or container constraints
  • Payment terms
  • Unit costs, and how they have moved

The PO export gets you the last two and lets you infer lead time from order and receipt dates. The rest is manual.

Historical purchase orders cannot be imported into Shopify. The CSVs you just pulled are for your own records and for whatever you move to next. They do not load back into Shopify Admin. If you plan to run supplier scorecards or landed cost analysis on past orders, that analysis now happens in your files, not in the platform.

How long do you have after August 31?

Shopify says you will have read-only access to export your data for at least 90 days after August 31, 2026.

Read the wording carefully. It is a minimum, not a commitment to a date, and it is read-only — enough to retrieve something you missed, not enough to run a migration through. Treat August 31 as the deadline and the window as insurance.

The related deadline is quieter and worse: any Stocky APIs stop working on August 31, 2026. If anything you own reads from Stocky programmatically — a reporting script, a middleware connector, a spreadsheet someone wired up years ago — it stops that day, and it will fail silently rather than loudly.

Do not uninstall Stocky to tidy up

Stocky was delisted from the Shopify App Store on February 2, 2026. You cannot reinstall it.

So the instinct to uninstall the app once you have "finished" is the one genuinely unrecoverable mistake available here. Leave it installed until the date passes. There is no upside to removing it early and no way back if you were wrong about having exported everything.

When Shopify Admin is all you need

For a lot of former Stocky users, the export is the hard part and the rest is straightforward: purchase orders, transfers, receiving, quantity adjustments and inventory history are all native in Shopify Admin now. If that is the half of Stocky you used, migrate and stop reading. It is included, it works, and paying for a tool to do what Admin now does for free is a bad trade.

Where Shopify Admin genuinely does not follow is the planning half — demand forecasting from sales velocity and seasonality, reorder points, and safety stock sized to actual demand variability. Those were the lighter half of what Stocky did and they did not make the move.

Which half you used is the whole decision, and we walk through it properly in the honest guide to what replaces Stocky. The head-to-head on what Admin does and does not cover is in Planster vs Shopify Admin, and if you want to know what the planning layer costs before you go looking, our pricing is flat and on one page.

The supplier records you are about to rebuild by hand are worth rebuilding somewhere the terms actually drive your ordering — see supplier management — and the purchase-order history you are exporting is the input a demand forecast needs before it can tell you what to order next.

The order to do it in

  1. Close out draft and partially received purchase orders.
  2. Export completed purchase order reports, stocktake history, and cost data.
  3. Rebuild supplier records by hand, working from the PO export. Start this first, it takes longest.
  4. Find anything that reads the Stocky API and rewire it.
  5. Migrate operations to Shopify Admin.
  6. Leave Stocky installed until September.

Sources

  1. Stocky won't be available after August 31, 2026, and any Stocky APIs will stop working on that datehttps://help.shopify.com/en/manual/products/inventory/transitioning-from-stocky (accessed 2026-08-10)
  2. After the shutdown you will have read-only access to export your data for at least 90 days after that datehttps://help.shopify.com/en/manual/products/inventory/transitioning-from-stocky (accessed 2026-08-10)
  3. Exportable from Stocky: all completed purchase order reports as CSV files, stocktake history, and historical cost datahttps://help.shopify.com/en/manual/products/inventory/transitioning-from-stocky (accessed 2026-08-10)
  4. Suppliers can't be exported from Stocky, and historical purchase orders can't be imported into Shopify Adminhttps://help.shopify.com/en/manual/products/inventory/transitioning-from-stocky (accessed 2026-08-10)
  5. On February 2, 2026, Stocky was delisted from the Shopify App Store, so it can no longer be reinstalledhttps://help.shopify.com/en/manual/products/inventory/transitioning-from-stocky (accessed 2026-08-10)

Common questions

Can you export supplier data from Stocky?

Suppliers cannot be exported from Stocky. Shopify states this plainly in its migration documentation, and it is the single most disruptive part of the shutdown, because supplier records are the part of the dataset that took the longest to build. Contact details, lead times, minimum order quantities and payment terms all have to be reconstructed by hand from purchase order history and email, so start that work early rather than in the final week.

What can be exported from Stocky?

Three things export cleanly, according to Shopify's own migration guide: all completed purchase order reports as CSV files, your stocktake history, and your historical cost data. That covers most of what you need for reporting and for reconstructing landed costs later. It does not cover suppliers, and it does not cover anything that lives only inside an incomplete or draft purchase order, so close out what you can before exporting.

How long do you have to export after Stocky shuts down?

Shopify says you will have read-only access to export your data for at least 90 days after August 31, 2026. That is a genuine safety net rather than a hard second deadline, but it is worded as a minimum and not a guarantee of any particular date. Treat August 31 as the real deadline and the read-only window as insurance against having missed something, not as extra time you have budgeted for.

Can historical purchase orders be imported into Shopify?

Historical purchase orders cannot be imported into Shopify. The CSV exports are for your own records and for whatever system you move to next, not for loading back into Shopify Admin. This matters for anyone planning to run supplier performance or landed cost analysis on past orders, because after the migration that history lives in your files rather than in the platform, and nothing will rebuild it for you.