Track supplier price changes without comparing the wrong things
Why package totals can mislead, how normalized unit costs help, and when a price comparison should remain incomplete.
A higher invoice line does not always mean the ingredient became more expensive. Before comparing two purchases, the restaurant needs to know whether the packages represent the same usable quantity.
Package prices are not automatically comparable
A 12-unit case and a 24-unit case are different purchasing units. The same is true for a 5-pound bag and a 10-pound bag. The larger package can cost more in total while costing less for each usable unit.
Compare the package and the unit
Fictional example: Purchase A is a 12-unit case for $24, or $2 per unit. Purchase B is a 24-unit case for $42, or $1.75 per unit. The package price increased by $18, or 75%, while the unit price decreased by $0.25, or 12.5%. Looking only at $24 to $42 would give the wrong operational signal.
Use the previous comparable purchase
The latest purchase should be compared with a previous purchase that can be expressed in the same base unit. That may require a known package size and unit conversion. Supplier, product identity, and packaging context also matter; the immediately previous invoice line is not always the right comparison.
Do not force a comparison
Sometimes the information needed to normalize two packages is missing or unreliable. A variable-weight case may lack its actual weight, or a package quantity may never have been recorded. In that situation, a trustworthy system should mark the comparison incomplete instead of calculating a confident percentage from incompatible totals.
Show both absolute and percentage change
Once two base-unit costs are comparable, absolute change shows the amount added or removed per unit. Percentage change shows that difference relative to the earlier cost. Both should be tied to the units being compared so the number cannot be mistaken for a package-level change.
Keep the number connected to its source
An operator reviewing a change should be able to see the supplier, package, purchase date, source purchase line, and previous comparable purchase. That context makes price history verifiable and helps reveal a packaging change or data-entry issue.
How Venkoi Serve approaches supplier price history
The initial release of Venkoi Serve is planned to connect comparable supplier prices, show absolute and percentage changes, and preserve package price, normalized cost, source purchase context, and supplier history. Insufficient conversion information will leave the comparison incomplete. It will not negotiate with suppliers or electronically place orders.
Helpful guides
Restaurant food cost: from ingredient cost to menu item
How package prices become usable ingredient costs, flow through preparations and yield, and reach the cost of a plate.
Inventory gets harder when the information lives in different places.
Why keeping inventory, purchases, and costs in separate places makes restaurant operations more difficult than they need to be.