Tobacco & liquor store manager - end-of-day premium cabinet close-out SOP - bottle-by-bottle check against slot and batch code, locked away, dual signatures, key and combination split, so a missing bottle surfaces by next morning instead of month-end

You are a store-operations consultant for a tobacco &
liquor shop. Write an archivable "Premium Cabinet
End-of-Day Close-Out SOP." Context: high-value
bottles are small and expensive; the later a
shortage is found, the colder the trail - footage
retention runs out, paperwork and memory blur
within days. A variance discovered at month-end is
essentially unsolvable. The goal: a missing bottle
surfaces by tomorrow morning at the latest.

Scope: the premium cabinet, the safe, and any
counter-display high-value items. Everyday shelves
follow the shift-handover checklist, not this SOP.

The routine (starting 15 minutes before close):

1. Count and match
- Bottle by bottle against three references:
  slot number x last digits of the batch code
  on the bottle x the cabinet log - three-way
  match
- Display samples and any bottle a customer
  examined and returned go back into their slots
- The day's sales, returns, transfers, and
  display loans reconcile line by line against
  the log - a count that matches while the
  paperwork doesn't is treated as a variance;
  the close-out isn't complete

2. Lock away
- All high-value items into the cabinet or
  safe; overnight the counter holds only empty
  display boxes or explicitly-designated
  samples (their status and liability covered
  elsewhere)
- On locking, apply the day's numbered seal
  (or log the lock number); next morning verify
  the seal is intact before opening the log

3. Dual signature
- Counter signs, verifier signs; the verifier
  re-counts at least three bottles from the
  premium section, one of them moved today
- Solo-staff fallback: before closing, video-
  call the owner (or manager) and complete the
  count and lockup on camera; the call record
  is archived with the day. "I'll sign
  tomorrow" does not exist

4. Key and combination split
- Cabinet/safe key and combination held by
  different people: key with the duty
  manager, combination with the store manager
  or owner; opening requires both present -
  there is no "emergency solo access"
- Key movements log who, when, why; the key
  never leaves the building

Variance path (when a bottle won't reconcile -
written with more care than the happy path):
- In the moment: no guessing, no plug numbers.
  Re-count the slot with a second person, then
  re-check the day's paperwork, then pull the
  day's footage for the relevant window
- Still unresolved: log the facts - the slot,
  what's missing, the last confirmed sighting
  in-cabinet - and escalate to the manager or
  owner tonight. It does not sit overnight, and
  nobody squares the books on their own
- First task tomorrow morning: follow up,
  route into the count-variance process; a
  premium-item shortage reaches the owner the
  same day, full stop

Records:
- Close-out sheets bound monthly; signatures
  or they're invalid; cross-checked against
  the monthly inventory
- Seal numbers, key log, and video-call
  captures filed with the sheets

Red lines (written into the SOP):
- No "sign now, count later" - the signature
  is the completion of the count
- No skipping the verifier's spot re-count to
  save time
- Solo access, proxy signatures, and altered
  sheets are violations, period

Why it is written this way

The whole SOP has exactly one goal: compress the discovery time of a high-value variance from a month to a day. That's not ceremony - the discovery lag directly determines solvability: within 24 hours the paperwork is still around, the handlers still remember, and the footage hasn't been overwritten; every extra day burns all three trails. The daily close-out doesn't prevent theft (what prevents theft is the certainty that the process exists); it makes any shortfall surface while the blast radius is one day wide. Counting, seals, and dual signatures all serve one property: every bottle has a named owner of responsibility at every moment in time.

"A count that matches while the paperwork doesn't is still a variance" is the rule most likely to be skipped and most worth defending. The most common shortage isn't physical disappearance - it's book-to-shelf drift: a bottle sold with no ticket, a display loan never logged, a return shelved without posting. The numbers happen to match because two errors cancel. A close-out that counts bottles without reconciling paperwork stores those landmines for month-end, when they go off un-attributable. The three-way match (slot x batch x log) exists for the same reason: a batch code that won't reconcile means the bottle and the record are different objects - swaps, miscounts, and misfiled slots all hide exactly there.

The variance path's "no plug numbers, no overnight, no self-squared books" is written more carefully than the happy path because the first reaction decides everything. The staff instinct is to make the books balance - find a compensating bottle somewhere, mark it "pending," and once the page looks level the matter dies. The SOP blocks that road: log the facts, escalate tonight, treat a variance as an event rather than an inconvenience. Splitting key and combination with no emergency solo access looks inconvenient by design: a cabinet one person can open is a cabinet whose variances can never be attributed - the inconvenience is the control.

Variables