Convenience store inventory count specialist - rolling count SOP for the store that never closes: the cut-off lands on the slowest hour of the day, every document inside the window has exactly one destination, one or two zones a day cycles the whole store, and the lone overnight clerk never counts high-value zones

You are an inventory count procedure designer for a
convenience store chain. Write an archive-ready
"rolling count during trading hours" SOP for one
24-hour, never-closes store. Readers: the inventory
count specialist, the store manager, overnight
staff. One premise - this store has no closed
hours, the count always runs alongside trading, and
every rule below starts from that fact.

1. Frame and cadence
- The rolling count is a standing cycle count, not a
  monthly event: the store splits into [ ] count
  zones; one or two zones counted per day; the full
  store cycles in [N] days
- High-value zones (highest-price items outside
  tobacco) get [ ] extra counts within each cycle
- The rotation sheet hangs in the back office:
  which zone each day, who counts, who re-counts;
  a zone not finished rolls to the next day, never
  skipped to the next cycle

2. Cut-off and the snapshot (every document has
   exactly one destination)
- The cut-off lands on the lowest-traffic hour of
  the day; the exact clock time [ ] is set from
  POS hour-by-hour sales data and does not drift
  with shift changes
- The book figure = the system on-hand snapshot at
  the cut-off
- Document destinations inside the counting window
  (one rule each, no alternatives):
  Sales - cannot stop. Each zone's sheet records
  its "zone finished" time; reconciliation
  reconstructs from the POS journal: counted qty +
  sales in that zone between cut-off and finish
  time = on-hand at cut-off, compared against the
  snapshot
  Deliveries - nothing received inside the window
  hits the shelf or the count; it parks in a
  marked held-receiving pen and posts after the
  count
  Write-offs and returns - goods are segregated
  and tagged inside the window; documents post
  after the count
- Pass/fail line: any document inside the window
  whose ownership cannot be stated is a process
  failure, logged in the day's exception column
  naming the document and the step where it
  stalled

3. Category carve-outs
- Foodservice and same-day-zero items: not in the
  rolling count; daily reconciliation - opening +
  received - sold - written off = expected on
  hand - checked against a physical count the same
  day, variances logged the same day
- Tobacco: not in the rolling count; runs its own
  dedicated count
- Held receiving and delivered-not-yet-posted
  stock: counted on its own sheet, never mixed
  into zones

4. The lone overnight clerk
- Solo-staffed hours ([ ] to [ ]) count
  non-high-value zones only; high-value zones are
  scheduled exclusively into dual-staffed hours
- The reason goes in the SOP body, so staff know
  why: a solo counter has no verifier - right
  cannot be proven, wrong cannot be ruled out -
  and when a variance lands, the counter cannot
  speak for themselves. A second person present
  protects the store and the counter both
- A variance found during solo hours: log it, do
  not dig; it gets re-counted by someone else in
  a dual-staffed window

5. After the count
- Variance logging: within [ ] hours of the zone
  finishing
- Re-count: over-threshold items re-counted by
  someone other than the original counter
- Variances over [amount] escalate to the store
  manager the same day
- The same zone showing same-direction variances
  [N] cycles running escalates to a targeted
  review, off the ordinary variance log

Count discipline (goes in the SOP body):
- Quantity columns on count sheets are blank; book
  figures never appear on the counting floor
- No cell ever filled from "we just counted this
  zone, it's about the same"
- No quiet netting: surpluses do not cancel
  deficits; each item's variance reports on its
  own line

Constraints (for the AI):
- Do not invent a "normal range" for convenience
  store count variance - there is no accepted
  watermark; this SOP sets process, not quality
  thresholds
- Every day count, clock time, amount, and count
  frequency is a [ ] variable; the structure of
  the SOP depends on no specific number
- Every rule must answer "who does it, what they
  do, how we verify it was done" - rules that
  cannot, do not get written
- No system names, no brand names

Why it is written this way

One destination per document is the foundation of the whole SOP. A never-closing store cannot count-then-reopen, so the book figure has to be assembled: the snapshot sets the base and the POS journal does the reconstruction. Each of the three document types gets exactly one destination because a rule with two options gets resolved by whoever is on shift, in favor of whatever is easiest at three in the morning - two months of that and the store's weekly numbers stop being comparable. The exception column exists as this rule's detector: a document with unclear ownership is not a variance, it is a process failure, and only by logging the two separately does the store see where the process leaks and how often.

A daily micro-cycle instead of a monthly full count is the decisive departure for this format. For a store that never closes, a monthly full count is a monthly battle that needs extra staff on a floor that never empties. The rolling count spreads the same coverage into the quietest hour of every day - one or two zones, over in minutes, no extra shift, no overtime - and the detection window for a variance shrinks from a month to a single cycle. The extra counts for high-value zones inside each cycle put the attention budget where the money density is: equal frequency for every zone is averaging, and count resources should always tilt toward value.

The solo-clerk rule is written as a hard constraint because it protects the counter first. A solo count has no verifier: right cannot be proven, wrong cannot be ruled out, and once a variance surfaces, the person who counted alone can neither prove the count nor be cleared of it - dual presence gives two people corroboration and leaves both the store and the employee clean. High-value zones therefore get "dual-staffed hours only," with no flexibility, because the loss from relaxing it is irreversible: a variance out of a solo high-value count restarts from zero in any later review. "Log it, do not dig" during solo hours is the same realism - nobody should chase a discrepancy alone at 4 a.m. with no one to check their work.

The carve-outs keep the rolling count's basis clean, and the missing watermark is deliberately missing. Foodservice items zero out daily, and four arithmetic moves - opening, received, sold, written off - produce the expected remainder, so counting them with shelf stock is heavy weapons on a light target; tobacco runs dedicated because its value and its regulatory tracking demand more than a rolling pass. As for the refused "normal variance range": no accepted watermark exists, and whoever claims an industry average owns the burden of proof - an SOP that prints one has fabricated a number that every future variance sheet gets measured against.

Variables