Procurement
Food cost

Restaurant Goods Received Note Price Errors: Fix Moving Average Cost

Restaurant Goods Received Note Price Errors: Fix Moving Average Cost

A wrong price on a single goods received note does not announce itself. The quantity is right, the supplier is right, the delivery turned up, so nothing on the screen looks off. But the unit price is wrong. That one figure quietly rewrites the item's moving average cost, and with it every recipe, food cost percentage and stock valuation that leans on it. Most operators find out weeks later, when a stocktake value looks wrong and nobody can say why.

How One Wrong Receiving Price Corrupts Your Cost

Moving average cost is built from your purchase history, so every goods received note feeds it. When a note carries a wrong unit price, the system blends that figure into the average and re-costs the recipes that use the item. One keying error therefore spreads from a single delivery into recipe costs, food cost percentage and the value of everything still on the shelf.

A goods received note records what arrived and at what price. Supy reads the price on each note, updates the item's running average cost in the inventory ledger, and recalculates the theoretical cost of every recipe that uses it. That is exactly the behaviour you want when a supplier's real price moves. It is also what makes a keying error dangerous, because the system treats a wrong price the same way it treats a real one.

A worked example shows how far one figure travels. Say you hold 30 litres of cooking oil at $3.00 a litre, a value of $90. A 20-litre delivery arrives, invoiced at $60.00 in total. Someone keys that $60.00 into the per-litre field, so the system books the delivery at $1,200 instead of $60.00. Your moving average cost is now $1,290 spread across 50 litres, which is $25.80 a litre. That is 8.6 times the real cost, and every dish using that oil looks 8.6 times more expensive to make.

Nothing errored, and the quantity on hand is still correct. Only the cost is wrong, which is why the error hides so well.

Illustrative example: one wrong receiving price lifts a sample item's moving average cost to $25.80 from a real $3.00 a litre

Where the Wrong Price Comes From

Most corrupted averages trace back to a handful of receiving habits, not to the system itself. Each one puts a plausible-looking number into the price field, so no alert fires.

  • A unit mismatch. The invoice shows a case or pack price and someone keys it against a single unit, or the reverse. The line total lands in the per-unit field and the cost jumps by the pack size.
  • A stale price carried forward. An old price is copied onto a new note because the catalogue was never updated, so the average drifts toward a figure the supplier stopped charging months ago.
  • A double-entered note. The same delivery is received twice. The quantity and the spend both double, and the average shifts even when every price on both notes is correct.
  • Charges spread onto item lines. Pallet, delivery or fuel fees get added to item prices instead of booked separately, lifting the cost of goods that did not actually cost more.

The pattern underneath all four is the same. The price field accepts whatever it is given, and a wrong entry becomes the new truth for that item until someone notices.

A case price on a supplier invoice keyed as the per-unit price on a delivery

How to Catch It Before the Stocktake

You can catch a wrong price the day it lands, rather than waiting for the stocktake to expose it. The checks below take minutes and run against what the system already stores.

  • Compare the two cost figures. Supy keeps a running average cost and the most recent purchase price for every item at every branch. When the average sits far above or below the last price you actually paid, a note has skewed it, and the gap tells you by how much.
  • Filter received items by price discrepancy. The Received Items Page lists every received line across your goods received notes and opens on a price-discrepancy view. Each line reads as needs review, price updated, credit issued or ignored, so you work a short list of exceptions instead of re-reading every delivery.
  • Read the cost-movement trail. Every price change recalculates the affected recipes and writes a timestamped record of what drove the move. A sudden jump traces straight back to the note that caused it, with no spreadsheet archaeology.
  • Scan the stock movement history. Filter an item's movements to goods received and export the list. An outlier price stands out against every other receipt for the same item, and the export gives finance the evidence in a form they can keep.

Run these on your highest-volume items first. A wrong price on oil, dairy or protein moves the average far more than the same error on a garnish nobody buys in bulk.

Supy Received Items page filtered to price discrepancies, flagging an olive oil line $16.00 above the agreed price

How to Correct the Price Without Breaking the Ledger

Correcting the cost does not mean deleting the delivery. A posted goods received note is locked so the stock and cost record stays intact, which means you fix the price in place rather than erasing history.

  • Update the expected price. On the Received Items Page, set the correct unit price on the flagged line. Supy recalculates the item's average cost and every recipe that uses it, so the numbers recover without a manual re-cost.
  • Raise a credit note for a real overcharge. When the supplier genuinely charged too much, post a supplier return. It syncs to your accounting system as a credit note and emails the supplier, so the books and the supplier relationship both stay straight.
  • Keep the trail. Every edit and every return is logged with a timestamp and the person who made it. That record is what you show a supplier in a dispute and an auditor at year end.

Fix the cost before the next count rather than after it. Once a stocktake is valued on a corrupted average, the variance it reports is noise, and you spend the review chasing a gap that never existed.

