Warehouse Robotics and Automation Software: AMRs, ROS 2 and Integration for SMEs

ApexlyTech Team 8 min read
Warehouse Robotics and Automation Software: AMRs, ROS 2 and Integration for SMEs

TL;DR: For small and mid-sized operations, the main choice is between fixed automation (conveyors, sorters, automated storage) that is fast and predictable but hard to change, and autonomous mobile robots (AMRs) that navigate freely and can be added or re-routed with software. Whichever you choose, most of the work is software: fleet management, traffic rules, and integration with your warehouse management system (WMS) and ERP so robots receive real tasks and report real outcomes. ROS 2 is the common open-source foundation for robot software, Open-RMF and VDA 5050 address multi-fleet coordination, and safety is governed by standards such as ISO 3691-4 for driverless industrial trucks and ISO 10218 for industrial robots. Build the business case from your own measured process data, not vendor averages.

Fixed automation vs mobile robots

Automation in a warehouse or light manufacturing site falls into two broad families.

Fixed automation

Conveyors, sortation systems, automated storage and retrieval, palletisers and robot arms in fixed cells. These are engineered for a specific flow and are very good at it: high, consistent throughput with little variation. The trade-off is flexibility. Changing the layout, the product mix or the process usually means physical rework, and the investment is tied to a building and a flow you expect to keep for years.

Automated guided vehicles and AMRs

Automated guided vehicles (AGVs) traditionally follow fixed paths defined by tape, magnets or reflectors. Autonomous mobile robots (AMRs) build a map of the site and plan their own routes, avoiding obstacles as they go. Both carry goods between points: totes to packing, pallets to docks, parts to lines. Their strength is that the system can be reconfigured in software and scaled one robot at a time. Their limits are the floor (ramps, uneven surfaces, narrow aisles), mixed traffic with people and forklifts, and the fact that throughput depends on traffic management as much as on robot speed.

A simple decision lens

QuestionLeans towards fixed automationLeans towards AMRs
How stable is the process?Stable for yearsChanging with seasons, customers or products
Throughput profileHigh and steadyVariable, with peaks
BuildingOwned or long lease, layout can be committedLeased, shared or likely to change
Investment styleLarger up-front projectIncremental, robot by robot
People in the areaCan be separated by guardingShared space must be designed for

Many sites end up with a mix: fixed automation where flow is predictable, mobile robots to connect the islands.

The software stack behind robots

ROS 2

The Robot Operating System is, in its own words, a set of software libraries and tools that help you build robot applications. ROS 2 is the current generation and the foundation used by many robot makers and research groups for drivers, perception, navigation and simulation. Distributions are released annually in May; releases in even-numbered years are long-term support (LTS) releases supported for five years. Jazzy Jalisco (May 2024) is supported until May 2029, and Lyrical Luth (May 2026) until May 2031. For production work, build on an LTS release and plan your upgrades around its end-of-life date.

On top of ROS 2, Nav2 (the ROS 2 Navigation Framework and System) provides mapping, localisation, path planning and behaviour control for mobile robots. If you are building or customising a robot rather than buying a finished product, Nav2 is the usual starting point.

Fleet management

One robot is a gadget; twenty robots are a traffic system. Fleet management software assigns tasks, decides which robot takes which job, manages charging, prevents deadlocks at intersections and narrow aisles, and reports status. Every AMR vendor ships its own fleet manager. The problem starts when you have more than one vendor, or when robots must use shared infrastructure such as doors and lifts.

Two open efforts address that:

  • Open-RMF describes itself as a free, open-source, modular software system, "a common language for robot interoperability". It coordinates fleets from different vendors and connects them to building infrastructure like doors and lifts.
  • VDA 5050, developed by the German automotive and machinery associations VDA and VDMA with KIT's Institute for Material Handling and Logistics, is an open standard for communication between mobile robot fleets and a central fleet control. Its specification and JSON schemas are published openly on GitHub. Asking vendors whether they support it is a reasonable way to reduce lock-in.

Integration with WMS and ERP

Robots create value only when they are driven by real work. The integration layer is where most projects succeed or stall:

  • Tasks in: the WMS or ERP decides what needs moving (a pick wave, a replenishment, a finished pallet) and passes tasks to the fleet manager, usually through an API or message queue.
  • Events out: the fleet manager reports pickups, drop-offs, failures and timings back, so inventory locations and order status stay correct.
  • Exceptions: blocked aisles, missing totes, robots needing help. Someone has to see them and act, so design the alerting and the screens for the people on the floor.
  • Master data: locations, stations and load types need consistent identifiers across WMS, fleet manager and maps.

