Stocky Shutdown: Shopify Inventory Checklist Before Aug. 31

Stocky is not just another Shopify app being retired. For many retailers, it has been the place where purchase orders, stocktakes, supplier records, transfers, receiving workflows, and replenishment habits quietly lived for years.

That matters because Shopify has confirmed that Stocky will no longer be available after August 31, 2026. After that date, merchants need to manage inventory in Shopify admin, Shopify POS, or another connected inventory system.

The deadline is close enough that this is no longer a “review later” task. It is an inventory automation deadline. If your team uses Stocky only occasionally, the migration may be simple. But if Stocky supports daily retail operations, this change can affect purchasing, receiving, stock counts, supplier communication, reporting, local pickup promises, and warehouse or ERP integrations.

This article explains what Shopify retailers should export, rebuild, automate, and test before August 31, 2026.

What Is Actually Changing?

Shopify is discontinuing Stocky on August 31, 2026. After that date, retailers will no longer be able to use the app for day-to-day inventory operations such as purchase order management, demand forecasting, supplier workflows, replenishment planning, and Stocky-specific reporting.

This does not mean that every piece of inventory data will disappear from Shopify. Product, variant, location, and inventory quantity data already stored in Shopify will remain there. The main risk concerns records, reports, and operational logic that exist only in Stocky or do not have a direct equivalent in Shopify admin or Shopify POS.

There is also an important clarification about the deadline: August 31 is the date Stocky stops operating, but it is not the moment all Stocky data disappears. Shopify guarantees merchants at least 90 days of read-only access after the shutdown so they can export their data. However, read-only access will not support ongoing inventory work, and access beyond that minimum period is not guaranteed.

Merchants should therefore treat the 90-day period as a final recovery window, not an extension of the migration deadline. Critical records should still be exported and verified before August 31 wherever possible. By that date, teams should also have replacement workflows in place for active purchase orders, supplier information, replenishment rules, transfers, reporting, and any other processes currently managed through Stocky.

Start With Data Extraction, Not App Replacement

Many merchants will be tempted to start by asking, “Which app replaces Stocky?” That is the wrong first question.

The first question should be: “What business data do we need to protect before Stocky becomes unavailable?”

Before August 31, export or document:

• completed purchase order reports
• stocktake history
• historical cost data
• current open purchase orders
• supplier names and contact details
• supplier-specific notes that cannot be exported automatically
• supplier SKUs, case packs, minimum order quantities, and lead times
• min/max thresholds or reorder rules used by the team
• custom fields used in Stocky
• recurring reports used by finance, operations, or store managers
• third-party tools connected to Stocky APIs

Shopify’s migration guide says historical purchase orders cannot be imported into Shopify as full historical records. Native CSV upload for purchase orders can add line items to a new draft purchase order, but it does not recreate past statuses, received quantities, or supplier links.

So the goal is not to recreate every old Stocky screen inside Shopify. The goal is to keep enough historical information for audit, finance, supplier review, and operational learning.

A clean export folder should include the raw CSV files, a short description of what each file contains, the export date, and the person responsible for verifying it. This simple documentation will save time later if finance, operations, or support needs to trace a purchasing decision.

Close Open Purchase Orders Before the Cutover

Open purchase orders are one of the easiest places for migration problems to appear. Shopify recommends closing out in-flight purchase orders in Stocky before the sunset date and stopping new purchase orders in Stocky about 14 days before August 31, 2026. For most merchants, that means Stocky should stop being the place where new purchasing work begins by mid-August.

A practical cutover plan looks like this:

1. Export all existing Stocky purchase order records.
2. Identify open, partially received, or in-transit purchase orders.
3. Receive and close everything that can be completed before the deadline.
4. Recreate only the remaining quantities in Shopify admin or the new inventory system.
5. Keep supplier documents, invoices, and receiving notes attached to the new process.
6. Confirm that staff know where the current purchase order now lives.

This is especially important for retailers with multiple stores, warehouses, or seasonal inventory. A purchase order that is half in Stocky and half in a new tool creates confusion about what is ordered, what is received, and what is available to sell.

