← Insights

How to compare AMR vendors

A structured evaluation framework covering technical capability, fleet management, integration approach, commercial terms, and reference quality for Autonomous Mobile Robot procurement.

9 min read · Vendor-agnostic


Why AMR comparison is harder than it looks

On the surface, AMR vendors look similar: robots that navigate autonomously, carry payloads between locations, and integrate with WMS. The performance differences between vendors become clear only when you look at fleet management software, exception handling, WMS integration depth, and long-term vendor stability.

Marketing specifications are not sufficient for a structured comparison. Payload ratings, speed, and navigation technology are relatively easy to compare. The harder evaluation is fleet software maturity, integration flexibility, and what happens when things go wrong.

Agilox.com is independent and vendor-neutral

This evaluation framework does not recommend specific AMR vendors. It provides the criteria and questions you need to run a structured, buyer-led evaluation. Apply these criteria equally to all vendors under consideration.

Technical evaluation framework

Evaluate technical capability across six dimensions. Request documented specifications and, where possible, verify against reference site performance.

Payload and form factor

Rated payload capacity and actual tested payload under operating conditions. Robot dimensions and turning radius relative to your aisle widths and operating environment. Shelf or load compatibility with your existing carrier formats.

Navigation technology

LIDAR-based, camera-based, or hybrid navigation. Map creation process and time. Map update procedure when layout changes. Performance in dynamic environments with pedestrians and variable obstacles.

Fleet management software

Task assignment logic: how does the fleet management system allocate tasks to robots? Traffic management in congested areas. Multi-floor support if relevant. Reporting and analytics capability. Software update frequency and process.

WMS integration

API documentation quality and completeness. Native connectors to your WMS (if applicable). Task confirmation and exception reporting back to WMS. Real-time versus batch integration model. Integration project timeline from reference implementations.

Charging and battery management

Battery technology and expected degradation over time. Autonomous charging: does the robot return to charge automatically? Charging time and whether charging interrupts operations. Battery replacement cost and frequency at year 3-5.

Safety certification

CE marking and relevant safety standards compliance. Safety scanner coverage and stopping distance at operating speed. Human detection sensitivity and false positive rate. Track record of safety incidents at reference sites.

Commercial evaluation framework

Technical capability alone does not determine value. Evaluate the commercial structure carefully, particularly support terms, software licensing, and exit provisions.

Pricing model

Hardware purchase versus robot-as-a-service (RaaS) versus lease models. Total cost of ownership over 5 years under each model. What is included in the base price and what is charged separately? Is pricing per robot, per shift, or per task completed?

Maintenance and support

What is the SLA for response time and resolution time? Is maintenance included or charged separately? Who holds spare parts stock and where? What is the procedure for a fleet-wide software fault? On-site support availability in your region.

Scalability terms

What is the pricing for additional robots beyond the initial fleet? Can you add robots from a different model generation to an existing fleet? What is the lead time for fleet expansion after ordering?

Software licence terms

Is fleet management software licensed per robot, per site, or per enterprise? What happens to the licence if robots are decommissioned? Are future software updates included or charged separately? What is the end-of-life policy for the current platform version?

Exit provisions

If you need to exit the relationship (RaaS model), what are the notice periods and exit costs? Can you transfer robots to a different site? What data portability rights do you have over operational data generated by the fleet?

Questions to ask reference sites

Vendor-provided references are selected to give favourable impressions. Ask specific operational questions rather than open-ended satisfaction questions. Speak to the operations manager, not just the project manager.

  • What throughput are you achieving versus what was promised at sale?
  • How long did WMS integration actually take versus the vendor timeline?
  • What is your actual system uptime percentage, and what causes the downtime?
  • How often do you need to remap due to layout changes or environmental changes?
  • What exception rate are you experiencing, and what are the most common causes?
  • How responsive is vendor support when you have an issue?
  • If you were starting again, what would you do differently?
  • Has the fleet management software received meaningful updates since you went live?
  • What did integration cost, including your internal time?
  • Would you buy from this vendor again?

Request at least two reference sites with similar operational profiles to yours. A reference in a different industry or with a different WMS is less useful than one in your sector.

Red flags during AMR evaluation

No WMS integration references in your sector

If the vendor cannot provide a reference site using the same or a comparable WMS, integration risk is higher. Generic API claims without demonstrated experience in your environment are not sufficient.

Throughput claims without conditions

Any throughput figure quoted without specifying load, environment, aisle width, and WMS latency is a marketing figure, not an engineering specification. Require conditions to be documented.

Proprietary data lock-in

If operational data generated by the fleet is not exportable or accessible through standard APIs, you lose the ability to analyse performance independently or switch vendors in future.

Unclear software update commitments

Fleet management software is the long-term value of an AMR system. If the vendor cannot commit to a software roadmap and update frequency, platform obsolescence risk is high.

Pressure to commit before pilot

Legitimate AMR vendors support structured evaluation and are comfortable with pilots before full fleet commitment. Pressure to commit to a full fleet before a structured pilot is a significant commercial warning sign.

Building the comparison scorecard

A structured scorecard allows you to compare vendors on the same criteria, weight each dimension according to your priorities, and document the evaluation rationale for internal review.

CategoryIndicative weight
Technical capability (payload, navigation, safety)25%
Fleet management software quality20%
WMS integration depth and track record20%
Commercial terms and total cost of ownership15%
Support model and SLA quality10%
Vendor stability and platform investment10%

Adjust weights to reflect your priorities. An operation with complex WMS requirements should weight integration more heavily.

Compare vendors in your workspace

Build a structured AMR vendor shortlist using your operational profile, technology fit assessment, and evaluation criteria.

Start Free Assessment