AI Robotics ·
Who should resolve failed handoffs when third-party apps dispatch delivery robots?
Problem and evidence
Serve Robotics announced a dispatch API and a simulator on November 11. It requires approval before developers can use live robots. In South Korea, Woowa Brothers announced in August that it was putting a newly certified Dilly robot into Baemin B Mart operations. The distinction is who takes the order and initiates dispatch.
| Dimension | United States — Serve Robotics | South Korea — Baemin B Mart |
|---|---|---|
| Verified stage | Developer sandbox is public. Live dispatch requires approval | Safety certification and field deployment of the new Dilly model were announced |
| Order path | Outside apps submit pickup and destination details. Serve dispatches and supervises robots | Robot delivery tied to B Mart orders. Public third-party dispatch was not verified |
| Evidence gap | No published partner-level misdelivery or refund-dispute results in the release | No published third-party handoff benchmark identified |
Alternatives and evaluation
A Korean fleet operator can keep dispatch within its own app or grant one partner access with traceable confirmation, cancellation and handoff records. An outside app adds another sales channel, but conflicting address updates can cause a failed handoff even when navigation works. Both systems should reconcile the order ID and destination. The ordering app should handle payment errors first, and the fleet operator should handle navigation and custody incidents first.
Compare partner traffic with first-party orders in the same service area and time slots. Measure duplicate dispatch, failed handoffs, refund completion time and support minutes per failed order. Pause the integration if dispatch proceeds after an address change has failed to synchronize.