QR codes for bars and pubs
Cocktail menus, tabs, and tip jars that actually get used.
Bars operate under one truth that separates them from restaurants: the menu is semi-live. A spirit runs out mid-shift, a cocktail gets 86'd because the garnish is gone, happy hour starts at 5 and ends at 7, and the beer list rotates more often than most restaurants change their plates. The printed menu can't keep up โ which is why most bars never had a real printed menu in the first place. A chalkboard above the bar, yes; a laminated folder, rarely. A QR on every corner of the bar pointing at a live menu page is what the chalkboard was trying to be, with pricing, staff picks, and real-time availability baked in. The UK pub chain Wetherspoons built an entire service model around its Order & Pay app in the late 2010s โ customers order to a table number from their phone, drinks arrive, the bar moves substantially higher volume than a counter-service model at comparable staff levels. It isn't QR-first by design (the app shipped before native camera scanning was standard), but the table-number-plus-order flow is the same shape as a QR-triggered mobile ordering pattern. Toast, Square for Restaurants, and Lightspeed all offer bar-specific modules that handle the tab model: card added once, tabs run all night, closeouts happen contactless even when the bartender is slammed. Three patterns earn their keep. A live cocktail menu that hides sold-out items, so the queue doesn't order a drink the bar can't make. A digital tab that doesn't require running the customer's card three times through the night. And a digital tip jar for the increasingly card-only clientele โ the one that matters more than it sounds. Card-paying customers tip at roughly 60% of the rate of cash customers when there's no obvious tipping UX, and the gap closes almost entirely when a QR gives them a frictionless way to leave a few dollars. In a tight-margin service business, closing that gap is meaningful compensation for bar staff.
Live cocktail menu that reflects what you can actually pour
The sold-out cocktail is a small embarrassment that happens a dozen times a night in a busy bar. A QR on the table pointing at a live menu page โ where out-of-stock cocktails are hidden or greyed-out โ eliminates it. The operational requirement is a bartender who can toggle items from a phone during service; most POS systems support this natively now (Toast, Square, Lightspeed), and the few that don't let you drive a dedicated menu app via an Airtable or Notion page. The detail to get right: the menu must load in under two seconds on cellular in a basement bar with weak signal, which means no hero images, no video, no bloated JS framework. Flat HTML, one print-sized list, dynamic hide/show by stock status. The bar up the street with the sophisticated menu app nobody can load in their basement has a worse experience than the bar with a fast static site and honest scarcity.
Digital tab that doesn't fight the bartender
The 2am closeout problem is real: a bar running on individual card-swipes per drink burns 15โ30 seconds per transaction at peak, which compounds through the last hour of service. A tab model fixes this โ the customer's card is authorized once on arrival, held open, and closed out at the end โ but historically the tab model has required either a physical card left at the bar (liability, lost cards) or a staff-managed ledger (slow, error-prone). A QR tab model gets both benefits: the customer scans, adds their card once, orders through the night through their phone or via the bartender who sees their tab, and closes out contactless. Toast's Tab feature and Square's comparable functionality both implement this pattern. The adoption curve in my experience: busy bars that try it for a weekend keep it forever; quieter bars don't see enough of a win to bother.
Tip jar for a card-only clientele
The tip-jar gap is the quiet crisis in bar economics. As cash use has declined in most US and European markets, the tip-jar ritual โ customer pays cash, drops ones in the jar, bartender acknowledges โ has fewer natural moments. Card terminals sometimes prompt for tips, but the UX varies by processor and many younger customers tip zero at terminals they perceive as corporate. A small framed QR near the register pointing at a Venmo, Cash App, or Stripe tip page closes the loop. The rule I've seen work: make the destination the tip pool (not a bartender's personal account), rotate the destination monthly if shifts change, and print the tip amount suggestions as part of the framed sign ('$3 ยท $5 ยท $10') rather than leaving it to the customer to type a number. The sign + suggested amounts pattern consistently outperforms the bare QR by a factor of 2โ3ร in tip frequency.
Printing and placement tips
- Keep codes away from condensation zones. A QR laminated in the ice well is hard to scan after one shift; behind the POS is better.
- Dim warm lighting is the enemy of colored QRs. Stick to black-on-white for bar-top codes; reserve branded palettes for menu pages, not the code itself.
- Rotate the tip-jar destination monthly if your bar splits tips by shift. A sign pointing at last month's bartender's Venmo is an uncomfortable conversation.
Build one now
The free generator handles every pattern above. Upgrade to Pro when you want dynamic destinations or scan analytics on top.
Further reading and sources
- J D Wetherspoon โ Order and Pay โ The UK pub chain's table-ordering app (QR-adjacent table-number flow)
- Toast Tab โ contactless ordering at bars โ Bar tab and ordering at the table
- Square for Restaurants โ bar module โ Bar-specific POS features
- Untappd for Business โ Menu platform used by many US craft-beer bars, QR-friendly