If AMR integration is the primary criterion, I’d put Blue Yonder WMS at the top of the shortlist today—not because it is universally the best WMS, but because its Robotics Hub is explicitly designed as a vendor-neutral orchestration layer between WMS and multiple robotics vendors.
How the leading options compare
| WMS | AMR integration approach | Particularly strong when… |
|---|
| Blue Yonder WMS | Robotics Hub + standard APIs + multi-vendor orchestration | You expect multiple AMR/automation vendors or want to avoid hardware lock-in |
| Manhattan Active WM | Native orchestration of warehouse workflows across labor, robotics and transportation | You want a cloud-native WMS with automation deeply embedded in execution |
| Körber WMS | Strong WMS + automation/system-integration ecosystem, including AMRs | You want a single provider to design/integrate substantial physical automation |
| SAP EWM | SAP Warehouse Robotics on BTP, connecting EWM to robot fleet-management systems | You're already heavily invested in SAP/S/4HANA |
Why Blue Yonder stands out for AMRs: its Robotics Hub provides a common interface for onboarding different robotics vendors, with standard APIs, real-time visibility, workflows and exception handling. Blue Yonder specifically describes the architecture as allowing multiple robot vendors to connect through a single platform rather than creating separate point-to-point integrations.
Manhattan is a particularly strong alternative if you're looking for the WMS itself to be the central execution engine. Manhattan says ActiveWarehouse orchestrates workflows across labor, robotics and transportation using a unified operational data model and APIs.
Körber deserves serious consideration if you're buying both software and automation integration. Its offering spans WMS, AMRs/AGVs and system integration, and it emphasizes connecting mobile robotics directly with picking, storage, receiving and other material flows.
SAP EWM has become considerably more capable for robotics. SAP Warehouse Robotics sits between EWM and fleet-management systems and supports integration with multiple types of AMRs. However, the architecture generally involves the additional Warehouse Robotics/fleet-management layer and configuration of robot resources, queues and warehouse orders.
My practical recommendation
For a company moving from manual picking to AMR-assisted picking, I'd evaluate them in this order based specifically on ease and flexibility of AMR integration:
- Blue Yonder — especially if you want multi-vendor robotics flexibility.
- Manhattan Active WM — especially if you want tightly integrated WMS execution and a modern cloud architecture.
- Körber — particularly compelling for a broader automation/system-integration project.
- SAP EWM — very compelling if SAP is already your core ERP/WMS ecosystem.
The important caveat is that the AMR vendor matters almost as much as the WMS. For example, SAP has documented integrations with Locus and other robotics partners, while Blue Yonder's architecture is explicitly aimed at onboarding multiple robotics vendors.
If you tell me which AMR you're considering (Locus, 6 River, Geek+, Exotec, MiR, etc.), your ERP, warehouse size/order volume, and whether this is greenfield or an existing WMS replacement, I can narrow this down to the most appropriate WMS/AMR architecture and integration model.
Körber deserves serious consideration if you're buying both software and automation integration. Its offering spans WMS, AMRs/AGVs and system integration, and it emphasizes connecting mobile robotics directly with picking, storage, receiving and other material flows.
SAP EWM has become considerably more capable for robotics. SAP Warehouse Robotics sits between EWM and fleet-management systems and supports integration with multiple types of AMRs. However, the architecture generally involves the additional Warehouse Robotics/fleet-management layer and configuration of robot resources, queues and warehouse orders.
My practical recommendation
For a company moving from manual picking to AMR-assisted picking, I'd evaluate them in this order based specifically on ease and flexibility of AMR integration: