How to Choose an AMR or AGV: The 2026 Buyer's Guide

Most facilities buy the wrong mobile robot because they start from a demo video instead of a route. A vendor rolls a sleek unit across a clean showroom floor, it dodges a walking human, everyone nods, and a purchase order gets written for a fleet that then struggles with the real building: mixed traffic, dock doors that swing, pallets stacked half a meter into the aisle, a WMS that will not hand out tasks, and a night shift that props the fire doors open. The hard part is the route, the traffic, the integration, and the throughput math, and none of them show up in the demo.

The order that works starts with the move. What is being transported, from where to where, how many times an hour, through what kind of traffic, and against what labor cost you are trying to offset. That single description fixes almost everything downstream: the payload class, whether you need free navigation or a fixed guidepath, the safety rating, and the fleet-software problem you are really buying. A mobile robot is a payload platform, a navigation stack, a safety system, and a fleet manager that talks to your warehouse or manufacturing software. You buy all four together, and the last one decides whether the first three ever earn their keep.

This guide is the hub for the mobile-robot buying decision. It walks the AMR-versus-AGV split and when the simpler machine is the right call, segments buyers by what they actually do (intralogistics, line-side manufacturing, e-commerce fulfilment, hospitals), lays out the specs that decide a purchase with real ranges, gives you budget tiers and the throughput and ROI math, names the real vendors by category, and covers the integration and total-cost work that determines whether the project pays back. Throughout it points at the deeper mobile robots ultimate guide and the live industrial robotics leaderboard, where you can compare shipping platforms by payload, speed, and navigation instead of trusting a datasheet.

The take: Describe the move before you shop the robot. The transport task (payload, route, cycles per hour, traffic, labor offset) fixes your payload class and your navigation type, and those two fix the shortlist. Choose an AMR with free SLAM navigation when routes change, traffic is mixed, and you need flexibility; choose a simpler AGV on fixed guidepath when the route is permanent, high-volume, and predictable, because it costs less and rarely fails. Then treat the fleet manager and its WMS or MES integration as the real purchase, because a robot that cannot get tasks moves nothing. Prove the throughput and ROI on your actual cycle times, not the vendor's showroom lap.

Companion reading: mobile robots (AMR & AGV), SLAM & localization, robot safety & functional safety, how to choose a cobot, industrial automation (PLC/SCADA/fieldbus), and robot power & batteries.

Table of contents

1. Key takeaways
2. AMR vs AGV, and when the simpler machine wins
3. Start with the buyer segment
4. Payload classes and form factors
5. Navigation: SLAM, natural-feature, tape, QR
6. Safety scanners, ratings, and standards
7. Runtime, charging, and battery strategy
8. Fleet software, VDA 5050, and interoperability
9. Throughput and ROI math
10. Vendors and the ecosystem
11. Integration, deployment, and total cost
12. Buy, lease, or RaaS
13. Frequently asked questions
14. Changelog

AMR vs AGV, and when the simpler machine wins

The whole market splits on how the robot knows where to go. An AGV (Automated Guided Vehicle) follows a fixed guidepath laid into or onto the floor: magnetic tape, an inductive wire, optical stripes, or a grid of QR codes. It runs a route someone defined, and if a pallet blocks that route it stops and waits rather than going around. An AMR (Autonomous Mobile Robot) builds and holds a map of the building with onboard sensors, localizes itself against that map in real time, and plans its own path, so it can route around an obstacle, take a different aisle, and be redeployed to a new task by editing software rather than relaying tape.

The instinct in 2026 is to assume the AMR is simply the better machine and the AGV is the legacy option. That instinct costs money. The AGV wins whenever the route is permanent, the volume is high, and the environment is predictable, because a guidepath machine is mechanically simpler, cheaper per unit, and far less likely to get confused. A tugger running the same loop between two fixed stations 200 times a shift, in a lane with no foot traffic, does not need a SLAM stack and the compute and sensing it demands. It needs to be reliable and cheap, and tape delivers that.

