Skip to main content

Choosing Which Receives Count Toward Average Cost

The Cost Calculation modal lets you choose which of an item's last three receives count toward its average cost — it's for excluding a bad receive, not for editing what any receive actually cost.

Written by Help

Choosing Which Receives Count Toward Average Cost

How Choosing Which Receives Count Toward Average Cost Works

Access requirements. Opening the modal needs view access to "Inventory" or "Prices"; saving needs edit access to either.

  • What it actually does. It lets you check or uncheck which of an item's most recent three receive, transfer, or initial import lines count toward its average cost, and correct the cost on any line you're counting.

  • You can also exclude a line as you receive it. When you review a line while receiving a purchase order, check "Exclude from avg/last cost" to take the stock in without letting that line's cost move the item's average or last received cost. An excluded line also won't suggest a price or margin change. It still shows up here under "Not used," so you can bring it back into the average later.

  • Editing a cost here changes the source too. If a cost was keyed in wrong, you can fix it on the line itself, and the correction is written back to the purchase order or transfer that line came from. Quantity is still not editable here.

  • Cost is still directly editable in the product list table. "Last cost" (unit and case) is still a live, editable column in the grid — nothing was removed or changed there.

  • Saving triggers a real recalculation. It updates the cached average cost, recomputes your FIFO cost layers — FIFO means first in, first out, so the oldest cost you paid for an item is used up before newer ones — going forward from the earliest affected receive, and can trigger a price update for any markup rule anchored to cost.


Opening the Modal

Step 1

Open the item's Product Drawer and find "Avg / Last cost" in the Price and cost section.

Step 2

Click the icon next to it to open "Cost calculation."


Choosing Which Receives Count

Step 3

Lines are grouped under "Used for cost" and "Not used." Uncheck any line you don't want counted toward the average, or check one to bring it back in. At least one line has to stay checked — otherwise you'll see "Select at least one line usable for cost" and can't save.

Step 4

To correct a cost, type over the cost field on a checked line. Unchecked lines show their cost as plain text instead.

Step 5

For items that come in cases, use "Per unit" and "Per case" in the header to switch how every cost on the screen is shown. Costs are saved per unit either way.

Step 6

Watch "Average cost," "Last received cost," and "Margin" at the top update as you check, uncheck, or edit lines.

Step 7

Click "Update costs" to save.


What It Looks Like

  • Each line shows its source and vendor, the date, the quantity, the unit cost, the line total, and the margin at that cost. Cost is editable on checked lines; quantity isn't editable anywhere in the modal.

  • The "Margin" figure at the top is based on the average cost and updates as you check, uncheck, or edit lines. A line's own total and margin update when you change that line's cost. If the checked lines add up to no cost or no quantity, the average falls back to the last received cost instead of showing $0.00.

  • Lines brought over when your store was first set up count toward the average too, so an item imported at setup and never received since still shows an average cost and a margin based on it.

  • If the item has no receive or transfer lines yet, the modal shows "No receive or transfer lines to calculate from" and lets you enter a cost per unit instead. That cost is used as both the last received and average cost until the item is received on a purchase order or transfer.


Troubleshooting

  • Wondering if this replaced editing cost on the product list: it didn't — "Last cost" is still directly editable in the product list table, and the older cost-editing flow in the drawer still works too. This modal only controls which receives count toward the average.

Did this answer your question?