Seasonal Menu Without the Confusion: How to Update Dishes, Prices and Availability

Why Seasonal Menu Changes Cause Confusion in Tourist Locations

In Europe’s holiday destinations, the calendar plans much of the menu. Eurostat figures for 2025 show that July and August alone accounted for 31.1% of all overnight stays in EU tourist accommodation. In the most seasonal countries the concentration is far sharper: 54.5% in Croatia, 43.4% in Bulgaria and 41.6% in Greece. Across the EU, overnight stays in August 2025 were 3.6 times those in January; in Croatia the ratio was 41.1 times, in Greece 20.5 times.

For a restaurant on the coast, that means a kitchen running flat out for a few weeks, slowing through the shoulder season and shrinking or closing in the low season. The seasonal menu moves with it: dishes appear and disappear, suppliers change, portions and prices are adjusted. Each change makes sense on its own. The trouble is how many places the menu now lives.

Costs add pressure. Restaurant prices in the EU have recently been rising faster than consumer prices overall, and few operators can absorb that for a whole tourist season, so a menu price update often lands just as peak season crowds arrive.

Guests rarely object to the increase itself. What unsettles them is a mismatch: one price on the Google Business Profile menu, another on the printed card at the table, a third in a delivery app. Each figure may have been correct on the day it was posted, yet together they leave a visitor feeling misled. The same happens when a dish still listed online has been off the kitchen’s list for weeks.

The real problem is not the price change but the absence of a single source of truth. When each channel is edited separately, by different people at different times, drift is inevitable. A consistent menu across channels is therefore less a design question than a matter of process.

Build a Seasonal Menu Calendar Around Your Tourist Season

A seasonal menu works best when it follows the rhythm of your guests, and as the Eurostat figures above show, in most European destinations that rhythm is extreme.

Map Peak, Shoulder and Low Season for Your Location

The EU average hides much sharper local curves, and even within one country a ski resort, a city-break destination and a beach town peak at different times. National figures are only a starting point.

Start by marking your own peak, shoulder and low season, using past covers or the local event calendar. Then overlay in-season produce: when do your local suppliers move from spring greens to tomatoes, stone fruit or different fish? Ask for supplier availability lists so seasonal ingredients peak in the weeks you are busiest.

How Often to Change: Full Seasonal Switch vs. Small Rotations

Many venues save the complete switch for the start of peak season and the return to low season, and handle everything in between through small rotations: a new special, a replaced side, a dessert that follows the fruit. Staple and signature dishes kept year-round anchor the menu, so returning guests still find what they came for.

It also helps to think in separate menu versions rather than one endlessly edited document: a seasonal main menu, a holiday menu, a weekend brunch menu, an event menu. On a digital menu, these can be prepared in advance and activated when needed, instead of rebuilding the same file each time.

Set Fixed Decision Dates, Not Launch-Day Improvisation

Restaurants routinely review their seasonal menus, but the review is often squeezed into the week the season opens. Put decision points in the calendar instead: when to confirm dishes with suppliers, when to freeze recipes and costs, when translations and the staff briefing must be ready. Fixed dates turn the switch into a routine instead of a last-minute rush at the pass.

Decide What Changes: Keep, Rotate, Add or Retire

Before anyone rewrites a description, decide which parts of the menu move at all. Every menu change forces the kitchen to relearn prep, waiting staff to relearn their answers and returning guests to hunt for their favourites. The aim is to change as much as the season demands and nothing more.

Keep Signature Dishes, Rotate Sides and Garnishes

The staple dishes people come back for rarely need to go. What can change is what surrounds them. A grilled fish can stay constant while its sides and garnishes follow in-season produce: asparagus in spring, tomatoes and peppers in summer, squash in autumn. Guests see something new and the kitchen keeps its core technique.

Check Supplier Availability and Cost Before Committing

