As IT Support Manager at StockTake Online, Ayushi Saxena brings eight years of rich experience in the Hospitality and IT sector. Her profound commitment to continuous learning and adaptability plays a pivotal role not only in enhancing technical trends but also in problem-solving capabilities, leadership skills, and people management. Her expertise spans System Implementation, Hospitality Analytical Data Study, Customer-Centric Approach, User Education and Comprehensive Training. All crucial components within the dynamic realm of support management. 

Ayushi Saxena embodies the spirit of growth and resilience, contributing significantly to StockTake Online's success. She has notably increased staff support's product knowledge while simultaneously enhancing troubleshooting skills. Her dedication is evident through designing and implementing training programs for the team. 


StockTake Online Editorial Guidelines 

StockTake Online is revolutionizing the process of discovering reliable and fitting restaurant content in the digital era, rendering it remarkably effortless. We are enhancing the comprehensibility and availability of hospitality information to empower you in making optimal decisions for your hospitality enterprise. 

Our software enables suppliers and operators to collaborate. It is the perfect sales, inventory, and accounting software for restaurants. It helps businesses manage their full-service restaurant catalogues, prices, and delivery services, accounting for food trucks, and bakeries accompanied by other small businesses with the goal to help them save money. StockTake Online’s vision is to help multi-unit operators and independent restaurants maximise their profits.

STO blog hero

Recipe Costing in 2026: How to Keep Dish Margins Accurate When Supplier Prices Change Every Week

Jun 10, 2026 10:09:35 AM / by Team STO


Your Margins are Bleeding (32)

Supplier price increases used to arrive quarterly, sometimes with written notice. In 2026, UK restaurant operators are dealing with price changes that arrive with the delivery van, sometimes mid-week, sometimes without warning, and sometimes on the same invoice as the previous price.

If your recipe cards were last costed when you launched the menu, you are not managing food cost. You are guessing it.

This guide gives you a repeatable, step-by-step process for keeping recipe costing accurate in an environment where ingredient prices move constantly. No theory. Just the method.


Why Recipe Costing Breaks Down When Prices Change Frequently

A recipe card has one job: tell you exactly what a dish costs to produce, right now, at today's prices. When that accuracy lapses, everything built on top of it, your GP percentage, your menu pricing decisions, your variance analysis, becomes unreliable.

The problem is not that operators do not know recipe costing matters. The problem is that most recipe costing workflows were built for stable price environments. You cost the dish at menu launch, set the selling price, and revisit it once a season. That model does not hold when a case of beef mince increases in price three times in eight weeks.

UKHospitality's 2024 Quarterly Tracker reported that food input costs remained the primary margin pressure for UK hospitality operators throughout the year, with ingredient inflation affecting purchasing costs across all venue types regardless of size or segment.

The gap between what your recipe card says a dish costs and what it actually costs today is called recipe variance. Identifying and closing that gap, consistently, is the core skill this article covers.

Takeaway: A recipe card that does not reflect current supplier prices is not a cost management tool. It is a record of what margins used to be.


Step 1: Audit Which Recipes Are Most Exposed to Price Movement

Before building a weekly update process, identify where price movement creates the most risk. Not every recipe carries the same exposure.

Proteins, beef, chicken, fish, shellfish, shift most frequently. Oils, dairy, and certain imported produce are next. Dry goods and ambient products tend to be more stable. Your price-sensitive recipes are the ones where a single high-cost ingredient accounts for more than 35% of the total recipe cost.

Work through your current menu and tag each recipe into one of three categories:

High exposure: The primary ingredient accounts for more than a third of total cost, and that ingredient has changed price at least twice in the last 90 days.

Medium exposure: Multiple ingredients contribute to cost, with no single item dominating, but two or more ingredients are subject to regular price movement.

Low exposure: Primarily dry goods, ambient, or ingredients with stable supply contracts.

Your high-exposure recipes need weekly review. Medium-exposure recipes need fortnightly checks. Low-exposure recipes can be reviewed monthly unless a specific product triggers an alert.

This triage step stops you from treating all 60 recipes on your menu as equally urgent and ensures effort concentrates where the margin risk is highest.

Takeaway: Prioritise your recipe costing review by exposure level, not by which dishes sell the most.


Step 2: Build a Price Update Trigger Into Your Delivery Process

The most reliable way to keep recipe costs current is to update them at the point of delivery, not at the end of the month.

