How to Track Supplier Price Changes Before They Hit the P&L

Most restaurants do not have a supplier price problem because nobody cares. They have one because the facts live in too many places.

The invoice has the new price. The recipe sheet has the old cost. The menu has last quarter's selling price. The POS has the volume. The chef remembers a substitution. The bookkeeper sees the spend after the month is already closed.

That gap matters right now. USDA ERS reported that food-away-from-home prices were 3.6 percent higher in April 2026 than in April 2025, while food-at-home prices were 2.9 percent higher.¹ ERS also forecast 2026 food-away-from-home prices to rise 3.5 percent, with a 2.8 to 4.2 percent prediction interval.² That is the air every operator is breathing. It does not tell you which dish is leaking. Your invoices do.

What should you track on each supplier invoice?

Do not start with a giant dashboard. Start with the fields that make a price change useful.

Field	Why it matters	Example
Invoice date	Shows when the price changed and whether it stuck.	June 2, 2026
Supplier and item code	Separates a true price move from a vendor or brand swap.	Northline Dairy · MOZZ-SHRED-6X5
Pack size and net weight	Catches smaller cases, new counts, and messy substitutions.	6 × 5 lb case = 30 lb
Case price and usable-unit price	Turns invoice noise into plate-cost math.	$97.50 case · $3.25/lb
Recipes and dishes affected	Ranks the change by menu impact, not annoyance.	Pizza, lasagna, arancini
Confidence and question	Prevents bad automation from treating a fuzzy line as truth.	Possible brand swap; confirm yield

The pack-size column is not optional. A supplier can hold the case price steady and still raise your cost by changing count, weight, grade, yield, or brand. If you only track case price, you miss the move that matters. That is the same trap behind pack-size shrink.

How do you decide which price changes deserve attention?

Use three filters: size of the move, volume of the item, and whether the item touches a dish people actually buy.

1. Calculate the usable-unit change. Case price divided by pounds, ounces, liters, eaches, or expected yield.
2. Attach the item to recipes. A $6 case jump matters more when it feeds the menu's top seller.
3. Use POS volume. Multiply the new ingredient cost by real dish counts.
4. Check for supplier context. Was it a substitute, credit, promo ending, minimum-order fee, delivery charge, or pack change?
5. Pick the action. Reprice, change portion, ask for a quote, swap supplier, adjust par, or accept the hit because quality or reliability is worth it.

This keeps the review from becoming a scavenger hunt. The goal is not to stare at 320 invoice lines. The goal is to know the five changes that can move this week's gross margin.

What does the math look like?

Here is a simple example for a pasta restaurant buying shredded mozzarella.

A $73 monthly move may not deserve a menu rewrite. But if the same mozzarella hits pizza, lasagna, catering trays, staff meal, and waste, the combined number can be worth a supplier call. This is why supplier price tracking has to connect invoices to recipes and POS volume. Price without usage is trivia.

Why timely food inflation data still matters

National price data will never know your exact mozzarella deal. It is still useful background because it tells you when to expect more noise.

In April 2026, ERS said beef and veal prices rose 3.1 percent from March to April and were 14.8 percent higher than a year earlier.³ Fresh vegetables also rose 3.1 percent from March to April, while fish and seafood rose 1.5 percent.⁴ If you run a steakhouse, taqueria, seafood bar, salad-heavy lunch spot, or banquet program, those are not abstract numbers. They are prompts to check recent invoices before the next order lands.

The mistake is treating broad inflation as the answer. It is only the smoke alarm. Your private cost memory is the room-by-room check.

What should the weekly owner review show?

Keep it boring. Boring gets read. A good weekly supplier price review should fit on one page:

• Top price increases by menu impact. Not just biggest percentage jump.
• Pack-size or substitution flags. Show the old and new pack side by side.
• Dishes affected. Include recipe quantity and POS volume.
• Estimated dollar impact. Weekly or monthly, but do not mix both in the same section.
• Missing facts. Yield unknown, invoice description changed, supplier minimum not checked, credit pending.
• Recommended next action. Approve, ask chef, quote-shop, update recipe, or ignore.

That last column is the difference between information and work. If the report does not say what to do next, the operator still has to do the whole job.

Where restaurants usually get tripped up

The first trap is item matching. Supplier descriptions are messy. One line says tomatoes plum 6/#10, the next says tomato canned 6 ct, and the next invoice changes brand or code. Someone has to decide whether those are the same item, a substitute, or a new product.

The second trap is yield. Raw weight is not always usable weight. Meat trim, fryer oil life, seafood loss, peeled vegetables, and batch shrink can turn a clean invoice number into a bad plate-cost number.

The third trap is timing. If supplier prices are reviewed after month-end, the menu and ordering decisions already happened. The useful window is before the next buy, before the next special, and before the chef assumes the old cost is still fine.

That is the job restaurant cost memory is meant to do: keep the last known price, pack, recipe link, and operator correction alive so each new invoice can be compared against something real. Mornay's restaurant operating graph is built around that idea, but the rule holds even if you start with a spreadsheet.

The simple starting system

If you are doing this manually tomorrow, do not boil the ocean. Pick 25 items: proteins, dairy, fryer oil, core produce, coffee, bread, disposables, and anything that appears in more than one high-volume dish.

For each item, write down the supplier, item code, pack size, last paid case price, usable-unit price, and dishes affected. Then process each new invoice against that list. Flag only three things at first: usable-unit price up more than 5 percent, pack size changed, or affected dish volume is high enough to matter.

Once that habit works, add more items. Then add quote checks. Then add recipe updates. The point is to build a living memory, not another dead sheet that is perfect for two weeks and stale by Friday.