Skip to main content
PandaCodeGen
Back to Insights

Shopify operations

Shopify Stocky Sunset: August 31, 2026

Shopify says Stocky stops working for inventory management after August 31, 2026. That is read from its transition documentation, checked August 8, 2026. Work backwards from that date rather than from when you happen to read this, and confirm the current position on that page before you plan against it. Before then: export the history you are required to keep, write down what each of your workflows actually does, test whatever you are moving to, fix anything that talked to Stocky, and show your team how the new thing works.

Status verified August 8, 2026 against Shopify's current migration guidance, and re-checked on 13 September 2026.

Update: this date has passed

The deadline in the title was 31 August 2026, which is now behind us, so read the rest of this page as a record of what was required rather than a plan you still have time to run. If you migrated, nothing here changes. If you did not, the position on 13 September 2026 is this: Stocky no longer manages inventory and its APIs stopped on the same date, so anything that called them is already failing. Shopify has said it provides read-only access for a limited time, and it has not published an end date for that window, which makes exporting purchase orders, stock counts and supplier records the only item on this page that is still urgent. Do that first, then work through the rest in order.

Hassan Jamal·Apr 25, 2026·10 min read

Confirmed timeline and impact

  • Stocky was delisted from the Shopify App Store on February 2, 2026. No new installs and no re-installs, so if you remove it from a store you cannot put it back. Check Shopify's own transition documentation for the current status rather than relying on a date reported second-hand.
  • Stocky ships with Shopify POS Pro rather than as a separate purchase, which is why many merchants have it running without having chosen it.
  • Stocky inventory management stops after August 31, 2026.
  • Shopify says read-only access remains for at least 90 days after the date, for exporting your data on the current migration page.
  • Historical purchase orders and stocktakes do not move into Shopify automatically.
  • Stocky APIs stop working on August 31, 2026, so connected tools must be updated.

If you are reading this close to the date

The full sequence below assumes you have time to map workflows and trial a replacement. If you do not, order the work by what is permanently lost rather than by what is most urgent-feeling, because those are different lists and only one of them matters after the date passes. Where custom code is the answer, PandaCodeGen builds it from $1,500 at a fixed price, has no minimum project size, and hands you code you own.

  1. Supplier records first. Shopify's own transition guidance states suppliers cannot be exported from Stocky. Everything else has a file format; this does not. Copy supplier names, contacts, terms, lead times and per-supplier costs out by hand into a spreadsheet today, before anything else on this page.
  2. Close and receive open purchase orders. A purchase order still open when the app stops is a reconciliation problem you inherit, not a record you can re-open later.
  3. Export purchase order history and stocktakes. These do not move into Shopify automatically, and read-only access is a window rather than a permanent archive.
  4. List anything that calls the Stocky API. Those integrations fail on the date rather than degrading, so they need an owner before it, not after.

Choosing the replacement is the one step that is safe to do afterwards. Inventory tooling can be swapped again later; supplier history you did not copy out is gone.

Preserve

Exports, source definitions, dates and retention.

Map

Every Stocky task, role, input and output.

Test

Native, vendor or custom workflow acceptance.

Cut over

Training, freeze, launch, support and rollback.

What to do first, and what can wait

The seven steps below are ordered deliberately, and three of them stop being possible after August 31, 2026. If you are reading this with weeks rather than months left, the order matters more than the completeness: do the irreversible things now, compress the reversible ones, and accept that some of the later steps will run after the deadline rather than before it. Nothing below asks you to have chosen a replacement first. If the sunset has also opened a wider platform question, that is covered separately in Shopify compared with a custom storefront and what headless commerce means.

  • Irreversible, do now: export everything (step 2). Purchase order history, supplier records, landed cost inputs and stocktakes do not migrate to Shopify automatically, and the APIs stop on the sunset date. Treat anything you have not exported as work you will have to do inside a closing window.
  • Irreversible, do now: do not uninstall Stocky first (step 1). Uninstalling before exporting removes the access you need to preserve the data, and Shopify says Stocky cannot be reinstalled.
  • Irreversible, do now: settle what you keep from read-only access (step 7). Shopify says you keep read-only access to export your data for at least 90 days after that date, so treat anything you have not exported as unavailable rather than delayed.
  • Was time-boxed to before 31 August 2026: mapping the workflows (step 3) against a running Stocky meant comparing observed behavior rather than memory. After the shutdown this one is reconstruction, so lean on read-only exports and on whatever downstream systems received the data.
  • Reversible, and safe to do after the deadline: choosing the replacement (step 4). The right answer depends on the workflow map, so a short runway is a reason to compress this decision rather than to bring it forward.
  • Can run after the date: acceptance testing, cutover rehearsal and rollback (steps 5 and 6). If the runway is short, these happen on the replacement rather than in parallel with Stocky, which is slower but not blocked.
