The short version.
Keep recipe costs current by tying every dish to dated invoice prices, usable yields, pack sizes, portions, menu prices, and POS volume. Update the recipes that matter whenever a new invoice changes a key item; review the rest monthly so the menu does not run on old math.
A stale recipe cost is quiet. Nobody gets a warning when the burger patty, sauce, cheese, and fries are still using last month's prices in the sheet.
The P&L just looks worse later.
That lag matters right now. BLS reported full-service meals and snacks CPI up 6.5% year over year in May 2026, with a 1.2% jump from April to May alone.1 USDA ERS also had food away from home up 3.6% year over year in April 2026 and forecast a 3.5% increase for the full year.2
Those are menu-side prices. Your buying side can move faster and messier. In the same USDA ERS April data, beef and veal was up 14.8% year over year and fresh vegetables were up 11.5%.3 Eggs moved the other way, down 39.2% year over year.4 That is the point: recipe costs do not drift in one clean direction. They need a current memory by item, supplier, pack, yield, and date.
What does "current" mean for a recipe cost?
Current does not mean perfect to the penny. It means the number is recent enough to make a menu decision without lying to you.
A useful recipe cost has six pieces attached:
- Dated supplier price. The invoice or quote the price came from, not a naked number in a spreadsheet.
- Pack and unit math. Case, pound, ounce, each, gallon, kilogram, and any conversion used to get to the recipe unit.
- Usable yield. Trim, cook loss, drained weight, portioning loss, and waste where it matters.
- Portion size. What the kitchen actually plates, not what the recipe card hoped for.
- Menu price. The price the guest pays today.
- Sales volume. How many units the POS says you sold, so you know whether the change matters.
If one of those is missing, the dish can still have a cost. It just needs a confidence flag. A current cost with a caveat is better than a clean-looking number nobody can defend.
Which recipes should get checked first?
Do not recost the whole menu every time a truck shows up. That is how recipe work becomes office punishment.
Start where the money moves:
| Check first | Why it matters | What to look for |
|---|---|---|
| Best sellers | A small cost change repeats hundreds or thousands of times. | Ingredient price, portion drift, and menu price. |
| Protein-heavy dishes | Beef, seafood, poultry, and pork can swing hard. | Case price, usable yield, and trim/cook loss. |
| Produce-heavy dishes | Weather and seasonality can move the true plate cost fast. | Substitutions, pack size, waste, and garnish creep. |
| Dairy, eggs, coffee, and oils | They hit sauces, brunch, pastry, drinks, and prep recipes. | Recipe mapping across many dishes, not one line item. |
This is where supplier price tracking and recipe costing have to meet. Supplier tracking says the case changed. Recipe costing says which dishes now make less money.
What is the operating rhythm?
Use a two-speed rhythm: fast checks for volatile/high-volume recipes, slower checks for the rest.
After each new invoice, ask three questions:
- Did a watched item move? Watched items are your top 20-40 ingredients by spend or menu impact.
- Does the pack or unit still match? A cheaper case can be worse if the yield, size, or count changed.
- Which dishes use it? Do not stop at the item. Follow it through prep recipes, portions, and POS volume.
Then run a monthly clean-up on the full recipe book: old prices, missing yields, dead menu items, renamed POS buttons, prep recipes that feed multiple dishes, and recipe cards that no longer match the line.
That monthly pass is not about making a beautiful binder. It is about catching the costs that did not scream loudly enough during the week.
Worked example: beef burger.
Say a burger uses 5.3 oz cooked beef. At 80% cooked yield, that is 6.625 oz raw, or 0.414 lb. If the raw beef price moves from $4.10/lb to $4.71/lb, a 14.8% increase, the beef cost rises about $0.25 per burger. At 900 burgers a month, that is about $227/month before bun, cheese, fries, labor, or waste. USDA ERS reported beef and veal up 14.8% year over year in April 2026, which is why this kind of math belongs in the weekly check, not the quarter-end surprise.3
What should change when a recipe cost moves?
Not every cost move deserves a menu price change. Sometimes the right answer is to buy differently, tighten the portion, swap a garnish, fix yield, or ignore the noise.
A good review ends with a short action, not a bigger spreadsheet:
- Approve the new cost if the invoice, pack, unit, and yield make sense.
- Ask a question if the unit conversion, count, brand, or yield changed.
- Flag the affected dishes by menu price, margin dollars, and POS volume.
- Pick the move: leave alone, reprice, resize, change recipe, rebid supplier, or watch one more invoice.
That is the job of Mornay's cost memory: keep dated supplier prices connected to recipes, menus, POS volume, and owner corrections, so the next action is visible. The system should show the proof and the caveat. The operator still makes the call.
What is the simplest setup that works?
You do not need a giant software rollout to start. Pick the 25 ingredients that drive the most spend, the 25 dishes that drive the most sales, and the recipes where the chef already says, "this one feels off."
For each one, store the latest invoice line, the conversion to recipe unit, the yield assumption, and the dishes touched. When a new invoice lands, compare it to the last approved price. If the move is material, push it through the dish math and ask for a human decision.
That is how recipe costs stay current without turning your managers into spreadsheet janitors.
References
- U.S. Bureau of Labor Statistics public API, CPI series
CUUR0000SEFG, full-service meals and snacks. May 2026 index 378.696 vs. May 2025 index 355.433 = 6.5% year over year; April 2026 index 374.201 to May 2026 index 378.696 = 1.2% month over month. Source. - USDA Economic Research Service, Food Price Outlook data download, "Food away from home" row. April 2025 to April 2026 was 3.6% year over year; 2026 prediction midpoint was 3.5%. Source.
- USDA Economic Research Service, Food Price Outlook data download. April 2025 to April 2026: beef and veal up 14.8%; fresh vegetables up 11.5%. Source.
- USDA Economic Research Service, Food Price Outlook data download. April 2025 to April 2026: eggs down 39.2%; 2026 prediction midpoint down 29.8%. Source.
FAQ
How often should restaurants update recipe costs?
Update high-volume and volatile recipes whenever a new invoice changes a key item, and do a full recipe-cost review at least monthly. Beef, seafood, eggs, dairy, coffee, and produce usually deserve faster checks than dry goods.
What makes a recipe cost go stale?
Recipe costs go stale when supplier prices change, pack sizes change, usable yield changes, portions drift, substitutions happen, or the POS mix shifts toward lower-margin dishes. The spreadsheet can still look clean while the kitchen reality moved.
Do I need inventory software to keep recipe costs current?
No. Inventory counts help, but the first control is simpler: keep dated invoice prices tied to recipe units, yields, portions, menu prices, and POS volume. Start with your most-used items and best-selling dishes.
Which recipes should I check first?
Check recipes with high sales volume, expensive center-plate proteins, volatile produce, dairy-heavy builds, and anything where a supplier changed the pack, brand, or case size. Those recipes move the P&L fastest.
What is the safest way to change menu prices from recipe costs?
Do not reprice from one invoice line alone. Confirm the unit conversion, usable yield, portion size, current menu price, and recent sales volume, then decide whether to raise price, change portion, switch item, or leave it alone.