Written by: JJ Tan, Founder, Jelly
Key Takeaways for Busy Pub Teams
- Menu engineering places every dish into one of four quadrants based on contribution margin and popularity. This approach supports targeted action on Stars, Plowhorses, Puzzles, and Dogs instead of treating the menu as a static list.
- Accurate, current data is essential. You need item-level EPOS sales for at least four weeks and live line-item invoice costs for every ingredient before any analysis starts.
- The seven-step workflow runs from data collection and quadrant classification through layout changes, pricing psychology, and live price alerts, then finishes with a scheduled quarterly review that keeps margins protected.
- Common pitfalls such as chef favourites, over-long menus, and spreadsheet drift can undermine the whole process. Shorter menus, objective data, and automated alerts reduce these risks.
- Jelly automates invoice scanning and EPOS integration so UK pubs can run the full workflow in under an hour each month. See how it protects your margins in a live demo.
Before You Begin: Data You Need in Place
Two data inputs must be ready before any analysis starts. First, item-level EPOS sales data covering a minimum of four weeks, ideally eight to twelve, pulled by dish rather than by category. Second, line-item invoice costs for every ingredient that reflect this week's supplier prices.
UK pub menu engineering uses sales volume, food costs, and selling prices to assess popularity and profitability. Without live invoice data, every margin figure is already out of date before the analysis begins.
Jelly connects to your EPOS via real-time API and pulls item-level sales the moment a transaction completes. Invoices arrive by email or photo and are scanned line by line automatically, so no spreadsheet is required. See how your data feeds the workflow in a live walkthrough.
Step 1 – Pull Your Data Cleanly
Objective: Assemble a clean, complete dataset before any calculation begins.
Action: Export item-level sales from your EPOS for the chosen window of at least four weeks. Pull every supplier invoice for the same period and confirm that ingredient prices match the most recent delivery, not last month's.
Inputs: EPOS sales export and scanned or digitised invoices.
Success criteria: Every dish on the menu has a units-sold figure and a current food cost. This standard means no blanks and no estimated prices anywhere in the dataset.
Step 2 – Calculate Popularity and Contribution Margin
Objective: Produce the two numbers that determine every dish's quadrant.
Action: For each dish, calculate contribution margin as selling price net of VAT minus food cost. Calculate popularity as that dish's units sold divided by total units sold in its category, expressed as a percentage. Gross profit per dish equals selling price net of VAT minus actual food cost, and mix percentage equals portions sold of an item divided by total portions sold in the category.
Inputs: Selling prices, food costs, units sold per dish, and total category units sold.
Success criteria: Every dish has a contribution margin figure and a popularity percentage. Set the high-margin threshold at or above the category average contribution margin. Set the high-popularity threshold at or above the category average mix percentage.
To make the classification actionable, structure your data so each dish's quadrant assignment sits clearly beside its core metrics. A suggested classification table for a six-item mains section might track dish name, selling price (ex-VAT), food cost, contribution margin, units sold, mix percentage, and quadrant. Keep it to four columns maximum per view by splitting into two views if needed.
Step 3 – Label Every Dish on the Four-Quadrant Matrix
Objective: Give every dish a label that dictates the action taken in later steps.
Action: Place each dish into its quadrant using the thresholds calculated in Step 2. Run this analysis per menu category, with mains separate from starters and starters separate from desserts. Analyse beverage items in a separate matrix because their contribution margins are typically higher than food and can distort food-item classifications if combined.
Inputs: Contribution margin and popularity figures from Step 2.
Success criteria: Every dish carries a quadrant label. Typical UK pub examples include Sunday roast as a Plowhorse with high popularity and margins compressed by beef and energy costs. Fish and chips often sit as a Plowhorse that drives volume and footfall at thinner margins. Steak and ale pie may appear as a Star or a Puzzle depending on your sales mix and recipe cost.
Step 4 – Reshape Menu Layout to Highlight Winners
Objective: Use physical menu real estate to steer guests toward Stars and Puzzles.
Action: Move Stars and repositioned Puzzles to the top-right area or centre of each menu section so guests see them first. Items in these prominent positions usually receive more orders than dishes in less visible zones. Remove right-aligned price columns entirely and place prices directly after descriptions to reduce price scanning.
Increase whitespace around key dishes because menus with more whitespace can raise perceived value and encourage guests to read more thoroughly. These layout choices work together to draw attention to high-margin dishes, reduce pure price comparison, and support higher average contribution per cover.
Inputs: Quadrant classifications from Step 3 and the current menu layout file.
Success criteria: Stars occupy prime positions. Dogs are removed or moved to the bottom of the section. No vertical price column appears anywhere on the menu.
Step 5 – Adjust Pricing and Descriptions for Higher Spend
Objective: Lift average contribution margin per cover through pricing psychology and language.
Action: Apply three tactics simultaneously. Each tactic addresses a different psychological barrier to higher spending: cost friction, value perception, and desire intensity.
- Remove the currency sign. Menu items listed without a dollar or euro sign produce about 8% higher average checks by reducing perceived cost friction.
- Anchor with a premium item. Place one premium main at the top of each section, priced 40–60% above the category average. This price anchor makes mid-range options feel better value and can increase average transaction value.
- Rewrite Puzzle descriptions with sensory language. Menu descriptions that combine origin, preparation method, and sensory detail convert more orders than generic descriptions. For example, “Slow-braised British beef and ale pie, buttered short-crust pastry, creamed potatoes” consistently outperforms “Steak and Ale Pie.”
Inputs: Current prices, quadrant classifications, and menu copy.
Success criteria: Stars and Puzzles carry refreshed descriptions. Plowhorse prices such as Sunday roast and fish and chips are tested with a 5–10% uplift or a paid side upgrade rather than removal. Regular menu engineering supports steady improvements in food gross profit.
Step 6 – Protect Margins with Live Invoice Alerts
Objective: Stop supplier price creep from silently eroding the margins established in Steps 2 to 5.
Action: Configure real-time price alerts so that every invoice line item is compared against the previous price the moment it is scanned. When a supplier raises the cost of beef, rapeseed oil, or cod, the alert fires in the same week, not at month-end when the damage has already occurred. Jelly's Price Changes feature provides real-time insights into ingredient price fluctuations and supports pricing decisions, ingredient substitutions, supplier switches, or better deals.
Inputs: A live invoice feed and previous ingredient prices stored in the system.
Success criteria: Any ingredient price movement above a defined threshold triggers an alert within 24 hours of invoice receipt. The head chef or operations manager reviews and acts by repricing, substituting, or negotiating before the next service. Before using Jelly, Chef Murat Kilic of Amber relied on tedious manual costing and pricing with spreadsheets. After switching, Amber consistently saves £3,000–£4,000 per month.
Watch the Price Alert feature in action in a live pub environment.
Step 7 – Lock In a Regular Review Cycle
Objective: Turn menu engineering from a one-off project into a repeatable monthly habit.
Action: Before closing this cycle, set the date for the next full classification run. Menu engineering reviews should sit on a regular calendar cadence, quarterly at minimum, to support ongoing improvement rather than one-time changes. A practical quarterly-review checklist covers four items.
- Refresh all ingredient costs from current invoices before recalculating.
- Pull fresh EPOS data for the preceding 4–12 weeks and exclude anomalous weeks.
- Re-run the quadrant matrix per category and compare results to the prior quarter.
- Assign one named owner to each action such as reprice, reposition, retire, or promote, with a deadline before the next service period.
Inputs: A calendar invite and prior-quarter quadrant classifications for comparison.
Success criteria: The next review date sits in the diary. Actions from this cycle have named owners and clear deadlines. This structure connects your ongoing price monitoring in Step 6 with periodic full reviews that reset the whole menu.
Common Pub Menu Engineering Mistakes to Avoid
Three errors account for most failed attempts at menu engineering in UK pubs, often surfacing during the first or second run of the workflow.
- Chef favourites distort the matrix. Dishes kept for sentimental or creative reasons rather than margin performance inflate the Dog quadrant. Worse, they consume kitchen capacity such as prep time, shelf space, and ingredient stock that could otherwise support higher volumes of your Stars.
- Over-long menus dilute every quadrant. A menu with 40 mains spreads covers so thinly that nothing reaches the popularity threshold to qualify as a Star. Shorter menus concentrate volume and make the matrix easier to act on during each quarterly review.
- Spreadsheet drift invalidates the data. Failing to analyse which dishes actually make money leaves food revenue underperforming. When ingredient prices move weekly and the spreadsheet is updated monthly or not at all, every classification is wrong before the ink dries.
Measurement Cadence for Lasting Results
Sustaining the gains from menu engineering requires a layered review rhythm rather than a single annual exercise.
- Weekly: Spot-check the top three dishes by sales volume for margin movement. If a supplier price change arrives mid-week, recalculate the affected dish's food cost immediately rather than waiting for the next scheduled check.
- Monthly: Re-run contribution margin and popularity figures for every dish. Identify any quadrant shifts since the prior month and assign actions.
- Quarterly: Complete a full layout and pricing refresh. Compare quadrant classifications quarter on quarter and update descriptions for any Puzzles that have been repositioned but not yet converted to Stars.
Frequently Asked Questions
How often should a UK pub run a full menu engineering review?
A full quadrant analysis that covers every dish across all menu categories should run at least quarterly. This cadence aligns with seasonal menu changes and gives four comparable data points per year. Between full reviews, recalculate ingredient costs when a supplier invoice arrives with a price change and check the top three dishes by sales volume weekly. Monthly management meetings should include a short review of any quadrant shifts and the actions assigned to address them.
Who should own the menu engineering process in a pub?
Shared ownership between the head chef and the operations or finance manager works best. The head chef brings recipe knowledge, portion control insight, and supplier relationships. The operations or finance manager brings margin targets, cash flow context, and authority to approve pricing changes.
In practice, the head chef runs the data pull and classification. The operations manager reviews the output and signs off on layout and pricing decisions. Both need access to the same live data, so a single platform that connects invoices and POS data removes the friction that often causes this handoff to fail.
Can menu engineering be rolled out across multiple pub sites?
Multi-site rollout delivers the strongest payback. The workflow stays identical at every site, but the quadrant classifications differ because customer mix, local competition, and supplier pricing vary by location. The most practical approach is to run the seven-step workflow at each site independently, then compare Stars and Dogs across sites to spot dishes that underperform at one location but act as Stars at another.
Jelly supports multi-site operations at a flat rate of £129 per site per month. Each site's invoice and POS data remains separate while staying visible to the operations manager from a central login.
What data sources does menu engineering actually require?
As noted in the workflow setup, you need item-level EPOS data for at least four weeks, current supplier invoices, and each dish's menu category. Historical or estimated costs are not sufficient because ingredient prices in the UK moved significantly through 2025 and into 2026. A cost figure more than 30 days old can misclassify a dish entirely. Jelly's automated invoice scanning updates food costs with every delivery so the data feeding the workflow stays current.
How long does the seven-step workflow take each month?
With manual spreadsheets, pulling data, calculating margins, and updating classifications typically takes several hours per site each month, even when the spreadsheet is already set up and ingredient prices have been entered manually. With Jelly, invoice costs update automatically and POS sales data flows in real time, reducing the active analysis time per site to under an hour.
The time saving compounds because the same automated data feeds three tasks that were previously separate: invoice management, dish costing, and margin reporting. Jelly users report that the combined saving removes several hours of manual work each month.
Turn the Workflow into a Monthly Habit with Jelly
The seven steps above are not complicated in theory. In practice, however, most UK pubs never complete them consistently because the data preparation, including pulling invoices, updating costs, and exporting EPOS figures, takes longer than the analysis itself. Jelly removes that barrier by automating invoice scanning, connecting directly to your EPOS, and surfacing live dish margins and sales mix in a single dashboard.
The result is a workflow that takes under an hour per month rather than a full day. Price alerts protect margins between reviews, and a Flash Report shows gross profit daily instead of at month-end. At £129 per site per month, Jelly replaces the spreadsheet, the manual cost checks, and the delayed accountant reports with one flat-rate tool built for growing UK pubs and restaurants.
See the full workflow running on your own menu data.