charte NVO - use of vehicles tupe & coupled to

charte NVO - use of vehicles tupe & coupled to

we use the backend in fleet to register which truck is coupled with which trailer or other unit

mceclip0.png

    • Related Articles

    • charter NVO app - start finish km's per ride

      I think the total of the kilometers per ride is very nice, but can we also note the start and finish of the kilometers? --> Not possible as we use odometer for start and end and multiple vehicles is able to drive a Dispatch, with different odometers. ...
    • charter NVO app / "office" hierarchy use to delimit contact choice in charter app segments

      By selecting a customer, can we use a category? (why? Every charter has only a few customers, it is easier to let the driver choose at 2 or 3 customers then the whole reation database. (it is important for invoicing to do this correct) We will fix. ...
    • charter NVO app - mileage logic

      add some logic to the mileage? the final mileage can never be less than the startmileage and perhaps not deviate more than 5000 km --> As we enter Start / End Km each vehicle, we will display the Start Km when enter End Km and ensure it’s not posible ...
    • charter NVO app - Translation remarks

      Translation is done. But I see it’s not possible to choose Nederlands, sorry. This will be fixed. Default will be English, as this is a shared login page. But after you choose ex. Nederlands, it will remember the chosen language in 7 days.
    • charter app NVO - temperatur logic

      All products placed in a product-group with ID ending “/!” is now required for enter a value (temp). Example “app/inventory/fruit/!” Products in a group without “/!” will still be able to enter a value, but not required. Label for the field to enter ...