The ordering mistake that costs the most

The common failure is selecting a replacement app in week one, migrating into it, and only then discovering which Stocky workflows it cannot reproduce. By then the export window has narrowed and the original system may already be uninstalled. Export first, map second, choose third.

Why you should not uninstall Shopify Stocky yet

Shopify advises merchants to avoid uninstalling Stocky unless Shopify Support explicitly directs it or the app is no longer required. Stocky cannot be reinstalled from the App Store, and data might not be recoverable after uninstalling. Preserve the existing environment while you export and validate the replacement. Keeping your own copy of operational data is the same ownership question set out in who owns your website and its data.

What Stocky data can you export before it shuts down?

Shopify says historical purchase orders and stocktakes will not automatically move to Shopify. Export them through Stocky's built-in reports while read-only access lasts. Suppliers cannot be exported from Stocky, so build and validate a separate supplier register from the records available to your business. Where a business wants its own view of that data afterwards, the operations dashboards we build show one approach.

  • Purchase orders and their status, line items, dates and costs.
  • Any stocktake or stock-adjustment record you need for running the shop, for finance, for tax, or for an audit.
  • Supplier names and contacts, the terms you agreed, lead times, currencies, and which products came from whom.
  • Inventory, SKU, barcode, location and cost references needed to reconcile the transition.
  • User, permission and process documentation for current Stocky work.
  • Copies of integration configuration, scheduled exports and downstream mappings.
Validate the archive

An export is not complete merely because a file downloaded. Record the report name, filters, timezone, currency, row count, date, owner and checksum where appropriate. Open the file, sample records against Stocky and test that authorized users can retrieve it from the approved archive.

What actually stops working

This is the audit to run first, because it decides how much of the rest applies to you. Stocky carried a set of operations that Shopify's native inventory tools do not reproduce one for one, and the gap is where your replacement budget goes. Check each of these against how your team actually orders stock, rather than against the feature list.

  • Demand forecasting and suggested reorder quantities driven by sales velocity.
  • Purchase order creation, approval and receiving against those forecasts.
  • Supplier records: contacts, terms, lead times and per-supplier cost history.
  • Landed-cost calculation, which is what makes SKU-level margin real rather than estimated.
  • Minimum and maximum reorder thresholds and the alerts built on them.
  • Stocktakes, transfers and the barcode workflows used inside them.
  • Multi-location coordination where stock moves between warehouses or stores.

Two consequences are worth naming because they surface later rather than on the day. Once landed-cost calculation stops, per-SKU margin becomes an estimate, which changes pricing and cash-flow forecasting rather than just reporting. And the supplier export is the line that scales with your business: twenty suppliers is an afternoon, two hundred is work that has to be scheduled, and it cannot be done after the date. Count yours before you plan the week. Confirm each item against Shopify's own transition documentation rather than this list, because Shopify is the authority on what it is replacing.

What changes when you replace Shopify Stocky?

This was best done while Stocky was still running, because it became guesswork the moment the app stopped; if you are reading after 31 August 2026, reconstruct what you can from read-only access and from whatever downstream systems received the data. The middle column is Shopify's own guidance for each workflow, not our assessment of it. The right-hand column is what you have to prove works for your operation before accepting the replacement.

WorkflowCurrent Shopify guidanceAcceptance question
Purchase ordersShopify admin can create and manage them, with documented feature differencesDo approvals, receiving and supplier communication still work?
TransfersInbound and outbound transfers move to Shopify workflowsCan each location initiate, receive and reconcile correctly?
CountsShopify describes inventory adjustments and POS Quick count optionsAre barcode, partial count and audit requirements met?
ForecastingShopify documents inventory insights and Sidekick-assisted planningAre the method, access and review controls acceptable?
ReportingSome Stocky reports differ or have no direct native equivalentWhich decision or compliance output must be recreated?
IntegrationsStocky APIs cease on August 31, 2026What supported interface replaces every read and write?

Which Stocky replacement fits your workflow?

There is no universal replacement price or best option. Obtain current vendor terms and a comparable scope, then include configuration, migration, integration, training, support, security, maintenance and exit in the decision. The four routes below are gated on requirements you have tested, not on which product looks closest.

  • Use Shopify's native inventory tools when tested workflows meet the operational and reporting requirements.
  • Evaluate a third-party inventory product when it meets defined gaps at acceptable total cost, security and exit risk.
  • Build a scoped custom extension when the requirement is differentiated, stable and supportable.
  • Use a hybrid only when ownership and system-of-record boundaries are explicit.