Seasonal ingredients are cheapest and best at their peak, but that window is often narrower than a printed menu assumes. Ask local suppliers for their availability lists for the coming months and cost each candidate dish before it goes on the menu. A dish that only works briefly, or whose food cost drags profit margins below the rest of its section, is better positioned as a short seasonal special than a permanent line. Provenance also sells: the National Restaurant Association’s 2026 What’s Hot Culinary Forecast puts local sourcing first among its top 10 overall trends.

Fewer Seasonal Additions, Better Stocked

The temptation is to add everything the market offers. The cost shows up in the bin. Eurostat puts EU food waste in 2024 at about 129 kg per person, 57.9 million tonnes in total, up 0.7% on 2023. Restaurants and food services generated 12% of it, or 15 kg per inhabitant. Every extra seasonal dish needs its own prep, its own par levels and often ingredients that nothing else on the menu uses.

An overlong list also runs out more often. A handful of well-supplied limited-time offers beats a long list that keeps disappearing mid-service.

Retiring a dish deserves the same discipline. If an item sells slowly, shares few ingredients with the rest of the menu or depends on a supplier who can no longer deliver, take it off rather than apologising for it every evening.

Prepare the Next Menu Before the Season Starts

The worst moment to rewrite a menu is the morning the first coach of tourists pulls up. Venues that handle seasonal changes calmly do the groundwork weeks earlier, while the current menu still runs, so launch day becomes a switch rather than a scramble.

Build the New Season as a Separate Menu, Not Edits to the Live One

Editing the live menu dish by dish invites half-finished states: a new starter with no photo, a summer price next to a spring description, a translation still describing last season’s recipe. Guests scanning the table code see every one of those gaps. A cleaner habit is to keep separate menu versions — seasonal, holiday, brunch, event — and build the incoming one in parallel. With a digital QR code menu, the printed code on the table stays the same; only the content behind it changes, so nothing needs reprinting. Some tools, Platoo among them, let venues prepare several menus in advance and activate the right one when needed.

Start the new version with the menu categories that carry over, then add a clearly labelled seasonal section so returning guests can find what is new without hunting.

The Per-Dish Checklist: Name, Description, Photo, Price, Ingredients, Allergens, Translations

Every dish entering the new menu should pass the same check before any guest sees it. A full seasonal preparation list covers new dishes, prices, ingredients, allergens, photos, categories, drinks, promotions, availability dates and translations. At dish level, that means a name and description that match what the kitchen actually plates, a current photo, the price, the complete ingredient list and allergen information covering the EU’s 14 regulated allergens.

Translations come last for a reason: they should be produced from the final wording, not from a draft the chef is still adjusting. A multilingual menu translated early and edited later is how an English description ends up promising something the German version never mentions.

Test on a Phone, Then Activate on Launch Day and Keep the Old Menu

A menu that looks tidy on a laptop can be awkward on a small screen, which is where guests will actually read it. A simple menu review workflow keeps the process predictable:

Once the new menu is live, keep the previous version rather than deleting it. It becomes the starting point for the same season next year, with photos and translations that only need checking.

Update Prices Without Confusing Guests

Few seasonal changes are as sensitive as a price change. According to Eurostat’s HICP data, prices for “restaurants, cafés and the like” rose by 4.2% year on year in December 2025, compared with 2.3% for the all-items index, so many venues will be adjusting prices between seasons. As the opening section argued, guests forgive the increase far more readily than a mismatch between channels, so the work is mostly about sequence.

List Every Place Your Prices Appear

Before changing a single number, map where your prices live.

Change the Master Menu First, Then the Rest the Same Day

Choose one menu as your single source of truth and make every menu price update there first. A digital QR code menu suits that role, because it is the version guests actually read at the table. In Platoo, for example, prices, dishes and descriptions are edited from a control panel and the changes appear instantly. Then work through the rest of the list on the same day: Google profile, delivery apps, other listings, boards. Edits on external platforms are not always visible straight away, so check them after publishing rather than assuming. A consistent menu across channels matters more than speed on any single one.

Price Display Basics: Final, Tax-Inclusive, Unambiguous (Check National Rules)

