A busy service does not always mean a menu is earning well. For independent restaurants, bars, cafes and boutique hotels in London, menu engineering helps you see which dishes contribute most, which need attention and which may no longer deserve their place.
## Menu engineering basics: find the dishes that earn and the ones that do not
Menu engineering compares how often an item sells with what it contributes after its ingredient cost. It gives you a starting point for decisions, not an automatic instruction to remove anything unpopular.
Use it alongside kitchen workload, waste, guest needs and the role each item plays. A modest seller might support a dietary requirement or complete a hotel breakfast offer. A popular dish might create prep bottlenecks that limit the whole service.
## Start with a manageable group
Choose one section, such as main courses, sandwiches, cocktails or breakfast dishes. Compare items that guests choose between, rather than judging a side dish against a main course.
Pick a review period that reflects normal trading. Separate breakfast from dinner where buying patterns differ. Note unusual circumstances, including private events, temporary closures and unavailable ingredients.
Before you begin, check that:
- Each item has a clear, consistent name in the POS. - Sales are recorded against the correct item. - Modifiers, extras and substitutions are captured. - Refunds, discounts and complimentary items are identifiable. - You know when an item was unavailable.
Low sales mean little if a dish was missing for much of the review period.
## Cost what actually leaves the kitchen
Build a recipe card for every item in your chosen group. Include garnishes, sauces, cooking ingredients, accompaniments and any packaging supplied with it. For drinks, include mixers and finishing touches.
Use current supplier costs and realistic usable yields. Buying weight is not always serving weight. Trimming, cooking and draining can change how many portions an ingredient produces.
Check recipes against practice:
- Weigh portions during normal preparation. - Confirm serving utensils deliver the intended amount. - Record batch yields and portion sizes. - Include preparation losses in the costing. - Update recipes when ingredients or suppliers change.
Keep avoidable spoilage and unsold batches visible in waste records. Do not assume a recipe costing captures every loss in the venue.
## Work out contribution, not just food cost
For each item, subtract its portion ingredient cost from its net selling revenue. Use a consistent tax basis for both figures. The result is its ingredient contribution per sale.
This is not net profit. It still has to help cover labour, energy, rent and other operating costs. Where an item has specific additional costs, such as takeaway packaging, include these consistently or show them separately.
Then multiply contribution per sale by the number sold. This shows total contribution over the review period.
Look at both measures. A dish with a strong contribution per sale may contribute little overall if rarely ordered. A frequent seller can generate useful total contribution even when its return per serving is modest.
## Sort dishes into four practical groups
Compare popularity and contribution within your chosen menu section. Set consistent benchmarks using that section’s results, and keep the same method for later reviews.
### Popular with strong contribution
Protect these dishes. Keep quality, availability and portion control consistent. Give them clear menu descriptions and make sure staff can explain them confidently.
Avoid unnecessary changes to something guests already value.
### Popular with weaker contribution
Investigate the recipe and serving process before making changes. Check portion drift, excessive garnishes, waste and supplier substitutions.
Consider whether a simpler accompaniment or revised recipe could improve contribution without weakening the dish. Review the selling amount if the current offer no longer supports its costs.
### Less popular with strong contribution
Check whether guests understand and notice the item. Its name, description, position or availability may be holding it back.
Give staff a straightforward explanation of its ingredients and appeal. Test a clearer description or more visible placement before changing the recipe.
### Less popular with weaker contribution
These deserve close attention. Ask whether the item serves a clear guest need, uses ingredients already stocked or supports another part of the offer.
If it adds complexity without a useful role, consider replacing or removing it. Check the effect on menu variety and dietary choices first.
## Check the operational reality
Review your findings with kitchen, bar and floor teams. Sales records cannot explain every problem.
Ask:
- Does the item slow a busy station? - Does it need ingredients used nowhere else? - Does it create frequent leftovers or spoilage? - Can staff prepare it consistently across shifts? - Do guests regularly request changes or leave components uneaten? - Would removing it leave an important gap?
For boutique hotels, consider breakfast, room service and other outlets separately before deciding whether shared ingredients or preparation make an item worth keeping.
## Test changes and repeat
Change a small number of things at a time. Record what changed and when, then compare a similar trading period. Check availability, guest feedback, waste and total contribution, not just sales volume.
Make the review part of routine management:
- Refresh supplier costs and recipe cards. - Investigate differences between expected and actual stock use. - Brief staff before menu changes go live. - Align ordering with the revised menu. - Revisit decisions when trading patterns change.
## Doing this in HBB Nexus
Use a walkthrough of HBB Nexus to map this process in one system, covering POS sales, menu costing, stock checks, staff workflows and supplier ordering. Bring a sample menu and recipe cards to check the fit for your venue, then [see pricing](/pricing) or [book a 15-minute demo](/demo).