Reconciliation
Inventory & shrinkage detection
Receipts in, sales out, every SKU reconciled.
Operating rules
SKU-level receipt and sales matching
Cycle-count mobile workflow (no all-store Sunday counts)
Slow-mover and dead-stock surfacing
Velocity-based reorder thresholds (configurable)
Inventory ingests SKU-level receipts from scanned invoices, decrements from POS sales, and flags movement deltas that don't reconcile. The slow $30/week tobacco leak gets surfaced in week one instead of compounding into a $1,500 monthly variance. Cycle-counts run on a mobile workflow. No all-store Sunday counts. Velocity-based reorder thresholds keep dead stock out of the system.
Reconciliation
Inventory & shrinkage detection
Receipts in, sales out, every SKU reconciled.
SKU-level receipt and sales matching
Cycle-count mobile workflow (no all-store Sunday counts)
Slow-mover and dead-stock surfacing
Velocity-based reorder thresholds (configurable)
Live review
Morning operating brief
Assistant summary
Inventory ingests SKU-level receipts from scanned invoices, decrements from POS sales, and flags movement deltas that don't reconcile. The slow $30/week tobacco leak gets surfaced in week one instead of compounding into a $1,500 monthly variance. Cycle-counts run on a mobile workflow. No all-store Sunday counts. Velocity-based reorder thresholds keep dead stock out of the system.
Overview
What it does.
SKU-level inventory ingests from invoice scans. Sales decrement from POS feeds where integrated. Movement deltas that don't reconcile are flagged with shift overlay, so the slow $30/week leak shows up before it compounds into a $1,500 month.
- SKU-level receipt and sales matching
- Cycle-count mobile workflow (no all-store Sunday counts)
- Slow-mover and dead-stock surfacing
- Velocity-based reorder thresholds (configurable)
- Anomaly flagging: SKU loses > 2% velocity over 14-day window
Operator fit
Operators who lean on this most.
Inventory & shrinkage detection is part of every StationPro deployment. These operator profiles tend to open it daily.
Questions
FAQs
Where does tobacco shrink usually come from?
Three main patterns: (1) clerks pocketing soft packs without ringing, (2) "buy 2 get 1 free" promos not enforced at the counter, (3) DSD vendors short-shipping cartons. We surface all three: per-clerk void/refund patterns, promo-violation flags, and invoice-vs-receipt mismatches.
How are cycle counts handled?
Counts are mobile and partial. Instead of one Sunday-night full count, the system suggests 30 to 50 SKUs per day across high-velocity categories. A clerk scans the SKU, enters the count, and any variance against expected on-hand flags for review. Most stores complete a full rotation in 30 days without ever doing a "big count" night.
Does this work without POS integration?
Yes, but degraded. Without POS, sales decrement happens at EOD (one bulk update per day) instead of per-transaction. Anomaly detection still works; the time-to-detection just goes from minutes to hours.
Want to try Inventory & shrinkage detection on your data?
A 30-minute demo. We'll set up a tenant with this feature wired to your operational shape and walk it live.