Key takeaways
- The 20 minute figure is a vendor best case for a 3,000 square meter supermarket, measured from power on to the first task.
- Gausium itself says a site counts as deployed only after a full week of scheduled tasks run without supplier involvement.
- Mapping, wireless coverage at elevators and docking placement often sit outside the stopwatch.
- Time a real layout change and count staff interventions in week one before you accept any setup number.
Is a 20 minute robot setup realistic for a supermarket?
Gausium, in an October 8, 2026 blog post, says a 3,000 square meter supermarket can go from zero to running in about 20 minutes. The company says the same process took one to two days in its demonstration, and that actual time depends on site conditions. Those are vendor figures, and they describe a best case.
The useful question is what the clock covers. Gausium says the 20 minutes ends at the first task, not at a full week of unsupported running. Its own definition of a deployed site is a full week of scheduled tasks completed without supplier involvement, so the claim and the finish line are two separate tests.
What do the three setup steps actually include?
Gausium describes its Smart Deployment process as three operator actions. First you build the map: power on, start mapping and switch on assisted pushing. Then you start the task, and the robot generates zones and cleaning parameters from the map. Shelved areas need only their main aisles covered.
Those three steps read cleanly on paper, but they say little about the work around them. Nothing in the sequence confirms that the docking spot was settled before delivery, that aisles were clear when mapping began, or that the staff who will run the robot were present. Ask the vendor which of those tasks sit inside the 20 minutes and which sit before it.
How long does mapping really take?
Gausium says a 2,000 square meter area maps in about 30 minutes, and that a single map can extend to 1,000,000 square meters. Those figures come from a different post than the 20 minute claim, so they do not describe the same steps. They are still the nearest benchmark you have, and they suggest the mapping walk, not the menu clicks, sets the clock.
Layout changes make mapping a recurring cost. Gausium's Mira product page says real time map updates handle layout changes with no remapping and no engineer revisit. The same company's training advice says mapping recurs when layouts change. Both statements may hold for small changes and fail for large ones, so test a real change, such as a moved gondola or a closed checkout lane, and time how long the fix takes.
What about wireless coverage and elevator access?
A robot that loses its network can stop mid route, and the stall often happens where nobody tested. Robolist.ai describes a hotel group whose robot stalled in a corridor after wireless coverage dropped below the robot's threshold. That corridor had not been on the demo route, which is exactly the kind of gap a short demo hides.
Multi level sites add another step. A Finnish master's thesis found that robots could not reliably connect to wireless networks inside freight elevators with metal walls, and it recommended access points inside the car. If your robot has to change floors, the setup clock has to include elevator access, and the 20 minute figure says nothing about it.
Who trains the staff, and how many days does it take?
Gausium's post lists the staff tasks a site should cover: starting tasks, emptying bins, replacing consumables and responding to alerts. It also says training recurs as staff change, which matters in stores with heavy seasonal turnover.
Robolist.ai, an industry knowledge site, says vendor onboarding usually runs one or two days. It recommends a 20 minute session before launch and a one page quick reference posted near the robot. Week one is where the gaps show. Gausium's post says the route often proves tighter than the floor plan suggested, and the cleaning window shrinks once shift handover is counted.
How do you run a timed test on your own floor?
Run the test before you sign anything, using a demo or the site assessment visit. Time the parts the claim leaves out, and write down every intervention. The checklist below gives you a scorecard you can hand to the vendor.
- Measure the narrowest passable route at end caps, checkout approaches and stockroom turns, and record it before the vendor arrives.
- Mark cleanable floor separately from excluded zones such as drains, ramps and display pads.
- Start the clock at power on and stop it at the first completed task, logging every human touch.
- Record wireless signal at the elevator, stockroom, loading dock and back corridors, not only on the sales floor.
- Confirm in writing where the dock goes and who places it before delivery day.
- Count a full week of scheduled tasks with vendor staff off site before you call the site deployed.
Where does Service Robot Co. fit into the test?
Service Robot Co. is a full service commercial robot integrator for US businesses, and we stay OEM neutral. We pick the right robots across manufacturers, then finance, deploy, integrate, train and service every unit through a nationwide US engineer network, so one partner carries the whole lifecycle.
We lease robots only, on a three year lease with one fixed payment quoted after a site assessment. That assessment is where a timed test like this one belongs, because the wireless survey, elevator path and dock plan get checked before any robot runs. The brand on the box matters less than the test you ran.
Frequently asked questions
Sources
- Gausium, Easiest commercial cleaning robots to deploy (October 8, 2026)
- Gausium, Mira product page
- Gausium, What is an autonomous floor scrubber (October 12, 2026)
- Robolist.ai, Cleaning robot operator training
- Robolist.ai, Hospitality vendor RFP red flags
- Aalto University thesis on robot connectivity in elevators
- Tycoonstory, How to evaluate delivery and cleaning robots for healthcare facilities
- AB Vassilopoulos deploys 25 Gausium autonomous cleaning robots across Greece (press release, May 21, 2026)

