Menu Engineering by Season: Reclassify Your Stars

Kitchen Economics

Most restaurants run a menu analysis once, file it somewhere sensible, and never look at it again until a dish starts coming back half-eaten. That is a mistake. Your stars and dogs are not fixed. They shift with the seasons, and if you are not reclassifying them accordingly, you are cooking last winter’s menu in the middle of summer and wondering why covers are down.

Why the BCG Matrix Is Brilliant and Also Slightly Broken

If you have spent any time on the business side of restaurants, you will have encountered the BCG matrix for restaurants. It is the classic menu engineering framework: dishes are sorted into Stars (popular and profitable), Ploughhorses (popular but low-margin), Puzzles (profitable but not ordered much), and Dogs (neither popular nor profitable). Good system. Genuinely useful. But it was not designed with British weather in mind.

The framework assumes a certain stability. It measures what is selling and what margin it carries, and then it tells you what to push, what to reprice, and what to quietly retire. What it does not account for is the fact that a slow-braised shoulder of mutton with root vegetables is a star in January and borderline unsellable by late May. The dish has not changed. The world outside has.

Seasonal dish performance is one of the most underanalysed areas in restaurant menu optimisation, and it costs kitchens real money every year. Not dramatically. Just quietly, in the way a badly seasoned sauce costs you: you notice something is off, but you can never quite put your finger on it.

What Actually Changes With the Seasons

Guest appetite is the obvious one. Not appetite as in hunger, but appetite as in desire. People walk into a restaurant in August wanting something bright, cold-edged, and green. They want to feel like the weather is being respected. They do not want a dish that smells like a November fireplace, however technically accomplished it might be. This is not about trend-chasing. It is about reading the room, which has always been the first job of anyone running a kitchen.

Then there is ingredient cost and quality. A tomato risotto in August, when British tomatoes are actually worth eating, carries a completely different margin and a completely different flavour story than the same dish in February, when you are either importing or apologising. The dish appears identical on the menu. The experience is not. That gap is why seasonal menu analysis matters.

Cover flow changes too. Longer evenings bring different tables: larger groups, later sittings, more sharing. Shorter days bring couples earlier bookings and comfort-led choices. Your puzzles in one season might be your stars in another simply because the people walking through the door are different people, wanting different things.

How to Run a Proper Seasonal Reclassification

This does not require sophisticated software, though it helps. What it requires is honesty, a spreadsheet, and the discipline to do it at least four times a year. Here is how to approach it properly.

Step One: Pull Your Data by Season, Not Just by Month

Most POS systems will give you dish counts by month. That is fine as far as it goes, but it is more useful to group by season and compare like with like: this spring against last spring, not this March against last December. You want to see how a dish performs when the conditions are similar, not just when the calendar ticks over.

Step Two: Recalculate Contribution Margin Using Current Costs

The margin you calculated in October is not the margin you have in April. Ingredient costs shift. Portion costs drift. A dish that was comfortably profitable in autumn may be quietly haemorrhaging in spring if you have not updated your costings. Menu engineering strategies that rely on stale numbers are not strategies at all; they are guesswork with a spreadsheet attached.

Step Three: Reclassify Every Dish Against the New Data

Run the full matrix again. Be ruthless. A dish that was a star in winter might genuinely be a dog by June, not because it is a bad dish but because it no longer belongs in this season. That is not a failure. That is the menu doing its job properly. The failure is leaving it on when it has stopped earning its place.

Step Four: Adjust Placement, Pricing, and Promotion

Menu engineering strategies are most effective when they respond to live data. If a dish has dropped to ‘Puzzle’ status (good margin, low orders), it may simply need better placement on the menu or a brief, honest description that tells guests why it is worth having. If something has become a workhorse (everyone loves it, but you are barely covering costs), that is a pricing conversation, and sooner is better than later.

Step Five: Retire What Is No Longer Seasonal

This is the step most kitchens skip. There is always a reason to keep a dish: the regulars expect it, the prep team has the muscle memory, and the head chef is attached to it. I understand all of that. I have been that head chef. But a dish hanging on past its season is a small drag on everything: on margins, on kitchen focus, and on the guest’s sense that the menu is alive and considered rather than assembled and forgotten.

The Dishes That Genuinely Shift Categories

A few examples worth thinking about, drawn from real kitchens rather than textbooks.

A confit duck leg with lentils and mustard sauce: a star from October to February, a reliable workhorse in March, and borderline dog by May. The dish is the same. The season is not.
A courgette and ricotta tart: irrelevant in winter, a genuine star in July and August when courgettes have actual flavour and the margin is clean. Seasonal menu analysis spots this window. Ignoring it wastes it.
Panna cotta: a puzzle for most of the year (easy to make, good margin, rarely ordered unprompted), but it becomes a star in summer simply because people want something cold, light, and elegant. Placement and a good fruit accompaniment do the work.
Braised short rib: a monster star from November to February. By April it is a dog. By June it will sit in the pass, making everyone uncomfortable. Let it rest until October.

The Broader Point About Menu Planning

Good menu planning is not a one-off event. It is a discipline, like stock rotation or mise en place. Seasonal menu analysis done properly connects your business data to your ingredients, your guests, and the actual world outside the restaurant. It is also, if you will allow me a moment of sentiment, one of the more satisfying parts of running a kitchen. There is something genuinely pleasing about a menu that shifts with the year: that feels of its moment, that uses what is good right now rather than what was good three months ago.

The BCG matrix for restaurants is a tool, not an answer. Used quarterly, updated with honest costings, and applied with a cook’s instinct for what actually tastes good in which season, it is a very good tool indeed. Used once and left to gather dust, it is just another thing you did that year and then forgot about.

Frequently Asked Questions

How often should a restaurant run a seasonal menu analysis?

Four times a year, roughly aligned to the seasons, is the minimum. Some kitchens do it every eight weeks, which is better still. The point is not to make constant radical changes; the point is to catch shifts in cost, demand, and ingredient quality before they damage your margins or your reputation.

Does the BCG matrix work for small independent restaurants?

Absolutely, and possibly more so than for large groups, because every dish counts more when your menu is compact. You do not need specialist software. A spreadsheet with dish sales counts, portion costs, and contribution margins is enough to run the analysis properly. The thinking matters more than the tool.

What is the difference between a dog dish and a dish that just needs better placement?

A genuine dog has low popularity and low margin, and no amount of repositioning or description is likely to rescue it in the current season. A puzzle, which is sometimes misread as a dog, has good margin but low orders and can often be improved with better menu placement, a more compelling description, or a verbal recommendation from front of house. The distinction matters because the solutions are entirely different.

Should you remove a popular dish just because it has become a workhorse?

Not necessarily, but you should address the margin. Workhorses sell well and guests like them, which gives you leverage to adjust pricing gradually or reduce portion cost without damaging quality. Removing a popular dish without good reason is a fast way to annoy your regulars. Repricing it thoughtfully is not.

The best menus are not the most complicated ones. They are the ones that know what time of year it is, what is actually worth cooking right now, and which dishes are genuinely earning their place. That is as true of a two-Michelin-starred kitchen as it is of a forty-cover bistro with one chef on the stove. Run the analysis. Update the numbers. Be honest about what the season is telling you. The menu will thank you for it, and so will the people eating from it.