Snack shop cashier - end-of-day voided scale label SOP: every voided label corner-clipped into the day's waste bag on the spot, counted slip-for-slip against the system's void log, and any mismatch settled with the shift lead that night - welding shut the snack trade's most classic exposure point at the process layer

You are a checkout-standards coach for a snack
chain. Turn the labeling station's daily close
into an archivable SOP, centered on destroying
and reconciling voided scale labels, executable
from tomorrow.

Context: bulk items are weigh-print-ring. A
misprinted label gets voided and reprinted - so
a voided label that survives intact is a price
tag that can be applied one more time in the
rush. Afterward it is almost impossible to
investigate; the only defensible position is
inside the closing routine itself.

I will give you: trading hours, whether weighing
and ringing are one combined post or two
separate ones, evening headcount, and the label
stock format you buy.

Daily close (run in order after locking up):

1. Voided label count (the core step)
- Each voided label gets its void time written
  on it by hand the moment it is voided, and
  goes straight into the day's waste bag under
  the counter - never parked on the counter top
- At close: empty the bag, count, clip every
  label's corner (cutting through the barcode),
  return them to the bag
- Write on the bag: date, shift, count, handler
2. Reconcile against the system
- Pull the day's void record count from the POS
  and match it against the bag - slip for slip,
  not roughly
- Mismatch: find the shift lead, go through the
  shift's receipts together tonight; whatever
  the difference remains, it goes in the
  exceptions column and is settled before
  everyone leaves - nothing waits overnight
3. Station and equipment
- Label paper below the [low-stock line]: log
  it, draw a fresh roll, park it at the station
- Scale zeroed, powered off, dust cover over
  the print head
- Handhelds back in place, charging
4. Record
- The day's row in the close log: voided labels
  / system void entries / match or not /
  exception notes / signature - one row is one
  day

Constraints:
- Every step states "what counts as done" (the
  waste bag re-tied after clipping with its
  header complete means done)
- "Straight into the waste bag" and "clip on
  the spot" are hard items - never relaxed to
  "handle it all at end of shift" for busy
  nights; voided labels sitting on a counter
  overnight are the vulnerability itself
- No "raise loss-prevention awareness" talk;
  an SOP carries actions only
- One page; append blank templates for the
  close log and the exceptions column

Why it is written this way

This SOP does not defend against "employees are thieves"; it defends against "the process makes becoming one possible." A voided label dropped on the counter or into an open bin is still a live price tag - applied again at rush, nobody can tell. Clipping the corner through the barcode is what makes the void physically real; the valuable part is not the cut but the habit that voiding equals destruction. And it is a hard item precisely because every "batch it at end of shift" version leaves hours where no one can say where the labels were.

"Slip for slip" rather than "roughly" sets the reconciliation strength: twelve void entries in the system and eleven labels in the bag makes that one label the only thing worth understanding tonight. The script gives the mismatch an exit - find the shift lead, page through receipts, log what remains, no overnight gaps - because most nights it is a jammed label that never made the bag, cleared in five minutes. But every mismatch allowed to sleep overnight is the beginning of the next, larger one.

Riding label stock and scale condition along in the same close is deliberate: the routine's real value is "the same person, at the same moment, walking the same station daily" - adding consumables and equipment to the loss-prevention pass costs no extra actions, yet means a misbehaving scale is known by next morning at the latest, instead of being discovered by a customer demanding a re-weigh.

Variables