Skip to main content

Overview

Platform​

Coolr Group's backend is based on a few key principles:

  1. Hosted in Azure for Scalability, Redundancy and reliability​
  2. Tested with millions of events per day​
  3. Flexible​
  4. Extensible​
  5. Multiple API endpoints with REST/ HTTPS interface​

Entire Coolr ecosystem is exposed as API with both inbound/ outbound data points. Everything available on Coolr platform is accessible by 3rd party systems authorized by the client​.

Infra Components​

Architecture Diagram

Edge Devices​​

These are devices such as Tack, Vista, Hub or VistaZ that collect the data at the endpoint. For example, Vista may collect door open/ close, temperature, humidity and light etc. periodically. This data is stored locally in the device.​

Gateways​​

These are the devices such as Coolr Global Hub or a phone or VistaZ that pulls the data from the edge devices and using their own connectivity such as WiFi or Cellular, transmit it over to the Coolr Cloud portal.​

Coolr Portal and Playbook​​

Coolr Portal is composed of various components such as App Server, database system, blob storage etc. All these components talk to each other internally and the access is restricted from outside. ​

The gateway devices communicate to Coolr Cloud Portal over HTTPS protocol to ensure that the data is encrypted during transmission.​

Users and Systems​​

These are end user devices or 3rd party sub systems such as an ERP, CRM or SFA system that interacts with Coolr Portal over HTTPS protocol.

Data sources​​

Sensors/ camera​​

Edge devices – Coolr hardware, Cooler OEM systems, Cooler controller companies​

Gateways​​

Data from Coolr devices or 3rd party devices can be transmitted either via Coolr hardware or 3rd party gateways such as Sollatek, AT&T etc.​

APIs​​

Coolr also works from data that may be directly collected in other platform. This includes:​

  • Cooler OEM platforms – such as Minus Forty, True etc.​
  • Cooler controller company platforms – such as Sollatek, Wellington etc.​
  • Customer platforms – such as master data, sales data, visit data etc.​
  • Other 3rd parties – Product distributors, audit companies (such as Acosta) and so on

Data Targets​

  1. Coolr Platform: Mobile applications, Web Platform, Alerts etc.​
  2. Customer endpoints: Pull/ Push via APIs, SFTP, Notifications​
  3. 3rd party: Data sharing as approved by our clients​

Example​ integration:

  1. Coolr pushes data for Low stock/ planogram compliance issues to 3rd parties such as Acosta​
  2. They visit and confirm via pushing data back through APIs/ SFTP​
  3. Coolr verifies data