Route CSV Upload

If you have a batch of orders that need to be dispatched to drivers as pre-planned routes, you can upload them all at once using a CSV file. This guide walks you through preparing your file, understanding which fields are required, and tracking the status of your upload.

Accessing the Feature

You can upload routes via CSV from two places in the dashboard.

From the Dispatch screen:

  1. Click on Dispatch in the left navigation bar.
  2. Click on Upload routes via CSV.

From the Orders page:

  1. Click on Orders in the left navigation bar.
  2. Click Bulk upload in the top-right area of the page.
  3. From the dropdown select Import Orders & Routes via CSV

Download the Template

Before preparing your file, download the official Burq CSV template from within the upload modal by clicking Download sample CSV template. The header row must be present and columns must appear in the correct order — the file will be rejected if any header is missing or out of sequence.

  • Dimensions template — uses numeric length, width, height, and weight fields for precise item and order dimensions. Required when dispatching to freight DSPs such as GoShare.

Note: Do not rename, reorder, or delete any column headers from the template. Even optional columns must remain in the file — leave them blank if unused.


CSV Field Reference

The table below covers every column in the standard template. See Route-Specific Fields for columns unique to those scenarios.

ColumnRequiredFormat / ExampleNotes
External Order ReferenceRequiredORD-001Your identifier for this order. Rows that share the same value are treated as multiple items on a single order.
Store IDConditionalstore_abc123Burq store ID. When provided, pickup name, phone, and address are auto-populated from your saved store. Required if pickup fields are omitted.
Pickup NameConditionalAcme KitchenRequired unless Store ID is provided.
Pickup Phone NumberConditional+13105550100Required unless Store ID is provided.
Pickup AddressConditional123 Main St, Los Angeles, CA 90001Full street address. Required unless Store ID is provided.
Pickup AtOptional2025-09-15T14:00:00ZISO 8601 datetime. Leave blank for ASAP pickup.
Pickup Unit NumberOptionalSuite 4BApartment or suite number at the pickup location.
Pickup NotesOptionalUse side entranceInstructions for the driver at pickup.
Dropoff NameRequiredJane SmithCustomer name at the delivery address.
Dropoff Phone NumberRequired+13105550199Customer phone number for delivery contact.
Dropoff AddressRequired456 Oak Ave, Los Angeles, CA 90002Full delivery address.
Dropoff AtOptional2025-09-15T16:00:00ZISO 8601 datetime for scheduled dropoff.
Dropoff Unit NumberOptionalApt 2Apartment or unit at the delivery address.
Dropoff NotesOptionalLeave at doorInstructions for the driver at dropoff.
VehicleOptionalcar, van, truckPreferred vehicle type. Affects which providers are shown.
Order ValueOptional49.99Declared value of the items in the order (USD).
Tip AmountOptional5.00Driver tip in USD.
Item NameOptionalBox of produceDescription of the item being delivered.
Item QuantityOptional2Number of units for this item.
Item Size (standard template only)Optionalsmall, medium, largeCategorical size. Not present in the dimensions template — use numeric dimensions instead.
Contactless DeliveryOptionaltrue / falseRequest a no-contact dropoff.
Request SignatureOptionaltrue / falseRequire recipient signature at dropoff.
Test ModeOptionaltrue / falseMarks orders as test deliveries. Must be the same value on every row in the file.
Auto InitiateOptionaltrue / falseAutomatically dispatch orders to a provider after creation. Must be the same value on every row in the file.
External Batch ReferenceOptionalBATCH-2025-09Your identifier for a collection of routes. Used for grouping and reporting only.

Route-Specific Fields

The three columns below tell Burq to group orders into a route. They work as a set — if any one of them is present on a row, all three must be provided. Leave all three blank on rows that should be created as individual orders rather than routes.

ColumnRequiredFormat / ExampleNotes
External Route ReferenceConditionalROUTE-001Your identifier for this route. All orders that share this value in the same file are grouped into one route.
External Stop SequenceConditional1, 2, 3Integer indicating the delivery order of this stop within the route. Lower numbers are served first.
External Order CountConditional3The total number of orders in this route. Must be the same on every row that shares the same External Route Reference. Route creation triggers once this count is reached.

Important: All orders for a route must be included in the same CSV file. If the actual row count for a route reference does not match the declared External Order Count, the entire file is rejected. Splitting a route across multiple uploads is not supported.

Example: A 3-Stop Route

The rows below show how three orders are linked into a single route. Each row carries the same External Route Reference and External Order Count, and a unique External Stop Sequence.

External Order ReferenceExternal Route ReferenceExternal Stop SequenceExternal Order Count
ORD-001ROUTE-00113
ORD-002ROUTE-00123
ORD-003ROUTE-00133


Uploading Your File

  1. From Dispatch, click Upload routes via CSV. From Orders, click Bulk Upload.
  2. Select your file. Click Select file or drag and drop your CSV onto the upload area. The file must be 1 MB or smaller and use the .csv extension.
  3. Click Import. Burq validates the file structure immediately. If any required headers are missing or a route validation rule is violated, the upload is rejected before processing begins and an error message is shown.
  4. Monitor processing. Once accepted, orders are created row by row in the background and routes will be created. Click View import history (via the same dropdown) to track progress and review any row-level errors.

Tracking Upload Status

Each upload creates an import job you can monitor from the Import history view. Click View import history from the Dispatch dropdown or the Orders page to see all past uploads.

StatusMeaning
in_progressOrders are still being created in the background.
completedAll rows processed successfully.
failedOne or more rows could not be processed. Click the job to see row-level error details.

Successfully created orders appear immediately in the Dispatch Unassigned Orders list. Once all orders for a route are processed, the route is created automatically and visible under Planning.

Error Reference

ErrorCauseFix
missing_csv_headerOne or more column headers are missing, misspelled, or out of order.Re-download the template and copy your data into it without modifying the header row.
missing_column_valueA required field is blank on a row. The error message names the specific column(s).Fill in the missing values and re-upload.
route_ref_order_count_mismatchRows sharing an External Route Reference declare different values for External Order Count.Ensure every row in a route carries the same External Order Count.
route_ref_rows_mismatchThe actual row count for a route reference does not match the declared External Order Count.Check that all orders for the route are in the file and the count is correct.
missing_dimensionsThe dimensions template is active but no dimensions were provided for an order.Add at least one complete set of dimensions (all four fields) to the order's first row.
incomplete_order_dimensionsOnly some of the four order-level dimension fields were provided.Provide all four — Order Length, Order Width, Order Height, and Order Weight — or leave all blank.
incomplete_item_dimensions_csvOnly some of the four item-level dimension fields were provided.Provide all four item dimension fields or leave all blank.
dimension_level_mismatchOrder-level dimensions were provided on a subsequent row of the same order (not the first row).Order-level dimensions may only appear on the first row of each order.
invalid_dimension_unitThe value in Dimension Unit is not recognised.Use one of: in, cm, or ft.
invalid_weight_unitThe value in Weight Unit is not recognised.Use one of: lb, kg, or oz.
cannot_parse_csvThe file could not be read as a valid CSV.Open the file in a spreadsheet app and re-save it as plain CSV (UTF-8 encoding).