Shopify Stocky Shutdown: Migration Checklist Before August 31, 2026

Shopify Stocky is shutting down

Shopify Stocky will no longer be available for inventory management after August 31, 2026.

If your retail operation still depends on Stocky, the most important job now is not choosing a replacement app. It is understanding exactly what you use Stocky for, preserving the information that will not move cleanly, and testing the Shopify workflows that will take over.

Shopify has already moved core inventory workflows into Shopify Admin and Shopify POS, including purchase orders, receiving, transfers, inventory adjustments and inventory history. But some Stocky-specific information and workflows require extra attention.

This guide separates those pieces so you can make a smaller, safer migration plan.

1. What exactly is happening to Stocky?

Shopify says Stocky will stop being available for inventory management after August 31, 2026.

Stocky was also delisted from the Shopify App Store on February 2, 2026, which means it cannot be reinstalled.

After August 31, Shopify says merchants will have read-only access for at least 90 days to export Stocky data. That does not mean you should postpone the migration. The operating workflows need to move before the shutdown date.

Most importantly, not everything stored or managed through Stocky becomes a like-for-like record inside Shopify.

Read Shopify's official Stocky migration guide.

2. What should you export from Stocky?

Shopify specifically recommends preserving:

• completed purchase-order reports
• stocktake history
• historical cost data

Historical Stocky purchase orders do not migrate into Shopify with their original status, received quantities and supplier links. Historical stocktakes also do not automatically become Shopify records.

If those records matter for accounting, audits, supplier disputes, purchasing analysis or simply understanding how the business operated, export them.

Preserve the purchasing facts you will need later

Shopify's recommended exports are the starting point. When you keep historical purchasing data, the useful facts to preserve usually include:

• supplier
• product or SKU
• unit cost
• quantity received
• received date

Treat those as the facts your team is likely to need for disputes, costing context and later analysis — not as a guaranteed list of Stocky export column names. Export what Shopify makes available, then fill gaps from the records your buyers and receivers already use.

Treat the export as an archive, not the migration itself

A CSV sitting in Downloads is not a migration plan.

For each exported dataset, decide:

Use whatever secure document-storage process your business already trusts. The key is that somebody owns the archive and knows where it is.

3. The supplier-data problem deserves its own workstream

One of the easiest migration risks to underestimate is supplier information.

Shopify's Stocky migration documentation explicitly says suppliers cannot be exported from Stocky.

That means the supplier relationship you built operationally may need more than a CSV export.

Before cutover, review the supplier information your team actually relies on, such as:

• supplier name and contact details
• supplier SKU and current supplier cost
• alternative suppliers and currency
• minimum order quantity and case or pack quantity
• lead time, payment terms and ordering notes
• location-specific instructions

Do not assume every one of these fields has a direct one-to-one destination in Shopify.

Shopify's native supplier and inventory workflows are evolving, and some richer supplier-specific attributes may need to be represented with Shopify metafields, metaobjects or a specialist app depending on your operation.

A useful migration rule: If a member of your buying or receiving team would say, “I know that because Stocky tells me,” capture it before Stocky becomes read-only.

That is operational knowledge, not just software configuration.

4. What happens to open purchase orders?

Shopify recommends finishing open Stocky purchase orders before shutdown.

Its migration guidance suggests stopping creation of new Stocky purchase orders roughly 14 days before August 31and receiving and closing open in-transit POs where possible.

If a Stocky PO is still open at cutover, Shopify recommends recreating only the remaining quantities as a Shopify purchase order or transfer.

For every open PO, record:

• Stocky PO number, supplier and destination
• order date and expected arrival
• quantity ordered and quantity already received
• quantity still outstanding
• whether the supplier invoice has been received
• final action: close in Stocky or recreate the remaining quantity in Shopify

This is worth doing even for a small store. Partial receipts are exactly where a rushed migration can create duplicate incoming inventory or confusing supplier conversations.

Creating a purchase order is only part of the cutover

A test PO that looks correct on screen is not enough. Receiving is where inventory, cost and supplier conversations usually go wrong.

Before you rely on the new workflow, test cases such as:

• the delivered quantity differs from the ordered quantity
• a partial receipt, with the remainder still outstanding
• the supplier price on the invoice differs from the price on the PO
• inventory is received into the intended location
• you can see what cost ultimately gets recorded
• barcode, label or other downstream warehouse steps still work after receiving

Run those tests in the tools you will actually use after Stocky, with a real or representative supplier document. Do not assume a successful PO create means receiving, costing and labels will follow.

5. What Shopify now handles natively

The Stocky shutdown does not mean every merchant needs another large inventory app.

