How recipe-level data drives better commercial decisions for hoteliers

Home » Resources

Hotel food and beverage teams make hundreds of decisions every day that can affect profitability. A supplier increases a price. An ingredient becomes unavailable. A recipe is changed. Portion sizes creep upwards. Waste increases. A dish sells well but delivers a disappointing gross profit.

Individually, these can appear to be relatively small operational issues. Across a busy hotel, multiple outlets or an entire hotel group, their commercial impact can quickly become significant.

The challenge is identifying what is happening early enough to act. This is where accurate recipe-level data becomes particularly valuable.

A recipe connects ingredients, supplier prices, quantities, portions, costs and menu performance. When environmental information is added, it can also show the carbon impact of individual dishes.

Rather than simply recording how a dish should be made, recipe data can therefore become a source of commercial intelligence. The principle is simple: Recipe Data – Insight – Action.

Here we outline five practical examples of how hotels can use that information to make better decisions.

#1. Supplier price increases: understand the impact before taking action

Ingredient prices rarely change in isolation. If the price of butter, beef, olive oil or another frequently used product increases, the impact may extend across multiple dishes, menus and outlets.

Looking only at the supplier price tells you that something has become more expensive. Recipe-level data tells you where that increase matters. This means that hotels can identify:

• which recipes use the affected ingredient
• how much of it each recipe uses
• how the new price changes the cost per portion
• which dishes experience the greatest margin pressure
• how significant the impact could be across sales volumes

That gives teams a much stronger basis for deciding what to do next. For example, teams can now see ingredient price increases, identify affected recipes, calculate the impact on cost and margin and review available options.

The appropriate action might be to negotiate with the supplier, source an alternative product, change an ingredient, review the portion size, adjust the recipe or change the selling price.

Importantly, the same response may not be appropriate for every dish. A small increase in ingredient price might have very little impact on a high-margin dish but could significantly impact another that is already operating close to its target food cost.

Recipe-level visibility helps teams focus attention where action is actually required.

#2. Find out what’s driving poor GP

Knowing that a dish isn’t achieving its target gross profit is useful. Knowing why is much more valuable.

Poor GP can have multiple causes. Ingredient prices may have increased since the recipe was originally costed. Portions may be too large. An expensive ingredient may be contributing disproportionately to the overall cost. The selling price might no longer reflect the cost of producing the dish.

Recipe-level data allows teams to investigate those factors individually. Instead of simply seeing that the dish is underperforming, they can start to see:

• which ingredients account for most of the cost
• whether supplier prices have changed
• what would happen to the margin if the portion changed
• could an alternative ingredient or specification deliver the same quality at a different cost?
• does the selling price need reviewing?

This changes GP reporting from something that identifies a problem into information that helps teams decide how to solve it. It also allows chefs to model potential changes before making them.

Rather than making broad menu price increases or indiscriminately cutting costs, hotels can make targeted adjustments based on the performance of individual dishes.

#3. High waste: identify where the problem starts

Waste affects both profitability and environmental performance, but knowing the total value of food being wasted doesn’t necessarily tell operators how to reduce it.
The more useful question to ask is where that waste is coming from. Connecting recipe, purchasing, stock and waste information can help hotels identify patterns.

• Is an ingredient being purchased for one dish but regularly left unused?
• Are portions consistently larger than the recipe specification?
• Are multiple dishes using similar ingredients efficiently, or is the menu creating unnecessary complexity?
• Is a particular product frequently being purchased but not converted into sales?
• Are certain recipes generating significantly more waste than others?

Once teams understand where waste occurs, they can take more targeted action. That might mean changing order quantities, reviewing portion sizes, adapting recipes, using ingredients across more dishes or simplifying parts of the menu.

The commercial impact can extend beyond the value of the discarded food. Better ingredient utilisation can also improve purchasing efficiency, stock control and kitchen operations.

Recipe-level information, therefore, helps shift waste management from measuring what has already been lost to identifying opportunities to prevent that loss in the first place.

#4. Menu engineering and looking beyond what’s the most popular dish

Traditional menu engineering typically considers what sells and what makes money. Recipe-level intelligence allows hotel teams to build a more complete picture. They can consider sales volume and gross profit alongside ingredient costs, portion performance, waste and environmental impact. This can reveal important differences between apparently successful dishes.

