Short answer
Publication date: September 24, 2024
For retail chains, supermarkets, restaurants, pharmacies, and cold-chain operators, one small technical failure may create several costs. A cooler alarm detected late can lead to inventory loss. A failed modem may interrupt payment and camera systems. A storage door left open can increase energy consumption. In many cases, the main problem is not the failure itself but the lack of timely visibility at headquarters.
NetRelay can create a local IoT automation layer that connects branch dry contacts, external sensors, and network devices with central software. Four digital inputs can receive cooler alarm contacts, door sensors, power status, or UPS alarms. Supported external analog modules can monitor temperature and other environmental values. Four relay outputs can operate an alarm, fan, auxiliary lighting, or an authorized control circuit through suitable electrical components.
The challenge of distributed branches
Keeping technical personnel at every branch is not economical, and store employees cannot always be expected to interpret technical alarms. The system must show which branch and equipment has a problem, when the condition started, and how long it has continued.
NetRelay devices can establish outbound MQTT connections to a central broker. This transfers status data without opening an inbound port on every branch router. Standard device identities, branch names, and input labels turn technical messages into operational events such as “Çorlu branch freezer alarm,” “Ankara storage door open for 10 minutes,” or “İzmir branch NVR unavailable.”
Cooler and freezer monitoring
Many commercial refrigeration controllers provide a dry-contact output for temperature limits or general faults. NetRelay can read this output through a digital input. When more detailed measurement is required, a suitable external temperature sensor and analog module can be evaluated. A threshold event can send MQTT data to central software, start an email workflow, or trigger a local alarm relay.
A single temporary temperature increase should not automatically create a critical alarm. Door opening and product loading can cause normal fluctuations. Reliable logic should include a delay, repeated validation, and a recovery event. This reduces false alarms and helps staff trust the system.
Door, power, and network continuity
A magnetic contact can detect a storage or cold-room door that remains open beyond a set duration. Power presence can be monitored through a suitable isolated detection circuit or auxiliary contact. UPS battery, bypass, and general alarm contacts may also be connected.
NetRelay's Ping Watchdog can monitor up to four IP addresses, including a modem, router, NVR, or local server. Consecutive failures, waiting periods, and controlled restart rules should be configured. Equipment should not be power-cycled after one failed ping. The connection must be verified, retries performed, and recovery checked after intervention.
Which actions can headquarters perform?
Authorized operators may control permitted relays through HTTP API, MQTT, or WebSocket. Electrical and operational safety must be assessed before any remote action. Compressors and similar equipment should not be switched directly; manufacturer controls and suitable contactors must be respected. In some cases, the safest action is to generate an alarm and dispatch qualified service personnel.
Local operation helps branch alarm or ventilation scenarios continue during an internet outage. If local history is required, an optional MicroSD module can be considered alongside central telemetry.
How should ROI be measured?
A credible sales proposal should use customer data instead of generic savings claims. Calculate:
- Average inventory loss caused by late cooler-fault detection,
- Monthly technical service and diagnostic visits,
- Travel, labor, and time cost per branch visit,
- Effect of network outages on payments, cameras, or ordering,
- Energy cost of open doors and unnecessary equipment operation,
- Number of incidents that can be resolved centrally.
A 30–60 day pilot in one or two branches can measure alarm accuracy, response time, and avoided visits. Once value is verified, standard panel, wiring, and software profiles can support a controlled multi-site rollout.
Which businesses are suitable?
NetRelay is suitable when a branch needs to monitor several critical dry contacts, environmental sensors, or network devices. Projects requiring many calibrated temperature points and regulated cold-chain records should use certified data loggers as the primary system. NetRelay can integrate their alarm contacts into central automation or provide auxiliary actions.
Before purchase, define the I/O list, sensor type, internet design, power supply, notification method, and central software. Ethernet and PoE may simplify installation, while Wi-Fi Client mode can be an alternative at suitable locations where cabling is difficult.
The real value is not switching a relay remotely. It is turning small technical signals across many branches into manageable operational information. Share the number of locations, equipment list, and network structure with the NetRelay team to define a scalable pilot.
Why is a standard branch installation necessary?
Different wiring and naming at each location make central operations difficult. A standard panel, device identity, input map, MQTT topic structure, and alarm delay should be prepared. Commissioning records should include router details, NetRelay IP and ID, connected equipment, sensor serial numbers, alarm-test results, and responsible personnel.
A repeatable profile reduces opening time for new branches and gives support teams a predictable architecture.
Who receives each alarm?
A cold-chain alert has different meaning for store staff, service providers, and regional management. The first warning may ask the branch to check the door. Continued temperature deviation can escalate to service, and a critical duration can notify operations management.
Messages should include branch, cabinet, value, threshold, duration, and last connection time. Recovery must also be reported. Repeated messages can be summarized, and after-hours contact lists may differ.
Sensor selection and calibration
Measurement range, accuracy, cable length, and placement matter. A sensor near an evaporator or directly opposite a door may show fluctuations that do not represent product temperature. Placement should follow product and regulatory requirements.
Where certified calibration and traceable records are mandatory, use an appropriate certified data logger. NetRelay can read its alarm contact, add it to central workflows, and create auxiliary relay actions. It should not replace regulated measurement equipment.
Business continuity and local logic
Branch protection must continue when central connectivity is unavailable. Local alarm relays, fans, or indicators can operate through NetRelay rules, while the communication loss itself should be reported through the available architecture.
When PoE is used, switch and UPS design must be reviewed. Runtime calculations should include NetRelay, router, switch, and critical sensors. UPS alarm contacts can report battery or bypass status.
Cybersecurity and privacy
Branch web interfaces should not be exposed directly to the internet. Use an IoT VLAN, VPN, secure MQTT, device-specific users, and access control. Remove access when staff change and log relay commands with user and time.
Door and employee-activity data may create privacy considerations. Collect only operationally necessary data and limit retention and access according to applicable rules.
Building a commercial package
A complete offer can include discovery, standard panel, NetRelay, sensors, installation, MQTT service, central dashboard, alarm rules, training, and maintenance. Hardware investment and ongoing central services can be presented separately.
Three levels may be useful: basic dry-contact alarms, standard temperature and network monitoring, and multi-branch reporting with software integration. Each level should explain the risk it reduces.
Pilot success criteria
Baseline incident and response data is needed before the pilot. Track true alarms, false alarms, communication losses, remote resolutions, service visits, and inventory loss.
The goal is not zero alarms but early and accurate alarms. Sensor failure and communication loss must also be visible. Successful profiles can become part of the standard new-branch checklist.
Frequently asked questions
Does every branch need a static IP?
Outbound MQTT can reduce the need for inbound static IP and port forwarding. Central security and broker design still require engineering.
How many coolers can one device monitor?
It depends on signals per cooler. NetRelay provides four digital inputs. Additional points require more devices or another expansion architecture.
What happens during an internet outage?
Central notifications may be delayed, while local scenarios can continue. Local recording and alternative communications depend on the risk assessment.
Where should the project begin?
Choose two branches with the highest inventory loss or service cost, map contacts, sensors, and network devices, and measure pilot results in time and money.
Which reports should the operations dashboard include?
A central panel needs more than red and green indicators. Report alarm duration, repeat count, connectivity, threshold violations, and response time by branch. Regional managers should see their locations, while service teams see assigned equipment.
Monthly reports can rank branches by alarms, longest interruptions, and remote resolutions. Maintenance budgets can then follow evidence. Repeated alarms from one cabinet should trigger equipment investigation rather than endless threshold changes.
A 45-day rollout plan
Use the first 10 days for contact and network discovery at two pilot branches. During the next 10 days, create standard wiring and a central screen. Validate alarm rules in observation mode, then use the final 15 days to refine thresholds with store and service feedback.
Deliver device inventory, branch diagrams, user permissions, alarm responsibility, and manual-failure procedures. Without documentation, a growing project becomes a collection of inconsistent installations.
One prevented high-value inventory loss or fewer recurring visits may justify investment, but pilot data should prove the result.
Final decision
As branch count grows, the total cost of small technical incidents increases. NetRelay enables gradual investment by making existing alarm contacts and network status visible instead of replacing every asset. Begin with one measurable branch loss, validate the alarm profile, and replicate only after evidence is available.