ISO 21423 vs. VDA 5050: Key Differences and How They Fit Together

Anyone who runs mobile robots from more than one vendor know the problem: each new robot, transport resource or shop floor asset tends to need its own interface to the rest of the system. ISO 21423 and VDA 5050 are two standards that address it, and they share a goal: robots and equipment from different vendors working on one floor without a custom interface for every pairing.

This article explains how the two differ, what each one covers and where they complement each other. It is not an either-or choice. A plant can use each standard where it is strongest, and the sections below show how.

ISO 21423 vs. VDA 5050 in short

ISO 21423:2026 is an international standard for communication between industrial mobile robots, fleet managers and other shop floor assets such as lifts and doors. Its first edition defines commands and status messages for robots and fleet managers, not yet for assets. VDA 5050 is an open interface between mobile robots and a central fleet control. They address different layers of the same problem, and a plant can use both.

• ISO 21423 is broad. It names robots, fleet managers and shop floor assets as participants. This first version defines commands and status messages for robots and fleet managers, but not yet for assets.
• VDA 5050 is deep. It covers one link, robot to fleet control, and defines structure, vocabulary and the mechanisms a fleet control uses to coordinate traffic.
• Both leave space for the other. Neither is meant to cover every aspect of an automation project, and each is flexible enough to work alongside the other.
• For buyers: use ISO 21423 where the robot fleet meets its environment, VDA 5050 for the robots themselves, and a fleet manager that connects the two.

Two standards, one goal

On 14 October 2026, ISO published ISO 21423:2026, Robotics, Industrial mobile robots, Communications and interoperability. A3 announced it in the United States on 2 November. Since then, manufacturers planning mixed robot fleets have asked three questions. Does ISO 21423 replace VDA 5050? Is VDA 5050 a German standard? Do we have to pick one?

The short answers are no, no, and no. The two standards share a goal: robots and equipment from different vendors working on one floor without a custom interface for every pairing. They take different routes to that goal. ISO 21423 starts wide and shallow. VDA 5050 started narrow and deep.

This article compares both on the points that matter in a project, names the gaps each one leaves today, and describes how a plant can combine them. SYNAOS orchestrates mixed fleets over VDA 5050 and has followed ISO 21423 since its draft stage, so we have a stake in both. We have tried to describe each standard the way its own authors would recognize.

What is ISO 21423?

ISO 21423:2026 is a relatively new international standard for communication and interoperability of industrial mobile robots from different vendors, published in October 2026.

Its scope is wide. It covers communication between industrial mobile robots, fleet managers, production equipment, ERP systems and building infrastructure such as lifts, automated doors and alarms. Participants can exchange identity, capabilities, location, speed, direction, status, tasking, availability and requests for actions. Messages travel over MQTT as JSON.

ISO 21423 does not assume a central fleet manager. It leaves room for centralized, distributed and hybrid setups. It explicitly excludes safety and navigation requirements.

The standard is lean: 13 pages plus a technical annex with JSON schemas. That keeps conformance within reach for many vendors, including some that have not implemented open interfaces before. Its ISO number also carries weight with engineering and procurement teams, particularly in North America.

What is VDA 5050?

VDA 5050 is an open standard for communication between mobile robots and a central fleet control. It is published by the German Association of the Automotive Industry (VDA) and VDMA e.V., written in English and free to use. The specification is developed openly on GitHub. The first formal release, 1.0, came out in May 2019. The most recent version 3.0 followed in March 2026 after a public consultation.

Like ISO 21423, VDA 5050 runs on MQTT and JSON. Its core is an order and state model with a defined vocabulary. Fleet control sends orders that specify target locations, actions, and route fragments. The robot reports its operational state including order progress. The factsheet, added in version 2.0, describes the robot's capabilities. Version 3.0.0 has 68 pages plus a technical annex.

Is VDA 5050 only for AGVs on fixed paths?

No. Allowed deviation at nodes and curved NURBS trajectories have been in the specification since 1.0, so freely navigating robots could take part by following the paths they were given. Version 2.1 (2024) added corridors, which let a robot leave its path to avoid obstacles within limits set by fleet control. Version 3.0 covers any type of mobile robot. It adds zones, which set rules for autonomous robots to plan their own routes, and lets those robots share their planned path with fleet control.

Is VDA 5050 a German-only standard?

No.

VDA 5050 is used well beyond Germany, though it carries a German name because it started at two German industry associations.