Every delivery creates a data point: what you received, in what quantity, at what price. That data should flow directly into your recipe costs. If it sits in a paper GRN or an email confirmation and nobody acts on it, the information is lost.

Here is what the process looks like in practice:

When a delivery arrives, the person accepting it records the actual unit price against each product. If the price differs from the last recorded price, that triggers a recipe cost review for every recipe using that ingredient.

Immediately after acceptance, any recipe containing the repriced ingredient gets its cost recalculated using the new price. This takes between two and five minutes per recipe if your recipe cards are structured correctly.

Before the next service, the updated recipe cost is reviewed against the current selling price. If the new cost pushes the dish GP below your threshold, the issue is flagged for a menu pricing conversation. It does not get left until month-end.

This approach requires that recipe cards are accessible during the receiving process, that ingredients are linked to the recipes using them, and that whoever receives deliveries has the authority to flag pricing issues immediately.

Consider a two-site gastropub group in the West Midlands that moved to delivery-triggered recipe updates after a steady increase in chicken thigh costs went unrecorded for 11 weeks. By the time the monthly review identified the issue, the GP on four chicken dishes had dropped by approximately 6 percentage points. The fix was structural: recipe cards were linked to the supplier product list, and any invoice price change above 3% now generates a same-day review notification.

Takeaway: The delivery process is the most accurate and timely moment to update recipe costs. Build the trigger there, not at month end.


Step 3: Recalculate Dish Margins Using Current Costs

Once a recipe cost is updated, the next step is to recalculate the gross profit margin for that dish at the current selling price.

The formula is straightforward:

GP percentage = (Selling price excluding VAT minus Recipe cost) divided by Selling price excluding VAT, multiplied by 100

A worked example:

  • Dish selling price: £16.50 (ex-VAT)
  • Recipe cost at launch: £4.80 (29.1% food cost, 70.9% GP)
  • Ingredient price increase: main protein repriced, adding £0.95 to the recipe cost
  • Updated recipe cost: £5.75 (34.8% food cost, 65.2% GP)

That 5.7 percentage point reduction in GP on a dish selling 80 covers per week represents a weekly GP reduction of approximately £44 on that dish alone. Across a menu with eight high-exposure dishes experiencing similar movement, the cumulative impact is significant.

The recalculation step also tells you whether the price change requires a menu pricing response. In most operations, a GP drop of 3 to 4 percentage points on a single dish triggers a review. A drop of 6 or more points typically requires either a menu price increase, a recipe modification, or both.

Use our free restaurant food cost calculator to run this calculation across your current menu without needing to set up a full system first.

Takeaway: Recalculating GP after every ingredient price change gives you the data to make menu pricing decisions before margins have been eroding for weeks.


Step 4: Decide Whether to Adjust Selling Price, Modify the Recipe, or Absorb the Cost

Once you know the updated GP percentage, you have three options. Each has a different set of implications.

Increase the selling price. This restores margin but creates customer price sensitivity, particularly on dishes guests order regularly. In 2026, with menus already adjusted multiple times in many UK restaurants, price increases need to be applied selectively and communicated carefully.

Modify the recipe. Adjusting portion weight, swapping a secondary ingredient, or changing a preparation method can reduce cost without changing the selling price. A salmon fillet dish where the protein is 180g could be reviewed at 160g if the presentation and guest experience support it. Portion changes require updating the recipe card with a new yield weight and recalculating accordingly.

Absorb the cost temporarily. Viable for short-term volatility on ingredients likely to return to a previous price. This requires monitoring the situation closely rather than simply accepting the reduced margin indefinitely.

Most operators use a combination of all three, applied by dish rather than applied uniformly across the menu. The key is that the decision is made deliberately, based on current data, rather than discovered weeks later during a financial review.

For operations managing multiple sites or a large recipe library, StockTake Online's restaurant stock control software connects recipe costs to live delivery pricing, so any invoice price change triggers an automatic recipe cost update across every site using that ingredient.

Takeaway: The response to a recipe cost increase is a business decision, not a passive one. Having current data is what makes the decision possible.


Step 5: Review Theoretical Versus Actual Food Cost Weekly

The final step closes the loop. Once recipe costs are being maintained accurately and updated at the point of delivery, the comparison between theoretical food cost (what recipes say you should have spent) and actual food cost (what stock records say you did spend) becomes a reliable tool for identifying operational issues.

