# ZeekNow
# Delivery processes
Here are the basic processes of Zeek food delivery:
- Store assignment by Zeek.
- Get quotations.
- Customer places order in App.
- Creates delivery order.
- Zeek assigns partner.
- Partner accepts order.
- Partner proceeds to store (merchant).
- Partner arrives store (merchant).
- Delivering, partner proceeds to customer location.
- Partner arrives customer location nearby.
- Customer receives food. Order is completed.
# Standard API flow
The standard API flow diagram demonstrates a food ordering app interacting with Zeek Open API. It also highlights the API in use.
# Order status code
During delivery process, system will update status by status codes. Developer can receive the latest status update by Order status update callback. Here are the status codes.
| Order status | Description | Provide in callback |
|---|---|---|
| 9001 | Order is created | No |
| 9005 | Partner accepted order | Yes |
| 9010 | Partner arrived merchant nearby | Yes |
| 9011 | Partner arrived merchant | Yes |
| 9015 | Delivery in progress | Yes |
| 9017 | Partner arrived destination nearby | Yes |
| 9021 | Order is completed | Yes |
| 9025 | Order is cancelled - before partner picked up food | Yes |
| 9026 | Order is cancelled - after partner picked up food | Yes |
| 8001 | Another partner is assigned | No Please contact Zeek team should you require this status. |
| 8012 | Partner departed from merchant | Yes |
# Order cancel code
When an order is being cancelled, the platform will record a Cancel code to identify the cancel reason. The code can be retrieve in API-3.4.1 Get order details, API-3.4.4 Get order details by user phone number and API-3.9.1 Order status update callback.
| Cancel code | Description |
|---|---|
| 7001 | Assign timeout |
| 7002 | Sender reason |
| 7003 | Recipient reason |
| 7004 | Shipper reason |
| 7005 | Order information error |
| 7006 | Test order |
| 7007 | Other reason |
# Time prediction (ETA)
In delivery journey, merchants need the time required in different delivery processes for operations. On the other hand, we can provide better user experiences to customer by povide the time prediction. Therefore, Zeek builds several time prediction models by machine learning. Developers can retrieve the time prediction via Open APIs.
# Accept time
Definition: Before delivery order is created. If a merchant is going to create an order in Zeek platform, the predicted time required for a partner to accept that order.
Suggested usage: Display the time on the order taking interface, so that store mananger knows the time.
API: API-3.2.3
# Showup time
Definition: After partner accepts an delivery order,the predicted time required for a partner to arrive store / merchant.
Suggested usage: Display the time on the order taking interface, so that store manager knows the time.
API: API-3.4.2
# Quote time
Definition: Before delivery order is created. If a merchant is going to create an order in Zeek platform, the predicted time required for the food to be delivered to customer.
Suggested usage: Display the time on customer interface, so that he knows the time before placing order.
API: API-3.2.2
# Delivery time
Definition: After order is created, the predicted time required for the food to be delivered to customer.
Suggested usage: Display the time on customer interface, so that he knows when will the food be delivered.
API: API-3.4.3
