The grapes and regions your floor team should know to sell wine better

In English-speaking restaurants, good wine service often starts with translation. The guest says dry white, smooth red or something local. The team has to convert that into a useful route through the list.

The minimum map

Start with the grapes that create the most conversations: [Chardonnay](/en/wine-library/grapes/chardonnay), Sauvignon Blanc, Riesling, Pinot Noir, Tempranillo and Cabernet Sauvignon. Then connect each grape to a region and a style. For example, Chardonnay can mean a crisp by-the-glass white, a richer food wine or a premium Burgundy-style recommendation. Pinot Noir can lead to lighter reds, fine dining pairings and guests who want elegance instead of power.

Regions that reduce friction

The team should know why a guest recognises [Rioja](/en/wine-library/regions/espana/rioja), Champagne, Burgundy, Bordeaux, Douro or Rías Baixas. Recognition creates trust. The recommendation improves when the team can add one useful detail: body, acidity, oak, freshness or food match. Use the [grape hub](/en/wine-library/grapes) and [region hub](/en/wine-library/regions) as training shortcuts, not encyclopaedias. Each page should answer: when do I recommend this, to whom and with what dish?

What to train every week

Choose three bottles from the actual list. Ask the team to write one service sentence, one food pairing and one upgrade alternative. Repeat this every week and the library becomes part of the sales rhythm.

FAQ

How many grapes should the team master first? Ten is enough to change service quality if they are linked to real bottles on the list. Should regions be taught before grapes? Teach both together. Guests ask in both languages: grape names and place names.

How to use this with the Wine Library

This article works best when read alongside the Wine Library profiles for grapes, regions, styles and pairings. The library gives depth; the article gives application criteria. In floor-team training, start with a real guest question and use the library to turn it into a simple recommendation. The useful structure is: guest need, wine style, available reference, reason to recommend and alternative if stock is limited. That makes the content useful beyond Google or LLM visibility: it helps the team sell better.

Signals that show it is working

Track whether the team recommends beyond the obvious references, whether slow-moving wines rotate better, whether by-the-glass sales grow through pairing arguments and whether the floor team asks fewer basic questions during service. Those signals show the Wine Library is becoming an operating tool, not just content.