A consistent gap between theoretical and actual food cost, even with up-to-date recipe cards, points to waste, portioning inconsistency, or theft. A gap that appears specifically after a supplier price increase that has not yet been recorded in your system is a reminder to complete step 2.

Run this comparison weekly, by cost category, not just as a single blended percentage. Breaking it down by protein, produce, and dairy separately tells you which area is driving variance, which is significantly more useful than knowing the overall food cost is 2 percentage points above target.

When recipe costing, stock counting, and purchase recording operate as connected processes rather than separate tasks, the weekly review becomes diagnostic rather than just confirmatory. You are not just seeing that a number is off. You are seeing exactly where and why.

Takeaway: Weekly theoretical versus actual review, built on accurate recipe costs, is the operational habit that converts a costing process into active cost control.


Recipe costing in 2026 is not a more complicated version of what it was five years ago. The principles are the same. What has changed is the frequency at which the inputs require updating, and the cost of not updating them.

If you want to start with a practical tool before building out a full process, the free resources on our Free Tools page include a food cost calculator and inventory template you can use immediately, at no cost.

 

 


Frequently Asked Questions

How often should I update my recipe costs in 2026?

For high-exposure recipes  dishes where a volatile ingredient like protein, dairy, or oil accounts for more than a third of the total cost  recipe costs should be updated every time a delivery invoice shows a price change for that ingredient. Medium-exposure recipes warrant fortnightly checks. Waiting for a monthly review means margin erosion happens silently across your highest-risk dishes for weeks before anyone notices.

What is the difference between recipe costing and food cost percentage?

Recipe costing calculates what a single dish costs to produce, based on the ingredients and quantities used. Food cost percentage expresses total ingredient spend as a proportion of total food revenue across a period. Recipe costing feeds into food cost percentage: if your recipe cards are out of date, your theoretical food cost percentage will be wrong, and comparing it against your actual food cost becomes meaningless. Accurate recipe costing is the foundation that makes food cost percentage a useful management number.

How do I update recipe costs when I have dozens of dishes on the menu?

Start by triaging your menu into high, medium, and low price-exposure categories. High-exposure recipes, those dominated by a single volatile ingredient, get updated at the point of delivery. Medium-exposure recipes get fortnightly attention. Low-exposure recipes can be reviewed monthly. This approach concentrates effort where margin risk is highest rather than treating all recipes as equally urgent.

What should I do if an ingredient price increase makes a dish unprofitable?

You have three options: increase the selling price, modify the recipe to reduce cost, or absorb the margin reduction temporarily while monitoring whether the price reverts. The right response depends on the dish's sales volume, its strategic importance to the menu, and how long the price increase is likely to hold. The critical thing is to make the decision deliberately once you have the updated cost data, rather than discovering the problem at month-end review.

Can a spreadsheet keep recipe costs up to date when prices change frequently?

A well-maintained spreadsheet can work for a small menu with stable suppliers. The limitation is manual input: someone needs to update every affected recipe card every time a delivery price changes, and the system relies on whoever receives deliveries to record the change accurately and promptly. As menu size or site count grows, the manual dependency becomes the weak point. Connected systems that link delivery invoices directly to recipe costs remove the reliance on a manual update step.

What is theoretical food cost and why does it matter for recipe costing?

Theoretical food cost is calculated from your recipes and your EPOS sales data: it is what your kitchen should have spent to produce everything sold in a given period. Actual food cost comes from your stock counts and purchase records: it is what you did spend. The gap between them is your variance, and it reveals where operational issues exist. Accurate recipe costing is what makes the theoretical figure meaningful. If your recipe cards do not reflect current ingredient prices, the theoretical figure is wrong before you even start the comparison.

How does AI invoice scanning help with recipe costing?

AI invoice scanning reads incoming supplier invoices, extracts item names, quantities, and prices, and updates your product cost records automatically. When this is connected to your recipe management system, any price change on a delivery automatically flags the recipes using that ingredient for review, or updates the recipe cost directly. This removes the manual step of cross-referencing invoices against recipe cards, which is the point in the process most likely to be skipped when kitchens are busy.

Tags: Best Recipe Management Software in the UK, Cloud Kitchen in UK, AI in restaurant supply chain, AI Invoice Scanning, AI inventory management UK Europe

Team STO

Written by Team STO

Recent Posts