The AMR earns its premium where the AGV struggles: routes that change with the season or the product mix, buildings shared with people and forklifts, and operations where you cannot shut an aisle to lay guidepath. Flexibility is the thing you are paying for, and if your operation does not need flexibility you are paying for nothing. Many real deployments are hybrids: AMRs for the variable last-100-meters of picking and delivery, AGVs or conveyor for the fixed high-volume trunk lines.

	AGV (fixed guidepath)	AMR (free navigation)
How it navigates	Tape, wire, optical, or QR grid	Onboard SLAM against a building map
Obstacle in path	Stops and waits	Re-plans around it
Route change	Re-lay guidepath	Edit software
Unit cost	Lower	Higher
Best when	Permanent, high-volume, predictable route	Changing routes, mixed traffic, flexible tasking
Infrastructure	Floor markings/wire	None (map only)
Failure mode	Loses the line	Loses localization in featureless space

Rule of thumb: If you could describe the route to a new hire as "always this exact loop, no exceptions," an AGV is probably the cheaper right answer. If the honest description is "it depends on the day," you are buying an AMR and paying for the navigation that lets it decide.

Start with the buyer segment

Four segments cover most mobile-robot purchases, and each one weights the specs differently. Find yours, then let it tell you what to prioritize.

Segment	The move	What dominates the choice	Typical payload
Warehouse / intralogistics	Totes and pallets across a DC	Fleet software, throughput, safety in mixed traffic	100 kg to 1,500 kg
Manufacturing line-side	Kits and parts to workstations	Precise docking, MES integration, uptime	100 kg to 1,000 kg
E-commerce fulfilment	Goods-to-person picking	Fleet density, cycle time, WMS integration	5 kg to 600 kg
Hospitals	Meals, linens, waste, pharmacy	Elevator/door integration, safety around patients	50 kg to 500 kg

Warehouse and intralogistics. The general-purpose case: moving totes, carts, and pallets between receiving, storage, and shipping. The route mix is broad and traffic is mixed with humans and forklifts, so safety rating and the fleet manager's traffic control do most of the deciding. Payload spans the whole range because one facility may want tote carriers for replenishment and pallet movers for the dock. This segment lives on the industrial robotics leaderboard, where the general-purpose platforms cluster.

Manufacturing line-side. Delivering kits, components, and work-in-progress to fixed workstations on a takt clock. Here precise docking (parking within a few millimeters at a station so a conveyor or arm can hand off) and integration with the MES or line controller matter more than raw speed. Uptime is sacred because a stalled robot can starve a line. Fixed, repeating routes make this a segment where a well-chosen AGV or a lightly-mapped AMR both fit.

E-commerce fulfilment. The goods-to-person model, where fleets of low, flat robots either carry mobile shelving racks to a picker or shuttle totes through a dense picking area. The economics live in fleet density (robots per square meter) and cycle time, and the WMS integration decides whether the picker ever waits. This is the highest-robot-count segment and the one most often bought as a whole system rather than by the unit.

Hospitals. Autonomous delivery of meals, linens, medications, and waste through corridors shared with patients, staff, and beds. The defining integrations are elevators and automatic doors (the robot must call and ride an elevator and open a door), and the defining constraint is safety and gentleness around vulnerable people. Payloads are modest but the environment is the most human-dense of any segment, so conservative speed and certified safety dominate.

War story: A distribution center bought a fleet sized on the vendor's quoted throughput, measured on a straight 40-meter run with no traffic. In the real building the robots crossed two forklift aisles where they slowed to a crawl for safety and queued at a single charging spur. Realized throughput came in near 55% of the quote, and the project needed a third more robots to hit the plan. The specs were honest; the test conditions were not the building.

Payload classes and form factors

Payload is the first hard fork because it changes the machine, the safety story, and the floor requirements. Three broad classes cover most of the market.

Tote, bin, and light-load carriers (5 to 100 kg). Small, low robots that carry totes or small parts, often with a top module (a conveyor, a shelf, or a lift) matched to the task. These are the e-commerce and light-manufacturing workhorses, cheap per unit and deployed in numbers. Speeds run 1 to 2 m/s and footprints are small enough to work dense picking aisles.

