Warehouse automation investment in India is accelerating. AMRs, ASRS, conveyor systems, pick-to-light and sort-by-light, technologies that were pilots five years ago, are increasingly adopted in FMCG, e-commerce, and 3PL distribution. The question operations leaders are now asking is not whether to automate, but which technologies deliver real ROI and what has to change in the software layer to realise it.
The answer to the second question is the one most frequently missed: automation hardware is only as effective as the system orchestrating it. A warehouse with AMRs each running on their own software, with no central task coordination and no connection to human workflows, has not automated its operation. It has added complexity. The WMS, or in Stackbox's framing the Warehouse Orchestration System, is what coordinates automation as a system rather than as isolated equipment.
AMRs handle goods-to-person picking, inter-zone transport, and inbound putaway. In FMCG and e-commerce DCs with large floor areas, AMRs reduce picker travel distance significantly. The ROI is strongest in operations where human travel time is a measurable drag on throughput. In compact operations where travel distances are already short, the case is weaker.
ASRS, mini-load systems, cube storage, shuttle-based systems, address high-density storage requirements where conventional racking has reached its spatial limits. They are capital-intensive and best suited to operations with consistent SKU profiles and predictable demand. In operations with high SKU churn or significant seasonal variation, the fixed configuration of ASRS can become a constraint rather than an advantage.
Conveyor systems move goods horizontally through a facility. Sortation systems direct items to the correct pack station or dispatch lane. In e-commerce and 3PL operations processing thousands of small orders per hour, sorters are enabling technology.
Sorters can be controlled through a WMS, a WCS (Warehouse Control System), or a dedicated sorter controller; different architectures exist in production. SAP's Material Flow System (MFS), for example, is integrated within SAP EWM and communicates with equipment through the interfaces configured for the supported architecture, rather than being a separate middleware product between the WMS and the hardware. The evaluation question is not whether the WMS can control the sorter directly, but whether the sorter routing logic is coordinated with the rest of the warehouse operation or runs independently.
Pick-to-light systems guide pickers to the correct location using visual indicators, eliminating the need to read a pick list or scan at each location. Sort-by-light guides operators sorting items into orders or dispatch lanes. Both reduce pick errors and increase throughput in environments with high pick rates and a limited SKU range. ROI is strongest where the current bottleneck is scanning and reading time at the pick face.
GTP systems bring inventory to a stationary picker rather than requiring the picker to travel to the inventory. In operations with large floor areas and high pick velocity, GTP reduces travel time dramatically. Travel time is one input to the ROI case, alongside equipment cost, utilisation, labour costs, throughput constraints and maintenance. No single travel metric establishes a proportional financial return.
Each automation technology above has its own control system. An AMR fleet has a fleet management system. An ASRS has a warehouse control system. A sorter has a sorter controller. If these systems operate independently, each receiving instructions from a different source, unaware of each other's state, the warehouse has multiple decision-makers. The result is congestion, idle time, and throughput ceilings that no individual technology can break through.
Warehouse orchestration puts a single intelligence layer above all of these. A Warehouse Execution System (WES), which Stackbox positions as a Warehouse Orchestration System (WOS), receives real-time state information from the assets it integrates with and makes task allocation decisions based on that combined picture rather than the view from one control system alone.
When an AMR completes a delivery in zone C, the orchestration layer knows the AMR is available in zone C and assigns the next task accordingly. When a sorter lane is approaching capacity, the orchestration layer can redirect output before a jam forms. When a 4-hour SLA order enters the system alongside 48-hour orders, the orchestration layer can elevate its priority where resources are eligible and available.
Automation hardware performs the physical work; orchestration coordinates it across the operation. Without coordination, independently controlled assets can leave potential throughput unrealised.
Human workers, AMRs, and conveyor systems all draw from the same task queue, managed in real time. Task assignment considers the current location of every resource, the priority of every pending order, and the state of every zone. A worker finishing a putaway task in zone B is typically assigned a suitable next task nearby rather than one requiring a long walk, subject to task priority and eligibility.
The orchestration layer monitors zone occupancy in real time and reroutes task assignments before congestion forms. When a zone is approaching capacity, the system stops routing additional resources to that zone and distributes work to adjacent zones. This is proactive management, the system does not wait for a jam before intervening.
In operations with mixed SLA profiles running simultaneously, the orchestration layer continuously recalculates which orders are under the most time pressure and factors this into resource allocation. Priority is one input; allocation also respects resource eligibility, safety, capacity, stock availability and task dependencies.
Integration breadth varies by platform. Stackbox WOS integrates with AMRs, ASRS, conveyors, pick-to-light, and sorters from multiple vendors through standard protocols; hardware support depends on tested interfaces, specific models and integration scope. New automation hardware integrates into the existing orchestration architecture where those interfaces are supported.
Stackbox reports 2x throughput of automation hardware on its product page. This is a Stackbox-reported figure, not an independently audited result, and the outcome in any operation depends on the degree of automation and the quality of the implementation.
The gap between automation that is deployed but not orchestrated and automation that is fully coordinated represents a meaningful share of potential ROI. The exact figure depends on the operation, the degree of automation, and the quality of the orchestration implementation.
WMS manages inventory records, order allocation, and workflow logic. WES orchestrates physical task execution across workers and automation in real time. WOS, in Stackbox's framing, combines both with adaptive decision-making and simulation. Stackbox WOS includes these in a single platform, with no middleware required between the layers.
Automation can be coordinated through native WMS capabilities or through an integrated WES/WCS, including an external execution layer that provides central coordination. Assess the supported interfaces, task ownership, response times and operational responsibility before deciding whether the existing WMS must change. A platform with native WMS and WES handles new automation within one architecture; an integrated execution layer is also a valid model.
Automation costs vary widely by technology, vendor, fleet size, and operational requirements. AMR deployments, ASRS, and conveyor systems each have different capital and operating cost profiles. Payback periods depend on labour costs, throughput gains, and the quality of the orchestration software. For accurate figures, operations should obtain quotations from automation vendors based on their specific layout, throughput requirements, and operational profile, rather than relying on published ranges.
Start with travel time analysis. If significant picker time is spent walking between locations, AMRs or GTP address the primary constraint. If throughput is limited by sorting and dispatch, conveyor and sortation systems are the priority. If storage density is the constraint, ASRS may be appropriate. The technology should follow the constraint analysis, not precede it.
To discuss warehouse orchestration and automation integration for your operation, visit stackbox.xyz/product/sbx-wms.
