Liquor Store Inventory Management: The Complete Guide
Per-size stock, daily chaining, shortage control and the audit ledger — how well-run liquor shops keep count to the bottle.
Liquor inventory is harder than most retail inventory for one reason: every brand is really five or six products. A single whisky exists as 90ml, 180ml, 375ml, 750ml and 1L SKUs, each with its own MRP, its own count and its own rate of sale. A shop carrying 200 brands is actually tracking 800–1,200 SKUs — by hand, in most of India.
The three numbers that must always agree
For every SKU, three numbers must reconcile every single day:
- Opening stock — what you started the day with (yesterday's closing).
- Movements — purchases received, bottles sold, shortages and corrections.
- Closing stock — what's physically on the shelf at night.
When opening + purchases − sales ≠ closing, you have a discrepancy — and finding its source days later, across hundreds of SKUs, is the single biggest time-sink in liquor retail. The fix is structural: record movements as they happen, in a ledger that chains day to day.
Why paper registers fail at scale
- No chaining: if Tuesday's closing was copied wrong into Wednesday's opening, every day after is wrong and nobody notices until a stock-take.
- No per-size discipline: registers often track "Royal Stag" as one line when 180ml and 750ml move at completely different speeds.
- No audit trail: a crossed-out number tells you nothing about who changed it, when, or why.
- Slow entry: a 40-line purchase invoice takes 20–30 minutes to copy in — so it gets postponed, and stock runs ahead of the books.
What a digital system must do (checklist)
| Requirement | Why it matters |
|---|---|
| Per-size SKUs out of the box | 180ml vs 750ml behave like different products — because they are |
| Day-to-day chaining of opening/closing | Eliminates the copied-wrong-opening class of errors entirely |
| Auditable movement ledger | Every discrepancy traceable to a specific entry, person and time |
| Shortage/leakage capture at receiving | Billed 100, received 98 — recorded at the door, not discovered later |
| Fast (ideally AI) purchase entry | If entry is slow it gets skipped, and skipped entries are how books drift |
| Low-stock alerts | Fast movers shouldn't run out on a Saturday night |
How AI changes the setup problem
The reason most shops never digitise is the opening inventory problem: typing 1,000 SKU counts into a system takes days. Modern apps solve it with AI: photograph your existing stock register and the system reads every brand, size and quantity, builds the opening inventory, and asks you to review and approve. In Liquor Pro this same pipeline also reads purchase invoices and gate passes, reconciling totals against the printed footer so misreads are flagged rather than saved.
Daily routine that keeps books true
- Morning: confirm opening stock matches yesterday's approved closing (digital chaining does this automatically).
- On receiving: scan the invoice the moment the delivery arrives; record any shortage against the bill before the driver leaves.
- Through the day: sales recorded by brand and size — by the counter staff, not reconstructed at night.
- Closing: spot-check 5–10 fast movers physically; investigate any mismatch the same evening while memory is fresh.
Cycle counting: stock-take without shutting the shop
The full-shop physical count is the reason most shops audit once a year and fly blind for the other 364 days. It takes a full night, it needs the shutter down, and by the time it is reconciled the numbers are already stale. Cycle counting replaces it with ten minutes a day.
The method is simple: split the catalogue into groups by how fast each SKU moves, then count each group on a fixed rhythm.
| Group | What goes in it | Count frequency |
|---|---|---|
| A — fast movers | The ~20% of SKUs driving most bottle movement — popular 180ml and 750ml whisky, strong beer | Weekly |
| B — steady | Mid-velocity brands, most wine and standard beer | Monthly |
| C — slow / premium | High-value bottles that rarely move; imported and specialty stock | Quarterly, but count every bottle |
Group A is where shrinkage hides, because high volume masks small losses. Group C is where value hides — a single missing premium bottle can outweigh a week of 180ml discrepancies. Counting both on their own rhythm catches far more than one annual sweep, and it never needs the shop closed.
Reading a discrepancy: the four usual causes
When a count disagrees with the book figure, the cause is nearly always one of four things. Check them in this order — cheapest first.
- Entry error (most common). A quantity typed as 12 instead of 21, or a purchase recorded against the 750ml SKU when the case was 375ml. Look at the last week of entries for that brand before assuming anything worse.
- Wrong-size posting. The total bottle count across sizes is right but individual sizes are off — a classic sign that two SKUs of the same brand were confused at entry or at the shelf.
- Unrecorded movement. Breakage, a sample bottle, stock moved to another branch, or a purchase received but never entered. These are legitimate movements missing their paperwork.
- Genuine shrinkage. What remains after the first three are ruled out. Only now is it worth treating as a loss investigation.
Per-size SKUs in practice: why "Royal Stag" is not one product
The single most common structural mistake in a liquor register is tracking a brand as one line. Consider one whisky across a typical week:
| SKU | Moves like | Margin behaviour | Stock-out cost |
|---|---|---|---|
| 180ml | High volume, daily, weekday-heavy | Thin per bottle, large in aggregate | High — buyer walks to the next shop |
| 375ml | Moderate, weekend-weighted | Middle | Moderate — often substituted |
| 750ml | Lower volume, festival and weekend spikes | Best absolute rupees per bottle | High on festival days specifically |
| 1L | Occasional, planned purchases | Good, but ties up capital | Low — buyer will wait or trade down |
These four lines need different reorder points, different shelf space and different festival-week planning. Collapsed into one "Royal Stag" row, none of that is visible — you cannot tell whether a stock-out cost you a sale or saved you dead capital.
Frequently asked questions
How often should a liquor store do a physical stock count?
Rather than one annual full count, most well-run shops use cycle counting: fast-moving SKUs weekly, mid-velocity monthly, and slow or premium stock quarterly. This takes about ten minutes a day, never requires closing the shop, and catches discrepancies while they are still traceable to a specific delivery or entry.
Why should liquor inventory be tracked per bottle size instead of per brand?
Each size of the same brand has its own MRP, its own rate of sale and its own margin. A 180ml and a 750ml of the same whisky need different reorder points and different festival planning. Tracking the brand as a single line hides stock-outs and dead capital, because the sizes behave like completely different products.
What causes stock discrepancies in a liquor shop?
In order of likelihood: data entry errors, postings against the wrong bottle size, unrecorded movements such as breakage or inter-branch transfers, and only then genuine shrinkage. Checking them in that order resolves most discrepancies quickly, because the first three have paperwork or memory attached.
What is opening and closing stock chaining?
Chaining means each day's opening stock is automatically taken from the previous day's approved closing figure, rather than being copied by hand. It eliminates the single largest source of register error, where one mistyped opening figure silently corrupts every day that follows until the next physical count.
How many SKUs does a typical Indian liquor shop actually track?
A shop carrying around 200 brands is usually tracking 800 to 1,200 individual SKUs, because most brands exist in four to six bottle sizes. This is why manual registers break down at scale and why per-size tracking has to be automatic rather than a discipline staff maintain by hand.
Related reading
Run your store on autopilot
Free AI-powered liquor store management — stock, sales, cash and reports in one app.
iOS 13+ · iPhone, iPad, Mac (Apple Silicon), Apple Vision · Android APK direct download · 18+ · Prefer a call? Request a callback →