Shopify's built-in inventory workflows now cover a significant amount of what merchants previously handled through Stocky, including:

• purchase orders and supplier receiving
• inventory transfers between locations and partial receiving
• inventory adjustments and inventory history
• multi-location inventory visibility
• inventory workflows in Shopify POS
• role-based permissions and audit trails
• low-stock alert workflows using Shopify Flow
• inventory and reordering analysis through Sidekick

That distinction can reduce migration complexity and recurring app costs.

Many merchants are not looking for a large ERP. If Shopify already covers purchase orders, receiving and transfers for your operation, the remaining gap may be a narrower process — not another platform that tries to own every inventory job.

6. Before choosing a Stocky replacement, write down the workflow you actually used

Many teams start the Stocky shutdown by comparing replacement apps. A more useful first step is writing down the jobs your buying, receiving and store teams actually depended on.

You often do not need to replace every historical Stocky feature. You need the operating steps that would break if they disappeared next week.

For most stores, that list is shorter than the full Stocky feature set. Common jobs include:

• reorder suggestions or low-stock planning
• creating supplier purchase orders
• receiving full or partial deliveries
• supplier-specific pricing or currency
• case-pack ordering
• barcode or label work after receiving
• stocktakes
• transfers and multi-location operations

Some merchants simply want to keep a practical loop working:

Treat this as an evaluation worksheet, not a shopping list. If a job was unused, do not pay to recreate it. If a job is still essential, test it in Shopify first and only then look for a specialist tool.

7. Do you actually need a Stocky alternative?

If you are searching for a Shopify Stocky alternative, Stocky replacement or Shopify POS Pro Stocky alternative, start with the workflow list above rather than an app comparison page.

We used Stocky mainly for...

• purchase orders
• receiving
• transfers
• stocktakes
• forecasting and reordering
• supplier information
• supplier-specific costs
• barcode workflows
• reporting and history
• integrations and API workflows
• several of the above

Then label each requirement:

This prevents a common migration mistake: replacing an old all-in-one application with another large application before checking how much of the workload has already moved into Shopify.

8. Don't replace one lock-in with another

Stocky is a reminder that operational history can sit inside a tool that later goes away. When you evaluate a replacement, ask whether you can take your records with you later.

Check whether you can export:

• purchase orders
• supplier data
• received quantities and received dates
• product or supplier cost history
• other operational records you may need for audit, disputes or later analysis

This is not an argument against specialist apps. It is a migration habit: if a workflow matters enough to move into a new tool, the records it creates should be exportable by your team, not trapped in another closed system.

9. Stocky migration replacement matrix

10. Supplier costs and invoice reconciliation are a separate problem

Moving purchase orders and receiving into Shopify does not eliminate the supplier invoice.

The document your supplier sends is still the commercial record of what they charged you.

In practice, teams may need to reconcile:

• what was ordered and what physically arrived
• what Shopify says was received
• what the supplier invoiced
• the latest supplier unit cost
• discounts, tax, freight or other charges
• currency differences

That is different from forecasting inventory or moving stock between locations.

Where Salor Invoice fits

Salor Invoice focuses on the invoice-to-reviewed-update workflow:

1. Upload a supplier invoice PDF or image.
2. Extract its line items.
3. Match invoice rows to Shopify products.
4. Review product, quantity and cost changes.
5. Apply only the changes you approve.
6. Keep a processing and history trail for later reference.

This is useful whether a merchant previously used Stocky or not.

11. GCC checks worth adding to the migration

The Stocky shutdown is global, but GCC retail operations often add a few practical wrinkles to supplier receiving and costing.

If you operate in the UAE, Saudi Arabia, Kuwait or elsewhere in the Gulf, include these in your migration test:

Supplier currency

Confirm which suppliers invoice in AED, SAR, KWD, USD, EUR or other currencies and where your team records the commercial cost used in Shopify.

VAT and tax fields

Make sure your receiving and reconciliation process distinguishes product cost from VAT or other tax amounts where appropriate for your accounting setup.

Freight, duty and import costs

If imported products carry freight, customs or other landed costs, document how those amounts are handled. Do not assume a supplier's invoice unit price equals your final landed cost.

Arabic and bilingual documents

If suppliers send Arabic or bilingual invoices, include those exact document layouts in testing before automating extraction or matching.

Multiple locations

Test which location receives inventory, who is allowed to receive it, and what happens when a shipment is split across locations.

These are operating checks, not accounting or tax advice. Use your accountant or tax adviser for the correct treatment for your business.

12. Final Stocky migration checklist

13. Stocky shutdown FAQ