Skip to main content

Architecture Overview

Platform​

CoolR runs on Azure and processes millions of device events per day. Authorized customer systems can exchange data through APIs and scheduled exports. See Integration Overview for available options.

Infrastructure components​

Architecture Diagram

Edge devices​

Devices such as Tack, Vista, Hub, and VistaZ collect and store data locally. Depending on the model, they capture images, door events, temperature, humidity, or light readings.

Gateways​

Gateways such as the CoolR Global Hub, a phone, or VistaZ retrieve data from edge devices and transmit it to the cloud over Wi-Fi or cellular connections.

CoolR Portal and Playbook​

The platform includes application servers, databases, and blob storage. These components communicate internally, with external access restricted. Gateways send data to the platform over HTTPS.

Users and systems​

User devices and authorized ERP, CRM, and sales-force automation systems communicate with the platform over HTTPS.

Data sources​

Data can come from CoolR hardware, cooler manufacturers, controller vendors, and third-party gateways. Integrations can also receive data from:

  • Cooler manufacturer platforms, such as Minus Forty and True
  • Controller platforms, such as Sollatek and Wellington
  • Customer systems providing master data, sales data, or visit data
  • Distributors and audit companies, such as Acosta

Data destinations​

  • CoolR applications: Mobile apps, web applications, and alerts
  • Customer systems: APIs, SFTP, and notifications
  • Third parties: Data shared with the customer's authorization

For example, CoolR can send low-stock or planogram-compliance information to a service provider. After a store visit, the provider returns confirmation through an API or SFTP, and CoolR verifies the data.