Choose a bar stock management system by checking how it counts open bottles, converts recipes into ingredient quantities and explains the gap between expected and observed use. Keep recorded waste separate from unexplained consumption. Use the worksheet below to investigate a discrepancy before treating it as a loss or blaming staff.
What should a bottle count actually tell you?
A bottle count should answer a defined question: what quantity was present at the start and end of the same service period? For a Zambian bar choosing software, start with that operational question rather than a dashboard demonstration. Record the item identity, bottle size, location, counting method and cut-off alongside the quantity. Treat these as proposed worksheet fields, not claims about every product.
WISK describes partial inventories as spot checks of a subset of items. WISK partial-inventory documentation. Use that distinction to request a demonstration focused on a troublesome spirit or wine. WISK says a partial inventory does not update the stock count or replace a regular inventory. WISK partial-inventory documentation. A targeted Friday-night check and the venue’s regular stock count therefore need separate purposes. Do not let the smaller exercise quietly become the only record of everything behind the bar.
WISK requires an opening count and a closing count to show consumption in a partial inventory. WISK partial-inventory documentation. Before counting, nominate who records the opening and who confirms the closing. Include unopened bottles and remaining liquid in open bottles, using a declared unit consistently. If the stock moves during the exercise, write down the movement and its time rather than silently adjusting the end figure. This is our recommended counting discipline, not a claim that the cited product automatically captures every movement.
How do you compare bottles, pours and recipes fairly?
Ask the demonstrator to follow one ingredient from its purchase container to a sold drink. Choose a simple serve and a cocktail using the same ingredient. Request the actual recipe quantities used in the demonstration; do not assume that a button labelled with a drink name defines its ingredient use correctly.
WISK recipe mapping associates inventory items and quantities with each sale of a menu item. WISK Bar FAQ. That documented relationship makes recipe maintenance a useful selection question. Ask who can change a recipe, what happens to the previous version and how an investigator can establish which quantity applied during the period under examination. These are questions to resolve with the product provider, not capabilities established by the FAQ.
For open bottles measured by weight, reproduce a suspect reading before accepting it. For an incorrect scale reading, WISK advises checking that the surface is level and the scale is zeroed or tared. WISK Bar FAQ. WISK advises matching the bottle size being weighed to the item selected in the app. WISK Bar FAQ. Put the bottle identity and method on the worksheet so the next person can repeat the count. Do not translate weight directly into liquid volume using an assumed universal conversion: request the product’s documented item-specific method and check its inputs.
An original bottle-to-recipe worksheet
Use the following worksheet for a single ingredient and a declared period. It is an original practical checklist for preparing a demonstration or an investigation, not a tested control framework. Enter actual observations in the blank working copy; the prompts do not supply invented benchmarks.
| Worksheet line | What to record | Question before accepting the figure |
|---|---|---|
| Opening position | Sealed bottles, open-bottle remainder, method and time | Was the same item and bottle size selected? |
| Receipts | Item quantity and receiving document | Does the receipt belong inside this period? |
| Transfers | Source, destination, quantity and time | Has stock moved into a batch or another bar? |
| Closing position | Remaining quantity and repeated measurement | Is the counting method comparable to opening? |
| Recipe expectation | Sold serves and the ingredient quantity assigned to each | Which recipe version explains the expected use? |
| Explained removal | Waste record, reason, quantity and author | Is this distinct from sold drinks and transfers? |
| Unresolved difference | Gap still requiring explanation and next action | Which input needs checking before escalation? |
WISK instructs users to add an invoice whenever stock is received. WISK Bar FAQ. Include that receiving evidence before comparing the opening and closing positions. Otherwise the investigator is asking the closing count to explain stock that arrived during service without acknowledging its arrival.
As an original reconciliation method, first account for opening quantity, receipts and documented transfers using one consistent unit. Then compare what remains with the closing count to establish physical use. Separately assemble recipe-based expected use and recorded removals. Keep the underlying lines visible: a final difference without the inputs is not enough for the proposed investigation.
Agree a sign convention on the sheet. Write whether a positive entry means extra physical use or a surplus, rather than relying on a coloured arrow whose meaning nobody has recorded. Retain the unadjusted observation and explain each correction. That recommendation helps keep this worksheet interpretable when different people revisit it; it is not a vendor reporting specification.
Where do waste and batched drinks belong?
WISK allows a depletion to record stock removed because of spoilage or wastage. WISK Bar FAQ. In the worksheet, distinguish an observed spill, an authorised tasting and an unexplained shortage. Give a recorded removal a reason and supporting note. Do not use a catch-all waste entry merely to make an unexplained difference disappear.
WISK describes creating an inventoriable batch item by adding its ingredients on the Batches page. WISK Bar FAQ. Ask for a demonstration that follows an ingredient into a premixed container and then follows servings out of that container. Specify whether the worksheet is following the raw ingredient or the finished batch at each stage. Request an explanation of how the candidate system avoids counting the same ingredient in both places; the FAQ alone does not establish that accounting behaviour.
Recipe yield is a useful interview topic here. Ask the bar team to describe the batch recipe, preparation method, usable output and leftover handling in their own terms. Preserve observed output separately from the recipe’s intended output. Do not turn an assumption about dilution, spillage or portion size into an established fact about the venue.
Hypothetical case: the gin that moved rather than vanished
Imagine a bar finds less gin in its original bottles at closing than its sales-based expectation suggests. During service, a bartender used some of that gin in a prepared cocktail batch. The closing record includes the remaining raw bottles, but nobody has yet reconciled the prepared container. This is a hypothetical teaching case, not a Spout client or a reported incident.
Work through the worksheet in order. Confirm the bottle identity and repeat the open-bottle measurement. Check receiving documents and transfers. Locate the batch preparation note and the remaining prepared drink. Ask whether the comparison currently includes the raw ingredient, the finished batch or both. Keep the difference unresolved until the records establish a consistent treatment.
Then inspect any recorded spill separately. A genuine spill and an omitted batch transfer could coexist in this hypothetical exercise. Record each explanation against its own evidence; do not choose whichever story makes the screen look tidy. If a quantity cannot be established, label it unknown and assign a follow-up rather than inventing a balancing entry.
When is a consumption report still missing part of the story?
WISK warns that counts completed before emailed sales data arrives may produce consumption without a variance report. WISK partial-inventory documentation. Before judging the comparison, write down when sales records arrived and which service period they cover. Ask the demonstrator to show the difference between physical consumption, recipe-based expectation and a report waiting for its sales input. This is a narrow timing check, not a general guide to POS integration.
For the wider receipt, movement and audit-trail process, use our inventory control guide. Keep this article’s decision focused on beverage measurement, recipes and unexplained consumption. A system should be assessed against a reproducible example from your proposed workflow, with unresolved questions recorded openly.
The cited WISK documents describe its own product. They do not establish Zambian availability, a compatible local POS, scale procurement or any Spout implementation result. Ask the provider directly about your account, equipment and support requirements before committing. Our web development page provides a relevant starting point for a website-related brief; get started with your requirements if you want to discuss them with Spout.
Spout Team — AI-assisted editorial draft prepared with Codex from the cited primary sources. No human or professional review, product test or client result is claimed.