Stocky to Kestori migration guide
Shopify is shutting down Stocky on 2026-08-31. This guide walks through the practical migration path for merchants who mainly depend on Stocky's low-stock report, daily email, and reorder thresholds.
Before you start
Do not uninstall Stocky before you have one clean comparison week. Kestori can run in parallel, so the safest migration is to keep Stocky as your reference until Kestori's daily digest has matched your expectations for at least seven days.
Kestori does not import Stocky purchase orders, suppliers, or forecasting graphs. It replaces the daily low-stock workflow: current inventory, recent sales velocity, dynamic reorder thresholds, and a daily low-stock digest.
Step-by-step migration
-
Step 1: Export your Stocky reference data
Export the low-stock products report, vendor list, and any manual reorder points you actively trust. Keep this export as your audit trail while Kestori learns from Shopify order history.
-
Step 2: Install Kestori
Install Kestori from the Shopify App Store when the listing is live, approve inventory and order-history access, and confirm the store email where the daily digest should land.
-
Step 3: Let Kestori backfill order history
Kestori backfills 28 days of Shopify orders, inventory levels, products, variants, and locations. That gives the first digest real velocity data instead of starting from zero.
-
Step 4: Compare the daily low-stock digests
Run Stocky and Kestori side by side for one week. Compare the flagged SKUs, stockout risk, and threshold values against the Stocky report and your own buying judgment.
-
Step 5: Turn off Stocky after one clean week
Once Kestori's digest is arriving daily and the SKU list is decision-ready, turn off Stocky's email. Keep your export for historical purchase order and supplier context.
Field mapping
| Stocky field | Kestori field | Migration behavior |
|---|---|---|
| SKU | SKU | Read directly from Shopify product variants. |
| Product title and variant title | Product and variant | Read directly from Shopify products and variants. |
| Vendor | Vendor | Read from the Shopify product vendor field. |
| Location inventory | On hand by location | Synced from Shopify inventory levels. |
| Reorder point | Manual override threshold | Optional. Kestori calculates a dynamic threshold first; add an override only when you need a hard floor for a specific SKU. |
| Sales velocity | 28-day velocity | Rebuilt from Shopify order history during backfill. |
| Purchase order history | Not imported | Keep your Stocky export for historical PO context. |
| Supplier records | Not imported | Kestori uses Shopify vendor data, not Stocky supplier records. |
Screenshot walkthrough
Edge cases to check
- If a SKU has no recent sales, Kestori keeps it visible but marks velocity as zero so it does not silently disappear from review.
- If Shopify has no cost data for a variant, leave margin decisions in your existing Stocky export and use Kestori for stockout risk.
- If a location is being closed or ignored operationally, confirm its inventory should still count before comparing Stocky and Kestori results.
Get started
The lowest-risk path is install, backfill, one week of parallel digest comparison, then turn off Stocky. Waiting until late August compresses that validation window exactly when every Stocky replacement will be under the most load.