Leaving Stocky? Export first. Choose after.
Stocky shuts down on 31 August 2026, and it already left the App Store, so an uninstall cannot be undone. Whatever you move to, the exports below are worth ten minutes this week. One of them cannot be re-created afterwards.
Your stock records exist only in Stocky. The only inventory history Shopify exposes to apps reaches back 180 days, so a Stocky stock report is the only copy of anything older: which days each product sat at zero, and for how long. That record is what lets a forecasting tool tell "slow seller" apart from "out of stock", because a sold-out day counted as a zero-sales day silently drags every average down. After 31 August there is nowhere to export it from.
Ten minutes, three exports.
What to export from Stocky
Column layouts vary by Stocky version and export settings, so Days of Cover matches every field by column name, never by position. These are the columns that matter in each file; extra columns are reported rather than guessed at.
- The catalogue exportSKU, product and variant title, unit cost, supplier, and lead time if you recorded one. This is the file that carries your costs, and costs are what profit-ranked reordering runs on.
- The purchase order export, open orders onlyPO number, supplier, SKU, quantity, and unit cost, plus the expected arrival date if your export carries one. We keep that date with the order, though no screen shows it yet; export it anyway, because Stocky will not be there to ask afterwards. Export only the orders you are still waiting on: every imported row is treated as stock on the way, so a received order in the file would be counted as inbound stock you already have on the shelf.
- The stock reportsHistorical stock on hand, and the adjustments report with its dates and reasons. Stocky's built-in history report totals stock by day rather than per product, so if you can produce a dated per-product file (SKU, date, quantity available), keep that one especially: it is the record of your past stockouts, and it exists nowhere else.
What each file becomes.
What Days of Cover reads from the export
Suppliers become your vendor list. Unit costs and lead times land on the matching variants. Open purchase orders arrive as placed orders with their lines. A dated per-product stock file, if you have one, becomes daily snapshots, and the sold-out stretches in it become corroborated stockout days, which are excluded from your sales velocity instead of dragging it down. Every imported number is labeled with where it came from, and a value you typed in yourself is never overwritten by an import.
- Matched by SKU, or reportedRows match by SKU first, then by product and variant title. An ambiguous row is skipped and listed with its row number, never guessed: a wrong cost on the wrong product is worse than a missing one.
- A per-row report, not a spinnerYou get a count of what imported, and every skipped or doubtful row listed with its row number and the reason, so nothing fails silently. Uploading the same file twice converges; it does not duplicate your purchase orders.
- The file itself is never written to diskIt is parsed in memory. What is kept: the parsed data, the file's name, and the per-row report, which quotes the cells that did not match so you can fix them.
Days of Cover is not a full replacement for Stocky. It does not do receiving, stocktakes, stock transfers, barcode labels, or multiple locations. If that workflow is what you are replacing, look at the purchasing apps built for it first, including Stockroom from MyWorks, and run a forecasting tool alongside. And one habit worth unlearning early, whatever you pick: marking a purchase order received here does not change your Shopify inventory. In Stocky it did.