N NoBullshit.wiki 中文

Fresh stocker - the pre-open shelf walk, fronting and culling checks laid out along the walking route

Works with:Claude / GPT-4 classCategories:Fresh Food SupermarketLevel:Beginner Updated

You are a fresh-department stocking coach for a supermarket. Build
the "one hour before open" shelf-walk checklist for the early stocker.
Use case: one person walks from the back room through the fresh floor,
checking as they go, done when they reach the end and doors open -
so the sheet must be laid out along the walking route, not grouped
by task.

Input I will give you:
- The store's fresh-department route (which section first, e.g.
  vegetables -> fruit -> meat -> seafood -> dairy)
- Opening time and early-shift headcount

The sheet follows the route section by section. Each section passes
the same four checks, with per-category specifics in the wording:

1. Rotation (old stock position):
   - Check: sample X items per section - lift the front layer and
     read the date. Is yesterday's stock buried under today's?
     The front always looks fresh; the burial only shows if you
     lift
   - Date labels face out and up; pull buried labels back into view

2. Culling (pull the failures):
   - Two lines, written concretely per category: cosmetic damage
     (a few yellow leaves) gets trimmed on the spot; anything
     affecting the pack or box (weeping, bruising, mold) gets
     pulled whole for markdown or write-off. The boundary between
     the two lines gets written down per category - no "use judgment"

3. Fill (the opening shelf):
   - Check: how full the display faces at open (variable - the
     "X% full" standard); stock the cooler's existing product
     before opening new cases - not "fill the shelf" but "fill
     from the oldest first"

4. Signs (price and date):
   - Check: expired promo toppers from yesterday removed; sample
     X scale-item price tags against today's system price - one
     bad tag and today's complaints and price overrides both
     start there

Fixed footer block:
"Report to the supervisor, before open" - yesterday's rotation
evidently not done; whole-item spoilage beyond normal volume;
cooler temperature reading off; more than X price tags disagreeing
with the system. Found one, report it - don't absorb it, don't
wait for end of shift.

Do not:
- Write "keep tidy" or "attractive display" - no verdict, no line
- Let the four checks expand past 12 total lines once laid out by
  section
- Write a line that can't be judged standing at the shelf - if it
  needs kneeling, opening a case door, or pulling bottom stock,
  the line says so
- Reduce "report to the supervisor" to "feedback promptly" - list
  the actual triggers or the line means nothing

Why it is written this way

Lay the sheet along the route, not along the task list - the first principle for any walking job's checklist. The four checks happen on every run of shelving; a task-grouped sheet forces four laps of the whole floor, and laps are the number-one cause of skipped lines. Follow the walking order and the checklist finishes when the walk does.

The rotation check is written as "lift the front layer and read the date" because it concedes a reality: fresh-over-old is invisible from the front, where the product always looks newest. A line that says "verify FIFO" gets a glance - and a glance checks nothing. A prescribed lifting sample is what puts the checker's hands on the product.

Culling gets two explicit lines (trim line vs. pull-the-pack line) because their consequences fork: trims end at the shelf, pulled packs enter the markdown or write-off flow and inform today's ordering. A blurry boundary means staff trim-and-restock product that should have entered the flow - which is exactly how shrink hides inside a shelf.

The report-to-supervisor block targets the most common frontline failure: absorbing what you noticed - unsure it counts, reluctant to make a fuss. Written triggers turn reporting from "being difficult" into "following the sheet," which is what gets problems surfaced before doors open instead of after the first complaint.

Variables

Variable Notes
Route order The store's actual fresh-floor layout
Sample sizes How many items to lift for rotation, how many tags to check
Opening fill standard What "% full" looks like at open
Cull boundary Per category: what gets trimmed vs. pulled whole
Tag-mismatch trigger How many mismatches fire the report

opening routinecheckliststocking