How to Migrate From Stocky: POs, Suppliers and Cost Data
How to migrate from Stocky: what to export, what can't come across, how to rebuild suppliers and open POs, and how to check stock and costs after the move.

On this page
- The two Stocky migration routes
- Step 1: Export everything you want to keep
- What the Stocky API returns, if your Stocky still works
- What can't come across from Stocky
- Step 2: Rebuild your suppliers and pack sizes
- Step 3: Settle open and partially received purchase orders
- Step 4: Choose where your Stocky data lands
- Step 5: Check stock and costs after the move
- Stocky migration checklist
- Migrating from Stocky to Channel Bay
Key Takeaways
- Migrating from Stocky comes down to four jobs: export what you can, rebuild what you can't export, settle open purchase orders and check stock and costs afterwards.
- Shopify says "Suppliers can't be exported from Stocky". Only stores whose Stocky still works can pull complete supplier records, through the API.
- No route carries supplier to product links, PO status or received quantities, so a partially received PO arrives looking fully received.
- Close open purchase orders before you move, or recreate only the remaining quantities in your new system.
- Historical POs can't be imported into Shopify. Keep your exports as a price and audit record whichever system you move to.
To migrate from Stocky, export everything Stocky will still give you, rebuild what it won't (your suppliers and their product links), settle any open purchase orders (POs), then check your stock and costs in the new system before you rely on it. The order matters, because some of that data can only be exported once, and some of it can't be recovered at all.
How much you can bring across depends on whether your Stocky still works. For most stores it doesn't: Shopify says Stocky "is no longer available as of August 31, 2026", and that "Stocky APIs stopped working on August 31, 2026" (Shopify Help Center). Those stores have export files only. A smaller group still has a working Stocky, API included, until 1 March 2027. If you're not sure which group you're in, check whether your Stocky is still working first.
We built Channel Bay's Stocky importer against that API, so the parts of this guide about what the API did and didn't return come from building it, not from reading about it.
The Two Stocky Migration Routes
| Your Stocky | What you can bring across | How long you have |
|---|---|---|
| Ended (most stores) | Export files from Stocky's reports: completed POs as CSV, stocktake history, cost data. No suppliers. | Read-only access "for at least 90 days" after 31 August 2026 |
| Still working | Everything in the export, plus complete supplier records and POs with line items through the API | Until the API stops, on 1 March 2027 |
Shopify's help centre only documents the first row. The second comes from the retirement banner some stores see, which says "After March 1, Stocky will no longer be available." Whichever row you're in, the steps below are the same. The API route just gives you more to start from.
Step 1: Export Everything You Want to Keep
Shopify's migration guide lists three exports to make from Stocky's reports before you move (Shopify Help Center):
- All completed purchase order reports, as CSV files. These are your purchase history and your price reference.
- Your stocktake history. Shopify can report on inventory activity, but it can't reference specific Stocky stocktakes.
- Your historical cost data. This is the only record of what you paid before the move.
Then add what the reports don't cover:
- Your supplier list, by hand. Shopify is blunt: "Suppliers can't be exported from Stocky." Write down each supplier's contact details, account number, currency, payment terms, and the supplier SKU, cost and pack size of everything you buy from them. If your Stocky has ended, this list is the only supplier record you'll have.
- A note of anything your reports and paperwork depended on. Some merchants moving off Stocky have found out at go-live that a report or a PO layout they relied on was built on Stocky data. Save a sample PDF of each document you send suppliers, so you can match it later.
Download every file, keep the copies somewhere other than your email inbox, and don't count on being able to run the same export again. Shopify says read-only access lasts "at least 90 days", which is a floor, not a published end date.
If your Stocky still works, make the same exports anyway. The API carries more than the reports, but it doesn't carry stocktakes, and it stops answering on 1 March 2027.
What the Stocky API Returns, If Your Stocky Still Works
The whole API was three resources: purchase orders, suppliers and tax types. There was never an endpoint for products, stocktakes, adjustments or transfers, which is why no importer brings those across.
- Suppliers came across complete. The supplier payload held name, company name, account number, contact name, email, phone, toll free phone, fax, both address lines, city, province, postal code and country. It's the one route that recovers your supplier book intact.
- POs came with their line items. Headers carried the number, invoice number, supplier, currency, paid and archived flags, the ordered, expected, ship, invoice and payment due dates, plus shipping and adjustments. Line items carried SKU, product and variant title, quantity, cost price, supplier cost price, retail price, tax type and account code.
- Tax types were a separate lookup. A line item pointed at a tax type by ID instead of carrying the rate. Pull the orders without the lookup and your costs are right but your tax treatment is meaningless.
One detail matters if you're reconciling. Alongside the PO number, Stocky returned a separate sequential_id, and the two don't always agree. Merchants know their orders by the PO number, so that's the one to match against your own records.
What Can't Come Across From Stocky
Some gaps belong to the manual export, some to the API, and some to Shopify's side. None of them are fixable by choosing a different tool.
| Data | Through the API | In the export files | Into Shopify |
|---|---|---|---|
| Supplier records | Yes, complete | No | Rebuild by hand |
| PO headers and line items with cost and retail price | Yes | Yes | Line items into a new draft PO only |
| Supplier to product links | Never exposed | No | No |
| PO status (open, partial, closed, cancelled) | Never exposed | No | No |
| Received quantity per line | Never exposed (only received or not) | No | No |
| Stocktakes, adjustments, transfers | No endpoint | Stocky's own reports | No |
On the Shopify side, the help centre says "Historical purchase orders can't be imported into Shopify." Its CSV upload for POs "only adds product line items to a new draft purchase order. It can't import past purchase order statuses, received quantities, or supplier links."
Supplier to Product Links
Stocky's API never exposed which products belonged to which supplier, at product or variant level. That link is what makes a PO quick to raise: you see the forty things you buy from a supplier instead of searching the whole catalog. It's also the step where migrations stall. Rebuilding it is the biggest job in step 2.
Received Quantities
Line items carried a received_at timestamp but no received quantity. Order 100 units, receive 40, and the API reports a received line of 100. The 40 exists nowhere, so an importer can only count the full ordered quantity or drop the information. If your received numbers look too high after an API migration, this is almost certainly why. Step 3 covers how to avoid it.
PO Status
With no status field, an importer can't tell an open PO from a closed or cancelled one. Expect imported POs to arrive as a read-only record rather than orders you can keep working on.
Step 2: Rebuild Your Suppliers and Pack Sizes
Do this in order: suppliers first, then the products each one supplies, then the per-supplier details (supplier SKU, cost, pack size, minimum order). Each layer needs the one before it.
In Shopify's admin, each product has a single Vendor field, and supplier records hold contact details and an address. For anything more, such as a second supplier, supplier SKUs, case packs, minimum order quantities or lead times, Shopify suggests variant metafields like supplier.case_quantity. They're reference fields only, so "your staff convert case packs into individual units manually when they create or receive an order." Supplier currency and payment terms are set on each PO, not saved to the supplier. We cover what that changes day to day in Stocky vs Shopify purchase orders.
In a third-party app, ask two questions before you start typing:
- How does it import supplier contact details? Shopify's own API returns supplier names only, so the rest has to come from a file, or from the Stocky API if yours still works.
- How does it rebuild supplier to product links? The options are a CSV mapping, matching on Shopify's Vendor field, or inferring the links from your PO history.
Inference from PO history saves the most time, but it has two limits. Suppliers you never raised a PO against leave no trace, so you link them by hand. And it gives you the supplier you used to order from, not the current one, so anything you re-sourced in the last year needs checking. Ask for a list of the inferred links, and check it before you raise your first PO.
Step 3: Settle Open and Partially Received Purchase Orders
Open POs are where a migration goes wrong quietly, because neither route carries their status or what has already arrived.
If your Stocky still works, close what you can before you migrate:
- Receive anything that has arrived, and cancel lines that won't.
- For each PO that's genuinely still open, write down the quantity still to come.
- Don't migrate half-received POs expecting them to carry on. Close them in Stocky, then raise a new PO in your new system for the remaining units.
If your Stocky has ended, you can no longer close anything in it. Use your PO export to list the orders you were still waiting on, compare each one against what's actually on the shelf, and recreate only what's outstanding. That's also Shopify's own advice: "If a purchase order is still open at the cutover, then recreate only the remaining quantities as a purchase order or transfer in Shopify."
Either way, don't recreate a whole PO for a delivery that has partly arrived. Receiving the full quantity again would overstate your stock.
Step 4: Choose Where Your Stocky Data Lands
The destination changes how much of steps 1 to 3 you do by hand.
| Your data | Shopify admin | A third-party app |
|---|---|---|
| Historical POs | Can't be imported. Keep the CSV export as your record | Depends on the app. Ask whether imported POs can be copied into editable ones |
| Open POs | Recreate the remaining quantities by hand or by CSV | Recreate, or copy from the imported record if the app supports it |
| Suppliers and product links | Rebuild by hand, one Vendor per product | Ask how it imports contacts and links |
| Pack sizes and supplier costs | Metafields, for reference only | Ask whether they fill in on the PO |
| Cost per item | One static field per variant | Ask how it updates cost from receiving |
If you're still deciding between Shopify's tools and an app, our comparison of Stocky alternatives covers which jobs each option handles. How POs work once you've moved is in our guide to Shopify purchase order management.
Step 5: Check Stock and Costs After the Move
Don't run your first real PO until you've checked the numbers against reality.
- Count stock. Run a stocktake, or at least a count of your fastest movers, and compare it with what the new system shows. Our guide to stocktakes in Shopify covers the native options.
- Reconcile received quantities. Shopify's guide suggests a custom report on the Inventory transfers data source, comparing
ordered_quantitywithreceived_quantity. Any line that shows fully received but you know arrived short came from a partially received Stocky PO. - Spot check costs. Shopify keeps a single static Cost per item per variant, which doesn't change when you receive. Compare it with the cost on your latest Stocky PO for a handful of products. Freight and duty don't reach it on their own either; see landed cost in Shopify.
- Check tax treatment on a few imported POs, if you came through the API. Tax types arrive as references, and a broken lookup fails silently.
- Check PO numbering. If your Stocky numbers carried a prefix, such as a location code, write down what each part meant. No payload carries that meaning, and imported numbers shouldn't collide with your new sequence.
- Run a test order end to end. Shopify recommends a test purchase order, transfer and inventory adjustment before you switch over, in Shopify POS too if you use it. Transfers are covered in our guide to Shopify inventory transfers.
Stocky Migration Checklist
- Find out whether your Stocky still works.
- Export completed POs as CSV, stocktake history and cost data. Back up the files.
- Write down every supplier with contacts, terms, supplier SKUs, costs and pack sizes.
- If the API still answers, migrate suppliers and POs through it before 1 March 2027.
- Close or record every open and partially received PO.
- Rebuild suppliers, then product links, then pack sizes and costs.
- Recreate only the remaining quantities of open POs.
- Count stock, reconcile received quantities and spot check costs.
- Run a test PO, transfer and adjustment, then switch over.
Migrating From Stocky to Channel Bay
If you're moving to Channel Bay, the migration is free and our team runs it. If your Stocky still works, you send us your Stocky API key and we connect it server-side, bringing across complete supplier records and your POs with line items. We then infer supplier to product links from your PO history and hand them back for you to check. If your Stocky has ended, you send us the export file instead.
Imported POs arrive read-only with an "Imported" status, because there's no status to read. To act on one, you copy it into a new editable PO. Supplier contacts and product to supplier links can also be imported from a CSV file, which covers suppliers the inference can't find. One limit to know: imported POs don't appear in the Purchase Order Report until they've been copied, one at a time. More on Channel Bay as a Stocky alternative.


