1. The facts and dates
Shopify built Stocky as a free inventory management app and later acquired it. For several years it was the only real PO and forecasting tool tightly integrated with Shopify — free, functional, and built for the specific way Shopify's inventory model works.
That changes permanently on August 31, 2026. Here's what's confirmed:
- February 2, 2025: Stocky was removed from the Shopify App Store. New installs stopped from that date.
- August 31, 2026: Stocky's APIs stop working. Any automated workflow, integration, or data sync that touches Stocky breaks on this date.
- After August 31: Shopify has indicated read-only access may continue for a period for data export, but this shouldn't be relied on for planning purposes. The safest assumption is that your access ends August 31.
If you're still running your reorder and PO workflow through Stocky, you have roughly seven weeks to migrate. That's enough time if you start now; it's not enough time if you leave it to mid-August.
2. Export your Stocky data now
Before doing anything else — before evaluating replacements, before migrating a single setting — export your Stocky data. Once the shutdown hits, this data is gone.
What to export
Purchase Orders: In Stocky, go to Purchase Orders and use the export function to download your PO history as CSV. This gives you a record of what you ordered, from whom, and at what quantities — useful for reference when setting up a new tool and for your accounts.
Suppliers: Go to Suppliers and export the supplier list. This contains contact details and the supplier-to-product mapping you've built up. Rebuilding this from scratch in a new tool is tedious but straightforward — having the export saves you from doing it from memory.
Reorder points: In Stocky, go to Products and export the product list with reorder points. This is the most valuable export — it captures the threshold decisions you've already made per SKU. Screenshot or export this before anything else, because reorder points are not stored in Shopify's core inventory data and will not transfer automatically to any replacement.
Stock transfers and adjustments: If you've been using Stocky to manage transfers between locations or record adjustments, export those too for your records.
Note on timing: Do these exports before August 31 regardless of which migration path you choose. Even if you decide to stick with Shopify's native tools and manage things manually, the historical PO data and your reorder point configuration is worth having offline.
3. What Shopify's native tools do — and don't — replace
Shopify launched its own Purchase Order system built into the admin. For merchants who mostly used Stocky to create and send occasional POs, this may be sufficient. But it's worth being clear about the gaps before assuming native is a drop-in replacement.
What Shopify's native PO system does cover
- Creating purchase orders manually within the Shopify admin
- Attaching a supplier (Shopify calls these "suppliers" in the PO context) to a PO
- Adding line items to a PO from your product catalogue
- Marking a PO as received, which updates inventory quantities
- Partial receipts — you can receive some items and leave others outstanding
- Basic PO status tracking (draft, ordered, received)
What Shopify's native PO system does not cover
- No automated reorder point monitoring. Shopify does not watch your inventory and alert you or act when stock drops below a threshold. That detection is entirely manual — you need to notice the problem yourself.
- No automatic PO generation. When stock is low, Shopify does not generate a PO draft for you. You create the PO manually, add the products manually, and set quantities manually.
- No reorder point per product. There is nowhere in Shopify's core admin to store a reorder point (minimum stock threshold) against a product or variant. Stocky had this. Native Shopify does not.
- No automatic supplier email dispatch. Creating a PO in Shopify's admin does not send it to your supplier. You still need to download the PO and email it yourself.
- No forecasting or demand-based reorder suggestions. Stocky's forecasting feature (which suggested reorder quantities based on sales velocity) has no equivalent in native Shopify.
- The supplier/vendor split is confusing. Shopify has "vendors" (stored on the product itself) and "suppliers" (stored on POs) as separate concepts. If your products have vendor names set, those vendor names do not automatically populate as PO suppliers. You'll need to manage these separately, which catches people out during migration.
The honest summary: native Shopify POs are a manual tool, not an automated one. If Stocky's core value for you was removing the manual work — watching stock, generating drafts, emailing suppliers — native Shopify does not replace that.
4. Decision framework: which Stocky feature was your main one?
Stocky did several things. Most merchants leaned heavily on one or two of them. The right migration path depends on which feature you'll miss most.
If forecasting was your main feature
Stocky's forecasting used your sales velocity to suggest how much to order and when. Replenishly now does this too — it reads 60 days of your Shopify order history, calculates average daily sales per product, and suggests a reorder point using the formula ceil(avg_daily_units × lead_time_days × 1.2). Suggestions appear as one-click chips in the Inventory Watch and as a bulk-apply panel in Settings. See how the calculation works.
Where Replenishly's velocity-based thresholds fall short: they use a rolling 60-day average and don't account for seasonality, trend direction, or promotional uplifts. If you need full demand forecasting with seasonal models and open-to-buy planning, that's a different category of tool — Inventory Planner (more powerful, higher price point) and Prediko (simpler, Shopify-native) are the established options there.
For most merchants migrating from Stocky, Replenishly's velocity-based suggestions cover the majority of what Stocky's forecasting actually provided in practice.
If stock counting and stocktake was your main feature
Shopify's native stocktake functionality covers most of what Stocky provided here. You can count stock and commit adjustments directly in the Shopify admin. For more advanced cycle counting workflows, apps like Stocky alternatives for counting (there are several on the App Store specifically for physical inventory counting) are worth evaluating.
If the PO-to-supplier-to-receiving loop was your main feature
This is the workflow where Stocky genuinely earned its keep: you set a reorder point, Stocky detected when stock dropped below it, you (or Stocky automatically) generated a PO, sent it to the supplier, and reconciled what arrived against what was ordered.
This is what Replenishly is built for. It monitors your Shopify inventory via webhook, generates a PO draft the moment stock drops below your threshold, routes it to the right supplier (you can have multiple suppliers, each with their own spreadsheet format), and emails the PO directly to the factory. When stock arrives, the receiving audit sheet lets you log what you actually received against what was ordered and commits the delta directly to Shopify inventory.
Two things worth being honest about:
- Replenishly now includes velocity-based threshold suggestions — it analyses 60 days of order history and suggests a reorder point per product based on how fast it actually sells and your lead time. For full demand forecasting with seasonal models, you need a dedicated forecasting tool.
- Replenishly is $29/month after a 7-day free trial. Stocky was free. That's a real difference, and it's worth factoring in.
If you used Stocky lightly — the occasional manual PO
Shopify's native PO system is probably sufficient. It's free, it's inside your existing admin, and if you're creating POs infrequently and manually anyway, the automation gap doesn't matter much.
5. A 7-day parallel-run migration checklist
The safest approach is to run your new tool in parallel with Stocky for at least one full reorder cycle before August 31. This lets you verify everything works end-to-end while Stocky is still your safety net.
7-Day Migration Checklist
Export all Stocky data
POs, suppliers, products with reorder points. Store offline. Do this today regardless of your migration decision.
Document your current reorder points
Screenshot or note down the threshold per SKU from the Stocky export. These don't exist anywhere else in Shopify and you'll need to re-enter them in your new tool.
Choose your replacement and install it
Use the decision framework above. Install and connect it to your Shopify store while Stocky is still live — this is your safety net week.
Configure suppliers and thresholds in the new tool
Re-enter your supplier contact details, map products to suppliers, and set reorder thresholds using the values from your Stocky export.
Run one real order end-to-end
Trigger a PO through the new tool for a real low-stock item. Verify the PO goes to the right supplier in the right format. Confirm that receiving the stock updates Shopify inventory correctly.
Verify any integrations that touch Stocky
If anything in your stack (3PL, accounting software, ERP) connects to Stocky's API, identify those integrations now and plan how they'll be rerouted or replaced.
Switch off Stocky monitoring before August 31
Once you've confirmed the new tool works end-to-end, disable any Stocky automations so you're not running duplicate PO workflows in parallel on shutdown day.
The bottom line
The August 31 deadline is firm and the search demand for "Stocky alternative" and "Stocky migration" is already climbing. If you're reading this, you probably already knew the shutdown was coming — the question is whether you've acted on it yet.
Start with the data export. Everything else follows from there once you have your reorder points documented and know which Stocky features you actually used.
If the PO-to-supplier-to-receiving workflow is your main concern and you want to try Replenishly, there's a 7-day free trial — no credit card required at install. It takes about 10 minutes to set up your first supplier and generate a test PO.