@foveo ,
Based on your requirements Stockie sounds like a good fit especially if your focus is on PO management rather than forecasting. Id also take a look at Sumtracker and Prediko both offer solid purchase order workflows barcode support and inventory management without forcing you into AI heavy features.
Before deciding I’d specifically test how each app handles multiple invoices per PO and landed cost adjustments as those features can vary quite a bit between apps.
Most inventory management systems can replace Stocky. However, if your key requirements are accurate landed-cost tracking with a clear cost breakdown, the ability to manage invoices from multiple vendors against a single purchase order, and barcode support, ChannelBay could be a good option if you havent finalized a tool. These features are included in our free plan, and you can also migrate your existing Stocky data easily.
I build EZStock, so usual grain of salt — but your list is specific enough that I’ll just tell you straight where it fits and where it doesn’t.
PO management, barcode scanning, and landed cost adjustments (shipping, discounts, other charges spread across the line items into the real per-unit cost) are all in there. Multiple invoices per PO too — you can track several invoices against one order, each with its own amount, date, due date, and paid status. Those last two were actually gaps until recently; I shipped them this week, partly because this exact combination keeps coming up from people leaving Stocky.
SKU/variant reporting is there (with CSV export), though I’ll be honest — the report headers aren’t customizable the way you described, so if that’s a hard requirement, worth checking before you commit.
The one thing it doesn’t do is print barcode labels — you marked that a bonus, so probably fine, but for that piece you’d pair it with a dedicated label app.
You said forecasting/min-max isn’t a priority for you, which is good — EZStock has it but it’s on the higher plans, so you’re not paying for something you won’t use on the lower tiers.
If the invoice + landed-cost side is the main thing, it’s genuinely built for that now. Happy to answer anything specific.
Coming back to this because I gave you two wrong answers earlier and both are worth correcting — one was already handled, the other I just built.
First: I said barcode label printing needs a separate app. It doesn’t. EZStock prints label sheets straight from a PO (Avery 5160, Code128) — I originally built that to kill a merchant’s separate label-app subscription, so it’s a solved problem, not a gap.
Second, the report headers. You wanted a SKU/variant report where you choose which columns show up. When you asked, that was a real limitation — the export was a fixed column set. So I went and added it: the stock report now has a column picker, and whatever you turn on drives both the on-screen table and the CSV export, in a stable order. Pick SKU + variant + cost and that’s exactly what the file contains.
For the record on the rest: multiple invoices per PO is there (each with its own number, date, due date, paid status), and landed cost too — shipping, discounts, and other charges spread across the lines so per-unit cost reflects reality, not just the sticker price.
If you still have your Stocky export handy, I’m happy to run it through before Aug 31 so you can see the columns and landed-cost fields land the way you need, rather than taking my word for it.
You guys gave FyreTrail a shot a while ago… but long before we had our stuff together. All of those things you’re looking for are now supported.
Barcode Scanning:
Has since been added to POs for receiving
Has been added to Adjustments to quickly create adjustments for scanned items
Transfers are now fully scannable as well
Invoice Data
Multiple Invoices can be added to a PO with paid/unpaid tracking
Individual Payment tracking coming soon
Landed Costs Adjustments
Landed cost is kept track at both the product and variant level now
Landed cost is kept track for all POs of a given product/variant
Landed cost is also kept track by product/variant of each supplier as well
Sure we have all the other items you said you didn’t want, but we also have the Label Printing bonus you mentioned… label printing comes with either a custom label for your store or one that you customize using our label customization tool.
I did reach out to you after you installed, but I wasn’t able to get a hold of you. If you do decide to come back I’ll reset your trial and you can pick up where you left off. If you don’t like FyreTrail even still then let me know why and I’ll work with you to make it so you do. I hope to see you soon.
PS: We also have a Stocky Migration Tool now that will help you connect to Stocky and get your POs, Suppliers and Adjustments.
I build Binly, so weigh this accordingly. Your list is specific enough that it is easy to say where it does not fit, so I will start there.
Landed costs are the one that rules most of us out. Freight, duty and discounts apportioned back across the lines so your unit cost is the real one is a feature, not a field, and several of the apps being named in these threads do not have it. Binly does not.
Barcode scanning works. You scan into a stocktake or into receiving, with a USB reader or with a phone as a companion scanner, so you can test it without buying hardware first.
Multiple invoices per PO is the other gap. A PO carries one due date and one invoice reference today, which is fine for a single invoice and useless for a deposit plus a balance. Both of these are what I am building right now, landed costs first, because you are the second person in a week asking for the same two things.
The SKU and variant report does export to CSV with the columns you pick: sales, days of cover, cost, value, vendor, location.
So, honestly: if landed costs have to work on 31 August, do not wait for me, go with something that already has them. If you can live without that piece for a few weeks, Binly installs free and the free plan is not a trial, so you can load your catalog and judge the rest before you pay anything.
One thing worth doing before you finalize any of these — and it’s separate from which app you pick.
The standard Stocky CSV export is what most migration flows (and this thread’s suggestions) are built around. It’s a solid baseline, but two fields that matter for post-migration analysis don’t make it into that file:
purchase_item.supplier_cost_price — the actual cost you paid on each PO line at the time of delivery. The CSV only gives you the current cost per product, not the historical trail. If your supplier has adjusted pricing across multiple orders, that history only exists in the API.
purchase_item.received_at — the real date goods arrived, per line item. The CSV gives you PO creation date. Without the received date, any lead time you had calibrated per supplier is unrecoverable after migration.
Supplier notes and par levels are a different problem — those don’t appear in the API either, manual copy is the only path, and Shopify’s own migration docs confirm it: “Suppliers can’t be exported from Stocky.”
So the practical sequence: pull the API data for cost history and received dates now while the API is live, capture notes and par levels manually while Stocky’s UI is still accessible, then pick your replacement app second — that decision is reversible, the data window isn’t.
I built InvoRescue (Chrome extension, one-time fee, runs in-browser) to handle exactly this pre-migration step: API extraction for the fields that CSV misses, plus a structured walkthrough for the manual capture. Link’s on my profile if useful.
One thing I’ve noticed in many of these Stocky discussions is that merchants are evaluating replacement apps feature-by-feature, which makes sense initially.
But after talking with operators, the challenges often show up after the migration is complete and the first purchase order arrives.
The questions become:
• How are receipts handled when shipments arrive short?
• Where does inventory go after receiving?
• How do put-away and bin locations get tracked?
• How does inventory move into pick/pack/ship workflows?
• How does purchasing connect back to inventory valuation and finance?
Landed costs, barcode scanning, and historical data preservation are all important parts of the puzzle. The bigger opportunity may be using the Stocky transition as a chance to rethink the operational workflow end-to-end rather than replacing one screen with another.
What others here consider the biggest operational gap they’ll need to solve after August 31.
@foveo Personally speaking, I switched from Stocky last year when it deprecated some of the features. I asked the same stocky replacement question here in the community forum only and someone recommended me Sumtracker and what a great app it is. It has all the features that Stocky has and several other features as well. You can give it a try.
Correcting my own post above, because it’s now wrong. Landed costs and multiple invoices per PO went live in Binly yesterday. Freight, duty and discounts spread across the lines, the landed figure written back to Shopify’s unit cost when you receive, and separate invoices against one PO each with their own due date and paid status.
I said I was building it. Seems only fair to say when it’s done rather than leave a stale “we don’t have that” sitting in the thread.
The point about supplier_cost_price and received_at not being in the CSV is the bigger one here though, whichever app you end up on. That’s the kind of thing you only notice in October, when you go to check a lead time and the history isn’t there.
Hey @foveo
Disclaimer: I’m the creator of Alfred Purchase Orders
I’m naturally biased but I’d suggest taking Alfred for the 30 day trial.
Addressing your asks point by point:
“The things that are important to me are po management:”
Barcode scanning: assuming you’re asking for barcode scanning to receive items, Alfred supports rapid barcode scanning (individual barcodes or configuring carton IDs+quantities) in PO receiving sessions, inventory transfers, stocktakes)
Invoice data (ideally fields for multiple invoices per po): Alfred currently supports breaking a PO (and its line items) into individual shipments where you can add Invoice #s, etc. and we’ll be launching improvements soon to actually track PO<>Invoice<>Shipments with invoice payment statuses
Landed costs adjustments (fields for discounts, shipping, etc): See my description for how Alfred POs handle landed costs. There’s also a dedicating “Pricing & Margins” module that let’s you calculate and bulk publish COGS or updated Shopify list prices for all the items in a PO.
I also use the sku/variant report: Would be helpful to understand what insights you glean from this report, but Alfred offers a variety of reports (inventory, sales, ABC-XYZ, etc.)
I don’t need forecasting, min/max, and all these other AI driven tools. Label printing is a bonus but not required: You don’t need them, but Alfred offers them! Label printing is not supported natively, but it does offer label file exports per PO, per shipment, or per “receiving session” items.
A QBO integration is nice but not needed: Alfred does not currently offer any live QBO or Xero integrations
@foveo the list you wrote �� barcode scanning, fields for multiple invoices per PO, landed cost adjustments with discount/shipping fields �� is the same shape I am building toward. The multiple-invoices-per-PO bit is the one most tools skip, and it is exactly where the real cost lands (deposit, balance, freight invoice, adjustment weeks later).
What I am working on: per-charge landed cost allocation with its own basis, multiple invoices / credit notes against one PO, and a late-invoice true-up that becomes a new revision with a visible trail instead of re-entering the PO. Since you clearly know what you need here �� would you be open to a 20-minute workflow review? I am pre-launch and validating against how people actually run this. No sales pitch.
Reading through the requirements here, it sounds like replacing Stocky isn’t really about finding another inventory dashboard — it’s about keeping the whole purchasing and receiving workflow efficient.
For those actively looking for a replacement, if you had to choose only one capability you absolutely couldn’t lose, what would it be?