Map Stocky Workflows to Shopify Admin and POS

Stocky migration is easier when each workflow has a clear new home.

Use a simple workflow map:

• Stocky inventory transfers: move to Shopify inventory transfers.
• Stocky purchase orders: move to Shopify purchase orders or an external procurement tool.
• Stocky stocktakes: move to Shopify POS Quick Count, admin bulk edits, CSV workflows, or a dedicated inventory app.
• Stocky custom fields: move to metafields, metaobjects, notes, or an ERP/WMS field.
• Stocky reports: move to Shopify Analytics, exported reports, or a reporting app.
• Stocky API integrations: move to Shopify inventory APIs, Transfers API, ERP/WMS integrations, or third-party inventory apps.

Shopify has also added useful building blocks for more structured inventory workflows. For example, inventory transfers now support metafields in Shopify admin and the Admin GraphQL API. That gives teams a place to store transfer context such as lot numbers, serial numbers, RFID identifiers, freight details, customs information, ERP references, or internal approval notes.

This is a meaningful replacement for some of the context merchants previously kept in Stocky custom fields or informal notes.

Decide Where Native Shopify Is Enough

Some merchants can move most Stocky workflows into native Shopify tools.

Native Shopify may be enough if your team needs to:

• move inventory between a small number of locations
• create and receive purchase orders
• adjust inventory manually or in bulk
• perform smaller POS-based counts
• review inventory changes and adjustment history
• use low-stock alerts
• keep inventory synced between online and physical retail
• run basic purchase and transfer workflows without heavy procurement rules

Shopify POS also supports inventory counting workflows such as Quick Count, which can help store teams scan or search variants, confirm quantities, and sync adjustments back to Shopify admin.

For retailers with straightforward operations, the Stocky shutdown can be a good moment to simplify. Fewer systems can mean less duplicate data, fewer manual reconciliations, and clearer ownership.

Know When You Still Need an Inventory App or Integration

Native Shopify inventory features are improving, but they will not replace every advanced Stocky workflow for every merchant.

You may still need a third-party inventory app, ERP, WMS, or custom integration if your team depends on:

• advanced demand forecasting
• automatic purchase order generation with complex rules
• supplier-specific cost defaults
• weighted-average costing
• landed cost allocation across freight, duty, or tax
• dedicated stocktake approvals
• multi-participant full-location audits
• supplier performance analytics
• purchase order emails sent directly from the system
• multi-supplier product logic
• case-pack conversion rules
• manufacturing, assembly, or bundle inventory logic
• bin-level movement tracking inside one location
• deep accounting reconciliation

The important point is to make this decision by workflow, not by app category. A growing retailer may use Shopify for the operational inventory record, an ERP for financial purchase orders, and a warehouse system for advanced receiving. That can work well if each system has a clear role and the data moves reliably.

It becomes risky when staff do not know which system is the source of truth.

Rebuild Supplier and Replenishment Data Carefully

Supplier data deserves special attention because Shopify’s Stocky migration guidance says suppliers cannot be exported from Stocky. That does not mean supplier knowledge should disappear. It means the team may need to document it manually before the deadline.

For each key supplier, capture:

• supplier name
• contact person
• email and phone number
• payment terms
• currency
• lead time
• minimum order quantity
• case-pack rules
• supplier SKU
• preferred shipping method
• notes about seasonal availability
• replacement process for missing or damaged items

Shopify’s migration guide suggests using variant metafields or metaobjects for details such as supplier names, supplier SKUs, case quantities, minimum order quantities, and lead times.

This is worth doing properly. Replenishment automation is only as good as the supplier and product data behind it. If lead times are outdated, case packs are unclear, or supplier SKUs are missing, even a good forecasting tool can produce bad recommendations.

Inventory Accuracy Affects Customer Experience

Inventory migration may sound like a back-office project. Customers feel it very quickly.

Bad inventory data creates visible ecommerce problems:

