How to Track Ingredient Price Changes in a Restaurant

Most restaurant owners do not lose margin in one big event. They lose it in small price changes nobody noticed: oil up a few percent here, chicken up there, a pack size quietly reduced. By the time it shows in the monthly numbers, it has been costing money for weeks. Dollar figures are illustrative examples.

The pressure is widespread. The National Restaurant Association reported in March 2026 that about 82% of operators had higher food costs than a year earlier, and that food costs were up 34% compared with pre-pandemic levels.

Step 1: Choose what to watch

You cannot track every item, and you do not need to. Rank ingredients by total spend over the last three months and start with the top 20. Those items drive most of your food cost, so they drive most of your risk.

Add any item that sits in a signature dish, because a price jump there hits your best seller.

Step 2: Find your price source

Prices come from three places:

• Invoices: the most reliable record of what you actually paid.
• Supplier ordering pages or portals: where prices are shown before you order.
• Price lists and sales reps: useful, but confirm against invoices.

Whichever you use, compare on the same unit. A change in pack size can look like a price change or hide one. Compare price per counting unit (per kg, per litre, per each), not price per case.

Step 3: Keep a simple log

The formula: change = (new price - old price) / old price. For olive oil: ($68.64 - $62.40) / $62.40 = 10.0%.

Step 4: Set alert thresholds

Decide in advance what size of change triggers action, so you are not reacting to every cent. For example, review any change over about 5% on a top-spend item, or over about 10% on any item. These are starting points; adjust them as you learn which items hurt.

Step 5: Carry the change into plate cost

The log is only useful if the numbers flow through to the menu. Illustrative case: chicken thighs go from $7.50 to $8.25 per kg, a 10% increase. A dish uses 220 g per plate.

• Added cost per plate: 0.22 kg x $0.75 = $0.165
• At 120 plates a week: about $19.80 a week, or roughly $1,030 a year

One ingredient on one dish. Now think about the whole menu. Update the recipe cost, check the new food cost percentage, and decide.

Step 6: Decide what to do

When a price rises you have options, roughly in this order:

1. Check the invoice. Was it an error? See how to check supplier invoices.
2. Ask the supplier why, and whether it is temporary.
3. Compare alternatives. See how to compare supplier prices.
4. Adjust portions or recipes deliberately, without hurting quality.
5. Feature other dishes that use cheaper ingredients.
6. Reprice the dish if the cost increase is lasting. See how to price a menu item.

Common mistakes

• Comparing case prices when pack sizes changed.
• Updating the log but not the recipe costs.
• Tracking everything and acting on nothing.
• Relying on memory. Memory rounds prices and forgets dates.
• Waiting for month-end. Act when you see the change.

Where software can help

ChefMind AI's Chrome extension reads item name, SKU, pack size and price on GFS and Sysco ordering pages as you browse and keeps a price history with the change from the previous reading. Invoice automation can also read invoice details into your records for you to review. Neither replaces the decision about what to do.

The short version

• Track your top 20 items by spend, on a per-unit basis.
• Log every change, set alert thresholds, and update recipe costs the same day.
• Decide deliberately: verify, ask, compare, adjust, reprice.