Cart tuggers and cart movers (500 to 1,500 kg of towed load). Robots that hook to or slip under wheeled carts and tow a train of them, or lift a single cart from below. The robot itself is modest but the towed mass is large, which changes braking distance and the safety envelope. This is a favorite for line-side milk-run replenishment because it reuses existing carts.

Pallet and unit-load movers (600 to 1,500 kg-plus). Robots that carry a pallet or a heavy unit load, either as a low platform the pallet sits on or as a robotic forklift that picks a pallet from the floor or a rack. These are the heaviest, most safety-critical machines, subject to the driverless-truck standard, and they demand good floor flatness and clear aisles. Robotic forklift AMRs that reach into racking sit at the top of this class and the top of the price range.

Class	Payload	Speed (typical)	Form factor	Best for
Tote / light-load	5 to 100 kg	1.0 to 2.0 m/s	Low deck, top module	E-commerce picking, light kitting
Cart tugger / mover	500 to 1,500 kg towed	1.0 to 2.0 m/s	Tow hitch or under-cart lift	Line-side milk runs, replenishment
Pallet / unit-load	600 to 1,500 kg+	1.0 to 1.5 m/s	Platform or robotic forklift	DC pallet moves, dock work

Rule of thumb: Size the payload for the loaded, worst-case unit, not the average. A robot rated for 1,000 kg that carries a 1,050 kg pallet on a bad day is a safety event, and derating for slopes and dynamic loads is real. Buy the class above your peak, not your mean.

Navigation: SLAM, natural-feature, tape, QR

Navigation is where AMR and AGV part ways, and it is worth understanding the flavors because they trade cost against flexibility.

SLAM (simultaneous localization and mapping). The AMR builds a map with lidar and/or cameras and localizes against it in real time, planning its own path. This is the most flexible option and the one that copes with mixed traffic and changing layouts. Its weakness is featureless environments (long blank corridors, empty warehouses, big open floors) where there is little for the scan to lock onto, which is where localization can drift. The full mechanics are in the SLAM and localization guide.

Natural-feature / reflector navigation. A middle path used by many AGVs and some AMRs: the robot navigates against fixed features, either the natural geometry of the building or a sparse set of reflective markers placed on walls and columns. Reflector navigation is very precise and repeatable, which is why it dominates high-accuracy AGV docking, at the cost of installing and maintaining the markers.

Magnetic tape or inductive wire. The classic AGV guidepath. Tape sticks to the floor and is cheap to lay and move; wire is cut into the floor and is permanent and robust. Both are simple, reliable, and cheap, and both mean the route is physical, so changing it is a floor job. Tape also wears and gets damaged by forklift traffic, which is a maintenance line item.

QR-code / grid navigation. A dense grid of QR or 2D codes on the floor that the robot reads with a downward camera to know exactly where it is. This is the dominant scheme for goods-to-person fulfilment fleets, because it gives very precise, very repeatable positioning at high density, and the grid is cheaper to install than it looks. The tradeoff is that the robots live on the grid; they are not free-roaming.

Method	Flexibility	Precision	Infrastructure	Typical use
SLAM	Highest	Good	None (map)	AMRs in mixed, changing space
Natural-feature / reflector	Medium	Very high	Markers	High-accuracy AGV docking
Magnetic tape / wire	Low	High on-path	Floor markings	Fixed-route AGVs
QR / grid	Low (on grid)	Very high	Code grid	Goods-to-person fulfilment

Rule of thumb: Do not pay for SLAM to run a route that never changes, and do not lay tape for a route that changes every week. Match the navigation to how often the route moves, and be honest about how featureless your building really is, because a blank 80-meter aisle is the classic SLAM trap.

Safety scanners, ratings, and standards

Safety is where a mobile-robot purchase stops being a productivity decision and becomes a compliance one, because these machines share floors with people. The specs here are not optional features; they are the difference between a legal deployment and a liability.

