πŸ”„ Order Status Update (From Blend to Delivery App)

🧾 Description


This document explains the order_updated event that Blend sends to the delivery app
when the order status is updated from Blend’s system β€” such as via the merchant dashboard or kitchen display system.


This allows Blend to notify the delivery partner of important changes to the order's lifecycle.





πŸ” Direction


Blend β†’ Delivery App


Blend pushes this event to the delivery app's registered webhook URL.




πŸ“¦ Example Payload


{
  "event": "order_updated",
  "event_time": "2025-01-01 00:00:00",
  "branch_id": "14589",
  "payload": {
    "order_id": "order_id",
    "status": "accepted"
  }
}



πŸ—‚ Field Descriptions

FieldDescription
eventAlways "order_updated"
event_timeTimestamp when the status update occurred
branch_idID of the branch that owns this order
payload.order_idID of the order being updated
payload.statusNew status of the order β€” one of accepted, rejected, cancelled, prepared


πŸ”„ Status Types

StatusMeaning
acceptedOrder was accepted by the merchant
rejectedOrder was rejected by the merchant
cancelledOrder was canceled by the merchant or system
preparedOrder has been prepared and is ready


πŸ“‘ Webhook Delivery


  • Blend pushes this JSON to the delivery partner’s webhook URL
  • Delivery app must return 200 OK on successful receipt
  • Optionally, Blend may retry on failures


βœ… Notes


  • Status updates help sync Blend’s internal state with delivery platforms
  • order_id should match the order previously sent in the order_created event
  • Delivery apps should process updates immediately to reflect order progress to couriers or customers