3 Things AI Won’t Sort Out for You in the Warehouse
Physical AI and Large Behavior Models are entering mobile robotics faster than most maintenance teams assumed even a year ago. An ever “smarter” AMR can make decisions that it previously had to be taught step by step — but warehouse readiness for AMRs still depends on what happens on the floor, not in the model. AI can give the robot a decision. Your facility still has to give it boundaries.
At the Robotics Summit & Expo, one of the largest events in the mobile robotics industry, more than 70 speakers and dozens of sessions pointed in the same direction: robot learning is moving from “write a script for every situation” to “the model learns behaviours”. Among the exhibitors and speakers were research teams working on so-called Large Behavior Models — models that generalise movement and manipulation instead of executing a rigidly programmed sequence. This is a real change. And that is exactly why it is worth coolly separating two things: what the algorithm does ever better, and what the environment has to provide.
Physical AI changes the robot, not the warehouse
The biggest misunderstanding in conversations about deployments goes like this: “since the robot has ever better AI, it will cope with our mess”. It won’t. A behavioural model improves the way the robot reacts to what it sees — but it does not change the quality of what there is to see. If the input signal is ambiguous, even the best model will make a decision based on bad data.
In practice, an intelligent AMR in a disorganised facility behaves predictably badly: it slows down more often, stops more often and interacts more often with pedestrian traffic, because it has no reliable frame of reference. The algorithm will not “guess” where a walkway ends and a drop-off zone begins if that boundary is not on the floor. Physical AI raises the ceiling of what the robot can do. You are still the one who lays the floor beneath it.
1. Legible travel routes
The first thing AI will not sort out for you is an unambiguous route layout. A robot can follow a designated aisle and avoid obstacles, but if the aisle itself is not physically defined, every run becomes a negotiation with the surroundings. Poorly marked routes increase the number of stops and the number of points where the machine meets a pedestrian — and every such encounter means seconds of downtime and a real risk.
A route that is legible to both people and robots is not the same as a line drawn “more or less where people walk”. It is a route with a defined width and direction and consistent marking along the entire length of the facility. High-contrast floor marking tapes define a route that the operator understands without instructions and that an autonomous system treats as a stable point of reference. The fewer places where “nobody knows which way”, the fewer micro-stops and the higher the fleet’s uptime.
2. Clear traffic and work zones
The second thing is separating the zones. A warehouse in which the drop-off area, the pedestrian walkway, the truck route and the robot’s path overlap generates conflicts no matter how good the model controlling it is. Autonomy does not remove conflict — it only reveals it faster.
Zoning starts with a design decision: where the robot may drive, where it should slow down, where it should give way and where it may not go at all. Only then is this translated into physical markings. What works well here is a combination of floor markings with elements that are easy to move when the layout changes. ZonePro mobile barriers make it possible to quickly fence off a charging zone, a buffer or an area temporarily closed to traffic, without any intervention in the floor. In a mixed traffic environment, where people, trucks and AMRs operate at the same time, a clear zone boundary is what turns a shared space into a predictable process.
3. Physical and visual boundary points
The third thing is the one most often overlooked, because it sounds trivial: an algorithm will not replace a barrier. A model may recognise that there is an obstacle in front of it, but it will not protect the place where the robot’s route crosses a column, a door or the edge of a rack. Boundary points must exist in two layers at once — as physical protection and as a visual signal for people.
Hard collision points are protected with an industrial barrier; places where legibility matters in poorer lighting or in the event of a power failure are supported with photoluminescent signs. The aim is for both the robot and the operator to receive the same information about the boundary — one in the system, the other in their field of vision. When a person understands the traffic rules in two seconds, the environment is ready. When they need to ask or stop and think, it is not.
The order that works: flow, boundaries, autonomy
Warehouse readiness for AMRs follows a proven order, and it is worth sticking to it even when the robot supplier promises that “the software will take care of the rest”. First the logic of the flow — which way and in which direction materials move. Then the boundaries — where one zone ends and the next begins. Only at the end comes autonomy, which on a foundation prepared in this way genuinely shortens the cycle instead of destabilising it.
Reversing this order is the most expensive mistake in deployments: a company buys an intelligent robot and then spends months tuning it to a space that nobody had organised beforehand. The effect is the opposite of what was intended — automation does not remove chaos, it only accelerates it and makes it visible. The robot will get where you tell it to go, but only if “where” is unambiguously described in the facility.
Warehouse readiness for AMRs — a checklist before you let the robot in
- Routes: can the operator see the course of the route without asking and without turning back? If they have to ask, the traffic is not obvious to the robot either.
- Zones: are the drop-off, pedestrian, truck and robot areas separated, or do they overlap?
- Boundaries: are hard collision points physically protected, not just “visible”?
- Legibility in poorer conditions: do the markings work in poorer lighting and during a shift change?
- Consistency between shifts: are the traffic rules the same in the morning and on the night shift, or does every team “do it its own way”?
If the answer to even one of these questions is “it depends”, it is worth starting with the traffic organisation layer rather than buying yet another technology. It is the cheapest stage of the entire deployment, and at the same time the one that determines the return on all the others.
Won’t a newer AI model make markings unnecessary?
Not within the time horizon we are talking about. Successive generations of models improve the robot’s decision-making, but they all work on signals from the environment. The better a model “reasons spatially”, the more weight the quality of what it sees carries. A legible facility is not a crutch for weak AI — it is a precondition for good AI to have something to work with.
Where do you start if the budget is limited?
With routes and zones, because they generate the most micro-stops. Organising routes with floor marking tapes and fencing off key zones with mobile barriers usually delivers the fastest return, even before the first robot appears in the facility. Securing boundary points and legibility in poorer conditions are added in the second step.
Sources
- The Robot Report, Robotics Summit & Expo — physical AI and Large Behavior Models in mobile robotics: therobotreport.com