Stocky Shuts Down August 31. What Actually Doesn't Migrate.

Stocky stops being a working inventory app after August 31, 2026. After that date, purchasing, stocktakes, and day-to-day inventory work move into the Shopify admin and Shopify POS. This is not a soft deprecate. The app goes read-only for exports, then you are done managing stock there.

If you already run purchase orders or stocktakes in Stocky, the risk is not "Shopify loses your live inventory counts." Live quantities already live in Shopify. The risk is the history and the operational data that never auto-moves: old POs, stocktake records, supplier profiles, and anything you built around Stocky's APIs.

What Actually Doesn't Migrate

Shopify is explicit about the gaps. From their transition guide:

• Historical purchase orders and stocktakes do not auto-move into Shopify. If you need them for taxes, audits, or vendor disputes, export them yourself using Stocky's built-in reports.
• Suppliers cannot be exported from Stocky. Names, contacts, lead times, payment terms, and product mappings have to be captured by hand into a spreadsheet or rebuilt as supplier records in Shopify.
• Historical POs cannot be imported into native Shopify purchase orders. CSV upload for native POs only adds line items to a new draft. It does not bring over past statuses, received quantities, or supplier links.
• Stocky APIs stop working on August 31, 2026. Anything that still reads Stocky for POs, transfers, or stocktakes breaks that day. Rebuild those integrations against Shopify's inventory APIs, not Stocky.

That last point matters more than it sounds. Teams that wired reporting, ERPs, or custom tools into Stocky often discover the dependency a week before cutoff. Map those connections now.

The 90-Day Export Window Is Not Extra Runway

After August 31 you get read-only access to export data for at least 90 days. Treat that as a safety net, not a plan.

Read-only means the purchasing workflow is already dead. You cannot create POs, run stocktakes, or keep operating inside Stocky. APIs are already off. If your replacement process is not live by August 31, you have a hole in purchasing — not a graceful extension.

Also: do not uninstall Stocky before your exports are finished. Shopify warns that data from an uninstalled Stocky app might not be retrievable if you try to bring it back, and Stocky is no longer available to reinstall from the App Store for new installs.

What to Pull Before August 31

Shopify's own prep list is short. Do it in this order:

1. Export key Stocky data while the app still writes. Pull completed purchase order reports as CSV, stocktake history, and historical cost data from Stocky's reports. Anything you might need for an audit later is cheaper to export now than to reconstruct later.
2. Close in-flight purchase orders. Finish open POs in Stocky before the cutoff.
3. Stop creating new Stocky POs about 14 days before August 31. That buffer exists so receiving can finish inside Stocky instead of straddling two systems.
4. Receive and close everything still open or in transit before the deadline.
5. If a PO is still open at cutover, recreate only the remaining quantities as a purchase order or transfer in Shopify — not the whole historical PO.

While Stocky is still live, also capture anything Shopify does not document as an export: PO notes, internal comments, par levels, reorder points, and any custom fields your team actually uses day to day. Put those in a spreadsheet you control. Do not assume they will be waiting for you in native Shopify.

What Native Shopify Covers Now (and What It Doesn't Claim)

Native inventory in Shopify admin and POS already covers the core loop: transfers between locations, purchase orders from suppliers, quantity adjustments, and inventory history. Store staff can send, receive, and adjust stock in POS with permission controls and an audit trail.

As of June 22, 2026, native purchase orders create transfers when you are ready to receive. That links what you ordered and what it cost to the physical movement of stock. You can receive in admin or POS, handle partial deliveries as separate shipments, keep the transfer linked to the PO, and import PO line items by CSV.

That is a real improvement for receiving. It is not the same claim as "Stocky's reorder and forecasting stack is fully replaced." Shopify documents Sidekick prompts for reorder suggestions and drafted POs, plus low-stock alerts via Shopify Flow. Whether that matches how your team used Stocky's planning tools is an operations question — verify it against your actual SKUs and locations before you cut over. If you need dedicated forecasting, multi-supplier case packs, or weighted-average costing, plan for metafields, a third-party inventory app, or both. Shopify's own migration guide flags that some Stocky-specific features work differently or are not available yet.

Common Pitfalls We See

• Assuming live inventory is the only thing that matters. Counts already live in Shopify. History, suppliers, and PO notes are what disappear.
• Leaving open Stocky POs into September. Anything still open at cutover has to be recreated manually for the remaining quantities.
• Planning around the 90-day read-only window. That window is for export. Purchasing is already over.
• Forgetting Stocky API consumers. Custom reports, middleware, and ERP hooks fail on August 31 whether or not someone remembers they exist.
• Skipping a parallel test. Run a test PO, transfer, and adjustment in Shopify (and in POS if you use it) before you stop using Stocky.
• Uninstalling Stocky early. Export first. Keep the app installed until you have the files you need.

Need a Clean Cutover Before August 31?

Stocky migration is mostly export discipline, supplier rebuild, and workflow practice — not a theme rebuild. We help Shopify merchants get through it without losing purchasing history or waking up on September 1 with open POs and no process:

• Export and retention plan — which Stocky reports to pull, how to store them, and what to capture manually while the app is still live.
• Supplier and PO rebuild — recreate supplier records and open remaining quantities as native Shopify purchase orders or transfers.
• Receiving workflow setup — native POs that create transfers, partial receipts, and POS receiving for floor staff.
• Integration updates — replace Stocky API consumers with Shopify inventory and Transfers workflows.
• Parallel run — a short overlap where the team practices the new path before Stocky goes read-only.

If Stocky still runs your purchasing, the calendar is the constraint. Get in touch and we will map what you need to export, what to rebuild in Shopify, and what (if anything) still needs a third-party inventory tool before August 31.