Skip to content
+90 850 885 27 43 info@argeict.com

Warehouse management (WMS)

Server and cloud infrastructure for Logo Edge WMS

According to Logo, Edge WMS does not work offline: devices in the warehouse connect to the server for every transaction. When the server is outside the warehouse building, the link between the two carries every scan. In warehouses with an automated storage and retrieval system (AS/RS), a stopped server also means stopped robots, and we plan the setup around that dependency.

Product architecture

Logo Edge WMS architecture on ARGE Cloud

In the diagram, Logo Edge WMS and the Logo ERP server run in the same VPC, and master data and transaction sync stays inside it. iOS, Android, and Windows devices in the warehouse connect to the server from the warehouse firewall over an encrypted link.

ARGE ICT infrastructure diagram (Logo Edge WMS). Head office and branches connect from their own firewall to the Istanbul data center over an IPsec tunnel or MPLS/SD-WAN; remote staff use SSL VPN, ZTNA, or ARGE ZTNA. Traffic passes from the data center router through the ARGE ICT Backbone HA Cluster to an HA firewall. Inside the dedicated VPC it passes the VPC firewall and the WAF and is spread across the application servers by a load balancer; the application server (Logo Edge WMS), the database, and the terminal server run in this VPC; application and database tiers can be built as HA clusters on request. A service zone beside the VPC runs monitoring, SIEM and SOAR, antivirus/XDR/EDR, and DLP. It runs on Dell and Supermicro servers with Xeon Platinum and enterprise NVMe, hosts linked by a 25–200G NVIDIA Mellanox network. Backups are kept in an isolated backup zone and can optionally be replicated to a second data center (DR site). Handheld terminals in the warehouse connect over Wi-Fi to the warehouse firewall and from there over an encrypted link to the data center. Logo ERP runs in the same VPC; master data and transactions sync both ways.ARCHITECTURE · LOGO EDGE WMSLogo Edge WMS architecture on ARGE CloudMPLS · SD-WANInternetCustomer: head office and branchesyour own firewallData center · Istanbuldata stays in TürkiyeARGE physical environmentARGE ICT network and racksYour dedicated VPCfirewall · WAF · serversVPC monitoring and security serviceMonitoring · SIEM and SOAR · AV/XDR/EDR · DLPBackup infrastructureisolated backup zoneDR site · second data centeridentical to the primary environmentWarehouse (on site)terminals, Wi-Fi, printersHead officeBranchesCustomer firewallIPsec tunnel endpointCustomer firewallyour company's gatewayIPsec tunnelfrom head office and branches, encryptedIPsec tunnelencrypted private linkRemote staffSSL VPN · ZTNA · ARGE ZTNARemote staffsecure access from home or fieldDC routersdata center network · HA pairDC routersterminates external linksARGE ICT Backbone HA ClusterHA link from DC network to ARGE networkARGE ICT Backbone HA Clusterredundant core backboneFirewall (HA)ARGE perimeter · HA pairFirewall (HA)only allowed traffic passesVPC firewallrules for you onlyVPC firewallentry to the VPCWAFweb application firewallWAFinspects web requestsTerminal serverRDS · desktop clientsTerminal serverremote access to the programApplication serverLogo Edge WMS · Windows ServerHA cluster: optionalApplication serverLogo Edge WMSredundant cluster on requestDatabase serverMicrosoft SQL Server · version to be confirmedDatabase HA cluster: optionalDatabase serveryour data lives hereredundant cluster on requestInfrastructure monitoringserver, disk, network, backupInfrastructure monitoringon one dashboardSIEM and SOARlog collection and correlationSIEM and SOARalerts handled in defined stepsAntivirus · XDR · EDRendpoint protection on serversAntivirus · XDR · EDRmalware and suspicious behavior stoppedDLPdata loss preventionDLPdata egress monitoredVirtualization hostsDell and Supermicro serversXeon Platinum · enterprise NVMeVirtualization hostsenterprise-class serversfast processors and storage25G / 50G / 100G / 200G host networkNVIDIA Mellanox Ethernet cards25G / 50G / 100G / 200G host network25–200G links between serversBackup copiesseparate logical zoneseparate from productionBackup copiesyour copies are kept hereDR firewallsame rulesDR application serveractive · serving usersDR application serverstandby · takes over in a disasterDR databasesynchronized both waysDR databaseup-to-date copy, read-onlyGlobal Load Balancerhealth-checked routingGlobal Load Balancersends users to the site that is upHandheld terminalsiOS, Android, Windows devicesHandheld terminalsscan on the floor, see it in the systemWarehouse firewallIPsec · second link advisedWarehouse firewallwarehouse on the same encrypted linkLogo ERP server (same VPC)next to the WMSLogo ERP server (same VPC)accounting and stock in the same VPCSSL VPN · ZTNAARGE ZTNAlogs and metricsBackup lineAlso to DR (active-active)traffic shared across both sitesFailover pathused only in a disasterTwo-way replicationContinuous replicationone way, primary to DRTwo-way integrationmaster data and transaction sync123456IPsec tunnelMPLS / SD-WANSSL VPN · ZTNAInternet to WAFDC and ARGE networkHA pairingApplication ↔ data25–200G host networkLogs and metricsBackup lineGlobal Load BalancerFailover pathDR replication1Step (below the diagram)Application integrationIllustrative · HA and DR are added with the buttons on the page
IPsec tunnelMPLS / SD-WANSSL VPN · ZTNAInternet to WAFDC and ARGE networkHA pairingApplication ↔ data25–200G host networkLogs and metricsBackup lineGlobal Load BalancerFailover pathDR replicationApplication integrationIllustrative · HA and DR are added with the buttons on the page
Hover over or tap a component to see its name and role; choose “Show all” to see every label at once. Zoom with Ctrl/⌘ + scroll, a two-finger pinch or a double click. Use the buttons above to add HA and DR options; click a step to bring its layer forward.
The diagram shows the path we build (Logo Edge WMS), from your sites to the data center and from the dedicated VPC to the isolated backup zone. Application and database HA clusters and the DR site (passive, or active with a Global Load Balancer) are added with the buttons above the diagram. It is illustrative; ports, database, and integration details are confirmed with the vendor before installation.