Safety-rated laser scanners. The core sensor is a safety-rated 2D laser scanner (often two, at diagonal corners, for 360-degree coverage) that defines protective fields around the robot. When a person enters the inner field the robot performs a safety stop; the outer field triggers a slowdown. "Safety-rated" is the load-bearing phrase: a scanner certified to the relevant performance level is a different, more expensive component than a navigation lidar, and only the certified one counts toward compliance. Many robots carry both, one for navigation and one for safety.

The standards. In practice you are looking for compliance with ISO 3691-4, the standard for driverless industrial trucks (the pallet and unit-load movers), and with the mobile-robot safety standard R15.08 in North America, which was written specifically for AMRs and their fleets. These standards cover the protective fields, the emergency-stop function, speed limits near people, and the safety of the whole fleet's behavior, extending beyond any single robot. The deeper treatment of performance levels, safety functions, and stop categories is in the robot safety and functional safety guide.

Speed, mass, and stopping distance. A heavier, faster robot needs a larger protective field because it takes longer to stop, and the protective field eats aisle width and slows throughput. This is a real design tension: the safest configuration is often the slowest. Do not let a vendor quote you throughput at a speed the safety scanners will throttle in a human-shared aisle.

Emergency stop and manual recovery. Every robot needs accessible emergency-stop buttons and a defined way for a human to safely move or recover a stalled unit without stepping into a hazard. In a fleet, the fleet manager must be able to halt everything at once.

Safety rule: Never accept "obstacle avoidance" or "collision detection" as a substitute for a safety-rated scanner and a certified stop function. Navigation sensing keeps the robot from bumping shelves; the safety system keeps it from hurting a person, and only the certified safety system carries legal weight. Confirm the safety rating and the applicable standard (ISO 3691-4 or R15.08) in writing before you buy, and have your own safety engineer sign the risk assessment.

Runtime, charging, and battery strategy

A mobile robot that is charging is not working, so the power strategy directly sets your effective fleet size. Three approaches exist, and the right one depends on duty cycle.

Opportunity charging. The modern default for AMRs. Lithium packs (LFP is common for its cycle life and safety) plus contact or wireless charging points at natural idle spots (pick stations, staging areas) let the robot take a 30-to-60-second top-up every time it pauses. The fleet manager schedules these so the robots sip power continuously and rarely need a full charge, keeping a fleet running close to 24/7 with no battery room and no swap labor. This is the right answer for most buyers.

Full charge cycles. The robot runs until low, then parks at a charger for a longer session (often 30 to 90 minutes). Simple and cheap, but it means you size the fleet with spare robots to cover the ones on charge, which is a real cost. Fine for lower-duty operations.

Battery swapping. A human or an automated station swaps a depleted pack for a charged one in a minute or two. This keeps the heaviest, highest-duty AGVs running near-continuously, but it needs a stock of spare packs, a swap area, and either labor or a swap station. Reserve it for the demanding cases where opportunity charging cannot keep up.

Strategy	Downtime	Extra fleet needed	Infrastructure	Best for
Opportunity charging	Near zero	Minimal	Charge points at idle spots	Most AMR fleets
Full charge cycles	Moderate	Spare robots	Charger stalls	Lower-duty operations
Battery swapping	Near zero	Spare packs	Swap area / station	Heavy, high-duty AGVs

Rule of thumb: Design opportunity-charging points into the route where robots already pause, and the charging problem mostly disappears. If your plan needs a dedicated charging aisle that robots queue for, you have under-provisioned charge points and will discover it as lost throughput. Battery chemistry and sizing detail live in the robot power and batteries guide.

Fleet software, VDA 5050, and interoperability

One robot is a science project. Value comes from a fleet, and a fleet is a traffic-managed system coordinated by fleet-manager software that assigns tasks, routes robots around each other, manages charging, and talks to your warehouse or manufacturing software. The fleet manager is the part of the purchase most buyers underweight and most regret underweighting.

What the fleet manager does. It receives work (a pick, a move, a delivery) from the WMS, MES, or an order system, decides which robot does it, plans a conflict-free path, resolves deadlocks when two robots want the same aisle, schedules charging so the fleet never runs flat, and reports status and exceptions. The quality of this software is what separates a fleet that flows from one that gridlocks at every intersection.

