Bar inventory benchmarks for 2026
A methodology-first guide to pour cost, usage variance, and shrinkage. Use ExactPour's formulas, or the same math in a spreadsheet, to build baselines from your POS and counts, not from unverified industry folklore.
By ExactPour · Updated
Methodology
- This page describes definitions and arithmetic ExactPour uses for pour cost, usage variance, and shrinkage residuals. It is a methods note, not a survey of industry outcomes.
- We do not publish fabricated multi-venue averages here. Any numeric target you see in trade literature should be treated as a starting hypothesis until you validate it against your own counts, recipes, and sales.
- Scope every metric to the same period, locations, and beverage categories. Mixing wine-only cost with total beverage sales (or mismatched count cutoffs) invalidates the ratio.
- Dataset note: the working dataset for benchmarks is your venue's inventory counts, receiving/transfer records, recipe mappings, POS item sales, and documented waste for a defined inventory period. ExactPour computes from that tenant data; this public page contains no customer or account data.
- Prefer period-over-period and product-level baselines for your own operation over cross-industry headline numbers. A stable internal baseline answers operational questions; an uncited external average does not.
Pour cost: definition and formula
Period beverage cost used = beginning inventory + purchases + transfers in − transfers out − ending inventory. Apply documented credits or returns consistently as reductions to purchases or as a separate adjustment, pick one policy and keep it.
Pour cost percentage = beverage cost used ÷ beverage sales × 100. Revenue and inventory cost must cover the same dates, locations, and beverage categories. Taxes and tips are normally excluded from beverage sales; state the accounting policy explicitly.
Trade literature often discusses pour cost targets in a mid-teens range, treat any cited target as a starting hypothesis and validate against your own POS and counts. A venue's sustainable ratio depends on mix, pricing, comps policy, and purchasing, so copy-pasting someone else's target is not a control system.
ExactPour surfaces pour cost from live bottle pricing, recipes, and reconciled usage so you can watch the ratio by category, product, and location. The product does not invent an industry benchmark for you; it keeps your arithmetic consistent.
Usage variance: projected versus actual
Actual usage = beginning inventory + received + transfers in − transfers out − ending inventory for the scoped products and locations.
Expected (projected) usage is the sum of sold menu-item quantities multiplied by their recipe quantities, adjusted only for documented events your policy treats separately (for example logged waste or comps).
Usage variance = actual usage − expected usage − documented waste. A positive result means measured usage exceeded recipe-based usage after listed adjustments. It does not identify theft, over-pouring, or measurement error by itself.
ExactPour builds projected inventory from POS depletion after menu items are mapped to recipes, then flags products that drift beyond tolerance so managers investigate with reason codes. Resolve scope, receiving, unit conversion, and mapping issues before interpreting behavior.
Shrinkage as a residual, not a verdict
Shrinkage is inventory purchased that cannot be matched to recorded sales, documented waste, or transfers. In practice it is the residual usage variance for a defined period and scope, expressed in units or cost.
Because shrinkage is a residual, it inherits every upstream measurement error: count accuracy, receiving records, unit conversions, recipe definitions, and POS mappings. Visual fill estimates and missing transactions can look identical to over-pouring in the arithmetic.
Use shrinkage as an investigation queue. Data and process explanations are cheaper to check first. Sustained patterns plus supporting records, not a single period's number, are the basis for operational conclusions.
How to build your own baselines
Pick a stable inventory cadence (many beverage programs review weekly so the trail stays warm). Hold period length constant when comparing periods.
For each key SKU or category, record pour cost and usage variance over several complete periods. Compute a simple mean and, if you have enough periods, a spread (for example standard deviation) so you can see what "normal for us" looks like.
Set investigation thresholds relative to your baseline (for example flag when a product's latest variance exceeds a multiple of its own historical spread), not relative to an uncited industry headline.
Re-baseline after menu, recipe, pricing, or vendor cost changes. A shift in the ratio after a well-price increase is often purchasing or pricing, not suddenly worse pouring.
Public calculators on /tools and the pour-cost method guide can help you reproduce the arithmetic outside ExactPour when you want an independent check.
What this page is not
This is not a claim that bars as a category lose a fixed percentage of inventory, nor a ranked leaderboard of venues. Cross-sectional industry averages require a disclosed sample, period, and methodology; without that, they are marketing folklore.
If you need product positioning rather than methods, start at /bar-inventory-software. If you need step-by-step pour cost arithmetic, use /docs/pour-cost-method and /blog/how-to-calculate-pour-cost.
Frequently asked
Does ExactPour publish industry-average pour cost or shrinkage figures?
Not on this page. We explain formulas and how to build baselines from your own POS and counts. Trade literature often discusses pour cost targets in a mid-teens range, treat any cited target as a starting hypothesis and validate against your operation.
What dataset do these benchmarks use?
Your venue's counts, receiving and transfers, recipes, POS sales, and documented waste for a defined inventory period. This public research page contains methodology only, no customer or tenant data.
How does ExactPour calculate pour cost?
Period pour cost uses beverage cost used divided by beverage sales for matching scope. Cost used comes from beginning inventory, purchases, transfers, and ending inventory. See pour cost method for the full definition and how to calculate pour cost for a worked narrative.
How should I set a variance threshold?
Prefer thresholds from your product-level history after recipes and POS mappings are clean. ExactPour can flag outliers against per-product baselines; you can also set operational tolerances that match how tightly you manage each category.