Guides
Report order statuses
Each status you report moves the order through the state machine, notifies the customer, and tells the delivery partner the food is ready.
The flow#
- Your system → Let's PizzaAccepted (with expected ready time)
status: accepted - Let's Pizza → Customer“Your order was accepted”
- Your system → Let's PizzaPreparing
status: preparing - Your system → Let's PizzaReady
status: ready - Let's Pizza → Customer“Ready”, the rider heads to the branch
Allowed statuses#
Kitchen: accepted · rejected · preparing · ready · picked_up · cancelled. Road: out_for_delivery · delivered · delivery_failed.
Yours are in settings.orders.statuses. The full rules are in Order lifecycle.
The event id#
Each status change carries an id from your system. The same id twice is applied once; events may arrive out of order, so we go by when they happened, not when they arrived.
{
"eventId": "BC-EVT-000985",
"to": "preparing",
"expectedFrom": "accepted",
"occurredAt": "2026-11-19T19:35:02+03:00",
"estimatedReadyAt": "2026-11-19T19:50:00+03:00"
}{
"outcome": "applied",
"status": "preparing",
"reason": null
}outcome: applied; duplicate (already applied); ignored (late or repeated); parked (waits for a person, such as a cancel after the kitchen started).
Reject and cancel#
- Reject and cancel carry a reason. Before the kitchen starts they apply at once and an online payment is refunded.
- After the kitchen started, a cancel goes to the branch manager to confirm with a reason, since the rider may already have the food.
Endpoints used#
Anything marked “Coming soon” is not served yet; it joins the reference as soon as it ships.