BarleyPowered by Brewlytics.ai

How to Turn Brewery POS Sales Data into Marketing Campaigns

By · Founder, Brewlytics.ai

Operator7 min readOutcome: Build five campaign audiences from your POS transaction history and run the first one this week
A manager's hands sorting a long curl of printed receipt tape into five piles, each weighted with a different bottle cap, on a worn wooden desk under a brass lamp in a brewery back office after close.

Short Answer

Turn brewery POS sales data into marketing campaigns by building audiences from customer-linked transactions, not from sales totals. Five plays work from POS data alone: win back regulars whose visit gap has doubled, alert recent buyers when their beer or style is freshly tapped, cross-sell guests stuck on one style, split taproom drinkers from package-only buyers, and seed special-release waitlists from past release-day buyers. Measure each by visits or purchases within a set window, and only message customers who opted in to marketing.

Barley's Take

Your register already knows who stopped coming in. It just has never been asked the question.

Why This Matters for Breweries

Every brewery POS can tell you that the Hazy IPA outsold the Pilsner last month. That report is useful for brewing schedules and almost useless for marketing, because a campaign does not go to a beer. It goes to a person.

The same system that produced the sales-by-beer report is sitting on something far more valuable: a record of who bought what, when, and how. Most modern brewery POS systems, Square included, can attach a transaction to a customer when a guest gives a phone number, joins loyalty, or pays with a saved card. Line those records up and you can answer the questions that actually fill a Thursday. Who stopped coming in? Who bought the last batch of the hazy that just got rebrewed? Who only ever buys four-packs of cans to go?

Most breweries never ask, so they fall back to the one campaign that needs no data: the weekly email to everyone. This playbook is the alternative. Five campaigns, each built from POS history alone, each with a clear audience rule and a way to tell whether it worked.

How It Works

Before the plays, one definition. A customer-linked transaction is a sale your POS has tied to an identifiable guest record. Anonymous cash sales and unrecognized cards do not count. Your campaign audiences can only be as big as that linked share, which is why a loyalty sign-up or phone lookup at the register matters more than it looks.

You need three fields on each line item: the item (which beer, which format), the timestamp, and the channel (draft pour in the taproom versus a package sale to go). Everything below is built from those three.

The five plays at a glance

Five kraft-paper table tents on a copper bar top, each printed with a single white icon: an hourglass, a keg, two pint glasses, a can beside a pint, and a ticket.
Five kraft-paper table tents on a copper bar top, each printed with a single white icon: an hourglass, a keg, two pint glasses, a can beside a pint, and a ticket.
PlayAudience ruleTriggerMeasure
1. Lapsed-regular win-backDays since last visit ≥ 2× their usual gapGap crosses the thresholdReturn visits within 14 days
2. Fresh-release alert to recent buyersBought this beer or style in the last 90 daysKeg tapped or batch packagedPurchases of that beer within 7 days
3. Style cross-sell80%+ of orders in one style familyA neighboring style goes on tapFirst purchase of the new style
4. Taproom vs. package splitDraft-only, package-only, or bothWeekly send, different content per groupVisits (draft) or package sales (to-go)
5. Special-release waitlistBought on a past release dayRelease announcedWaitlist sign-ups and release-day pickups

Play 1: The lapsed-regular win-back

Sort customers by their average gap between visits, then flag anyone whose current gap is at least double it. A weekly regular gone three weeks is lapsing. A once-a-month guest who has not been in for five weeks is not, yet. One cutoff for everyone gets this wrong in both directions.

The message should name what they used to order, not offer a discount first. "The Porter is back on" does more for a porter regular than 10% off anything.

Play 2: Fresh-release alerts to recent buyers

When a beer gets rebrewed, the people who bought the last batch are the warmest audience you will ever have. Pull everyone who purchased that beer, or its style family, in the last 90 days. Send when the keg is tapped or the cans are packaged, not when the newsletter is due. For more on why the dated event is the trigger, see fresh beer alerts.

Play 3: The style cross-sell

Some guests order the same style every single visit. If 80% or more of a customer's orders sit in one family, they are telling you what they like and, by omission, what they have never tried. When a neighboring style goes on, such as a West Coast IPA for a hazy loyalist or a Baltic porter for a stout drinker, invite that group specifically. Keep the ask small: a taster pour, not a full pint.

Play 4: Split taproom drinkers from package buyers

The channel field splits your list into three groups: draft-only, package-only, and both. They want different messages. Taproom drinkers care what is pouring tonight. Package buyers care what is in the cooler, the package date, and whether that four-pack will still be there Saturday. One email trying to serve both is half-irrelevant to everyone who opens it.

Play 5: The special-release waitlist

Anyone who bought on a past release day has already shown they will plan around one. Seed a waitlist from that group before the public announcement: an early heads-up, a reserved allocation, or a pickup window. It rewards the people who make release days work, and it tells you roughly how many cans to hold back.

