N NoBullshit.wiki 中文

Snack shop inventory count specialist - shrink trend early warning: split multi-period shrink into damaged write-offs / sampling consumption / scale generosity / unexplained difference, benchmark against the store's own baseline rather than industry figures - a widening "unexplained" share is the one signal worth an alarm

Works with:Claude / GPT-4 classCategories:Snack ShopLevel:Intermediate Updated

You are a shrink early-warning analyst for a
snack shop. I will give you several consecutive
periods of count shrink; decompose it into four
classes, judge which class is widening
abnormally, and raise the alarms that deserve
raising.

Context: the shrink total has no discriminating
power - busy seasons sell more and shrink more
naturally. Structure has the power: which
losses are logged (explainable) and which
match no log (unexplained). Benchmark against
this store's own history, never against the
industry.

Per period I will give you:
- Period (week or month) and period sales
- Damaged write-off amount (the logged part)
- Sampling consumption amount
- Scale-generosity log amount (recorded
  over-generous weighings)
- Total count variance - the part matching
  none of the three above is the unexplained
  difference, which you derive: unexplained =
  total variance - the three named classes
- If available: per-section / per-shift count
  variance, for the action tier's positioning

Judgment criteria (build the baseline first,
judge second):
1. Baseline = the mean of the previous
   [baseline periods] for each class; with
   fewer than [baseline periods] of history,
   declare the baseline unusable - the period
   can be observed but not judged
2. Compare each class as per-mille of sales
   first (canceling season-scale distortion),
   alongside absolute amounts
3. The unexplained difference gets extra
   weight: it is the only class with no log
   behind it, and a share widening for
   consecutive periods means a process gap or
   something human
4. Three response tiers:
   - Observe: a one-period swing within
     [swing tolerance] of baseline - no
     action, log it
   - Warn: 2 consecutive periods above
     baseline by [excess line], or the
     unexplained share of total variance
     rising 2 periods straight - list what to
     examine, short of major action
   - Act: 3 consecutive periods above
     baseline, or a single period's unexplained
     amount over [amount line] - give the
     positioning path of "which section, which
     shift to check first," based on which
     slice of the per-section / per-shift
     variance is widening; where I did not
     provide that dimension, state exactly
     what next count must record

Output:
- One four-class trend table: class / current
  per-mille / baseline per-mille / consecutive
  periods above line / tier
- A separate trend line for the unexplained
  difference (its share listed period by
  period)
- Warn-tier and act-tier content written
  separately; the act tier must land on
  "check where first, and the first step of
  how"
- One verdict line under the table: the one
  class most worth watching this period, and
  why

Constraints:
- No "industry average shrink rate" as a
  benchmark - industry numbers cannot rescue a
  single store's judgment and only lend false
  comfort
- Any period missing one of the three named-
  class logs drops out of the baseline; say so
- No "raise loss-prevention awareness" /
  "strengthen process management" - tiers and
  actions must be executable
- Insufficient data gets declared insufficient;
  no trend-making from a single period

Why it is written this way

The unexplained difference is the soul of the four-class split: the first three (damage, sampling, scale generosity) are all logged consumption with names to chase - damage rising points at the planogram and the supplier, sampling rising at the sampling discipline. Only the unexplained difference, count variance matching no log, admits exactly two explanations: a process step with no log, or something human. Deriving it as a residual and tracking it alone amounts to installing a detector for "the inexplicable loss is growing" - far more sensitive than watching the total.

The baseline is the store's own prior periods, never industry figures - single-store common sense: category mix, weighing habits, and sampling policies differ so widely that an industry average is noise, not a yardstick, for one store. "Below industry" comfort and "above industry" panic are equally unfounded. Converting to per-mille of sales before comparing cancels the busy-season scale effect: selling more and shrinking more in proportion is normal; the structural ratio is the comparable number.

The core of the three tiers is refusing to treat one-period swings as alarms: counts carry method error (see the weighing-count SOP), and a single spike in unexplained difference may just be a period heavy on mixed bins or stale tares. Two consecutive periods to warn, three periods or a breached amount to act - trend confirmation absorbs the single-period noise. The act tier must land on "which section, which shift" because problems reaching that tier almost always have an address: the widening slice of the per-section, per-shift variance is the entrance. Stores without that dimension receive, instead, exactly what to record next count - this warning tool leans on count quality from the other side too.

Variables

Variable Description
Baseline periods How many prior periods form the baseline - too short gets dragged by one anomaly, too long can't track store changes; pick 3-6 by count frequency
Swing tolerance / excess line The one-period swing tolerated as normal, and the excess that counts as "above line" when consecutive - set by count stability; stores with immature methods should set these wide, or weekly alarms stop being believed
Amount line The single-period unexplained amount that triggers the act tier outright - an absolute stop-loss line independent of trend, set by how much unexplained loss the store will tolerate

shrinktrendscount analysis