Written by: JJ Tan, Founder, Jelly
Key Takeaways
- Kafoodle is a recipe-first costing platform that calculates cost-per-serving from ingredient quantities and supplier prices, with dynamic price propagation and GP analysis.
- Accuracy depends on manual updates to supplier prices and recipe versions; stale data quickly erodes margins in multi-site or volatile-cost environments.
- Recipe-first models create ongoing admin burdens that scale poorly as kitchens grow, as weekly price updates and per-site recipe maintenance become unsustainable.
- Invoice-first systems like Jelly remove manual entry by scanning every invoice automatically, which delivers live GP margins and price alerts without extra labour.
- Jelly suits growing UK kitchens that want automated, real-time food costing at a flat £129 per month per location.
See How Jelly Automates Food Costing
Step-By-Step: How Kafoodle Food Costing Works
How To Calculate Food Cost Per Item In Kafoodle
Kafoodle follows a standard recipe-first costing model. A chef or manager builds each dish inside the platform by selecting ingredients, specifying quantities, and assigning wastage percentages. The platform then calculates cost-per-portion automatically. The underlying maths works as follows:
- Determine the unit cost of each ingredient: purchase price divided by purchase quantity.
- Apply a yield or wastage percentage to reflect usable weight after trimming or cooking loss.
- Multiply the yield-adjusted unit cost by the quantity used per portion.
- Sum all ingredient costs to produce a total recipe cost.
- Divide total recipe cost by the number of portions to get cost per portion.
- Divide cost per portion by the net (ex-VAT) selling price and multiply by 100 to produce food cost percentage.
A food cost percentage of 28–35% is the industry standard for most UK sit-down restaurants, though the right target varies by format. UK operators must calculate GP on net (ex-VAT) revenue, because including VAT-inclusive figures overstates GP by around 16.7% on a standard-rated item.
Kafoodle supports sub-recipe rollup behaviour. A sauce or base that appears in multiple dishes is costed once and rolled up into each parent recipe, which avoids duplicated ingredient maths. When a supplier price changes, Kafoodle propagates the update across every recipe containing that ingredient, provided the new price has entered the system manually or via supplier purchasing integrations.
How Accurate Kafoodle Food Costing Can Be
Kafoodle stays accurate when the team maintains the data consistently. The platform calculates correctly from the data it holds, and a person must keep that data current.
Three variables drive accuracy in Kafoodle’s model, and they compound each other. First, supplier prices are the most volatile. If a produce supplier increases the price of a line item between deliveries and nobody updates the ingredient record, every recipe using that ingredient is costed on a stale figure. A 4% monthly price drift on a £60,000 food spend costs £2,400 per month, and that loss accumulates silently until someone reconciles the invoices.
Wastage percentages add a second layer of error. Ignoring yield and waste is a common costing mistake. If trimming reduces usable weight by 20%, the actual cost is 25% higher than the purchase price. Recipe versions introduce a third variable. Kafoodle’s recipe versioning keeps costing tied to a specific revision, which supports consistency but requires the team to create and maintain new versions whenever dishes change.
Kafoodle’s documented limitations include limited invoice scanning coverage for high-volume workflows and AP automation depth that is not comparable to dedicated invoice systems. A single-site operator with a stable menu and a disciplined admin process can achieve good accuracy. A multi-site operator with volatile fresh produce costs and a kitchen team that is too busy to update ingredient prices weekly will see accuracy degrade as complexity grows.
A full breakdown of where recipe costing software helps and where it strains is worth reading before committing to any platform.
Talk To Jelly About Live GP Margins
Kafoodle Pricing And Total Cost Of Ownership For UK Operators
Kafoodle subscription pricing can change, so check current rates directly with the vendor, as published figures here are not independently verified. Total cost of ownership for a UK operator extends beyond the subscription line and includes the full cost of keeping the system accurate.
For a recipe-first platform, the ongoing cost drivers are:
- Subscription fee: the monthly or annual licence cost per site or user.
- Onboarding time: the hours required to build the initial recipe library, map ingredients to suppliers, and configure wastage percentages before the system produces useful output.
- Staff training: the time investment for kitchen and management teams to learn the platform and adopt it consistently.
- Ongoing admin: the recurring weekly or monthly effort to update supplier prices, create new recipe versions, and reconcile what the system shows against what invoices actually say.
Recipe costing software saves time versus manual costing by hand, but the admin burden shifts to maintaining the data the software depends on. A growing kitchen with multiple suppliers and volatile fresh produce costs sees that maintenance burden scale with complexity.
An invoice-first model changes this equation. Costs update automatically from scanned invoices rather than manual entry, so the ongoing admin required to keep the system accurate drops to near zero. That reduction in hidden labour cost becomes the most important line in the total cost of ownership calculation.
Start Reducing Food Cost Admin
Common Menu Pricing Methods And Where Kafoodle Fits
Widely used menu pricing methods include:
- Cost-plus pricing: add a target margin to the plate cost. Menu price = ingredient cost ÷ target food cost %.
- Competitive pricing: set prices relative to comparable local operators.
- Value-based pricing: price based on perceived guest value rather than cost alone.
- Contribution-margin pricing: set a minimum cash contribution per cover regardless of food cost percentage.
- Bundle or set-menu pricing: group dishes at a combined price to increase average spend.
- Psychological pricing: use price presentation (for example £11.95 vs £12.00) to influence purchasing behaviour.
- Dynamic or demand-based pricing: adjust prices for peak periods or high-demand slots.
Sources differ on the exact set and number of methods, and many operators rely most on cost-plus pricing. Kafoodle’s RRP suggestion feature calculates a recommended selling price from a target gross profit percentage applied to the recipe’s automatically calculated ingredient cost-in-use. That figure comes from stored supplier ingredient costs and wastage. Most independent UK operators do well by combining cost-plus pricing with a contribution-margin check rather than relying on food cost percentage alone.
A quick worked example using the 30% food cost rule illustrates the maths. A dish with a net ingredient cost of £4.50 priced at a 30% food cost target yields a selling price ex-VAT of £15.00 (£4.50 ÷ 0.30). At 20% VAT, the menu price shown to guests is £18.00. The contribution margin is £10.50 per cover, which is the figure that pays rent, labour, and utilities.
Explore Jelly’s Pricing And Features
Where Kafoodle’s Recipe-First Costing Strains For Growing Kitchens
Recipe-first costing works well when a kitchen has a stable menu, a small supplier base, and a dedicated admin resource to keep ingredient prices current. It strains when any of those conditions change, and for a UK operator expanding from one site to two or five, all three conditions usually change at once.
The specific failure modes for multi-site operators are well documented. A mid-sized restaurant group ran at a 38% food cost for six full weeks before their spreadsheet-based reconciliation process caught it. That delay pushed corrective action back by over a month of compounding loss. This pattern appears because a 3-location operation with 25–30 fresh produce items per site, where market prices move weekly, can generate a significant number of manual updates per week just to keep the system’s expected prices current. When that maintenance burden becomes too heavy, teams start approving exceptions without reviewing them, and the accuracy the system promised disappears in day-to-day practice.
For a growing UK kitchen, the root causes of recipe-first strain are:
- Recipes must be maintained per site, and a dish that changes at one location requires a manual update to stay accurate.
- Supplier price changes must be entered manually before they flow into dish costs, and fresh produce prices can move weekly.
- The kitchen team carries the admin, and chefs are busy cooking rather than updating ingredient records.
- There is no real-time GP visibility between manual update cycles, so margin erosion only becomes visible in arrears.
Invoice-first, real-time food costing addresses these root causes. An invoice-first system starts with the invoice, scanning every line item automatically and updating dish costs the moment a new price arrives.
Jelly is built on this model. Every invoice is captured by photo or email. Jelly automatically scans every line item, including quantity, SKU, price, and tax, without manual data entry. Ingredient costs update with every new invoice, so the GP margin for every dish stays live. A red percentage appears when a dish drops its margin. A green one appears when it improves. The Price Alert feature flags every supplier price increase or decrease, which gives chefs the concrete evidence needed to negotiate better rates or claim credit notes.
Jelly integrates natively with Square, Lightspeed, EPOS Now, and Toast via real-time API. It pulls item-level sales data the moment a transaction completes and combines it with live dish costs. The result is a Sales Mix report that shows which dishes are most popular and most profitable at the same time. Xero accounting integration is live, with Sage coming soon. The flat rate is £129/month per location, with no variable charges per user or feature.
Documented outcomes from Jelly customers include 10–20 hours of admin saved per month, an average 2 percentage point improvement in gross margins in the first three months, and an average 3% food cost reduction in the first three months. Stuart Noble, Head Chef at Cairn Lodge Hotel, reported slashing food costs by 5% in a single month. One operator improved gross profit from 65% to 72% within 12 weeks on approximately £500,000 in revenue.
How to automate real-time food cost tracking explains the invoice-first workflow in detail for operators considering the switch.
Start Saving On Food Costs With Jelly
Verdict: Kafoodle Vs Jelly For UK Food Costing
Kafoodle suits operators who want a structured recipe-first tool with strong allergen and Natasha’s Law compliance and a centralised recipe library with sub-recipe rollup. These operators also accept the ongoing admin required to keep ingredient prices and recipe versions current. A single-site operation with a stable menu and a dedicated person to maintain the data can find Kafoodle a reasonable fit.
Jelly suits growing restaurants, pubs, and boutique hotels with £500k+ in annual revenue that are expanding to 2–5 sites and want food costing to run itself. The invoice-first model means costs update automatically from every delivery. Price alerts surface supplier increases the same week they happen. Live GP margins are visible to both the head chef and the owner, without anyone spending hours on admin. POS integration with Square, Lightspeed, EPOS Now, and Toast means sales data flows in automatically alongside cost data, which produces a complete picture of dish profitability in real time.
The target reader of this article is a UK operator at the tipping point of growth, evaluating whether their current costing approach will scale. For that operator, Jelly is the stronger choice. The P&L case is straightforward. Two percentage points added to gross margins on a £500k revenue base is £10,000 per year. A 3% food cost reduction on a £200k annual food spend is £6,000. Against a flat rate of £129/month per location (£1,548/year), the return is clear.
The best food costing software with inventory tracking for UK operators in 2026 provides a broader market comparison for operators still weighing their options.
Frequently Asked Questions
How Does Jelly Handle Multi-Site Recipe Management?
Jelly links ingredient costs to invoices rather than to individual site recipes, so price updates flow across locations automatically. Central teams can standardise recipes once, then see live GP performance by site without rebuilding the same dish multiple times. This structure keeps multi-site menus aligned while still allowing local tweaks that remain costed in real time.
Can Jelly Work Alongside Existing Kafoodle Setups?
Many operators run Jelly for invoice-first costing and keep Kafoodle for allergen management and compliance. Jelly handles live costs, price alerts, and profitability reporting, while Kafoodle continues to store structured recipes and allergen data. This combined approach lets teams gain automation benefits without disrupting existing compliance workflows.
How Quickly Can A Team See Value From Jelly?
Most operators onboard Jelly within a week and start scanning invoices on day one. Live GP margins appear as soon as the first invoices and recipes are in place, so teams can spot overpriced dishes and supplier increases in the first trading week. Documented case studies show measurable food cost reductions within the first three months.
Conclusion: Why Invoice-First Costing Wins For Growing Kitchens
Manual, recipe-first food costing becomes a burden as UK kitchens grow. Supplier prices move weekly, kitchen teams are too busy to maintain ingredient records, and by the time a margin problem surfaces in a monthly report, weeks of compounding loss have already occurred. For an operator at £500k+ in revenue and expanding to multiple sites, that lag becomes a structural threat to profitability.
An effective solution is invoice-first, automated, and real-time. It scans every invoice line item without manual entry, updates dish costs the moment a new price arrives, alerts the team to supplier price changes before they erode margins, and integrates with POS and accounting software. The full picture of costs, sales, and GP then stays visible in one place without anyone spending 10–20 hours a week on admin.
Jelly delivers this solution. At £129/month per location, onboarding and generating initial value within the first week, and with documented outcomes that include £3,000–£4,000 saved per month for individual operators, Jelly provides a clear path from manual food costing to automated margin control for growing UK restaurants, pubs, and boutique hotels.
Use Jelly’s restaurant food cost calculator guide to benchmark your current margins before the demo.
Schedule Your Jelly Walkthrough
