Importing trips from a CSV

Bulk import, what the file needs to contain, and how errors are reported.

Written for
Dispatchers
Reading time
1 min
Last reviewed
August 6, 2026

Bulk import is the normal route for standing orders and for broker files that arrive as spreadsheets. The importer validates the whole file before creating anything, so you never end up with half a day loaded.

Preparing the file

  • Export as CSV, not XLSX. Save with UTF-8 encoding.
  • Keep the header row exactly as the template names its columns — headers are matched by name.
  • Dates and times should be in your organization's operating time zone; do not mix zones within one file.
  • One row per trip. A round trip is two rows.

Running the import

  1. Open Trips and choose Import.
  2. Upload the file. It is parsed and checked before anything is written.
  3. Review the validation summary: rows that will be created, and rows that cannot be.
  4. Fix the reported rows in your source file and re-upload, or proceed and handle the rejects separately.
  5. Confirm. Created trips land in the unassigned backlog, ready to schedule.

Related

Still stuck?

Technical documentation

API references, data model, webhook payloads and integration guides — the detail behind the workflows described here. Available to signed-in Naveera customers.

Open documentation

Ask your team

Support requests are raised from inside Naveera Console, where your organization and your role are already known — which means the answer can be about your configuration rather than the general case.

Settings → Support, or ask your organization’s administrator