Fresh supermarket backroom three-zone daily-clear SOP - staging out in two hours, pending never overnight, oldest batch facing out

You are a backroom management consultant for a fresh-food supermarket.
Write our backroom daily routine as an archivable daily-clear SOP. Our
backroom is not small's problem - the problem is always "things sat
until nobody remembered them": staged goods sleeping overnight,
sellable product mixed into write-off boxes, batches turned the wrong
way so the new stock sells first.

Structure the SOP as three zones, three lines:

Zone one: receiving staging (goods inspected, not yet put away)
- Hard line: inspected goods must leave staging within X hours
  (default 2, adjustable). Cold chain goes into the cooler first -
  non-negotiable, and the clock starts the moment the acceptance
  ticket is signed; ambient goods put away same day
- On surge days when staging can't clear, the priority order is
  fixed: chilled > frozen > short-shelf ambient > long-shelf ambient.
  Work the clock in that order - "whichever pallet is easiest to
  move" is not a priority order
- Tape a floor line; staging lives inside it - a full taped area
  means today's processing speed has a problem. That is a signal,
  not an argument for more space

Zone two: storage (rack locations)
- Batch orientation: same item, multiple batches - earlier arrivals
  face out and sit low (grabbed first), new arrivals face in and
  sit high. Executed during every day's put-away, not at a weekly
  tidy-up
- Off the wall, off the floor: nothing touches exterior walls or
  ground; pallets or risers underneath
- Raw and ready-to-eat separated: different racks, physically apart,
  never sharing a shelf level
- One batch card per location: item / arrival date / shelf life /
  quantity; card comes down when the batch clears

Zone three: pending area (write-offs awaiting approval, returns
awaiting pickup, transfers awaiting dispatch)
- Hard line: **pending does not stay overnight** - approved today,
  picked up today, loaded today. Every box in this zone must answer
  "who handles me today"; any box that can't, the duty manager
  decides its disposition today
- Three streams, separate areas or color codes: write-off box,
  return box, transfer box never mix. Mix them once and the box
  contains everything

Daily clear (last 30 minutes before close):
- One pass per zone: staging empty? / three random locations checked
  against their batch cards? / anything pending overnight? Three
  results onto the daily-clear log, one line: zone / status /
  exception note
- At shift handover, backroom state travels with the handover book:
  one sentence per zone

Attach an "exception paths" section covering the two line-breakers
that will happen: staging that can't clear (surge day) and pending
boxes stacking up (approver on leave) - the recovery action and the
escalation target for each.

Do not:
- Write "keep the backroom tidy" - tidiness is not the objective,
  traceability is; every rule must answer "what gets lost if this
  isn't done"
- Recommend a WMS or new racking - write for what exists
- Pull sales-floor replenishment into this SOP - that belongs to
  the stockers' SOP, and mixing them causes fights

Why it is written this way

The backroom's real failure mode is forgetting, not capacity: goods staged overnight become unclaimed orphans by morning, and a week-old pending box holds contents nobody can name. So the whole SOP hangs on three timelines - out in two hours, batch-facing done daily, pending never overnight - each answering "when must this move." Anything beyond the timelines (tidy, neat) is decoration.

"A full taped area is a signal, not a space argument" is a management stance: fix the staging footprint and the problem presents as "processing can't keep up" instead of quietly growing into "the backroom got bigger." Space self-adapts to fill; only the tape line doesn't move. That sentence exists to kill the easiest wrong answer - "let's take over more floor."

The three-box color separation targets the dirtiest corner of shrink management: the write-off box is "already expensed," the return box is "still has value on the books" - mix them and which account a box settles into depends on whoever moves it last. The SOP grants no such discretion.

The exception-paths section decides whether this SOP survives: surge days and absent approvers will happen, and an SOP silent on what to do when the lines break teaches everyone that breaking them is free - all three hard lines fail together. Recovery steps written in advance are what make the lines mean anything.

Variables