Seasonal Menu Planning: Cost, Sourcing and Rotation

The best asparagus I ever cooked cost me less than the tired stuff I'd been buying in February. That's the whole argument for seasonal menu planning in one sentence, and it's the part chefs who've never tracked it don't quite believe: peak-season produce is usually both the cheapest and the best you'll get all year. You don't trade quality for margin. You get both, at the same time, for about six to ten weeks — and then it's gone.

Most kitchens half-do this. They put "seasonal" on the menu as a word, source out of habit, and let the cost cards drift a full quarter behind the market. This piece is about doing it properly: building a real sourcing calendar, deciding how often to actually rotate, and — the part that separates a nice idea from a profitable one — keeping your costing, allergens and HACCP current every time the menu turns over.

Why seasonality lowers cost and raises quality together

Supply and demand does the work. When a crop hits peak local supply, growers have more of it than the market can absorb quickly, so the wholesale price falls. At the same time, that produce was picked closer to ripe and travelled a shorter distance, so it eats better. The two effects arrive on the same truck.

Run the numbers on a single ingredient and it stops being abstract. Take vine tomatoes:

That's a $2.30-to-$6.40 swing on the same line item — the peak price is roughly a third of the winter price. If a caprese-style starter uses 180 g of tomato, your ingredient cost on that component alone moves from $1.15 in winter to $0.41 in August. On a dish you sell for $12, that's the difference between a component running at 9.6% of the price and one running at 3.4%. Nobody tastes the accounting, but they absolutely taste the July tomato.

The trap is the mirror image: cooking a dish out of season. A "summer" tomato salad built in February costs you more and disappoints the guest. You pay a premium to serve something worse. That's the single most common seasonal mistake, and it's usually caused by a menu that didn't rotate when the market did.

Building a sourcing calendar

A sourcing calendar is a one-page document — a table, really — that maps your core ingredients to the months they're at peak in your region. Not a national average. Yours. Asparagus peaks in April in one hemisphere and October in another, and even within a country a warm valley runs weeks ahead of a cold coast.

Start from a reliable baseline and then correct it against your own suppliers. The USDA Seasonal Produce Guide is a solid free reference for what's in season by quarter; treat it as the first draft, not the final word. Your produce supplier's price list, read across twelve months, is the second and more honest draft — price is the market telling you the truth about supply.

The calendar itself is simple. Rows are ingredients, columns are months, and each cell is marked peak, shoulder, or out:

Once you have this, menu planning inverts. Instead of deciding a dish and then hunting for its ingredients, you look at what's about to peak and build around it. The calendar becomes the brief. The March meeting isn't "what shall we cook in spring" — it's "asparagus lands in three weeks, what are the two dishes."

How often to rotate, and why

There's no universal cadence, but there is a wrong answer: whenever you feel like it. Ad-hoc rotation breaks your costing, confuses your team, and makes it impossible to learn anything year over year because nothing repeats. Pick a rhythm and hold it.

The four-season baseline

Quarterly rotation — four menus a year, turning the ~30% seasonal slice — suits most restaurants. It's frequent enough to catch the big produce shifts (spring greens, summer fruit, autumn game and roots, winter citrus and brassicas) and rare enough that you can properly cost, train and print each change. Each menu runs about twelve to thirteen weeks, which is long enough for the kitchen to get fast at the new dishes and for guests to notice and reorder favourites.

When to go faster

Some operations rotate monthly or even weekly — a chef's-market menu, a tasting counter, a produce-led bistro. The upside is you ride the very peak of each short window (the three good weeks of wild garlic, not the mediocre eight around them). The cost is real: every rotation is a full re-cost, a fresh allergen pass, new kitchen cards, and a team that never fully settles into muscle memory. Faster rotation only pays if your systems make re-costing cheap. If re-costing a menu takes you two days of spreadsheet surgery, monthly rotation will quietly bury you in admin.

When to go slower

High-volume, systemised operations — banquet kitchens, corporate catering, anywhere consistency and purchasing scale matter more than chasing peak — often run two menus a year, summer and winter. Fewer SKUs, deeper supplier contracts, tighter prep. That's a legitimate choice, not laziness; it trades the seasonal upside for operational stability. Know which trade you're making.

Managing cost volatility and re-costing on change

Here's where seasonal menus go wrong even when the sourcing is right. You design an autumn dish in September when squash is $1.80/kg, you cost it, you set the price, and you leave it there. By late November the same squash is $3.40 because everyone's buying it for the holidays. Your dish is now running six or seven points hotter than the card says, and nobody noticed because nobody re-costed.

