Purpose

This article contains the most frequently asked questions and their respective answers regarding MarketSight.

Process

Configuration and Settings

1. What 365 products are supported by MarketSight?
   Currently, MarketSight is available for MM6Mini only.
   
   
2. Can my existing fleet of MM6Mini kiosks be retrofitted with MarketSight?
   Yes. There will be a separate part number to order the MarketSight as a retrofit kit.
   
   
3. Do I lose any existing functionality by adding MarketSight?
   Yes. QuickPay is currently not compatible with MarketSight.
   
   
4. Do settings need to be enabled in ADM for MarketSight to function?
   Yes. As part of the ordering process, 365 will configure the appropriate ADM settings.
   
   
5. Can the MarketSight devices be moved from one kiosk to another without the assistance of 365?
   No, the MarketSight kit is tied to a specific device upon setup and swapping it into another device requires backend changes. Please contact 365 Support.
   
   
6. Do MarketSight devices have a serial number?
   No, they do not.
   
   
7. Is there a recurring fee associated with using MarketSight?
   Yes. There is a fixed monthly fee of $20 a month to utilize MarketSight that will be billed per device with a MarketSight kit connected.
   
   
8. Does MarketSight work with QuickPay?
   No. QuickPay is currently not compatible with MarketSight configuration.
   
   
9. Will MarketSight greatly increase my data bandwidth usage?
   No. Increased data usage will be negligible.
   
   
10. Will MarketSight increase power consumption and temperature?
    No. Increased power consumption and operating temperature is negligible.
    
    
11. Can I simply disconnect the kit to disable MarketSight on my kiosk?
    No. You must inform the Sales team for billing and the 365 Support team so they can disable MarketSight from the backend. Without these actions you may continue to get billed and the kiosk's performance may be negatively impacted.

Consumer Journey

1. How does MarketSight assist in identifying un-scanned items? MarketSight utilizes an advanced AI model with a proprietary camera, that tracks scanning activities from consumers in real time. As consumers scan, the AI model will compare the product against the item cart and flag any products that were missed.
   
   
2. How is the consumer notified that MarketSight has detected an un-scanned item?
   When MarketSight identifies an item that was not scanned, a UI modal pop-up will appear on the kiosk, displaying images of the items that were not scanned.
   
   
3. How does the consumer know how many items to scan that were missed?
   The UI modal pop-up will notify consumers of the specific number of items to scan.
   
   
4. What actions can the consumer take once the UI modal displays? The consumer is prompted with two choices:
   1. Scan items that MarketSight detected, adding items to cart before proceeding with transaction.
      
      
   2. Confirm that all items were indeed scanned, requiring no further action.
      
      
5. What happens if multiple items are identified by MarketSight and the consumer doesn’t scan all of them? If a consumer does not scan all items identified, the UI modal pop-up will re-appear prompting the user to scan the remaining items they missed. If the consumer then confirms no further items need to be scanned, an UnderRinging record will be made.
   
   

Reporting and Privacy

1. What happens when a consumer does not scan missing products?
   If a consumer chooses not to scan missing items, an UnderRinging record will be made that captures the transaction information and images of the products not scanned.
   
   
2. Where can this report be accessed?
   UnderRinging records are available alongside the cancelled and returned-item records in the Loss Prevention report in ADM.
   
   
3. Does the MarketSight camera capture more than just products? The camera used to capture MarketSight under ringing transactions, has a top down view and is focused on the products being scanned. No identifiable personal attributes should be captured during the image capture.