Stocky isn’t just “going away.”
It’s exposing how much operational work many retailers were relying on one tool to handle.
Over the last few months we’ve spoken with merchants, followed Shopify community discussions, and watched the same themes come up repeatedly:
• Receiving inventory still involves manual reconciliation.
• Partial shipments create unnecessary work.
• Inventory knows what you have, but not always where it is.
• Purchasing, warehouse operations, and finance become disconnected as the business grows.
None of these are storefront problems.
Shopify is excellent at selling products.
These are operational execution problems.
That’s exactly why we’ve spent the last several months building workflows for:
✓ Receiving
✓ Put-away
✓ Bin management
✓ Label printing
✓ Pick / Pack / Ship
We didn’t start with AI.
We started by asking:
“Where does a warehouse operator lose the most time during the day?”
Every workflow we’ve built has come from trying to remove those small operational bottlenecks that quietly consume hours every week.
The end of Stocky isn’t just the end of an app.
It’s an opportunity to rethink how inventory operations should work in 2026.
HI @kthoppae
You raise a good point that Stocky covered much more than purchase orders and reorder suggestions for many merchants. As businesses grow, inventory management often extends into receiving, put-away, bin locations, and warehouse workflows, which can become difficult to manage with basic inventory tools alone.
It’ll be interesting to see how merchants adapt after the transition. Some may only need lightweight purchasing features, while others may take the opportunity to move to a more complete warehouse management solution.
Hey @kthoppae ,
I like the way you’ve framed this around operational workflows rather than simply positioning it as a Stocky replacement.
One suggestion that could make the message even stronger would be to include some real world examples or measurable outcomes. For instance, if you’ve seen reductions in receiving time, fewer reconciliation errors, or faster pick and pack workflows during testing, sharing those results would help merchants understand the practical value of the workflows you’ve built.
Operational improvements are often easier to appreciate when they’re tied to tangible outcomes rather than feature lists alone.
If you found this reply helpful, please consider marking it as the accepted solution so it can help other merchants following this discussion.
Thank You !
Thanks! That’s exactly what we’ve been seeing as well.
Many merchants initially look for better purchasing or inventory visibility, but as operations grow, the bigger challenge becomes connecting receiving, put-away, picking, shipping, and inventory into one operational workflow instead of separate manual steps.
That’s been a major focus for what we’re building, and it’s been interesting to see how consistent those pain points are across different merchants.
Thanks, Steve—I appreciate the suggestion.
I agree that measurable outcomes are what ultimately matter. We’re still in the product-building phase, so rather than publishing numbers we can’t yet validate, we’ve been sharing the operational problems we’re solving and the workflows behind them.
As we begin working with pilot customers, I’m looking forward to sharing real data around receiving efficiency, inventory accuracy, and warehouse productivity. Those are exactly the outcomes we’re designing for.
Thanks for the clarification. I think that’s the right approach. It’s better to share validated results once they’re backed by real world usage than to publish estimates too early.
In the meantime, explaining the operational problems you’re solving and the reasoning behind your workflow gives merchants a good understanding of the product’s direction.
I’ll be interested to see the results from your pilot customers, particularly around inventory accuracy and receiving efficiency, since those are metrics that can clearly demonstrate the value of the solution.
If you found my reply helpful, please consider marking it as the accepted solution so it can help other merchants following this discussion.
Thank You !
The operational gaps you’ve listed are the right ones to focus on — they’re exactly what shows up after the migration is done and the first real PO lands. The receiving → put-away → bin management loop has quietly been pieced together across too many separate tools.
One layer worth flagging for merchants reading this, since it precedes all of it: before you optimize the post-migration workflow, there’s a narrow window to get your historical data out of Stocky while the API is still live.
The CSV exports miss two things that matter operationally:
purchase_item.supplier_cost_price — the actual per-line cost at time of order, not just today’s snapshot. Without this, your full cost trail disappears on Aug 31.purchase_item.received_at — the real arrival date per shipment (not PO creation date). This is what makes supplier lead-time analysis usable post-migration.
Supplier notes and par levels are in neither the CSV nor the API — manual capture is the only route, and the clock is running.
I built a Chrome extension (InvoRescue) to pull the API data and walk through the manual capture systematically before the shutdown. One-time purchase, runs in the browser. Link’s on my profile if useful — happy to clarify what it covers here.
Thanks for sharing this. That’s a good point, especially for merchants who have years of purchasing history in Stocky.
Preserving historical operational data before the shutdown is an important step, regardless of what platform merchants move to next. Once that transition is complete, the focus shifts from data migration to improving the day-to-day workflows—receiving, put-away, inventory visibility, and fulfillment which is the area we’ve been concentrating on.
I appreciate you highlighting the migration side of the equation since it’s something many merchants may not be thinking about yet.
Hi there @kthoppae
Sunset at Stocky certainly showed how many merchants relied on workflows outside of the basics of inventory tracking. Receiving, putaway, bin locations, and partial shipments become more difficult to handle with higher order volumes.
I think the biggest opportunity is to keep those workflows very closely tied to Shopify inventory and orders without causing manual reconciliation. A more efficient receiving and packing process can certainly help, particularly for companies with multiple stores or large product lines. So it’s about addressing the operational gaps but still making it easy enough for the warehouse teams.