User purchase
Select/pay in a mini-program and choose destination.
Building merchant shopping and delivery
Connect merchants with office customers.Bring purchases upstairs.
Connect in-building coffee, retail and light-food merchants: users order, merchants accept/prepare/call a robot, and recipients verify collection.
Request
Users
Select items, destination and required time.
Deliver
Robot
Follow configured routes and access rules.
Handover
Recipients
Receive the arrival alert, use configured access and verify receipt.
Pilot the documented workflow with responsible staff verifying key handovers.
The service
Service flow and ownership
Robots execute configured tasks; responsible staff retain verification and on-site response.
Users
Request
Select items, destination and required time.
Dispatch staff
Prepare and load
Check items, packaging and compartments; load manually and confirm.
Robot
Deliver
Follow configured routes and access rules.
Recipients
Handover
Receive the arrival alert, use configured access and verify receipt.
Managers
Retain records
Review completion, exceptions and handover records.
Confirm execution separately from human handover/review; assigned staff take over exceptions.
Roles
Dispatch and receiving staff
Request, prepare, load, verify and acknowledge receipt.
Robot
Transport, notify and return status within the configured scope.
Management and support
Maintain points, schedules, equipment, exception handling and records.
Service modes
Select modes for the workflow; agree extensions separately.
Merchant fulfilment
App, WeChat or printer notifications; prepare and call the robot.
Property operations
Coordinate onboarding, access, power and service rules.
Confirm delivery, payment, membership, marketing and settlement scope. The source’s 10–20 minutes and 5–10% sales uplift are references, not guarantees.
Terminals and configuration
Document-based scope; confirm supplied model, options and site fit.
Robot / business platform
Configure orders, merchants, membership, payment, marketing, delivery and operations within scope.
Deployment
Choose cloud, local/private, APIs or mini-program links.
Suitability
Scenario fit
Connect in-building coffee, retail and light-food merchants: users order, merchants accept/prepare/call a robot, and recipients verify collection.
User purchase
Select/pay in a mini-program and choose destination.
Merchant fulfilment
App, WeChat or printer notifications; prepare and call the robot.
Property operations
Coordinate onboarding, access, power and service rules.
Where the service helps
Reduce repeated trips around these tasks and define on-site handovers.
| Service area | Service scope |
|---|---|
| User purchase | Select/pay in a mini-program and choose destination. |
| Merchant fulfilment | App, WeChat or printer notifications; prepare and call the robot. |
| Property operations | Coordinate onboarding, access, power and service rules. |
Coordination priorities
Reduce repeated trips
Assign suitable repeated routes to robots and compare results in the pilot.
Clear handovers
Verify outcomes against task, destination and responsible role.
Operational review
Use task states and exception records to adjust routes, schedules and configuration.
Building route
Routes and service points
Configure routes for the actual site; diagrams explain the workflow.
Merchant loading
Check order, goods, loading code and recipient number.
Floor delivery
Call/SMS, verify collection and redeliver if needed.
Operations
Missed orders, after-sales, data and reconciliation.
Locations
- Merchant loading
- Floor delivery
- Operations
Validate a complete loop
Merchant loading → Floor delivery → Operations
Diagrams explain the flow; survey actual passages, thresholds, access and stops.
Site readiness and operations
Confirm site, equipment and staffing; verify interfaces per project.
Operations
Follow missed orders, monthly reconciliation, invoicing, after-sales and business data.
Ownership
Merchants own goods/preparation; platform and property responsibilities follow the agreed service scope.
Commission configured interfaces, notifications and access; assign site contacts and staff fallback.
Suggested readiness checks
Swipe horizontally to see all columns.
| Item | Scope | Confirmation |
|---|---|---|
| Scope and points | Merchant loading, Floor delivery, Operations | Confirm accessible scope and responsible staff on site. |
| Routes and access | Maps, passages, doors/lifts, network and charging. | Commission cross-floor and controlled-door access as needed; diagrams do not replace site tests. |
| Handover and exceptions | Dispatch and receiving staff, Robot, Management and support | Agree notifications, staff takeover, records and review rules. |
Fleet planning
Pilot and expansion
Agree merchant contracts/settlement, build storefronts and train teams before piloting the order-to-collection loop.
Robot / business platform
Configure orders, merchants, membership, payment, marketing, delivery and operations within scope.
Deployment
Choose cloud, local/private, APIs or mini-program links.
Sizing considerations
| Sizing variable | Effect on capacity |
|---|---|
| Task cycle | Measure request, execution, handover, return and charging time. |
| Site scope | Merchant loading, Floor delivery, Operations |
| Staff coordination | Allow for available receiving, reviewing and exception-response staff. |
Source configurations/data refer to their stated scenario; confirm final sizing through site validation.
Pilot & operation
Suggested implementation
The following are project assessment and acceptance suggestions, subject to site confirmation.
Confirm scope
Site preparation
Agree merchant contracts/settlement, build storefronts and train teams before piloting the order-to-collection loop.
Configure and commission
When ready
Check devices, routes, points, accounts and necessary access/system interfaces.
Trial and acceptance
By project agreement
Validate real tasks, staff coordination, exceptions and records before expansion.
Suggested exception handling
The following are project assessment and acceptance suggestions, subject to site confirmation.
View the exception checklist
Swipe horizontally to see all columns.
| Condition | Action | Ownership and records |
|---|---|---|
| Task cannot continue | Pause, wait or hand over to staff under site rules. | Managers record cause, owner and recovery conditions. |
| Handover/review incomplete | Contact the assigned staff; automatic task closure does not replace their confirmation. | Record the reason and follow-up. |
| Device/access exception | Follow support procedures and use staff service if required. | Support and site staff coordinate and validate recovery. |
Suggested acceptance
The following are project assessment and acceptance suggestions, subject to site confirmation.
View acceptance measures and responsibilities
Swipe horizontally to see all columns.
| Check | Status | Verification |
|---|---|---|
| Task execution | Suggested acceptance item | Complete tasks within agreed routes/scope and record success, failure and reasons. |
| Staff coordination | Suggested acceptance item | Verify notification, permissions, human review/handover and exception takeover. |
| Operational records | Suggested acceptance item | Sample tasks, times, points and outcomes; agree metrics and targets with the project team. |
Agree before delivery
Service scope
Confirm delivery, payment, membership, marketing and settlement scope. The source’s 10–20 minutes and 5–10% sales uplift are references, not guarantees.
Responsibilities
Dispatch and receiving staff, Robot, Management and support
Configuration and metrics
Agree device models, options, interfaces, timing and targets in project documents.
Questions
Related equipment
Review product information and reconcile the document version with the supplied model/configuration.
View productDocument configuration and device checks
- Robot / business platform
- Configure orders, merchants, membership, payment, marketing, delivery and operations within scope.
- Deployment
- Choose cloud, local/private, APIs or mini-program links.
Common questions
Where should the pilot start?
Agree merchant contracts/settlement, build storefronts and train teams before piloting the order-to-collection loop.
How do robots and staff share work?
Dispatch and receiving staff：Request, prepare, load, verify and acknowledge receipt. Robot：Transport, notify and return status within the configured scope. Management and support：Maintain points, schedules, equipment, exception handling and records.
What needs separate confirmation?
Confirm delivery, payment, membership, marketing and settlement scope. The source’s 10–20 minutes and 5–10% sales uplift are references, not guarantees.
How are configuration and acceptance set?
Use source recommendations as a starting point, then confirm against site routes, supplied equipment and trial data. Suggested checks do not establish fixed performance or service guarantees.
Pilot preparation
Agree merchant contracts/settlement, build storefronts and train teams before piloting the order-to-collection loop.
Scope and points
Merchant loading, Floor delivery, Operations Confirm accessible scope and responsible staff on site.
Routes and access
Maps, passages, doors/lifts, network and charging. Commission cross-floor and controlled-door access as needed; diagrams do not replace site tests.
Handover and exceptions
Dispatch and receiving staff, Robot, Management and support Agree notifications, staff takeover, records and review rules.
Related solutions
Choose a dedicated solution for each workflow.
Building group-meal delivery solution
Coordinate loading, separate compartments and floor delivery around meal peaks using user reservations, courier loading and merchant order tools.
Building takeaway delivery solution
Couriers load meals for autonomous delivery through commissioned doors/lifts.
Building document delivery solution
Support floor-to-floor documents, reception bulk dispatch, reverse pickups to mailrooms and urgent tasks, with human packaging/recipient/handover checks.