Why Your Restaurant Wine Inventory Doesn’t Match the POS

What the POS actually knows

A point-of-sale system records a button press. If that button is mapped to the right wine, the right vintage and the right unit (bottle or glass), the depletion is accurate. If any of those three are off, the POS will report a confident, wrong number. In my experience running a 400+ label program, most ‘missing bottle’ panics turn out to be record problems first and loss problems second — but you only know which after you reconcile.

The POS also knows nothing about bottles that leave without a sale: a server’s tasting, a corked bottle replaced at the table, a bottle sent to the kitchen for a sauce, or a case moved from the main cellar to a bar fridge. Each is legitimate; each is a variance unless someone records it.

The most common causes of variance

1. Vintage changes. The 2019 sells out, the 2020 arrives, and the POS button still says 2019. Sales deplete a vintage you no longer have while the new one looks untouched.
2. SKU mapping errors. Two similar wines share a button, or an ‘open wine’ key is used during a busy night and the item is never identified.
3. By-the-glass depletion. Glass sales are recorded as glasses, but inventory is counted in bottles. Without a defined conversion and an open-bottle count, BTG wines always drift.
4. Comps, voids and staff tastings that are not recorded against inventory.
5. Transfers between storage locations, outlets or the kitchen with no transfer record.
6. Receiving errors: invoices not entered, short shipments accepted as complete, or credits for broken bottles never posted.
7. Breakage, spoilage and returned corked bottles awaiting distributor credit.
8. Count errors: bottles in a second location missed, or a case counted as twelve when two are already open behind the bar.

A reconciliation workflow that holds up

1. Freeze the period. Choose a count date, close receiving for that day and pull POS sales, comps and voids for exactly the same window.
2. Count by location, not by list order. Main cellar, service fridges, bar, overflow and any off-site storage — each counted and recorded separately.
3. Count open BTG bottles in tenths, or by an agreed fill-level method, so glass programs can be reconciled.
4. Line up beginning count + received − sold − recorded adjustments = expected count, for each SKU and vintage.
5. Compare expected to actual. Sort variances by dollar value, not by bottle count — one missing bottle of a high-cost wine matters more than four inexpensive ones.
6. Investigate the top variances first: check vintage mapping, the POS item, invoices, credits and transfer notes before assuming loss.
7. Correct the records and document the cause of each correction.
8. Fix the control that failed — a POS mapping, a receiving step, a transfer log — and schedule the next count.

Worked example (hypothetical numbers)

Common mistakes

• Treating every variance as theft before checking records.
• Counting once a year. Variances compound; monthly or more frequent counts of high-value SKUs are easier to explain.
• Reconciling totals instead of SKUs. A total that matches can hide offsetting errors.
• Assuming software will fix it. A tool makes good processes faster; it does not create them.

Can the POS update inventory automatically?

Sometimes, partially. Whether sales can deplete inventory automatically depends on the specific POS, the inventory tool and the integration they genuinely support. Even where it works, it only depletes what was rung in. Comps, transfers, breakage and receiving still need people and procedures. Design the workflow around what your systems actually do, not what a brochure implies.