Stocky Is Going Away: What Shopify Merchants Should Export First

Before you replace Stocky, export the data that keeps your inventory operation running. The goal is not only to preserve product records. The goal is to keep buying decisions, supplier conversations, and purchase orders understandable after the migration.

1. Export products and variants first

Start with Shopify product and variant CSVs. Confirm every sellable variant has a stable SKU, vendor, barcode if used, cost, price, and inventory quantity. Missing SKUs are the highest-risk problem because they prevent supplier mapping and reorder recommendations from matching cleanly.

2. Capture supplier and vendor relationships

Stocky workflows often depend on supplier names that are not perfectly aligned with Shopify vendors. Export supplier lists, supplier item costs, vendor names, and any SKU-to-supplier mapping you can access. If two supplier names refer to the same vendor, decide which name becomes the future source of truth.

3. Save reorder rules and low-stock thresholds

Reorder points are easy to lose during migration. Export reorder points, minimum stock levels, preferred order quantities, lead times, and recent sales velocity when available. These fields determine whether the new workflow can recommend purchases or only show static inventory counts.

4. Preserve open purchase orders

Open POs should be exported separately from historical POs. Capture supplier, PO number, SKU, quantity ordered, expected receipt date, unit cost, and status. A migration that loses open PO state can cause duplicate orders or missed replenishment.

5. Save the operational fields behind the numbers

Exporting a quantity is not enough. Save the lead time, safety stock, minimum order quantity, pack size, supplier SKU, and location where the stock should be received. These fields determine whether a forecast can become a usable supplier order instead of a generic low-stock warning.

6. Keep an evidence trail for the migration

Write down who exported each file, when it was exported, and which Shopify location or Stocky screen it came from. This sounds basic, but it prevents bad re-imports later. If a buyer uploads an old supplier CSV after a newer Shopify inventory export, reorder math can become inconsistent even when every individual file looks valid.

Suggested migration folder structure

• 01-products: Shopify product and variant exports, one file per export date.
• 02-inventory: location-level inventory exports and any stocktake files.
• 03-suppliers: supplier contacts, supplier SKUs, costs, lead times, MOQ, and pack sizes.
• 04-purchase-orders: open POs first, historical POs second, receiving notes third.
• 05-audit-results: findings, fix notes, and the final clean CSV set.

7. Run an audit before importing into the next system

Do not import messy CSVs directly into a new WMS or ERP. Run a migration audit first so you can identify missing SKUs, supplier gaps, duplicate vendors, weak reorder points, and inventory quantities that need manual review.

What a useful audit should tell you

A useful audit does more than count rows. It should tell you which SKUs cannot be matched, which suppliers cannot create clean POs, which low-stock SKUs need action before migration day, which overstock SKUs should be paused instead of reordered, and which open POs might duplicate buying if incoming quantities are ignored.

8. First-week operating checklist

After the first import, run a small operational test before trusting the new process. Pick five SKUs: one healthy SKU, one low-stock SKU, one overstock SKU, one SKU with an open PO, and one SKU with missing supplier data. Confirm each SKU appears correctly in the product list, forecast, reorder queue, purchase-order draft, receiving screen, and audit findings. If those five cases behave correctly, the rest of the catalog is much safer to process.

Vamao Inventory OS turns these exports into a readiness report and a prioritized action list.