Bar Stock Control: The Tightest Ship in the House
The bar is where hospitality margins go to be tested — pour discipline, nightly bottle counts, empties and deposits, and the variance math that makes the tightest ship in the house.
Every hospitality operator eventually learns the same lesson: the kitchen loses money in percentages, the bar loses it in bottles. Liquor is dense value in portable form, sold in pours nobody weighs, in an environment designed to be convivial rather than supervised. That combination makes the bar the single most leak-prone point in the house — and, paradoxically, the easiest to lock down, because unlike a kitchen, a bar's stock is countable to the shot.
The arithmetic that runs a bar
A bottle of spirits is a fixed number of portions: a 750ml bottle at 25ml pours is 30 shots — 28.5 with an honest spillage allowance. Every bottle issued to the bar should therefore produce a knowable revenue, and the nightly reconciliation is three numbers:
- Consumption by count: opening bottle levels + issues − closing levels, in tenths of a bottle (or by weight — a bar scale reads a bottle's remaining pours in seconds).
- Sales by POS: what the till says was sold, item by item — tots, cocktails (via their recipe cards), bottles served.
- The variance: consumption valued at selling price minus recorded sales. That gap, per night, per bar, per bartender shift, is the number the bar answers to.
Percentage points are bottles
A busy bar turning KES 1.5M a month at a 5% variance is losing KES 75,000 — roughly two bottles of spirits a night walking, over-pouring, or selling off-book. Bars that post the nightly variance where staff see it routinely land under 2% within a month. The math being visible is the control.
Where bars leak, specifically
| Leak | How it works | The counter |
|---|---|---|
| Over-pouring | Generous free-pours, friends' doubles | Measured pourers or jiggers as house standard; variance by shift |
| Own-bottle sales | Bartender's bottle, house's customers, pocketed revenue | Nightly counts + sealed-stock rotation; consumption that exceeds issues is the tell |
| Unrecorded comps | "On the house" without a void trail | Comp button with reason and approver on the POS |
| Cocktail short-pours | Recipe says 50ml, glass gets 35ml, difference accumulates | Measured pourers, a published spec sheet, and periodic test rounds |
| Empties fraud | Refilled premium bottles, recycled seals | Empties broken/marked at count; premium stock sealed and serialized |
| Store-to-bar shrinkage | Bottles vanish between issue and shelf | Issues signed at handover; bar holds its own location stock |
Par levels, issues, and the beverage supply chain
- Each bar carries a par per SKU — enough for the busiest expected night plus margin — and is topped back to par by daily issue, signed at handover.
- Kegs and draught lines get their own math: a 50L keg is a fixed number of glasses; line cleaning and foam loss are recorded allowances, not explanations.
- Empties, crates, and deposits are stock too — beverage suppliers' deposit systems leak real money when nobody counts returns against deliveries.
- Wine cellars run on bin cards with bottle-level counts monthly — low turnover, high value, and the easiest place for a bottle to be "breakage".
The nightly close, bar edition
Fifteen minutes at last call
- Bottle levels counted (or weighed) and entered — tenths matter.
- POS sales pulled by category; comps and voids reviewed with reasons.
- Variance computed and posted — by bar, by shift.
- Cash and M-Pesa reconciled with the same discipline as any till.
- Tomorrow's par top-up requisition raised from tonight's counts.
None of this needs exotic hardware — a bar scale, measured pourers, and a system where issues, counts and the POS meet cover a full-service operation — with your pour measures on a sheet, since no recipe lives in the product. What it needs is the nightly ritual, unskipped, including the nights the owner is buying.
What AWRA OpsHub does today
- The bar as its own location with an independent on-hand position, separate from the main store.
- Issues to the bar as recorded transfers, so what went in is a fact rather than a memory.
- Blind counting with the expected quantity withheld and a permission required to reveal it — which is what makes a bar variance figure mean anything.
- Variance rules that force approval when a count is out beyond tolerance.
- Weighted average cost per item, so a variance can be valued.
More we can add to your workspace
- A pour cost. A recipe and measure definition, so cost per drink and pour-cost percentage compute themselves.
- Par levels per outlet. A per-item reorder point is the closest equivalent.
- Shift scoping. Counts belong to a count session, not to a shift or a bartender, so per-shift variance is not something the system produces.
- A partial-bottle measurement. Stock is whole units unless you define a smaller unit yourself.
- POS depletion by drink, with a recipe linking a sale to a measure.
The practical read: you can run a genuinely rigorous bottle count here, blind, with an enforced reveal permission and a valued variance — which is more control than most bars have. Expressing that variance as a pour-cost percentage is what the measure-level layer above adds.
Anything above that you need, we can build for you
Everything listed above as something we can add describes what ships in the standard product today — it is a starting point, not a limit on what AWRA OpsHub can do for your organisation. Kenya's eTIMS integration and its maintained payroll engine are both in the product because clients needed them and commissioned them; neither appeared by itself, and the same door is open for whatever you just read about. One qualification so this is worth what it claims: a small number of things on this blog we deliberately leave to a specialist rather than build — a statutory ledger we will not sign our name to, a rule that would decide a tax question for you, a clinical or member-funds record that belongs in a regulated system — and where that is true the post says so in those words. Everything else is a scope, a timeline and a price.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
The module-shaped additions, which are the ones readers ask for most often
A price list with real discount authority, a customer-facing quotation that expires, a bill of materials or recipe costing, a staff advance that is issued, acquitted and chased, a member or unit ledger, a matching rule that holds a payment. Each of these is a build rather than a setting, and each has been quoted before — a bigger piece of work than a custom field, with a written spec and a date instead of a roadmap slide.
The report, document or pack nothing currently produces
The board pack in the shape your board actually asks for, a donor or funder layout, an invoice or receipt template carrying what your regulator or your customer expects, a dataset the report builder cannot reach yet. Usually the fastest thing on this list to deliver, because the data is already in the system.
Systems, rails and hardware you already run
The accounting package, CRM, online store, core banking or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed. Plus the physical edge: a scanner, a scale, a weighbridge or a till peripheral feeding the door it belongs to.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. Nothing here waits on a regulator or a published specification, which is why operational builds are the ones we quote fastest. Tell us the requirement that would otherwise rule us out — that is a better first conversation than a demo.
Tell us what your operation needsRun the tightest ship in the house
Bottle-level counts with genuinely blind entry, a valued variance per outlet, and issues to the bar recorded as transfers.
See bar control in AWRAFrequently asked questions
Free-pour or measured pour — does it really matter?
A skilled free-pourer is accurate to ±10%; a jigger is accurate to ±2%. On a bar's volume, that difference is the whole variance target. Measured pouring also protects good bartenders — their shift variance proves their honesty in a way style never can.
How do we handle happy hour and promotional pricing in the variance math?
Value consumption at the price actually charged in each period — the POS knows which price band every sale used. What breaks variance math is unrecorded discounting: promos through the till are fine; "special prices" negotiated at the counter are leakage wearing a smile.
Should bartenders see their own variance numbers?
Yes — per shift, posted where the team sees them. Named, visible variance changes behavior faster than cameras or searches, and it converts the honest majority into the control system: nobody wants to inherit the shift after a bad number.
What about stock for events and outside catering?
Issue event stock as its own mini-location — provisioned against the function sheet, returns counted back, variance closed per event. Event bars run the same math as fixed bars, just with a defined start and end; the [banqueting pattern](/blog/hotel-restaurant-inventory-kenya) applies bottle-for-bottle.
