The shopreme Management Console is the middleware between the retailers’ data and the shopreme DataHub. It allows users to view analytics, transaction information, and imported data about stores, products, and pricing.

The sections below will introduce each functionality and piece of information available on the shopreme Management Console, and the detail pages on the left side will provide more insights to help you understand how to make the best use of the tools offered by shopreme.

ℹ️ The information in this guide may vary based on your custom implementation or the version of your backend.

✨ You can always verify the version of your backend by clicking on “Version” in the bottom right corner of your Management Console view. The version includes the build date and the supported API levels for Mobile SDK, Supervisor, and matrix/vector.

Health dashboard

The Health Dashboard is part of the admin user experience to have a quick overview of the state of the servers, in-store activity, import jobs, and hardware – in one place. This section is in active development and improvement, so the view and features can vary depending on the version of your shopreme backend.

The widgets included in this overview are the following

• Failed conversions: From the last hour to the current moment, what percentage of shopping sessions did not finish in a payment completed or session completed state. A high percentage can indicate technical difficulties in payment processing, product scanning, or any other puzzle piece needed for a successful checkout. A set minimum of simultaneous sessions is required to show a percentage.

• Failed evaluations: During the last hour, what percentage of basket evaluation calls (API requests) gave an error response. This could signal an issue with a third-party engine or a product import, for example, if products cannot be recognized in the Scan & Go basket.

• Failed clearing calls: Percentage of failed clearing calls in relation to the total number of clearing calls. This only works if you enable Live Clearing in your shopreme backend. For more information about this feature, please contact your shopreme Integration Consultant.

• Hardware status: Total count of hardware units, either shopreme matrix SCO, vector exit, or portable scanners. If any hardware unit is not operational (either due to maintenance or a technical issue), this will be visible here. Clicking on the widget will lead to the filtered view of devices for some quick analysis.

• Job status: This widget can be configured to show specific jobs that are important to monitor and ensure that the last run was successful. If any of those “watched” jobs fails during its last run, it will be highlighted in this section.

Analytics section

Revenue analysis

The revenue analytics are based on revenue and transaction counts, which show the overall performance of the shopreme systems (Scan & Go and/or shopreme POS hardware). This data can be filtered per store and per device type.

More details can be found here.

In-store analysis

The in-store analytics are focused on the shopper activity within the stores. This relates to the client app they use, the payment process, the conversion rate, and the products they scan.

We show more examples and descriptions in our article here.

Supervisor analysis

The Supervisor Analysis section includes insights and KPIs related to shopper-employee interactions: waiting times and details about spot checks and age verifications.

Take a look at the detailed page about the Supervisor analysis and KPIs to see all the information.

User feedback

You can keep track of the user feedback from end customers using Scan & Go and other shopreme clients. Learn more about that in this article.

Payment section

Shopping sessions

In the shopping sessions section, you can see the ongoing and past sessions in your stores. Shopping Sessions start from the moment a shopper starts the first product (a basket is created) and 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 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.

The table on this page shows:

• Ongoing (not paid or not yet expired) shopping sessions, marked by the Clock 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. Learn more about the shopping sessions and the details they include in the Shopping Session Details page article.

Transactions

The transactions section lists all payment activity in your shopreme server. A transaction is created when a shopper taps on “Pay” to either choose a payment method or pay immediately with a preselected one. This also means that more than one transaction can belong to the same shopping session. Review the previous section about Shopping Sessions for more information.

On this page, you can:

• See transactions per day

• Search by transaction ID or customer ID and see the status

• Filter transactions per store

• Filter transactions by status

• See the overview for each transaction: date, ID, amount paid, payment method, status, and store.

In the following example, you can see what the transaction overview may look like. Each table row is a transaction. If the payment in a transaction fails for any reason, it will be highlighted in red. Clicking on the row will take you to the transaction details page.

Check the full article here to learn all the details of what can be seen in each transaction details entry.

Hardware section

shopreme currently offers two specialized retail hardware devices that can streamline the Scan & Go journey.

Read more about shopreme vector here, and find out what is new with the shopreme matrix here.

shopreme vector management

On the vector management page, you can see a list of all registered devices for your server. The list also shows the vector ID, whether there are add-ons such as an exit gate or a payment terminal, and the last-reported state (heartbeat sent by the vector to the shopreme backend).

At the top of the page, there is a “Status report” widget, which offers a summary of all devices’ states. It will be green if all devices are operational and working. If other statuses are available, they will be shown here. Clicking on the status will filter for all devices with that status.

Online devices:

Offline devices:

The common states here are:

• Operational: Devices are stable, connected and working.

• Offline: The last two heartbeats from a device were not received, so shopreme assumes the device is offline (either off or disconnected from the network).

• Needs employee interaction: The device settings screen is open, or the employee is configuring the device.

• Critical issue: A critical hardware component is not working or is not connected. Critical components are Scanner, nexus board, Payment Terminal (if it is a vector with payment) and the Ethernet connection.

Clicking on a device will open the vector detail page. You can learn more about the detail page here.

shopreme matrix management

On the matrix management page, you can view all the matrix devices that are registered to your server. The list includes the device name, which is displayed on the Supervisor app, and also the Store name where it is located, the matrix ID (device serial number), the status of all critical components, and the last reported state of the device.

If a device requires attention (e.g., the printer is out of paper or the settings screen is open), it will be highlighted on the top widget with a different status.

The available statuses are:

• Operational: All critical components are working, and the SCO is connected and ready to use.

