In the shopping sessions section, you can see the ongoing and past sessions in your stores.

Shopping Sessions refer to the entire shopping journey, starting from the moment a shopper scans the first product (a basket is created), and they can have different final states depending on whether the customer paid, scanned a checkout code, or the shopping session expired. By default, shopping sessions expire at midnight if the shopper has not paid for a transaction. If the shopper pays and leaves the store, the shopping session is marked as completed immediately.

It is also important to note that shopping sessions can include multiple payment attempts (transactions). For example, if a payment attempt is canceled and the customer edits the items in the basket and tries to pay again, there will be two transactions within the same shopping session.

The table on this page shows:

• Ongoing (not paid but active) shopping sessions, marked by the Clock icon in the Last Activity column.

• Stale (not paid and inactive for at least 30 minutes) shopping sessions, marked by the Zzz icon in the Last Activity column.

• Started and ended shopping sessions, filtered by time and store.

• The client (app) used to complete the shopping session.

• The quantity of products and value of the basket.

• The store where the session was started.

• The last step that was completed in the shopping session (“Progress”).

You can also download an export with all the shopping session details for the current filters, for further analysis.

Clicking on any shopping session row in the table will lead you to the shopping session detail page.

Shopping session details

The shopping session details page offers all the information about a shopping journey, from the moment the first product was scanned (Basket created) until the shopper paid and left the store (Payment completed / Session completed), or if the session expired due to inactivity (Abandoned). By default, shopping sessions expire after 2 hours of inactivity if the shopper did not pay a transaction. If the shopper pays and leaves the store, the shopping session is marked as completed immediately.

It is also important to mention that shopping sessions can include more than one payment attempt (transaction). For example, if a payment attempt is canceled and the customer edits the items in the basket and tries to pay again, there will be two transactions within the same shopping session.

This detail page includes the following fields:

General information

• Basket: Quantity of products and basket total value

• Session ID: Internal unique identifier of a shopping session

• Start: Local time when the first product was scanned (shopping session started)

• End: Local time when the session was marked as completed or expired.

• Duration: The difference between the end and start time.

• Store: Name and ID of the store where the shopper started the shopping session.

• Customer ID: Unique identifier of a shopper. This ID is generated and sent by the client app.

• Client: Type of app used to start the shopping session. Can be SDK (Android/iOS), Hand scanner, matrix.

• Progress: The last step completed by the shopper in the shopping session.

• Feedback: Rating given at the end of the purchase, if available.

Employee interaction:

• Spot check: Whether a spot check was required during the shopping journey and its outcome by the end of the session.

• Age verification: Whether any age check was required during the shopping journey and its outcome by the end of the session.

• Employee interaction: Duration of the interaction between the employee and the shopper. Since the employee opened the customer’s basket in the Supervisor app, until an outcome was confirmed.

• Total waiting time: Duration of the time since the verification was shown on the shopper’s app until it was acknowledged (started) by the employee in the Supervisor app.

In the example below, we can see that this session had two transactions, while using the matrix SCO. The first one was not completed (canceled) and then the payment was completed in the second transaction. A spot check was required but approved after 24 seconds after starting the payment process. The last progress step, however, is “Payment completed”, which means that the shopper completed the payment and received a receipt, but they did not scan the exit code at the checkout. In that case, the last step would have been “Session completed”.

To learn more about Transactions, check this article about Transaction Detail pages.