Delivery robot service in restaurants and hotels: common field failures and fixes
Short answer: On delivery and serving robots in North American restaurants and hotels, the parts that need field service most often are the ones that touch the building: drive wheels and casters, dirty or knocked sensors (LiDAR, depth and vision cameras), charging docks and contacts, ageing batteries, and the robot's links to Wi‑Fi, elevators and doors. Most of these can be diagnosed and fixed on site in one visit with a cleaning kit, a wheel or caster, a contact brush, a laptop and the maker's service tool. Main boards, motor controllers, sealed drive modules, battery packs that need opening and anything that needs factory calibration usually go to the robot maker, either as a remote session or as a part swap from local stock with the failed part shipped back. The table below lists each failure by part: what staff see, the likely causes, what a technician can do on site, and when to escalate.
KeepRobots is a robot field service company in Vancouver serving Canada and the United States. We don't make or sell robots and are not an exclusive agent for any brand. Brand names below are used only to cite their public documents. Hours and costs are illustrative estimates, not measured data; your robot's manual and the maker's service instructions always take priority.
How this page fits with our other delivery robot notes
- Delivery robot field service in North America: the overview, covering what goes wrong, who does what on elevators, and what we offer.
- Preventive maintenance schedule for cleaning and delivery robot fleets: what to do before things break, daily to yearly.
- How long delivery-robot drive wheels actually last: wheel wear in depth.
- This page: what to do after a robot starts failing. Symptom → cause → on-site fix → escalation, by part.
The diagnostic table: delivery robot field failures by part
Read it left to right. "On site" means a trained technician with ordinary tools, a cleaning kit, common spares and the robot maker's service app or laptop tool, working under the maker's instructions. "Escalate" means the fix belongs to the maker: remote engineering, a part from the maker, or a return.
| Part | What staff see | Likely causes | What can be done on site | Escalate to the maker when |
|---|---|---|---|---|
| Drive wheels, suspension, casters | Robot drifts or wobbles, pulls to one side, misses the dock, gets "lost" in long corridors, clunks over sills | Worn or flat-spotted tread, tread softened by kitchen degreasers, hair and string wound round axles, worn bearings, tired suspension springs, cracked caster | Clear the axles, measure tread, replace wheels and casters in pairs, check suspension travel, re-run odometry/docking checks | A motor or encoder fault code persists after the mechanical fix, or the drive module is sealed and has to be swapped whole |
| LiDAR, depth and vision cameras | Sudden stops in open space, "obstacle" alerts with nothing there, slow creeping, localisation failures near windows or mirrors | Grease film or fingerprints on sensor windows, scratched cover, a knock that moved the sensor, sunlight, glass walls, mirrors and black surfaces, new ceiling decorations covering a ceiling marker | Clean windows with the method in the manual, inspect for cracks and loose mounts, run the maker's sensor self-test, mark glass and mirror areas on the map, restore ceiling markers | Self-test still fails after cleaning, the sensor needs re-calibration with maker tools or targets, or a cover is cracked and the sensor is not a field-replaceable part |
| Emergency stop and bump strips | Robot refuses to move, shows an e-stop or collision alarm, or keeps stopping after light contact | E-stop button left pressed or partly stuck, bump strip pinched or bent after a cart hit, broken switch, connector loose | Reset and test the e-stop and every bump zone, free or replace the strip if it is a listed spare, reseat connectors, record the test | The safety circuit fault stays after reset, or any repair would involve bypassing a safety input. That is never a field fix. |
| Charging dock and contacts | Robot misses the dock or bounces off it, docks but doesn't charge, "charging" flickers, overnight charge incomplete | Dirty or burnt contacts, bent spring contacts, dock moved or knocked, dock on a shared or switched outlet, dock in a spot with glare or clutter | Clean contacts, check springs, verify the outlet and wiring with a meter, reposition and re-register the dock, re-test docking from several approach angles | Dock electronics fail, or the robot's charging port or charge controller is the problem |
| Battery | Shorter run time, robot heads to the dock mid-service, percentage jumps, won't wake after a closure | Normal ageing, many deep discharges, long storage at low charge, cold storage (patios, loading docks, winter shipping) | Read battery health and cycle data in the service tool, compare with run logs, adjust charging schedule, swap a pack if it is a field-replaceable spare | The pack has to be opened, it is swollen, damaged or hot, or a warranty claim needs the maker's verdict. Damaged lithium packs have special shipping rules (see our warranty and RMA note). |
| Trays, compartments, door locks | Tray sensor reports a load that isn't there, delivery won't complete, hotel compartment door won't open or close, rattling | Spilled drinks and food under the tray, loose mounts, worn pads, misaligned compartment door, lock actuator or PIN problem | Clean and dry the tray area, tighten or replace mounts and pads, realign doors, test the lock through every mode | Lock actuator or tray sensor board has failed and is not a listed spare |
| Wi‑Fi, roaming, elevators and doors | Tasks drop in certain corridors, robot waits forever at the elevator, gets stuck in front of a door, "offline" alerts at the same spots | Dead zones, slow roaming between access points, guest network with a captive portal or client isolation, password change, elevator gateway offline, car in independent or fire service, access-control schedule change | Walk the route with a Wi‑Fi survey, work with the venue's IT on SSID and roaming settings, check the robot-side gateway and credentials, re-test the elevator floor by floor and every door | The fault is in the elevator controller or the door operator (that is the building's licensed contractor, not us or the robot maker), or in the maker's cloud service |
| Map and localisation | Wrong table, wrong room, robot "lost" after a refit, sudden failures on one route | Furniture moved, new partitions, seasonal decorations, new carpet or a mat that changes wheel slip, glossy new floor, map version mismatch after an update | Edit the map or rebuild it, update waypoints, no-go and slow zones, re-test every route at service speed | Map or localisation stays broken after a clean rebuild, which points to sensor or software faults |
| Software and OTA updates | New behaviour after an update, features missing, robot stuck on an update screen, app and robot disagree | Update pushed during service hours, partial download on weak Wi‑Fi, version mismatch between robot, app and elevator gateway | Record versions, restart in the documented order, give the update stable power and network, confirm settings and maps survived, report to the maker | Almost always: rollback, re-flash and bugs are the maker's job. The on-site job is clean evidence and a stable environment. |
One pattern runs through the table. Pudu's public maintenance guide for BellaBot asks for trays, drive and auxiliary wheels, the vision and depth sensors and the LiDAR to be wiped weekly, with the robot powered off, and warns not to use water or any other liquid on the robot. In a busy restaurant that weekly wipe is often skipped, and a share of the "sensor faults" we would be called for are dirt.
North American venue problems that cause many of these failures
Robots designed and tested in Chinese restaurants and hotels meet some different building conditions here. These are the ones to plan for.
Carpet, rugs and mats
Hotel corridors, function rooms and many casual-dining rooms in North America are carpeted, and entrances have thick walk-off mats in winter. Carpet loads the drive motors harder, changes wheel slip (which affects odometry), and the edges and transition strips are where small casters catch. A robot that ran perfectly on tile in the demo can start drifting on a long carpeted corridor. On site we can map carpet edges, set slow zones, check that the robot's rated threshold height covers the actual strip, and ask the venue to tape or replace curled mat edges.
Ramps, thresholds and accessible routes
Accessibility rules shape North American floors. Under the 2010 ADA Standards for Accessible Design, ramp running slope can be up to 1:12 (about 8%), changes in level up to ¼ inch can be vertical and up to ½ inch must be bevelled, and door thresholds are generally limited to ½ inch. In Canada, provincial building codes and CSA B651 set similar accessibility requirements. Two consequences for robots: a 1:12 ramp is steep for some serving robots when loaded, so check the maker's rated slope against the real ramp before routing over it; and the robot must never park on or block an accessible route, ramp or door clearance. Ask the venue which routes are required to stay clear.
Kitchen grease, floor chemicals and wet floors
Restaurant kitchens and pass areas leave a grease film on floors, wheels and sensor windows. High-pH degreasers and quaternary disinfectants also attack polyurethane tread (our wheel note explains why). Pudu's general precautions ask for the running path to be kept clear of liquids and sticky substances. In practice: route the robot so it doesn't cross the wet zone at the dish pit, add sensor-window cleaning to the closing checklist, and expect wheels to wear faster near kitchens.
Long hotel corridors and Wi‑Fi
Hotel corridors are long, repetitive and often covered by many small access points serving guest rooms. Robots roaming from one access point to the next can lose connection for long enough to drop a task, and a guest network with a captive portal or client isolation may block the robot entirely. Long featureless corridors also give LiDAR little to localise against, so worn wheels show up here first. What helps: a dedicated robot SSID agreed with hotel IT, a route walk with a Wi‑Fi survey tool, roaming settings tuned with the IT team, and, where the robot supports it, an LTE fallback.
Elevators, fire recall and doors
Multi-floor delivery depends on the elevator. Elevators in the US and Canada are built to ASME A17.1/CSA B44; British Columbia currently enforces CSA B44-16 through Technical Safety BC, and work connected to the elevator controller has to be done by a licensed elevator contractor. The case to test on site is Phase I emergency recall: when a fire alarm triggers recall, cars return non-stop to the designated landing and stay there for firefighters. A robot inside a recalled car has to leave at the recall floor, stop calling cars and not block the doors. Fire doors held open magnetically will also close on alarm under NFPA 80, so the robot's route must handle a door that is suddenly shut. Our elevator integration note covers who does what and the floor-by-floor test.
Cold and closures
Pudu's precautions say not to operate its robots below 0 °C or above 40 °C, and to store a robot charged above 60% with the key switch off, recharging every three months. Seasonal patios, unheated loading docks, winter shipping and venues that close for a season are where batteries get damaged. Bring robots indoors before winter, and charge them before a closure.
On site vs remote vs send back: a simple triage rule
- Remote first (10–30 minutes): the maker or the operator checks logs, fault codes, battery data, network status and recent changes. A good share of "robot broken" calls are Wi‑Fi, a moved dock, an e-stop left pressed or a map change, and some of them can be solved over the phone with the venue's staff.
- Send a technician when the fault is physical (wheels, sensors, contacts, trays, mounts), when the building is involved (Wi‑Fi walk, elevator re-test, door, map rebuild), or when remote checks are inconclusive and the robot is out of service.
- Escalate to the maker for boards, motor controllers, sealed modules, battery packs that need opening, factory calibration, firmware rollback and anything touching a safety circuit. The technician's job then is to collect evidence (serials, firmware versions, logs, photos), swap the part if it is in local stock and ship the failed one back under an RMA number.
Whatever the outcome, the visit should end with a short report: what was found, what was changed, versions before and after, and what the venue should do differently. That report is what makes the next remote triage faster.
What a delivery robot service visit costs: examples
Using KeepRobots' published rates in our Greater Vancouver core area as an example: diagnostic fee $200 CAD per visit (credited against an approved repair), call-out $100 CAD, on-site labour $150 CAD per hour; in the US the diagnostic fee is $200 USD and labour $150 USD per hour. Taxes, parts and travel outside the core area are extra. The hours below are estimates for illustration, not measured data or a quote.
| Visit (one robot unless stated) | Estimated time on site | Labour and call-out (before tax, parts extra) |
|---|---|---|
| Robot drifts and misses the dock: wheels and casters replaced in pairs, docking re-tested | 1.5 h | $100 + 1.5 × $150 = $325 CAD (diagnostic credited) |
| "Phantom obstacles": sensors cleaned and checked, glass areas marked on the map, routes re-tested | 2 h | $100 + 2 × $150 = $400 CAD (diagnostic credited) |
| Tasks drop on two hotel floors: Wi‑Fi walk with IT, elevator re-test on 4 floors, map update | 4 h | $100 + 4 × $150 = $700 CAD (diagnostic credited) |
| Fault found to be a main board, part ordered from the maker; diagnosis only on this visit | diagnostic visit | $200 + $100 = $300 CAD; the swap visit is billed separately when the part arrives |
Two practical points. Several robots at one venue on the same visit share one call-out. And local spares change the cost more than the hourly rate does: a second trip because a $30 caster wasn't on hand costs another call-out and another day out of service (see how many spares to stock).
Common mistakes
- Cleaning sensors with spray cleaner or a wet cloth. Follow the manual. Pudu, for example, says no water or other liquid on the robot; use a dry cloth or lens cleaner.
- Replacing one wheel. Mismatched tread diameters make the robot curve. Replace in pairs.
- Moving the dock "a little" during a refit and not re-registering it. Docking failures follow.
- Letting a firmware update run during dinner service on weak Wi‑Fi.
- Asking a robot technician to "just wire in" the elevator. Anything connected to the controller is the elevator contractor's work.
- Treating every stop as a robot fault. Check what changed in the building first: furniture, decorations, a new mat, a new Wi‑Fi password.
What KeepRobots can do
For restaurants, hotels and robot makers with delivery and serving robots in Canada and the US, we can:
- Diagnose and repair robots on site by the hour, under the maker's fault tree and approval rules: wheels, casters, sensors, docks, trays and locks, maps, Wi‑Fi and elevator re-tests, with a written report after each visit, in English or Chinese. Our engineers read Chinese technical documents.
- Coordinate with the building's IT team and licensed elevator and door contractors, and do the robot-side work ourselves.
- Hold the maker's spare wheels, casters, bump strips and battery packs in Vancouver for same-visit swaps, and handle RMA tagging and returns.
- Deploy and commission new robots and run preventive maintenance visits. More on our robot service across Canada page and our Vancouver service point for robot brands.
Robot makers looking for a North American field service partner for delivery robots can email partners@keeprobots.com. Venues with a robot down can email support@keeprobots.com or book a service call.
FAQ
What breaks most often on delivery robots in restaurants and hotels?
The parts that touch the building: drive wheels and casters, sensor windows covered in grease or fingerprints, charging docks and contacts, ageing batteries, and the robot's connection to Wi‑Fi, elevators and doors. Many "robot faults" turn out to be building changes such as moved furniture, a new mat or a changed Wi‑Fi password.
Can a delivery robot be repaired on site, or does it have to go back to the manufacturer?
Most common faults can be fixed on site: wheels and casters, sensor cleaning and checks, dock contacts, trays and locks, map rebuilds and Wi‑Fi or elevator re-tests. Main boards, motor controllers, sealed drive modules, battery packs that must be opened, factory calibration and firmware rollback usually go to the maker, often as a swap from local stock with the failed part shipped back.
Why does my delivery robot stop for obstacles that aren't there?
Usually dirty or scratched sensor windows, sunlight, glass walls, mirrors or very dark surfaces, or a sensor knocked out of position. Clean the windows the way the manual says (many makers say no liquids), run the maker's sensor self-test and mark glass and mirror areas on the map. If the self-test still fails, the sensor may need re-calibration by the maker.
How much does a delivery robot service call cost in Vancouver?
At KeepRobots' published rates in the Greater Vancouver core area: $200 CAD diagnostic fee per visit (credited against an approved repair), $100 CAD call-out and $150 CAD per hour on site, before tax and parts. A wheel and caster replacement taking about 1.5 hours would come to roughly $325 CAD plus parts; this is an illustrative estimate, not a quote.
What should a delivery robot do during a fire alarm in an elevator?
When the fire alarm triggers Phase I emergency recall, elevator cars return to the designated landing and stay there. The robot should leave the car at the recall floor, stop calling elevators and not block the doors or the accessible route. Test this on site with the building's elevator contractor before go-live.
Sources
- Pudu Academy, BellaBot maintenance guide: academy.pudutech.com; robot usage precautions and maintenance (battery storage, temperature, running path): academy.pudutech.com
- U.S. Access Board, 2010 ADA Standards for Accessible Design (303 changes in level, 404.2.5 thresholds, 405 ramps): access-board.gov; CSA/ASC B651:23, Accessible design for the built environment (Accessibility Standards Canada): accessible.canada.ca
- ASME A17.1/CSA B44 Safety Code for Elevators and Escalators: asme.org; Technical Safety BC, elevating devices (CSA B44-16 in effect): technicalsafetybc.ca; Technical Safety BC, elevating devices licences: technicalsafetybc.ca
- Fire service operations with elevators (Phase I and Phase II): fireengineering.com
- NFPA 80 and hold-open fire doors (Fire & Smoke Containment Association webinar): fcia.org
Hours and example costs on this page are illustrative estimates, not measured data. KeepRobots rates are current published rates and may change; taxes, parts and travel outside the core area are extra. Manufacturer documents are quoted as of 2026-10-17 as examples; KeepRobots is an independent field service company and is not affiliated with or authorized by these manufacturers. Your robot's manual takes priority.