• Offline: The last two heartbeats from a device were not received, so shopreme assumes the device is offline (either off or disconnected from the network).

• Needs employee interaction: The devices settings screen is open, or the employee needs to take action, .e.g., refill paper in the printer or set up the EFT (payment terminal) in a newly-configured matrix.

• Maintenance mode: An employee enabled Out-of-Order manually on the device. Self-checkout is temporarily unavailable on the device, but otherwise the device is operational.

• Critical issue: A critical hardware component is not working or is not connected. Critical components are Printer, Scanner, Payment Terminal, nexus board, and the Ethernet connection.

More details about the device can be seen by clicking on the entry to see the matrix details page.

Different device states:

You can learn more about the information on the matrix detail page here.

Portable scanners

The Portable Scanners section includes all shopreme-managed devices that can be set up in stores for customers to shop with using Scan & Go. These devices can be handheld scanners, such as the Zebra PS20 or PS30 devices, or the shopreme snap cart. The Unlocking Station is also included as part of the portable scanners system.

To see more details about the Portable Scanners management, read the “Portable scanner management” article. You can also see learn about the mobile apps for these portable scanners and their features, in the main “shopreme Portable Scanners” articles.

Beacons

The shopreme store detection on the SDK is powered by BLE (Bluetooth Low Energy) beacons located in the stores. Whether you have individual beacons in the store location or beacons inside the vector or matrix devices, they will appear in this list.

Please note that only the individual beacons can be reassigned to a different store. The beacons that belong to a hardware device are bound to the location where the device is.

Stores

The Stores section lists all imported or manually-created stores in your server. Usually, stores are within the same country for tax and management reasons.

To create a store manually, click ” New store ” in the Stores view and fill in the details. There are some required fields:

• The “name” is the display name shown in transactions and other parts of the Management Console.

• The “External ID” is linked to product and price imports and can also be used for basket evaluation and external payment processing. It should be a unique ID that identifies the specific store.

• The “Address” is used to display the store in the map on the Dashboard section.

In addition, the Store entry shows the available Features:

Features to select in a new store

• Enable shopreme checkout: Checking this box allows shoppers to detect the store via Bluetooth in the Scan & Go app or use the matrix SCO if available, scan products, pay for them, and leave the store. Disallowing this option will tell shoppers that Scan & Go is unavailable in the store when they open the app.

• Enable checkout at the exit terminal: This option enforces that a QR code be displayed on the shopper Scan & Go app to be scanned at the vector to be able to leave the store. The QR code can be used to open the gate at the vector, if available.

• Activate basket quantity limit: This option sets the maximum allowed number of items to be purchased per transaction.

• Enable automated spot checks: This option enables the spot check algorithm to select shoppers randomly for basket verification. A store risk level should be selected, which sets a pre-defined probability (default: low = 5%, medium = 10%, high = 15%).

Please note that the store information can also be imported via the store import job. See the DataHub > Jobs section for more details.

Products

When clicking on the Products menu button, you will see the Product data list, with all imported or manually-created products in the database for this server. The products table shows the name and product number, and also allows you to select products and delete them, or manually create a product by clicking the option on the purple bar.

To see what products are available for scanning in a specific store, you can use the “Available in” dropdown search.

Clicking on a specific product entry will take you to the Product Detail page. You can learn more about the Details page here.

Product catalogue

The Product Catalogue helps retailers organize products into categories to make shoppers’ experience to find products much easier. These categories are used for the matrix category browsing and the “no-barcode search” in the SDK (if enabled).

You can read more details about this feature and how use it in this article.

Users section

There are currently three types of “Users” in the Management Console:

• Management Console users: Usernames allowed to access the Management Console and different pieces of information in there.

• Supervisor App users: Usernames allowed to sign in to the Supervisor app for all stores or specific ones.

• API Tokens: Tokens used for authentication when using the shopreme API described in the DataHub.

Please check this article to learn more details about each type of user and their roles and permissions.

DataHub section

Jobs

The shopreme DataHub jobs are a key component for a smooth integration for Scan & Go. The DataHub jobs work out of the box and allow retailers to import the following data:

• Product import: Data about products, their characteristics, requirements, and details such as age restriction, theft protection, etc.

• Price import: Data about each product’s prices for each store.

• Store import: Data about each store and their location, external ID, etc.

• Categories import: Data about categories, images representing them, and child categories.

Visit the following article for more details and insights on the shopreme jobs and how to use them best: shopreme Import Jobs.

API connector

In the API connector section, you can find the documentation for the shopreme APIs, specifically for your server. Please visit the DataHub documentation for more information, data flows, diagrams, and details.

In the Settings tab, you can set a username and password for the HTTP basic authentication and enable other services, such as an external basket evaluation service (under “Basket and pricing”).

You can see more in the Outbound API and Inbound API tabs.

⚠️ Please note that enabling or disabling options on the Settings screen can break behaviors. We recommend only changing this in test environments (“Stage” server, for example) and never in Production unless you are sure about the changes.

Server settings section

Configuration parameters

As shopreme can be customized depending on each retailer’s needs, some of these changes are set up as parameters in the server.

These flags can vary depending on the features available on your server, but some examples are the following:

ℹ️ Some example parameters that can be customized

ℹ️ Remember that the parameters and their values depend on your custom implementation and other customizations. The values above are only an example.

If you have specific questions about the parameters in your server, don’t hesitate to contact your shopreme Integration Consultant.