Stocky Is Shutting Down August 31, 2026: What Shopify Stores Should Do Now
9 min read
The Timeline: Two Dates Every Stocky User Should Have on Their Calendar
On February 2, 2026, Shopify quietly removed Stocky from the Shopify App Store. The app stopped accepting new installations and reinstallations that same day. If you uninstalled Stocky after February 2 thinking you could come back to it later, that decision is now permanent.
The bigger date is August 31, 2026. That is when Stocky stops functioning entirely. The web interface stops loading, the APIs stop responding, scheduled purchase order syncs stop running, and forecasting reports stop generating. Shopify has said read-only access will continue for a limited time after the shutdown so merchants can export their data, but the working app — the one that actually runs your inventory planning — disappears that day.
This is a hard cutover, not a feature reduction or a phased migration. If you rely on Stocky for any operational workflow in your store, you have roughly three months from when this article was published to decide what replaces it and to move your data across. That window sounds long until you account for the lead time of a new tool selection, the data migration itself, retraining your warehouse or fulfillment team, and validating that the new system produces forecasts that match what Stocky was telling you. Three months becomes tight fast.
The bigger date is August 31, 2026. That is when Stocky stops functioning entirely. The web interface stops loading, the APIs stop responding, scheduled purchase order syncs stop running, and forecasting reports stop generating. Shopify has said read-only access will continue for a limited time after the shutdown so merchants can export their data, but the working app — the one that actually runs your inventory planning — disappears that day.
This is a hard cutover, not a feature reduction or a phased migration. If you rely on Stocky for any operational workflow in your store, you have roughly three months from when this article was published to decide what replaces it and to move your data across. That window sounds long until you account for the lead time of a new tool selection, the data migration itself, retraining your warehouse or fulfillment team, and validating that the new system produces forecasts that match what Stocky was telling you. Three months becomes tight fast.
What Stocky Actually Did (and Why Stores Are Going to Miss It)
Stocky was Shopify's free inventory planning app for Plus merchants and an inexpensive add-on for everyone else. It did five things particularly well, and most stores using it depend on at least three of them:
Demand forecasting: Stocky pulled your sales history and projected future demand by SKU. Not perfect, but good enough that buyers could place purchase orders against a forecast instead of a gut feeling.
Automated purchase orders: When stock fell below a reorder point you defined, Stocky generated a purchase order, populated supplier details, and emailed it. For stores with 200+ SKUs across multiple suppliers, this alone saved 10-15 hours a week.
Supplier and lead time tracking: Each supplier had its own lead time and minimum order quantity stored in Stocky. The system used those to time reorder suggestions so stock arrived before it ran out, not after.
Stock-on-hand reporting across locations: For merchants with a warehouse, a retail location, and Shopify Fulfillment Network, Stocky was the single place that showed total stock and stock by location, with cost-of-goods rolled up.
Low-stock and out-of-stock alerts: Daily digest of SKUs running low, SKUs out of stock, and SKUs that had been out of stock for more than X days. This is what kept catalogs from quietly dropping bestsellers off the storefront.
None of these are surface-level features. Stores that have been on Stocky for a year or two have woven it into their daily standup, their supplier relationships, and their financial planning. Replacing it badly costs real money in stockouts, overordering, and reorder fire-drills.
Demand forecasting: Stocky pulled your sales history and projected future demand by SKU. Not perfect, but good enough that buyers could place purchase orders against a forecast instead of a gut feeling.
Automated purchase orders: When stock fell below a reorder point you defined, Stocky generated a purchase order, populated supplier details, and emailed it. For stores with 200+ SKUs across multiple suppliers, this alone saved 10-15 hours a week.
Supplier and lead time tracking: Each supplier had its own lead time and minimum order quantity stored in Stocky. The system used those to time reorder suggestions so stock arrived before it ran out, not after.
Stock-on-hand reporting across locations: For merchants with a warehouse, a retail location, and Shopify Fulfillment Network, Stocky was the single place that showed total stock and stock by location, with cost-of-goods rolled up.
Low-stock and out-of-stock alerts: Daily digest of SKUs running low, SKUs out of stock, and SKUs that had been out of stock for more than X days. This is what kept catalogs from quietly dropping bestsellers off the storefront.
None of these are surface-level features. Stores that have been on Stocky for a year or two have woven it into their daily standup, their supplier relationships, and their financial planning. Replacing it badly costs real money in stockouts, overordering, and reorder fire-drills.
What Shopify Is and Is Not Replacing
Shopify's public position is that it is consolidating point-of-sale and inventory features directly into Shopify Admin, and that the native tools will be sufficient for most merchants. That is partially true and partially marketing.
What Shopify Admin natively does well after the Stocky shutdown:
What Shopify Admin does not do, even after the announced consolidation:
If your use of Stocky was just "see stock levels and get a low-stock email," you are fine — Shopify Admin covers that. If your use of Stocky was the forecasting, reordering, and supplier workflow side, native Shopify is going to leave a real gap. The official message that "native tools are sufficient" is true for the simplest cases and misleading for the use case that made Stocky valuable in the first place.
What Shopify Admin natively does well after the Stocky shutdown:
- Track stock-on-hand per location
- Set low-stock thresholds and email alerts
- Show stock-on-hand history per SKU
- Transfer inventory between locations
- Bulk-edit inventory levels
What Shopify Admin does not do, even after the announced consolidation:
- Demand forecasting based on velocity, seasonality, or trend
- Automated purchase order generation
- Supplier records with lead times and minimum order quantities
- Reorder suggestions tied to forecast plus lead time
- Multi-supplier purchase order workflows
- Cost-of-goods tracking by purchase order
If your use of Stocky was just "see stock levels and get a low-stock email," you are fine — Shopify Admin covers that. If your use of Stocky was the forecasting, reordering, and supplier workflow side, native Shopify is going to leave a real gap. The official message that "native tools are sufficient" is true for the simplest cases and misleading for the use case that made Stocky valuable in the first place.
Your Realistic Options Before August 31
There are four credible paths for a Stocky user in 2026, and the right answer depends on store size and how dependent your operations are on what Stocky did:
Option 1: Move to a dedicated inventory SaaS. Tools like inFlow, Cin7, Katana, Prediko, and Sumtracker do most of what Stocky did, sometimes more. The trade-off is the subscription cost — most start at $99-299/month and scale by SKU count or order volume. For stores with $50K+ monthly revenue and 500+ SKUs, this is the obvious replacement and usually the right answer. For smaller stores it is a meaningful new line item on the app bill.
Option 2: Move to a Shopify-native inventory plus spreadsheet. Use Shopify Admin for stock levels and low-stock alerts, then run forecasting and purchase orders in a spreadsheet that pulls data via the Shopify API. Cheap, flexible, and brittle. Works for stores with under 200 SKUs and one or two suppliers. Falls apart at scale and burns staff time that costs more than the SaaS subscription would have.
Option 3: Build a custom replacement. For stores spending €200+/month on inventory tooling already, or stores where Stocky was deeply woven into the warehouse and supplier workflow, a custom-built inventory module tailored to exactly how your operation runs makes the most economic sense. You pay a one-time build cost, own the code, and pay nothing per order or per SKU forever. For stores in the DACH region this also lets you build native integration with your existing WaWi or ERP system, which the SaaS tools handle poorly.
Option 4: Migrate to your ERP/WaWi. If you already run JTL, Pixi, plentymarkets, Billbee, SAP, or any other warehouse management system, the cleanest path is often to retire Stocky entirely and let the ERP own inventory planning. This requires that your ERP's Shopify connector is solid and that your team is comfortable working in the ERP rather than in Shopify Admin. For mid-size DACH stores this is often the right answer because the ERP was supposed to be the source of truth all along.
Option 1: Move to a dedicated inventory SaaS. Tools like inFlow, Cin7, Katana, Prediko, and Sumtracker do most of what Stocky did, sometimes more. The trade-off is the subscription cost — most start at $99-299/month and scale by SKU count or order volume. For stores with $50K+ monthly revenue and 500+ SKUs, this is the obvious replacement and usually the right answer. For smaller stores it is a meaningful new line item on the app bill.
Option 2: Move to a Shopify-native inventory plus spreadsheet. Use Shopify Admin for stock levels and low-stock alerts, then run forecasting and purchase orders in a spreadsheet that pulls data via the Shopify API. Cheap, flexible, and brittle. Works for stores with under 200 SKUs and one or two suppliers. Falls apart at scale and burns staff time that costs more than the SaaS subscription would have.
Option 3: Build a custom replacement. For stores spending €200+/month on inventory tooling already, or stores where Stocky was deeply woven into the warehouse and supplier workflow, a custom-built inventory module tailored to exactly how your operation runs makes the most economic sense. You pay a one-time build cost, own the code, and pay nothing per order or per SKU forever. For stores in the DACH region this also lets you build native integration with your existing WaWi or ERP system, which the SaaS tools handle poorly.
Option 4: Migrate to your ERP/WaWi. If you already run JTL, Pixi, plentymarkets, Billbee, SAP, or any other warehouse management system, the cleanest path is often to retire Stocky entirely and let the ERP own inventory planning. This requires that your ERP's Shopify connector is solid and that your team is comfortable working in the ERP rather than in Shopify Admin. For mid-size DACH stores this is often the right answer because the ERP was supposed to be the source of truth all along.
When a Custom Build Pays Back (And When It Doesn't)
The math on a custom inventory module is more favorable than most merchants assume, but it is not universal. A useful rule of thumb: if your current inventory tooling is costing you €200/month or more, and it would be expected to grow with order volume, a one-time custom build typically pays back within 8 to 18 months.
Worked example. A mid-size DACH store doing 4,000 orders per month, 800 SKUs, two suppliers. Current Stocky usage is free (it came with Shopify Plus). After Stocky shuts down they have three offers in front of them: inFlow at $179/month, Cin7 at $349/month, Katana at $199/month. Pick any one — call it €200/month. Over five years that is €12,000 plus annual price increases. Add 25-30% for the percentage of those plans that escalate by SKU count and order volume as the store grows, and the realistic five-year SaaS cost is closer to €15,000-17,000.
A custom build for exactly the forecasting, purchase-order, and supplier-workflow features that store actually uses, integrated directly with Shopify and their existing WaWi, typically costs €8,000-14,000 as a one-time investment. After build, ongoing cost is hosting plus minor maintenance — call it €30-50/month. Five-year cost: roughly €10,000-15,000. The math is close enough that the deciding factor is usually fit, not price. The custom build wins on fit because it does only the workflow steps your operation actually needs and integrates with the systems you already use, instead of forcing your team to learn another SaaS dashboard.
The custom build does not pay back for stores under 500 orders per month or stores that only used Stocky's simplest features (low-stock alerts, basic stock-on-hand views). For those stores, Shopify's native tools plus a $29-49/month app is the right answer. The point of a custom build is to replace a workflow that scales painfully, not to over-engineer something a $20 app would handle.
Worked example. A mid-size DACH store doing 4,000 orders per month, 800 SKUs, two suppliers. Current Stocky usage is free (it came with Shopify Plus). After Stocky shuts down they have three offers in front of them: inFlow at $179/month, Cin7 at $349/month, Katana at $199/month. Pick any one — call it €200/month. Over five years that is €12,000 plus annual price increases. Add 25-30% for the percentage of those plans that escalate by SKU count and order volume as the store grows, and the realistic five-year SaaS cost is closer to €15,000-17,000.
A custom build for exactly the forecasting, purchase-order, and supplier-workflow features that store actually uses, integrated directly with Shopify and their existing WaWi, typically costs €8,000-14,000 as a one-time investment. After build, ongoing cost is hosting plus minor maintenance — call it €30-50/month. Five-year cost: roughly €10,000-15,000. The math is close enough that the deciding factor is usually fit, not price. The custom build wins on fit because it does only the workflow steps your operation actually needs and integrates with the systems you already use, instead of forcing your team to learn another SaaS dashboard.
The custom build does not pay back for stores under 500 orders per month or stores that only used Stocky's simplest features (low-stock alerts, basic stock-on-hand views). For those stores, Shopify's native tools plus a $29-49/month app is the right answer. The point of a custom build is to replace a workflow that scales painfully, not to over-engineer something a $20 app would handle.
Migration Checklist: What to Do Between Now and August 31
Whichever path you pick, the migration window is short. Here is a practical sequence that minimizes risk:
1. Export your Stocky data this week. Suppliers list, lead times, reorder points, historical purchase orders, forecasting data. Shopify will provide read-only access after August 31 but do not rely on it. Get your data out now, in a format you control.
2. Document your current Stocky workflows. Walk through one week of normal operation and write down everything Stocky does — who looks at which report, when purchase orders get generated, how alerts get routed. This becomes your requirements document for whatever replaces Stocky, and forces you to discover the workflow assumptions you forgot were tied to Stocky.
3. Make the build-or-buy decision by mid-June. A custom build typically needs 6-10 weeks for planning, development, and testing. A SaaS migration typically needs 4-6 weeks for setup, data import, and team training. Either way, leaving the decision until July puts you in a panicked migration in August.
4. Run both systems in parallel for 30 days. Whatever you migrate to, keep Stocky generating reports alongside the new system for at least four weeks. Compare forecasts, compare reorder suggestions, look for discrepancies. The most common migration failure is discovering on September 15 that the new system was miscounting one warehouse location all along.
5. Sunset Stocky on your timeline, not on August 31. If you do the migration cleanly, you should be operating fully on the replacement by mid-August with Stocky as a backup that you stop using two weeks before the deadline. Do not let Shopify's calendar force your cutover into the last week of August when half your team is on holiday.
For stores in the DACH region, this is also the moment to think about consolidation. If you are about to spend money on a new SaaS for inventory, it is worth asking whether other Shopify apps on your stack are also good candidates to consolidate into one custom build at the same time — invoicing, address validation, order tracking. The fixed cost of a custom development project amortizes much better across three workflows than across one. Services like NoRentApps specialize in building consolidated inventory and operations apps for European Shopify stores that replace four or five SaaS subscriptions with a single owned codebase.
1. Export your Stocky data this week. Suppliers list, lead times, reorder points, historical purchase orders, forecasting data. Shopify will provide read-only access after August 31 but do not rely on it. Get your data out now, in a format you control.
2. Document your current Stocky workflows. Walk through one week of normal operation and write down everything Stocky does — who looks at which report, when purchase orders get generated, how alerts get routed. This becomes your requirements document for whatever replaces Stocky, and forces you to discover the workflow assumptions you forgot were tied to Stocky.
3. Make the build-or-buy decision by mid-June. A custom build typically needs 6-10 weeks for planning, development, and testing. A SaaS migration typically needs 4-6 weeks for setup, data import, and team training. Either way, leaving the decision until July puts you in a panicked migration in August.
4. Run both systems in parallel for 30 days. Whatever you migrate to, keep Stocky generating reports alongside the new system for at least four weeks. Compare forecasts, compare reorder suggestions, look for discrepancies. The most common migration failure is discovering on September 15 that the new system was miscounting one warehouse location all along.
5. Sunset Stocky on your timeline, not on August 31. If you do the migration cleanly, you should be operating fully on the replacement by mid-August with Stocky as a backup that you stop using two weeks before the deadline. Do not let Shopify's calendar force your cutover into the last week of August when half your team is on holiday.
For stores in the DACH region, this is also the moment to think about consolidation. If you are about to spend money on a new SaaS for inventory, it is worth asking whether other Shopify apps on your stack are also good candidates to consolidate into one custom build at the same time — invoicing, address validation, order tracking. The fixed cost of a custom development project amortizes much better across three workflows than across one. Services like NoRentApps specialize in building consolidated inventory and operations apps for European Shopify stores that replace four or five SaaS subscriptions with a single owned codebase.
FAQ
+When exactly does Stocky stop working?
Stocky stops functioning on August 31, 2026. After that date the web interface no longer loads, the APIs stop responding, and scheduled tasks like purchase order syncs stop running. Shopify has said read-only data access will continue for a limited time after the shutdown so merchants can export their data, but the working app — the one that runs your inventory planning — disappears on that date. New installations were already disabled on February 2, 2026.
+Will Shopify's native inventory tools fully replace Stocky?
Only for the simplest use cases. Shopify Admin natively handles stock-on-hand tracking, low-stock alerts, and multi-location transfers. It does not provide demand forecasting, automated purchase order generation, supplier records with lead times, or reorder suggestions tied to forecast and lead time. If your use of Stocky was just to see stock levels, you are fine. If you used it for forecasting and purchase orders, you will have a real gap that needs a dedicated tool or a custom build.
+Can I still get my Stocky data out after August 31?
Shopify has announced that read-only access will continue for a limited time after the shutdown, but the duration has not been precisely defined and the working API endpoints will be gone. The safe approach is to export everything — supplier lists, lead times, reorder points, historical purchase orders, forecasting outputs — well before August 31 and store it in a format you control. Treat August 31 as the last day Stocky data is reliably available, not the start of a grace period.
+Is a custom inventory app realistic for a mid-size store, or only for enterprise?
It is realistic for mid-size stores when the alternative is paying €200+/month for an inventory SaaS that will scale with your order volume. A custom-built inventory module covering forecasting, purchase orders, and supplier workflow for a typical European Shopify store costs €8,000-14,000 as a one-time build and pays back in 8-18 months versus the SaaS alternative. For stores under 500 orders per month or that only used Stocky's simple alerting, a custom build is overkill and Shopify's native tools plus a $29-49/month app is the right answer.