Fresh-store ramp-up monitoring SOP - the dip is a normal chapter; watch signals by stage, step in only on red lines

You are a store-opening consultant for a fresh-food chain. Write
the 6-month new-store "ramp-up monitoring" as an archivable SOP
for the regional manager. Anchor it on the mistakes we've paid
for: two new stores panicked when sales dipped in month two -
one swapped the manager, one ran a major promo to force volume -
and both proved to be friendly fire. The dip is a normal chapter
of the ramp; the real holes were elsewhere (one never built
repeat customers, one sat in the wrong trade zone). This SOP's
mission: separate "normal dip" from "actually broken."

Stages and monitoring (all thresholds parameterized; I preset
no numbers):

[Opening stage: weeks 1-4]
- Core stance: opening-surge data has almost no decision value -
  friends-and-family visits, opening promos, neighborhood
  curiosity - all one-time traffic. Do **not** read absolute
  sales this month. Watch two structural measures only:
  - Repeat signal: second-week repurchase rate among members
    or regulars (each store defines its own capture: loyalty
    system, receipt retention, cashier recognition - all legal)
  - Category mix: traffic-driving fresh items versus everyday
    items - if only the traffic drivers sell, the neighborhood
    has not yet filed this store under "where I buy groceries"
- Don'ts this stage: no large ordering adjustments (the sales
  data is distorted; any adjustment is wrong on arrival); no
  evaluation of the manager

[Dip stage: months 2-3]
- Core stance (this goes in a prominent place in the SOP):
  **the dip is normal**. The surge recedes and sales step down
  - every new store's path. This stage watches for the
  stabilization, not the level:
  - Two consecutive weeks of week-over-week movement inside a
    normal band = stabilized; where it stabilizes is this
    store's true baseline
  - Keep watching the repeat signal - a rising share of
    returning customers during the dip is a good sign
- Don'ts this stage: don't replace the manager (fighting a
  normal dip with a personnel change treats a growth problem
  as a competence problem); don't force volume with a major
  promo (it buys the same one-time traffic, burns money, and
  pollutes the baseline read)
- Red lines (touch them and you act): sales trending down
  week-over-week for 4 straight weeks without stabilizing;
  the repeat signal flat for 4 straight weeks; veteran staff
  attrition past threshold

[Stabilization stage: months 4-6]
- The baseline has formed. Compare against mature stores of
  the same type - but only on the structure of the gap, never
  absolute values:
  - Gap mostly in traffic -> trade-zone penetration problem:
    circulation, assortment, community presence
  - Gap mostly in basket -> assortment and merchandising
    problem: traffic drivers sell, margin items don't
- The two gaps take entirely different paths; spell out what
  moves and who leads for each
- End of month 6: the ramp verdict, and all three conclusions
  are legal: on track / structural gap (fixable - list the
  fixes and deadlines) / wrong trade zone (not fixable -
  enter the closure evaluation process)

Attach a one-page "ramp monitoring rhythm": what to read
weekly, what structure to read monthly, what verdict each
stage-end produces.

Do not:
- Predict "where a normal ramp curve should sit" - curves
  differ by trade zone, and any preset number is invented
- Write mood-language like "stay patient" or "keep
  supporting" - the SOP deals in actions and red lines
- Anything outside the red lines goes under "don'ts" - most
  of ramp management is managing your own hands

Why it is written this way

The SOP exists for one sentence: separate the normal dip from real failure. A month-two drop is structural - one-time traffic leaving - and management's first reflex is to be triggered by exactly that: swap the manager, force a promo, both of which pollute the data and damage the organization. "The dip is normal" goes in a prominent place as a chemically stabilized sedative for the regional manager - institutionalized calm outlasts willpower, and the opening story of two friendly-fire stores is its evidence base.

The opening stage watches only repeat rate and category mix: surge data is noise, and deciding on noise (adjusting orders, rating the manager) is shooting blindfolded. The repeat signal answers the only question that matters - have the neighbors started filing this store under "where I buy groceries" - and that answer decides everything about the next five months. Absolute sales cannot see it at all.

The stabilization stage compares gap structure, not absolute values: 20% behind a mature store in sales carries no action; behind on traffic versus behind on basket does - the first moves penetration, the second moves assortment and merchandising, with different owners and clocks. Lock both paths in writing and comparison finally leads somewhere.

"All three conclusions are legal" is written for month six: verdict systems naturally admit only "on track" - but until "wrong trade zone, evaluate closure" is a legal exit, nobody will dare render it. A standard with no exit produces nothing but self-soothing "basically on track."

Variables