These optional fields are used to calculate duration of ownership as well as any depreciation or appreciation costs. For length of ownership, you must provide a Purchase Date, if Sold Date was not provided, LubeLogger will calculate the amount of days between the current day and the Purchase Date as length of ownership. If both Purchase and Sold Costs are provided, LubeLogger will calculate any depreciation / appreciation costs as well as the cost per mile and cost per day. These data will show up in the Vehicle Maintenance History Report under its own section.

The multiplier that will be applied on the record's odometer field. Primarily used for vehicles where the odometer uses a different unit compared to the user's settings. E.g.: A user residing in the U.S. or U.K. which uses miles as the distance unit imports a vehicle that uses kilometers(Kei trucks, motorcycles, etc).

The user will have to enter 0.621 as the odometer multiplier to convert kilometers to miles. When the user creates a new record, they can just enter the reading off the odometer in the vehicle(i.e.: 15000 km) and the app will automatically convert it to 9315 miles when the record is being saved. In the opposite scenario where a user imports a vehicle with miles as its distance and they use kilometers by default, they will have to enter 1.609 as the odometer multiplier.

Note that this field has a limit of 3 decimal places.

This is primarily used for vehicles where the dash cluster was swapped out and hence the odometer no longer reflects actual mileage. E.g.: The user swapped out the dash cluster when their vehicle had 200000 miles but the new dash cluster only has 15000 miles. The user will have to enter 185000 as the odometer difference. The next time the user creates a new record, they can just enter the reading off the odometer in the vehicle(i.e.: 17500 miles) and the app will automatically add 185000 to the odometer field when the record is being saved. The user can also input negative values in here if the new dash cluster has more miles than the user's original odometer.

Note that this field only takes in whole numbers(no decimals).

Note that in the event the user has a negative odometer difference, the record will not save if the odometer field falls below 0 after applying the odometer difference, it will throw a validation error.

The app will always apply the odometer difference first before applying the multiplier. Therefore if a dash cluster swap was performed the user must input the converted odometer difference.

To copy collaborators from one vehicle to another, simply navigate to the garage tab, drag and drop the vehicle you wish to copy the collaborators from onto the vehicle you wish to copy collaborators to. You will be prompted for confirmation and the collaborators will be copied over.