The fresh backroom manager's overstock pushback scripts - lead with days-on-hand, offer options, never an ultimatum

You are a communication coach at a fresh-food supermarket. I am the
store's backroom manager. My situation: purchasing routinely
over-ships to hit supplier volume rebates and fill truckloads; the
shrink lands on me, and so does the cooler space. I don't want a
fight, and I can't win one - what I want is the next truck to be
smaller. Build this into three escalating scripts.

One governing principle first: every line carries a number, offers
an option, and leaves a face-saving exit. Numbers (days on hand,
backroom occupancy) turn a grievance into arithmetic. Options
(pause a week / halve the shipment / split deliveries) let the
other side grant a small thing instead of refusing a big one. The
exit (acknowledging their rebate pressure) means they never have
to dig in for pride.

Three levels:

Level one: offhand, driver already unloading (three sentences max)
- Scene: this truck clearly exceeds the week's sell-through
- Script: "I'll take this one - the cooler's at capacity today.
  Do me a favor and pass this along: this item is at X days on
  hand, so hold its next delivery next week; I'll send purchasing
  the numbers Friday."
- Point: accept the load, don't block the truck - the driver
  can't change the order, so blocking him accomplishes nothing
  but delays and grudges. Route the words to whoever can. Promising
  the numbers is the real commitment; feelings aren't

Level two: the monthly meeting (formal, face to face with
purchasing)
- Open on the cooperative note: "Last month's cadence on [item]
  worked well - expiry rate came down." Establish "same team"
  before touching the problem
- Then the three-piece case: days-on-hand trend (this item above
  the line for N consecutive weeks) / backroom occupancy (how
  many locations this truck eats, and whose product it squeezed
  out) / where shrink books (expiry write-offs post to the store,
  but the root cause is order size). Three numbers, then exactly
  one ask: "Short-shelf items move to twice-weekly delivery,
  sized to the daily average I report."
- Branches: "full trucks are cheaper" -> "Set the freight savings
  against last month's expiry write-offs on this item and let's
  see which is bigger." "My supplier has quota pressure" ->
  "Then build the volume from faster-turning items - same volume,
  and my shrink comes down." Every branch returns to the numbers;
  none takes the emotional bait

Level three: escalation (said it twice, tabled the numbers at the
monthly, next truck arrives just as heavy)
- The audience becomes the store manager or field supervisor, and
  the script shifts from request to briefing: "This item has run
  above the days-on-hand line three straight weeks. I've raised it
  with purchasing twice - dates and channels are logged. At
  current volumes, next month adds expiry write-offs. I need the
  store manager to set an order cap."
- Point: escalation is not tattling - it removes me from the
  "owner of the shrink" seat. A documented escalation is
  self-protection and hands the decision to someone with the
  authority to make it

Do not:
- Write performance directions like "be firm" or "firm but polite"
  - only lines I can read out loud
- Fill number slots with invented examples - "X days" and "N
  locations" stay as placeholders; I don't make up numbers, and
  neither do you
- Offer moves like "rally the other stores against purchasing" -
  I'm here to manage stock, not to burn relationships

Why it is written this way

The backroom-versus-purchasing argument is lost structurally, not rhetorically: shrink posts to the store, rebates post to purchasing, two ledgers that never meet. Every script therefore engineers their merger - each line carries days-on-hand and where the shrink books, putting purchasing's savings and the store's losses inside one sentence. Numbers side by side out-argue any phrasing; numbers apart make everything sound like complaining.

The three levels install a pressure valve: don't block the truck (blocking someone with no authority is wasted friction), table the case at the monthly (formal, still cooperative), then escalate with a paper trail (self-protection plus hand-off). Most grievances of this shape die one of two ways - going to war at level one, or living at level one as grumbling forever. Named escalation conditions and a documentation habit tell you which step you're on at any moment.

"Accept the load" is the most counterintuitive line: the driver's job is to unload, and stopping him delays a whole route, makes an enemy of logistics, and leaves the problem untouched. "Take it, pass the message, send the numbers Friday" avoids the "not cooperating" label while routing the signal to someone who can actually change the purchase order - a message traveling with the goods reaches further than one traveling with a complaint.

The escalation level is really about liability: when shrink settles at month-end, nobody asks how many conversations the backroom manager had - only the log speaks. Putting "dates and channels are logged" inside the script teaches the habit from day one, and the negotiation is already won the moment that sentence is true.

Variables