Convenience store backroom manager - stockroom FIFO stacking SOP: new stock enters one side only, picking happens on the other, date labels face outward uniformly, open half-cases stand alone and unstacked, and the pass test is a five-box spot check where the earliest dates sit at the front within reach

You are a store backroom operations consultant for
convenience stores. I manage the backroom and need
first-in-first-out written up as an archivable,
trainable, checkable SOP. Produce the full document
using the framework below, written for store staff,
not for warehouse professionals.

Framing (put this at the top of the document):
- This SOP exists to solve one problem: without a
  stacking rule, staff grab the easiest box - and
  the easiest box is always the one stacked last.
  FIFO does not run on diligence; it runs on stock
  that can only enter from one side and leave from
  the other
- "Backroom" means the store's storage area, not
  the sales shelves

Document structure (follow it exactly):
1. Zones and signage
- Fixed lanes or areas: distribution dry goods /
  direct-delivery goods / fresh-food staging /
  supplies / empty totes. Each zone gets a sign;
  once placed, zones do not drift
- Every lane is marked "intake side" and "pick
  side" (floor tape or hanging tag), with the
  orientation identical across the whole store

2. Three stacking principles (each with a written
compliant / violation scene pair, painted in
words):
a. One-way flow: new stock is stacked on the
   intake side only; picking happens on the pick
   side only. Any stack with a new case in front
   of an old one is a violation, no matter how
   rushed the day was
b. Dates face outward: every case's date label
   faces the pick side; standing at the pick
   side, all dates are readable without moving
   a box
c. Open half-cases stand alone: an opened
   half-case goes to its item's designated spot
   or the half-case area, opening up, never
   stacked, never wedged between full cases - a
   stacked half-case is deleted from view

3. Post-delivery reset (part of the receiving
flow, not an extra task):
- After shelving, the receiving shift returns
  that day's half-cases to the half-case area
  while hands are already in the lane
- Daily at closing, [reset minutes, suggest 10]:
  walk every zone doing exactly three things -
  new cases to the intake side, date labels
  turned to the pick side, half-cases returned
- Any old case found buried gets pulled to the
  front of the pick side immediately and noted
  in the shift handover log

4. Exceptions:
- Promo volume exceeding lane capacity: stack
  separately in a temporary zone with a "promo -
  FIFO" tag; clear that zone first when the
  promo ends, never merge it behind the regular
  lanes
- Return-to-DC stock: separate area, listed
  separately, physically separated from sellable
  stock so it cannot be restacked as new goods

5. Acceptance standard (a hard ruler, runnable on
the spot):
- Method: pick any lane, pull five random cases,
  check the dates inside each - the earliest-
  dated stock in that lane must sit in the front
  two rows and be reachable with one hand. That
  is a pass
- Three instant violations: a new case stacked in
  front of an old one; a half-case stacked; a
  date label facing away from the pick side
- Violations go into the handover log with
  location and the corrective move - never
  "watch out next time"

6. Roles and training:
- Every action carries a role: delivery reset
  with the receiver, closing walk with the shift,
  weekly spot check with the backroom manager
- A new hire's first day includes one spot check
  run by the backroom manager - knowing how to
  check is the proof of understanding

Output requirements:
- The document carries three fill-in fields:
  version, effective date, owner - archivable
  as is
- Every compliant / violation pair is a concrete
  scene ("20 cases of water arrive Friday and get
  stacked at the pick-side door to save time" is
  the violation scene), never an abstract
  principle

Prohibitions:
- No "tidy regularly" or "keep it clean"
  sentences without a frequency and an owner -
  every line must say who, when, doing what
- Do not cite warehouse certifications or
  standards numbers
- Do not invent stacking heights, layer limits,
  or temperatures as hard rules - lane
  structures differ per store; such parameters
  stay blank for the store to fill from reality
- No preamble or closing pleasantries - start
  straight from the document title

Why it is written this way

FIFO is written as geometry rather than a requirement because "ship by date order" is simply not executable in a convenience store backroom - no one in a five-minute replenish window is going to read dates case by case. One-way flow drops the decision cost to zero: no judgment about which case is older; whatever sits outermost on the pick side is the oldest by construction. The rule only works if intake and pick sides are physically fixed and identically oriented store-wide, which is why zones and signage form section one - one-way flow without a fixed orientation degrades back to random stacking within three days.

Half-cases get their own principle because they are where backroom FIFO dies: an opened case shows no outer date label, and once stacked onto a second tier it is neither visible nor remembered until a count surfaces three months of forgotten stock. Opening up, never stacked, never wedged - all three moves serve one goal: keep the half-case inside the field of view. It is a hard rule rather than a habit reminder because everyone's definition of "handy" differs, and a rule that depends on personal style is not a rule.

The acceptance test is deliberately a ten-second spot check: five random boxes, earliest dates in the front two rows. Verifiability is the line between an SOP and a poster - "first in, first out" hung on a wall cannot be checked, so it is not executed; a ruler anyone can pull at random turns the weekly check into a real action. The three instant violations are written concretely precisely so an untrained newcomer can judge them independently; a standard that needs experience to apply is not a standard.

Banning frequency-free sentences and pinning every line to a role and a time fights the most common way SOPs rot: vague clauses have no owner, and the document becomes wallpaper. The two exceptions - promo volume and return stock - get explicit rules because they are exactly the moments FIFO breaks: an exception without a written rule gets improvised on the spot, and the improvised rule is always the laziest one.

Variables