WMS and MES integration. The robots must receive tasks from and report to your existing systems. In a warehouse that is the WMS; on a line it is the MES or a PLC layer. This integration is the single biggest source of deployment delay, so ask precisely how the fleet manager connects to your specific WMS or MES: a supported connector, a REST API, or a custom integration project. The industrial automation guide covers the PLC and fieldbus side of that handshake.

VDA 5050. This is the interoperability standard that matters. VDA 5050 defines a common interface between a fleet manager and robots from different vendors, so a single master control can drive a mixed fleet rather than locking you to one brand's controller. If you expect to buy from more than one vendor over the life of the operation, or you want to avoid vendor lock-in, ask for VDA 5050 support by name and confirm how completely it is implemented, because coverage varies. It is the closest thing the industry has to a standard that protects your future buying freedom.

Rule of thumb: Score the fleet manager and its integration story as heavily as you score the robot. A mediocre robot on excellent fleet software beats an excellent robot on software that cannot get tasks from your WMS. Ask to see the fleet manager running a real mixed-traffic scenario, and ask whether it speaks VDA 5050.

Throughput and ROI math

A mobile-robot project justifies itself on throughput and labor offset against total cost. The math is not hard, but it has to run on your real numbers rather than the vendor's showroom lap.

Throughput. Effective throughput is deliveries per hour, and it derates hard from the ideal. Start from the cycle: travel time each way plus load and unload time plus queueing and charging overhead. A robot doing a 60-meter round trip at an effective 1.2 m/s (after the safety slowdowns) with 30 seconds of handling each end runs a cycle of roughly 2.5 to 3.5 minutes, so 17 to 24 moves an hour, and traffic congestion pulls that down further as the fleet grows. Model the real route with its real slowdowns, not a straight-line sprint.

Labor offset. The savings come from redeploying the people who used to walk those routes or drive those forklifts. Count the shifts you actually eliminate or redeploy, priced at fully-loaded labor cost (wage plus benefits plus overhead), and be honest that partial offsets (freeing 0.6 of a person per shift) only pay when you can actually reassign the fraction.

Total cost. Against the savings, price the whole program: the robots, chargers, the fleet-software license or subscription, the integration project, any safety and floor work, training, and ongoing support. A rough 2026 shape for a mid-size AMR fleet lands payback in the 1.5-to-3-year range for a two- or three-shift operation with real labor to offset, and much longer for a single-shift operation where the robots idle two-thirds of the day.

Input	How to estimate	Common mistake
Deliveries/hour	Real cycle time with safety slowdowns and queueing	Using straight-line speed
Labor offset	Fully-loaded cost of shifts actually redeployed	Counting fractional people you cannot reassign
Utilization	Moves per robot per shift across all shifts	Modeling one busy shift as if it were three
Total cost	Robots + chargers + software + integration + support	Pricing only the sticker

War story: A single-shift facility bought a fleet on a payback model built for three shifts. The robots did real work for eight hours and sat idle for sixteen, so the labor offset was a third of the model and payback stretched past five years. The same fleet in a three-shift building would have paid back in under two. Utilization across all your shifts is the number that makes or breaks the case.

Vendors and the ecosystem

The market has consolidated into recognizable categories, and knowing who plays where shortcuts the shortlist. Names below are representative of their category as of 2026, not an endorsement, and the market moves, so verify current products.

General-purpose intralogistics AMRs. MiR (Mobile Industrial Robots, part of the Teradyne group) and OTTO Motors (part of Rockwell Automation) are the reference names for payload-platform AMRs spanning light loads to heavy pallet movers, with mature fleet software and strong safety pedigrees. These are the default starting point for a mixed warehouse or line-side deployment.

Goods-to-person and fulfilment fleets. Locus Robotics (autonomous picking assistants that meet pickers in the aisle), Geek+ (rack-moving and shelf-to-person systems at large scale), and 6 River Systems (collaborative picking, now under Ocado) built the fulfilment-fleet category. These are usually bought as a whole system with the software and workflow, not as loose robots.

