Restaurant recipe costing: understand ingredients, portions and food cost

Understand the ingredients behind a dish's cost

A dish can be popular with guests while consuming more ingredients than expected. The real portion may be larger than the recipe, a garnish may be missing from the calculation or purchase prices may have changed. Restaurant recipe costing brings these details together. It describes the quantities behind an offer and the ingredient costs associated with them, giving you a practical basis for discussions about menu design, purchasing and portioning.

Bonzumo includes product recipes, base recipes and costing views. These let you consider a dish alongside its components rather than placing a selling price next to an estimated food cost. The value is in the explanation: when a figure changes, you can ask which ingredient or quantity is responsible. A recipe calculation is a model of your kitchen process. The more accurately that model reflects actual preparation, the more useful it becomes for your restaurant's decisions.

Begin with a complete ingredient picture

Choose a frequently sold dish whose preparation is well understood. Describe all its components, including sides, sauces, dressing and garnish. Small quantities can matter across many servings. A calculation that includes only the main ingredient does not describe the plate your guest receives. Use a finished dish as the reference and walk through what is on it with the kitchen team, including prepared components that may be easy to overlook.

Separate standard ingredients from optional additions. Extra cheese sold only on request should not silently be included in every standard portion. Equally, a side that is always served should not be treated as an occasional exception. This distinction supports both costing and a clear sales offer. It also gives staff a better answer when guests ask what is included. Starting with the real plate often exposes gaps more quickly than reviewing an abstract ingredient list alone.

Translate purchase units into recipe quantities

Suppliers may price products in units different from those used in recipes. You buy a pack but use grams, or receive a bottle but serve millilitres. The relationship must be correct before the calculation can be meaningful. Pay special attention when pack sizes change. A lower package price does not necessarily mean a lower cost for the quantity used if the package now contains less product.

For example, an ingredient costing €8 per kilogram contributes €1.20 when a portion uses 150 grams. At 180 grams, the contribution becomes €1.44. The 24-cent difference looks small on one plate but matters across repeated portions. This is a simple quantity example, not a promised Bonzumo saving. It demonstrates why reliable units and actual serving sizes are fundamental to recipe costing before more complex comparisons are attempted.

Maintain recurring preparations as base recipes

Sauces, dressings, stocks and prepared components often appear in several dishes. Describing each use independently can produce inconsistent assumptions. Bonzumo includes base-recipe maintenance with components and costing, allowing a recurring preparation to be considered as a coherent kitchen process. Its quantity can then be discussed sensibly in relation to the dishes that use it.

Yield is especially important. A batch that produces 4.8 litres of usable sauce distributes its cost differently from a batch assumed to produce six litres. Establish the usable output as well as the ingredients entering the preparation. When that output changes, review the dishes built on it. Documenting a base recipe does not remove the kitchen's flexibility; it creates a shared starting point from which deliberate changes can be understood and their consequences considered.

Put food cost in the wider pricing decision

Ingredient cost is useful information, but it is not the complete cost of serving a dish. Labour, energy, premises and other operating costs also matter. Service style changes the context: a carefully finished dish delivered to a table has different requirements from an item quickly handed over at a counter. Use recipe costing as one part of pricing rather than assuming that a single percentage can determine the right selling price.

Make sure the figures share an appropriate basis. Net and gross amounts should not be mixed without recognising the difference, and tax treatment should be agreed with the relevant advisers. You can then examine the ingredient cost associated with a proposed price and the assumptions behind it. A high selling price alone does not establish a strong contribution to the business. The composition of the dish and the work required to serve it must also be considered.

Investigate price changes where they matter

When an ingredient becomes more expensive, review the dishes in which it plays a meaningful role. Its contribution may be small in one recipe and central in another. Increasing every menu price by the same amount can be as imprecise as ignoring the change. Use the maintained quantities to understand the effect and discuss several possible responses rather than moving straight to a blanket adjustment.

You might examine portion composition, supplier pack sizes or an alternative ingredient. Quality remains part of the decision. A cheaper product that harms taste, handling or the guest's expectations is not automatically better. Discuss changes with the kitchen and test the result. Bonzumo can provide the product and costing structure; supplier terms, quality assessment and approval of recipe changes remain real responsibilities within your restaurant.

Compare the calculation with the portion actually served

A maintained recipe is not helpful if the kitchen routinely serves a different quantity. Occasionally compare the recorded amount with an actual plate. This need not be a statement of mistrust. Different ladles, plate sizes or new team members can unintentionally change portions. A shared review helps make the intended serving clear and gives the calculation a realistic foundation.

Distinguish a deliberate larger offer from an accidental variation. If you want to increase the portion, update the description and reconsider the price relationship. If the quantity varies unintentionally, clearer preparation or a suitable portioning tool may help. The aim is not to monitor every kitchen movement. It is to make the dish being sold, the intended quality and the commercial assumptions describe the same offer.

Use recipe information in a menu decision

Imagine two dishes with similar sales volumes. One requires a separate, labour-intensive preparation; the other uses a well-planned base recipe. Ingredient value alone does not explain the complete difference. Consider preparation, service conditions and each dish's role in your concept. A useful menu discussion brings calculated quantities together with the kitchen's experience and feedback from the people serving guests.

Ask specific questions. Which ingredients are purchased for only one dish? Which preparations can sensibly be used in several offers? Which items regularly leave small unusable quantities? Which dishes do guests particularly seek out? The answers may support a clearer menu or more targeted preparation. Such choices depend on several kinds of information. Bonzumo supports an organised data foundation without automatically deciding what belongs in your restaurant concept.

Assign ownership of recipe information

Recipe data remains useful when someone is responsible for maintaining and reviewing changes. The kitchen understands preparation, purchasing knows supplier changes and management owns the offer. Agree a simple handover between these roles. A new pack size, revised batch or different serving quantity should not remain only a spoken update while the calculation continues to use the old assumptions.

Begin with a manageable set of important dishes and review them completely before expanding. Make sure new staff understand the units and base recipes being used. A small collection of maintained recipes can support better decisions than a large catalogue of unclear or outdated entries. Introducing recipe costing should therefore include responsibility for data quality, not just an explanation of the input screen. Decide when the information will be reviewed and what triggers an update.

Questions about recipe costing and food cost

Is the calculated food cost my profit? No. Ingredients represent only one part of the restaurant's costs; other expenses and the price basis also need consideration. Does every ingredient have to be perfect immediately? A defensible comparison requires the significant quantities and costs of the dish to be reliable. Unknown values should be resolved explicitly rather than hidden behind an apparently precise final result.

Can prepared components be included? Bonzumo contains base recipes and associated costing functions. Bring a preparation used in several dishes to the demonstration. Is creating a recipe once enough? Changes in purchasing, yield and portions may require another review. Can the system assess ingredient quality? Taste, handling and suitability remain kitchen decisions. The calculation helps make the financial assumptions surrounding those decisions more visible.

Build a demonstration around a real dish

Bring a frequently sold dish, its complete ingredient list and the corresponding purchase information. Include a base recipe and a typical change, such as a larger portion or a higher ingredient price. Follow the route from quantities to the costing result. Check that you can explain the units and assumptions yourself. A demonstration is most useful when it answers a question you currently have about your menu.

Recipe costing can then become a practical tool: prices are easier to discuss, quantities are clearer and changes can be reviewed more deliberately. Bonzumo supports this work through structured products, recipes and base recipes. Decisions about flavour, the offer and your positioning remain yours. Arrange an inventory and costing demonstration around the plate whose financial basis you would most like to understand, and use that example to define a useful first setup.