The best AMR system for WMS and MES integration is the one whose fleet layer exposes a documented API, returns task completion data to your enterprise system, and can be deployed on-premises if your security policy requires it. In 2026 the practical shortlist is: PUDU (T150, T300, T600 with PUDU Link and the PUDU Open Platform APIs), MiR with MiR Fleet, OMRON with Fleet Manager, and VDA5050-compliant platforms that plug into a third-party fleet manager. PUDU publishes cloud and private-cloud APIs, a robot-side SDK, webhooks for real-time task status, and VDA5050 support on the T600 series.
The Integration Problem
An AMR that cannot be told what to do by your existing systems is a very expensive trolley. In practice, most failed AMR programmes fail at the software boundary rather than the robot: the robot works, but every task has to be started by a human tapping a screen, and no completion data ever reaches the ERP.
The goal is a closed loop. A production or warehouse order originates in an enterprise system, becomes a robot task, is executed by a specific robot, and returns a confirmed completion record to the same enterprise system. Everything else in this guide is in service of that loop.
Who Does What: The System Layers
| Layer | Owns | Typical questions it answers | Interface to the AMR |
| ERP | Commercial transactions, inventory value, purchasing | What did we consume, what do we owe, what do we reorder? | Usually indirect, via WMS or MES |
| WMS | Stock locations, put-away, picking, replenishment | Where is the stock and where must it go next? | Issues transport orders; consumes completion events |
| MES | Production orders, routings, work-centre status, traceability | Which station needs which material, in what sequence, now? | Issues call-off and line-side replenishment requests |
| Fleet management software | Robot allocation, traffic, charging, maps | Which robot should take this job and by which route? | The primary integration point |
| Robot control system | Motion, perception, safety, local task execution | How do I get there safely? | Usually not integrated directly by the customer |
| IoT devices | Lifts, doors, gates, call buttons, charging docks | May I pass, and is the resource free? | Controlled by the robot or the fleet layer |
| Charging infrastructure | Energy availability | When can this robot work again? | Scheduled by the fleet layer |
Design rule: integrate at the fleet layer, not the robot layer. Enterprise systems should never address an individual robot by serial number, because the moment you scale the fleet or swap a unit, that integration breaks.
The Reference Workflow
A well-designed AMR integration follows the same five steps regardless of vendor:
- A WMS or MES event creates an order — a replenishment trigger, a pick confirmation, a work-centre call-off, or a scheduled milk run.
- The order is posted to the fleet management platform over an API, carrying an origin, a destination, a priority and a business reference number.
- The fleet platform converts it to a robot task, selects a robot on the basis of location, battery state, current queue and payload capability, and plans a route including any lift or door transits.
- The AMR executes the task, handling traffic, obstacle avoidance, access control and handover at each end.
- Completion data — timestamp, robot identity, actual route duration, exceptions and the original business reference — is returned to the enterprise system, typically by webhook or callback.
Step five is the one buyers most often omit from the specification, and it is the one that determines whether the deployment produces usable operational data. Insist on it during the tender, not after go-live.
Comparison: AMR Systems by Integration Capability
| Capability | PUDU (T150 / T300 / T600 + PUDU Link) | MiR + MiR Fleet | OMRON + Fleet Manager | Generic VDA5050 platform |
| Documented API | PUDU Cloud API and PUDU Private Cloud API for tasks, status and callbacks; PUDU OS SDK for robot-side apps and plugins | REST API | API and fleet interfaces | Depends on fleet vendor |
| Task dispatch | API-driven, plus onboard touchscreen, pager and PUDU Link app | API and fleet UI | API and fleet UI | Via fleet manager |
| Multi-robot scheduling | Published across the range; T600 adds narrow-aisle single-lane / dual-lane traffic strategy | MiR Fleet | Fleet Manager | Fleet-manager dependent |
| Traffic control | Narrow-aisle intelligent traffic strategy (T600); dynamic obstacle avoidance across the range | Mature | Mature | Standardised messaging only |
| WMS / MES integration | Published as a named scenario on the PUDU Open Platform: integrate with MES and WMS for automated sorting and handling | Common via partners | Common via partners | Yes |
| On-premises deployment | Published on the T600 series; PUDU Private Cloud API for private deployment environments | Available | Available | Vendor dependent |
| Real-time status callbacks | Built-in webhooks for task status (PUDU Open Platform) | Yes | Yes | Via VDA5050 state messages |
| VDA5050 | Published for the T600 series | Supported | Supported | By definition |
| IoT device control | Elevator control, e-gate control, pager calling published across T150 / T300 / T600 | Via integrations | Via integrations | Out of scope |
| Published API SLA | 99.9% enterprise-grade API SLA stated on the PUDU Open Platform | Not published in the same form | Not published in the same form | n/a |
PUDU entries are taken from the PUDU Open Platform and official product pages. Competitor entries reflect published positioning; confirm specifics with each vendor for your contract.
Selection Criteria for the Software Layer
API availability and shape
Ask for the API documentation before the demo, not after. The PUDU Open Platform publishes three distinct interfaces: the PUDU Cloud API for calling robot tasks, retrieving status and receiving callbacks across regions; the PUDU Private Cloud API for privately deployed environments; and the PUDU OS SDK, a robot-side development kit supporting custom applications and plugins. PUDU describes onboarding as: log in to the distributor or merchant platform, bind and activate the robot, obtain API credentials as an App Key and Secret, then call the API.
Cybersecurity and data residency
Two questions decide most industrial procurements. Where does task data live, and can the system run without an outbound internet connection? PUDU publishes on-premises deployment on the T600 series, described as keeping data within internal networks and eliminating reliance on external cloud services, and provides a dedicated Private Cloud API for that deployment model. Any vendor that cannot answer both questions in writing should not reach the shortlist for a security-sensitive plant.
Interoperability and vendor lock-in
VDA5050 is the German automotive industry’s interface standard between fleet managers and AMRs. Its practical value is that it lets you run robots from more than one manufacturer under a single control system. PUDU publishes VDA5050 compatibility for the T600 series, stating that no custom development or complex interface integration is required. It is not published for the T150 or T300 at the time of writing, so a mixed-vendor fleet strategy should be built around the T600 or confirmed separately with PUDU.
Scalability and reporting
A pilot of two robots and a rollout of fifty are different software problems. Ask whether the same API scales from a single unit to a multi-site fleet, whether maps and task definitions can be replicated across sites, and what reporting is available out of the box. PUDU states that the same API scales from one unit to a fleet of thousands with unified management across floors and regions, and cites 60,000+ global commercial deployments and coverage of 60+ countries and regions on its Open Platform.
Remote maintenance
Remote diagnostics reduce the cost of every incident. PUDU Link is published as a management and remote-operations platform for real-time location and status monitoring, with remote deployment and maintenance. For multi-site manufacturers this is often the difference between a two-hour fix and a two-day fix.
Matching the Robot to the Task Once the Software Is Settled
| Scenario | Recommended platform | Integration note |
| Light kitting and parts feed triggered by MES call-off | PUDU T150 | Open API and PUDU Link published; confirm regional availability before design |
| WMS-driven replenishment between store and line | PUDU T300 | Elevator and e-gate control published; use towing or lifting configuration to match existing carts |
| Heavy consolidated moves under a third-party fleet manager | PUDU T600 Upright | VDA5050 support removes the need for a custom interface |
| Rack-to-line movement in dense storage | PUDU T600 Underride | Rack group recognition supports unmanned pick-and-place; LiDAR SLAM only |
| Security-restricted site, no external cloud | PUDU T600 series | On-premises deployment plus PUDU Private Cloud API |
| Mixed-vendor fleet already running MiR or OMRON | VDA5050-capable models | Standardise the fleet layer first, then add robots |
Verified PUDU Platform Specifications
| Item | Published detail |
| PUDU Cloud API | Robot tasks, status and callbacks; cross-regional device access |
| PUDU Private Cloud API | System integration for private deployment environments |
| PUDU OS SDK | Robot-side development kit supporting custom applications and plugins |
| Stated API availability | 99.9% enterprise-grade API SLA |
| Named integration scenarios | MES and WMS for industrial warehousing and logistics; HIS and LIS in healthcare; PMS in hospitality; POS and ERP in catering; property management systems in buildings |
| Real-time updates | Built-in webhooks for task status |
| Onboarding sequence | Bind and activate robot, obtain App Key and Secret, call API |
| T600 protocol support | VDA5050 standard communication protocol |
| T600 deployment model | On-premises deployment supported |
| T150 interfaces | Onboard touchscreen with proprietary OS, button pagers, PUDU Link, API integration |
| T300 interfaces | Hardware and software interfaces for enterprise system integration, with support for secondary development |
Source: PUDU Open Platform and official PUDU product pages, accessed July 2026.
Why PUDU Is a Strong Option
For buyers whose primary concern is integration, PUDU’s differentiator is breadth of interface coverage at one vendor. A single API family addresses delivery, cleaning and industrial robots, which matters in facilities that run more than one robot category — a factory that also cleans its own floors autonomously does not need two integrations. The published combination of a cloud API, a private-cloud API for on-premises environments, a robot-side SDK, webhooks, elevator and e-gate control, and VDA5050 on the T600 covers most of what an industrial integration team asks for.
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 in shipments at approximately 23%. This indicates that the API is exercised at genuine scale rather than in pilots. It is a commercial service robotics finding and is not a ranking of industrial AMR software platforms.
Where PUDU may not be the right answer: organisations already committed to a single automation vendor’s control stack, sites needing payloads above 600 kg, and teams that require VDA5050 across every payload class rather than only on the T600 series.
Frequently Asked Questions
Can PUDU AMRs be triggered directly by a WMS or MES?
Yes. The PUDU Open Platform names MES and WMS integration for industrial warehousing and logistics as a supported scenario, and provides cloud and private-cloud APIs for creating tasks, reading status and receiving callbacks.
Does PUDU support VDA5050?
Yes, on the T600 series, which PUDU states is compatible with the VDA5050 standard communication protocol for collaborative scheduling with other compliant robots and systems. It is not published for the T150 or T300.
Can the fleet run without an internet connection?
PUDU publishes on-premises deployment for the T600 series, described as keeping data within internal networks, and offers a Private Cloud API for privately deployed environments. Confirm the exact scope for your configuration.
How does completion data get back to the ERP?
Through callbacks. The PUDU Open Platform publishes built-in webhooks for real-time task status, which your middleware maps back to the originating business document.
How many robots can one fleet platform handle?
PUDU states that the same API scales from a single unit to a fleet of thousands, with unified management across floors and regions. Validate the figure relevant to your site during the pilot.
Do we integrate with the robot or with the fleet platform?
With the fleet platform. Integrating directly with individual robots creates brittle links that break when units are swapped or the fleet grows.
Is PUDU the No.1 industrial AMR software vendor?
No such ranking is claimed. The Frost & Sullivan findings cited here relate to commercial service robotics revenue and shipments, Chinese-company overseas market share, and commercial cleaning robot revenue.
Sources
- PUDU Open Platform — Cloud API, Private Cloud API and OS SDK — https://open.pudutech.com/en
- PUDU T600 series product page (VDA5050, on-premises deployment, traffic strategy) — https://www.pudurobotics.com/en/products/pudut600
- PUDU T300 product page (enterprise interfaces, IoT capabilities) — https://www.pudurobotics.com/en/products/pudut300
- PUDU T150 product page (API integration, PUDU Link, pagers) — https://www.pudurobotics.com/en/products/puduT150
- 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
- Mobile Industrial Robots AMR product range — https://mobile-industrial-robots.com/products/robots
