Glossary
brewery establishment record
A brewery establishment record is the unit of observation used by Open Brewery DB: one row or JSON object per physical brewing venue rather than per company. The corpus spans 11,822 records covering breweries, cideries, brewpubs and bottleshops across every delivery format the project ships.
What is a brewery establishment record?
It is a venue-level row, not a corporate one. Open Brewery DB defines its granularity as 'One row per physical establishment (brewery, cidery, brewpub, bottleshop)', so a single brewing company operating three taprooms appears as three records.
Delivery keeps the same grain across formats: the GitHub repository ships 'One CSV row per establishment, partitioned by country then state/province', while the API returns 'One JSON object per establishment' with list endpoints paginating at up to 200 records per page.
Why does the establishment unit matter when choosing a dataset?
Because company-level counts distort market density. A state with many small brewpubs looks 'under-served' if you count companies but correctly saturated if you count venues - the establishment record is what site-selection and distribution analyses need.
Type coverage matters equally: since bottleshops and cideries sit inside the same corpus, any 'number of breweries' claim must first filter by establishment type or it silently inflates counts. And because pagination caps at 200 per page, bulk work should take the file route rather than paging the API thousands of times - the CSV/SQL downloads exist precisely for that.
How do you evaluate brewery establishment data in a source?
- Confirm venue-level grain. One row per physical establishment is the standard; company-aggregated files have already destroyed venue detail.
- Check type fields. Brewery, cidery, brewpub and bottleshop classifications must be filterable for accurate category counts.
- Benchmark corpus size. 11,822 records is the published total; large deviations need explanation.
- Match format to workload. Country-then-state partitioned CSVs suit bulk analysis; the 200-per-page API suits lookups, not full mirrors.
Related terms
- bulk-csv-json-sql-download - the file delivery channel for these rows.
- keyless-api-access - the no-signup API serving them live.
Sector hub: brewers data.
Frequently asked questions
How many brewery establishments does Open Brewery DB cover?
11,822 records, each representing a physical establishment such as a brewery, cidery, brewpub or bottleshop.
Does an establishment record mean one company?
No. Each record is one physical venue; a company running multiple locations appears once per location.
Datasets containing this field
Datasets containing brewery establishment record
6 datasets carry brewery establishment record in the catalog. Open one, count the fields, judge for yourself.
Open Brewery DB — API Documentation
Every listing shows the field dictionary, sample rows, and coverage before you commit. API, files, or your warehouse. Daily, weekly, or hourly.
Get sample rows