Self‑checkout (SCO) has become a core pillar of modern retail operations, delivering speed, convenience, and labor efficiency. However, as adoption has grown, so have loss vectors linked to unintentional errors and deliberate misuse. One of the most common patterns observed in stores is “Pick in aisle but not scan in SCO”—a scenario where an item is picked from the selling aisle but never registered at the self‑checkout terminal.
The Pick in aisle but not scan in SCO feature of the SAI Group’s Visual AI platform is designed to address this gap by providing retailers with visibility into missed‑scan events across the shopper journey. By correlating in‑aisle product interaction with activity at self‑checkout, the feature helps stores identify when an item leaves the aisle but does not appear in the transaction flow. The goal is not confrontation, but early detection, operational insight, and informed intervention.
This feature supports retailers in reducing shrink, improving SCO integrity, and gaining a clearer understanding of where and why breakdowns occur in the checkout process—while preserving a friction‑light customer experience.
Retail shrink is no longer driven solely by traditional theft. A significant portion arises from process gaps, especially at self‑checkout. The “pick but not scan” scenario sits at the intersection of customer behavior, store layout, and technology limitations.
Key reasons why this scenario matters:
By addressing this scenario specifically, retailers can shift from reactive loss handling to proactive exception awareness.
At a conceptual level, the feature works by connecting two previously disconnected moments in the shopping journey:
In‑Aisle Product Interaction Awareness
Visual AI models observe product movement events in store aisles, such as items being picked from shelves. These observations establish a baseline expectation that the picked item will later appear in the checkout process.
SCO Transaction Observation
At self‑checkout, the system observes the flow of scanned items and transaction completion. This creates a record of what was registered and paid for.
Cross‑Journey Correlation
When an item is seen leaving the aisle, but no corresponding scan event is detected at SCO within a reasonable window, the system flags a potential pick‑but‑not‑scan exception.
Contextual Exception Handling
Rather than treating every exception as wrongdoing, the feature is designed to surface actionable context:
This context allows retailers to decide how best to respond—through associate assistance, process improvement, or layout changes.
Importantly, the feature is intended to support operational decision‑making, not to replace human judgment.
No. The feature is designed to identify exceptions, not intent. It provides context so retailers can choose appropriate, customer‑friendly responses.
Conceptually, the system focuses on patterns and confidence thresholds, not single isolated events, to reduce noise and false positives.
Traditional SCO systems only observe what happens at the checkout. This feature extends visibility upstream into the aisle, closing a major blind spot.
Yes. Many missed scans are accidental. Identifying them allows stores to improve signage, prompts, and associate assistance.
The intent is to keep the experience friction‑light. Any interventions are informed, selective, and aligned with store policies.
While loss reduction is a key outcome, the feature also supports operational optimization, staff efficiency, and better store design decisions.