N NoBullshit.wiki 中文

Community supermarket receiving - rejected-goods holding and return SOP; the refusal was the easy part. How rejected stock is held, how it is tagged, how fast it leaves, and how the paperwork closes - every step with an owner and a deadline

Works with:Claude / GPT-4 classCategories:Community SupermarketLevel:Intermediate Updated

You are a receiving advisor for a community
supermarket. Write an archivable, trainable
Rejected-Goods Holding and Return SOP.
Context: the store averages [rejection
frequency] rejections a week (quality, shelf
life, wrong item). The act of refusing, staff
already know; everything that fails happens
afterward - where the goods went, where the
paper is, who was tracking it. Structure the
SOP in four phases: at the truck / holding /
return / closing.

1. At the truck (the ten minutes the
   rejection is made)
- Three elements, all mandatory: photos
  (whole batch plus close-ups, phone
  timestamp on), a rejection slip (item /
  quantity / reason), and the driver's
  signature
- Driver refuses to sign: photograph the
  original slip, record the plate number,
  and the rejection stands anyway - a
  missing signature limits nothing as long
  as the evidence exists
- Reasons state facts, not feelings:
  "production date leaves 3 days of shelf
  life, below store policy" works; "this
  stuff is no good" does not
- Partial rejections: the acceptable
  portion gets signed in normally; only the
  rejected portion runs this SOP - never
  "refused the whole truck" over an
  acceptable load

2. Holding (between rejection and return)
- Rejected goods enter the rejection bay:
  physically separated from saleable stock
  (barrier, floor tape, or a dedicated rack)
  - never into normal backroom slots, never
  into normal cold-room positions
- Hang a "rejected - pending return" tag:
  item / quantity / rejection date /
  supplier / owner (the receiver who
  rejected it)
- Temperature-controlled goods (chilled,
  frozen) still get held at their original
  temperature zone - rejection is a
  commercial dispute, but the goods are
  still perishable; if they spoil in our
  care, the store owns part of the loss
- Goods held past [holding limit] hours
  without shipping back: the tag turns red
  and the store manager is escalated to

3. Return (goods leaving the store)
- Tracked returns: the supplier's next
  delivery carries them back, or the
  supplier's designated carrier collects -
  the method follows the supplier's billing
  rhythm, never the driver's on-the-spot
  preference
- Handover: count, sign the return copy of
  the rejection slip, photograph before and
  after loading
- Suppliers who never arrange pickup (past
  the [chase limit]): the store manager
  takes it up with the supplier's contact;
  if still unresolved, follow the contract
  toward write-down or abandonment - and
  abandonment requires the manager's written
  sign-off

4. Closing (what "done" means)
- Three items close a case: the store copy
  of the slip archived, the document's
  status closed in the system, the holding
  tag removed
- The rejection log gets a weekly check:
  date / supplier / item / value / status
  (holding / returned / closed / stalled) -
  anything sitting in "holding" over a week
  gets named
- Monthly, the log goes to the store
  manager with the reconciliation - the
  rejection record is the store's claim
  against the supplier, not scrap paper

Forbidden:
- No "store rejected goods appropriately" -
  holding conditions are fixed (temperature
  zone, segregation, tagging)
- No "small amounts may be handled
  informally" loophole - small rejections
  are exactly where the books rot; if a
  simplified path is truly needed, the
  manager authorizes fixed categories in
  writing, never the receiver's on-the-spot
  judgment
- Two pages maximum; each phase carries its
  deadlines and owners; no paragraphs about
  purpose

Why it is written this way

This SOP fills the stretch nobody wants to document: teaching how to reject is everywhere (quality standards, evidence photos), while the part where stores actually lose money - afterward - is written nowhere. Goods squat at the dock for three days and either creep back onto the shelf (the rejection never happened) or rot in holding (responsibility flips to the store); the supplier turns around and says "we never received a return," and the store has no handover evidence. The four phases - at the truck, holding, return, closing - follow the lifecycle of the goods and the paperwork, each with an explicit finish condition, none papered over with the word "follow up."

The temperature-controlled clause says something counter-intuitive: rejected chilled goods still get held in their original zone. A receiver's instinct is "it's rejected, why care about temperature" - but ownership transfers when the return completes, and if the goods spoil in our care, commercially it was a rejection and operationally it was negligent custody, and the supplier will exploit that distinction precisely at claim time. The rule protects the store's own standing to claim.

The closing checklist and the weekly log review are this SOP's actual teeth: rejection processes rot at exactly one point - the slip never closed, the tag never removed - until three months later the holding bay holds a pile nobody can attribute. Anything stuck in "holding" over a week gets named: make the stall visible and the process stops leaking silently. Routing the monthly log to the store manager upgrades rejection records into bargaining capital: a year of which supplier got rejected how often for how much is the hardest number at buying negotiations - throw it away and you hand it back for free.

Banning "small amounts handled informally" is a scar clause: tiny rejections (one crate of milk, two packs of greens) are the ones most often waved off with "forget it," and the books rot from exactly there - small per case, frequent per year, and a wall of unexplainable holes at annual count. If a fast lane for small amounts is genuinely needed, authorize fixed categories on paper rather than leaving it to the receiver's discretion at the truck: hand a gate to on-the-spot judgment and it opens wider every week.

Variables

Variable Description
Rejection frequency Rejections per week - sizes the holding bay and sets log cadence; high-frequency stores should check the log daily
Holding limit How long goods may sit in the bay before escalating to the manager - match it to supplier delivery rhythm, usually 48 hours
Chase limit How many days without a pickup counts as the supplier stalling - the trigger line for the manager to step in; write it next to the log's stall-naming rule

rejectionsreturnsSOP