Your recipe costs were right the day someone entered them. Odds are that was 12 to 18 months ago, and your vendors haven’t stood still since.
expect costs to keep climbing through year-end
started tracking inventory and waste more often
switched suppliers or vendors
Source: R365 2026 State of the Restaurant Industry Mid-Year Report
Operators are pulling every lever they can find. Only 52% raised menu prices to cover the hit, the lowest share in three years, because guests are already stretched. So they’re working other angles: Twenty-two percent started tracking inventory and waste more often, and 20% switched suppliers or vendors. On the revenue side, nearly half say growing sales is their top priority for the rest of the year.
Every one of those moves assumes you know what each plate costs you today. If your recipe costs are off, the math stops working. A price increase can still leave a dish underwater, and selling more of a plate that’s losing money only loses more money.
The fix is something you already have: Recipe Costing. This guide breaks down
01
A recipe cost stays accurate only until the next vendor price change. After that, it slowly turns into a guess.
When a vendor raises the price of an ingredient, every recipe that uses it gets more expensive. If those costs were entered by hand, nothing updates on its own. The dish keeps selling at its old margin, and nobody notices.
Here’s what that looks like on a single plate:
Vendor pricing gets the attention, but recipe costs also go stale from inside the kitchen:
A cook swaps in a $6-per-pound cheese when the usual $4.50 one runs out. The swap sticks, and the recipe still costs it at $4.50. That’s a 33% jump on that ingredient that nobody recorded.
A scoop creeps from 4 ounces to 4.5 ounces. That’s a 12.5% overrun on that ingredient, and the recipe still says 4.
A house aioli costs 40 cents a portion and goes on six dishes. If it isn’t built as its own recipe, every one of those plates is undercosted by 40 cents.
A case of tomatoes costs the same whether you dice it for a salad or seed it for pico de gallo, but seeding throws away more of each tomato. Cost both at the same yield and the pico looks cheaper than it is.
Every number built on a recipe cost inherits its error. Here’s where that shows up in practice:
If these sound familiar, your recipe costs are due for an update. Finishing setup keeps them current from here on.
Pick your best-selling dish. Pull the latest invoices for its three most expensive ingredients and compare those prices to what your recipe uses. If they don’t match, you’ve found your first stale cost. Write down the difference per plate and multiply it by last month’s sales of that item. That number is what one stale recipe cost you in a single month.
02
Once setup is finished, your recipes run on a loop that keeps itself current.
01
Build: Recipes are built from standardized ingredient lists and portion sizes.
02
Price: Vendor invoices keep ingredient prices up to date.
03
Compare: POS sales show what you should have used, and inventory counts show what you did use.
04
Adjust: You adjust price, portions or purchasing based on the gap.
Vendor price changes flow into recipe costs automatically. Nobody has to re-key a price, and nobody has to hunt for every recipe that uses a given ingredient.
With Recipe Costing connected to Purchasing and your POS, R365 compares what you should have spent with what you did spend. That actual-vs-theoretical (AvT) variance shows up by item and by location as often as you count inventory. Count weekly, and you’ll catch problems weekly, well before period close.
Current recipe costs feed menu engineering, so you can catch problems before guests do. That $15 plate that quietly went from $4.50 to $5.25 to make shows up as underpriced before your next menu goes out. That leaves you time to reprice it or rework the recipe.
Once setup is done, ingredient prices take care of themselves. What’s left is the upkeep only your team can do: updating a recipe when a substitution becomes permanent and building new dishes before a menu launch.
Setup goes faster when the right people and files are ready before anyone opens a screen. Work through this list first.
Setup stalls when it belongs to everyone. Name one person to own it, usually an Ops Director or Kitchen Manager, and give them a finish date. Ask finance to review the first AvT report with them.
Binders, spreadsheets, laminated line sheets, whatever your team actually cooks from.
At least the last month for your main distributors.
Every item guests can order, including modifiers you charge for.
Last month’s item-level sales, so you know which dishes matter most.
You don’t need every recipe built on day one. Sort last month’s sales by quantity sold and start with the top 20 items. The dishes you sell most use the most ingredients, so building them first gets you meaningful AvT data fastest.
One thing to expect: Until every menu item has a recipe and is mapped, your AvT report will overstate the gap. Theoretical usage only counts items with recipes, but actual usage counts everything you bought. Treat early reports as a progress check, and start reading variance closely once mapping is complete.
Walk the line with your kitchen lead and list every sauce, dressing, marinade and batch item. Anything prepped in-house and used in more than one dish should become its own recipe. These are the costs most likely to be missing today.
For your top sellers, have a cook build each dish while someone weighs every component. Use those real weights in the recipe instead of the numbers on an old spec sheet. The gap between the two is often your first finding.
04
Recipe Costing builds on Item Costing, so each step depends on the one before it. Skipping ahead is the most common reason setup stalls.
Full instructions for each step live in the Recipe Costing setup documentation.
Complete every Item Costing requirement before you build a single recipe or map anything to a menu item.
Done looks likeYour purchased items and vendor items exist in R365 and carry current costs from your invoices.
Common snagDuplicate items from different vendors that never got linked. Clean these up now, or your recipes will pull the wrong price.
Your POS menu items import into R365 so they can be matched to recipes later.
Done looks likeEvery item guests can order shows up in R365, and new items appear when your POS adds them.
Common snagOld or seasonal items still active in the POS. Retire what you no longer sell so your mapping list stays clean.
Once your purchased items and vendor items exist, build your recipes in R365. Start with your top 20 sellers and every sub-recipe they use, then work through the rest of the menu.
Done looks likeEvery menu item has a recipe with exact quantities, and each shared sauce or prep item is built once and used everywhere it belongs.
Watch the Prepped boxIf a recipe item isn’t used for Prep Logs, leave the Prepped box unchecked. Checking it by mistake will throw off your costing.
This is the last step. Map each recipe to its POS menu item.
Done looks likeWhen a menu item sells, R365 knows exactly which ingredients it should have used.
Common snagMenu items with modifiers or sizes. Make sure each variation points to the right recipe.
Run through these questions with your team. The first “no” is your next step.
05
A recipe in the system is only as good as the numbers inside it. These habits keep your theoretical food cost honest.
List every ingredient at the quantity actually used, down to the ounce or the each. A “handful” of cheese can’t be costed. Four ounces can.
Make each sauce, dressing and batch item its own recipe, then add it to every dish that uses it. When the price of cream goes up, every dish with your house cream sauce updates at the same time.
Cost ingredients as they land on the plate, after trim and cooking loss. If a case of produce loses a quarter of its weight to trim, your recipe should reflect that. Otherwise your theoretical cost will look better than your kitchen can ever deliver.
The recipe in R365 should match what cooks actually make. If the line has quietly changed a dish, decide which version is right, then update either the recipe or the training.
Every location should build the same dish from the same recipe. That’s what makes location-to-location comparisons fair. If one store runs a different version for a good reason, build it as its own recipe.
Add a recipe check to every menu launch and every vendor switch. It takes minutes at the time and saves weeks of confusing variance later.
06
Your first full actual-vs-theoretical report, once every item is mapped, is where Recipe Costing starts paying for itself. Here’s how to read it.
Say your food cost goal is 31%. Two locations report their numbers:
Actual is 33.3%. It looks like trouble. But theoretical is 32.9%, so the gap is only 0.4 points. The kitchen is running close to spec. The real issue is that the recipes themselves cost too much at current prices.
Actual is 31.5%. It looks close to goal. But theoretical is 29%, so the gap is 2.5 points. This kitchen is losing product somewhere.
Looking only at actual food cost, you’d send help to the wrong store. The variance tells you which problem you have: a pricing problem or an execution problem.
Rank ingredients by variance in dollars. A small percentage on an expensive protein often costs more than a big percentage on a cheap garnish.
Focus there first. Chasing every line item at once wears a team out.
Compare invoices to what was ordered and received. Missed overcharges show up here.
Weigh a few portions during a real service. Portion creep is easy to spot once you look for it.
Make sure the recipe matches what the line makes today, including any substitutions.
Eli’s Restaurant Group began reviewing AvT reports weekly with its location managers. Those reviews turned up one location making macaroni and cheese incorrectly, which was causing steady overuse of cheese and cream. The report pointed to the ingredients. The weekly review made it visible.
Put a 20-minute AvT review on the calendar every week, with the GM and kitchen lead for each location. Bring the top three variances and leave with one owner for each.
Current recipe costs change which menu decisions make sense. They also show you where your old assumptions were wrong.
The SOTRI Mid-Year Report shows operators getting more careful about menu price increases. Instead of raising prices across the board, many are building dishes around ingredients that work across several menu categories. Others lean on seasonal and limited-time items so they can pivot quickly when ingredient prices move. Both strategies need accurate, current recipe costs to work.
Menu engineering weighs each dish’s profit against how often guests order it. With stale costs, a popular dish can look profitable when it has quietly lost margin. Recheck your crowd favorites first.
For the full menu engineering framework, see our Guide to Recipe Costing and Menu Engineering.
Before you change a price or a portion, update a copy of the recipe and check the new cost and margin. Then decide. It’s faster than guessing and cheaper than finding out a month later.
08
Each of these R365 customers got current, item-level cost data in front of the right people and moved its food cost.
theoretical food cost improved
saved on two ingredients
food cost
companywide CoGS
Six Connecticut concepts had loose recipes that differed from location to location, so a theoretical food cost wasn’t possible. The team standardized recipes and automated accounts payable, so vendor price changes flowed into plate costs. Weekly AvT reviews with location managers found problems like the macaroni and cheese overuse above.
The group saved $500,000 in food and liquor, beer and wine costs, and improved theoretical food cost by 2.5 to 3 points.
Ultra Steak runs 23 locations across brands including Texas Roadhouse and Aspen Creek Grill. Its team used R365’s inventory cost-tracking tools to watch item costs over time. That visibility saved $58,000 on ribs and $48,000 on lettuce.
VP of Finance Kevin O’Bold described how the team uses it: “Our corporate chef or product coach can pull up custom financial reports and actually see item cost trends and say, ‘Wow, it’s been stable for so long, and then boom, I saw this spike. I need to talk to purchasing. We have to figure out a substitute.’”
Before R365, manual work in QuickBooks Enterprise took up most of the finance team’s time. After, reports showed item-level price discrepancies. The team then took that data to vendors and negotiated. The result was a food cost drop from 30% to 25%.
Five locations share a menu with millions of possible ingredient combinations. Recipes were standardized across every location, and staff were trained to precise portion standards. Store managers could see sales against their forecasts and weekly food budgets. Companywide CoGS fell from 28% to 23%, beating the 26% target.
09
Setup is a one-time project. Keeping costs honest is a cadence.
Kitchen leads glance at variance on the ingredients that move most, such as proteins and produce.
GMs review food cost percentage and AvT variance for their location. Do quick counts of high-cost and perishable items between full counts.
Finance compares locations side by side and flags any store whose variance keeps climbing.
Review menu performance.
Once your costs update from invoices, you have a price history for every item you buy. Show vendors exactly when and how much a price moved, and ask them to explain it. BRG used item-level price reports in vendor negotiations and cut food cost from 30% to 25%. Ultra Steak tracked item costs to spot spikes early and saved more than $100,000 on two ingredients.
Give managers a reason to care. Food cost moves when the people on the floor can see it. Share location-level numbers with GMs every week. If bonuses are tied to food cost, give managers the data during the period so they can act on it.
10
Food costs are still climbing for most operators, and fewer are covering the increase with menu prices. That puts more weight on what happens inside your kitchen and at your receiving door.
You’re already paying for the tool that shows you what’s happening there. What’s left is a short list of setup steps, and each one is covered above. Start with the first “no” on your checklist, and book your first weekly AvT review for the week setup is done.
See how Restaurant365 helps finance leaders protect every point of margin — with accounting, inventory, workforce, and operations unified in one system built specifically for restaurants.
Stay up to date on restaurant trends, best practices, and insights to help your team run smarter.
Growing menu of restaurant resources all designed to help you optimize your restaurant operations.
Restaurant365 brings together accounting, operations, scheduling, and more in a flexible platform—empowering restaurants to choose the solutions they need and scale with confidence.