Broad automation and cart platforms. Zebra Technologies (which acquired Fetch Robotics) offers AMRs oriented to material transport and data-driven fulfilment. Vecna Robotics focuses on pallet trucks and tuggers with a strong fleet-orchestration story. Traditional forklift makers (Toyota, Jungheinrich, Hyster-Yale) also field automated and robotic trucks that plug into existing fleets.

Category	Representative vendors	Sweet spot
General-purpose AMR	MiR, OTTO Motors	Mixed warehouse and line-side transport
Goods-to-person fulfilment	Locus, Geek+, 6 River	High-volume e-commerce picking
Cart / pallet movers	Vecna, OTTO, forklift OEMs	Tuggers, pallet trucks, dock work
Broad automation	Zebra (Fetch)	Material transport, data-driven ops

The vendor question is really an ecosystem question: fleet-software quality, WMS/MES connectors, safety certification, VDA 5050 support, spare-parts availability, and a support and service footprint near your site. A cheaper robot from a vendor with no local service and no WMS connector is more expensive by the time it runs. Compare shipping platforms by payload, speed, and navigation on the industrial robotics leaderboard to build a shortlist grounded in real hardware.

Integration, deployment, and total cost

The robot arrives working; the deployment is the project. Budget for it honestly.

Mapping and commissioning. An AMR fleet must map your building and be tuned for its real traffic, slowdown zones, docking points, and charging spots. This is days to weeks of on-site work, and it is where a good integrator earns their fee. For AGVs, it is laying and testing guidepath, which is faster but more physical.

Software integration. Connecting the fleet manager to your WMS or MES is the long pole. A supported connector is a configuration job; a custom integration is a software project with its own timeline and risk. Pin down which one you are buying before you sign, because "we integrate with any WMS" often means "we can, for a fee, on a schedule."

Facility readiness. Floor flatness matters for heavy pallet movers, network coverage (Wi-Fi or private 5G) must reach every aisle the robots use, dock doors and elevators may need controls integration, and aisle widths must accommodate the robot plus its safety field plus passing traffic. These are real line items and real lead times.

People. Someone on site has to own the fleet: monitor it, clear the exceptions (a robot stuck behind a dropped pallet), and manage the maps as the building changes. A fleet with no internal owner degrades quietly as the layout drifts from the map.

Total cost of ownership. Over three to five years the program is the robots plus chargers plus the software subscription plus integration plus facility work plus training plus support and spares. The robots are often half or less of the total. Price the program, not the pallet of hardware.

Rule of thumb: Ask every vendor for a reference customer with a building like yours and call them. The question that matters is "what did deployment actually take and what broke," and the honest answers come from a peer operator who has lived it rather than a sales deck.

Buy, lease, or RaaS

Mobile robots are increasingly sold as a service, which changes the financial decision.

Buy (capital purchase). You own the robots and the software license, capitalize the cost, and carry the maintenance. This is cheapest over a long horizon for a stable, high-utilization operation, and it suits buyers with capital budget and internal robotics capability.

Lease. Conventional financing that spreads the capital cost over a term while you still operate and maintain the fleet. It smooths cash flow without changing the operating model.

RaaS (Robotics-as-a-Service). A subscription where you pay per robot per month (or per pick, or per move) and the provider handles hardware, software updates, and often maintenance and support. Typical figures land in the low-to-mid thousands of dollars per robot per month depending on class and duty, with little or no upfront capital. RaaS shines for seasonal operations (scale robots up for peak, down after), for buyers who want to avoid capital outlay and obsolescence risk, and for first deployments where you want to prove the case before committing capital. Over many years of steady use it usually costs more than owning, which is the tradeoff you pay for flexibility and offloaded risk.

Model	Upfront	Who maintains	Best for
Buy	High capital	You	Stable, high-utilization, long horizon
Lease	Financed	You	Same operations, smoother cash flow
RaaS	Low / none	Provider	Seasonal, first deployments, capital-averse

