This page pulled purchase order history out of Stocky using nothing but the merchant's own API key. Shopify's Stocky API stopped answering on 31 August 2026, so there is nothing left for it to call, and I have taken the form down rather than keep a page that asks for a credential and then fails. The page itself stays up. I wrote things that point here, and a dead link would be a worse answer than an honest one.
It still works. Nothing in that file depended on the API staying up — the CSV is one row per line item and the JSON is the raw payload, both plain text you can open without me and without Shopify.
Check the trailer before you file it away. The CSV's last line reads # EXPORT COMPLETE with the purchase order and line counts; the JSON ends with "complete": true. If the trailer is missing, that export was cut short — and there is no longer any way to run it again, so treat a partial file as your only copy and put it somewhere that gets backed up.
Keep it even if you have no immediate use for it. It is the only machine-readable record left of which cost belonged to which receiving.
The API route is closed. I cannot get your purchase order history back and neither can anyone else, which is an uncomfortable thing to write at the top of a tool that existed to stop exactly this. Here is what is actually worth doing, in the order I would do it.
Look for a file somebody already made. Stocky's own interface had CSV exports, and in a lot of teams somebody pulled one at some point — for a stocktake, for an accountant, for a supplier dispute. Search your shared drive and your sent mail for attachments before you conclude anything is gone. I never mapped that UI export column by column, so I will not tell you what is in it. Open the file and see.
Then go to the suppliers. Freight and duty numbers existed twice: once in Stocky, and once in the invoices that produced them. Those invoices are in your mail and your accounting system, and for landed cost purposes they are the primary source. Stocky was only ever the place you copied them to.
What invoices cannot give back is the connective tissue — which receiving each cost belonged to, and the received dates that were the only record of how long each supplier actually took. If lead times mattered to you, that is the loss worth mourning, not the costs.
And ask Shopify support what they retain. I am not claiming Shopify deleted anything; what I verified is that the API stopped answering, and the distance between those two statements is exactly the space where support might still have something. Ask before you assume.
Up to 20,000 purchase orders, streamed, with the integrity trailer described on the left.
Every key was used inside one request and then discarded — not written to a database, not put in a log, not sent anywhere except Stocky's own API. There was no account and no email gate. That is also why I cannot tell you how many merchants used this before the lights went out: I never measured it, and I would rather end with that gap than with a number I collected by breaking the promise.
This was a read-only export. It never touched Stocky, Shopify products, inventory or costs — and now it does not touch anything at all.
The reason that export mattered is the freight and duty sitting on those purchase orders. Stocky spread it across the lines and pushed the result into Shopify's cost per item. That job did not end when Stocky did; it just lost the thing that was doing it.
Costfold is what I build, and it does that one piece: bring in a receiving from a CSV or by hand, spread its landed costs by value, quantity or weight, and write the true cost back to cost per item — every write logged, and reversible per receiving. If you exported with this tool, its importer reads that file directly. The columns it needs are sku, title, qty, unit_cost, weight_grams.
It is in Shopify's app review queue rather than the App Store, so there is nothing for you to install today. I would rather say that here than let you find out by clicking.