Shopify is sunsetting
Stocky. Now what?

Bottom line up front: if you run inventory through Stocky, you have a hard deadline and a data problem, not a someday problem. Shopify has confirmed Stocky ends on August 31, 2026, your records do not come with you automatically, and the native replacement is not yet a like-for-like swap. This is what happened, why, and exactly what to do depending on whether you sell on Shopify or build on it.

I helped build and scale the Partner Program in Shopify's early days, and I have watched this exact pattern run for over a decade. Shopify buys or builds a capability, bundles it, lets it sit, then folds it into the core and retires the standalone. Stocky is the latest name on that list. The panic is optional. The deadline is not.

What Shopify actually
announced.

Shopify is fully retiring Stocky, its first-party inventory and purchase-order app included free with Shopify POS Pro. This is a complete shutdown, not just a delisting. Shopify's Help Center states plainly that "Stocky is no longer available after August 31, 2026" (Shopify Help Center, Migrating from Stocky, 2026).

There are two dates that matter. On February 2, 2026, Stocky was pulled from the App Store, so no one can install it fresh, and if you uninstall it you cannot get it back. On August 31, 2026, the app and all of its APIs stop functioning. Stocky launched back in 2015 and was acquired by Shopify; after eleven years it is being switched off.

For context on how well the bundled tool served merchants, its App Store listing sits at a 2.8 out of 5 rating across 208 reviews (Stocky, Shopify App Store, 2026). That is a large, and clearly frustrated, install base. Stocky shipped with POS Pro, which runs $89 per location each month, so plenty of retailers were paying for the subscription partly to get it.

Why kill a free app
people paid to get.

Shopify's stated reason is consolidation. It wants inventory to live inside the core admin and POS for "a unified experience, faster feature improvements, and reduced need for multiple apps" (Shopify Help Center, 2026). Stocky ran on a separate codebase that Shopify never fully wired into the platform, and its development had visibly stalled.

The deeper reason is the one I have watched play out every year. Every edition, Shopify widens the surface it considers core. Tobi Lütke has said internally that AI use is a baseline expectation, not optional (Tobi Lütke on X, April 2025), and native inventory with Sidekick demand hints is exactly the kind of thing Shopify now wants to own outright rather than run as a bolt-on app. Retiring Stocky is that thesis, applied to a specific tool.

Why it matters: this is the same move that hit Shopify Scripts before it. If your operation depends on a first-party tool that sits slightly outside the core, treat that dependency as temporary and plan for the day it gets absorbed. That is not cynicism. It is how the platform has worked for a decade, and it is covered more broadly in the ecosystem value map.

The part most people
are missing.

Here is the sharp edge. When Stocky goes dark, your historical data does not automatically flow into Shopify's native inventory. Past purchase orders and stocktakes do not migrate, and your supplier list cannot be exported at all (Shopify Help Center, 2026). After August 31 you get read-only access for a limited window, reported unofficially at around 90 days, and then the records are gone.

If you have years of purchase history, cost data, and supplier records in Stocky, that is real operating knowledge. Losing it means rebuilding reorder logic and supplier terms from memory. So the first task is not choosing a replacement. It is getting your data out while the app still runs.

If you sell
on Shopify.

Start with an honest read of what you actually used Stocky for. If it was basic stock counts and the occasional purchase order at a single location, Shopify's native tools in admin and POS will likely cover you, and the switch is mostly housekeeping. If you leaned on demand forecasting, reorder points, or printing labels straight from a PO, native is not there yet.

Shopify's own documentation lists automated demand forecasting, minimum and maximum reorder levels, CSV import into purchase orders, barcode-scanner receiving in the admin, and PO barcode-label printing as "not yet available" or "expected soon" as of mid-2026. Those are not edge cases for a growing brand. They are the daily workflow. Getting inventory wrong is expensive: IHL Group estimates global retail loses $1.73 trillion a year to out-of-stocks and overstocks, equal to 6.5% of retail sales, with North America alone accounting for $415 billion (IHL Group, Retail Inventory Crisis, September 2025).

So match the tool to the operation. Here is the shortlist merchants are moving to, with rough entry pricing.

Pick by SKU count, number of locations, and how much you rely on forecasting. Do not wait until August to test. Run your chosen tool in parallel for a few weeks so you catch the gaps before the old system disappears, not after.

If you build
on Shopify.

For app founders, a Shopify sunset is a demand signal. Stocky is leaving thousands of merchants without forecasting, reorder logic, and PO-based label printing, and native tools have publicly acknowledged those gaps. That is a window. The apps moving fastest into the threads, Prediko and inFlow among them, understand that the moment a first-party tool dies is the moment its users go shopping.

The catch is where you build. Shopify's Transfers API is live, but the purchase-order API is still "not available and under consideration" as of mid-2026, which limits how deeply a third party can automate the exact workflow Stocky users are losing. Build where a general platform structurally cannot follow: deep demand forecasting, multi-supplier logic, barcode and receiving workflows, and integrations off Shopify's surface. Retailers deploying AI and machine learning in inventory posted sales growth 2.3 times higher than laggards (IHL Group, 2025), so the forecasting layer is where the value and the defensibility sit.

The strategic frame is the same one I use for every edition. Read the Spring 2026 Editions for where Shopify is expanding next, and assume anything adjacent to the core is a candidate for absorption. Build the thing the platform will not bother to build, or will not build well.

Questions I keep
getting asked.

The move here is simple: export your data now, pick a replacement that matches how you actually run inventory, and treat any first-party tool near the edge of the core as a temporary convenience. For the wider view of where Shopify absorbs value, start with the ecosystem value map.