Since Stocky is going away will there be a way to get a csv download of received items in the new PO creation link under Products. Stocky is currently the only quick way to create barcode labels for incoming stock for POS locations.
Hey @PBN1 ,
Indeed, there is a major operational gap right now when it comes to barcode printing workflow.
To figure out the cleanest way to extract and route that data for you, I’d look into two things:
-
Your Printing Setup: Once you have the CSV of received items, what software or hardware are you using to actually generate the labels (e.g., Dymo, Zebra, Shopify’s Retail Barcode app)?
-
Partial Deliveries: If a PO is only partially delivered, do you need the CSV to strictly isolate the newly received units, or the entire original PO?
Curious to hear how you are handling the transition!
Thanks,
Julien
Disclosure up front: I build LabelCraft. The CSV export-then-reimport dance is exactly the gap Stocky left. LabelCraft reads a received Transfer or Shipment directly and prints exact-size labels for every line item, so there’s no CSV step at all. It also prints from a pasted or uploaded SKU list if you’d rather skip Transfers, and generates a valid GS1/EAN-13 for anything missing a barcode so it scans at the till. Free up to 200 labels a month if you want to try it on your next received batch. Whatever you land on, export your Stocky data before Aug 31, it doesn’t migrate automatically.
If it helps, we do support label printing in the PO app we recently built - completely free, to help merchants as Stocky goes away.
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 in a way that fits their business.
I don’t think a CSV output will happen under the native POs. You can though either utilize Stocky’s API, download those POs into a CSV now using Stocky’s download feature (pain the the …) or just move to an app that has a migration from Stocky using their API.
Using an app that does have a Stocky API integration (like FyreTrail’s Stocky Migration Tool), you can download your delivered POs, your incoming POs, Suppliers and Adjustments into FyreTrail and then print labels directly from the PO for items that you receive. There’s a ton of flexibility to get your data out of Stocky and into FyreTrail in plenty of time and you can simply pick up where you left off (many stores who use FyreTrail have done just that). If you choose to do that you will get a solid replacement in FyreTrail that has more intelligence built in to the day to day operations that you previously did in Stocky.
If you just want to print labels then the 2 other apps (LabelCraft and FlochForster) are likely great solutions for you as well.
Quick follow-up since this thread picked back up (still the LabelCraft founder).
@FlochForster puts a finger on the real pain: partial deliveries. Exporting the whole PO gives you labels for the ordered quantities, not for what actually arrived. That is exactly why we read the received lines of a native Transfer or Shipment instead of the PO: one label per unit actually received in this delivery, nothing else.
@PBN1 if you already have a Stocky CSV and want to sanity-check what will print before touching anything: we put a free, no-install checker at labelcraft.tech/stocky-label-preview. Paste the CSV, it previews the labels and flags missing or non-scannable barcodes. No account needed.
On the Stocky API route @DougInOr mentions: agreed, that is the clean path for PO history. For the label half specifically you do not need history, just the received lines going forward.
Hi @PBN1 - I am researching the receiving-to-label workflow after Stocky, not promoting an app. I tested Shopify Transfers and found that basic received-quantity label printing is already covered, so I am trying to understand the remaining CSV gap.
For your most recent delivery, did the CSV need to come from Shopify’s native PO, or would a supplier packing-list CSV have worked? Which exception took the most time: a partial receipt, a SKU mismatch, or a missing barcode?
If you are comfortable sharing only an anonymized header row or 5-20 rows with fake values, I can turn it into a no-cost reconciliation mockup and send the result back for feedback.