Native POs need to match Stocky before August 2026 sunset — here are the gaps

With the Stocky sunset there is no PO API replacement.
There was nothing fundamentally wrong with Stocky. Why not have the same purchase order functions?
There are three concrete gaps with the Native POs
No retail price on the receiver document
No integrated label printing from the PO for non-barcoded items
No separate receiver document distinct from the vendor PO

Same gripes here from the partner side. Receiver doc is the worst gap because non-barcoded receiving is common in apparel/food/consignment and the Stocky workflow (PO line → confirm received → Dymo print) doesn’t have a native equivalent right now.

Workarounds I’ve seen people piece together while waiting:

  • Receiver doc: clone the PO email template into Order Printer or a custom Liquid PDF template. Solves format, doesn’t fix the workflow gap
  • Label printing: most stores fall back to running Dymo Connect off a CSV export from the PO, manual but consistent
  • Retail price on receiver: same story, Liquid block in the receiver template pulling variant price

The bigger question is whether Shopify treats POs as a real workflow surface or just a cost-tracking object. Right now it reads like the latter. Have you raised these specifically with anyone on the Inventory team or in Partner Slack? Concrete gaps with examples tend to land better than “bring Stocky parity”.

There are solutions, but no not “Native”. You can currently get not only this functionality you are seeking, but also extra features that Shopify will likely never introduce. One such solution is FyreTrail in the app store. It’s not only a Stocky replacement, but a full featured application that gives you many features that take you multiple apps to replicate. FyreTrail includes:

  • PO Label Printing - Zebra, Dymo, etc.
  • Full partial delivery support including PO resolution that allows you to adjust pricing should you not get the entire original PO.
  • Stock Takes
  • Stock Adjustments
  • Shopify product syncing
  • Inventory management - low stock, target stock and “fill the shelves” one-button ordering
  • Plus many more features

I encourage you to take a look.

This breakdown is really helpful because it shows the issue isn’t just missing features it’s how those features fit into the receiving workflow.

Things like retail price on the receiver doc or label printing seem small individually, but they’re part of a sequence people rely on operationally (receive → label → place → update inventory).

Once that sequence gets broken, even if each piece can be recreated with templates or exports, the process itself becomes slower and more error-prone.

The bigger question lumine raised is interesting whether POs are being treated as a cost object vs. a workflow surface.

Curious for those using the workarounds today does it feel like a temporary patch, or something you could realistically run day-to-day at scale?

Adding the planning-side gaps to this list, since the document and printing ones are well covered above:

No reorder suggestions or forecasting. Stocky suggested what to reorder based on sales history. Native POs are blank forms — you have to already know what and how much to order before you open one.

Nowhere to store supplier lead times or MOQs. Native POs don’t hold them, so the timing math (order X days before you run out, in quantities the supplier will accept) now lives in your head or a spreadsheet.

No low-stock → PO connection. You can get low-stock alerts, but nothing turns an alert into a draft PO at the right quantity.

Two practical things while everyone figures out replacements:

  1. Export the un-exportable now. Stocky’s export doesn’t include supplier names, lead times, or MOQs — those only come out by manual copy, while the app still opens. Whatever you migrate to, grab that data first.
  2. A simple reorder sheet covers the planning gap surprisingly well in the meantime: reorder point = (average daily sales × supplier lead time in days) + safety stock. When stock hits that number, raise the PO, rounded up to the supplier’s MOQ. It’s not real forecasting, but it prevents most stockouts while you evaluate tools.

I put together a one-page spreadsheet version of this while researching the migration — happy to share the layout if it’s useful to anyone here.

Also agree with kthoppae’s framing above — each gap on its own is an annoyance, but the broken loop (forecast → PO → receive) is the real operational cost.

@Philip_Gangi We’ve also heard the same issues from our users - over and over again.

With Stocky going away, and our own users asking us for a robust way to handle POs and light inventory management / reordering with Shopify; we decided to build our own solution, but for free. It includes all the features Stocky had - and more, including retail price and flexible label printing.

Check it out at Stockroom - Stockroom ‑ Purchase Orders - Unlimited purchase orders, receiving & sync with QuickBooks | Shopify App Store - we’re making it completely free for everyone!

We think Shopify merchants deserve a robust, stable and long term way to handle Purchase Orders (and the re-ordering/receiving processes that come with them) in a way that fits their business, and not at an additional cost. We’d love to hear any feedback as we continue to build more features to make this a helpful home for Shopify store merchants coming from Stocky!

@Philip_Gangi I’m not with Shopify and I’m not selling anything, just
trying to understand how retailers are coping since 31 August.

You listed three gaps: no retail price on the receiver document, no
label printing from the PO, and no separate receiver document distinct
from the vendor PO. Which of those three costs you the most time on a
normal delivery?

Thanks.

A receiver is a different document from the purchase order, not a reprint of it.

A purchase order is a promise. It runs in the order you typed, it lists what you asked for, and it faces outward, at a supplier. A receiving document records an event instead, so it should follow the order goods physically arrive or the order somebody walks the shelves, it should put ordered quantity beside a blank box for the count, and it should carry the retail price, so whoever holds the box can price and label without opening a second screen.

Then there is the arithmetic. A receiver covers one delivery, so its lines are what came today. Print the purchase order against a partial delivery and you have labels for stock still on a truck.

Disclosure: I build Binly (Binly ‑ Stocktake & Reorder - Stocky replacement: phone stocktakes, POs & smart reorder | Shopify App Store). It prints labels from a received order for the quantity that actually arrived, which is the part of your list I can speak to.