Page History

The Sweethearting  detailed report enables real-time monitoring of goods scanning events by cashiers in order to prevent intentional theft by carrying goods past the barcode scanner (so-called sweethearting).

Unlike other detailed reports, going to which is performed from the corresponding general reports, the Sweethearting report is available as an individual menu item at POS reports > Sweethearting.

Image RemovedImage Added

The interface of the Sweethearting monitor is shown in the picture below. 

Image RemovedImage Added

The Sweethearting report is generated automatically based on the data from the Sweetherting detection module, which is part of the Intellect Detector Pack. For more information on the detector, see Detector Pack. User Guide.

The goods scanning events are loaded into the table (1), ranging from the newest to the oldest. Each of the events is provided with the following summary information:

• Date - − the date and time at which the goods were recognized and identified at the cash register;

• POS terminal - − the POS-terminal on which the goods were recognized;

• Cashier - − the full name of the cashier, who was supposed to make a scan;

• Status - − the status of the event, which is determined by the operator of the Web Report System, working with the Sweethearting monitor.

...

1. The video of the event with the indication of the time when the event was recorded and the possibility of viewing in the archive mode (4).

   Info
   title Note
   Working with video surveillance window in the archive mode is given in details in Intellect software package. Operator's guideGuide.

   
   

2. The dropdown list for selecting the status of the event (5). By default, all events have the Event not processed (by default) status. Having examined the video, the operator of the Web Report System, working with the Sweethearting monitor, can manually assign the event one of the following statuses:
   1. Non-violation
   2. Possibly violation
   3. Minor violation detected
   4. Moderate violation detected
   5. Serious violation detected
3. The text field for operator comment (6). If necessary, the operator can leave his comment to the event (no more than five lines).
4. The field for program log output, unavailable for editing (7).
5. The Save button to save the event changes (new status and comment) (8).

...