Purchasing scripts for a bad batch of beans - negotiate the swap with your dial-in log and the batch number, this batch only, asks only, no verdicts

You are the purchasing lead of a coffee shop. Turn the
"flavor-defect bean return/exchange" conversation below
into scripts that can be read verbatim, in a phone
version and a chat version, covering four beats: the
open, the evidence, the ask, and the disagreement
ladder. Store details stay as 【】 placeholders.

Background (put it at the top of the script page): a
new batch is extracting unstably and tasting clearly
off (burnt and woody / burlap bagginess / sharp sourness
that won't settle). We need a swap from the roaster,
whose first reaction will likely be "your parameters
are off." The goal is not winning - it's getting this
batch replaced and the next batch's risk reduced.

The open (frame it as joint troubleshooting, not blame)
"Hi 【name】 - we've been on batch 【batch no.】 for two
days and the shots are off. I've put the records
together and would like to walk through them with you.
To be clear up front: I'm not saying whose fault it is
- I want the beans handled and the next batch
protected."

The evidence (only three verifiable things)
"Three records for you. One, our dial-in log: same
grinder, same recipe, and this batch is running
【】 seconds fast/slow against the previous one. Two,
our cupping notes done to the protocol you showed us -
three words: burnt / baggy / sharp-sour. You can re-run
it under the same settings. Three, I've kept the sample
bag and batch number; happy to ship it back."
Points: the evidence is exactly the log, the cupping
sheet, and the batch number; descriptors stay in the
three buckets - never "tastes bad" or "something's
off," which nobody can re-test.

The ask (clear, single, this batch only)
"For the remaining 【】 bags we'd like 【replacement/
refund】. And for the next batch, could you include
the roast profile, or take the roast level one notch
【direction】? Let me know what works."
Points: two items, nothing stacked on top - no lost-
sales compensation. Add that and it stops being a
technical check and starts being a commercial dispute.

The disagreement ladder (when they insist it's your
extraction)
"Let's do this: you re-test using the parameters in
our log, and we keep our sample. If your re-test is
clean, we'll absorb this batch and pay the freight. If
it confirms the defect, we go with the plan above.
Both sides keep records - nobody has to guess."
Points: hand them an exit that requires no admission -
"re-test" is cheaper than "we were wrong," and the
cheaper the exit, the more likely it gets taken.

Chat version (three messages, no voice notes)
1. "Hi 【name】 - batch 【batch no.】 is extracting off.
  I've got our records together - got ten minutes for
  a call today?"
2. Photos of the three evidence pieces: dial-in log
  page / cupping sheet / bag label with batch number
3. The two asks in text: "Remaining 【】 bags as
  【replacement/refund】; next batch with roast profile
  or one notch 【direction】. What works for you?"

Constraints:
- No emotional words anywhere (disappointed,
  ridiculous, "every time"), and no re-litigating old
  batches - this batch only; open the history books
  and today's ask dies
- No diagnosing their side ("you over-roasted it") -
  report only what we measured
- Every line speakable verbatim; no "be sincere" or
  "argue from facts" style stage directions

Why it is written this way

The outcome of a return negotiation is decided by the shape of the evidence: say "it tastes bad" and the only possible reply is "parameters," and the conversation idles. Lay out the extraction-time drift at identical settings, the three-word cupping sheet, and the retained batch-numbered sample, and the topic moves from taste disputes to fact-checking. Descriptors are locked to burnt/baggy/sharp-sour because "could be brighter" can be argued forever while "burnt" can be re-tested by anyone - auditability is the entire design principle of this evidence.

The ask is two items with nothing stacked: replace this batch, improve the next. Attach lost-sales compensation and a technical check turns into a commercial dispute on the spot - the roaster's posture switches from "how do we fix it" to "how do we avoid liability." The defect sits in every cup served meanwhile; a fast swap beats a won argument.

The disagreement ladder centers on the act of re-testing: it lets the other side move forward without conceding, with both sides keeping records. Negotiations deadlock on unwillingness to bow first far more often than on genuine conflicts of interest - replace the bow with an experiment and the road opens. The re-test binds both ways (defect confirmed, the plan proceeds; clean, we eat the batch and the freight), which makes saying yes nearly costless.

The chat version compresses to three messages because that's the real medium: calls don't get scheduled and voice notes don't get heard, while three messages - intent, evidence, ask - can be handled in the gap between the roaster's own customers. Evidence travels as photos, not paraphrase, because photos carry no tone and escalate nothing; in a text negotiation, the form of the evidence sets the temperature of the conversation.

Variables