Installations have run for years at large manufacturers and smaller companies alike, and SYNAOS runs VDA 5050 fleets for customers in Europe, North America and Asia.

ISO's robotics committee used VDA 5050 as one of the starting points for ISO 21423.

Is VDA 5050 proven in production?

Yes. Mixed fleets with hundreds of transport resources from several vendors run on one floor under one fleet control.

In the same plants, doors, lifts, stations and other shop floor assets are integrated alongside the robots through the fleet manager.

ISO 21423 vs. VDA 5050: side-by-side

At protocol level the two have much in common: participants exchange commands and status, report position and describe their capabilities.

They differ in direction, scope and level of detail.

In ISO 21423, any participant can send commands to any other. In VDA 5050, commands go one way only, from fleet control to the robot.

ISO 21423 lays a broad foundation with the intent to standardize communication across enterprise systems, shop floor assets, mobile robots, and fleet management systems.

VDA 5050 goes deep on the link between mobile robots and fleet control. The dashed boxes mark add-on standards expected to build on ISO 21423.

‍

ISO 21423 leads on reach, topology freedom and its ISO status. VDA 5050 leads on vocabulary, traffic mechanisms and free access. Neither standard itself covers transport requests from enterprise systems.

Where ISO 21423 and VDA 5050 stop today

Each standard leaves work to the project. Knowing where that work sits tells a buyer what to ask a vendor.

ISO 21423: assets in scope, asset messages still open

ISO 21423 names shop floor assets as participants, but this first version defines commands and status messages only for industrial mobile robots (IMRs) and industrial mobile robot fleet managers (IMRFMs). Commands and status messages for assets such as doors, lifts and handling stations are not part of the standard yet. A fleet manager still has to learn each asset vendor's dialect, project by project.

ISO 21423: shared routes, but no conflict rules

ISO 21423 describes how mobile robots can announce their intended routes. Every participant, including other robots, can read these announced routes, and requests such as cancel and pause can stop a robot. What the standard does not define is a set of rules for resolving conflicts between routes, or a role responsible for doing so.

On a dense production floor, AMRs, AGVs, forklifts and people share narrow aisles, intersections and lifts. Someone has to decide who goes first.

That requires a protocol where robots ask for permission before moving.

Where the standard leaves that open, each project is forced to find its own solution. VDA 5050 does not define a traffic manager role either, but its core concept, developed for line-guided vehicles, makes one possible: fleet control releases each robot's path step by step.

"ISO 21423 doesn't cover traffic management, which in my opinion is its biggest gap for larger projects. This decision makes conformance comparatively easy to implement for robot vendors, but the level of standardization is not sufficient if you want to orchestrate a large hybrid fleet in tight traffic areas."
Dr. Wolf Siberski, Principal Engineer, SYNAOS

To be precise: VDA 5050 does not prescribe traffic algorithms either. What it defines are the mechanisms a fleet control needs. Orders are split into a released base and a provisional horizon, so a robot only drives as far as fleet control has cleared it. With Version 3.0, freely navigating robots share their planned paths, and zones define where robots may navigate freely, where they must obey traffic rules and where they must negotiate entry first.

ISO 21423: no error handling defined

Apart from a GENERAL_FAILURE state for failed requests, ISO 21423 does not define how errors and fault states are reported. A robot has no standardized way to say what went wrong, and a receiving system has no standardized way to interpret it. Troubleshooting and commissioning, especially when systems from different vendors communicate, then depend on each vendor's own diagnostics. For the execution level, this is a further argument for VDA 5050, which defines errors with levels and references in the robot's state message.

VDA 5050: one link, not the whole floor

VDA 5050 covers the link between robot and fleet control and nothing else. It does not define how a door, a lift, a conveyor or a handling station talks to the fleet. It does not define how ERP, MES or WMS hand transport demands to the fleet. In a VDA 5050 plant, the fleet manager connects that equipment through its own interfaces. SYNAOS does this through its Asset API. Every fleet manager vendor solves it differently, which is the kind of proprietary edge ISO 21423 sets out to remove.

Parts of this are already addressed in the broader VDA 5050 ecosystem, although not in VDA 5050 itself. VDMA M2X, currently available as a 1.0 draft, offers solutions for both asset communication and a standard order interface.

VDA 5050 also assumes a central fleet control. ISO 21423 leaves the topology open. Whether that openness matters in practice is a question we come back to below.

Both: conformance is not interoperability