How to read the diagram

  1. 1
    Your sites and staff connect over encrypted links

    Head office and branches come in from their own firewall over an IPsec tunnel, or over an MPLS or SD-WAN circuit. Staff outside the office use SSL VPN, ZTNA, or ARGE ZTNA. Where an application is internet-facing, its traffic passes through the WAF.

  2. 2
    Traffic is filtered at the data center edge

    The connection goes from the data center router to the ARGE ICT Backbone HA Cluster and then to the firewall. All three are HA pairs side by side; if one fails, the other takes over.

  3. 3
    Your dedicated VPC: firewall and WAF

    Traffic entering the VPC passes your own firewall and then the WAF, and a load balancer spreads it across the application servers. The application, terminal, and database servers run in this VPC. On request we build the application and database tiers as HA clusters.

  4. 4
    Monitoring and security service beside the VPC

    Server, disk, network, and backup status show on the monitoring dashboard. Logs are collected in SIEM and SOAR, and alerts are handled in defined steps. Antivirus and XDR/EDR run on the servers, and DLP monitors unauthorized transfers of sensitive data. The scope is set in the contract.

  5. 5
    Enterprise hardware, fast internal network

    The environment runs on Dell and Supermicro servers with Xeon Platinum processors and enterprise NVMe drives. Hosts are interconnected at 25G, 50G, 100G, or 200G with NVIDIA Mellanox cards.

  6. 6
    Backup in an isolated zone, DR site optional

    Backups are kept in an isolated backup zone, separate from the production environment. On request we build an identical environment in a second data center: in passive mode it takes over in a disaster, in active mode a Global Load Balancer spreads traffic across both sites.

What is Logo Edge WMS?

Logo Edge WMS is Logo's on-premises warehouse management system (WMS). According to Logo, its earlier names were Logo WMS and Logo WMS Platform; today it is offered in two packages, Platform and Basic. Goods receipt, putaway, replenishment, picking, shipping, and stock management are functions common to both packages.

The Platform package includes production stages, script-based customization (WMS Platform Script), and additional tables and fields. It tracks address and zone, pallet, serial and lot, reserved, damaged, rejected, and blocked stock, as well as returns, and it reads barcodes, RFID, and QR codes. The AS/RS module for automated storage systems, BackOffice, and the Polaris Digital Assistant are also part of this package.

The Basic package is parametric and has no script-based customization: address, pallet, or expiry date tracking is switched on with a parameter. According to Logo, mobile use stays the same when moving from Basic to Platform.

Companies that use the Platform and Basic packages

According to Logo, Basic is designed for companies that use Logo Edge T-Series and N-Series ERP, while Platform also works on its own. The product is used in manufacturing and distribution warehouses. Logo's Platform brochure names food, electronics, textiles, white goods, and spare parts as example sectors.

The choice of package depends on one question: are the processes standard, or does the warehouse need its own rules, screens, and automation links? In the first case Basic is chosen; in the second, Platform, which can be customized with scripts.

The heavy work is the scanning that runs through the shift and the two-way sync with the ERP. In the Platform package, the database also grows as script customizations and additional tables are added. Server resources are set by both the modules used and the number of concurrent devices, and the plan is redone when moving from Basic to Platform.

Server, mobile devices, and ERP sync

According to Logo, the product runs on a Windows and SQL database server and has mobile apps for iOS, Android, and Windows. The database has been redesigned with foreign keys and macros are stored in the database, which determines the scope of the backup.

ERP sync is two-way: master records flow from the ERP to the WMS, and transactions flow from the WMS to the ERP. If the connection slows down or drops, the sync lags and warehouse transactions are posted to the ERP late. The method and frequency of the sync are settled with Logo or your partner before setup.

It is enough for devices to be on the local network; the warehouse does not need a separate internet connection. When the server moves outside the warehouse, the link leaving the local network becomes the only path for scans and sync. As long as the server cannot be reached, transactions on the devices cannot be completed.

Logo Edge WMS setup on ARGE Cloud

