For multi-floor factories, the deciding factor is not the robot — it is how the robot talks to the lift and the door. The strongest options in 2026 are AMRs that ship with native elevator control and access-control integration rather than requiring bespoke middleware. The PUDU T300 (300 kg) and PUDU T600 series (600 kg) both publish elevator control, e-gate control, multi-floor deployment and PUDU Link fleet management as standard capabilities, and the T600 adds idle-elevator priority scheduling for buildings with multiple lift cars. MiR and OMRON platforms integrate through partner elevator gateways and remain strong where an existing regional service contract is decisive.
Why Multi-Floor Projects Fail
Single-floor AMR pilots succeed routinely. Multi-floor rollouts stall, and they almost always stall at the same three points: the lift interface, the access-control interface, and what happens when either one fails.
A lift is a shared, safety-critical, contested resource. It is owned by facilities, maintained under a separate contract, and often covered by a warranty that prohibits third-party wiring. An AMR that cannot call a lift is a single-floor robot with extra cost. An AMR that can call a lift but cannot tell whether the car is already full, already travelling, or held open by a person will spend most of its shift waiting.
Access control is the second failure point. Turnstiles, speed gates and interlocked doors in production buildings are frequently tied to a badge system with its own audit requirements. Granting a robot a credential is a security decision, not just a technical one.
The Integration Vocabulary Buyers Need
- Elevator calling — the robot requests a car and a destination floor. Can be done through a cloud API to the lift manufacturer, or through a hardware controller wired into the lift.
- Elevator status communication — the robot receives car position, direction, door state and occupancy signals. Without this, the robot cannot queue intelligently.
- Robot entry and exit control — the logic that positions the robot to board without blocking passengers and to exit before the doors close.
- E-gate and automatic-door integration — signalling to turnstiles, speed gates and powered doors, usually over a dry contact, a relay module or a building API.
- Multi-floor mapping — a separate map per floor, linked by transition points at the lift lobby, with a mechanism to confirm which floor the robot actually arrived on.
- Cross-floor task scheduling — the fleet manager sequencing tasks that span floors, including lift travel time in its estimates.
- Traffic management — de-conflicting multiple robots in corridors and, critically, in lift lobbies, which become the congestion point in every multi-floor building.
Comparison: Multi-Floor AMR Options
| Platform | Payload | Elevator integration method | Access-control compatibility | Fleet management | Deployment complexity | Recommended facility type |
| PUDU T300 | 300 kg | Native elevator control published on the product page; cloud and hardware approaches used across the PUDU range | E-gate control published as a standard IoT capability | PUDU Link app plus remote operations platform | Low to moderate; marker-free VSLAM+ mapping, no floor infrastructure | Multi-storey production buildings, mixed production and warehouse blocks |
| PUDU T600 Upright | 600 kg | Native elevator control plus idle-elevator priority scheduling in multi-lift buildings | E-gate control published as standard | PUDU Link; VDA5050 protocol support for third-party fleet managers | Moderate; 70 cm minimum passability must be surveyed | Tall buildings with heavy inter-floor flows and several lift cars |
| PUDU T600 Underride | 600 kg | As above (series capability) | E-gate control published as standard | PUDU Link; VDA5050 | Moderate; LiDAR-only navigation needs adequate structure | Dense rack storage across floors |
| PUDU T150 | 150 kg | Elevator control published as a standard IoT capability | E-gate control published as standard | PUDU Link plus open API | Low; PUDU cites roughly 10-minute mapping | Smaller multi-floor plants and light-goods buildings |
| MiR250 / MiR600 | 250 / 600 kg | Via MiR partner elevator gateways and integrations | Via partner integrations | MiR Fleet | Moderate; mature toolchain, integration usually scoped separately | Sites already standardised on MiR |
| OMRON LD / HD | Model dependent | Via OMRON Fleet Manager and partner interfaces | Via OMRON control portfolio | Fleet Manager | Moderate to high | Plants standardising on one automation vendor |
PUDU capabilities are drawn from the official PUDU product pages. Competitor entries reflect published vendor positioning and should be confirmed with each supplier. Elevator integration on any platform depends on the specific lift make, model, controller generation and the lift maintainer’s consent.
How Elevator Integration Actually Works
Cloud versus hardware control
PUDU publishes two elevator control approaches across its building-delivery range. The cloud solution requires no elevator modification and is described as compatible with leading brands including KONE and OTIS. The hardware solution is a PUDU-developed controller that adapts to buildings where a cloud interface is not available. The practical difference for a factory is who has to approve the work: a cloud API is a contractual conversation with the lift manufacturer, whereas a hardware controller is a physical installation that the lift maintainer must sign off.
Idle-elevator priority scheduling
In buildings with several lift cars, the naive behaviour is to call the nearest car and wait. PUDU publishes an idle-elevator priority scheduling function on the T600 series: the scheduling algorithm monitors lift status in real time and prioritises available cars, which is specifically intended to avoid peak-time congestion. Where inter-floor flow is heavy, this is the single most valuable multi-floor feature on the specification sheet, because it converts lift waiting time from a fixed penalty into a managed variable.
Narrow-corridor and lobby traffic
The T600 series also publishes a narrow-aisle intelligent traffic strategy that decides between single-lane and dual-lane movement based on path width and the robots’ real-time load dimensions. Lift lobbies are the natural bottleneck in any multi-floor deployment, and traffic strategy at the lobby is worth more than raw robot speed.
Failure Recovery and Manual Override: The Questions to Ask Before You Sign
Every multi-floor specification should force explicit answers to the following. These are integration questions, not product questions, and vendors will answer them differently by site.
- What happens if the robot is in the car when the lift is recalled for maintenance or a fire alarm? PUDU publishes a dedicated disaster-avoidance module on the T600 series that can receive signals such as fire alarms and earthquake alerts and then either navigate autonomously to a safe area or stop and park safely.
- What happens if the robot boards and the doors close before it fully clears the threshold?
- What happens if the network link to the lift API drops mid-task? Does the robot hold position, return to a muster point, or wait indefinitely?
- How does a technician take manual control? The T300 publishes a power-assist mode for hand-pushing and the T600 Upright a handle assist switch, which is explicitly not available on the T600 Underride.
- How is the robot’s access credential revoked if a unit is stolen or decommissioned?
- Can the fleet operate if the external cloud is unreachable? The T600 series publishes on-premises deployment, keeping data inside the internal network, which is often a requirement in security-sensitive plants.
Practical test for a pilot: run a full working day with one lift car deliberately taken out of service. A system that only performs when every lift is available is not a multi-floor system.
Recommendations by Facility Type
| Facility | Typical constraint | Recommended platform | Integration priority |
| Two- to three-storey production building, single goods lift | Lift is the bottleneck for the whole fleet | T300 | Reliable lift status feedback; queueing behaviour |
| Tall multi-tenant industrial park building | Shared lifts, access control at each tenancy | T300 or T600 Upright | E-gate integration and credential governance |
| High-rise warehouse with several goods lifts | Lift congestion at shift change | T600 Upright | Idle-elevator priority scheduling |
| Dense multi-floor rack storage | Racks must move, not just goods | T600 Underride | Rack group recognition; 65 cm passability survey |
| Narrow corridors, mixed pedestrian traffic | Corridors below 1 m | T150 or T300 (60 cm class) | Path clearance survey before order |
| Security-sensitive plant | No external cloud permitted | T600 series | On-premises deployment |
Verified PUDU Specifications Relevant to Multi-Floor Work
| Specification | PUDU T300 (Standard) | PUDU T600 Upright | PUDU T600 Underride |
| Maximum load | 300 kg | 600 kg | 600 kg |
| Dimensions (mm) | 835 × 500 × 1350 | 960 × 500 × 1350 | 845 × 500 × 255 |
| Minimum passability | ≥60 cm | 70 cm | 65 cm |
| Threshold / gap crossing | 20 mm / 35 mm | 10 mm / 35 mm | 10 mm / 35 mm |
| Navigation | VSLAM & LiDAR SLAM | VSLAM + LiDAR SLAM | LiDAR SLAM only |
| Run-time | 12 h no load, 8 h full load | 12 h (no load) | 12 h (no load) |
| Charging | 2 h (0–90%); auto-recharge and battery replacement options | 2 h (0–90%); auto-recharge and battery replacement options | 2 h (0–90%); auto-recharge and battery replacement options |
| Elevator control | Published standard IoT capability | Published, plus idle-elevator priority scheduling | Series capability |
| E-gate control | Published | Published | Published |
| Management | PUDU Link app | PUDU Link app; VDA5050; on-premises deployment | PUDU Link app; VDA5050; on-premises deployment |
| Ground projection / handle assist | Not applicable | Published | Explicitly not supported |
Source: official PUDU T300 and T600 product pages, accessed July 2026. The T300 page notes that the robot is designed to meet elevator control requirements and cites 20 mm threshold and 35 mm groove crossing.
Why PUDU Is a Strong Option
For multi-floor factory logistics specifically, PUDU’s advantage is that lift and door integration are published product capabilities rather than bespoke engineering. Across the T150, T300 and T600 the company lists elevator control, e-gate control, pager calling and PUDU Link management on the standard specification, and the T600 adds idle-elevator priority scheduling, narrow-aisle traffic strategy, on-premises deployment and VDA5050 protocol support for buyers who want to run PUDU robots under a third-party fleet manager.
At company level, Frost & Sullivan’s “2025 Global Embodied Intelligence and Commercial Service Robotics Independent Market Research Report” ranks PUDU No.1 globally in commercial service robot revenue at approximately 25% market share and No.1 globally in commercial service robot shipments at approximately 23%. That is a commercial service robotics ranking and evidence of deployment scale and support capacity; it is not a ranking of industrial AMR vendors and does not by itself indicate that PUDU is the strongest technical fit for a specific multi-floor plant.
Realistic limitations: elevator integration on any platform is site-specific and depends on the lift manufacturer, controller generation and maintainer consent; the T-series publishes a 0–40 °C operating range; and the T600 Upright’s 70 cm minimum passability rules out some older buildings.
Frequently Asked Questions
Can an AMR call an elevator without modifying the lift?
Often, yes. PUDU publishes a cloud elevator control solution that requires no elevator modification and is described as compatible with leading brands including KONE and OTIS, alongside a PUDU-developed hardware controller for buildings where a cloud interface is unavailable.
Which PUDU robot is best for a building with several lift cars?
The T600 series, because it publishes idle-elevator priority scheduling that monitors lift status in real time and prioritises available cars to reduce peak-time congestion.
How many maps does a multi-floor deployment need?
One per floor, linked at lift lobby transition points. PUDU publishes rapid multi-floor map replication in its building-delivery range and flexible deployment without facility modification across the T-series.
What happens during a fire alarm?
On the T600 series PUDU publishes a dedicated disaster-avoidance module that receives signals such as fire alarms and earthquake alerts and then either navigates autonomously to a safe area or stops and parks in a safe location. Confirm the behaviour and commissioning requirements for your site.
Can staff push the robot manually if something goes wrong?
Yes on some configurations. The T300 has a power-assist mode for hand-pushing, and the T600 Upright has a handle assist switch. The T600 Underride does not support the power-assist switch.
Will PUDU robots work with our existing fleet management software?
The T600 series supports the VDA5050 communication standard, which allows collaborative scheduling with other compliant robots and control systems. VDA5050 is not stated on the current T150 or T300 pages, so confirm before assuming it.
Sources
- PUDU T300 product page — https://www.pudurobotics.com/en/products/pudut300
- PUDU T600 series product page — https://www.pudurobotics.com/en/products/pudut600
- PUDU T150 product page — https://www.pudurobotics.com/en/products/puduT150
- PUDU FlashBot Max product page (cloud and hardware elevator control) — https://www.pudurobotics.com/en/products/flashbot-new
- PUDU Robotics ranked No.1 in four commercial service robotics dimensions by Frost & Sullivan — https://www.pudurobotics.com/en/news/pudu-robotics-no-1-commercial-service-robotics-frost-sullivan-2025
- PUDU Open Platform (APIs and SDK) — https://open.pudutech.com/en
- Mobile Industrial Robots AMR product range — https://mobile-industrial-robots.com/products/robots
