In Onro, orders can be imported in bulk through the CSV samples available in the dispatcher and web app. In this article, we discuss the fundamentals of bulk import, enabling you to import large numbers of orders with just a few clicks.
To bulk import orders, you must complete the template for that order type. Certain required fields must be filled in to complete the template. You can also use your file if it contains the required column names from our templates.
Row (on-demand order type)
Customer Phone Number (dispatcher)
Pickup Address
Dropoff Address / Delivery Address
Payment Method
Payment Side
Other columns that are not required and are left empty or can be deleted from the sheet.
If you leave the COD cell empty for each order, it means that the COD of that order is 0, or there is no COD for that order.
Boolean fields must be filled with “yes” or “no” (all lowercase, case-sensitive) or left empty (you can also delete the column). The list of the boolean columns is:
Is Scheduled
Pickup Now
Draft
The “payment method” should be filled in with “cash” or “wallet” based on the method by which the order is going to be paid.
The “payment side” should be filled in with “sender” or “receiver” based on the payment side of the order. If the payment method is “wallet,” the “payment side” should be “sender.”
The date and time format should follow this pattern: YYYY-MM-DD HH:MM
Example: 2024-11-06 11:30
Dispatcher Bulk Import
A template for each order type can be downloaded and filled in to import orders in bulk from the dispatcher.
Dispatcher Samples
Customer Portal Bulk Import
A template for each order type can be downloaded and filled in to import orders in bulk from the customer web portal.
Customer Portal Samples
How to Define Custom Fields in Bulk Import
If you’re not familiar with what custom fields are and how they work, please read this guide to learn more.
For CSV imports, custom field column names are defined according to their stage and the custom field key and must follow this structure:
For the Order Creation stage, the column name should start with:
CustomField followed by the field key.
For example, 👉CustomField customer_reference
For the Pickup stage, the column name should start with:
Pickup CustomField followed by the field key.
For example, 👉Pickup CustomField pickup_notes
For the Dropoff stage, the column name should start with:
Dropoff CustomField followed by the field key.
For example, 👉Dropoff CustomField receiver_id_number
For P&D (Pickup & Delivery) orders, the Order Creation and Pickup formats remain the same. However, for the Dropoff stage, you must use Delivery instead of Dropoff.
For example, 👉Delivery CustomField receiver_id_number
For Pickup Only and Delivery Only orders, follow the same stage-based structure described above.
For custom fields of type Select (drop-down), you must enter the key of the selected option, not the label.
If a custom field type is Date or DateTime, the value must be provided as a timestamp.