Seasonal produce shapes the menu of almost every restaurant. And the problem is almost never in the kitchen: it's that the change throws your costs out of step, your website keeps old prices, and every fix ends up going through the technician who built the page. Here's a simple method to plan the change calmly and publish it on your website the same day, without mistakes.
Why change your menu with the seasons (and how often)
Cooking with seasonal produce has two very practical advantages. The first is quality: a winter artichoke or a July tomato is at its best when the time comes, not when it has travelled halfway around the world. The second is cost: buying what is abundant now is cheaper and steadier than buying what has to be brought in out of season.
Then there's your regular customer. A menu that breathes, with two or three new dishes every so often, gives them a reason to come back and gives your team something new to talk about. That said, you don't need to change everything. As a reasonable rule of thumb, between two and four revamps a year work for most menus; market gardens and coastlines don't follow the same calendar, so adjust that number to your own produce.
And if you run a market kitchen and buy whatever you find, it can make sense to tweak a dish every week. What matters is not the exact figure: it's having a rhythm you can sustain without wearing anyone out.
How to plan the menu change step by step
Start three or four weeks before the launch. With a full dining room there's no headspace to redesign anything; with breathing room, the change gets made with judgement. The order matters:
- Review what sold and what was left behind. Have your tickets or your till's end-of-day report in front of you: the dishes almost nobody orders are the first candidates to leave the menu.
- Update your recipe costs with today's prices. A costing sheet built on supplier prices from a year ago is the quietest way to lose margin.
- Decide what is fixed and what rotates. Write it down in a short list: anchor dishes, seasonal dishes coming in and dishes going out.
- Try the new dishes with the team and brief the front of house. If nobody can explain the new dish, as far as the customer is concerned it doesn't exist.
Which dishes come in and which stay: produce cost and rotation
Every menu has anchor dishes: the ones people always order and the ones you're known for. Think twice before removing them in the name of novelty, because a good part of your repeat custom comes precisely for them. Seasonal dishes are the ones that rotate around those anchors.
It also helps to move in step with the calendar when dealing with suppliers. If you know wild mushrooms arrive in October, ask about price and volume in September. Negotiating with room to spare almost always beats buying in a rush.
And watch your margin dish by dish: a bestselling dish that earns very little is a problem dressed up as a success. Change the menu in stages. If you replace half the menu in one go, neither the customer nor your kitchen has time to adjust.
How to update your online menu without depending on a technician
Your digital menu has to reflect what is in your restaurant today: prices, allergens and availability. If every change means emailing whoever built your website and waiting days, the site goes stale and customers end up seeing prices that no longer apply.
This is where a tool like WordNext makes it simple. Its block editor works with a live preview, no technical knowledge required, and every plan includes a "Menu" block designed for restaurants: sections and dishes with prices, icons for the 14 allergens, labels such as vegetarian, vegan, spicy, gluten-free or recommended, and a "sold out" checkbox that hides the dish from the website without deleting it. When it's back in stock, you untick it and the dish reappears.
Common mistakes when changing the menu (and how to avoid them)
Mistakes almost always repeat themselves in the same places. Run through this list before every launch:
- Website prices that don't match the restaurant's. Update the online menu the same day the change happens, not the following Monday.
- An old PDF behind the QR code. If your digital menu is a PDF, every change means uploading a new file in every place it lives; sooner or later, one of them goes stale.
- Allergens not updated. If a new dish contains an allergenic ingredient, that information needs to reach the website the same day the dish does.
- Sold-out dishes still showing. A customer choosing something on your website that's already run out is exactly the disappointment you wanted to avoid.
- Not announcing the new menu. An email to your list or a social media post on launch day turns the change into a reason to come back.
A checklist for every seasonal change
So nothing slips through, organise the work by milestones:
- Four weeks before: review the sales of the season that's ending, ask seasonal suppliers for prices and update your recipe costs.
- Two weeks before: finalise the menu, try the new dishes with the team and set the final prices.
- On changeover day: publish the menu on the website, check the allergens of every new dish and make sure the QR code points to the current menu.
- In the weeks after: watch what sells and what doesn't, keep an eye on the real margin and mark dishes without stock as sold out.
Frequently asked questions
How many times a year should a restaurant change its menu?
There's no single number: it depends on your produce and your area. As a guide, two to four revamps a year suit almost any menu, with small day-to-day adjustments.
Do allergens have to be shown on a digital menu too?
The safest practice is always to provide allergen information on any medium where customers see your menu, whether paper or screen. WordNext's "Menu" block includes icons for the 14 allergens; if you're unsure what your local regulations require, check with your adviser or your hospitality association.
What should I do when a dish sells out during service?
Remove it from the online menu straight away, so nobody orders it afterwards and walks away disappointed. In WordNext you simply tick the "sold out" box: the dish is hidden from the website without being deleted and reappears when it's available again.
Do I have to review the prices of the whole menu at every change?
At the very least, review the dishes whose cost has changed. A full review once or twice a year avoids surprises: out-of-date costings are the fastest way to lose margin without noticing.
This blog belongs to an example restaurant built with WordNext. If you want to launch your next seasonal menu with a website that's always up to date, create your restaurant's website for free.