There is no universal replacement price or best option. Obtain current vendor terms and a comparable scope. Include configuration, migration, integration, training, support, security, maintenance and exit in the decision. The build-or-buy comparison itself is set out in our build versus buy worksheet, a review of recurring Shopify app charges covers the subscription side, and the project side is collected in our migration cost breakdown.

How to test a Stocky replacement before cutover

This is where a mapped workflow becomes evidence. Seven tests, and the ones people skip are the awkward ones: a partial receipt, a count run on the actual devices and roles used in stores, and every integration that previously called a Stocky API. This step can still run after the sunset date, slower but not blocked.

  • Create, approve, receive, partially receive and close a test purchase order.
  • Transfer inventory between representative locations and reconcile quantities.
  • Run a count or adjustment with the devices and roles used in stores.
  • Test low-stock, replenishment, forecasting and exception handling.
  • Reproduce required supplier, finance and operational reports.
  • Verify permissions, audit history, exports, backups and recovery.
  • Exercise every integration that previously called a Stocky API.

How to leave Stocky without losing stock data

Inventory truth is the thing you are protecting, so name the system of record and the freeze window for each field before anything moves. Six steps cover it. Note the timing constraint in the fifth: keeping current Stocky access until sign-off only works before the sunset date, after which Shopify's current transition page describes read-only export access for at least 90 days.

  • Name the system of record and freeze window for each inventory field.
  • Reconcile quantities, open purchase orders, transfers and locations at the agreed cutoff.
  • Publish role-based instructions and train every affected team.
  • Set go or no-go criteria, escalation contacts and a support window.
  • Keep the validated archive and current Stocky access intact until the owner signs off.
  • Monitor discrepancies and integrations daily through the stabilization period.

How long will Shopify keep Stocky read-only?

Shopify states you keep read-only access to export your data for at least 90 days after that date, as specified on its current transition page. That window is finite, so do not use it as your retention plan. and validate your exports before August 31, 2026.

We scope transitions of this kind as part of e-commerce development and custom engineering, with project tiers on the pricing page and build examples in our client work. If storefront performance is on the same roadmap, our Shopify store speed checklist and headless Shopify guide cover that track.

Get your Stocky migration plan

We will inventory Stocky data, workflows and integrations, define acceptance tests and scope the least disruptive native, vendor or custom transition.

Primary sources

Frequently Asked Questions

What is the Shopify Stocky sunset date?

Shopify says Stocky can no longer be used to manage inventory after August 31, 2026. Stocky APIs stop on that date, while read-only access remains for an unspecified period. Shopify delisted Stocky from the App Store on February 2, 2026. These facts were rechecked in Shopify's transition guide on July 24, 2026.

What features are lost when Stocky sunsets in August 2026?

Shopify says historical purchase orders and stocktakes do not move automatically, suppliers cannot be exported, Stocky APIs stop, and some Stocky-specific features may work differently or may not yet exist in Shopify Admin. Inventory the exact workflows your team uses and test each against Shopify's current transition guide before choosing a replacement.

What replaces Stocky in native Shopify inventory tools?

Shopify's current guide points merchants to Shopify Admin and Shopify POS for transfers, purchase orders, quantity adjustments, inventory history, in-store workflows, APIs, Shopify Flow, and other current inventory capabilities. Some Stocky-specific workflows differ or may not yet be available, so verify requirements against the live account and current documentation.

Should I migrate to Sumtracker, Fabrikator, Prediko, or another inventory app?

Compare Shopify Admin, current inventory apps, and custom software against verified workflow fit, data migration, APIs, security, support, portability, vendor terms, internal capability, time to implement, and total cost. No option is a permanent fix, and custom software still depends on maintainers, hosting, services, and third-party components.

What does it cost to rebuild Shopify headless with custom inventory?

A headless rebuild with custom inventory sits beyond our standard tiers and is scoped separately, because the inventory logic is bespoke by definition. Before pricing it, check whether an existing app already covers your workflow. Replacing Stocky is usually a purchasing decision, and only becomes an engineering one if nothing on the market fits how you actually order.

How do I export my Stocky data before August 31, 2026?

Use Stocky's built-in reports to export the historical records you need, verify the exports, store them securely, and document retention and access. Shopify says suppliers cannot be exported, so recreate and validate required supplier data manually. Do not rely on the unspecified post-cutoff read-only period as the retention plan.

Why did Shopify deprecate Stocky?

The current Shopify help pages document the transition and replacement capabilities but do not provide a basis for attributing a broader motive. Plan from the announced dates, export limitations, API cutoff and workflow differences rather than speculating about why Shopify made the product decision.

How long does a Shopify headless rebuild with custom inventory take?

Work backwards from August 31, 2026, because that is when access ends rather than a date you can negotiate. Export what you need first and separately from choosing a replacement, so that if the replacement decision takes longer than expected you still hold your own data. Do not leave the export until the week before.