Phase 6 — Delivery Dispatch

The RideNDine flow creates a delivery job and dispatches a driver once the order is READY and paid. COOCO receives driver information via webhook.

---

Overview

RideNDine (internal) → Driver App → RideNDine → COOCO (webhook) → Customer

Step	From	To	Action
6.1	RideNDine	RideNDine	Internal — create delivery job
6.2	RideNDine	Driver	Driver App notification
6.3	Driver	RideNDine	Driver accepts job
6.4	RideNDine	COOCO	POST /webhooks/delivery-status
6.5	COOCO	Customer	Internal — display tracking

---

Step 6.1 — Create Delivery Job (RideNDine Internal)

RideNDine internally creates a delivery job once the order is READY and paid. COOCO does not send anything at this step.

---

Step 6.2 — Notify Driver (RideNDine → Driver App)

RideNDine calls a driver via the Driver App. COOCO does not have its own driver app.

---

Step 6.3 — Driver Accepts Order

The driver accepts the job on the Driver App. COOCO is not involved.

---

Step 6.4 — Webhook: Driver Assigned

From: RideNDine → To: COOCO

Endpoint (COOCO expose): {DIRECTUS_URL}/ridendine/webhooks/delivery-status

Method: POST

Purpose: COOCO receives driver information and ETA.

Payload received

{
  "event": "driver_assigned",
  "ridendine_order_id": "<string>",
  "driver": {
    "name": "<driver name>",
    "phone": "<driver phone>"
  },
  "eta_minutes": 25
}

Save to Directus

Field	Value
orders.delivery_status	DRIVER_ASSIGNED
orders.delivery_driver_name	driver name
orders.delivery_eta_minutes	ETA in minutes

---

Step 6.5 — Display Tracking (Internal)

From: COOCO → To: Customer

COOCO reads orders from Directus and displays tracking information on /my-orders/:id.

No requests are sent to RideNDine at this step.