Shopify Stocky Shuts Down Aug 2026: What to Do

Stocky stops working on 31 August 2026, and if you use it for purchase orders or forecasting, that data needs to come out before it does.

Shopify has confirmed the shutdown. Features were already being removed through 2025, and the app was delisted from the App Store on 2 February 2026. This is a migration with a deadline, not a rumour.

What is actually happening

| Date | What changed | |---|---| | July 2025 | Inventory transfers and min/max forecasting removed | | 2 February 2026 | Delisted from the Shopify App Store | | 31 August 2026 | Stops working entirely |

Shopify is moving core inventory functionality into the admin itself. What lands there covers the basics — stock levels, adjustments, multi-location. What it does not cover is the reason most people used Stocky: demand forecasting, replenishment workflows, purchase order management and supplier records.

Do this first: export your data

Nothing is recoverable after the shutdown. Before anything else, export:

1. Purchase orders — including history, not just open POs. This is your supplier lead-time record.
2. Supplier details — contacts, terms, minimum order quantities.
3. Cost prices — if your COGS lives in Stocky rather than Shopify, this is the most painful thing to lose.
4. Stock adjustment history — needed for auditing and for any forecasting tool you move to.

Export to CSV and keep it somewhere outside both Stocky and Shopify. Do this now rather than in August; a delisted app receives no support if an export fails.

Check where your cost data really lives

# Confirm cost is set on variants in Shopify itself, not only in Stocky.
query {
  products(first: 50) {
    edges { node {
      title
      variants(first: 10) {
        edges { node {
          sku
          inventoryItem { unitCost { amount currencyCode } }
        } }
      }
    } }
  }
}

If unitCost comes back null across your catalogue, your margins are living in Stocky alone — and that is the single most important thing to export.

Choosing a replacement

Pick based on what you actually used Stocky for. Most merchants used one or two features, not all of them.

If you used it mainly for purchase orders

You need PO creation, supplier records and receiving. This is the most common use and the easiest to replace — several mid-market tools cover it well.

If you used it for demand forecasting

This is the harder gap. Forecasting tools differ substantially in method: some extrapolate simple velocity, others account for seasonality and lead-time variability. If you have strong seasonality — and most Gulf retailers do around Ramadan and Eid — test against your own history before committing.

If you used it for multi-location stock

Shopify's native multi-location handling has improved considerably. Check whether the admin now covers your case before paying for anything.

If you barely used it

Plenty of stores installed Stocky, used it twice and forgot. Check before you migrate anything — the answer may be "nothing to do but export".

Evaluating candidates

Whatever you shortlist, test these before committing:

• Does it sync both ways? A tool that reads Shopify but cannot write stock back creates manual work forever.
• How does it handle multi-currency cost prices? Relevant if you buy in USD and sell in SAR or AED.
• What is the sync frequency? Real-time versus hourly matters a lot during a sale.
• Can you export your data out again? Do not solve a lock-in problem by creating another one.
• Does it handle your channel mix? If you sell on marketplaces as well as Shopify, single-channel tools will not do.

A realistic migration sequence

1. Now — export everything from Stocky.
2. Audit — list which Stocky features you genuinely used in the last six months.
3. Shortlist — two or three tools covering those specific features.
4. Trial in parallel — run the new tool alongside Stocky and compare its numbers against reality for a few weeks.
5. Migrate cost prices into Shopify — set unitCost on inventory items so the data survives regardless of which tool you use next.
6. Cut over well before 31 August.

Pushing cost prices into Shopify itself is the step most worth doing:

mutation {
  inventoryItemUpdate(
    id: "gid://shopify/InventoryItem/123456789"
    input: { cost: "24.50" }
  ) {
    inventoryItem { id unitCost { amount } }
    userErrors { field message }
  }
}

Cost stored on the inventory item belongs to your store, not to an app — so the next migration is easier than this one.

Frequently asked questions

Will Shopify migrate my Stocky data automatically?

No. Export is your responsibility, and after 31 August the data is gone.

Is the native admin inventory enough?

For stock levels, adjustments and multi-location, often yes. For forecasting, purchase orders and supplier management, no — that is the gap you are replacing.

What happens to open purchase orders on the cutoff date?

Anything unreconciled becomes a manual problem. Close out or migrate open POs before the deadline rather than after.

Related reading

• What a Shopify store really costs to run
• How to choose a Shopify development agency
• Shopify development — our service page

Need a hand?

We help Shopify merchants in the USA, UAE, Saudi Arabia, Qatar and the UK migrate systems without losing data. If you need help planning the move off Stocky, get a free audit or see our Shopify development services.