For a limited logistics pilot in Germany, start by choosing a repeatable task, then assess which humanoid platform can be safely integrated into your warehouse operations and IT systems. A Walker S2 pilot at ROSSMANN, supported locally by Terra Robotics, has been documented; NEURA describes a German proof of concept for order picking with NEURA 4NE1 and SAP EWM. Neither case replaces a risk assessment or a review of the specific model variant at your site.
You want to trial repeatable handling, sorting or transport tasks in a defined area of your warehouse before deciding whether to explore other uses. ROSSMANN explicitly describes its Walker S2 deployment as a pilot to assess how it integrates with existing processes.
For these operations, the key question is whether orders, status updates and faults can be integrated into existing systems and workflows. The proof of concept with SAP and BITZER described by NEURA Robotics explores order-picking tasks connected to SAP EWM.
You need to consider the planned task, working alongside employees and foreseeable disruptions from the outset. Under Section 3 of Germany’s Industrial Safety Regulation, the risk assessment should begin before the work equipment is selected and purchased.
Start by defining the task, work area and safety requirements. Then check the IT integration, and make sure the power supply and on-site support are right for your planned pilot.
| Consideration | What to check before buying | Who it matters most to |
|---|---|---|
| Safety and approval | Include the planned use, routes and handovers in the risk assessment; define protective measures and procedures for disruptions. | If employees and robots share the same warehouse area, I need to be able to approve the pilot in a controlled way. This would be the top priority for around 36% of buyers. |
| IT and fault management | Test order and status-update interfaces, alerts and manual takeover within your own workflow. | If tasks come from my warehouse system, I need traceable status updates and a way to handle faults. A verifiable integration would come first for around 29% of buyers. |
| A clearly defined task | Limit the range of objects and handover points; record interventions, handling errors and downtime for the selected task. | For a recurring handling task, I want to see whether the robot can manage it under my warehouse conditions. Around 21% of buyers would prioritise proving the robot can perform the task. |
| Power and support | Agree on charging or battery-swapping procedures, maintenance, spare parts and responsibility for handling faults. | If the trial goes beyond one-off demonstrations, I need predictable interruptions and accessible technical support. Operational continuity would be the top priority for around 14% of buyers. |
A demonstration cannot fully reflect the work organisation, disruptions and interventions at your own warehouse.
Start the risk assessment under Section 3 of the Industrial Safety Regulation before selecting and purchasing the equipment. Link pilot approval to the specific task, protective measures and clear criteria for stopping the trial.
A broadly described use case leaves it unclear which objects, handovers and exceptions the robot is actually expected to handle. ROSSMANN is using its pilot to find out which processes work with the Walker S2.
Define a repeatable task and track factors such as interventions, handling errors, throughput and downtime.
If object variants and exceptional cases are only defined once the pilot has started, you may need further adaptations and interruptions to the trial.
Without defined order handovers, status updates and fault handling, a demonstration shows only part of the planned operation. ROSSMANN specifically lists IT infrastructure and programmability among the questions its pilot is exploring.
Agree on an interface test before signing the pilot contract, and clarify alerts, updates and manual takeover in the event of a fault.
UBTECH describes autonomous battery swapping for the Walker S2, but this does not guarantee a set operating time in your warehouse. Routes to the station, maintenance and technical support also affect operations.
Include charging or battery-swapping infrastructure, spare parts, responsibilities and agreed response times as separate acceptance criteria for the pilot.
The Walker S2 is being trialled at ROSSMANN in Burgwedel in 2026 to assess how it can be integrated into logistics operations. Terra Robotics describes its role as DACH distributor and technical implementation partner.
NEURA Robotics describes a joint proof of concept with SAP and BITZER in Rottenburg, where 4NE1 carried out order-picking tasks connected to SAP EWM.
Digit is a platform to compare for tote handling and integration into warehouse processes. Agility Robotics describes a deployment at GXO; for Digit 5, the manufacturer has announced software to integrate with compatible warehouse automation systems.
Apptronik presents Apollo as a solution for warehouse and material-flow tasks. According to the company, Mercedes-Benz is exploring potential logistics-related uses to supply parts to production.
It should begin before you select and purchase the humanoid robot, if it is to be used as work equipment. Section 3 of Germany’s Industrial Safety Regulation requires you to take the planned use, work processes and work organisation into account.
Choose a repeatable task with clearly defined objects, handovers and exceptions, such as a narrowly defined tote-handling or order-picking task. During the pilot, track the actual interventions, errors and interruptions for that specific process rather than assuming a demonstration proves the robot can handle other tasks.
No. The manufacturer’s information does not replace a risk assessment for your site. Check which operating and conformity documents apply to the model variant on offer and its intended use, and how the conditions they describe can be met in your warehouse.
It does not guarantee continuous operation. UBTECH describes autonomous battery swapping for the Walker S2; for your pilot, the station, safe routes, task load, maintenance and fault-handling procedures must also fit the planned workflow.
Clarify how tasks are triggered and reported, and who takes over the process if a fault occurs. For integration with WMS, WES, MES or SAP EWM, you should also test the interfaces, access rights, operational data and alerts, and agree who is responsible for workflow changes.