Prices on the menu card were set by looking at competitors, and the chef adjusts portions by eye. At the end of the month, the food cost ratio is higher than expected, and no one knows which plate is losing money.
Pricing without recipe costing is a guessing game; a price that looks right might subsidize the wrong product. Talking about profit before clarifying the cost per plate is misleading.
In this article, we explained step-by-step portion standards, ingredient costs, waste allowances, menu pricing, and update routines.
Table of Contents
Why recipe costing?
Recipe cost is the total calculated using the current purchase price of every ingredient used in a plate. Without this figure, the gross profit margin cannot be known on a product basis.
Popular but unprofitable products melt away profits while appearing to have high turnover. Meanwhile, quiet, profitable products may remain in the background on the menu.
As purchasing prices change, the old menu price becomes obsolete. Current recipe costing enables timely decisions on price increases or grammage adjustments.
We summarized the general framework of restaurant operations in the restaurant management system article.
Recipe costing also feeds inventory planning; theoretical consumption is derived from sales volume. If this link is not established, inventory count discrepancies cannot be interpreted.
Portion standard
A portion is the recipe's counterpart in the field; if the grammage is not written down, the cost is not written down either. Serving the same dish differently across two shifts ruins the calculation.
Net weight, unit, and preparation state must be defined for each item. Raw weight and cooked weight must not be confused.
Modifiers and extra options should be linked to a separate recipe line. We covered the topic in the modifier management article.
Ladles, scales, and standard plate sizes enforce the standard in practice. Training notes alone are not enough.
Portion changes are a menu engineering decision; temporary generosity looks like waste. Changes must be approved and dated.
Material cost
Material cost is the product of the unit price in the inventory card and the quantity in the recipe. The source purchase price must be clear.
The last purchase price is fast; the weighted average is more balanced for volatile products. The business must define in writing which method to choose.
Semi-finished products and sauces must also have their own recipes. Writing “sauce” in a single line hides the cost.
We explained the bill of materials logic in the bill of materials (BOM) article.
Unit conversions are critical; mixing up kilograms and grams skews the cost a hundredfold. Inventory units and recipe units must be mapped.
Waste allowance
Preparation waste is added to the recipe as a percentage or net loss depending on the product group. Without this allowance, theoretical cost remains below actual consumption.
If the waste allowance is exaggerated, the price inflates; if ignored, profit melts away. Ratios based on actual measurement must be used.
Waste tracking and recipe allowances feed each other; measured losses update the standard. We expanded on this in the kitchen waste tracking article.
Variable losses such as returns and spoilage should not be written off as constant allowances. These are operational issues and should not be permanently embedded in the menu price.
Allowance rates should be reviewed periodically; when supply quality changes, losses change too. Old ratios do not reflect the new reality.
Menu price
The menu price is built on top of the recipe cost with target gross profit and VAT layers. Competitor prices can only serve as an upper limit or a reference.
Target cost ratios can vary by product; signature dishes and side items do not have to carry the same margin. Flexible margins balance the menu.
Channel difference also affects the price; delivery and dine-in can leave different net margins for the same dish. Channel management article explains this distinction.
Price list versions should be kept with dates; which price was valid on which date must be tracked. We covered the topic in the price list management article.
Psychological rounding should not make you forget the cost; the rounded price must still protect the target margin. Aesthetics should not compromise profit.
Update routine
When the purchase price changes, the recipe cost must be automatically or quickly recalculated. Manual Excel updates cause delays and are forgotten.
Define a critical threshold; when costs increase by a certain percentage, a decision on price or portion size should be triggered. Without a threshold, every minor fluctuation shakes the menu.
Recipe alternatives should be kept ready for seasonal products. When supply is cut, instead of panicking and deleting the menu, a backup item is activated.
Update authorization must be restricted; letting everyone change prices creates chaos. We covered authorization in the user permissions article.
Change history must be stored; past records are necessary for cost analysis and auditing. The question "Since when has this price been in effect?" should not remain unanswered.
Comparison and engineering
Menu engineering reads sales volume and gross profit together. High-volume low-margin products and low-volume high-margin products require different actions.
The difference between theoretical cost and actual consumption indicates portion deviation or unrecorded waste. If the gap is growing, fix the operations, not the recipe.
Grouping products by cost band speeds up decision-making. Products in the same band offer shared improvement opportunities.
Portion consistency can be monitored via the kitchen display system; when the order rhythm breaks, portioning also breaks. KDS article explains this connection.
Comparisons should be made weekly; a monthly view closes the window of opportunity. Early intervention protects menu reputation.
Reporting
Product-based cost and margin reports are the foundational document for menu decisions. Total food cost percentage alone does not provide sufficient direction.
Theoretical stock consumption must be derived from sales and compared with physical counts. The variance list must turn into an action list.
Recipe compliance and cost variance should be added to the manager's KPI set. We discussed the topic in the daily KPI set article.
An abnormal cost warning must be visible at the shift closing. A problem that spills over into the next day grows larger.
The report should be reviewed together by the chef, procurement, and the business owner. One-sided interpretation remains incomplete.
Together with your existing system,
EQLEM is a solution platform; it does not replace your existing ERP system. Recipe and portion operations can stay on the platform, while financial records remain in the existing system.
If stock cards reside on the Mikro or Logo side, the platform matches and uses them. We discussed opening duplicate cards in this article.
Sales and consumption summaries are transferred to the existing system, allowing cost accounting to proceed uninterrupted. Field speed and financial order are preserved together.
The connection to the local server is established with an on-prem component; no external ports are opened. We explained the architecture in the on-prem agent article.
The web side is mature for restaurant scenarios; mobile may remain partial in certain flows. Cash register (ÖKC) firmware is out of scope.
Points to consider
An Excel recipe loses its relevance in a short time; calculations must depend on live prices and sales. A static table creates an illusion of security.
Calculating costs without keeping portions in writing is a waste of time. Lock down the standard first, then talk about the price.
Forcing every product into the same margin band ruins the menu. Set targets based on product roles.
Recipe costs cannot be verified without a stock count; theoretical and actual diverge. Stock control see the article.
The scope must be verified according to your business. Instead of a generic model, your menu and supply structure should be evaluated.
Frequently asked questions
How often should recipe costs be updated?
Whenever purchase prices change. Weekly checks on critical items are a good practice.
Is a waste allowance mandatory?
Yes, for items with prep loss; a measurement-based rate should be used. Otherwise, the theoretical cost will be incomplete.
Do I need to abandon my current ERP?
No. EQLEM works alongside your existing system and does not interfere with your financial record-keeping.
How are modifiers factored into the cost?
They are linked via separate recipe lines or sub-recipes. Baking them into a single price hides the margin.
Setting a menu price without knowing the cost per plate is leaving profit to chance. Recipe costing eliminates this uncertainty on a product-by-product basis.
Costs calculated without portion standards remain only on paper. Lock down the grammage, then discuss price and margin.
Base waste allowances on actual measurements; exaggerating inflates prices, while ignoring them ruins profits. Waste tracking and recipes must support each other.
Tie price updates to thresholds and authorizations so minor fluctuations don't shake the menu. Keeping a history makes auditing easier.
It is possible to speed up the recipe and portioning side while preserving your existing accounting setup. Clarify the scope based on your own menu.
By consulting with the EQLEM team, you can clarify the scope of your recipe costing and menu pricing.