The EU’s price indication directive, Directive 98/6/EC, defines the selling price as the final price for a unit or quantity of the product, including VAT and all other taxes. Article 4(1) requires that price to be unambiguous, easily identifiable and clearly legible. However, Article 3(2) allows Member States not to apply these rules to products supplied in the course of providing a service, so restaurant price display is largely governed nationally. Check local requirements on cover charges, service charges and tax display. As a working rule, show the VAT-inclusive selling price and avoid surcharges tucked away in small print.

Close the Printed-Menu Gap

Printed menu reprinting is where most mismatches start. Reprints cost money, so old copies tend to stay on tables for weeks after a change. If you keep paper, reprint in one batch timed with the switch, collect every old copy and avoid correcting prices by pen or sticker, which looks improvised. Alternatively, cut printed material down to table inserts that point to the QR menu, so each price exists in one place only.

Handle Sold-Out and Unavailable Dishes in Real Time

Seasonal produce runs out, and a seasonal menu has to cope with that. What damages the guest experience is rarely the sell-out itself; it is the waiter who learns about it only after a table has read, translated and chosen.

A Simple 86 Routine: Kitchen, Floor, Menu

Kitchens use “86” to mark a dish that is unavailable and off service until further notice. The call only works if everyone hears it at once. A clean routine is short: the kitchen calls it early, ideally with a countdown of the last portions; front of house confirms; one person marks the dish unavailable in one place; someone verifies that every channel shows the same thing; and the dish is switched back on the moment it returns.

That “one place” matters. If a printed insert, a chalkboard, the digital QR code menu and the Google Business Profile menu are updated separately, one will be wrong by dinner. Treating the digital menu as the single source of truth keeps the menu consistent across channels. The routine belongs in the staff briefing at the start of each season, and in any retraining on the new menu, so seasonal hires know who calls an 86 and who updates it.

Hide, Don’t Delete — and Switch It Back On

Deleting a sold-out dish means rebuilding its description, photo, allergens and translations when it returns. Hiding it keeps everything ready. Platoo, for instance, lets staff hide an item in a few clicks and show it again later, with changes appearing instantly and no reprinting. It does not sync with POS or inventory systems, so availability is changed manually — which is why switching dishes back on needs a named owner. Otherwise a restocked dish can stay invisible for days.

When Sell-Outs Repeat, Fix Prep Levels, Not the Menu

An occasional 86 is normal; the same dish vanishing every evening is a planning signal. Chronic sell-outs are fixed upstream: honest par levels, prep planning based on what actually sold rather than on optimism, and a right-sized menu the kitchen can deliver at peak. A dish that cannot be prepped reliably in seasonal quantities may belong on the specials board instead.

Keep Ingredients and Allergens Accurate When Recipes Change

A seasonal menu change rarely stops at the dish name. A new supplier, a swapped herb or a different sauce base can quietly alter what a guest is eating, and in the EU that is a legal matter as much as a culinary one.

What EU Law Requires for Non-Prepacked Food

Under Regulation (EU) No 1169/2011 on food information to consumers, Article 44(1)(a) makes the allergen particulars mandatory for food offered without prepackaging, including dishes served by restaurants and mass caterers. Those particulars cover the 14 substances listed in Annex II: cereals containing gluten, crustaceans, eggs, fish, peanuts, soybeans, milk, nuts, celery, mustard, sesame, sulphur dioxide/sulphites, lupin and molluscs.

Article 44(2) lets Member States set how this allergen information is made available and presented, so check the national rules where you operate. Without prejudice to those national measures, Article 13(1) adds that mandatory information must sit in a conspicuous place, be easily visible and clearly legible, and not be hidden or obscured by other matter.

Guests notice, too. The National Restaurant Association’s 2026 What’s Hot Culinary Forecast also lists clear menu labelling, icons and cues, and allergen-friendly menus among its top 10 overall trends.

The Seasonal-Swap Trap: Same Dish Name, New Allergen

