BonZumo · DE

Seasonal restaurant menus: maintain products, recipes and prices together

Plan a menu change that works for purchasing, the kitchen and the people taking orders.

Guide overview: Seasonal restaurant menus: maintain products, recipes and prices together: Make a seasonal menu work beyond the printed page; Put the right selection in the right place; Prepare your next menu change with Bonzumo

Make a seasonal menu work beyond the printed page

A new lunch offer, the opening of your terrace or the start of a fresh produce season can give guests a reason to return. For the restaurant team, a seasonal menu is also a practical change: products must be easy to find at the till, prices must be clear and staff need to know which offer belongs in which area. If these questions are left until the first order arrives, the launch creates unnecessary interruptions just when you want service to feel confident.

Bonzumo includes product management, recipes, costing and location-specific menus. These functions let you consider a menu change as a connected task, from the dish you want to sell to its ingredients and its presentation in the sales workflow. The views and assignments you use depend on your setup. The important point is to prepare an offer that your team can actually handle, rather than treating the new menu as a piece of marketing copy separate from daily operations.

Define what guests can actually order

Begin with the offer itself. Is the new dish a separate product, a menu or a variation of an existing item? Will there be a smaller portion, an extra side or an alternative preparation? Each distinction should serve a purpose. Too many almost identical entries make selection harder, while one broad catch-all product can hide important differences. Agree the structure first, then reflect it in your product data so that the system follows a clear restaurant decision.

Consider a seasonal pasta dish with a vegetarian base and an optional addition. Staff should know what is included in the base price and what the guest is choosing separately. The recipe and the sales description should follow the same logic. An addition that is sold as a distinct option should not exist only in an informal note. During setup, follow a complete order and check that kitchen and service staff recognise the same dish, quantities and choices throughout the process.

Use names that help people choose correctly

A useful product name supports sales while remaining recognisable at the point of order. “Special 3” tells a new team member very little, particularly when several promotions overlap. Choose precise names that match the language of your restaurant. A supporting description can explain ingredients or preparation, but it should reflect the dish actually being served. Attractive copy loses its value when it creates an expectation that the kitchen cannot fulfil.

Be careful when deciding whether to rename an existing item or create a new one. A clearer description of the same dish is different from an entirely new recipe. Avoid casually turning an old product into a new dish if this makes earlier sales difficult to interpret. Agree which offers are continuing and which represent a genuine change. A clear product structure helps later when you compare seasons or want to understand how a specific menu item was received.

Check recipes and yields together

A menu change should include a recipe review. A different ingredient, portion size or prepared component changes the basis of your food cost calculation. Bonzumo includes product recipes and base recipes, allowing you to describe the composition of an offer. This is particularly useful for preparations used in several dishes, such as a sauce, dressing or vegetable component. The same preparation can then be discussed consistently rather than being understood differently in each menu item.

Pay attention to yield. A batch described as ten portions is a useful reference only if the kitchen produces approximately ten suitable portions from it. Trimming, cooking and serving practices can change that result. Review the recipe basis when the practical output differs. Software calculations depend on the quantities entered; the kitchen provides the evidence that those quantities match the preparation method. Testing a real batch gives you a stronger basis than merely accepting an inherited spreadsheet figure.

Prepare prices with understandable assumptions

Do not choose a new price only by looking at last year's menu. Review current purchase information, portion quantities and the nature of the offer. Bonzumo's recipe costing supports the examination of ingredient costs. Your complete pricing decision also needs to consider staffing, energy, rent, service style and positioning. A useful calculation makes the choice easier to explain without pretending that one ingredient percentage determines the right selling price.

Check the basis of every figure. A net purchase cost and a gross selling price should not be compared as if they were equivalent. Agree tax-related assignments with the relevant advisers and the actual system setup. Practical scenarios help the team understand the result: what changes with a larger serving, which additional component is expensive and how does a different pack size affect the quantity used? These questions turn menu pricing into an informed restaurant decision.

Put the right selection in the right place

