Sommelier Wine Cellar Inventory Log

It covers the core checks a sommelier or beverage manager needs during a cellar count: bin-by-bin bottle counts, vintage and label verification, condition checks, and storage integrity. It is designed to confirm what is physically in the cellar against what should be there. Use it as a recurring inventory log rather than a one-time audit. It works best when each checklist item can be answered yes, no, or N/A.

Most cellars benefit from a weekly or monthly cadence, depending on volume, turnover, and value concentration. High-end programs with frequent transfers or high shrink risk may use a weekly recurrence, while smaller cellars may use monthly counts with spot checks in between. The key is to keep the cadence consistent so variance trends are visible. If you already do receiving or pre-service checks, this log should complement them rather than replace them.

The DRI is usually the sommelier, beverage manager, or cellar lead, with support from an assistant manager or inventory team member. One person should own the final reconciliation so the count is not split across multiple versions. If the cellar is large, assign by zone or bin and then reconcile centrally. The person running the log should also be able to escalate discrepancies and blocking issues immediately.

It is primarily an operations template, but it also supports compliance-minded controls around storage conditions, traceability, and loss prevention. It helps document that bottles were checked for proper storage, damage, and inventory accuracy. If your program handles regulated alcohol inventory or internal audit requirements, this log creates a repeatable record. It should not replace legal records, tax documentation, or formal audit procedures where those are required.

The biggest mistake is combining too many checks into one vague line item, such as asking whether the cellar is 'fine.' Another common issue is counting without verifying vintage, bin location, or bottle condition, which hides shrinkage and mis-pulls. Teams also often skip a reconciliation step, so discrepancies never become actions. Finally, if the log has no recurrence or no clear owner, it turns into an ad hoc count instead of a control.

Yes. You can adapt it for rack, bin, or region-based layouts, and you can split the checklist by still wine, sparkling, dessert wine, or premium allocations. If your cellar uses multiple storage zones, add a section for each zone and keep the verification steps separate. The template should still preserve atomic checklist items so each count or condition check is independently verifiable. That makes it easier to compare results over time.

A spreadsheet can hold the numbers, but this template gives the team a repeatable process for how the count is performed. That matters because cellar issues often come from missed verification steps, not just bad totals. A task template also makes ownership, recurrence, and follow-up clearer than a freeform sheet. Use both together if needed: the template for the workflow and the spreadsheet or inventory system for the final numbers.

Yes, it can sit alongside POS, inventory, purchasing, and cellar management workflows. Many teams use the log to trigger follow-up tasks for reorders, transfers, breakage review, or storage repairs. It also pairs well with receiving checklists and pre-service cellar checks. The important part is that the log produces a clean action list when a discrepancy or storage issue is found.