This feels like more than a display preference because receiving is one of the few moments where you have the supplier document and the physical goods in front of you at the same time.
I’d actually separate it into three checks:
Did the quantity delivered match what was ordered?
Did the supplier charge the cost you expected?
Does that new cost still produce the margin you expect at the current retail price?
If those checks happen later, you’re effectively auditing the delivery twice.
Even if Shopify doesn’t put every calculation directly into the receiving screen, having a clean way to reconcile quantity + supplier cost + selling price during the same workflow would remove a lot of manual checking.
@ondrejulehla margin at receiving is one of the things Reorda does, disclosure I built it. Each PO line stores unit cost and selling price on same row so margin’s right there next to quantity when you’re receiving, not separate lookup per product after.
Doesn’t solve deeper thing Teddy_Chang’s asking below (per-receipt audit trail with reversals) it’s cost+price visible on same screen. For day to day catching supplier overcharge before it hits shelf it’s been enough for us
This is the part I keep circling back to as well, and you put it more precisely than the original request does. Two things I would add from trying to build it.
Reversals matter more than they look. If a correction overwrites the original receipt, the cost of goods for orders that already shipped changes with it. Close your books, fix a cost next week, and last month’s margins quietly move. Keeping the original receipt plus a reversal is what makes the number explainable instead of merely current.
The second half is the sale side. A receipt trail only pays off if each order resolves against the cost that applied on its own date. Shopify’s Cost per item is a single mutable field, so any profit report built on it rewrites history every time somebody updates a cost. That is why “show cost at receiving” and “keep a cost history” are really one feature request, not two.
@Roman_P thanks for the note. Cost and price on the same PO row is the right fix for catching a supplier overcharge before the goods hit the shelf, and I agree that is a different job from the audit trail.
@carriec228 you asked for weighted average cost on receiving specifically. Disclosure: that is what I am building (Costline: cost history per receipt, margins from the cost that was true on the day of each sale, writes the current average back to Cost per item). It is deliberately not an inventory suite.
To either of you, or anyone else here receiving real deliveries every week: I would rather test the model against your actual workflow than guess. If you are willing to tell me where it breaks, reply here or use the link in my earlier post. Either way, the receipt-level spec in the post above is the version Shopify should be reading.
Margin columns at receiving would help. But after watching merchants do this daily I think the number you need in that moment is different: what changed since the last time you bought this item.
Margin tells you where you stand. The delta tells you whether to act - reprice, renegotiate, or flag the invoice because the supplier moved 8% and nobody caught it until the P&L did.
Native receiving shows neither, and this request has been open since February, so I wouldn’t hold my breath.
Disclosure: I build an app in this space ([Binly](Binly ‑ Stocktake & Reorder - Stocky replacement: phone stocktakes, POs & smart reorder | Shopify App Store)) and we ended up building exactly that comparison. Receiving checks each line against your last order from the same supplier and flags drift past your threshold, with the % and the dollar impact on that order. The static margin view is the half Shopify could ship tomorrow; the comparison is the half that catches money actually leaving.
And +1 to the earlier point about reversals. If a correction overwrites the original receipt you lose the audit trail. Receipts should be immutable rows and corrections should be new rows.
We built Stockroom for exactly this - purchase orders, receiving, reordering and stocktakes for merchants coming off Stocky, and it imports your Stocky data directly via API (do that before Aug 31 - Stocky’s API shuts off with the app). Purchase orders and receiving are free and stay free - that’s the core of the app, not a trial. Would love your feedback if you try it.
I think the supplier-cost part is especially important here. If the quantity is received correctly but the supplier cost has changed, the inventory can look operationally fine while the margin behind it is already wrong.
Founder disclosure: I’m building VedaSuite for Shopify merchants. One of our current areas combines supplier/operational reconciliation with Product Profit Intelligence — identifying cost discrepancies and showing their financial impact rather than discovering them later through margin reporting.
Your “catch the supplier pricing error before it reaches the shelf” workflow is very close to that use case.
Developer of Replenly here, being upfront. Replenly shows cost, price, and margin data on purchase orders. When you’re receiving stock, you see the landed cost per unit including shipping and duties, not just the supplier price. Margin visibility is baked into the PO workflow so you’re not guessing while receiving.
It also imports your Stocky CSV exports directly if you’re coming from that workflow. $19/month, free tier for under 100 SKUs.
