Infrastructure diagrams

These diagrams visualize the required (or optional, with dashed lines) connections between components of the shopreme ecosystem and external services. Each service is numbered with the following references:

1. shopreme Middleware: The shopreme backend acts as middleware to handle requests to third-party services, such as payment providers. This means that the shopreme apps do not communicate directly to a payment provider (e.g. Adyen) but to the shopreme backend, which in turn handles the payment logic.

2. 3rd party system: Some retailers may use 3rd party systems to handle the price calculation, add promotions, or issue receipts. These services are grouped into this category.

3. Google Cloud Messaging (Push Service): Google Push notifications are used to notify client apps about events, such as the Supervisor notifications for Spot Check or Age Verifications, or the Unlocking action for hand-held scanners.

4. Mobile Device Management: shopreme currently uses Miradore MDM to remotely manage Android devices, such as the matrix SCO and vector exit. An MDM allows shopreme to push app updates and other over-the-air customizations.

5. Payment service provider: A payment service provider, or PSP, is a third-party company that allows businesses to accept electronic payments, such as credit card and debit card payments. PSPs act as intermediaries between shoppers, who make payments, and retailers, who accept them.

Infrastructure: SDK + Cash desk

Infrastructure: Supervisor app

Infrastructure: matrix SCO + vector exit

Infrastructure: Portable scanners system

Network connections for in-store hardware

Below is the table with all required DNS domains or IP addresses that need to be allowed in a retailer’s network for the matrix SCO, vector, snap cart, and handheld scanners to work as expected.

The number of each item refers to the numbers also used in the diagrams above.

Certificates:

• Let’s Encrypt, auto-renewed every 3 months

Bandwidth usage for matrix SCO

The following values can illustrate the bandwidth usage for matrix SCO devices in stores.

We obtained these results by testing locally at the shopreme office. The data transfer load via Ethernet can vary slightly depending on how much the devices are used throughout the day, as well as whether the product images are big in size.

Usage per SCO

• We assume a day is 12 hours of use.

• General rough averages are only for illustrative purposes. The actual values can vary for each implementation.

Usage per store

• We created 3 categories of stores: each store has 6 matrix SCO with different levels of usage – low, mid and high.