How to Create Orders in Bulk via CSV Upload Template

Line #

COLUMN HEADING

DESCRIPTION & BEST PRACTICES

EXAMPLES

WHY USE IT?

2

Customer_Address_part 1

Street, suburb, city, state, zipcode altogether

111 Oakbirch Street, Chicago IL, 60603

Any order orchestration platforms must know the driver's current location, as well as the location of their destination (e.g. store, customer home, etc). Use this field to send the customer address to Bringg all in a single field. Bringg will use it to calculate ETA's, manage your customer's expectations, and allow drivers to open their preferred navigation app from within the Bringg app. 

If you want to add customer address in multiple cells, in this cell include only the first part of the address e.g. Street

3

Customer Phone Number

The phone number should only contain numbers. Best practice is to include the plus sign and the country dialing code, but it should work if you leave this out.

Use this field to ensure Bringg can share delivery updates with the recipient (e.g. "your driver is on the way, click here to track") and allow the driver to call the customer as needed.

4

datetime_tz

This is the scheduled date-time for the order delivery. Please provide a time as well, otherwise it will be defaulted to 00:00.

Best practice is to use the format Day-Month-Year for the date, and 24 hour clock for the time.

25-08-2020 18:00;

25/08/2020 05:45;

2020-08-25 13:00

Use this field if you know exactly when the driver is expected to arrive to the customer. This data will be displayed for both drivers and dispatchers. Bringg will notify both on any lateness, ensuring the proper action is taken and customer expectations are managed in a timely manner.

5

Task_Note

Notes that the customer has specified. Instructions to the driver.

Leave order at the door

Customers often share specific delivery instructions, which must be relayed to drivers. For example, customers may request the driver not ring the doorbell in order not to wake a sleeping baby. This data is displayed to dispatchers & drivers, ensuring the customer's wishes are respected.

6

Team_ID

If you're dispatchers/stores are divided in teams (=geographical areas they deliver to), be sure to pass this data along to Bringg. This will ensure Bringg only show your dispatchers data that is relevant to them, e.g. a dispatcher only assigned to the "Chicago North" team will only see orders & drivers assigned to that team, and nothing else.

7

External_ID

The ID of the order in your system

123456; STH-3546

If your system provides a unique ID for every order, you can send it along to Bringg with the rest of the order information. You can use these external IDs to query order data on Bringg using your own system's IDs without having to keep track of Bringg's order IDs.

8

Title

This can be a description of the order, a title that helps the driver.

If your business refers to orders by particular data (e.g. the customer's name), send this data to Bringg as the order title. The order title appears across the Bringg platform, ensuring your staff are always on the same page when discussing particular orders. More importantly, we follow your lead as to what an order's title is, making it easy for staff to move from your native system to Bringg.

9

Customer Email

Email address of the customer

BringgNow@email.com

Use this field to ensure Bringg can share delivery updates with the recipient (e.g. "your driver is on the way, click here to track"), as well as get rated for their delivery experience.

10

address_second_line

Second part of the address. Depending on how your addresses are structured, this could be the Suburb or the Town/City.

Chicago, IL

See line 2.

11

Zipcode

Zipcode or Postcode

60603 

See line 2.

12

Customer_Address _Part 3

Third part of the address. Depending on how your addresses are structured, this could be the Town/City or State.

IL

See line 2.

13

no_earlier_than_tz

If you have a delivery time window instead of a specific scheduled date-time, then specify the start of the window here.

Best practice is to use the format Day-Month-Year for the date, and 24 hour clock for the time.

2020-08-25 13:00 

Use this field if you promise customers their driver will arrive within a certain delivery window. Specifically, this field should contain the start of the delivery window. Bringg will display this info to relevant drivers/dispatchers.

14

no_later_than_tz

If you have a delivery time window instead of a specific scheduled date-time, then specify the end of the window here.

Best practice is to use the format Day-Month-Year for the date, and 24 hour clock for the time.

2020-08-25 14:30

Use this field if you promise customers their driver will arrive within a certain delivery window. Specifically, this field should contain the end of the delivery window. Bringg will display this info to relevant drivers/dispatchers, and notify both if a driver cannot deliver to your customer by the end of the promised delivery window.

15

wp_position

Always Use wp_position = 2 this corresponds to the final destination being the customer address

When sending orders to Bringg, the data must include the stops (aka way points) that the driver is expected to fulfill. In case there are more than one way point, you must specify the order of the way points using the "way point position" field. Specify which way point is in the 1st, 2nd, etc position, allowing Bringg to present the information to your drivers correctly and ensuring no driver completes way points without regard for the intended order.

16

total_price

Provide drivers with the total price of the order using the "Price" field, enable them to collect payment directly from customers.

17

Inventory_Title

If your business refers to inventory items by particular data (e.g. the name of the meal, make+model, etc), send this data to Bringg as the inventory title. The inventory title appears across the Bringg platform, ensuring your staff are always on the same page when discussing particular inventory items. More importantly, we follow your lead as to what an inventory title is, making it easy for staff to move from your native system to Bringg.

18

Inventory_Quantity

When delivering goods of any kind, your drivers must know the quantity of which goods they are expected to deliver. This aligns your drivers knowledge with your customers expectations, and ensures no misunderstandings occur on site. More importantly, providing precise inventory data allows Bringg to notify your drivers if an item is missing, or is still due to be delivered.

19

Scan_ Code

Providing Bringg with inventory scan codes (if they exist in your native system) ensures your drivers will never mistakenly load or deliver the wrong item, and allows drivers to scan items at any time for identification or other purposes.