Stocky has shut down: export records and rebuild your workflow

## What changed on August 31?

Stocky stopped managing inventory and its APIs stopped working on August 31, 2026. Shopify documents read-only access to export data for at least 90 days after that date. An exact final access date is not promised. Use the built-in reports while your records remain accessible.

Source checked September 8, 2026: Shopify’s Stocky migration guidance. That page also explains which inventory workflows now live in Shopify.

## Preserve the records you still have

1. Export available reports. Save the Sales Summary / Finance report, Inventory Valuation Report, and relevant purchase-order and stocktake records through Stocky’s built-in reports. Check the actual fields and date coverage in each export.
2. Retain the originals. Keep the export date, source, reporting period and unedited file. Store invoice and receipt evidence alongside it so future adjustments are explainable.
3. Reconstruct supplier information carefully. Shopify says suppliers cannot be exported from Stocky. Use purchase documents and contacts you already retain to rebuild the details you need; do not assume an export contains every supplier field.
4. Check gaps before importing elsewhere. Historical Stocky purchase orders and stocktakes do not move automatically into Shopify. A native PO CSV upload adds lines to a new draft; it does not recreate historical receipt statuses, received quantities or supplier links.
5. Stop relying on Stocky API integrations. The APIs are retired. Keep missing evidence marked as missing, and assess the replacement’s supported import format before recording anything.

## Choose the workflow you need now

Start with Shopify’s current native tools for inventory, transfers and purchase orders. Shopify’s migration guidance also describes Sidekick-assisted reordering and draft creation. Availability and workflow fit should be checked in your store before adding an app.

For a dedicated low-stock dashboard, configurable reorder inputs and supplier-grouped drafts, review RestockRadar. For a dated receipt-cost ledger, estimated monthly COGS and current inventory valuation, review CostLedger. lcCode builds both apps; these are focused workflows rather than full Stocky replicas.

## Map retained cost records into CostLedger

1. Use the CostLedger CSV template. Required fields are SKU, quantity and unit cost; supported optional fields include received date, supplier, reference and note. Map your source columns rather than uploading an arbitrary Stocky export unchanged.
2. Check currency, unit quantities, tax treatment and the date of each receipt. Preserve a consistent cost basis; the app does not automatically allocate shared landed charges or reconstruct missing invoices.
3. Review the Shopify-seeded opening baseline before adding older batches. Use the supported opening-balance procedure where appropriate so starting stock is not counted twice.
4. Inspect representative cost timelines and reconcile the imported values with your original records. Plus PO PDF imports support completed Shopify purchase orders, a separate format from Stocky exports.
5. Review report coverage, freshness and uncosted units with your bookkeeper. Monthly COGS is estimated; a report export is not a locked accounting period or automatic QuickBooks posting.

## Validate the new routine

Choose a small set of representative SKUs: one steady seller, one seasonal item and one with changing supplier costs. Compare inventory, incoming stock, costs and expected reorder inputs against records you trust. A forecast can use available recent sales, but missing cost or order history cannot be recreated by changing a date label.

Keep exported snapshots of the reports used for bookkeeping decisions. Record later corrections and review their effect on the next report. For purchase planning, check the supplier draft before you communicate or place an order.

## Common migration questions

Can I keep using Stocky to receive new inventory?

No. The documented access is for reading and exporting retained data. Use a supported current inventory workflow for new activity.

Will importing a CSV restore historical Shopify purchase orders?

No. Shopify’s native purchase-order CSV upload creates lines in a new draft. CostLedger’s receipt import records cost evidence in its own ledger; it does not restore historical Shopify PO states.

What if I no longer have all the source data?

Preserve what you do have and identify gaps explicitly. Establish a documented starting point for future records rather than presenting incomplete historical reports as complete.

Compare replacement workflows by the job you need.