How do I cost dishes with local and seasonal products?

Start with the usable portion, not the delivery price

I cost local and seasonal products by working from the saleable portion first. The real question is not what the crate, bunch or tray costs on the invoice, but what remains after trimming, peeling, sorting, cooking loss and small prep waste. That usable amount is the only honest basis for recipe costing. After that, I test whether the dish still leaves the contribution my operation needs, because the ingredient does not just have to pay for itself. It also has to carry prep time, energy, holding risk, menu space and the chance that tomorrow’s purchase price will already look different. That is how I keep a seasonal idea commercially sound instead of pricing it from enthusiasm alone.

A simple hypothetical asparagus dish shows the logic. If I buy 10 kilograms of regional asparagus at 8 euros per kilogram, I start with 80 euros on the delivery note. If peeling and sorting leave only 6.5 kilograms usable, the effective ingredient cost rises to about 12.31 euros per usable kilogram. At 220 grams per plate, the asparagus alone costs around 2.71 euros before potatoes, sauce, garnish and a small safety buffer. This is exactly where many seasonal dishes go wrong. The gross purchase price still looks fine, but the edible portion is already much more expensive. In my kitchen organisation, I therefore insist that recipe talks happen in usable yield, not in optimistic purchasing impressions.

Set fixed costing rules for products with moving prices

Seasonality becomes difficult when prices move but the team has no shared method for reacting. I therefore set clear rules before the season gets busy. First I define the costing unit that matters for the product: gross kilogram, net kilogram, piece, bunch or litre. Then I decide who updates purchase prices, how often we review them and from what level of deviation we recalculate a dish. Strawberries from a local grower might need checking twice a week in peak season, while herbs may only need a recalculation after a supplier or quality change. That gives my team a stable process even when the market itself is unstable. Without that discipline, the kitchen cooks from last week’s assumptions while purchasing already pays this week’s reality.

I use three decision zones so we do not improvise under pressure. In the normal zone, the dish stays as it is because recipe cost still fits the planned frame. In the warning zone, I first review portion logic, side dish choice or menu position before I change the selling price. In the replacement zone, I only keep the dish if a seasonal substitute works both culinarily and economically, for example rhubarb instead of strawberries in a dessert or a different market vegetable as the accompaniment. I want those changes prepared in the recipe structure, not invented during service. That is also why Understand what goes into every dish on your menu matters to me: maintained ingredients and quantities give me one current basis for recalculation instead of guesswork from memory.

Break every seasonal dish into costed components

A seasonal dish only becomes manageable when I split it into parts. Suppose I plan a fictional autumn main course: braised local beef cheek with celeriac purée, glazed carrots and apple jus. On the menu, that sounds coherent and valuable. In costing, I cannot leave it at that. I calculate the meat with raw weight, trim loss, cooking loss and final portion size. I calculate the jus and purée as base recipes with their own yield. I include garnish, because repeated over many covers it stops being trivial very quickly. Finally, I allow for mise en place loss and slower days when not every prepared portion sells. Braised dishes in particular can deceive an operator, because the raw purchase price may look acceptable while the final edible quantity tells a much tougher story.

A hypothetical calculation makes the point. Eight kilograms of raw beef cheek might cost 96 euros. After trimming and braising, perhaps only five kilograms remain suitable for service. That means the edible kilogram now stands at 19.20 euros. If I plate 180 grams, the meat alone costs around 3.46 euros. Once I add celeriac, potato in the purée, butter, carrots, apple, wine, stock, herbs and garnish, the full recipe may sit around 5.80 to 6.20 euros per plate. At that moment I can judge the price honestly. If I want the dish near one third food cost, I know the minimum selling range I need. If I price far below it, I subsidise every plate. If I price above it, presentation and service must clearly support that value perception for the guest.

Treat local sourcing as a value mix, not only as a cost issue

Local does not automatically mean too expensive for my menu. Very often it means the cost and value are distributed differently. A local tomato may cost more per kilogram than standard wholesale product, yet arrive riper, taste stronger and create less rejection in prep. In that case I may need fewer extra components, because the main product already carries the plate. I therefore judge local buying against four points every time: purchase price, net yield, spoilage rate and realistic selling power. A higher input cost can still be the better decision if I waste less, need fewer supporting ingredients or can charge a clearly stronger menu price without awkward explanations. Looking only at invoice price per kilo is one of the fastest ways to reach the wrong conclusion while thinking I am being financially strict.

