Stocky’s shutdown creates a data problem that is easy to underestimate. A clean purchase-order CSV is useful, but it may not preserve the context behind the numbers: supplier notes, receipt dates, partial deliveries, historical costs, lead times, and reorder decisions.
Before August 31, treat the export as an archive project, not just a one-time migration.
1. Export every source while access still works
Save the raw files before transforming anything:
- Purchase orders, including draft, confirmed, archived, and unarchived records
- Supplier and vendor data
- Stock counts, inventory adjustments, and transfer reports
- Current costs and any report that contains historical or manually adjusted costs
- Receipt details, especially received dates and partial-receipt status
Keep the original JSON or CSV untouched and date-stamped. A flattened worksheet is a working copy, not a replacement for the source export.
2. Check whether the export is complete
If you use an API export, page through the result until no records remain. A single response can look valid while containing only the first page. Keep a simple count of:
- Purchase orders exported
- Line items exported
- Orders by status
- Orders with a supplier, SKU, cost, location, and receipt state
Round-number batches are worth investigating. So are missing statuses, missing locations, and a sudden drop in line-item counts.
3. Preserve the fields that CSVs often flatten
For each purchase-order line, keep the PO number, supplier, SKU, title, ordered quantity, received quantity or receipt state, unit cost, location, and status. Store notes and dates in separate columns instead of combining them into one description field.
If an export has no explicit received quantity, do not invent one. Use the available receipt date and item status as evidence, then mark partial or unconfirmed lines for manual review.
4. Build a small truth set
Pick a few known purchase orders:
- One fully received order
- One partially received order
- One with a cost adjustment
- One with supplier or PO notes
- One with multiple locations, if applicable
Compare those records against the exported worksheet. This catches missing context before you trust the full archive.
5. Keep the handoff reviewable
Before recreating anything in another system, filter for:
- Missing SKU, supplier, cost, or location
- Ordered quantity greater than received quantity
- Missing receipt dates
- Duplicate PO numbers or duplicate line identities
- Supplier notes or historical-cost fields that did not survive
A local browser-side option is the Stocky purchase-order JSON to CSV exporter. It accepts a JSON export you provide, flattens purchase orders and line items into a review worksheet, and keeps likely pagination, ambiguous receipts, and missing fields visible. It does not call Stocky, ask for credentials, upload the file, or write back to Shopify.
The practical goal is simple: keep the raw export, prove the archive is complete, and only then decide what deserves a new purchase order, transfer, or migration step.
Top comments (0)