Pour5

Your register counts drinks, not bottles

Your register rang up every drink tonight and never once rang up a bottle. That gap is where inventory drifts.

A bar register drawn in ink: a tablet showing a grid of glass icons, one rocks glass lit in bourbon as the drink just rung up. Behind the screen, on a packed shelf, the whiskey bottle it came from, two thirds full, the only other color.

Your register rang up every drink tonight, and it never once rang up a bottle. It counts units: one Negroni, one beer, one single. A bottle of liquor isn't a unit. It's 750 milliliters, going out a pour at a time in whatever size the drink called for, over days or weeks, sitting part-full for nearly all of that time. That's the whole problem, and it isn't a software bug.

The mismatch is physical, not technical

A unit and a reservoir aren't the same thing

Someone orders a rum and coke. The bartender pours it, the register rings "1 rum and coke," a card gets charged, and as far as the point of sale is concerned that transaction is finished. It did its job. Somewhere behind the bar, the bottle that pour came out of still has about twenty-four ounces in it, and may sit there part full for another two or three weeks, depending on how often someone orders from it. The register has no way to know that, and it was never built to.

That's the fact everything else here comes back to. A POS decrements units. A bottle isn't a unit, it's a reservoir: one object that gets a little emptier with every pour, sits open on a shelf between pours, and doesn't finish being sold until the last ounce is gone, sometimes weeks after the first one left. Ring up a sale and the system can tell you a drink went out the door. It can't tell you what's actually left in the bottle that supplied it, because nothing about a sale event carries that information forward.

Where it actually breaks

A Negroni pulls partials from three bottles. One drink, three spirits, each pulled at a different rate. The register logs "Negroni, 1." It has no idea it just touched three separate reservoirs, so nothing about that sale tells you the gin moved faster than the vermouth this week, or that the Campari you're running low on came almost entirely from cocktails, not from anyone ordering it on its own.

A single is usually 1.5 ounces. Not always. The POS records the sale at whatever size is on the menu. The bottle empties at whatever size actually left the spout, and those two numbers drift apart a little more with every shift.

"Make it a double" changes two things, and the register only sees one. The price goes up, that part's easy. The depletion should double too, and on most systems it doesn't, because the item on the register is still just "Negroni" with a modifier, not two units of gin coming out of the well.

Spills, comps, staff drinks, and tastings are real consumption with no sale attached. A round on the house, the pour someone tastes to check a keg, the glass that gets knocked over: all of it is liquid actually leaving a bottle. None of it rings anything up, so none of it shows up anywhere the register looks.

What the blind spot costs you

You can't see what it should be

None of this is dramatic on any single night. A quarter ounce here, a comp there, a double that only counted once. The cost is that you can't see it. To know what a bottle should have left, you need every drink that draws on it, and the register only tells you drinks.

You can work it out. Take the gin. Find every item on the register that pours from it, and what each takes:

Singles
40 × 1.5 oz = 60 oz
Doubles
10 × 3 oz = 30 oz
Negronis
25 × 1 oz = 25 oz
Martinis
12 × 2.5 oz = 30 oz
The gin
145 oz, about 5.7 bottles

That is one bottle, for one week. Now do the vodka, the rum and everything else on the back bar. So most weeks you take the count as the answer, maybe with a hunch that the gin is moving faster than it should, and nothing to hold that hunch against.

Your pour cost, your margin on a category, the variance report that says you're three bottles short: all of them start from a picture of the shelf that the register was never able to see. You aren't being lied to. You are being told, accurately, about something else.

A sale, taken apart

A drink is a list of withdrawals

So we stop treating a sale as one event and start treating it as what it actually was. The register says "Negroni, 1." A Negroni is equal parts, an ounce each of gin, Campari and sweet vermouth, so that sale was three withdrawals from three different reservoirs, not one unit of anything.

We hold that mapping, so a sale coming off the register turns into amounts leaving specific bottles. A single of the same gin takes an ounce and a half. A double takes three. The Negroni takes one. All of it comes off the same gin, because it is the same gin.

The register carries on doing the job it is good at, which is telling us what sold. It was never built to know what each sale used up from the bottles.

Not a knock on your register

A register is excellent at what it does. It authorizes cards, splits checks, tracks tips, and closes out a shift fast enough to survive a Friday rush. We integrate with Square for exactly that reason. It is good software, doing the job it was built for.

We are not going to tell you your POS is bad. It was built for a different job. Selling things is the job. Modeling a slowly draining reservoir that gets touched by a dozen different drinks in a dozen different amounts was never part of the brief, and no register vendor claims otherwise.

And the mapping only knows what a drink was supposed to take. We cannot see the spout. A heavy hand on a Friday leaves the bottle further down than any recipe says it should be. We catch that at the count, not at the pour: we know what should be left, so a bottle that is lower stands out, and if the gap matters, we bring it to you.

We share each new essay on LinkedIn. Follow Pour5 there.