Stocky records are useful because they connect products, suppliers, purchase orders, receipts, costs, and stocktakes. A basic product export does not necessarily preserve those relationships. Before moving to another tool, create a source archive designed to stand on its own.
Decide what the archive must answer
Begin with business questions rather than file names. Can the archive show what was ordered, what was received, which supplier was involved, what a SKU cost at the time, and why a stocktake changed inventory? If a future dispute or accounting question cannot be answered from the files, another export may be required.
Download separate source exports
Export the available purchase-order, supplier-cost, product-cost, and stocktake data. Keep separate files when the source exposes different record types. Merging too early can hide one-to-many relationships or repeat header values in ways that later appear to be duplicates.
- Use a consistent folder name such as
stocky-archive-2026-07-22. - Do not open and resave the only copy in spreadsheet software.
- Keep the original extension and file name in the raw folder.
- Write down the store, export date, date range, and person who performed the export.
Verify every file immediately
Open a copy and confirm that it contains more than a header row. Check that the expected columns exist and that important fields are populated. Look at the earliest and latest records, then compare a few rows with Stocky while access remains available.
Purchase-order checks
- PO numbers are present and stable.
- Supplier and SKU values are populated.
- Ordered and received quantities are numeric.
- Status and date fields cover the expected history.
- Currency and unit-cost fields are understandable.
Stocktake checks
- Location and SKU identify the counted item.
- Expected and counted quantities are present.
- Variance can be recalculated from the exported values.
- The export includes the intended locations and dates.
Create cleaned derivatives, not replacements
After verification, create a separate working folder. Clean formula-like cells before opening generated CSV reports, normalize obvious header differences, and document any rows removed or combined. Never replace the raw folder with the cleaned version.
Add a manifest
A manifest lists each file, size, row count, detected record type, and cryptographic fingerprint. The fingerprint proves whether a file changed after the archive was created. Include a short readme explaining the source, the known limitations, and the destination system used after Stocky.
Store and test the archive
Keep at least two controlled copies. Test the archive from another computer or browser profile. Confirm that the CSVs and human-readable report open without needing a Stocky login. Access permissions should be limited because operational exports can contain commercially sensitive supplier and cost data.
Shopify documents the current transition details in its official Stocky transition guide. Use that page as the authority for product deadlines and available export options.
Verify up to 10 Stocky CSV files locally
Run the free scan to identify file types, row coverage, receipt differences, duplicates, stocktake variances, and cost changes before building the archive.
Audit the exports