# Bulk Upload Order Creation

Module: CORE Platform
Module slug: core-platform
Source URL: https://helpcentre.shipsy.io/en-US/shipsy/article/04Sho6v5-create-order-through-bulk-upload
Article ID: 04Sho6v5
Breadcrumbs: CORE Platform > Shipment Properties and Dashboard > Dispatch Management > Create Order through Bulk Upload

---
**Description :** Create an bulk order through Upload Excel in Dispatch Screen.

### Bulk Upload Order Creation

* In Dispatch Screen, click on Actions → Add Bulk Orders

  ![image.png](/kb-images/create-order-through-bulk-upload--04sho6v5/img_001_b00f9112aa.png)

* A file upload window appears. This method is used to create multiple vehicles makes.
* Click on the **Select From Computer** button to upload your Excel sheet and click on **UPLOAD** button.

sample\_add\_order\_dispatch1 (5).xlsx

29 Apr 2022, 03:36 PM

Following is the description for the keys for order object

|  |  |  |  |  |
| --- | --- | --- | --- | --- |
| Key Name | Description | Data Type | Required Key | Remarks |
| order\_number | Order Number | Integer | required | Combination of order\_number, order\_date and store\_id should be unique |
| order\_date | Order Date | YYYY-MM-DD | required | Only current\_date order are displayed on Dispatch Screen |
| store\_id | Store ID | String | required | Store\_Code as saved in Shipsy |
| menu\_code | Code for menu item | String |  |  |
| menu\_description | Description of item | String |  | Description of item |
| quantity | Quantity | Integer |  | Number of orders |
| order\_line\_total | Total Amount for order | Decimal |  | Total Amount |
| final\_amount | Final Amount to be charged | Decimal |  | Final Amount to be paid by the customer during delivery |
| order\_saved | Time Order was received | YYYY-MM-DD HH:mm:ss | required | Time at which order is communicated through API |
| makeline\_time | Time Order was put in oven/making | YYYY-MM-DD HH:mm:ss | required | Time at which order should be visible in Dispatch Screen |
| load\_time |  | YYYY-MM-DD HH:mm:ss |  |  |
| tent\_number | Any identifier to be used | String |  |  |
| latitude | Customer’s Location | Decimal |  | Customer\_Location\_Coordinate -  Latitude |
| longitude | Customer’s Location | Decimal |  | Customer\_Location\_Coordinate - Longitude |
| delayed\_order | If the order is delayed | 0/1 |  | If order is to be served after a couple of hours, set to 1 else 0 |
| order\_type | Select the Order Type | String |  | Planned or Express |
| slot\_start | Slot Start Time for the order | YYYY-MM-DD HH:mm:ss |  |  |
| slot\_end | Slot End Time for the order | YYYY-MM-DD HH:mm:ss |  |  |
| pickup\_otp | OTP at the Time of Pickup | Number |  |  |
| delivery\_otp | OTP at the Time of Delivery | Number |  |  |
| return\_otp | OTP at the Time of Return | Number |  |  |

Following is the description for the keys for customer object

|  |  |  |
| --- | --- | --- |
| Key Name | Description | Data Type |
| customer\_name | Customer’s Name | String |
| phone\_number | Phone Number | String |
| street\_number | Street Number | String |
| street\_name | Street Name | String |
| city\_name | City | String |
| address\_line\_2 |  | String |
| address\_line\_3 |  | String |
| address\_line\_4 |  | String |
| postal\_code | Postal Code | String |