Shopify's Spring '26 Edition landed on June 17, 2026 with more than 150 updates, and buried among the agentic commerce headlines is the most significant overhaul of Shopify's native inventory management in years. The timing is not a coincidence. Stocky, the free inventory app Shopify acquired in 2018 and bundled with POS Pro, shuts down permanently on August 31, 2026. The Spring '26 inventory features are Shopify's answer to the question every Stocky merchant has been asking since the deprecation announcement: what am I supposed to use instead?
The short answer: native Shopify now covers more of Stocky's ground than ever before but not all of it. If you sell perishable goods, track batches or lots, manage expiry dates, or sell multi-SKU bundles, there are real gaps you need to plan around before the deadline.
This guide breaks down exactly what changed, what native Shopify covers post-Stocky, what it doesn't, and a practical migration timeline you can start this week.
What changed in Shopify's Spring 2026 inventory overhaul?
Six updates matter most for merchants managing physical inventory.
1. SKU sharing across locations is now the default
You can now stock the same variant at multiple locations, including third-party fulfillment centers without duplicating inventory items. Under the hood, Shopify removed the permitsSkuSharing restriction entirely, so inventory can be stocked at multiple locations for any fulfillment service. For multi-location brands and anyone splitting stock between a 3PL and their own warehouse, this eliminates one of the platform's longest-standing structural annoyances: phantom duplicate SKUs that fragmented reporting and broke reorder logic.
2. Barcode receiving for inbound shipments
Instead of receiving inventory transfers item by item, staff can now scan shipment-level barcodes (including GS1-128) to receive transfers directly in the Shopify admin. If your team currently receives stock with a clipboard and a prayer, this is a meaningful workflow upgrade and it replaces one of the receiving workflows Stocky users depended on.
3. Sidekick generates purchase orders
Shopify's AI assistant, Sidekick, can now help with purchasing decisions and generate purchase orders based on your stock data, with the ability to automatically create the associated transfers. This is Shopify's first real move toward replacing Stocky's replenishment intelligence, though, as we'll cover below, it's not yet a substitute for true demand forecasting with min/max reorder points.
4. Audit trails on every inventory adjustment
Every inventory adjustment now carries a full audit trail: who changed what, when, and why, with reason codes. For merchants who've ever spent an afternoon trying to reconstruct why on-hand quantities drifted from reality, this is quietly one of the most valuable updates in the entire Edition. It also matters for compliance-sensitive categories, food, supplements, cosmetics where traceability isn't optional.
5. Faster inventory syncing
Back-in-stock updates now reach your storefront faster during high-traffic events. Oversells during a drop or a BFCM surge happen in the gap between a sale and an inventory update; Shopify shrinking that gap reduces oversell risk for everyone though, as bundle sellers know, sync speed at the single-SKU level is only half the story (more on that below).
6. The new batch fulfillment workflow
Spring '26 introduces a native batch fulfillment workflow: pick, pack, scan, and ship. Merchants can group orders into batches, generate consolidated pick lists, and scan-verify items during packing to reduce mis-ships. If you're fulfilling in-house and currently processing orders one at a time, batching alone can cut fulfillment time dramatically.
One important clarification, because the terminology trips people up: Shopify's "batch fulfillment" means processing orders in batches. It is not batch or lot tracking the ability to trace which production batch or lot a unit belongs to, with expiry dates and recall traceability. That distinction is at the heart of the migration decision for a lot of Stocky users, and we'll come back to it.
The Stocky shutdown: key dates and what you'll lose
Here's the timeline every Stocky merchant needs on their calendar:
- July 7, 2025: Inventory transfers and min/max forecasting removed from Stocky (already done)
- February 2, 2026: Stocky delisted from the App Store; no new installs or reinstalls (already done)
- August 31, 2026: Stocky stops working entirely. All Stocky APIs shut off.
- ~90 days after shutdown: Read-only access window to export remaining data closes
Three things catch merchants off guard:
- Historical data does not migrate. Old purchase orders, stocktakes, and forecasts will not automatically move into Shopify. If you want them, you must export them manually via Stocky's reports before the deadline.
- Supplier records cannot be exported at all. Vendor contacts, costs, and lead times configured in Stocky must be manually documented and recreated in whatever system you move to.
- Integrations break instantly. Any spreadsheet, custom tool, or third-party app connected to Stocky's API stops working on August 31: not gradually, immediately.
Your actual inventory levels are safe: those live in Shopify, not Stocky. What's at risk is the operational layer built around them.
What native Shopify now covers and where the gaps are
Covered natively after Spring '26
- Multi-location stock tracking with SKU sharing
- Inventory transfers between locations
- Purchase order creation and receiving (with Sidekick assistance)
- Barcode-based receiving of shipments
- Inventory adjustments with full audit trails
- Batch fulfillment (pick, pack, scan, ship)
- Basic stock counts via Quick Count on POS
For a single-location merchant with straightforward SKUs and modest purchasing needs, native Shopify is now a genuinely viable Stocky replacement. That's the honest assessment, and plenty of merchants should take that path.
Still missing from native Shopify
- Batch and lot tracking. There is no native way to record which lot a unit came from, sell through lots in FEFO (first-expired, first-out) order, or trace a specific batch through a recall.
- Expiry date tracking. Shopify has no concept of a best-before date. For food, beverage, supplements, cosmetics, and pharma-adjacent brands, this is disqualifying on its own.
- Demand forecasting with min/max reorder points. Sidekick suggests purchase orders, but it doesn't replicate Stocky's replenishment logic with configurable minimum and maximum stock levels per location.
- Bill of materials / raw material tracking. If you manufacture or co-pack, native tools can't convert components into finished goods.
- Supplier management depth. Native purchase orders exist, but vendor-level cost history, lead times, and pack sizes are thinner than what Stocky offered.
- Bundle-aware inventory sync. More on this next, because it's the gap that bites hardest at scale.
The bundle problem: where inventory sync breaks
Multi-SKU bundles are one of the most common places Shopify inventory accuracy falls apart and neither Stocky nor the Spring '26 updates solve it.
Here's why. When a customer buys a gift set containing a candle, a mug, and a bag of coffee, Shopify sees one line item. Unless something deducts the candle, the mug, and the coffee from component inventory in real time, your on-hand counts are wrong the moment the order lands. Multiply that across a promotion and you're overselling components you don't have or blocking bundle sales while component stock sits on the shelf.
Faster sync at the single-SKU level (welcome as it is) doesn't fix this, because the problem isn't sync speed it's sync logic. Bundles need component-level awareness.
This is exactly what Simple Bundles is built for: when a bundle sells, every component SKU is deducted in real time, and bundle availability is automatically calculated from component stock so a bundle shows as sold out the moment any component runs dry, and never before. If you're rebuilding your inventory stack post-Stocky and you sell kits, gift sets, multipacks, or build-your-own bundles, component-level deduction should be on your requirements list from day one, not bolted on after your first oversell.
Perishable and batch-tracked brands: your migration path
If you sell anything with a shelf life food and beverage, supplements, cosmetics, candles with natural ingredients, pet treats or anything regulators might one day ask you to trace, native Shopify's gaps aren't inconveniences. They're compliance and waste-management risks.
What to look for in a Stocky replacement if you're in this category:
- Lot/batch-level inventory, so every received shipment carries a batch ID
- Expiry date tracking with FEFO logic, so oldest-expiring stock sells first
- Recall traceability, so you can identify affected orders by batch in minutes, not days
- Expiry-driven discounting workflows, so short-dated stock moves before it becomes shrink
This is the exact problem Freshly Batch Inventory was built to solve for Shopify merchants: batch and lot tracking, expiry date management, and traceability that native Shopify even after the Spring '26 overhaul simply doesn't offer. If Stocky was the operational backbone of your perishable inventory workflow, Freshly Batch Inventory is the purpose-built replacement for the parts Shopify didn't absorb.
Your Stocky migration checklist and timeline
With roughly 60 days left, here's a realistic plan.
Week 1: Export and audit
- Export all historical purchase orders and stocktakes from Stocky's reports
- Manually document supplier records (contacts, costs, lead times) these cannot be exported
- List every spreadsheet, tool, or integration touching Stocky's API
- Write down your actual workflows: how you reorder, receive, count, and transfer stock
Weeks 2–3: Decide your path
- Simple operations (single location, no batches, no bundles, light purchasing)? Plan to move to native Shopify admin + POS
- Perishable or batch-tracked products? Trial Freshly Batch Inventory for lot/expiry tracking
- Selling multi-SKU bundles or kits? Confirm component-level inventory deduction with Simple Bundles
- Heavy forecasting needs? Evaluate a dedicated planning layer alongside native tools
Weeks 4–6: Parallel run
- Set up your new system(s) while Stocky is still live
- Recreate suppliers and reorder rules
- Run one full purchasing cycle (PO → receive via barcode → adjust) in the new setup
- Verify audit trails and stock counts match reality with a test count
Weeks 7–8: Cut over and train
- Train staff on the new receiving, counting, and fulfillment workflows
- Switch integrations off Stocky's API
- Retire Stocky before the deadline, don't let August 31 be your forced cutover date
FAQ
When exactly does Stocky shut down?
August 31, 2026. After that, the app and its APIs stop working. Shopify provides read-only data access for at least 90 days afterward, but you should export everything well before the deadline.
Does Shopify's new batch fulfillment replace batch tracking?
No. Batch fulfillment groups orders for efficient pick-pack-scan-ship processing. Batch/lot tracking, tracing units to production batches with expiry dates is not natively supported. Apps like Freshly Batch Inventory fill that gap.
Will my inventory levels disappear when Stocky shuts down?
No. Stock levels live in Shopify. What disappears is Stocky-specific data: historical POs, stocktakes, forecasts, and supplier records.
Is native Shopify enough after the Spring '26 updates?
For simple, single-location operations — often yes. For perishable, batch-tracked, manufactured, or bundle-heavy catalogs, you'll need purpose-built apps to cover the gaps.
How do bundles affect inventory accuracy?
Multi-SKU bundles break naive inventory sync because one sale must deduct multiple component SKUs. Simple Bundles handles real-time component-level deduction so bundle availability always reflects true component stock.
Selling bundles, kits, or products with shelf lives? Install Simple Bundles for real-time component-level inventory sync, and Freshly Batch Inventory for batch, lot, and expiry tracking before the Stocky deadline forces the decision for you.