Timeline showing a wrong receiving price is a two-minute fix on delivery day but corrupts the stocktake by month end

If you are not sure this is happening in your own operation, three checks settle it quickly. Pull any item where the average cost and the last purchase price are far apart. Open the Received Items Page and look for lines still flagged for review. Check whether a recent stocktake valuation moved more than the deliveries behind it should explain. If any of the three turns something up, start with the item whose average cost sits furthest from its last price. That is where the biggest correction is waiting.

Wrong receiving prices are one of the quiet ways a cost of goods sold number drifts with no obvious cause. Supy catches the price at the door and keeps the average honest. The stocktake becomes the moment you confirm the count, not the moment you discover the cost was wrong all along.

Book a Demo with Supy - catch wrong receiving prices before they corrupt your cost

Ready to optimize your restaurant operations?

Blog

Our operational insights

Inventory
Procurement

Cost control strategies for multi-unit restaurants

Integration
Inventory

AI‑Driven Procurement: A Step‑by‑Step Guide to Slashing Food Waste and Food Costs

Inventory
F&B
Analytics

How Technology Can Streamline Restaurant Procurement: Optimise Inventory, Staffing, and Menu Planning for Profitability

Your questions 
answered

Everything you need to know about Supy — from setup to integrations, pricing, and daily use. If it’s not covered here, just ask.

What is moving average cost in restaurant inventory?
+

Moving average cost is the running cost per unit the system holds for an item, recalculated from your purchase history each time you receive stock. When a delivery arrives at a new price, the system blends that price with what you already hold to produce a fresh average. Recipe costs, food cost percentage and stock valuation all read from this figure, so it drives most of your cost reporting. Supy also keeps the most recent purchase price alongside the average, which lets you see at a glance whether a recent delivery has pulled the average away from what you pay now.

How does a wrong goods received note price corrupt moving average cost?
+

A wrong price on a goods received note feeds straight into the average, because the system cannot tell a keying error from a real supplier price. It blends the wrong figure with your existing stock, recalculates the item's average cost, and then re-costs every recipe that uses the item. One mistyped unit price therefore moves recipe costs, food cost percentage and the value of stock on hand, all from a single line. The quantity stays correct, so nothing looks broken on screen. That is why the error can sit undetected until a stocktake valuation finally exposes it.

Why does a receiving price error stay hidden until the stocktake?
+

Because the delivery itself looks correct. The supplier, the date and the quantity all match, so the receiving check passes and no alert fires on a plausible-looking price. The damage sits in the cost field, which few people review line by line during a busy service. The average cost drifts quietly, food cost percentage moves a point or two, and none of it points back to one note. The error usually surfaces only when a stocktake values stock on the corrupted average and the number comes out wrong, by which time the goods may already be used.

How do I find a wrong receiving price before it affects my stock valuation?
+

Compare the average cost against the most recent purchase price for each item. When the two sit far apart, a note has skewed the average and the gap shows by how much. Supy's Received Items Page lets you work faster, listing every received line and opening on a price-discrepancy view, so you review a short list of exceptions rather than every delivery. The cost-movement trail then traces a jump back to the note that caused it, and the stock movement history lets you export an item's receipts so an outlier price stands out. Run these checks on high-volume items first.

Can I delete a posted goods received note to fix a wrong price?
+

No. A posted goods received note is locked so the stock and cost record stays intact once a delivery is confirmed to the ledger. You fix the price in place instead. On the Received Items Page, set the correct unit price on the flagged line, and the system recalculates the item's average cost and the recipes that use it. When the supplier genuinely overcharged, post a supplier return, which syncs to your accounting system as a credit note. Both routes keep a full timestamped trail of who changed what, which is what protects you in a supplier dispute or an audit.

What happens to my recipe costs when I correct a goods received note price?
+

They recalculate automatically. When you set the correct price, the system updates the item's moving average cost and re-costs every recipe that uses the item, so theoretical food cost and profitability figures recover without a manual re-cost. It also writes a timestamped record of the change, so the correction is auditable rather than silent. The recovery is only as good as the figure you enter, so check the correct unit price against the invoice before you save. Once it is in, the next stocktake values stock on an honest average, and the variance it reports reflects real movement.

How do I stop wrong receiving prices from recurring?
+

Tighten the moment the price is keyed, because that is where the error starts. Confirm the unit on every line, so a case price never lands in a per-unit field. Keep the item catalogue current, so old prices are not copied onto new notes. Receive each delivery once to avoid double entries, and book pallet or delivery fees separately rather than spreading them across item prices. Supy's auto-dispute threshold and additional-charges cap help by flagging variances and limiting what can be added to a note. A short weekly review of the price-discrepancy list catches anything that still slips through.

Ready to transform your operations?

Join 3500+ restaurant operators cutting costs, streamlining operations and making smarter decisions with Supy.