Shutdown: August 31, 2026
What happens to your Stocky data
Some of what appears in Stocky already lives in Shopify and is untouched by end of life. Stocky-specific history is not moved into Shopify automatically. Active inventory management and every Stocky API stopped on August 31, 2026; Shopify says read-only access, including exports, remains for at least 90 days. Knowing which route each data type needs tells you what to secure first. See Shopify’s official transition guide.
Data by data
Reorder points and lead times
Not moved to ShopifyNot part of your Shopify product data and not inherited by any Shopify feature. Keep the complete official nine-file export; for Low Stock CSV files saved through August 31, use the unchanged legacy import tab and retain the original independently.
Purchase order history
Not imported into ShopifyShopify has stated plainly that historical Stocky purchase orders cannot be imported into Shopify. Keep purchase_order_items.csv with manifest.json and the other seven official CSV files, and preserve any legacy reports independently. This history records what you last paid and which supplier each product came from.
Suppliers
Not moved automaticallyShopify now has native supplier management, but Stocky supplier records are not transferred into it automatically. Shopify’s current official Stocky export includes suppliers.csv and supplier_variant_costs.csv; keep the complete nine-file package and a separate contact backup.
Stocktake and stock adjustment history
Not moved to ShopifyThe record of why a quantity changed is not transferred into Shopify. Keep stock_take_items.csv and stock_adjustment_items.csv inside the complete official package, plus any legacy reports saved through August 31. Check your own retention obligations before deciding what to archive.
Current stock quantities
SafeYour on-hand quantities live in Shopify, not in Stocky. They are unaffected by the shutdown.
Products, variants and SKUs
SafeAlso Shopify data. Note that cost per item may exist in both places — check whether the values you rely on are the Shopify ones or Stocky’s.
A workflow that leaves room for mistakes
- 1
Request and download the complete official export
On Stocky’s current read-only page, choose Request data export, then download the package from the link Shopify sends to the store’s registered email. Keep all nine files together; a header-only CSV is valid and must not be removed.
- 2
Store the original package unchanged
Keep an independent copy before opening or inspecting the files. Do not rename, merge, or resave the source files.
- 3
Preview on Sep 1 onward
Select all nine files together, review missing or unexpected files, row counts, unmatched references, and retained-only records, then explicitly confirm.
- 4
Keep legacy sources on Through Aug 31
Import CSV files and copied tables saved before shutdown through the unchanged legacy tab. Do not mix them into the official package.
Common questions
Q.Will the Stocky API keep working after the app is retired?
No. Every Stocky API stopped on August 31, 2026. Use Shopify’s official Stocky data export instead and keep the complete package unchanged: manifest.json, suppliers.csv, supplier_variant_costs.csv, product_variants.csv, purchase_order_items.csv, stock_transfer_items.csv, stock_take_items.csv, stock_adjustment_items.csv, min_max_available.csv. Import it on the Sep 1 onward tab. CSV import in UreyukiBox has two tabs: Through Aug 31 and Sep 1 onward. On Sep 1 onward, select manifest.json and all eight CSV files from Shopify’s official Stocky export together, review the preview, then import the supported data. Through Aug 31 keeps the existing CSV and paste workflow unchanged. Neither route infers missing fields or changes current Shopify inventory, transfers, product catalogue, or tax settings.
Q.Can I just take screenshots instead of exporting?
Screenshots are better than nothing for a handful of values, but they cannot preserve structured relationships such as which purchase order belongs to which supplier. Keep manifest.json and all eight official CSV files together and unchanged; keep legacy CSV files and copied tables saved through August 31 separately.
Q.Should I uninstall Stocky as soon as I have exported?
Keep Stocky installed while you verify the official package and imported result. Active inventory management ended on August 31; Shopify says read-only access remains for at least 90 days, so do not uninstall until the complete package and counts are verified.
Keeping the parts that would otherwise be lost
CSV import in UreyukiBox has two tabs: Through Aug 31 and Sep 1 onward. On Sep 1 onward, select manifest.json and all eight CSV files from Shopify’s official Stocky export together, review the preview, then import the supported data. Through Aug 31 keeps the existing CSV and paste workflow unchanged. Neither route infers missing fields or changes current Shopify inventory, transfers, product catalogue, or tax settings. Review the supported result against the complete official package. Importing history does not change current Shopify inventory, execute transfers, or assign tax settings to current products automatically.
The interface, the App Store listing and support are available in English. Alerts and supplier emails use English for stores outside Japan and Japanese for stores in Japan. Supported Stocky official exports, saved CSV files and copied tables can be imported manually from CSV import; missing fields are not inferred. Purchase orders follow your store too: totals are in your store’s currency, with editable purchase-tax presets for 53 countries. The US, Canada, Brazil, Hong Kong, Indonesia and Malaysia start with no tax line because one national rate would be misleading.
Related guides
-
How to export your Stocky data
Keep manifest.json and all eight CSV files from Shopify’s official Stocky export together, with legacy pre-shutdown files stored separately.
-
Import the official Stocky export
Use Sep 1 onward for Shopify’s manifest plus eight CSV files, or Through Aug 31 for saved legacy CSV and copied-table sources.
All guides in one place: the UreyukiBox blog