Why Did My Turo Reservation Import Fail?

A reservation import can fail even when the CSV opens correctly in a spreadsheet — import systems validate structure, required identifiers, dates, amounts, and relationships that spreadsheet software simply doesn't check. One real, specific version of this: Kelviz's own mapping step will block validation with "Map required field(s): …" until every field marked required has a column assigned, and rows the system can't tie to a fleet vehicle come back flagged "unmatched vehicle" rather than silently dropped — see Common errors and how to resolve them for the exact current message text.

Start with the import record itself

Check the file name, file type, upload time, row counts, rejected-row count, duplicate count, and error status — and preserve the failed source file rather than editing it in place, which destroys the evidence you'd need to explain what actually went wrong.

Check the common causes before assuming corruption

Wrong report or export format, missing headers, renamed or reordered fields the importer doesn't recognize, invalid date or currency values, blank reservation or vehicle identifiers, mixed encodings or broken delimiters, a file truncated mid-download, a provider or Turo format change, or — simplest of all — the same file already being processed once.

Test a clean re-export, and compare row-level errors

Download a fresh source export rather than opening and resaving the failed one first — spreadsheet applications routinely mangle dates, leading zeros, encodings, and identifiers on save. If some rows succeed and others don't, inspect the rejected ones for a pattern; one malformed value doesn't mean the whole file is unusable. When you do need to escalate, provide the file type, import time, error message, affected row numbers, and a redacted sample — never send unprotected guest or account data along with a support request.