Written by: JJ Tan, Founder, Jelly | Last updated: 22 June 2026
Key Takeaways for UK Restaurant Menus
- Most UK restaurant operators lack a fast, repeatable way to see which menu items erode margins because manual invoice and POS analysis takes too long.
- A 15-minute weekly scan using actual supplier invoice prices and live POS sales data can surface unprofitable dishes before the next service.
- Contribution margin and the 2×2 menu engineering matrix give clearer decisions than food-cost percentage alone, so you can prioritise repricing, portion changes, or removal.
- Common pitfalls include relying on theoretical recipe costs instead of real invoice prices and reviewing profitability monthly instead of weekly, which allows margin erosion to continue unnoticed.
- Jelly automates the entire workflow and turns the 15-minute scan into daily alerts; see how it works in your own kitchen.
Data You Need and What a Good Result Looks Like
You need two data sources before you run the scan: recent supplier invoices covering the last 7–14 days, and a connected POS system delivering item-level sales for the same period. These sources must overlap in time because contribution margin compares actual selling prices against actual ingredient costs, and any mismatch turns the calculation into guesswork.
The target benchmark for UK full-service operations in 2026 is 65–70% gross profit on food, calculated on VAT-exclusive net revenue. Segment-level targets vary: casual dining sits at 66–70% GP, pub food at 67–72% GP, fine dining at 62–68% GP, and hotel F&B at 64–70% GP. A successful weekly scan highlights every dish trading below the lower bound of its range and produces a clear action list before the next service.
Step 1: Pull the Last 7–14 Days of Sales and Invoice Data
Export item-level sales from the POS for your chosen window. Then gather every supplier invoice received in the same period and line them up against those sales. The critical discipline here is using the actual invoice price for each ingredient, not the theoretical recipe cost entered months ago.
Post-Brexit supply chain disruption has pushed up food costs for many UK operators, so a recipe costed six months ago may already be materially wrong. If invoice prices and recipe costs diverge by more than 2%, update the recipe cost before you trust any margin calculation. This simple check prevents you from making decisions based on outdated numbers.
Troubleshooting: If invoices are missing for any supplier, do not substitute last month's price. Flag the gap and chase the invoice. Using stale prices creates false confidence in dishes that may already be loss-making.
Step 2: Calculate Contribution Margin for Every Menu Item
Contribution margin per dish equals selling price (net of VAT) minus direct food cost. This metric is more decision-useful than food-cost percentage alone because it shows the actual cash a dish generates, not just a ratio. To see the difference, compare two dishes: a 70% GP dish priced at £6 contributes £4.20, while a 60% GP dish priced at £14 contributes £8.40, so the lower-percentage dish wins on cash margin.
Apply the 65–70% GP target as your minimum acceptable threshold. Any dish falling below 65% GP needs immediate review, even if it sells well or feels like a “signature” item.
Troubleshooting: Do not deduct delivery platform commissions from the dine-in contribution margin calculation. Delivery and dine-in menus need separate GP targets. Sushi Revolution uses Jelly to set distinct GP targets for dine-in and delivery menus, accounting for 30% delivery commissions, and achieves actual gross profits 2–3% higher on average as a result.
Step 3: Map Dishes onto the 2×2 Menu Engineering Matrix
Menu engineering classifies every dish by contribution margin and sales volume into four quadrants: Stars (high margin, high popularity), Plowhorses (low margin, high popularity), Puzzles (high margin, low popularity), and Dogs (low margin, low popularity).
Stars deserve protection and prominent placement on the menu. Plowhorses create the most common margin problem because they sell well but do not contribute enough cash. The right response is a subtle price increase, a portion adjustment, or an ingredient swap, not removal, because they drive covers.
Puzzles are candidates for better menu placement or stronger descriptions to lift volume. Dogs are the clearest candidates for removal, and menu space is valuable and persistent Dogs should be cut.
A well-engineered menu can increase gross profit by 10–15% without adding new customers. Treat menu engineering as a continuous recurring process rather than a one-off exercise so that small changes compound over time. The following checklist turns this matrix into a quick weekly scan.
10-Minute Red-Flag Scan Checklist
- GP below 65%: Flag every dish whose contribution margin falls below the 65% floor for its segment. These dishes require action before the next menu cycle.
- Ingredient price movement: Identify any ingredient whose invoice price has increased since the previous scan. Recalculate the GP for every dish containing that ingredient. UK food and non-alcoholic beverage prices rose 4.2% in the 12 months to November 2025, so small shifts add up quickly.
- High-volume, low-margin combination: Cross-reference the sales mix against contribution margin. A dish in the top 20% of sales volume but below the GP floor is a Plowhorse and becomes your highest-priority repricing target.
- Dogs with no redemptive quality: Any dish in the bottom 20% of sales volume and below the GP floor has no clear justification for remaining on the menu. Mark it for removal and reclaim the space.
- Delivery menu GP check: Confirm that every dish offered on delivery platforms carries a GP target that includes the platform commission. If not, the dish is likely loss-making on delivery even if it appears profitable on the dine-in menu.
How Jelly Automates the Margin Scan
Running the scan manually means pulling invoices, updating recipe costs, exporting POS data, and cross-referencing everything in a spreadsheet. Jelly removes every manual step so the same logic runs in the background. Invoices arrive by email or photo and Jelly scans every line item automatically, including quantity, SKU, price, and tax, then updates ingredient costs in real time.
Dish recipes sit inside Jelly and use those scanned ingredients, so the GP for every dish updates the moment a new invoice lands. You see the real margin impact of a price change on the same day, not at month-end.
The Price Alert feature flags every ingredient price movement, up or down, with the supplier name and the exact change. The Flash Report delivers a daily, weekly, or monthly GP view calculated from actual invoice costs and live POS sales. The Sales Mix view, powered by real-time POS integration, shows which dishes are selling and what each one contributes in cash margin, effectively turning the menu engineering matrix into a live dashboard.
Connecting a POS takes approximately five minutes across all four supported systems, Square, EPOS Now, Lightspeed, and Toast, through a straightforward integration flow inside Jelly. These systems work alongside Jelly to deliver the real-time sales data that powers accurate margin tracking. One operator improved gross profit from 65% to 72% within 12 weeks on approximately £500,000 in revenue after connecting their POS and automating invoice capture through Jelly.
Schedule a walkthrough to see the Flash Report, Price Alert, and Sales Mix views running on your own data.
Troubleshooting Common Profitability Mistakes
The most damaging mistake is reviewing menu profitability monthly instead of weekly. Daily P&L reports based on actual sales and costs let managers act during the week rather than reacting to data that is already two weeks old. A supplier price increase that goes undetected for three weeks compounds across every service in that period.
Jelly's Price Alert surfaces the change on the same day the invoice is processed and removes that lag. You can adjust prices, tweak portions, or call the supplier while the impact is still small.
A second common error is costing dishes against theoretical recipe prices instead of actual invoice prices. The gap between theoretical and actual food cost reveals variances from over-portioning, waste, and vendor pricing discrepancies. Jelly closes this gap through the invoice-to-recipe link described earlier, so the theoretical cost and the actual cost converge automatically.
Using Price Alert Data in UK Supplier Negotiations
Price Alert data turns supplier conversations from subjective to evidence-based. When a supplier increases the price of a key ingredient, Jelly flags the exact percentage change and the date it appeared on the invoice. That single data point is enough to open a negotiation and keep the discussion grounded in facts.
The operator can request a credit note for the difference, ask the supplier to match a competitor's price, or switch to an alternative SKU. Stuart Noble, Head Chef at Cairn Lodge Hotel, reduced food costs by 5% in a single month after gaining this level of invoice visibility through Jelly. The same data supports requests for volume discounts when purchasing patterns show consistent spend with a single supplier.
Weekly Cadence and Results You Can Expect
On Monday, run the 10-minute red-flag scan using the previous week's invoice and POS data. Identify all dishes below the GP floor and any ingredient price movements. On Wednesday, implement the priority actions, reprice Plowhorses, adjust portions on flagged dishes, and contact suppliers about price increases highlighted by Price Alert.
Repeat this pattern every week so that small fixes compound. Operators following this cadence consistently see a 1–2 percentage-point gross profit lift within four weeks, which aligns with the three-month average reported earlier. Some operators, including Populu across 16 locations, have lifted GP from 68% to 72%.
Frequently Asked Questions
How often should I review menu profitability?
Weekly review is the minimum effective cadence for UK operators managing live supplier pricing. Monthly reviews leave too large a window for undetected price increases to erode margins across multiple services. A weekly scan using the previous seven days of invoice and POS data takes under 15 minutes when the data is connected and current.
Quarterly deep-dives using 4–12 weeks of sales data work well for structural menu decisions such as removing a category or redesigning a section. These deep-dives complement the weekly operational check rather than replace it.
What is a healthy contribution margin for UK restaurants in 2026?
The standard target for UK full-service restaurants in 2026 sits in the 65–70% GP range established earlier, with segment-specific floors detailed in the Prerequisites section. Beverage GP targets are higher, typically 75–80%. These benchmarks assume ingredient costs come from actual invoice prices, not theoretical recipe costs.
Operators using stale recipe costs will report inflated GP figures that do not reflect real trading performance, which hides problems until cash flow tightens.
Can I still use my existing POS if I adopt Jelly?
Jelly integrates natively with the four POS systems mentioned earlier via real-time API. Each integration delivers item-level sales data the moment a transaction completes. For operators using other POS systems, Jelly continues to add integration partners and expand coverage.
Invoice automation and dish costing remain available without POS connection, so operators can start capturing margin data from invoices immediately while a POS integration is being configured.
How quickly will I see margin improvements?
Most operators see measurable GP improvement within the first four weeks of running a consistent weekly scan. The main early driver is supplier negotiation, because Price Alert data surfaces ingredient price increases that were previously invisible, which enables credit note requests and renegotiations that reduce food cost directly.
Dish repricing and menu rationalisation add further improvement between weeks four and twelve. Jelly users achieve an average 2 percentage-point GP improvement in the first three months, and food costs fall by an average of 3% over the same period.
Conclusion: Turn the 15-Minute Scan into Daily Automation
This playbook gives you a repeatable workflow, from pulling invoice and POS data to calculating contribution margin, mapping dishes onto the engineering matrix, and acting on the red-flag checklist. The method works and produces results within weeks, but manual execution demands time for data collection, spreadsheet maintenance, and cross-referencing that many operators cannot sustain every week.
Jelly removes that constraint by automating invoice capture, live dish costing, and POS integration, then surfacing the outputs, Price Alert, Flash Report, and Sales Mix, as daily notifications instead of weekly tasks. The 15-minute scan becomes a standing alert that needs action, not assembly.
Book a demo and see how Jelly surfaces your margin-killers before they cost you another week of GP.