Different operating areas may need different selections. Your terrace might have a shorter menu than the dining room, and a café may sell a different range in the evening. Bonzumo includes location-specific menu management. During setup, clarify how your organisational areas will be represented and which products should be available in each. A successful assignment is one that gives the team a suitable choice when they are actually serving guests.

Check the change from the devices and sales workflows your staff use. Editing a product in the back office does not by itself establish that it appears in the right place. Ask someone to find the new dish, select a variation and explain the order. This article does not assume automatic seasonal scheduling; agree how the new offer will be made available and the old one removed. A deliberate handover prevents an unintended overlap between two versions of the menu.

Brief kitchen and service before launch

The team needs practical answers rather than a long presentation. What is new, what has been removed, which side is included, what can change and what can guests expect? Go through the main items together with kitchen and service staff. The product information in the system gives this discussion a foundation. It does not replace a short conversation about taste, portion presentation and the handling of special requests.

Use a complete example: a guest orders the new dish, requests a change and asks about an alternative. Check whether the selection remains clear and whether the kitchen receives enough information. If the example requires several confusingly similar products or vague free text, improve the structure before launch. The best seasonal menu feels straightforward at the point of sale because the product data and the team's everyday language support one another.

Include existing stock in the changeover plan

A new season rarely starts with an empty storeroom. Review ingredients and prepared items before withdrawing the old menu. Some products can sensibly continue into the new offer, while others need a separate plan. Base the decision on quality, suitability and the dishes you intend to serve. Existing stock is not a reason to force an unsuitable ingredient into a new recipe, but an early review can prevent unnecessary duplication in purchasing.

Bring kitchen and purchasing together around recipes, products and current stock observations. A base sauce may suit two new dishes while a specialist garnish is available for only a few remaining portions. Plan the transition in those concrete terms. Calculated consumption depends on the quality of quantities and movements, so a physical stock check before a major change can still be useful. This process supports purchasing decisions without promising that the system will make them automatically.

Review the first weeks with context

After launch, look beyond the simple question of whether an item sold. Does service often need to explain it? Is preparation difficult during busy periods? Do actual portions match the costing assumptions? Sales information can help you assess demand, while kitchen and service feedback explain the working conditions. A popular product is not necessarily commercially attractive, and a low-volume dish may still have a deliberate place in your concept.

Compare reasonably similar periods. A rainy weekday and a sunny event evening are not equivalent tests of a seasonal offer. Note availability and any stock constraints before drawing conclusions. Where practical, change one important factor at a time, such as the name, menu position, portion or price. This makes responses easier to understand. Bonzumo provides a framework for product maintenance and reporting; interpretation becomes valuable when it stays connected to how your restaurant actually traded.

Common questions about seasonal product maintenance

Does everything need to be created again for each season? First distinguish continuing products, changed variations and genuinely new dishes. The appropriate data structure depends on those cases. Can base recipes support several products? Bonzumo includes base recipes; demonstrate their use and quantity relationships with actual dishes. Does a new product appear everywhere immediately? Availability depends on assignments and setup, so check the intended sales workflow before opening the offer to guests.

How detailed should descriptions be? Detailed enough to support the choice and accurately describe the dish. Claims about origin, characteristics or ingredients need reliable product information behind them. Can the software decide the best price? Costing informs your choice but does not automatically know every operating cost, your intended positioning or the expectations of your guests. A productive demonstration makes those boundaries clear while showing the information you can use.

Prepare your next menu change with Bonzumo

Bring your current menu and three proposed seasonal dishes to a demonstration. Add a base recipe, a product variation and an area that will sell only part of the range. Follow the route from product maintenance to selection during service. Ask to see the quantity and price assumptions explained, rather than only the final result. This lets you judge whether the structure is understandable to your team without extra interpretation.

A well-prepared seasonal menu connects an appealing guest offer with orderly work behind the scenes. Bonzumo can help you maintain products, recipes and the appropriate selection together. Your team can then understand what is being sold, where to find it and what sits behind it. Arrange an inventory and menu-management demonstration around your next real changeover so that you can assess the required setup against a task you already need to complete.

See how the workflow fits your operation.

Request a demo