In practical menu planning, I never assess a local ingredient in isolation. A regional fresh goat cheese may cost more than a generic alternative, but it can turn beetroot, herb oil and bread into a starter with much stronger perceived value. Guests usually accept a firmer price when season, origin and the plate itself make sense together. The real danger is softer than that: I mention locality on the menu but still price too cautiously because I am nervous about pushback. Then my food cost and labour go up while revenue does not. Before each seasonal change, I therefore review with the team which element may vary and which part of the dish must stay stable. That avoids rushed substitutions and keeps guest expectation, prep planning and execution aligned.

Change portion logic and format before you panic on price

When local or seasonal ingredients become more expensive, I do not start with a price increase by reflex. I review three levers in order. First, can I improve portion logic without making the guest feel short changed, for example by strengthening texture, contrast or the seasonal side? Second, can I swap to a more abundant accompaniment that lowers cost or waste while keeping the dish attractive? Third, only if those routes are not enough do I change the selling price. This sequence is fairer to guests and easier for staff to explain. It stops me from pushing every supplier movement directly into the dining room and forces me to manage the menu actively rather than reacting to invoices with panic.

This matters most with daily specials and weekly recommendations, because that is where beautiful market produce appears and where recalculation is often neglected. I never release a seasonal special unless three figures are written down first: recipe quantity, expected yield and planned selling price. If one of those is missing, the dish is not ready. Once it is on sale, the sold version also has to arrive clearly in production. If a side or garnish changes, everyone still needs to understand what was ordered and what should be plated. That is one reason Give service, kitchen and bar a shared view of orders is useful in practice. Clear naming and structured handover prevent confusion in mise en place, pass communication and later review.

Assign responsibilities so the process stays fair for the team

Good seasonal costing rarely fails because the maths is difficult. It usually fails because nobody owns the right part of the process. I therefore separate responsibilities clearly. Purchasing or the kitchen lead reports price changes and availability. The person responsible for recipes maintains quantities, yields and base preparations. I decide from that information whether we change the item, the side dish, the portion or the selling price. That is fair to employees because a server should not be blamed for commodity swings they cannot see and do not control. If guests ask why a dish changed, the team needs a short honest explanation such as seasonal availability, local sourcing, limited supply or updated composition. They do not need to solve a margin problem tableside during a busy service.

I also run a small review rhythm for each seasonal phase. Before launch, I check recipes, current purchase prices, expected yields and planned selling prices. After the first week, I do not look only at sales. I also check whether portions were actually served as calculated and whether waste was higher than expected. A very ordinary detail can change the result quickly: smaller carrots, herbs wilting early in warm weather, mushrooms arriving wetter than last week, or a batch of fruit that bruises faster than usual. Each of those shifts changes the real net cost immediately. In that case I correct recipe, side dish or price early rather than carrying false assumptions for a month. That feedback loop is not mistrust. It is normal operational learning.

Use a short formula and apply it dish by dish

My practical formula is simple: choose the seasonal product, measure or estimate real yield, cost the full recipe, test the target food cost and contribution, then lock the selling price or adjust the portion logic. If a local ingredient works beautifully as a story but not as a viable standalone plate, I give it a smaller role, a shorter selling window or a place in a set menu where the wider structure can carry it better. Good costing does not mean passing every fluctuation straight to guests. It means deciding consciously which products define the concept, which dishes need a buffer and where a strong seasonal plate can be built with simpler supporting elements. That is how locality becomes an operational decision instead of decorative menu wording.

If I were setting this up from scratch tomorrow, I would start with one dish rather than the whole menu. I would note gross purchase cost, net yield, portion size, every secondary component and a modest waste allowance. Then I would define the minimum contribution that dish has to make. If the planned price does not reach that level, I choose one of four deliberate responses: raise the price, change the side, reduce the expensive component or shorten the sales period. That keeps the question manageable and concrete. Guests then receive better-tasting seasonal dishes, my staff receive clearer routines and I keep control of margin without pretending that local buying is either automatically profitable or automatically too expensive.