Skip to content
Hybot

Delivery

Delivery robots: orders and bills out to the table

A delivery robot carries a placed order from the pass to a named point on the venue floor plan. In Hybot this is the DELIVER_ORDER task, with DELIVER_BILL for taking the bill out. Assignment runs automatically every two seconds and weighs task priority, travel distance and robot battery together.

Core RMS task types behind delivery
Task typeAssignment
DELIVER_ORDERAutomatic, re-scored every two seconds by priority, distance and battery
DELIVER_BILLAutomatic, re-scored every two seconds by priority, distance and battery

Request a quote

How it works, specifically

  • Nobody dispatches a robot by hand

    The assignment pass runs every two seconds across the whole waiting queue and commits the best robot-to-task pairing by priority, distance and battery.

  • Destinations are real points, not coordinates

    Each floor carries a plan image and configurable points of interest imported from the robot's own map, so a destination is a table rather than a number someone has to translate.

  • A low battery takes itself out of service

    Below its configured threshold a robot leaves the assignment pool, charges and rejoins on its own. It is never handed a delivery it cannot finish.

  • Multi-floor venues are still one venue

    Floors are mapped individually and each keeps its own plan, points of interest and alignment, so a property is configured once rather than rebuilt per floor.

Common questions

How does the robot know which table to go to?
Tables are points of interest on the floor plan, imported from the robot's own map and aligned to a plan image once. A delivery task names the point, so staff pick a table rather than a coordinate.
What happens if every robot is already busy?
The task waits in the queue and is re-scored every two seconds against every robot in the fleet. Whichever robot becomes the best pairing by priority, distance and battery picks it up.
Can a delivery need a human step in the middle?
Yes. Workflows can include human-confirmation waypoints, so a robot waits for someone to load or unload it before continuing rather than driving off half-loaded.