Fresh supermarket cashier - shelf tag says one price, the scale says another, scripts by direction of the difference

You are a cashier coach for a fresh-food supermarket. Write the
register-side scripts for "weighed fresh item: shelf tag price
disagrees with system price." Scene: the customer picked by the
shelf tag; weighing or scanning brings up today's system price;
the customer catches it at the lane (or on the receipt).

Rules of handling first, scripts second - with a line of customers
watching, the cashier's first need is a definite answer to "which
key do I press," and only then something to say.

Handling rules, split by direction (the directions are opposites):

Direction A - system price higher than the tag (customer pays more):
- Action rule: charge the tag price immediately (or follow the
  store's authorization convention in the variables - chains
  differ: some honor the tag, some charge system and refund the
  difference; tell me which before writing the scripts)
- Script points: one acknowledgment + immediate handling, no
  hollow promises ("we'll look into it" means nothing); after
  handling, note the bad tag and pass it on (see variables) -
  and the script should show it: "I'm having them fix that tag
  right now"
- Banned: "it's a system issue, there's nothing we can do" or
  "shelf tags are indicative only" - blaming the system pours
  fuel on the fire

Direction B - system price lower than the tag (store undercharges):
- Action rule: charge the low price, close the transaction, keep
  the line moving
- Script points: do not volunteer an explanation of "we mislabeled
  that" - if the customer didn't ask, ring the displayed amount
  and move on; if asked, one line: "the system price today is
  this one, so that's what you pay"
- The real risk in this direction is the cashier recalculating
  the difference back and forth with the customer and re-ringing
  the item twice - two re-rings jam the line and raise the
  cashier's own error rate

Two general add-ons:
- The long-line minimal version (one line per direction): one
  sentence of handling, no mid-transaction relitigating, log it
  afterward
- The escalation version for the customer who wants a reckoning:
  one closing line + how to summon the supervisor (bell / hand
  signal / name, per store - variable)

Hard format:
- Three sentences maximum per script, spoken register
- Each script leads with "press what, then say what" - action
  first, words second, order fixed

Do not:
- Use long apology templates ("we sincerely apologize for any
  inconvenience") - with a line watching, an apology past one
  sentence becomes the next complaint
- Coach the cashier into explaining the store's tag-management
  process or why mismatches happen
- Write "thank you for your understanding" - the goal is a fix,
  not understanding

Why it is written this way

What makes this scene special is that it's the one error that must be adjudicated on the spot, mid-line: a complaint can be handled in the office afterward, a price mismatch cannot - the customer is standing at the register with eight people behind them. So the structure is action-before-script: first the rule for which price to charge (which can be fixed in advance and memorized), then a sentence or two to keep the temperature down. Stores that never fixed the rule have cashiers improvising - and improvising is slow.

The two directions get separate sets because their philosophies are opposite: when the customer overpays, their money is at stake - be fast and settle it visibly; when the store undercharges, litigating the difference loses on both sides - take the low price, move on, fix the tag in the back. Training materials that merge the two get recalled wrongly under pressure, and wrongly-recalled rules mean a rulebook open at the register.

Direction B's "don't volunteer the mislabel" is a small but strategic line: store-wide tag-matching demands ("the tag said so - honor it on everything") usually start at one register with one "yeah, we mislabeled that." Ring the displayed price, fix the tag invisibly - cheapest path for customer and store alike.

Capping the apology at one sentence isn't coldness; it's respect for the queue. The patience of the people behind the customer is an asset in this scene too, and long apologies spend it while solving nothing.

Variables