For example, one dish may sell in high volumes but generate a relatively weak margin. Another might achieve a strong margin but rely on expensive ingredients that are vulnerable to supplier price increases. A third might combine strong sales, an attractive margin, efficient ingredient usage and a comparatively lower carbon impact.
Understanding these differences helps operators decide:

• which dishes to promote
• which dishes need reviewing
• where recipe changes could improve margin
• which items could be repositioned on the menu
• which dishes combine strong commercial and environmental performance.

It also gives chefs the ability to evaluate potential changes at recipe level.

An ingredient substitution, a different portion size, or a revised specification can be assessed in terms of its effect on the overall dish rather than being considered purely as an isolated purchasing decision. This creates a more intelligent approach to menu engineering based on how each dish performs overall.

#5. Multi-property benchmarking to understand why the same dish performs differently

Recipe-level data becomes even more valuable for hotel groups. The same dish may appear on menus across several properties but deliver very different results.
Hotel A might achieve its target margin while Hotel B doesn’t. But why is this? The answer could lie in supplier pricing, ingredient specifications, portion sizes, local recipe variations, preparation methods, waste or purchasing practices.

Without consistent recipe-level information, those differences can be difficult to identify. Centralised recipe data creates a common foundation for comparison while still allowing appropriate local variations. Hotel groups can begin to ask:

• Why does this recipe cost more at one property?
• Why is another hotel achieving a stronger margin?
• Are different suppliers or product specifications being used?
• Are portion sizes consistent?
• Is one property generating more waste?
• Is a local variation improving or reducing performance?

The objective isn’t simply to make every hotel operate identically. It is to identify where differences exist, understand why they exist and determine whether successful approaches can be shared across the group.

If one property achieves a better margin, lower waste or lower environmental impact for a comparable dish, that insight can potentially inform decisions elsewhere.
Recipe data therefore becomes a powerful benchmarking tool rather than simply a recipe library.

From operational data to commercial intelligence

These scenarios demonstrate why the value of recipe data extends far beyond recipe management.

Recipes sit at the centre of a connected chain of commercial decisions. Supplier prices affect ingredient costs. Ingredient costs affect recipe costs. Recipe costs affect margins. Portion sizes affect both costs and stock usage. Menu choices affect sales and waste. Ingredient and recipe choices also influence environmental impact. And looking at any one of these measures independently provides only part of the picture.

Connecting them allows hotel teams to ask more commercially useful questions about which recipes are most exposed to supplier price increases, where they are losing margin, where waste is impacting profitability, etc. Then, most importantly, seeing what they can do about it.

Bringing the data together

The quality of those decisions depends on having accurate information that teams can access and use.

Kitchen CUT provides the operational foundation for managing recipe data alongside purchasing, supplier pricing, stock and menu performance. And through its integration with Klimato, carbon-impact information can also be considered at recipe and dish level.

This means chefs, procurement teams and management can assess commercial and environmental factors using connected information rather than working across separate datasets.

A chef reviewing a recipe can understand its cost and margin. Procurement can understand how changes in supplier prices affect recipes. Management can compare performance across menus and properties. And sustainability information can add another dimension to those decisions.

The value isn’t simply having more data. It is being able to turn that data into insight, decisions and action.

Make every recipe a source of commercial insight

Better recipe-level data can help hotel teams identify problems earlier, understand what’s causing them and evaluate the most appropriate response.

From reacting to supplier price increases and improving GP to reducing waste, engineering stronger menus and benchmarking performance across multiple properties, the recipe can become one of the most valuable sources of commercial intelligence within a food and beverage operation.

Kitchen CUT and Klimato help bring operational, commercial and environmental information together, giving hotel teams a clearer picture of how every dish performs.

Learn how F&B data can support profitability and sustainability across your hotel

Download The Profitable Sustainability Guide for Hotels for practical strategies to improve menu performance, reduce waste and make more informed commercial decisions.

Sources

• Champions 12.3 – The Business Case for Reducing Food Loss and Waste: Hotels
• WRAP – Hospitality and Food Service Sector Guidance
• WRAP – Strathmore Hotels case study
• GHG Protocol – Scope 3 Calculation Guidance