Retail Network Infrastructure

IoT Gateway
Buying Guide

The critical bridge between your smart retail devices and the cloud.

It connects Electronic Shelf Labels (ESL), environmental sensors, smart cameras, and beacons to your central management platform. Choosing the right gateway determines your network coverage, data latency, and overall system reliability.

1. Wireless Protocol Selection

The wireless protocol determines compatibility with your IoT endpoints. Your gateway's radio frequency (RF) module must match the devices you intend to deploy.

Protocol	Frequency	Indoor Range	Best Use Case
Sub-GHz RF	433/868 MHz	15 - 30m	ESL tags. Superior wall & metal penetration.
BLE (Bluetooth)	2.4 GHz	10 - 15m	Beacons, asset tracking, proximity marketing.
Zigbee	2.4 GHz	10 - 20m	Smart lighting, mesh sensor networks.
Wi-Fi	2.4/5 GHz	20 - 50m	Smart cameras, heavy data signage payloads.

Recommendation: For Electronic Shelf Label (ESL) deployments, Sub-GHz (433/868MHz) is strictly recommended. Lower frequencies bend around metal gondola shelving and penetrate cold-room walls far better than 2.4GHz Wi-Fi or Bluetooth. View Sub-GHz Gateways.

2. Coverage Planning & Site Survey

RF signals are physical waves. Metal shelving, thick concrete walls, and dense liquid merchandise all attenuate (reduce) signal range. Never calculate coverage based purely on square footage.

Open Retail Space

Apparel, Furniture, Electronics

Line-of-sight coverage is excellent. Plan 1 gateway per 400-600 sqm (approx. 20-30m radius).

Dense Shelving

Grocery, Pharmacy, Hardware

Metal gondolas reduce range by 40%. Plan 1 gateway per 200-300 sqm.

Cold Rooms

Walk-in Freezers, Dairy

Insulated metal walls completely block RF. Place a dedicated gateway inside or directly adjacent pointing in.

3. Device Capacity vs. Update Frequency

Each gateway has a maximum bandwidth limit. Crucially, device capacity and update frequency are interdependent.

The Golden Rule

A gateway rated for 5,000 tags updating once daily (e.g., at midnight) may only support 2,000 tags if you utilize hourly "Dynamic Pricing" algorithms.

Tag Volume Freq.

5,000 tags (1x/Day)

3,000 tags (1x/Hour)

1,000 tags (Real-time)

4. Network Backhaul & Redundancy

The gateway connects the IoT network up to your cloud platform via a "backhaul" connection. This link must be ultra-reliable.

LAN

Ethernet (RJ45) - The Standard The most reliable method. Highly recommended for all permanent store installations to avoid Wi-Fi congestion interference.

Mission Critical

4G LTE

Cellular Failover Enterprise gateways include a SIM card slot. If the store's primary broadband goes down, the gateway automatically switches to 4G to ensure price updates and security sensors remain online.

5. Cloud Integration & Management Platform

Hardware is useless without the software layer. Evaluate the cloud management platform for API extensibility and maintenance tools.

MQTT Protocol: Ensure the platform supports MQTT, a lightweight messaging protocol ideal for low-bandwidth IoT, rather than heavy HTTP polling.
REST APIs & Webhooks: Crucial for syncing the ESL cloud with your native ERP (SAP, Oracle) or POS system. Webhooks allow real-time event notification.
Firmware OTA: Over-The-Air updates allow IT teams to patch gateway security vulnerabilities across 500 stores simultaneously from HQ.

POST /api/v2/gateway/sync HTTP/1.1
Host: api.synqnode.iot
Content-Type: application/json

{
  "action": "update_price",
  "gateway_mac": "00:1A:2B:3C:4D:5E",
  "tag_id": "ESL-99824",
  "payload": {
    "price": 14.99,
    "promo": true
  }
}

6. Power over Ethernet (PoE) & Installation

Because gateways are typically mounted on ceilings to maximize RF coverage (radiating downward), providing local AC power is expensive and difficult.

Always Demand PoE Support

Power over Ethernet (802.3af/at) allows a single standard Cat5e/Cat6 network cable to deliver both network data and electrical power to the gateway. This eliminates the need to hire electricians to install ceiling power outlets during store fit-outs.

7. Security & Compliance

IoT devices are notorious network entry points for hackers. Secure your edge infrastructure.

AES-128/256 Encryption Ensure all wireless RF communication between the gateway and the ESL tags is encrypted to prevent packet sniffing.
VLAN Isolation The gateway must support VLAN tagging to isolate IoT traffic onto a separate subnet, keeping it away from secure POS transaction data.
TLS / SSL Certificates The backhaul connection from gateway to the Cloud platform must use TLS 1.2+ to prevent man-in-the-middle attacks.

IoT Gateway Buying Checklist

Validate these requirements before finalizing your network architecture.

Identify exact RF protocol (Sub-GHz vs BLE) required by your endpoint tags.

Conduct a physical site survey to identify metal/cold-room dead zones.

Verify device capacity meets your peak tag count based on update frequency.

Confirm the gateway supports PoE (Power over Ethernet) for ceiling installs.

Assess need for 4G LTE cellular failover for mission-critical store locations.

Evaluate Cloud Platform API documentation for ERP/POS integration.

Plan Your IoT Network Architecture

Tell us your store size, IoT device types, and update frequency requirements. Our network engineers will calculate the exact gateway quantity and topology you need.

Request a Deployment Plan