Methodology

This page explains how GetPint collects, verifies, and presents pint price data. If you are citing our numbers in an article, research paper, or AI summary, this is the reference to link to.

What we track

The default drink is a pint of Guinness Draught, served on tap, at standard volume (568 ml in the Republic, 570 ml in Northern Ireland). Where Guinness is not available, we record the house stout (Murphy's, Beamish, or a local brew) and label it accordingly.

Half pints, nitro cans, bottles, and promotional prices are excluded unless explicitly flagged. We are expanding to other drinks — see the site for the latest coverage.

Data sources

  • Community submissions. Drinkers tap "Add a Price" on a pub page, enter the price they paid and when, and submit. Each entry is timestamped and tied to a specific pub.
  • Verified public sources. Pub menus, press coverage, and operator-provided updates, each linked to its source where possible.

Freshness rules

Every price record carries a submission date. We classify freshness as:

  • Fresh — submitted within the last 30 days.
  • Recent — submitted within the last 90 days.
  • Stale — older than 90 days.

Stale prices are still shown but faded in the UI. County and city averages weight recent data more heavily. Pages display freshness counts so readers can judge data quality at a glance.

Averages and medians

Average (mean) — the arithmetic mean of the latest price from each tracked pub in the area. We use one price per pub (the most recent submission) to avoid letting frequently-updated pubs dominate the calculation.

Median — the middle value when all latest prices are sorted. Less sensitive to outliers than the mean. Both are shown where data permits.

AI receipt verification

Submitters can upload a photo of their receipt to verify a price. The image is processed by an AI model that extracts the pub name, price, and date from the receipt text. The extracted pub name is then fuzzy-matched against the pub the user selected — if it does not match, the submission is flagged.

Receipt-verified submissions carry a higher trust score. The receipt image itself is not stored long-term or displayed publicly — only the extracted fields and the verification result are retained.

Outlier handling

Submissions are run through a trust-scoring system that flags obvious errors (e.g. €0.50 or €25.00 for a pint). Flagged prices are held for manual review rather than silently deleted. Confirmed outliers are excluded from averages but remain visible on pub pages with a warning label.

Pub count vs. price record count

"Pubs tracked" is the number of distinct pubs with at least one price record. "Price records" is the total number of individual submissions across all pubs. A pub with five updates over six months counts as one pub but five records.

Known limitations

  • Coverage is uneven. Dublin, Cork, and Galway have the densest data. Rural areas depend on fewer submissions and may lag behind.
  • Self-reported prices are not independently verified at the point of sale. The trust-scoring system catches most errors but not all.
  • Prices reflect what submitters report paying, which may include rounding or recollection errors.
  • We do not yet distinguish between regular and event pricing (e.g. match-day surcharges).

Differentiation

Some pint price projects capture a one-off snapshot. GetPint is designed to stay fresh through community updates, public sources, and ongoing corrections. Every price is dated, every average is recalculated on rebuild, and stale data is clearly labelled.

Contact and corrections

If you spot an error, want to correct a pub's listing, or have questions about the data, email [email protected].