Thirty minutes today keeps your purchase orders, stocktakes, and cost history after Stocky shuts down. Free, no account, and your API key never leaves your hands.
Use the lowest-risk option that gets the job done.
Most stores should start with option 1. Add option 2 to capture the history Stocky's screens don't show, or option 3 to have your AI assistant do the driving.
01 / no key
Recommended for most stores
Back up the files you can already see
Follow a 30-minute checklist to save your purchase orders, stocktake sheets, and cost reports as plain files you keep.
Stocky's screens never show everything. The free exporter saves your complete supplier list and purchase history into one archive on your computer — your key and your data never leave your device.
The documented API window has passed. Keep any existing archive unchanged, verify its manifest and checksums locally, then fill gaps from remaining UI and business records.
If you already use Claude or ChatGPT, install the free Stocky Rescue skill and let the assistant do the driving — what to save, how to run the exporter, and how to check the result. It is built to never ask for your key.
Works in the ChatGPT desktop app and Claude Code
Plain language, one step at a time
Never asks for your key or your files
Check what you saved with your AI assistant
The same free skill inspects an existing backup on your computer, verifies its checksums, and helps you write an honest gap report — without sending your files anywhere.
Read this before choosing the local exporter. Never paste a key into an AI chat, email, form, support ticket, shell command, filename, or archive.
01
Why the exporter needs a key
Stocky's UI does not export supplier profiles in bulk. Stocky Rescue v0.2.0 uses the key only for its fixed HTTPS GET requests to the documented API.
02
Where to find it
Shopify's prior migration instructions show: Apps → Stocky → account icon → Preferences → API access → Current key. Confirm the screen in your own store because the interface can change.
03
Endpoints called
Fixed HTTPS GET requests only: suppliers,purchase_orders, stock_adjustments,stock_adjustment_items, and tax_types under Stocky API v2.
04
What it cannot access
It cannot write Shopify inventory, read customers or orders, or retrieve Stocky data the API does not expose—including stocktake count sheets, Average Cost, forecasts, transfers, and every custom setting.
Post-API boundary
Preserve the archive. Retire the key.
Do not hunt for or share a Stocky key after the documented API window. Keep existing ZIP files unchanged, verify checksums locally, and use surviving UI or business records to document gaps.
01
Keep originals unchanged
Hash every ZIP, CSV, PDF, and screenshot before making working copies.
02
Verify locally
Check archive paths, checksums, manifest status, endpoint failures, and gaps.
03
Label inference
Keep source facts, inferred candidates, and unrecoverable gaps visibly separate.
04
Use the fallback
Build a portable evidence pack from remaining Stocky UI, Shopify, accounting, supplier, and operational records.
Optional · after your data is safe
Your rescued suppliers can move into ShelfTally today.
ShelfTally already imports the supplier list from your Stocky Rescue backup, and shows you a review before writing a single record. The Guide, exporter, and recovery resources stay free either way — join the list to hear when PO and stocktake import ship.