Choosing an Autonomous Mobile Robot vendor, otherwise known as an AMR vendor is one of the most consequential decisions a warehouse or logistics operation can make. The right partner accelerates throughput, reduces labor strain, and scales with your business. The wrong one leaves you with costly hardware, integration headaches, and a support team that disappears after go-live.
The AMR market has matured quickly, and so has the sales playbook vendors use to win business. Polished demos, impressive ROI calculators, and enthusiastic reference calls are standard. What separates a genuinely strong deployment from a disappointing one usually comes down to the questions buyers asked before signing the contract. Here is a thorough guide to those questions.
Does The System Scale With Your Operation?
Start with growth in mind, not just your immediate needs. Ask vendors how their fleet management software performs as robot counts increase, and request benchmark data from deployments comparable in size to your three-year growth plan, not just your day-one rollout. Some platforms handle 20 robots gracefully but begin to show latency, routing conflicts, or dashboard instability at 100. You need to know where those thresholds are before you are locked in.
It is also worth asking how the vendor handles multi-site deployments. If you plan to roll out across several facilities, understand whether a single software instance can manage robots across locations, how data is segmented, and whether learnings from one site can be applied to another. Scalability is not only about robot count. It is about whether the whole system grows with you without requiring a costly reimplementation every time you expand.
How Does It Integrate With Your Existing Systems?
AMRs do not operate in isolation. They need to receive tasks from, and report back to, whatever warehouse management system, ERP, or order management platform you already run. Ask whether the AMR vendor offers a documented, standards-based API or whether integration depends on proprietary middleware that creates long-term lock-in.
Support for open standards like VDA 5050 is a good sign. It suggests the vendor is building toward interoperability rather than dependency. Find out exactly how the system synchronizes with your WMS in real time, how task prioritization works when order volumes spike, and critically, what happens to operations if cloud connectivity is lost. A system that halts entirely during a network outage is a serious operational risk, particularly for facilities running around the clock. Ask specifically about edge computing capabilities and local fallback modes that keep robots moving even when the connection to a central server is disrupted.
What Navigation Technology Does It Use & How Reliable Is It In Your Environment?
Not all navigation approaches are equal, and the differences matter enormously depending on your facility type. Natural feature navigation, commonly called SLAM, is generally more adaptable than older methods that rely on QR codes, reflective targets, or magnetic tape embedded in the floor. But even among SLAM-based systems, performance varies widely across vendors.
Push for a live demonstration in a facility similar to yours, with real traffic, seasonal product changes, and dynamic racking configurations. Ask how long initial site mapping takes, how often remapping is required as your facility evolves, and how the robot reacts to blocked aisles, fallen product, or unfamiliar obstacles. A robot that simply stops and waits for human intervention every time it encounters something unexpected will create as many problems as it solves. Request incident logs and resolution data from active deployments, not just curated marketing materials, and pay attention to how the system escalates issues to human operators when it cannot resolve them autonomously.
What Does The Hardware Actually Look Like Over Time?
It is easy to focus on software and integration during vendor evaluation and overlook the physical reality of running a robot fleet day in and day out. Ask vendors for the mean time between failures for their current production units, and make sure those numbers come from live high-volume deployments rather than internal testing environments.
Battery life and replacement cycles deserve close attention. Understand how long a charge lasts under your expected workload, how charging is managed during shifts, and what the process and cost of battery replacement looks like over a five-year period. Ask about wear components such as drive motors, wheels, and sensors, and find out whether your maintenance team can perform routine servicing on-site or whether repairs require the robot to be sent back to the vendor. The answers will shape both your operational planning and your long-term cost projections.
What Does AMR Vendor Support Actually Look Like After Go-Live?
This is where many AMR deployments run into trouble. An AMR vendor often invests heavily in implementation resources and then thin out the support team once the contract is signed and the robots are running. Getting specific about post-launch support before you sign is essential.
Ask for the guaranteed response times for critical outages in writing, and distinguish between software support and hardware support. A four-hour remote response SLA for a software issue is very different from a four-hour on-site response for a robot that is physically down on a busy dock floor. Find out where spare parts are warehoused and what the typical lead time for critical components looks like. Ask whether you can hold safety stock under a contract arrangement to reduce downtime risk.
Perhaps most importantly, ask who your named point of contact will be at 6, 12, and 24 months into the deployment. Customer success structures change. The team that onboarded you may not be the team supporting you a year later. These commitments should be in the contract, not a verbal assurance during a sales call.
What Is The True Total Cost Of Ownership?
Sticker price comparisons between vendors are almost meaningless without a full picture of total cost of ownership. A low upfront hardware price can be more than offset by annual software licensing fees, mandatory maintenance contracts, integration services, and consumable costs like batteries and wear parts.
Ask for a fully itemized five-year TCO projection and compare it across vendors line by line. If the vendor offers a robots-as-a-service model, run that comparison too. RaaS structures can lower capital expenditure but may cost more over time depending on your volume and contract terms. Make sure you understand what happens contractually if your business needs change: if you need to scale the fleet down after a slow season, relocate equipment to a different facility, or choose not to renew a software subscription at the end of the term. Flexibility in commercial terms is worth paying for.
Is The AMR Vendor Financially Stable & Committed For The Long Term?
The AMR market has grown fast, attracted significant investment, and already seen its share of consolidations, pivots, and shutdowns. Choosing a vendor that goes out of business two years into your deployment leaves you with orphaned hardware, no software updates, and no support path. That is not a hypothetical risk. It has happened to buyers who did not ask the right questions early enough.
Ask directly about the vendor’s funding status, revenue trajectory, and path to profitability. A vendor that deflects these questions or responds only with vague reassurances is worth scrutinizing further. Also ask for a 12 to 18-month product roadmap and verify how well past roadmap commitments have been delivered. Do not rely solely on the vendor’s own account. Check independent review platforms, industry forums, and LinkedIn for unfiltered perspectives from operators who have been running the system for a year or more.
Are Performance Guarantees Written Into The AMR Vendor Contract?
Every vendor will promise strong uptime, fast throughput, and high pick accuracy during the sales process. The question is whether those commitments appear as enforceable terms in the contract, with defined remedies if benchmarks are not met.
Uptime guarantees, throughput rates, and accuracy targets should be specified clearly, measured in an agreed-upon way, and tied to concrete consequences if they fall short. Service credits, contract extensions, or remediation obligations are all reasonable remedies to negotiate. If a vendor is reluctant to put performance commitments in writing, that reluctance tells you something important about their confidence in their own product and their willingness to be held accountable.
How Will Your Team Be Trained & Supported Through The Transition?
AMR deployments are as much a people change as a technology change. Ask vendors what their implementation and training program looks like for your floor staff, supervisors, and IT team. Find out how long the typical onboarding period takes, what resources are provided for ongoing training as staff turns over, and whether there is a train-the-trainer model that lets you build internal expertise rather than depending on the vendor for every new hire.
Change management is often underestimated in automation projects. Workers who understand how the robots work alongside them, rather than feeling replaced by them, tend to adopt new workflows faster and surface operational issues sooner. A vendor with a thoughtful onboarding process is more likely to have a track record of successful deployments.
Final Thought
The AMR vendor that is worth trusting are the ones who welcome hard questions and answer them with data rather than enthusiasm. Ask to speak with a customer who went through a difficult deployment or a major software upgrade, not just a showcase success story. Request an unescorted visit to a reference site where you can talk directly with the people operating the system every day. Run a structured pilot under real conditions before committing to a full rollout.
The due diligence you do before signing an AMR vendor will shape every day of the deployment that follows. Take the time to get it right.