Treat this like any other systems integration project: agree message formats, define idempotent operations (a task sent twice must not create two moves), log everything, and test with realistic volumes before go-live. If your WMS cannot expose the events you need, a thin middleware service is usually cheaper than customising it. We cover the IoT side of this plumbing in our guide to industrial IoT architecture, and simulation before go-live in our guide to digital twins.

Safety standards: an overview

This is an orientation, not compliance advice. Standards are purchased documents, and requirements depend on your jurisdiction, so involve a qualified safety engineer and your integrator.

  • ISO 3691-4:2023 sets safety requirements and verification methods for driverless industrial trucks and their systems, which explicitly includes AGVs, AMRs and tunnel tuggers. It also addresses the operating zone: the standard notes that the condition of the operating zone strongly affects safe operation and specifies how to prepare it. Your site is part of the safety case, not just the robot.
  • ANSI/A3 R15.08 is the US standard series for industrial mobile robots: Part 1 covers the robot, Part 2 covers systems and applications for integrators, and Part 3 covers safe use by end users.
  • ISO 10218-1 and ISO 10218-2 cover industrial robots and robot applications and cells respectively. Both were revised in 2025. Part 2 covers integration, commissioning, operation, maintenance and decommissioning of robot cells.
  • ISO/TS 15066 gives guidance on collaborative robot applications, where people and robots share a workspace. Check how its content relates to the 2025 edition of ISO 10218 for new projects.

Practical consequences for planning: risk assessment is iterative and starts at layout design; marking, floor condition, lighting and pedestrian routes matter; and changing the site later (racking, doors, traffic) can mean revisiting the assessment.

Thinking about ROI without invented numbers

Vendor brochures quote impressive averages. Your return depends on your own process, so build the case from your own data:

  1. Measure the current process. How much walking and transport time per order, per shift? How many touches per item? What are error rates and their cost? Time studies over a few representative days are worth more than any industry benchmark.
  2. Identify the bottleneck. If packing is the constraint, faster transport to packing does not increase output. Automate the constraint, or the step that feeds it.
  3. Model peaks, not averages. Many sites justify automation on peak capacity they currently cover with temporary labour or overtime.
  4. Count all the costs. Robots or equipment, software licences, integration work, site changes, training, maintenance contracts, spare parts, and the internal time to run the project.
  5. Count the risks. Downtime while you switch over, vendor dependence, and what happens if volumes change.
  6. Pilot with a measurable scope. One flow, one area, a defined success metric agreed before the start.

Soft benefits such as fewer injuries from manual handling, easier recruitment and better traceability are real but should be stated as such, not converted into imaginary money.

Where software teams add the most value

  • Integration services between WMS/ERP and fleet managers, including retries, idempotency and monitoring.
  • Operator dashboards and mobile apps for exceptions, task status and KPIs.
  • Data pipelines that turn robot events into throughput, utilisation and bottleneck reports.
  • Simulation of layouts and fleet sizes before buying hardware.
  • Custom behaviours on ROS 2 when an off-the-shelf robot needs to do something specific.

How ApexlyTech can help

We build the software that makes robots useful in a real operation: WMS and ERP integration, fleet-level dashboards, exception handling apps and analytics, and ROS 2 development where a custom behaviour is needed. See our robotics and automation and custom software services, or contact us to scope a pilot.

Frequently asked questions

What is the difference between an AGV and an AMR?

AGVs traditionally follow fixed, predefined paths such as tape or magnetic strips. AMRs build a map and plan their own routes, navigating around obstacles. Both are covered by safety standards for driverless industrial trucks such as ISO 3691-4.

Is ROS 2 suitable for commercial robots?

Yes, it is widely used as a foundation for commercial robot software. For production, build on a long-term support distribution, such as Jazzy Jalisco (supported to May 2029) or Lyrical Luth (supported to May 2031), and plan upgrades before end-of-life.

Can robots from different vendors work in the same warehouse?

Yes, but it needs coordination. Open-RMF is an open-source system for multi-fleet interoperability, and VDA 5050 is an open standard interface between mobile robots and a central fleet control. Ask vendors which they support before you buy.

Which safety standards apply to warehouse robots?

Commonly ISO 3691-4 for driverless industrial trucks including AMRs, the ANSI/A3 R15.08 series for industrial mobile robots in the US, and ISO 10218 for industrial robot arms and cells. Which apply depends on the equipment and your jurisdiction, so involve a safety professional.

How do we estimate ROI for warehouse automation?

Measure your current process, find the real bottleneck, model peak demand, count every cost including integration and maintenance, and validate with a pilot that has an agreed success metric. Avoid relying on generic industry averages.

Sources