Example Brewery Scenario

Kestrel Yard Brewing runs a 10-barrel brewhouse, a taproom that pours about 35,000 pints a year, and a busy to-go cooler by the front door. They are on Square. In 12 months of transactions, 1,450 guests are customer-linked, and 610 of those have opted in to marketing texts or email.

A woman lifts a four-pack of cans from a brewery's glass-door to-go cooler in afternoon window light while a staff member waits at a counter with a tablet register.
A woman lifts a four-pack of cans from a brewery's glass-door to-go cooler in afternoon window light while a staff member waits at a counter with a tablet register.

In September, they ran all five plays against that history:

  • Win-back: 38 opted-in regulars had a current gap at least double their norm. Each got a text naming their usual, including 11 Slow Burn Imperial Stout regulars who heard it was back. 14 came in within two weeks.
  • Fresh-release alert: Glass Lantern Hazy IPA was rebrewed. 120 opted-in guests had bought it or another hazy in the last 90 days. They got the alert the afternoon it was tapped, and 47 bought a pint or a four-pack within a week.
  • Style cross-sell: 52 hazy loyalists were invited to a free taster of the new Two Ferry Pilsner. 19 ordered a full pour.
  • Taproom vs. package: 180 package-only buyers stopped getting the tap list and started getting a Thursday cooler update with package dates. That group bought 265 four-packs the next month, up from 212.
  • Waitlist: 90 guests who bought on the last two release days got a 48-hour head start on the Bramble Gose can release. 64 reserved; 58 picked up.

None of it needed a survey. All of it came from data Kestrel Yard already had.

Practical Checklist

Barley points at a printed checklist with one box ticked while a brewery owner in reading glasses marks it with a pen at a taproom table, beside a laptop and a half-finished pilsner.
Barley points at a printed checklist with one box ticked while a brewery owner in reading glasses marks it with a pen at a taproom table, beside a laptop and a half-finished pilsner.
  • Find your linked share. What percentage of last month's transactions are tied to a customer record? If it is under a third, fix capture at the register before building campaigns.
  • Export 12 months of customer-linked transactions with item, timestamp, and channel. A spreadsheet is fine for the first pass.
  • Calculate each customer's average visit gap and flag everyone at double it. That is your first win-back list.
  • Tag every item as draft or package, if your POS does not already separate them.
  • Filter every audience to marketing opt-ins only. A number from the card reader is not consent; the brewery SMS guide covers what is.
  • Run one play this week. Win-back is the easiest to measure and usually the fastest to pay off.
  • Write down the window before you send (7 or 14 days) and count visits against it afterward.

How Brewlytics Helps

Brewlytics does this work continuously instead of in a spreadsheet once a quarter.

At dusk outside a brewery's open garage door, guests line up for a can release pickup while one guest in the foreground holds a phone showing a simple ticket notification.
At dusk outside a brewery's open garage door, guests line up for a can release pickup while one guest in the foreground holds a phone showing a simple ticket notification.
  • POS Sync backfills 12 months of Square transactions on connection, so visit cadence and menu-level insight are available from day one. Square is live today, with Toast next on the roadmap and Arryved third.
  • Customer Segments in Customer Insights build automatically: at-risk regulars flagged against their own visit baseline, first-timers, high-value guests, and taste segments like Hazy IPA lovers that fill in as customers opt in and engage. Any segment exports as CSV with consent flags.
  • Campaign Triggers fire when a regular goes quiet, a new beer drops, or a customer hits a loyalty milestone, and send over iMessage, SMS, or email to customers who opted in.
  • Attribution shows sends, opens, and attributable visits per campaign in the dashboard, so the measurement step is not a separate project.

For how these campaigns fit alongside events, social, and email, see the complete guide to brewery marketing. For which automations to hand to software and which to keep human, see automated marketing for breweries.

FAQ

(See the schema-ready FAQ block at the end of the page for the full set: required POS data, finding lapsed customers, texting consent, taproom vs. package messaging, measurement, and minimum list size.)

Ready to see who your POS says stopped coming in?

Your transaction history already holds the win-back list, the release waitlist, and the cross-sell audience. The only question is whether anyone reads it.

Book a demo and bring your Square account. We will show you the at-risk regulars in your own data. → See how Brewlytics works if you would rather look first.

Frequently asked questions

Related Brewlytics Feature

Campaign Automation

Taste-segmented iMessage, SMS + email that runs itself once it's wired up.

See how it works →

Want to see this working in your brewery?

Go Pro to see your customers and act on the data — taste profiles, segmented iMessage, SMS + email campaigns, the AI bartender, and the full dashboard. Or book a walkthrough with the brewer who built it. Not ready? Start free, no card.

Just here for the beer? Get the free Barley app