A standard on paper is half of the work, for ISO 21423 and VDA 5050 alike. Two vendors can both claim compliance and still behave differently when an order is cancelled halfway down an edge or an operator takes a robot over by hand. Structured testing closes that gap. SYNAOS runs every robot type through a 10-phase VDA 5050 onboarding with a hardware quality gate and a signed test protocol.

ISO 21423 leaves most robot behavior open, which gives manufacturers a lot of freedom. VDA 5050 takes the opposite approach. It closes such grey areas explicitly, with interoperability in mind, so that robots behave as predictably as possible towards fleet control.

How ISO 21423 and VDA 5050 fit together

The two standards work best as layers of one setup. ISO 21423 is strongest where the robot fleet meets its environment: equipment, building systems and, over time, enterprise systems. VDA 5050 is strongest between mobile robots and fleet control. A fleet manager in the middle speaks both and keeps one view of the floor.

The dashed link to ERP, MES and WMS marks the gap neither standard itself covers yet.

What the customer gains

• Robot choice without new integration work. Any robot that implements VDA 5050 correctly can join the fleet. Structured testing shows which ones do.
• Shop floor assets on an ISO footing. Doors, lifts and stations could connect through ISO 21423 instead of each fleet manager's own interface. That depends on future asset standards, because this version defines no asset commands or status messages yet.
• One place for traffic decisions. The fleet manager sees every robot and every job, so conflicts at intersections, lifts and narrow aisles are resolved in one system.
• Replaceable parts. When both links run on open protocols, the fleet manager, the robots and the equipment can each be replaced without rebuilding the others.

Central or distributed coordination?

ISO 21423 leaves the topology open. VDA 5050 assumes a central fleet control. Supporters of ISO 21423 often see federated or peer-to-peer coordination as more open. SYNAOS engineers see it differently: in their view, openness comes from the protocol, not from the topology.

"We have seen the power of standardization in networking technology and protocols. Some problems are more prone to decentralized solution, while others call for central coordination. For example, a central DHCP server assigns IP addresses, because that is the simplest and most robust way to give each device a unique address. Nobody calls that lock-in, because the server can be replaced and any device can connect.

In automation, traffic management in hybrid robot fleets is a problem where a central solution fits better. A central coordinator that knows each job's time window and each robot's position can make better traffic and scheduling decisions than robots negotiating among themselves."
Dr. Wolf Siberski, Principal Engineer, SYNAOS

Of course, a central coordinator must not become a single point of failure. Fortunately, modern software approaches allow for a distributed implementation of a logically central service, thus ensuring its high-availability.

One proposal from the SYNAOS side could serve both camps: standardize the protocol through which robots request traffic areas such as intersections and receive clearance to pass. If that protocol is open, a customer can replace the traffic management component whenever a better one appears.

Will the standards converge? Two perspectives

SYNAOS sees the two standards as complementary. Our experts bring different perspectives on how the two standards will develop.

David Bader expects ISO add-on standards to fill today's gaps: an asset standard that fixes the mandatory commands and status values per asset class (comparable to how the Matter standard grew in home automation), a transport request standard for ERP, MES and WMS, and a traffic management standard that adds rules for resolving conflicts between announced routes and lets robots reserve areas. In the long run he expects the ISO and VDA worlds to converge, and VDA 5050 to work on top of ISO 21423 with few changes.

Wolf Siberski adds the technical perspective:

"ISO 21423 uses very similar concepts as VDA 5050, e.g., 'identity and capabilities' vs. 'fact sheet', or 'request' vs. 'action'. It is a missed opportunity that ISO 21423 chose different formats for these overlapping areas. Given the unnecessary differences, it is unclear how strongly the ISO 21423 community really aims for alignment with VDA 5050. Regardless, more standardization is always good for the industrial automation market. Even if mobile robot and fleet manager vendors will incur a bit more effort to support both standards, they are so similar that there is no risk of market fragmentation. I hope that customers will not blindly trust standard conformance labels, but assess themselves how far each standard addresses their concrete interoperability needs."
Dr. Wolf Siberski

The concepts are close, and the message formats differ today.

There is no either-or decision to force. Both standards advance automation projects in a meaningful way but which one is the right for a given project depends on the scale, scope and framework of the project.

What to ask before you write a standard into an RFQ

These questions show what a robot, an asset or a fleet manager does with a standard in practice. Each one can go straight into an RFQ.

