SAP Piloting Warehouse Orchestration No Other WMS Offers

SAP EWM Is Starting to Move Into Highly Advanced Warehouse Orchestration

At Hannover Messe 2026, SAP and Vodafone Procure & Connect showcased a pilot conducted at Vodafone’s warehouse in Duisburg, integrating humanoid robots with SAP Extended Warehouse Management to execute inspection tasks and return results in real time.

In this pilot, SAP is creating the work, sending it to the warehouse floor, and receiving the results back directly into the same system. The robots were used to identify misplaced or damaged products, assess pallet conditions, flag safety risks, and detect unused space. That information flows back into SAP immediately, where it can drive follow-up actions without relying on separate systems or manual interpretation.

That loop—task creation, execution, and response—sits inside one environment.

This is where the conversation starts to shift.

In most warehouse environments, that loop is fragmented. The WMS releases tasks, automation systems execute them, and reporting tools sit on top trying to make sense of what happened. The decision layer is often disconnected from the execution layer, and that’s where delays, workarounds, and loss of control begin to show up.

What SAP is testing here is a more direct structure. The same system that holds the operational data is also driving execution and reacting to it as it happens. That reduces the number of layers between decision and action.

From there, the implications go beyond the pilot itself.

Once the execution loop sits inside the core system, the question of control becomes very different. In many automated warehouses today, control is not where companies think it is. It sits inside vendor-specific layers—middleware, control systems, or orchestration platforms that are often introduced by integrators. Those layers are usually not transparent, and over time they become difficult to change, extend, or even fully understand without going back to the original vendor.

That’s where long-term dependency starts to build.

Every change requires external support. Every new piece of automation has to be integrated into the same structure. Over time, the operation becomes stable, but rigid. Flexibility drops, and the cost of change goes up.

If SAP EWM continues to move in the direction shown in this pilot, it starts to offer a different model. The execution logic sits closer to the enterprise system, tied directly to inventory, orders, and business rules. That makes it possible to manage workflows, exceptions, and coordination without relying entirely on external orchestration layers.

It also changes how different technologies fit into the warehouse. Robots, automation systems, and even manual processes can operate within the same framework, instead of being managed through separate control environments. That doesn’t remove complexity, but it changes where that complexity is handled.

There is also a workforce aspect to this. The same structure that assigns and validates robotic tasks can apply to human-driven work. Tasks can be created, adjusted, and validated based on real-time conditions rather than fixed sequences. That becomes more relevant as operations mix different types of automation with human intervention.

SAP is tying this into its Joule layer, but the key point is simpler than that. The decisions remain grounded in operational data inside the system—inventory positions, order priorities, and constraints. That keeps execution aligned with how the warehouse actually runs, rather than separating logic from reality.

This is still a pilot, and it will take time to see how far it goes in production environments. But it shows a direction where SAP EWM is not just supporting warehouse operations—it is moving closer to coordinating them directly, with fewer external layers between planning, execution, and response.