Recommending wine by style is a practical way to help a customer who is unfamiliar with grapes, regions or appellations. Many tables do not say "I want a lees-aged Godello" or "I am looking for a cool-climate Pinot Noir". They say things like "something fresh", "a red that is not too strong", "a white that can stand up to the dish" or "something special to start". The service team's job is to translate those phrases into wine styles.
Learning about wine through styles does not lower the standard. Quite the opposite: it organises knowledge so it can be used. A region provides context, a grape provides identity and a winery provides confidence, but style is what the customer usually understands first: fresh, light, creamy, dry, fruity, full-bodied, elegant, intense, sweet or food-friendly.
Summary: recommending wine by style helps restaurants turn customer preferences into clear options. Styles connect sensation, dish, price and occasion, and provide a bridge between Learn Wine and the Wine Library.
Why start with styles
Customers cannot always name what they want, but they can almost always recognise a sensation. If they ask for "something easy", they may mean low tannin, clear fruit and a moderate price. If they ask for "a serious white", they may be looking for volume, ageing, lees or a prestigious region. If they ask for "something different", they may accept a less familiar grape if the style is explained well.
Styles can help organise recommendations around the customer's preferences, without requiring them to know the wine map. They also help the team organise the wine list:
- fresh whites for aperitifs, seafood and briny dishes;
- textured whites for sauces, rice dishes, poultry and oily fish;
- food-friendly rosés for mixed tables or Mediterranean cooking;
- light reds for customers who do not want power;
- medium-bodied reds for sharing and accompanying a variety of dishes;
- structured reds for meat, rich stocks and customers seeking intensity;
- dry sparkling wines for aperitifs, fried food and long menus;
- sweet and fortified wines for cheese, dessert and the end of the meal.
The minimum style map for service
There is no need to start with thirty categories. A team can work very well with eight:
Fresh white
Acidity, lightness, citrus or saline sensations. Useful for aperitifs, fish, seafood, salads, green dishes and customers asking for "something refreshing". Example routes: Albariño, Verdejo, Sauvignon Blanc, Rías Baixas, Muscadet.
Service sentence: "It is a fresh, direct white, with acidity that can bring a feeling of freshness alongside the dish."
Textured white
More body, ageing, lees, integrated oak or a creamy sensation. Useful for fish with sauce, rice, poultry, dishes with butter or customers who think a white will fall short.
Service sentence: "It is still a white, but with more volume; it works if the dish needs something with more presence."
Food-friendly rosé
Not all rosés are sweet. A dry, structured rosé can be useful when the table cannot agree between white and red.
Service sentence: "It has the freshness of a white and some of the structure of a red, which is why it fits several dishes at once."
Light red
Low tannin, fresh fruit, served slightly cool. Useful for tuna, duck, mushrooms, roasted vegetables, white meats or customers who say "red, but not strong".
Service sentence: "It is a fine, fresh red, more about texture than power."
Medium-bodied red
A style that can be versatile for sharing. It has fruit, enough structure and gentle tannin. It works with meat, rice dishes, stews, cheeses and tables ordering one bottle for everyone.
Service sentence: "It is a balanced red: it has enough body for the food, but does not dominate the table."
Structured red
More body, tannin, ageing or concentration. Useful for red meat, intense dishes, rich stocks, game or customers looking for a bottle with presence.
Service sentence: "It is a wine with more structure; it deserves a dish with intensity and a little time in the glass."
Dry sparkling wine
It should be presented as a food wine. It can open the meal, accompany fried food, seafood, ham, sushi, tasting menus or celebrations that continue at the table.
Service sentence: "It is not just for a toast; the bubbles and acidity can offer a fresh contrast with fried food or briny dishes, depending on the wine and the preparation."
Sweet or fortified
Not just dessert. It can accompany blue cheese, foie gras, nuts, bitter chocolate or spiced cooking. The key is to pour a little and explain balance.
Service sentence: "If it is sweet, we explain the balance between sweetness and acidity; if it is a dry fortified wine, we do not promise sweetness. We adjust the amount to the wine and the occasion."
How to translate customer phrases
The team can practise these translations of preferences into styles:
- "I do not want a very strong wine" -> light red or medium-bodied red.
- "I want a white that can stand up to the dish" -> textured white.
- "Something fresh to start" -> fresh white, dry sparkling wine or saline rosé.
- "A wine to share" -> medium-bodied red or textured white.
- "Something special" -> recognisable region, specific producer or a less familiar style explained well.
- "Not too expensive" -> a clear style with a price alternative, not the cheapest bottle without a reason.
This exercise prevents recommendations from relying on memory alone. The team learns to listen for intent.
Training exercise
Choose two real wines for each style. For each one, write:
- One sensation word: fresh, creamy, light, structured.
- One dish from the menu.
- A twenty-second sentence.
- A more affordable alternative.
- An upsell alternative within the same style.
Then simulate five customer phrases and require the team to answer by style before naming a grape or region. A practical sequence is: understand the need, choose a style, justify it with the dish and only then name the bottle.
How to review whether the list covers styles well
Learning by style also helps audit the wine list. Draw a table with the eight styles and place the actual wines available by the glass and bottle under each one. If a style has too many options, it may be creating noise; if it has none, the team will have to force recommendations that do not fit.
The review is not intended to give every style the same number of wines. It aims to provide an answer for every drinking occasion. A fish restaurant may need more fresh whites, dry sparkling wines and textured whites. A grill restaurant may need more medium-bodied and structured reds. A wine bar may need better coverage of food-friendly rosés, fortified wines, sweet wines and less obvious styles. What matters is that the list can respond to real customer phrases without always falling back on the same two bottles.
A useful indicator is to ask the team to name, for each style, a safe choice, a more curious alternative and a higher-value bottle. If they cannot, there is a gap in training, signposting on the list or the balance of the range.
Common mistakes
The first mistake is presenting style as a rigid category. A wine can sit between two styles; what matters is its usefulness to the customer. The second is confusing "light" with "simple" or "fresh" with "cheap". The third is always recommending the familiar region even when another bottle better fits the requested sensation. The fourth is not reviewing whether the list has enough options per style.
Frequently asked questions
Is it better to teach styles before regions? For teams starting out, yes. Styles help with quick recommendations. Regions and grapes add depth afterwards.
How many styles should the team master first? Between six and eight. More categories can be confusing at first.
How does this connect with the Wine Library? Each style should link to grapes, regions, pairings and the glossary. The practical route is in Learn Wine; the in-depth reference is in the Wine Library.
Continue with: wine styles, pairings, glossary, Learn Wine and the service guide.