The rule is simple: a menu change is a re-costing event, and so is a price shock inside a season. Every dish that goes onto the new menu gets re-costed at current prices before it's priced for the guest — not carried over from last year's card, not estimated from memory.

If your new autumn ravioli costs $3.90 at today's squash price and your target food cost is 30%, the floor price is $3.90 ÷ 0.30 = $13.00. Set it there or above. Then — and this is the discipline most kitchens skip — recompute the food cost percentage mid-season if a key ingredient jumps more than about 15%. A single volatile line (squash, wild mushrooms, anything weather-sensitive) can drag a dish two to four points on its own.

The reason this is hard by hand is the cascade. A seasonal pesto that goes into three dishes; a squash purée that feeds the ravioli, the soup and a side. Change the squash price once and all of them should revalue. Doing that in a spreadsheet, four times a year, across a full menu, is exactly the job that gets skipped when service is busy — which is always.

Using last year's data

The second time you cook a season is far better than the first, but only if you wrote things down the first time. A seasonal menu is a naturally repeating experiment: the same window comes back every year, so anything you record becomes a forecast.

Three things are worth capturing each season, and none of them takes long:

• Actual peak dates and prices. Last year asparagus hit $4.10/kg the week of 8 April and dropped to $2.90 by the 22nd. This year you can time your feature menu to the drop instead of guessing.
• Which seasonal dishes sold. The heritage-tomato salad outsold the stone-fruit dessert three to one. Bring the salad back, rework or cut the dessert. This is menu engineering applied to the rotating slice.
• Yield and waste on short-window produce. Soft fruit and leaves spoil fast; if you binned 15% of the stone fruit last August, order lighter and turn it faster this year.

You don't need a data warehouse for this. A dated note on each seasonal menu — prices paid, dishes that moved, what you'd change — is enough. The point is that year two starts from evidence instead of from a blank page and a hopeful memory.

Keeping allergens and HACCP current when the menu changes

This is the part that gets forgotten in the excitement of new dishes, and it's the part that gets you shut down. A menu rotation isn't only a cost and creative exercise — it's a compliance event.

Allergens first. Every new dish needs its allergen profile worked out before it goes on the menu, not after a guest asks. Swap the almond crumble for a hazelnut one and you've changed the allergen declaration; introduce a new supplier's pesto and you need its full spec, because "may contain" clauses travel with the jar. The declared allergens on the printed and online menu must match what's actually in the current dish — a menu that still lists last season's ingredients is a live liability. If your allergens are derived automatically from the recipe rather than typed by hand each season, this stops being a thing you can forget.

HACCP second. New ingredients and new methods can introduce new hazards and new critical control points. A summer menu heavy on raw and lightly-dressed dishes leans hard on cold-chain and cross-contact control; an autumn menu of slow-braised game shifts the risk to cook and cool. When you rotate, walk the new dishes through the same questions you'd ask on any HACCP review: where's the danger step, what's the limit, who logs it. Your temperature logs, cooling records and receiving checks don't change format — but the products flowing through them do, and a rotation is the natural moment to confirm the new proteins and preps are actually being logged.

A working rotation checklist

Pulling it together, here's the sequence I run each time the menu turns. It's boring on purpose — the boredom is what keeps the holes closed.

1. Read the calendar and the price list. What's about to peak in your region, confirmed against your supplier's actual prices.
2. Design the rotating third around the peak. Keep the stable core; build new dishes on the cheap, brilliant produce.
3. Re-cost every dish at today's prices. Set each price off current cost and your target food cost %, not last year's card.
4. Confirm allergens on every new dish and make sure the printed and online menu matches.
5. Fold new products into HACCP — receiving, storage, cook/cool, logging.
6. Reprint kitchen cards so the line is cooking from the current recipe, not memory.
7. Note it for next year — peak dates, prices, what sold, what to change.

The point

Seasonal menu planning isn't a marketing angle or a chalkboard word. It's a discipline that happens to pay twice — lower cost and higher quality — for the kitchens that keep their systems current. The produce will move whether you're ready or not. The only question is whether your cost cards, allergen sheets and HACCP logs move with it, or lag a quarter behind while you quietly serve February tomatoes at a summer price.

"Anyone can put 'seasonal' on a menu. Keeping the cost card, the allergen line and the temperature log honest through the turnover — that's the actual job."

Get the sourcing calendar built, pick a rotation rhythm you can sustain, and treat every change as a re-costing and compliance event. Do that and seasonality stops being a slogan and starts being one of the few reliable edges a kitchen has.