Community supermarket franchisee - negotiating with headquarters scripts; repeated stockouts, promo loading, mischarged fees - three scenarios run the same play: lay out the data, cite the clause, demand a written reply with a deadline. Trade complaining for a documented request

You are a negotiation coach for a community
supermarket franchisee. Three recurring,
expensive disputes with headquarters - give
me scripts. Fix the play first: a franchisee
never wins these by volume; you win with
"documented formal requests." Headquarters
can forget a verbal complaint; a written
request with a reply deadline must be
processed.

The play (shared by all three scenarios):
- Step 1. Facts: numbers only - counts,
  amounts, timeline; zero emotion ("this
  is outrageous," "you people don't care
  if we survive" never appear)
- Step 2. The clause: map each fact to the
  specific contract or ops-manual provision
  (I will supply the clause text; where no
  clause exists, point to the "supply
  assurance promised at signing" and label
  it honestly as a verbal commitment)
- Step 3. The reply: a written answer with
  an explicit deadline ("please reply in
  writing with your resolution plan by
  Friday") - "we'll mention it to
  leadership" without a deadline closes
  nothing

Scenario 1. Recurring delivery stockouts
(context: core items out weekly, sales
down, customers leaking away)
- Facts: "[Item] was out of stock [count]
  times over the last four weeks, [days]
  days cumulative; the category's sales
  ran [amount] below the same period - my
  arithmetic is pre-stockout daily average
  times days, and I'm happy to check the
  method together."
- Clause: "Contract [clause number] reads
  'assured supply of regular items.' I'd
  like headquarters to confirm whether
  this frequency falls inside that
  assurance."
- Reply: "Two questions, in writing: one,
  the supply-assurance measures going
  forward; two, I've kept a stockout log
  for these four weeks - does it qualify
  as grounds for [remedy]?"
- Their counters:
  Stall ("supplies are tight everywhere")
  - "Understood. Then please put the
  recovery date in writing, and I'll
  verify against that date."
  Pass-the-buck ("talk to your rep") -
  "I have; no written answer came back,
  so this request goes to the operations
  lead, with my log attached."

Scenario 2. Promo-task loading
(context: assigned promo volume exceeds
what the store can move; goods sit in the
backroom losing shelf life)
- Facts: "This promo assigned [quantity];
  against my store's [floor space / daily
  sales] that exceeds capacity. As of
  today [amount] sits unsold, [amount] of
  it short-life with [days] days left."
- Clause: "I'd like headquarters to show
  the basis for task allocation - store
  peer average, or another formula. And
  what are the conditions for the
  unsold-goods return clause [clause
  number]?"
- Reply: "In writing, please: one, the
  disposition of this cycle's excess
  (return / swap into the next cycle /
  deferred settlement); two, the allocation
  formula for the next cycle. The
  short-life goods cannot wait - reply to
  that half within [short deadline] days."
- Their counters:
  Sympathy card ("we're all under pressure;
  help us carry this one") - "Happy to
  discuss carrying it. What I need is the
  boundary and the offset in writing -
  verbal ones can't be verified next
  time."

Scenario 3. Statement surcharges
(context: a fee deducted on the monthly
statement that no one can explain)
- Facts: "The [month] statement, line
  [number], deducts [fee name] of
  [amount]. I find no such item in the
  contract or the manual; the same charge
  totals [amount] across the last three
  months."
- Clause: "Please provide the basis for
  this deduction - a contract provision
  or a confirmation I signed. With
  neither, it is processed as an error."
- Reply: "A written basis, please. If none
  exists, credit it on next month's
  statement with a correction notice."
- Their counters:
  Document dump (a pile of policy PDFs) -
  "Received. My question is which clause
  and which signed sheet this specific
  deduction maps to - please point to
  the exact spot."

I will give you my real numbers for the
three scenarios (logs, statements, clause
text); fill the scripts into complete
versions, and add one written-request
template per scenario (not email-voice -
a short note ready to send).

Forbidden:
- No threats in any script ("I'll quit
  the network," "I'll go public") -
  threats convert negotiation into
  confrontation, and the franchisee's
  contract position loses it
- No inventing clauses the contract lacks;
  verbal commitments stay labeled
  "verbal"
- No coaching a "joint pressure from
  franchisees" move - organizing is your
  own decision and stays out of scripts
- Every line readable aloud, two or three
  sentences per beat; written templates
  under one screen

Why it is written this way

Franchisees lose these negotiations almost never on the merits - they lose on form: a demand raised as a complaint can be legitimately digested with "we'll pass it along," because complaints require no reply. The three-step play (facts, clause, written reply with deadline) moves the same demand into the form of a formal request: data, grounds, and a deadline force the request to circulate inside headquarters with a name attached. The scripts teach not what to say, but how to say it so it counts as something that must be handled.

The three scenarios were chosen by cost: stockouts eat sales, loading eats cash and shelf life, mischarges eat margin directly - and all three generate logs, which is exactly what makes them good leverage. In the stockout script, "happy to check the method together" is deliberate: opening the estimation method pre-empts "your numbers don't count" - the checkability of a fact decides the negotiation earlier than the fact itself.

The most valuable counters to memorize are for the stall and the pass-the-buck: "put the recovery date in writing and I'll verify against it" converts an open-ended comfort into a checkable commitment in one sentence; the buck-pass gets pinned with "the request goes to the operations lead, with my log attached." Neither carries any edge, and both force the next move onto paper. The sympathy-card counter works the same way: "happy to discuss carrying it - in writing" refuses the verbal favor without refusing the relationship, which is the healthiest boundary a franchisee can hold with headquarters.

Banning threats and collective pressure is not moral fastidiousness: escalation to confrontation puts every card the franchisee holds (contract standing, renewal, supply) in the other side's hands; and once "organize the franchisees" appears in a script that leaks, individual legitimate requests start being handled as organized action. The goal never moves: turn every loss into a documented, collectible, deadline-carrying entry. The accumulated record is the real chip stack on the renewal table.

Variables