Updates: what’s new in January 2021

15 February, 2021
Tatsiana Bravina
January update

The year is young, and we decided not to waste time and did our best to let the Wialon community enjoy the major updates. Well, firstly, just recently we have successfully launched the Wialon help center: a unified knowledge base about the products and the company. We welcome you to come in, test a new resource and tell the others how helpful it is!

Secondly, today we traditionally invite you to thoroughly examine a detailed recap of the new features released in January. Please note that for a month, our team has been working on improving the functionality of Wialon applications. The system update this time remained invisible for a common user.


Fuel data on the service unit page 

Now the app users have access to summary information on fuel consumption. The Total cost of fuel option becomes available when clicking on the Total cost of services field on the Unit info tab.

If the Total cost of fuel value is selected, the Cost per 1 liter value is available by default.


With this new option added, the user can have information on fuel costs for a particular unit.

The reports by fuel fillings 

We have added the options "By fleet refueling" and "By refueling facility". They can be found on the Reports tab in the Report type field.


The new features provide users with summary information on fuel fillings, which is essential for summing up the results for a certain period and fuel costs’ planning of fuel costs.

The reports fuel fillings can be exported from the reports' page and received to the user's emails according to the administration panel's settings. These options will allow users to access reports outside the application.

Find more details on Fleetrun new features in this forum topic.


Multiple reports’ improvements

We have modified the reports. Below you’ll find the details. 

  • No Actual fulfillment time column 

Previously, it was not clear what time exactly is displayed in this column. Thus, the actual fulfillment time could be visit time, confirmation/rejection time, or exit time. The truth is that different users mean different things when we say "fulfillment". For some of them, it is the moment when the order is being delivered to the client; for other ones, it is the arrival at the destination or the moment when unloading starts, etc. Given that there are separate columns for all events, and the subjective nature of the fulfillment concept, the Actual fulfillment time column is no longer needed.

  • Unloading time has been renamed into Service time

As a rule, at the delivery point, the driver not only unloads but also performs a number of other processes typical for each business. Thus, to make the parameter name more appropriate, it has been changed.

  • New columns

Delivery interval from/to. The beginning and end of the interval within which the driver should fulfil the delivery;

Actual time to point. The actual time spent on covering the distance between the previous and current destination points;

Estimated departure time. The time when the driver should leave the delivery point (system calculation);

Estimated service time. The time that the driver should spend at the delivery point, including time for unloading goods, charging the client, and so on (system calculation).


Please note that the new columns are also available in detailed reports. The new columns can be exported in both XLSX and PDF formats, and are available for printing.

Thanks to the new columns, the users will be able to get more delivery information and, as a result, improve the analysis quality by comparing the key delivery targets with actual data. Please consider that by reducing just a couple of minutes of service time on each request, you can significantly reduce costs.

  • Improved filtering in reports 

The following options appeared in the settings in the report navigation panel:

  • visited;
  • not visited;
  • visited on time;
  • visited late.

These new parameters are the result of the report modifications we featured above. 

  • New algorithm for visit time determining 

Now, if the driver has not visited the order (the unit is to send a message at zero speed within the order delivery radius), then the data in specific columns ("Deviation", "Actual mileage", "Actual time to point", "Fuel consumed", columns with temperature) will not be displayed. Thus, the events on the order will be reflected most accurately.

  • The same set of columns for both detailed and basic reports

A detailed report consists of 32 columns. The basic report has 24 columns. “By driver” is the only one report type without the Driver column.

  • Modified statistics logic 

With no “fulfillment time” concept in use, we have specified the visit and the confirmation/rejection of orders. And now the order that the driver actually visited is considered as the visited one. Thus, statistics has become more user-friendly.


New map layer

We have added a new map layer – "OpenStreetMap". The option is available by default. 


Visit the forum and read more about the new Logistics options. Please share your experience with the updated functionality.


New layout of the potential cultivation registration page 

We have made some changes in the layout of the potential cultivation registration page:

  • the field name is now in the page header;
  • the field area is indicated in brackets next to the field name;
  • the fuel rate is now in the Consumables block;
  • the option to select several drivers per cultivation. In this case, if one driver is selected, then his name is shown in the field. If several drivers are selected, the user sees the number of drivers displayed as, e.g. "Drivers: 2". Find their names in the block tooltip.


You will also notice some other slight adjustments in the layout. Now all the most relevant information is available within one screen, and the user does not need to make any additional scrolling.

 Please note that the Consumables block will not be displayed in the registered processing if the fuel rate is not specified during registration.

New time option in the Working day starts at section 

Following the users’ requests, we have added a new time option – 6:30 in the Working day starts at section.


New deletion procedure for crops and operations 

We implemented safe deletion of crops and operations. Now, when deleting a crop/operation, the system will check if the crop/operation is involved in cultivation.

If the crop/operation is involved in at least one cultivation, before deletion, the system will require an additional confirmation from the user, warning about the possible consequences.


This additional confirmation will protect users from accidentally removing crops/operations from registered cultivations.

New grid technology in table reports 

The report tables have been converted to CSS Grid Layout, a modern interface design system implying that a web page is easily divided into columns and rows. As a result, the application users see consistently styled report tables with more readable content, making working with tables faster, easier, and more enjoyable.

Find more on the new features, as well as comment on the app functionality and user experience on the Wialon forum.

In a month, you will find February new features’ recap. Still, now we encourage you to test the applications’ new functionality added in January and leave your comments on the Wialon forum.

Kindly remind you that we have recently launched the marketplace, a comprehensive catalog of Wialon-based applications and integrations with third-party systems. Visit the marketplace to find the right solution and get inspired for implementing unique projects.

Tatsiana Bravina
Tatsiana Bravina
Tatsiana is the Content Marketing Specialist at Gurtam who writes about subjects valuable to the Wialon community. She creates blog content, product presentations, and printed materials that our partners use in their business activities.


Related articles