Loss Prevention · All retail

POS Exception Sweep

Voids and refunds clustering on a register or operator.

Target KPI Shrink
Executes in ≤ 24 hours
System of record POS · LP analytics
Trigger condition

Void, no-sale or manual price-override rate for an operator or lane exceeds the peer-group distribution by more than 3 standard deviations over a two-week window.

Write-back

Exception review case opened in LP analytics with the transaction set attached; lane or operator flagged for observation.

Every write is gated on an approver role you name. Nothing runs unattended.

Procedure
  1. Build the peer distribution from operators on comparable lanes, shifts and volumes, not the store average.
  2. Rule out the innocent explanations first: a training lane, a broken scanner, a mispriced promotion.
  3. Where the pattern survives, assemble the transaction set with timestamps and basket context.
  4. Route to the LP manager as a review, explicitly not an accusation, because the false-positive cost here is a person.
  5. Close when the pattern normalises after coaching, a fix, or a substantiated case.
Outcome metric

Exception rate against the peer distribution over 30 days, and the recovered value where a cause was substantiated.

The case closes on this number, not on the action being taken. A playbook without a close condition is a dashboard.

Run POS Exception Sweep on your data.

Pick three playbooks from the catalog. We wire them against your system of record for the pilot.

Read-only to start · your LLM keys · SOC 2 Type II underway · or book a call directly

Find out what your data has been hiding.

Tell us about your operation. We’ll show you the problems Ward catches, and the ones your current tools miss.

Step 1 of 3
What are your goals?
Step 2 of 3
About your operation
Step 3 of 3
Your contact info