Exact logic
Neudash writes code for the specific rules, exceptions, approvals, and edge cases in this process instead of forcing it into a fixed flowchart.
Restaurants & Cafes
Running a restaurant on gut feel for food costs is like driving blindfolded—you think you know where you're going until you hit a wall. A 2% food cost increase on $1M revenue erases 50% of your profit. Can you afford not to know?
Running a restaurant on gut feel for food costs is like driving blindfolded—you think you know where you're going until you hit a wall. A 2% food cost increase on $1M revenue erases 50% of your profit. Can you afford not to know? Typical workflow steps include Recipe costing setup, Real-time cost tracking, and Menu profitability analysis.
Best fit
Restaurants & Cafes teams coordinating work across MarketMan, xtraCHEF, and Restaurant365.
Workflow covered
Recipe costing setup, Real-time cost tracking, and Menu profitability analysis
Outcome
Reduces manual work across recipe costing setup, real-time cost tracking, and menu profitability analysis.
Neudash writes code for the specific rules, exceptions, approvals, and edge cases in this process instead of forcing it into a fixed flowchart.
Built-ins are only the start. Neudash can connect the systems in this stack through APIs, webhooks, and OAuth, so the workflow is not capped by a marketplace action list.
The running workflow is code. AI is used to design, document, and repair the process, and only used inside the workflow where reasoning or extraction is actually needed.
Your Sysco rep sent you an email last Thursday:
“Heads up—beef prices are increasing 18-22% effective next delivery due to supply chain issues. Let me know if you want to adjust your standing order.”
You missed it. Buried under 47 unread emails about staff scheduling, equipment repairs, and a customer complaint about cold food.
Friday’s delivery arrives. Your standing order includes 60 lbs of ribeye at the new price: $18.50/lb instead of $15.20/lb. That’s $3.30/lb more.
Your menu price for the ribeye special: $32. Your recipe calls for 12oz (0.75 lb). Your ribeye cost just went from $11.40 per plate to $13.88 per plate.
Old margin: $32 menu price - $11.40 cost = $20.60 (64% margin) New margin: $32 menu price - $13.88 cost = $18.12 (57% margin)
You lose $2.48 per ribeye sold. You sell 15-20 ribeyes per night, 6 nights/week. That’s $1,487-$1,984 per month in lost profit on one menu item.
It’s Tuesday. You’ve been selling ribeyes at the old margin calculation for 5 days. Nobody noticed.
This is what running on gut feel looks like.
28-32% target food cost percentage for full-service restaurants
Restaurant Profitability Benchmarks 2025
2% food cost increase = 50% of net profit on 4% margins
Restaurant Finance Analysis
Only 35% of restaurants track food costs by menu item
MarketMan Restaurant Operations Survey
Ingredient costs fluctuate 5-15% quarterly on average
USDA Food Price Index
Most restaurant owners have a rough mental model of their food costs:
This mental model worked when:
It doesn’t work when:
The problem isn’t that you don’t care about food costs. It’s that you’re flying blind between monthly financial statements.
Here’s what food cost tracking looks like in most restaurants:
You have a Google Sheet with your recipes:
RECIPE COSTING SHEET
Item: Ribeye Special (12oz)
Menu Price: $32.00
Ingredients:
- Ribeye, 12oz @ $15.20/lb = $11.40
- Mashed potatoes, 6oz @ $2.80/lb = $1.05
- Green beans, 4oz @ $3.50/lb = $0.88
- Butter, 1oz @ $4.20/lb = $0.26
- Garlic, 0.5oz @ $6.00/lb = $0.19
Total Cost: $13.78
Food Cost %: 43%
Margin: $18.22 Problems:
Ingredient prices are 6 months old. Ribeye is now $18.50/lb, not $15.20. Butter went from $4.20 to $5.80. Your actual cost is $16.21, not $13.78.
You don’t update it when prices change. You’d need to manually check every supplier invoice, find new prices, update the spreadsheet. That’s 2-3 hours of work monthly. You never do it.
It doesn’t account for waste. The spreadsheet says 12oz ribeye. Your line cook cuts 13-14oz steaks. Actual cost is 15% higher.
It doesn’t connect to anything. This spreadsheet doesn’t talk to your POS, your inventory system, your accounting. It’s a guess, frozen in time.
You use this spreadsheet to make menu pricing decisions, but the data is 6 months stale. You’re steering with outdated information.
| Aspect | Manual Process | With Neudash |
|---|---|---|
| Recipe cost data | Spreadsheet updated manually every 3-6 months (or never) | Recipe costs auto-update when supplier invoices are processed |
| Ingredient price tracking | No systematic tracking, only notice when financials show problem | Track every ingredient price from invoices, alert on changes above 10% |
| Menu profitability | Gut feel about which items are profitable | Exact contribution margin for every menu item, sorted by profitability |
| Price change impact | Don't know impact until month-end financials | Instant: 'Ribeye cost up 22%, menu item margin down from 64% to 57%' |
| Menu engineering | Random menu changes based on popularity | Data-driven: promote high-margin items, fix/remove low-margin items |
| Portion control | Hope line cooks follow recipes | Compare theoretical (recipe) vs actual (sales) usage, flag over-portioning |
Let’s calculate what poor food cost tracking actually costs you:
Scenario: $1M annual revenue, 30% target food cost, 4% net margin
Current state (no real-time tracking):
With real-time food cost tracking:
The math: For every 1% you improve food cost, you add $10,000 to bottom line on $1M revenue.
$15,000-$25,000
annual savings
Recovering 1.5-2.5% food cost through real-time tracking, price spike alerts, portion control, and menu engineering. On $1M revenue at 4% margins, this doubles or triples your net profit.
Food cost tracking automation isn’t about complex algorithms. It’s about connecting data sources you already have so you see problems before they compound:
You build recipe cards for each menu item:
Recipe: Ribeye Special
Ingredients:
Cost calculation method: Link ingredients to supplier SKUs
Now when supplier invoices are processed:
Sysco invoice (March 1):
System automatically:
Alert to manager:
🚨 RECIPE COST ALERT
Ribeye Special cost increased 18% (from $13.78 to $16.21)
Cause: Ribeye price +22%, Butter price +38%
Current margin: $15.79 (49% margin, 51% food cost)
Previous margin: $18.22 (57% margin, 43% food cost)
Lost margin per plate: $2.43
You sold 18 Ribeye Specials last night = $43.74 lost margin
Recommendations:
1. Raise menu price to $36 (maintains 57% margin)
2. Reduce portion to 10oz (maintains current price, 52% margin)
3. Remove from menu, promote higher-margin items
[View Menu Profitability Report] You see this alert Tuesday morning. You decide: raise price to $34 (split the difference), update menu that day.
Impact: Instead of losing $1,500-2,000 over a month, you caught it in 5 days and lost $218. You adjusted. Crisis averted.
You open the system dashboard:
MENU PROFITABILITY ANALYSIS — Last 30 Days
High Margin Items (above 60% margin):
✅ Pasta Primavera: $12 menu, $4.20 cost, 65% margin (32 sold)
✅ Margherita Pizza: $14 menu, $4.90 cost, 65% margin (47 sold)
✅ Caesar Salad: $10 menu, $3.20 cost, 68% margin (28 sold)
Medium Margin Items (50-60% margin):
➖ Chicken Marsala: $22 menu, $9.80 cost, 55% margin (41 sold)
➖ Salmon: $28 menu, $12.60 cost, 55% margin (23 sold)
Low Margin Items (below 50% margin):
⚠️ Ribeye Special: $32 menu, $16.21 cost, 49% margin (18 sold)
⚠️ Lobster Ravioli: $26 menu, $13.80 cost, 47% margin (12 sold)
Overall Food Cost: 31.2% (target: 30%)
Recommendations:
- Promote high-margin items (Pasta, Pizza, Salad)
- Fix or remove low-margin items (Ribeye, Lobster Ravioli)
- If you shift 20% of sales to high-margin items, food cost drops to 28.5% This is menu engineering—using data to make strategic menu decisions.
Before automation, you guessed. (“The ribeye is popular, let’s keep it.“) Now you see: ribeye is popular but barely profitable at current costs.
Here’s a feature most restaurants don’t even know they need:
The system compares theoretical usage (based on recipes × POS sales) to actual usage (based on inventory depletion).
Example:
Last month you sold 120 burgers. Recipe calls for 6oz beef per burger.
Causes:
Alert to manager:
⚠️ VARIANCE ALERT: Ground Beef
Theoretical usage: 45 lbs
Actual usage: 53 lbs
Variance: 8 lbs (18% over)
Impact: $56 wasted cost last month
Possible causes:
- Over-portioning (most common)
- Waste during prep/cooking
- Theft
Recommendation: Review portioning with line cooks. Consider using
a scale during service for consistency. You investigate. Turns out your line cook is eyeballing portions and consistently making them too large. You implement a simple fix: use a scale during prep to pre-portion 6oz patties.
Impact: Variance drops from 18% to 5%. You save $40-45/month on burgers alone. Scale that across all proteins, and you’re saving $300-500/month.
The food cost metric that matters most isn’t overall food cost %—it’s contribution margin by menu item. Contribution margin = menu price - food cost. A $10 salad with $3 cost has better margin ($7) than a $32 steak with $16 cost (also $7)—but the steak requires more labor, takes longer to cook, and has more waste risk. When analyzing menu profitability, sort by contribution margin per minute of labor, not just by margin %. This reveals your true MVPs: items that are fast to make, have high margin, and sell consistently.
Once you have real-time food cost data, you can do menu engineering—the practice of optimizing your menu for profitability.
Plot every menu item on a 2x2 matrix:
Popularity (X-axis): Low → High (based on sales volume) Profitability (Y-axis): Low → High (based on contribution margin)
This creates 4 quadrants:
Examples: Margherita Pizza (47 sold, 65% margin)
Strategy: Feature prominently, make easy to order, train servers to recommend
Examples: Ribeye Special (18 sold, 49% margin)
Strategy: Raise price, reduce portion, or redesign recipe to improve margin
Examples: Lobster Ravioli (12 sold, 47% margin)… wait, this one is both low popularity AND low profitability. That’s a Dog.
Let’s say you have: Truffle Mushroom Risotto (8 sold, 68% margin)
Strategy: Promote more aggressively (it’s profitable but people don’t order it), improve menu description, train servers to recommend
Examples: Lobster Ravioli (12 sold, 47% margin)
Strategy: Remove from menu or redesign completely
Without real-time food cost data, you can’t do this analysis. You’re making menu decisions based on popularity alone, which keeps unprofitable items on the menu just because people order them.
“We don’t have time to build recipe cards for every menu item.”
Start with your top 20 items (80% of sales). Build those recipe cards first. You’ll see immediate value. Then add 5 more items per month until complete. It’s a one-time investment: build the recipe once, it auto-updates forever.
“Our line cooks don’t follow recipes exactly anyway.”
That’s exactly why you need this. Variance tracking will show you when portions are inconsistent. You’ll see “burger recipe calls for 6oz, but actual usage suggests 7-8oz portions.” Then you can address it through training, portioning tools, or recipe adjustments.
“Ingredient prices change constantly—this will just be noise.”
You set the alert threshold. If you only want to know about changes above 15%, configure it that way. The point isn’t to react to every fluctuation—it’s to catch the significant changes (15-25% spikes) that materially affect profitability.
“We already know which items are profitable.”
Do you? Most restaurants guess based on menu price (“the steak is expensive, so it’s profitable”). But food cost %, labor time, and waste vary dramatically. The $32 steak might have lower contribution margin than the $18 pasta because the steak costs $16 in ingredients and the pasta costs $6. You need data, not gut feel.
Week 1: Build recipe cards for your top 10 menu items (highest sales volume). Calculate current food cost using latest supplier prices.
Week 2: Set up supplier invoice automation. When Sysco/US Foods invoices arrive, parse them and update ingredient costs.
Week 3: Add recipe cost recalculation. When ingredient costs change, recipes auto-update.
Week 4: Set up price spike alerts (increases above 10%). Test with recent invoices.
Month 2: Build remaining recipe cards (all menu items). Add menu profitability dashboard.
Month 3: Add variance tracking (compare theoretical vs actual usage from inventory).
By month 3, you have complete food cost visibility. You see margin by menu item, get alerted when costs spike, and track whether portions are consistent.
You’re no longer flying blind between monthly financials. You’re steering with real-time data.
Running a restaurant on 3-5% net margins means you can’t afford 2% food cost slippage. But that’s exactly what happens when you don’t track food costs in real-time:
Real-time food cost tracking isn’t optional for serious restaurants. It’s the difference between profit and loss.
Build your recipe cards. Connect your supplier invoices. Set up price alerts. Track variance.
Then watch your food cost % drop from 32% to 29% while your profit doubles.
Let’s get you out of gut-feel territory and into data-driven profitability.
Target 28-32% for full-service restaurants, 25-30% for fast-casual, 20-25% for QSR. Fine dining may run higher (32-38%) due to premium ingredients. But the "right" percentage depends on your concept, pricing strategy, and labor costs. What matters more is consistency—if your food cost suddenly jumps from 30% to 34%, that's a $40,000 problem on $1M revenue, regardless of your target percentage.
A 10% increase in ingredient costs typically requires a 3-4% menu price increase to maintain the same profit margin. But most restaurants don't track ingredient costs closely enough to notice gradual increases until quarterly financials show profit erosion. By then, raising prices feels like catching up rather than proactive management.
Not necessarily. Small fluctuations (±3-5%) can often be absorbed or offset through portion adjustments, recipe modifications, or promotional focus on higher-margin items. But sustained increases (10%+ over 3 months) usually require either menu price adjustments or menu redesign. Automation helps you see the trend early enough to choose your strategy rather than being forced into reactive price hikes.
Describe this workflow in plain English. Neudash writes the code, connects the tools involved, runs it on schedule, and repairs routine failures when something changes.