Snack shop customer service - foreign object and spoiled product complaint SOP - from first message to same-batch pull-and-check, with fixed response clocks, the four evidence fields, tiered compensation, and an escalation line; anything involving illness does not wait overnight

You are a complaint SOP writer for a snack shop.
Write a "Foreign Object and Spoiled Product Complaint
SOP" for store customer service (usually doubling as
cashier or stocker), escalating to the manager beyond
their authority. I want a document that runs on the
day it happens, with no improvisation required.

Put this at the top of the SOP:
how this complaint is handled decides whether it
stays a payable complaint or becomes a fermenting
food-safety incident. Both service instincts are
traps: admit and pay on the spot (the same batch is
still selling on other shelves), or demand the
customer come in with a receipt (interrogator's
posture toward the person holding the evidence).

Step 1 - Respond and preserve evidence (within 2
hours of the message)
- Log four fields: item and pack size, batch number
  and best-by date from the packaging, purchase
  channel and time, the problem description in the
  customer's own words (never paraphrased)
- Ask the customer for two things: photos (the
  problem area + the full front of pack with batch
  number visible) and keeping the packaging and
  remaining product - phrase it as "help us check
  this properly," never as "we need proof"
- No on-the-spot admission, no on-the-spot price:
  "I'm logging this now; you'll have our resolution
  today" - a deadline, not a verdict

Step 2 - Same-batch self-check (same day, without
waiting for the customer)
- Pull and quarantine this store's same-batch stock;
  inspect the rest of the batch for the same issue
- Trace the batch's receiving date, where it sits,
  and whether any other customer reported the same
- Log the check in the register whether or not it
  found anything

Step 3 - Resolution (within 24 hours)
Tiers:
- Base: refund or replacement, customer's choice -
  within the rep's own authority
- Illness involved: ask after the person's condition,
  point to medical care, and explain the receipt-
  based expense path (terms confirmed by the manager
  before being quoted; the rep never promises an
  amount)
- Compensation multipliers and statutes: the rep
  quotes no law and promises no multiplier at the
  counter - the unified terms come back from the
  manager or owner. Reason written into the SOP:
  a verbal promise, once spoken, is the store's
  obligation

Step 4 - Escalation (same day, any one trigger)
- The customer or anyone who ate the product feels
  unwell
- A second report arrives on the same batch
- The customer mentions exposure, reporting to
  authorities, or media
Escalation path: rep -> manager -> owner, each level
with a named contact and "next level if unreachable"

Step 5 - Follow-up and filing (within 3 days)
- One-line follow-up: resolved or not, and the
  person's condition
- Register fields: four evidence fields / resolution /
  self-check result / customer response / handler
- Monthly: check whether repeated same-type reports
  point at one supplier or batch - that is what
  the register is actually for

Constraints:
- Every clock is fixed (2 hours / same day / 24
  hours / 3 days); no "as soon as possible," no
  "immediately"
- Anything involving illness moves through the whole
  flow before the day ends
- No "raise food-safety awareness" - this SOP
  contains only actions and clocks

Why it is written this way

The same-batch check runs without waiting for the customer because that parallelism is the boundary between this SOP and a generic complaint flow. The real risk in a food-safety complaint isn't what this one case costs - it's that the same batch is still on the shelf. Every hour the pull-and-quarantine slips raises the odds of report number two, and report number two collapses the "isolated incident" story for good. Logging the check even when it finds nothing also builds the record any later escalation will demand.

The phrasing "help us check this properly" solves a two-way problem in one move. Asking for photos and packaging as "we need proof" interrogates the customer - it hands the burden to the person harmed and turns the conversation adversarial on the spot. Asking so "we can check this properly" puts both parties on the same side of the investigation. The compliance rate on evidence differs accordingly, and without the batch number and packaging, every later step in this SOP is running blind.

No statute-quoting at the counter guards against promising more than gets delivered. Anything a rep says aloud, in a customer's recording, becomes the store's obligation - and compensation statutes have preconditions a rep under pressure will misapply. Routing the terms through the manager costs half a day and prevents the second complaint, the one that hurts more than the first: a promise walked back.

Every clock is a fixed number because "as soon as possible" in a real store means "after the rush." These complaints have a golden window measured in hours - the customer's patience, the fermentation risk, and the same-batch exposure all race the same clock. Hour figures are what make the flow checkable and the delays ownable.

Variables