FAQ

Yes. The app doesn’t just import any arbitrary CSV file — it expects a specific CSV schema.

CSV import template file: watch_import_template.csv

Important:
The headers/field names must exactly match the expected format.
If the headers don’t match, the import will be rejected.
For each record, at least the mandatory fields Brand and Model name must be filled in; otherwise, that row will be skipped.
Incomplete rows are also skipped.

Regarding new or unknown options:
For many dropdown fields, the app also accepts values that it hasn’t seen before.
Such new values are automatically added as new field options during import.
This also applies, for example, to new complications or other new values in supported dropdown fields.
So, in those cases, the dataset is not rejected outright.

Limitation:
Labels are not automatically created. If a label from the CSV doesn’t yet exist in the app, it will be skipped and not imported.
Collections are also not automatically created — an assignment only works if the collection already exists.

What about the ID field? Can it be empty, or is it required?
The ID column must exist, because the app recognizes the CSV structure via the fixed header layout.
However, the value in the ID cell itself can be empty:

• If the ID is empty, the app automatically generates a new ID.

• If an ID is present and already exists in the app, the existing record will be updated instead of created anew.

• If an ID is present but not yet known, a new record with that ID will be created.

In short:

• ID column: required

• ID value per row: optional (can be empty)

Does the field order have to be maintained?
Yes. The order of the fields must be maintained.
The app doesn’t flexibly recognize fields just by name — it checks the headers at their expected positions.
That means:

• Same field names but in a different order → import error

• Therefore, it’s recommended to use a CSV exported from the app itself as a template.

Summary:

• Headers must match exactly

• Column order must match

• Unknown values in many dropdown fields are automatically adopted

• Labels and collections are not automatically created

• ID column must exist; ID value may be empty