Loss Prevention · All retail
Shrink Investigation
Shrink above baseline. Attributes dock, floor, or admin and opens the case.
Trigger condition
Store shrink exceeds estate baseline by 1.5×, or a single cause crosses threshold. Dock-receipt mismatches above 3 a week, for example.
Write-back
LP case created with evidence chain attached; corrective-action task assigned.
Every write is gated on an approver role you name. Nothing runs unattended.
Procedure
- Decompose shrink into theft, damage, spoilage, dock-receipt mismatch, and admin error.
- Isolate the dominant cause and its interval: day, daypart, dock or floor.
- Pull the matching transactions, GRN events, POS exceptions, and camera windows.
- Open an LP case with the evidence chain pre-filled and the next step named.
- Close when corrective action is logged and shrink trends to baseline for 14 days.
Outcome metric
Shrink over 30 days post-action vs. the pre-action baseline. Positive if half the gap to estate baseline closes.
The case closes on this number, not on the action being taken. A playbook without a close condition is a dashboard.
The rest of Loss Prevention
Receiving Dock Audit
Dock-receipt mismatches recurring. Flags the vendor and deliveries to audit.
Shrink
POS Exception Sweep
Voids and refunds clustering on a register or operator.
Shrink
Refund-Fraud Pattern
Refund behavior outside the norm. Builds the case with the timing.
Shrink
Sweethearting Detection
Discount and void patterns suggest sweethearting. Correlates operator and lane.
Shrink
Run Shrink Investigation on your data.
Pick three playbooks from the catalog. We wire them against your system of record for the pilot.
御社のデータに何が隠れているか、確認する。
お客様のオペレーションについてお聞かせください。デモまたはPoCをご提案します。