Wine tourism is a $108B market. Forty-five million Americans visited a winery in the last year. Europe's wine routes — Bordeaux, Tuscany, Rioja, Burgundy — attract tens of millions more. The Barossa Valley in Australia alone draws over 1.7 million visitors annually. Mendoza's wine tourism numbers have tripled since 2015.
So why, in 2026, is the best tool most people have for planning a wine trip still a spreadsheet?
We asked ourselves that question for a long time before we decided to build TheWineTrip. Here's what we found.
The existing tools are built for different jobs
TripAdvisor has winery reviews — good ones, often. But it has no concept of a wine trip as a multi-day itinerary. It will show you five wineries in Napa, sorted by rating, with no awareness that you probably can't taste at more than three in a day without destroying your palate, that two of those wineries require reservations made six weeks out, or that driving between them adds forty minutes you haven't accounted for.
Wine Folly is excellent for education. Buy the book. But it doesn't help you plan geography or logistics.
Wanderlog is a great general trip planner. We use it for other kinds of trips. But it treats wineries like restaurants — pin them on a map, add them to a day, done. There's no understanding of tasting appointments, harvest blackout periods, sub-regional variation, or budget reality. Napa in peak season costs $300+ per person per day in tasting fees alone. Mendoza in the same season costs $50. These are not interchangeable.
What makes wine trips genuinely different
Wine trips have constraints that general travel tools don't model:
Appointment culture. Many serious producers — in Burgundy, in Priorat, in Barossa — don't accept walk-ins. You email, you wait, you get a reply in French or Spanish, you confirm a time that may or may not survive a harvest emergency. A planner that doesn't surface this leads to real disappointment.
Harvest timing. Visiting Champagne in October during harvest is a completely different experience from visiting in July. Mendoza's harvest season in March means crowds and limited producer availability. Timing your trip to a region's rhythm matters enormously, and no tool was surfacing this clearly.
Sub-regional complexity. "Rioja" is not one place. Rioja Alta, Rioja Alavesa, and Rioja Oriental produce recognizably different wines, are geographically spread, and have different producer concentrations. Same story in Burgundy — Côte de Nuits and Côte de Beaune are distinct enough to deserve separate itineraries for serious wine travelers. Collapsing all of this to a single pin on a map loses the plot.
Budget variance. This one surprised even us when we ran the numbers. The gap between the most expensive and least expensive regions we cover spans a factor of six or more — tasting fees, accommodation, restaurant pricing, transport costs. A planning tool that doesn't model this cannot produce a usable itinerary.
Language barriers. Booking tastings in Douro means emailing in Portuguese. Alsace producers often correspond in French or German. This is a real friction point that prevents travelers from accessing the best experiences.
What we built
TheWineTrip is API-first. That's not a buzzword — it's a structural choice that changes what the platform can do.
We've mapped 18 wine regions with structured data: GPS-coordinated wineries, tasting fee ranges, appointment requirements, peak and harvest seasons, accommodation tiers, and sub-regional breakdowns. All of it queryable via a clean REST API with an OpenAPI spec.
The planner generates structured itinerary output that AI agents can consume. Pass it a region, a date range, a budget, and a style preference, and it returns a day-by-day plan with actual producer suggestions, realistic timing, and honest cost estimates.
This matters because the next generation of travel planning isn't happening in browser tabs — it's happening in Claude, in ChatGPT, in agent workflows that need structured, reliable data to work with. We built for that.
What's coming
More regions. We're adding McLaren Vale, Wachau, Stellenbosch, and the Finger Lakes in the next quarter.
An MCP server for Claude Desktop users — so you can ask Claude to plan your wine trip and it will call our API directly for real data, not hallucinations.
An affiliate accommodation layer that surfaces stays with genuine wine-region context — vineyard hotels, agriturismos, wine estates with rooms — not just whatever hotel has the most reviews near the city center.
Try it now
The planner is free. No signup required. Pick a region, tell us your dates and budget, and see what it generates.
We're a small team of wine-obsessed builders. If you find something wrong, something missing, or something that could be better — we want to hear from you. That's what the early days are for.