Vinovoss Wine Catalogue & Case Pricing Dataset, Twice a Week
The same 30-column Vinovoss wine file as the daily feed, captured twice a week — bottle and case pricing, unit inventory, seller, winery, grape, region, vintage, alcohol band, ratings and a tasting description.
Two captures a week is the right cadence for assortment and range work: in the sample, 40 wineries across Piemonte, Napa, Mendoza and South Australia, 10,061 bottles of stock, and case ladders on 40 of 50 rows.
The file already exists, because this pipeline runs twice a week whether you buy it or not. Most vendors start collecting after you order — which is why they quote a lead time. Here the most recent file is in your account within minutes of payment, with an API key issued at the same time.
What you get, in plain terms
Four things. Catalogue depth at a cadence that suits range work.
Bottle, 3, 6 and 12-bottle prices
Price is JSON holding the whole ladder — “1 bottle $36.70, 3 bottle $33.95, 6 bottle $31.95, 12 bottle $29.95” — so case discounts are readable, not inferred.
Unit inventory per listing
Inventory Count gives the number of bottles the seller shows as available, which is depth of stock rather than a yes-or-no flag.
Wine attributes, already structured
Winery, Grapes (pipe-separated for blends), Region, Vintage ID and an alcohol band sit in their own columns, with a tasting description of around 100 words.
However you want it
Direct download, REST API, Amazon S3, Google Cloud, Snowflake or SFTP. The API key comes with the dataset.
Fields included in this dataset
All 30 columns, in the exact order they appear in the file — taken straight from the sample, not from a brochure. The free sample ships with a data dictionary giving an example value for each one.
Sample rows from the real file
Real rows from the sample file, not an illustration. The supplied sample has 50 listings with all 30 columns.
Coverage
Captured twice a week across vinovoss.com. One row is one listing of one wine by one seller, timestamped in Scraped Datetime.
| Metric | In the supplied sample | What it tells you |
|---|---|---|
| Rows | 50 listings · 40 wineries | Mostly 750 ml |
| Price ladder | 3 or more steps on 40 rows | 1, 3, 6 and 12 bottles |
| One-bottle price | $20.95 – $192.95 | Median $36.95 |
| Inventory | 4 – 1,200 units · 10,061 total | Median 82 bottles |
| Regions | Piemonte 10 · California 8 · Napa 5 | Plus Mendoza, South Australia |
| Alcohol band | No Alcohol through very high | Six bands, on every row |
Only tracking a region, a grape or your own SKU list? Send the list and we will price a narrower file.
Historical data
The last 30 days come with the dataset. Beyond that we hold Vinovoss records from February 2025 onwards.
Ask about historical dataNeed more data points?
We can extend this dataset beyond the standard 30 columns — the price ladder flattened into columns and vintage split from the wine name are the most requested additions.
Request custom fields“We do not need wine prices twice a day. Twice a week, with the case ladder and the grape, is exactly the shape of our buying cycle.”
What people use this dataset for
Importers and distributors
See which of your wines are listed, at what bottle and case price, and how deep the stock runs.
Retailers and e-commerce teams
Benchmark your wine list against a live marketplace on price, vintage and region.
Wine tech and app builders
Enrich a catalogue with region, grape, vintage and ratings without building a wine database first.
Analysts and data teams
Track how a marketplace's assortment and pricing shift by region and grape over time.
About Vinovoss wine data
Vinovoss is a wine marketplace and discovery platform where independent merchants list their inventory with full producer detail. Twice a week keeps a catalogue current without paying for a speed that range planning does not use.
Breadth across regions
The sampled listings spanned Piemonte, California, Napa, the Central Coast, Mendoza and South Australia, across 40 different wineries — the kind of spread that makes region-level benchmarking possible.
Case pricing is the point
Forty of the 50 sampled rows carried a full four-step price ladder from one bottle to twelve. Wine trades on the case price as much as the bottle price, and this is the rare feed that publishes both.
Two things to plan for
Six of the 50 sampled rows had no price, seller, bottle size or inventory behind them. Category holds a breadcrumb — “Home | Ancient Peaks Merlot” — rather than a real category, so group on Region or Grapes instead.
Built for matching, too
client_id, price_per_bottle and client_price hold your own catalogue's reference and price beside the marketplace's, and vinovoss_url gives the matched wine page. Send us a SKU list and the file comes back joined to it.
Is collecting this data legal?
We collect only what is publicly visible on a wine listing — producer, region, grape, vintage, price, availability and the retailer's own description. No account is created, no age gate is circumvented and no personal data is touched, so the file holds no consumer records. These are age-restricted products: the data describes what is listed publicly, and what you may do with it depends on your own market's rules. Producer names, tasting notes and imagery stay the property of their owners; the licence covers the compiled dataset.
Frequently asked questions
Customer Average Rating actually holds the number of customer ratings and Customer Ratings holds the average score — the two names are swapped in the source. Expert Ratings carried a score on every sampled row; Critic Ratings was 0 throughout.
