Practical guide · Vaxeron
How to create a digital wine list for your restaurant
A practical checklist for moving from a printed or PDF wine menu to a guest-facing digital list, without losing the character of your restaurant.
Start with the list your team actually serves
Prepare one working catalogue with producer, wine name, vintage, region and bottle size. Check bottle and by-the-glass prices separately. Resolve duplicate entries and outdated vintages before presenting the list to guests. A digital menu cannot correct inaccurate source information on its own.
Separate the working cellar from the guest selection
Decide which wines belong on each restaurant’s menu. Your purchasing catalogue may include wines that are not ready for service or are reserved for another venue. Give one team member responsibility for reviewing the published selection and deciding how unavailable wines should appear.
Tablet, QR code or both?
A QR code opens the wine list on a guest’s own phone: useful when guests want to browse at their own pace. A venue tablet gives the team control over the screen size and presentation, but needs charging, cleaning and a clear handover routine. You can use both routes to the same published list. Test readability, navigation and Wi-Fi at the tables where guests will use it; keep a printed fallback for interruptions.
Standard presentation or bespoke design?
Start with the standard presentation when your priority is getting an accurate, readable wine list into service. Choose bespoke design when typography, layout and the way wines are introduced need a more individual treatment. Vaxeron’s bespoke examples are labelled design concepts; they are not included as standard screens. Agree the scope, price and delivery expectations separately before commissioning work.
Updating prices and availability
Choose who can edit the working catalogue and who checks the guest view before service. Verify bottle and by-the-glass prices, vintages and the selection for each venue after changes. In Vaxeron, published availability follows the configured stock rules and depends on accurate recorded movements. A digital list does not make stock accurate by itself. Any POS connection needs a separate review of the provider, API access and available data.
Test before the first service
Review the list with your team: confirm vintage, bottle size, descriptions, prices and availability, then open the guest view on the intended devices. Keep a practical fallback for a network interruption. Ask staff which steps are unclear and adjust the presentation before extending it to more tables.
What to bring to your demo
Bring your current wine list or a small sample, the number of venues and menus you need, and the devices you plan to use. We can walk through the guest list and the back office before discussing imports or integrations. Review what your plan includes and the cost of extra menus before committing; you do not need to connect your till to request a demonstration.
What to test during a 14-day pilot
Start with a representative selection, one venue and the devices you expect to use. During the pilot, ask staff to find a wine, update a price and check how availability appears to guests. Review what worked and what needs adjustment before choosing a plan. No card is required and the pilot does not automatically become a paid subscription. Extensions up to 30 days can be agreed; existing 30-day commitments remain unchanged. Bespoke design and integrations are scoped separately.