RetailNext operates two separate services: a global service based in the United States (denoted as Global Cloud Service) and a separate service operated entirely within China (denoted as China Cloud Service). This page details the comprehensive network requirements for these services.
For a quick reference guide to the Basic Network Requirements, click here.
Store Network | RetailNext Cloud Service | |
---|---|---|
Admin Access Initial setup (HTTP): TCP 80 → Discovery (mDNS): UDP 5353 → Discovery (UPnP): TCP 1900 → IP Cameras Video (RTP/RTSP): TCP 554 ←, UDP → Video (HTTP): TCP 80 ← | Store Appliance | Cloud Service Management: TCP 8278 → Required Hosts (Global): 104.154.145.235 The addresses in gray must be allowed today but will be phased out in 2021. China: Static IP addresses are not used. Connections will be made to hosts with the retailnextchina.net domain. Note: all devices require access to public DNS (TCP/UDP 53 →) |
Admin Access Initial setup (HTTP): TCP 80 → Discovery (mDNS): UDP 5353 → Discovery (UPnP): TCP 1900 → Power IEEE 802.3af PoE at 15.4W | Aurora | Cloud Service Management: TCP 8278 → Required Hosts (Global): 104.154.145.235 The addresses in gray must be allowed today but will be phased out in 2021. China: Static IP addresses are not used. Connections will be made to hosts with the retailnextchina.net domain. Note: all devices require access to public DNS (TCP/UDP 53 →) |
Admin Access Initial setup (HTTP): TCP 80/443 → | Stereo Sensors | Cloud Service Data delivery (HTTPS): TCP 443 → Required Hosts (Global): 35.244.170.41 (*.camera.ops.retailnext.net) NTP: UDP 123 → The addresses in gray must be allowed today but will be phased out in 2021. China: these devices are not used Note: all devices require access to public DNS (TCP/UDP 53 →) |
Admin Access Initial setup (HTTP): TCP 80/443 → | Open-Mesh Switches | Cloud Service Management: TCP 80/443 → Required Hosts (Global): cloud-switch.cloudtrax.com China: these devices are not used Note: all devices require access to public DNS (TCP/UDP 53 →) |
Aurora & Store Appliances
...
RetailNext also offers the capability of streaming recorded video directly from the store appliance or Aurora over RTMPS on TCP port 9800, which is implemented with WebRTC data channels. This allows users in the store to play back videos over the local network instead of the WAN connection. Use of this port will be phased out by the end of 2020.
As mentioned above, some older IP video devices may also require the store appliance to accept RTP/UDP data on any port.
Aurora & Store Appliance Network Summary
Service | Protocol | Port | Direction | Destination | Notes |
---|---|---|---|---|---|
Sensor control and data delivery | Proprietary | TCP 8278 | Outbound | RetailNext cloud service | Requires public DNS |
Administrative interface | HTTP/HTTPS | TCP 80/443 | Inbound | - | |
Video retrieval over RTSP | RTSP | TCP 554 | Outbound | IP video cameras/encoders | Ports may vary by product |
Video retrieval over HTTP | HTTP | TCP 80 | Outbound | IP video cameras/encoders | Ports may vary by product |
Legacy video retrieval | RTP | UDP high ports | Inbound | - | |
Discovery | UPnP | UDP 1900 | Inbound | - | |
Discovery | mDNS | UDP 5353 | Inbound | - |
User Access & Data Integration
All connections for the China Cloud Service will be made to hosts with the retailnextchina.net domain.
End User Access | Protocol | Port | Direction | Destination (Global) | Notes |
---|---|---|---|---|---|
Browser-based UI | HTTPS | TCP 443 | 👤 → ☁ | *.cloud.retailnext.net | For load balancing, capacity expansion, Customers will need to allow Internet access |
. |
Video playback |
WS |
TCP 443 | 👤 → ☁ |
*.cloud.retailnext.net |
In-store video playback |
WS |
TCP 443
over WebRTC Data Channel | Coming Soon | 👤 → Store network | Store Appliance | Configuration details are coming soon | |
- | ☁ → 👤 | - | Reports, notifications, and user account management Customers will need to allow mail from | ||
Data Integration | Protocol | Port | Direction | Destination | Notes |
---|---|---|---|---|---|
Query API | HTTPS | TCP 443 | → ☁ | *.api.retailnext.net | For load balancing, capacity expansion, |
POS, staffing, store hours, and other file uploads | HTTPS | TCP 443 |
→ ☁ | *.upload.ops.retailnext.net |
*.pos.retailops.io
*.staff.retailops.io
HTTPS uploads are preferred over SFTP HTTPS: 35.244.192.136, 35.244.228.205 |
52.41.71.27
52.23.88.204
52.87.95.219
52.43.11.78
52.207.54.215
Security events | TCP 443 | → ☁ | *.security-events.ops.retailnext.net |
*.security.retailops.io
35.244.170.41 | |||||
Health monitoring alerts | - | ☁ → | - | Customers will need to allow mail from | |
POS Integration | Protocol | Port | Direction | Destination | Notes |
---|---|---|---|---|---|
Lightspeed, Vend, Shopify, Square | API | - | ☁ → ☁ | - | Requires OAuth setup |