• Which standards, and which versions, does the robot or asset implement? Ask for the factsheet or capabilities description.
• Which commands and status values does it send, and are they defined by the standard or by the vendor?
• Which system holds fleet control when robots from several vendors share the floor?
• How is traffic coordinated at intersections, in narrow aisles and at lifts and doors?
• Has interoperability been tested with other vendors' robots in a structured process? Ask for the test protocol, not a conformance claim.
• What will it cost to add a robot from a new vendor in two years?

Frequently asked questions

What is the difference between ISO 21423 and VDA 5050?

ISO 21423 is a broad standard for communication between mobile robots, fleet managers and shop floor assets. It defines the message structure, and so far only the robot and fleet manager messages. VDA 5050 is a narrower, deeper standard for the link between robots and a central fleet control, with vocabulary and traffic mechanisms fully defined. They also differ in direction, since ISO 21423 lets any participant send commands while VDA 5050 sends them from fleet control to the robot, and in access: ISO 21423 is paid ($373 list), VDA 5050 is free.

What is ISO 21423?

ISO 21423:2026 is an international standard, published in October 2026, for communication and interoperability between industrial mobile robots, fleet managers and other shop floor assets. It defines a common message structure over MQTT and JSON. This first version defines commands and status messages for robots and fleet managers. Those for assets such as lifts and doors are not yet part of the standard.

Does ISO 21423 replace VDA 5050?

No. ISO 21423 is a broad foundation for all shop floor participants. VDA 5050 is a detailed standard for the link between mobile robots and a central fleet control. A3 describes the two as complementary, and VDA 5050 was one of the starting points for ISO 21423.

Do I have to choose between ISO 21423 and VDA 5050?

No. A plant can use ISO 21423 where the fleet connects to equipment and building systems, and VDA 5050 between robots and fleet control. A fleet manager that supports both connects the two layers.

Can a robot support both ISO 21423 and VDA 5050?

Yes. If a robot already supports VDA 5050, adding ISO 21423 support takes a bit more effort for the vendor. One caveat: VDA 5050 assumes that fleet control has exclusive control of the robot, while ISO 21423 lets any participant send commands. So while the robot works for a VDA 5050 fleet manager, it has to ignore ISO 21423 commands, or it may get instructions that conflict with the fleet manager's orders. From a fleet management system perspective, if the robot supports both standards, VDA5050 enables fleet-wide optimization of traffic management and scheduling.

Does ISO 21423 include traffic management?

Not as a defined function. ISO 21423 lets robots announce their routes and every participant can read them, but it defines no rules for resolving conflicts between routes and no role responsible for doing so. VDA 5050 does not prescribe traffic algorithms or define a traffic manager role either, but it gives a central fleet control the mechanisms to manage traffic, such as step-by-step path release, zones and planned-path sharing.

Is VDA 5050 only for AGVs?

No. Allowed deviation and curved NURBS paths have been available since 1.0. Version 2.1 added corridors, and version 3.0 covers any type of mobile robot, with zones in which robots plan their own routes inside rules set by the operator.

Is VDA 5050 only a German standard?

No. It was published by the German associations VDA and VDMA, is written in English and is developed openly on GitHub. North American robot makers such as OTTO Motors, Seegrid and MiR have certified models or added VDA 5050 support.

Is a central fleet manager a form of vendor lock-in?

Not when it speaks open protocols. A central DHCP server on a network is not lock-in, because the server can be replaced and any device can connect. The same holds for a central fleet control that uses an open standard such as VDA 5050.

Is ISO 21423 a safety standard?

No. ISO 21423 explicitly excludes safety and navigation. Mobile robot safety is still addressed through safety standards such as ISO 3691-4, the ANSI/RIA R15.08 series and application-specific risk assessments. The same applies to VDA 5050.

What do I need to run a robot that supports ISO 21423?

A fleet manager that speaks ISO 21423 to the robot. In the layered setup there are two ways to get there. Either the fleet manager offers an ISO 21423 robot interface, or the robot supports VDA 5050 as well, so the fleet manager keeps its established VDA 5050 connection.

Using ISO 21423 and VDA 5050 together

ISO 21423 will show up in specifications, and that helps everyone who wants open protocols on the shop floor. It does not yet settle how equipment from different vendors describes its state, or who decides when two robots want the same aisle. VDA 5050 settles both for mobile robots and leaves the rest of the floor to the fleet manager. A plant that uses each standard where it is strongest gets more choice in robots and equipment, and fewer interfaces built for one project only.

‍

‍