Data imports
Instead of registering vehicles and drivers one at a time, you can upload a list from a spreadsheet file. An import first shows a row-by-row preview with any errors, and only writes data once you approve it — nothing reaches the registry without being validated first.
Who it's for
A fleet manager or organization administrator runs imports — the same roles that register vehicles and drivers by hand in the console.
Key concepts
An import moves through four statuses: draft (the file isn't uploaded or checked yet), validated (the file has been checked, and a row-by-row preview is available), committed (the data has been written to the registry), and failed (the file couldn't be parsed, or at least one row failed validation — in which case nothing is written).
Template and supported entities
Two registries are supported today: vehicles and drivers. For each you download a CSV template with a header row and one example row — the columns match the registration form's fields exactly (for a vehicle: VIN, plate number, make, model, year, class and energy type; for a driver: name and site). You can upload the file as CSV or XLSX; if the file's headers differ from the template, you map them to the target fields when you start the import.
Validation and commit
Once the file is uploaded, the platform parses every row and checks it against the exact same rules the manual registration form enforces — including cross-references, such as confirming the referenced site actually exists in your organization. The result is a preview: a count of valid and invalid rows, and for every invalid row a list of the specific reasons. You commit an import only once every row is valid — committing creates every vehicle or driver in one operation; if the file changed in the meantime and a row is no longer valid, the whole commit is rejected and nothing is created.
In the background
You upload the file directly to object storage, and normally trigger validation yourself right after the upload finishes; if that call never lands, a recurring job running every few minutes checks for draft imports whose file has already arrived and runs validation for them on its own.