Edge WMS and Microsoft SQL Server run on Windows Server in your dedicated virtual private cloud (VPC) on ARGE Cloud. A highly available (HA) firewall is placed in front of the VPC; ARGE Cloud is our own infrastructure running in a data center in Istanbul. Logo ERP is placed in the same VPC, and the sync traffic stays inside it.

The warehouse Wi-Fi and the server link are part of the setup: devices go from the local network through the warehouse firewall to the VPC over an encrypted link. The warehouse link is built over IPsec, MPLS, or SD-WAN and is monitored; we recommend a second link. Individual users who work outside the office connect over SSL VPN, zero trust network access (ZTNA), or ARGE ZTNA. If an internet-facing component is added, we route its traffic through a web application firewall (WAF).

Both databases go to the isolated backup zone on the same plan, and the restore test runs together with the ERP; the frequency is set in the contract. If the two databases are restored to different times, the WMS and ERP records no longer match, which is why they share one plan. Edge WMS's application configuration is also in the backup scope. The backup arrangement is described on our backup and disaster recovery page.

We monitor the server, the SQL Server service, disk and memory, the warehouse link, and backup results. Security tools run in a service zone beside the VPC: security information and event management (SIEM), security orchestration, automation, and response (SOAR), antivirus, and XDR/EDR. The contract defines which hours are monitored and how far a response goes.

For warehouses that use AS/RS, an application and SQL HA cluster and a disaster recovery (DR) site in a second data center are optional. Edge WMS's cluster support is confirmed with Logo. For these warehouses, server maintenance is scheduled around the shift plan.

Script customizations, package selection, and mobile app settings stay with your Logo partner. We obtain the server and network requirements of the AS/RS module from Logo; we take on the servers, the network, backups, and monitoring.

Logo Edge WMS system requirements and preparation checklist

Logo's Edge WMS document, which we read in November 2026, has no table of cores and memory. Logo instead lists what has to be in place in the warehouse. Because of that, we confirm server size with Logo based on the number of devices and the transaction volume. The server must be a machine that runs continuously; the handheld terminals depend on it, so when the server stops, work on the warehouse floor stops too.

The warehouse needs access points for the handheld terminals, with no area left without coverage, and Logo wants the server to answer a ping through an access point. The terminal must be able to join the Wi-Fi, and terminals running a Microsoft operating system also need a Telnet license. In our setup the warehouse line reaches the VPC over IPsec, MPLS, or SD-WAN, so we test the whole path from the access point to the server together.

If the ERP and the WMS server talk to each other over the internet, a VPN must be set up, and Logo gives two minimum speeds: at least 8 Mbps download on the WMS side and at least 2 Mbps upload on the ERP side. When we place the Logo ERP in the same VPC, the sync traffic stays inside the VPC and this VPN is not needed. SSL is mandatory with Edge: once the certificate is defined on the server, SSL is bound to port 4567.

The same document also holds a separate value list for Logo WMS Platform, the pre-Edge release of the product. Those values do not belong to Edge WMS; an installation moving from the older release should have its server reviewed against the Edge WMS checklist above.

What we confirm with Logo before setup

  • Supported Windows Server and SQL Server versions
  • Server size by device count and transaction volume (Logo's document has no table)
  • How mobile devices connect to the server, and the ports
  • The connection method for the sync with Logo ERP
  • Server and network requirements of the AS/RS module
  • Operating conditions in an HA cluster

Technologies: Windows Server · Microsoft SQL Server · IPsec · MPLS · SD-WAN · ARGE ZTNA · ARGE Cloud

Frequently asked questions

Are Logo WMS and Logo Edge WMS the same product?

According to Logo, the earlier names of the product are Logo WMS and Logo WMS Platform. Today it is offered as Logo Edge WMS, in the Platform and Basic packages. Whatever the name, the product we discuss on the infrastructure side is the same.

Does the infrastructure change when moving from the Basic package to Platform?

According to Logo, mobile use stays the same. The production stages, additional tables, and script customizations that come with Platform enlarge the database, and server resources and backup space are re-planned accordingly.

What is planned for the server in a warehouse that uses the AS/RS module?

Because the robots stop when the server stops, we recommend an optional application and SQL HA cluster and a second link for the warehouse. We confirm with Logo the conditions under which Edge WMS runs on a cluster.

Are WMS customizations and macros included in the backup?

According to Logo, macros are stored in the database and are taken together with the database backup. If script files are kept separately on the server, we add them to the backup scope. We ask for the location of the script folder before setup.

What server and network preparation does Logo Edge WMS need?

Logo asks for a server that runs continuously, access points that leave no area without coverage, and handheld terminals that can join the Wi-Fi. Terminals running a Microsoft operating system need a Telnet license. SSL is mandatory, and once the certificate is defined it is bound to port 4567.

For Logo Edge WMS, licensing, implementation, and functional support are obtained from the vendor or your partner. Logo Yazılım makes the software and owns its name and trademark; ARGE ICT is not an official partner or reseller of the vendor, and it provides and operates the infrastructure underneath the software.

Sizing call for warehouse management system infrastructure

Share your warehouse and handheld terminal counts and the software you use; we respond to your request within one business day.

Request a sizing call