The Anti-Check-In: Why We Skip the Feed
Why fresh tap lists shouldn't depend on social posting.
Untappd is a social network first and a beer database second. The two roles are in conflict, and you can see the seam every time you open a pub's tap list and find it hasn't moved since the last person felt like doing a check-in — often days ago, sometimes weeks. The tap list isn't a picture of what's on. It's a picture of what people posted about.
PINtPOINT now lets you improve any pub's tap list with one tap. No check-in. No feed post. No badge. And critically — no requirement that you actually drank the beer.
The check-in as gatekeeper
There's an exception. Verified venues — publicans who've claimed their pub on Untappd Business and upload a curated menu themselves — get a proper published tap list. When those work, they work well, and they're the ideal case. But verified venues are a small minority of the pubs anyone actually drinks in. For everyone else, and that's most of them, Untappd's tap list is inferred from check-ins.
The inference goes like this: someone drinks a beer at that pub, opens Untappd, taps check in, picks a beer, rates it, adds a photo, tags a friend, posts it to their feed. Every beer on those unverified tap lists is the residue of a public social act. If nobody at the pub feels like broadcasting their pint on a Tuesday night, the tap list rots for a week.
Untappd's data model has a single input event: the check-in. It bundles four separate things — "I saw this beer," "I drank this beer," "I have an opinion about it," and "I want my followers to know I drank it" — into one action. That bundling is elegant if the goal is a social network. It's a problem if the goal is a fresh tap list.
Consider what it excludes. You went to the pub, saw a great cask ale on the handpull, ordered the cask ale, drank the cask ale — but you don't want to check in because your feed is your feed and not everything belongs on it. Untappd's tap list doesn't learn from your visit. You saw six beers on tap, drank one, and could describe every pump clip from memory — Untappd's tap list learns about at most one of them, if you check in.
Now consider the friend who was with you and had a lager. Their check-in updates the tap list. Yours doesn't. The state of the world according to Untappd is: the pub had one lager on tap that Tuesday. Which is what makes their tap lists look the way they look.
The check-in bundles "I saw this beer" and "I want everyone to know I drank it" into one action. Untappd tap lists are only as fresh as the people willing to do the second thing.
What the anti-check-in looks like in PINtPOINT
Open a pub, tap Log a beer, paste the Untappd link for the beer that's on. That's the whole flow.
The transaction
- Find the beer on Untappd (search from inside the app if you don't already have the URL).
- Copy the URL from the address bar. Or the beer ID number — either works.
- Paste it into PINtPOINT's Log a beer modal, pick a serving type, tap Add.
- The beer appears on that pub's shared tap list for every PINtPOINT user.
There is no check-in event on our side. Your Untappd feed is untouched. No friends are tagged. No badge fires. The beer's canonical identity — its name, brewery, style, ABV — stays anchored to Untappd's canonical beer page, so the same beer at three different pubs is the same row in our database. The only user input is the URL. You didn't have to drink the beer. You didn't have to like it. You didn't even have to have a beer at that pub yourself. You saw a pump clip, you knew what it was, and you told the next drinker.
Why this compounds
The gap between "did I drink this?" and "did I see this?" is quietly enormous. Every regular sees dozens of beers a week they don't drink. Every pub-crawler notices what's on at pubs they only walk past. Every publican working the bar has perfect knowledge of their own current tap list and no incentive to publish it as a series of check-ins on their personal Untappd account. All of that knowledge is stranded on Untappd because the only way to contribute it is to pretend you drank the beer.
Multiply that across a year and a city and you get the tap-list quality gap PINtPOINT is closing. Untappd's tap lists reflect check-in behaviour, filtered through people's willingness to broadcast. PINtPOINT's tap lists reflect what's actually on. Same underlying beer identities — Untappd's canonical beer_id — but a different contribution contract. Less social, more useful.
What it isn't
It isn't a substitute for Untappd's check-in graph. Ratings, badges, personal history, the social feed — that's what Untappd is for and it does that better than anyone. If you want to keep a lifetime record of every beer you've ever drunk with a friend list and a scoring rubric, use Untappd. PINtPOINT doesn't try to replace any of it.
It also isn't free-form. You can't type "IPA" into the log-a-beer field and have it appear at your local — the input is only an Untappd beer URL or ID, and the beer identity comes from Untappd's canonical page. This is deliberate. Free-form beer names collide (four breweries make a beer called Trinity, three make Session IPA, dozens make Pale Ale), and one wrong guess about which brewery it is corrupts the data for everyone. Every beer that lands on a PINtPOINT tap list, whether it came from our Untappd scrape or from a user's anti-check-in, has the same identity anchor. The contribution surface is narrow on purpose.
The pitch is not that we've solved beer discovery. It's that we've removed one specific friction — the requirement to publicly broadcast your own consumption in order to update the shared record — and that removing it makes the shared record noticeably better.
What we owe you back
If you tell the app what's on at a pub, we do two things. First, we render it: your addition appears on that pub's tap list, alongside our scrape, for every drinker who opens the app after you. Second, we push it: if any of your watched beers land on nearby taps because of your own additions or someone else's, you get a notification. The contribution loop closes on the drinker who cares, not the drinker who checked in.
Nothing you add inside PINtPOINT goes back to Untappd. No check-in fires on your Untappd feed, no friends get tagged, no badge advances. We don't ask for your Untappd account, we don't read your feed, we don't touch your personal history.
What we do use from Untappd is what's already public: venue pages, beer pages, verified-venue menus — the same URLs any browser can hit. That means if you check in on Untappd at a pub, your check-in becomes one of the public signals our venue-scrape reads to keep that pub's tap list current. We don't store your username against it — we take the beer identity and the fact that it was on tap, and drop the rest. The two apps sit next to each other and can be used together or separately. The only shared vocabulary is the beer_id, which is the one bit of Untappd's system that everyone benefits from being canonical.
The pub in front of you is right now pouring some beers. If you know what they are and Untappd doesn't, help the next drinker. No feed post required.