Stocky is retiring: how to keep your supplier notes and cost history
Most of what's been written about the Stocky shutdown covers the obvious part: purchase orders and receiving now live in the Shopify admin, so that workflow has somewhere to go. The part nobody prepares for is quieter — the supplier context you built up over years, and the cost trail that tells you what you really paid. Here's what survives an export, what doesn't, and how to lift out the rest while you still can.
The deadline is earlier than August 31
Shopify's migration guide asks you to stop creating new purchase orders in Stocky about 14 days before August 31, 2026, and to receive and close all open, in-transit purchase orders in Stocky before the deadline.
So the practical cutoff for anything you still need to do inside Stocky — including exporting — is closer to mid-August. If you have purchase orders in transit with a two-week lead time, that date is already this week's problem.
What comes back from an export, and what doesn't
| What you had in Stocky | Does it come across? |
|---|---|
| Inventory quantities | Yes — and there's nothing to migrate. Shopify holds your stock levels already. |
| Purchase orders (as data) | You can export them to CSV. But in Shopify's words, "historical purchase orders can't be imported into Shopify." |
| Stocktakes / count history | No. "Your historical data in Stocky, such as old purchase orders and stocktakes, won't automatically move into Shopify." |
| Suppliers | No. Shopify's guide states it plainly: "Suppliers can't be exported from Stocky." |
| Supplier notes, terms, lead times, MOQs | No. These live inside the supplier records that can't be exported. |
| Cost history — how unit cost moved over time | No. See the next section. |
Why cost history has nowhere to land
On the Shopify side, "each product variant has a single static Cost per item field," and that cost stays fixed when you receive a purchase order or a transfer.
One number, entered by hand, that doesn't move. That's fine for a rough margin figure. It isn't a cost history, and it won't tell you next spring that a supplier's price crept up across four orders — because after each receipt, the previous number is simply gone.
Shopify's guide is direct about the gap: for weighted-average costing or automatic landed cost allocation, use a third-party inventory app.
The same is true of supplier detail. "Each product has a single Vendor field." To track multiple suppliers for one product, supplier-specific SKUs, lead times, minimum order quantities or case packs, the guide points you at variant metafields. Worth knowing before you design a spreadsheet, because a metafield is something apps can read and a spreadsheet cell isn't.
The preservation checklist
Work through this while Stocky is still writable — roughly, before mid-August.
1. Capture the supplier list by hand
There's no export, so open your supplier list and copy it out. Selecting the table in your browser and pasting it into a spreadsheet keeps the columns intact and beats retyping. Do this first — it's the only item here with no technical fallback.
2. Capture the fields one click deeper
Open each supplier and copy across contact name and email, payment terms, currency, lead time, minimum order value or quantity, and the free-text notes. The notes are the part people skip and regret — they hold the knowledge that isn't written down anywhere else.
3. Export your purchase orders to CSV
Do this even though Shopify can't import them. A PO export is the richest file you'll get out of Stocky: supplier names, line items, quantities and the price you paid, each with a date. Keep it — see step 6.
4. Export cost prices, and note the date
A cost list without a date is just a snapshot. With a date it becomes the first point in a new cost history, and every receipt you record after the move extends it.
5. Export stocktakes and inventory history
Anything you rely on for tax or audit won't move automatically, and there's no route back to it later.
6. Turn the PO export into a cost history
This step recovers most of what looked lost. Sort the export by SKU and date and you have, for each product: which supplier, what you paid, and when — a real per-SKU price trail assembled from data you already own. It doesn't reconstruct what Stocky computed, but it puts your history back in your hands, in a file you control.
7. Decide where it lands
A spreadsheet is free and genuinely fine for a handful of suppliers — nothing reads it for you, so reorder points stay a manual habit. Native Shopify plus variant metafields follows the guide's own recommendation and is structured, at one static cost field per variant. Or a costing app, which is what the guide suggests for weighted-average and landed cost.
Inventory quantities are already safe
Stock levels are one thing you don't need to migrate. Shopify is the source of truth for quantities and always was. Whatever you do about suppliers and costs, your inventory numbers aren't at risk in this move.
What our app does with the files above
We build Replenio, so treat this section as the interested part of the page.
Replenio is a purchasing app for Shopify — purchase orders, supplier records, barcode receiving — with the two costing behaviours the migration guide sends you looking for: it recalculates unit cost on every receipt using FIFO or weighted costing rather than holding one static number, and it allocates freight, duty and fees across the lines that actually carried them.
For the migration specifically: the supplier sheet from steps 1 and 2 goes in through a CSV template, notes column included, and becomes supplier records with lead times, terms, currency and MOQs. A guided Import from Stocky recognises the export columns Stocky does produce, so cost prices and reorder points come in without hand-mapping. And if you followed the guide and put supplier SKUs, lead times or MOQs into variant metafields, Replenio reads them directly — new products link themselves to the right supplier as you create them.
The purchase-order export from step 3 has its own import: feed it in and Replenio rebuilds your supplier list, links each product to the supplier you actually bought it from, and turns the file into a dated price series per SKU — the cost trail Shopify can't import. It's kept separate from inventory valuation on purpose, so importing years of old orders reports your history without distorting what today's stock is worth.
There's a free plan with no time limit covering purchase orders, receiving and weighted-average costing on one location, so you can check whether your data landed properly before deciding anything.
And if you'd rather do all of it in a spreadsheet: steps 1–6 still work, and they're worth doing this week either way. The supplier notes are the part you can't get back.
Questions about a specific export column or a migration edge case? Write to support@veltriolabs.com — we'll answer whether or not you're using our app.