The most dangerous menu update is the one that looks like no update at all.

A blanket “ingredients subject to change” line does not fix this; it shifts the burden to the guest without saying what changed. When a recipe changes, the ingredient list and allergen fields should change with it, and dish photos and descriptions should be refreshed if the dish looks different.

When a recipe changes, the allergen list has to change the same day, not at the next reprint.

Allergen Check Before Every Menu Activation

Seasonal menus prepared in advance give you a natural checkpoint. When a digital menu stores ingredients and allergens per dish alongside photos and descriptions, the review can happen before activation rather than after a guest asks:

1. Check each new or modified recipe against the 14 allergens, including sauces, garnishes and frying oils.
2. Update the allergen information on every version of the menu, printed and digital.
3. Have the head chef sign off before the menu goes live.
4. Cover every allergen change in the staff briefing, so waiting staff answer from facts, not memory.

Keep Every Language in Sync for International Guests

A seasonal menu change rarely fails in the original language. It fails in the German, Italian or Polish version that nobody reopened after the new dishes went in. Illustrative example: the English page lists a summer gazpacho while the French page still offers a winter stew, and guests trust neither.

Why a Half-Translated Menu Is Worse Than It Looks

A menu that is fully translated except for three new dishes tells guests the venue has lost track. Readers hit untranslated names, guess, or ask staff who may not share their language. Many simply skip the new items.

A 2020 CSA Research survey of shoppers points the same way:

Those figures concern online buying, not dining, but the instinct carries over: people commit more easily when they understand what they are choosing.

There is also a legal floor. Article 15 of Regulation (EU) No 1169/2011 requires mandatory food information to appear in a language easily understood by consumers of the Member State where the food is marketed, and it does not preclude showing it in several languages. In practice, the mandatory information has to be available in a language local consumers easily understand; other languages can be added on top, and they are only useful if they are kept as current as the original.

Auto-Translate, Then Review Names, Allergens and Local Dishes

Machine translation makes it realistic to cover every language after each menu update. Platoo, for example, translates the menu automatically and lets the venue edit every translation. The review step still matters.

Check three things after each change. First, dish names: a regional speciality often reads better under its original name with a short explanation than translated literally. Second, allergen information for the EU 14 allergens must match across all menu translations; a new recipe that adds nuts has to flag them in every language, not only the source one. Third, dish photos and descriptions: an outdated photo contradicts even a flawless translation.

A staff member who reads the language can spot-check the most-used versions in minutes.

Brief Staff, Highlight New Dishes and Review Each Season

A Short Pre-Launch Staff Briefing

A new menu fails quietly when the floor team learns about it from guests. A short staff briefing before the first service is usually enough: taste the new dishes, walk through changed ingredients and allergens, and agree how sold-out items will be handled. Retraining on the new menu needs no classroom. Everyone on the floor should be able to describe every new dish in one sentence. Ask everyone to open the live menu on their own phone, so they see exactly what guests see.

Highlight Seasonal Dishes Without Cluttering the Menu

Limited-time offers and seasonal specials work best when they are few and clearly described: what is offered, why it is special and how long it is available. “Only while local apricots last” gives guests a reason to order now. Highlighted or recommended dishes should reflect what the kitchen genuinely wants to sell, which also matters for the food waste figures discussed earlier: steering guests towards specials built on perishable seasonal produce is one practical lever. The same dishes can anchor social media promotion, provided the post and the menu say the same thing.

Several Venues or Hotel Outlets: One Routine, Local Exceptions

Hotel F&B outlets and groups running multi-venue menus benefit from one shared routine plus a short list of agreed local exceptions, such as a pool bar that drops hot dishes. Some digital menus, Platoo among them, manage several venues from one account and show promotions or highlighted dishes, keeping the routine consistent without forcing identical menus.

End-of-Season Review: What to Keep, Retire or Bring Back

Close each season with a short review while the details are still fresh, then feed the results into the preparation workflow described earlier:

FAQ: Seasonal Menu Updates