N NoBullshit.wiki 中文

Deli stall cashier - rounding, tabs, and third-party comp scripts: drawing the line on favor-account transactions, in full sentences

Works with:Claude / GPT-4 classCategories:Deli StallLevel:Beginner Updated

Write a set of favor-account scripts for a cooked-food stall's
cashier, covering three moments. For each: the situation / a
line readable verbatim / why it works / the never-say version.
I am the cashier; my rounding authority is [X] or less.

Moment 1 - The regular wants rounding ("It's 37 - make it 35,
you always do")

Line A (within authority - round down fast):
"Done, 35 - that's 2 off, I've noted it in the book. Here you
 go."
Why: a rounding within authority should land instantly -
dithering offends more than refusing. But "noted it in the
book" is not optional: it turns a favor into a ledger entry,
so at month-end those 2 have a home and the cashier explains
nothing.
Line B (over authority - offer an alternative, don't dig a
hole):
"Two is past what I can take off on my own - here, call it 36,
the 1 is on me. Fair enough?"
Why: an over-authority gap can't be silently swallowed, and a
flat "no" pushes a regular away; splitting the difference shows
exactly where the authority line sits without chilling the
air.
Never say: "No can do, the boss will bite my head off" (casts
the boss as the villain and sells off the boss's goodwill into
the bargain); "I rounded it for you last time too" (favor
accounts must never re-open the ledger - the moment you do,
it's an audit, not a favor).

Moment 2 - The regular asks for a tab ("Put it on, I'll settle
tomorrow all together")

The line (the registration trio: amount, date, name):
"Sure - 38.50, under your name, Ms. Zhang, settling tomorrow
 when you come. Let me read it back: Ms. Zhang, 38.50,
 tomorrow."
Why: whether a tab ever collects depends entirely on the moment
it's created. The read-back fixes the amount without dispute,
the date turns "tomorrow" from pleasantry into deadline, and
the name gives the debt a hook. Reading it aloud converts the
entry from the cashier's private note into a two-party record.
Never say: "Sure, sure, I've got it in my head" (an unwritten
tab is a bad debt - three days later the two remembered totals
differ, and what tears is not the account but the
relationship); "No tabs, no tabs" (treats a neighbor like a
stranger; a stall that says this three times a day is a stall
with a countdown).

Moment 3 - Third-party comp instruction ("The boss's wife said
this one's free" / "The boss said knock it down to round")

The line (ring up, verify, refund on the nod):
"Here's what I'll do - I'll ring it up at the normal price
 first, and I'll call the boss's wife this second. The moment
 she nods I refund you - two minutes."
Why: a relayed verbal instruction can't be refused on the spot
(refusing embarrasses the messenger) and can't be honored
silently (at month-end the unexplained gap is the cashier's).
Ringing up normally keeps the money traceable; verifying gives
the instruction a source; refunding on the nod - after three
steps the favor, the ledger, and the cashier all come out
clean.
Never say: "If she said free, then free" (the cashier
underwrites someone else's promise - if it turns out wrong,
the bag is entirely yours); "Nobody told me that" (challenges
the messenger on the spot and turns verification into
confrontation).

Constraints:
- Every line complete and readable verbatim - "use judgment"
  coaching banned
- Each script must carry one recording or verification action
  (noted in the book / read back aloud / phone the owner) -
  pure lines without actions are not allowed
- The rounding authority X is the owner's call; these scripts
  never widen it
- No "keep smiling" filler

Why it is written this way

The whole set runs on one sentence: every favor transaction must leave with a recording action attached. "Two off, noted in the book," "Ms. Zhang, 38.50, tomorrow," "rung up normally, verifying now" - each moment welds one action into the line, because a cashier's real risk isn't offending a regular; it's facing a month-end gap with no way to explain it. The craft isn't in sounding warm - it's in every concession having a paper trail: the rounding has a log, the tab has a registration, the comp has a verification. The favor gets granted, and the books stay standing.

The tab moment is the critical one. "An unwritten tab is a bad debt" is not rhetoric: three days on, two memories of a verbal tab have diverged by a few units, and what tears isn't the balance, it's a decade of neighborly standing. The registration trio plus the read-aloud makes the debt a jointly confirmed fact at the moment it's born - and the read-aloud has a side effect worth noticing: a deadline the customer personally agreed to behaves nothing like a pleasantry, and collection rates show it.

The third-party comp moment is the cashier's flak jacket. "Ring up, verify, refund" keeps the money on the books throughout: if the comp is real, the refund traces back cleanly; if the instruction was misremembered (or invented), the original sale is recoverable. The never-say "Nobody told me that" deserves its own look - it isn't a rude line, but it converts "verify whether this instruction is real" into "accuse the messenger of lying," and with that one shift the scene stops being about a comp and starts being a fight. A register script only ever handles the path of the money, never the rightness of the people - that is how this trade survives inside a web of familiarity.

Variables

Variable Notes
Rounding authority X The largest discount the cashier may grant alone - the owner fixes it in writing as part of the handover; beyond it, the verification path is mandatory
Tab scope Which regulars may run tabs and the per-tab cap - scripts never widen the owner's tab policy; outside scope, the line is "settle today, please"

favor accountsroundingtab registration