Seasonal Sourcing Without Rewriting Your Menu

TL;DR: Seasonal sourcing only causes chaos when menus are treated as fixed documents. Build ingredient substitutes into your original brief and manage availability as a normal part of kitchen planning, not a crisis.

Seasonal sourcing is not a marketing concept. It is the thing that keeps your food honest, and if you have never had a supplier ring you on a Tuesday morning to say the courgettes are finished and there will be no more until August, you have not been doing this long enough.

The panic that follows that phone call is entirely avoidable. Not by abandoning your menu, not by sourcing from four different wholesalers at once in some frantic hedge against disappointment, but by building a kitchen culture and a purchasing approach that treats ingredient availability as a feature of the season rather than a failure of logistics.

Why Seasonal Sourcing Catches People Out

Most menus are written optimistically. A chef has a great idea in March, prices it up, prints it, and then discovers in November that the tomatoes they specified are watery, expensive, and arriving on a lorry from somewhere that does not bear thinking about. The menu stays. The dish suffers. The customers notice, even if they cannot say why.

The problem is not seasonality itself. The problem is treating a seasonal menu as a fixed document rather than a living framework. A dish does not have to change when a key ingredient does. Sometimes it just needs a properly considered substitute baked into the original brief.

I spent years running a kitchen where the menu changed every few weeks and I thought that was the answer. It is exhausting, it confuses regulars, and it means your team never quite masters anything. The better answer is writing dishes with enough flexibility that a swap feels natural rather than desperate.

Building Dishes Around Ingredient Availability

The most resilient dishes are not the ones with the fewest ingredients. They are the ones built around a technique or a flavour profile rather than a single non-negotiable component. A braise is a braise whether the root vegetables are parsnip or celeriac. A salad dressed with a good vinaigrette and something bitter holds up whether that bitterness comes from chicory or watercress or frisée.

When you write a dish, ask yourself what the actual point of it is. If the point is sweetness and earthiness and something that will hold a rich sauce, then beetroot, carrots, and squash are all plausible vehicles depending on the month. Write the dish around the idea, not the specific ingredient, and you give yourself room to move.

This is not dumbing things down. It is knowing your craft well enough to understand which substitutions hold and which do not. Swapping spinach for kale is not the same as swapping sea bass for pollock (though pollock is a better fish than its reputation suggests, and I will not apologise for saying so).

Menu Engineering and the Art of the Soft Swap

Menu engineering, at its most useful, is the practice of thinking about which dishes carry the menu and which ones are there to support them. The dishes that carry the menu, the ones people come back for, the ones that define the place, should be built from ingredients that are either available year-round or that have obvious, well-tested substitutes. Everything else has more freedom to shift.

The ‘soft swap’ is worth understanding properly. It means identifying, in advance, what you would use if your first-choice ingredient became unavailable or unacceptably priced. Not as a crisis plan but as a standing instruction. Your asparagus dish in May becomes a mangetout dish in July. Same dressing, same protein, same structural logic. New menu description, printed that morning.

This works if you have done the tasting ahead of time. It does not work if you decide on the night that broad beans will be fine and then serve something that tastes like an afterthought. The substitute has to be tested properly, costed properly, and briefed to the whole team before it goes on the pass.

Talking to Your Suppliers Before Things Go Wrong

A good supplier relationship means you know what is coming before it arrives, not just what failed to arrive. Ask your suppliers at the start of each season what they expect to be difficult. Ask what they are growing in abundance. Ask what is coming early or late because of the weather. They know. They are usually delighted to be asked rather than just shouted at.

If you work with a farm directly, even better. The conversation about a courgette glut in August is a much more interesting one when you are talking to the person who grew them rather than a rep with a spreadsheet. You might end up with courgette flowers on the menu, which is no bad thing, or courgette preserved four ways for the winter, which is considerably better than nothing.

Practical Steps for Managing Supplier Fluctuations

1. Map your menu by season at the start of each quarter. Identify which dishes rely on ingredients with a narrow availability window and flag them.
2. For each flagged ingredient, decide on one tested substitute. Write it down. Cost it. Make sure your team has cooked with it.
3. Agree a price threshold with your head chef or buyer. If an ingredient goes above that threshold, the soft swap triggers automatically rather than being a debate at seven in the morning.
4. Build a short standing order of pantry items that extend your options: good dried pulses, quality tinned tomatoes for the months when fresh are pointless, preserved lemons, decent stock bases. These are not shortcuts. They are infrastructure.
5. Review your supplier list twice a year and ask directly what is working and what is not. If your primary greengrocer cannot give you reasonable notice on shortfalls, find one who can.

What Not to Do When Supply Goes Wrong

Do not serve an ingredient past its best because you already ordered it. Customers are not obliged to eat watery tomatoes because you printed the menu in September. Pull the dish, run a special, charge what it costs, and move on. Nobody ever complained about something tasting properly of what it was.

Do not substitute silently with something that changes the character of the dish entirely and say nothing. If the dish now has celeriac where the menu says parsnip, tell the front of house. They will sell it if you give them something honest to say about it.

And please, do not reach for imported out-of-season produce as a default. A strawberry in November is not a strawberry. It is a red object with the texture of wet foam and the flavour of mild regret. Save your money, use something that is actually in season, and serve it well.

The kitchen that handles seasonal sourcing well is not the one with the most flexible menu. It is the one where the chef understood, before service started, exactly what was in the building, what it could become, and what they would do if the delivery had been half what they expected. That knowledge does not come from a system. It comes from paying attention, season after season, until the rhythms of the year stop feeling like surprises and start feeling like old friends who are occasionally late.