How to Manage Costs in Shopify When Stock Arrives at Several Prices

Which is exactly the right answer until your stock stops arriving at one price.

The field shows the current cost on the product page and feeds Shopify's own profit reports, and it does that job well. What it is not built to do is remember that the same SKU came in at $10.40 in March and $12.90 in June, because there was one field and there were two receipts. So the fix people reach for first, going back and making the number accurate, does not work. Accuracy was never the missing ingredient. Room was.

The distinction matters, because "our costs are out of date" and "our costs cannot be represented" have completely different fixes. The first one you solve with an afternoon and a bit of discipline. The second one you cannot solve in that field at all, no matter how carefully you type.

Why an Accurate Cost Still Gives You the Wrong Margin

Say you sell one SKU. You received 300 units in March at $10.40 each landed, and 500 units in June at $12.90 each landed, because the supplier moved and so did the freight rate. Both lots sit in the same bin. Nobody can tell them apart on the shelf.

In July you sell 400 units.

Now go and make Cost per item accurate. Which number is the accurate one?

This is an example, not a customer. The arithmetic is the point, and you can check every line of it.

One Field, Four Defensible Answers

Four answers. A $1,000 spread, on one SKU, in one month. Three of them are defensible if you are looking only at the field, and someone in your business could argue for any of them in good faith.

None of that is carelessness. The field is doing exactly what it says it does. You asked one number to describe two receipts, and it answered with one number.

If you want the structural version of this, we wrote it up separately: can Shopify track two costs for the same product?

The Part That Does Not Tie Out

Here is the test that turns this from a reporting preference into an accounting problem.

You spent $9,570 on that stock. 300 at $10.40 is $3,120, plus 500 at $12.90 is $6,450. After selling 400 units you have 400 left. Whatever you book as cost of goods sold, plus whatever is sitting in inventory, has to add back up to $9,570, because that is the money that left your bank account.

Cost them oldest first and it does. COGS of $4,410, closing stock of $5,160, total $9,570.

Cost them from one field holding $12.90 and it does not. COGS of $5,160, closing stock of 400 units at $12.90 which is another $5,160, total $10,320. You have $750 of inventory value that never existed. Put $10.40 in the field instead and the total is $8,320, which is $1,250 of stock you paid for and cannot find on the balance sheet.

That is the difference between a number and a record. A number can be right about today. A record has to add up to what you actually spent, and it has to keep adding up next month, which is the thing your accountant signs.

What Shopify Says the Field Is

Shopify does not hide any of this. As of August 2026, their own documentation says it plainly.

• Cost per item is the cost to you of the product or variant, and the example given is "the price that you paid the manufacturer, excluding taxes, shipping, or other costs" (Shopify Help Center). Shipping is excluded by design.
• Shopify describes a "single static Cost per item field" that "stays fixed when you receive a purchase order or transfer", and adds: "For weighted-average costing or automatic landed cost allocation, such as duty, freight, or tax, you can use ... a third-party costing app" (Shopify Help Center).
• Profit reports run off it: "Profit is reported only for products and variants that had cost recorded at the time they were sold", and "the Cost per item field contains static data, which means that the data in your profit reports is only relevant to a specific point in time" (Shopify Help Center).

Static, fixed on receipt, excludes freight, and only meaningful at a point in time. Every one of those is a reasonable design decision, and the vendor names the limit itself rather than leaving you to find it. They are only a problem if you are asking the field to be your cost record.

Where the Rest of Your Costs Live

If your costs are also written down somewhere outside Shopify, you already know the shape of the second half of this. A sheet of supplier prices. A freight invoice or two. A tab where somebody works out what a unit really cost, updated when there is time.

That file is usually right about the arithmetic. Its flaw is somewhere else: it cannot see a sale. Your store shipped forty units this morning and the file has no idea, so every number in it was true when it was typed and has been drifting since. We compared the two honestly here: managing COGS in a spreadsheet.

Which makes the real question something other than which of the two to trust. Neither one is a record of what your stock cost, and something has to be.

The Cost You Type Is Not the Cost You Paid

There is a second problem underneath the first one, and it only bites if you import.

Whatever you type into the field on the day the container lands, you are typing the supplier invoice, because that is the only document you have. The forwarder bills after the goods arrive. The customs broker bills after that. If those invoices turn up three weeks later and you have already sold 400 units, the cost you sold at was never the cost you paid, and nothing goes back and restates it.

So "make the field accurate" has a hidden precondition: accurate as of when, and including what? We walk through the four ways this goes wrong, with the numbers, in why your Shopify COGS is wrong.

What a Cost Record Needs Instead

Three things, and none of them fit in a field.

A cost per receipt, not a cost per SKU. Every delivery of stock arrives at its own price. The record has to keep each one, because those units are genuinely different costs wearing the same barcode.

A drawdown order. When you sell 400 units, something has to decide which receipt they came out of. Oldest first (FIFO) is the usual answer, and it costs stock in the same order expiry-dated products already ship in. Weighted average is a legitimate alternative, compared honestly in FIFO vs weighted average cost. What is not an alternative is having no answer, because then the cost of a sale is whatever was in the field that day.

Freight and duty folded in before the number forms. Not added to a report afterwards. Allocated across the units in the shipment while the cost of those units is being decided, so what gets drawn down later is what the goods actually cost to land.

That is the whole of it. Landara sits beside Shopify and keeps that record: a costed quantity for every receipt of stock, drawn down oldest first as orders ship, freight and duty allocated in before the cost is set, ending in a ready-to-post Dr COGS / Cr Inventory journal for Xero or QuickBooks Online. You decide when it posts. Shopify stays the system of record for quantity, and nothing gets ripped out.

So Should You Fill In Cost per Item?

Yes. It is not a useless field. It is a field with one job.

It drives the margin display on the product page and Shopify's own profit reports, so it should hold your best current landed cost rather than the supplier price you typed in 2024. Landara writes the cost back to it, which is the part that keeps it true without anyone maintaining it (how the Shopify connection works).

Just do not ask it to be the record. It is a display of a cost. It is not a history of your costs, and it was never built to be one.

That distinction has a consequence people meet the first time they correct the field after a freight invoice lands: updating Cost per item does not fix the orders you have already shipped, because Shopify recorded the cost at the moment of each sale.

Frequently Asked Questions