Rule of thumb: Prove the case on RaaS or a paid pilot before you buy a fleet outright. The pilot answers the questions the spreadsheet cannot (does it hit throughput in your traffic, does the WMS integration hold up, does the safety config throttle it), and only then is a capital purchase a confident bet rather than a hope.

Frequently asked questions

What is the difference between an AMR and an AGV? An AGV follows a fixed guidepath (magnetic tape, wire, optical stripes, or a QR grid) and stops if the path is blocked. An AMR builds a map with onboard sensors, localizes itself in real time with SLAM, and plans its own path, so it can route around obstacles and be redeployed by editing software. The AMR is more flexible and more expensive; the AGV is cheaper and more reliable on a fixed route. See the mobile robots guide for the full comparison.

When is a simpler AGV the right call? When the route is permanent, high-volume, and predictable, and the aisle is not shared with unpredictable traffic. A tugger running the same loop 200 times a shift does not need SLAM and the compute it demands; it needs to be cheap and reliable, and a guidepath delivers that. Pay for AMR flexibility only when your routes actually change or your building will not let you lay guidepath.

How much does an AMR cost? Indicative 2026 figures: light tote-carriers land in the low tens of thousands of dollars per unit, general-purpose payload AMRs in the mid-to-high tens of thousands, and heavy pallet or robotic-forklift AMRs from around $100,000 up. The robot is often half or less of the program once you add chargers, fleet software, integration, and support. RaaS subscriptions run in the low-to-mid thousands per robot per month with little upfront capital.

What safety standards should I look for? For driverless industrial trucks (pallet and unit-load movers) the reference is ISO 3691-4; for AMRs in North America the mobile-robot standard is R15.08. Confirm the robot uses safety-rated laser scanners with certified protective fields and a certified emergency-stop function, and have your own safety engineer sign the site risk assessment. Uncertified "obstacle avoidance" does not satisfy these standards. The robot safety guide covers performance levels and stop categories.

What is VDA 5050 and why does it matter? VDA 5050 is an interoperability standard that defines a common interface between a fleet manager and robots from different vendors, so one master control can drive a mixed-brand fleet. It matters because it protects you from vendor lock-in: if you standardize on a VDA 5050 fleet manager, you can add robots from other makers later. Ask for it by name and confirm how completely each vendor implements it, because coverage varies.

How do I calculate ROI? Model deliveries per hour on your real cycle times (travel plus handling plus queueing, with the safety slowdowns), multiply by the fully-loaded labor cost of the shifts you actually redeploy, and subtract the total program cost (robots, chargers, software, integration, support) over three to five years. A two- or three-shift operation with real labor to offset typically pays back in 1.5 to 3 years; a single-shift operation where robots idle most of the day pays back far more slowly.

AMR or cobot for my line? They solve different problems. An AMR moves material between places; a cobot is a stationary arm that manipulates parts at a workstation. Many lines use both: the AMR delivers the tote to the cell and the cobot does the pick-and-place. If your problem is transport, buy an AMR; if it is manipulation, buy a cobot; if it is both, plan the handoff between them early.

How does charging work without a battery room? Opportunity charging: lithium packs plus contact or wireless charge points at spots where robots already pause (pick stations, staging areas), with the fleet manager scheduling 30-to-60-second top-ups so the fleet runs near 24/7 with no swap labor and no battery room. Reserve full charge cycles or battery swapping for the heaviest, highest-duty AGVs where opportunity charging cannot keep up.

How long does deployment actually take? Plan for weeks to a few months, driven mostly by two things: mapping and commissioning the fleet for your real traffic, and integrating the fleet manager with your WMS or MES. A supported WMS connector is a configuration job; a custom integration is a software project with its own timeline. Ask a reference customer with a building like yours what their deployment really took, because that answer is more honest than any Gantt chart in a sales deck.

Can I mix robots from different vendors? Yes, if they and your fleet manager speak VDA 5050, which is exactly what the standard exists to enable. Without it, each vendor's robots need that vendor's controller, and you end up running parallel fleets that do not coordinate traffic with each other. If a multi-vendor future is plausible, make VDA 5050 support a hard requirement now rather than discovering the lock-in later.