• products appear available when they are not
• store pickup promises become unreliable
• local availability pages show the wrong location
• staff cannot find items that should be on hand
• support teams handle more “where is my order?” tickets
• substitutions and cancellations increase
• AI shopping tools may misunderstand availability

For merchants with physical locations, dealer networks, or pickup workflows, inventory truth should connect to the customer-facing journey. A store locator or dealer locator is more useful when customers can trust what each location actually offers.

Progus has covered this local-commerce layer in its guide on how to show dealers and stockists on a Shopify store. Tools such as Progus Store Locator can help merchants present location and dealer information clearly, but the underlying operational data still has to be maintained.

The same principle applies to AI shopping readiness. In guide on optimizing Shopify product data for AI shopping, availability is part of the product truth that both people and AI systems need to understand. If inventory records drift after the Stocky migration, product pages, local pickup promises, and automated recommendations become less reliable.

Use Automation After the Workflow Is Stable

Automation should come after workflow clarity, not before.

Once your team knows where purchase orders, transfers, stock counts, and supplier records will live, you can start adding automation. Useful automation ideas include:

• low-stock alerts for key SKUs
• Slack or email alerts when inventory drops below a threshold
• Flow workflows for replenishment review
• transfer metafields that sync ERP or WMS references
• alerts when incoming transfers are delayed
• weekly reports for products with repeated stock discrepancies
• exception queues for high-value inventory adjustments
• reminders to review slow-moving seasonal stock
• staff notifications when pickup inventory falls below a safe level

Shopify’s migration guide mentions Shopify Flow for low-stock alerts and Sidekick for inventory analysis, reordering suggestions, and draft purchase orders or transfers. These tools can reduce manual work, but they still need clean data and human review.

A good rule: automate reminders and draft actions first. Automate final decisions only after the team has tested the data and trusts the process.

Migration QA Checklist

Use this checklist before the cutover is considered complete.

Data retention

• Completed purchase order reports exported
• Stocktake history exported
• Historical cost data exported
• Supplier details manually documented
• Current open purchase orders reviewed
• Custom Stocky fields mapped or archived
• Export folder labeled and accessible

Workflow migration

• New purchase order process tested
• Inventory transfer process tested
• Receiving process tested
• POS count process tested
• Inventory adjustment process tested
• Supplier review process tested
• Reporting process tested

Automation and integrations

• Stocky API dependencies identified
• Third-party apps updated or replaced
• ERP/WMS sync reviewed
• Low-stock alerts configured
• Transfer metafields defined where needed
• Replenishment rules reviewed
• Exception alerts tested

Team readiness

• Store staff trained
• HQ operations trained
• Finance knows where records live
• Support knows how to check stock issues
• Store managers know how to receive inventory
• Permissions reviewed for inventory changes

Customer experience

• Product availability checked
• Store pickup promises tested
• Local inventory or dealer data reviewed
• Support scripts updated
• Cancellation and substitution process reviewed
• Post-migration inventory errors monitored

What to Monitor After the Migration

The first few weeks after the migration matter. Even if the technical cutover works, process gaps often appear once staff use the new workflows during real trading days.

Track:

• stockout rate
• oversell incidents
• order cancellations due to unavailable stock
• receiving accuracy rate
• inventory discrepancy rate
• putaway time
• transfer cycle time
• purchase orders reopened or corrected
• support tickets about product availability
• pickup orders that require substitutions
• staff questions about the new process

If one metric worsens, do not assume the new system is the problem. Often the issue is a missing field, unclear staff ownership, incomplete training, or an old habit that was never formally documented.

Final Thoughts

The Stocky shutdown is a deadline, but it is also a chance to clean up inventory operations before peak-season pressure arrives.

The merchants who handle this well will not simply replace one app with another. They will protect historical data, rebuild supplier and replenishment logic, clarify which system owns each workflow, test real staff journeys, and connect inventory accuracy back to the customer experience.

That is where inventory becomes more than back-office data. It becomes the operational layer behind local availability, pickup promises, faster support, better automation, and more trustworthy ecommerce.