📘

To maintain the system performance, we currently restrict the date range to export reports to no more than 1 month

Compulsory Configurations

  • You need to enable the configuration Reports at both the Manufacturer and the Branch
  • You need to enable the module Report for the User group. Refer to this article: Manage Users

🚧

Report Export Permission

At the moment, only the user accounts that belong to the Manufacturer and Branch can view and export reports. User accounts that belong to the lower-level Organization Types, such as Depot, will not have this permission

Locate Report tab

  • Navigate to Reports > Report tab
  • This tab is where you can generate and export reports
18991899

Illustration (English)

18981898

Illustration (Vietnamese)

General steps to generate and export report

📘

The steps outlined below only apply to the following reports: ST02, ST04, ST05, ST08, ST09, ST10, ST12. For other reports, you will need to do additional steps

  • Step 1: Select the report: Click on the field below the text Report Type, select the appropriate report from the drop down list
464464

Illustration (English)

581581

Illustration (Vietnamese)

  • Step 2: Select the date range: Click on the field below the text Date Range, select the appropriate date range from the drop-down calendars, then click on Apply to confirm selecting the date range. Alternatively, you could input the date range directly into the field in the following format: yyyy-mm-dd:yyyy-mm-dd
538538

Illustration (English)

598598

Illustration (Vietnamese)

  • If your selected date range exceeds 31 days, there will be an error message as below. In this case, please select another date range.
19201920

Illustration (English)

19201920

Illustration (Vietnamese)

  • Note: If the language for display is a language other than Vietnamese (for example, English, Indonesian, Japanese...), the default language of reports is English.

  • Step 3: Select whether there will be a header in the report or not By default, you will see a toggle button named Exclude Report Header. When you leave this button off, there will not be a header of the report name and the date range

  • If you want to add the report name and the date range to the report, click on that switch button. When the button changes to , the text will change to Include Report Header, which means in the report there will be a header of the report name and the date range, as in screenshots below

18991899

Illustration (English)

19201920

Illustration (Vietnamese)

  • Step 4: Download the report: Click on the button Download . The system will immediately start gathering data based on your filters, and will generate a downloadable Excel template shortly
673673

Illustration (English)

876876

Illustration (Vietnamese)

ST01 - Orders By All Drivers

Information fieldDescriptionData typeUnit
"Driver Code"Management code of the driverString (text, number and special characters)_
"Driver Name"Name of the driverText_
"Vehicle Type"Vehicle typeText_
"Re-delivered order"Total unplanned orders of the previous day dragged back to current route planNumber_
"Net Re-delivered Revenue"Revenue of the previous day's total unplanned orders before discountNumberVND
"Number of Orders"Total orders in all locked/finalized route plansNumber_
"Net Revenue"Revenue from all orders (including that from all re-delivered orders) before discountNumberVND
"Total Order Weight"Total weight of the orders assigned to the vehicle. Data in this field is gathered from the total weight of the products in those ordersNumberKilogram (kg)
"Total Order Volume"Total volume of orders assigned to the vehicle. Data in this field is gathered from the total volume of the products in those ordersNumberCubic meter (m3)
"Planned Revenue"Revenue from orders in locked/finalized route plans (This is the same as Revenue displayed in the Route Plan View and calculated after discount)NumberVND
"Planned Cost"Costs from orders in locked/finalized route plans (This is the same as Costs displayed in the Route Plan View)NumberVND
"Planned Distance"Calculated distance of locked/finalized delivery routes (This is the same as Distance displayed in the Route Plan View)NumberKilometer (km)
"Planned Time"Delivery Time as planned in the Route PlanNumberHour(s)
"Actual Revenue"Revenue from successfully delivered ordersNumberVND
"Actual Cost"Cost delivered as actualNumberVND
"Actual Distance"Distance delivered as actualNumberKilometer (km)
"Actual Start Time"Actual start time of driverDate_
"Actual End Time"Actual end time of driverDate_
"Total Actual Time"Total actual time of the vehicle to deliver product.NumberHour(s)
"VFR By Trips"Vehicle filling rate by volumeNumberPercentage (%)
"VFR By Weight"Vehicle filling rate by weightNumberPercentage (%)
"Fulfilled Orders"Number of orders that have been successfully delivered by the vehicleNumber_
"Net Revenue Delivered"Revenue from successfully delivered orders before discount as actualNumberVND
"Partially Fulfilled Orders"Number of orders that have been partially delivered by the vehicleNumber_
"Unfulfilled Orders"Numbers of orders that have not been delivered successfully by the vehicleNumber_
"Not Yet Fulfilled Orders"Number of orders that have not been delivered yet by the vehicleNumber_
"Number of off-200m check-in"Number of times when the distance between the vehicle check-in's location and the store is over 200 metersNumber_
  • Calculation Formula
  • Re-delivered Order = Total Not-yet-fulfilled Orders + Total Unfulfilled Orders
  • Net Re-delivered Revenue = Number Of Cases x Case Price + Number Of Items x Item Price
  • Net Revenue = Number Of Cases x Case Price + Number Of Items x Item Price
  • Total Actual Time = Check out Time - Check in Time

ST02 - KPI Scoreboard

Information fieldDescriptionData TypeUnit
No.Numerical OrderNumber-
"Delivery Date"The date on which the Order was performedDate
(Format: YYYY-MM-DD)
-
"VFR by Trips"The average vehicle fill rate (by volume) of all tripsNumberPercentage (%)
"Truck Utilization"The ratio of the number of trucks used to Total Vehicle of all trucksNumberPercentage (%)
"Service Level"The ratio of the number of delivered orders to the number of planned orders of all driversNumberPercentage (%)
"Driver Adoption"The ratio of the number of drivers who have used Abivin App to the total number of driversNumberPercentage (%)
"Compliance Driver"The ratio of Executed Tasks over Planned tasks of all driversNumberPercentage (%)
"Delivery GPS Compliance"The ratio of the number of correctly submitted Check-in tasks (In the distance of 200 meters from the customer location) over the total Number of Check-in tasks submitted by all driversNumberPercentage (%)
"Planned Distance"The total planned distance of all vehicles (the figure can be checked in the Route Plan)NumberKilometer (km)
"Actual Distance"The total actual distance traveled by all vehiclesNumberKilometer (km)
"Kilometer Actual"The ratio of Actual Distance to Planned DistanceNumberPercentage (%)
  • Calculation Formula
  • VFR (Volume Fill Rate) = Sum of VFR of all trips/ Number of trips of all trucks
  • Truck Utilizations (%) = Vehicle Used/Total Vehicles (Total vehicles include active vehicles and inactive ones)
  • Service Level (%) = Total delivered orders/ Total planned orders of all drivers (Total delivered orders include Partially Fulfilled Orders and Fulfilled Orders)
  • Driver Adoption ratio = Number of drivers who have used Abivin App during delivery trips/Total number of drivers in the route plan
  • Compliance Driver ratio = All Executed Task/ Planned tasks of all drivers
  • Delivery GPS Compliance = Number of correct Checkin (within 200m from the delivery stop)/ Total Number of Checkin of all drivers

ST02.2 - KPI MTD Scoreboard

Information FieldDescriptionData TypeUnit
"Day"The date of the orderDate
"Depot Code"The management code of depot. This must be the same as Depot Code found in Web AppString (text, number and special characters)_
"Average VFR by Volume"The average fulfillment rate (VFR) of the vehicle by Volume of a depotNumberPercentage (%)
"Total Product Volume"Sum of volume of all products going out of each Depot each dayNumberCubic meter (m3)
"Planned Time Utilization"Average planned working time of all deliverymen from each depot (Unit: %)NumberPercentage (%)
"Actual Time Utilization"Average actual working time of all deliverymen from each depot (Unit: %)NumberPercentage (%)
"Average Transaction Time"Average service time of all truck from each depotNumberMinute(s)
"Truck Utilization"The Truck Utilization rate of each depot (Unit: %)NumberPercentage (%)
"Number of Trucks"Total number of truck belong to each depot (excluding Rent Vehicles)Number_
"Number of Used Trucks"Total number of assigned truck for each day of each depot.Number_
"Average Drop Point"Average stops on each trip of each depotNumber_
"Percentage by Value of On-Time Orders (Sponsor Item)"Percentage of orders that are executed on-time in a depotNumberPercentage (%)
"Percentage by Value of On-Time Orders (non Sponsor Item)"Percentage of non-sponsor orders that are executed on-time in a depotNumberPercentage (%)
"Service Level"The service level rate in a depotNumberPercentage (%)
"Percentage by Value of Rejected Orders (Sponsor Item)"Percentage of rejected delivery in a depotNumberPercentage (%)
"Percentage by Value of Rejected Orders (non Sponsor Item)"Percentage of non-sponsor rejected delivery in a depotNumberPercentage (%)
"Driver Adoption"The completion rate of the Drivers on ordersNumberPercentage (%)
"Planner Adoption"The completion rate of the Planners on ordersNumberPercentage (%)
"Total Adoption"The average of helper and planner compliance in executing ordersNumberPercentage (%)
"Delivery GPS Compliance"The compliance rate of the drivers on each Task within 60m of each storeNumberPercentage (%)
"Planned Distance"Total planned distance of all truck for each depot for 1 dayNumberKilometer (km)
"Actual Distance"Total actual travelled distance of all truck for each depot in 1 dayNumberKilometer (km)
"Actual/Planned Distance (Ratio)"The actual rate of the distance for each deliveryNumberPercentage (%)
"Route Plan Compliance"The compliance rate of the Route Plan OptimizationNumberPercentage (%)
  • Calculation Formula
  • Average VFR by Volume = Volume of all product going out of each Depot / Total capacity of all assigned trucks of each depot x 100%
  • Planned Time Utilization = "(A) Planned working time of each deliveryman for 1 day / working hour in driver's contract x 100%
    Result: Average of (A) of all deliverymen of each depot"
  • Actual Time Utilization = "(B) Actual working time of each deliveryman for 1 day / working hour in driver's contract x 100%
    Result: Average of (B) of all deliverymen of each depot (%)"
  • Average Transaction Time = "(C) Average Service time of each truck at each stop
    Result: Average of (C) all truck of each depot"
  • Average Drop Point = "(D) Average number of the stop of each trip, for each truck
    Result: Average of (D) of all truck of each depot"
  • Percentage by Value of On-time Delivery (sponsor items) = Percentage of on-time delivery: Sum by value of all orders completed on the planned date with sponsored items / Sum by value of all order with sponsored items x 100%
  • Percentage by Value of On-time Delivery (non-sponsor items) Percentage of on-time delivery: Sum by value of all orders completed on the planned date with non-sponsor items / Sum by value of all orders with non sponsor items x 100%
  • Percentage by Value of Rejected orders (sponsor items) = Percentage of rejected delivery: Sum by value of all orders rejected on the planned date with sponsor items / Sum by value of all orders on the planned date with sponsor items x 100%
  • Percentage by Value of Rejected orders (non-sponsor items) = Percentage of rejected delivery: Sum by values of all orders rejected on the planned date with non-sponsor items / sum by value of all order on the planned date with non-sponsor items x 100%
  • Driver Adoption = Total number of completed tasks through mobile of all deliverymen / Total number of tasks of all deliverymen of each depot x 100%
  • Planner Adoption = Total number of orders vRoute is able to plan / Total number of orders input to vRoute x 100%
  • Total Adoption = Average of driver and planner compliance x 100%
  • Delivery GPS Compliance = Number of tasks completed by driver, for POD, within 60m of each store, for all store/ total number of tasks of all deliverymen x 100%

ST03 - Orders By Single Driver

Information fieldDescriptionData typeUnit
"No."The numerical order of the Order in the reportNumber_
"Order Date"The date on which the Order should have been performed (As planned)
Same as the attribute "Order Date" of the Order
Date
(Format: YYYY-MM-DD)
_
"Driver Code"Driver CodeString (text, number and special characters)_
"Driver Name"Full name of the driverText_
"Customer Code"Customer CodeString (text, number and special characters)_
"Customer Name"Customer NameText_
"Customer Address"Customer AddressText & Number_
"Order Code"Order CodeString (text, number and special characters)_
"Salesman Code"Code of the Salesman who placed the Order (If that happened)String (text, number and special characters)_
"Order Status"Status of the Order at the time the report was generated. Possible values are: Open; ShippedText_
"Planned Total Revenue"The total revenue generated from the order as planned. Data in this field is gathered directly from the order informationNumberCurrency unit based on the attribute Country configured at the Manufacturer
"Actual Total Revenue" (*)The actual total revenue of the order. Data in this field is gathered from the amount that was manually submitted by the driver on the Mobile App.NumberCurrency unit based on the attribute Country configured at the Manufacturer
"Fulfillment Status"The delivery status of the order at the time the report is generated. Possible values are: Fulfilled; Unfulfilled; Not Yet Fulfillment; Partially FulfilledText_
"Order Unfulfilled Reason"The reason why the order could not be delivered to the customer (If that happens). Data in this field is taken from the reason that the driver selected on the Mobile AppText_
"Customer Lat"Latitude of the customer locationNumber
Format: Decimal Degrees
_
"Customer Long"Longitude of the customer locationNumber
Format: Decimal Degrees
_
"Check-in Lat"Latitude of the location where the driver submitted the task Check-inNumber
Format: Decimal Degrees
_
"Check-in Long"Longitude of the location where the driver submitted the task Check-inNumber
Format: Decimal Degrees
_
"Distance Difference"The distance between the location where the driver submitted the task Check in and the actual location of the customerNumberMeter (m)
"Planned Index"The planned index of the customer on the Delivery routeNumber_
"Task Name"The planned index of the customer plus the Customer NameText & Number_
"Signature Status"The status to specify whether the customer has signed digitally when receiving the delivery or not. Possible values are: Not yet; SignedText_
"Email Sending Status"The status to specify whether the email with the Electronic proof of delivery was sent to the customer or not. Possible values are: Not yet; SentText_
"Total Quantity"Total number of Items per Order plannedNumber
"Total Order Weight (kg)"Total Weight (in kg) per Order planned.Number
Format: Decimal Degrees
Kilogram (kg)
"Total Order Volume (m3)"Total Volume (in m3) per Order planned.Number
Format: Decimal Degrees
Cubic meter (m3)
  • (*): Calculation formula:

  • Total Quantity = Number of Cases x Item per Case + Items

  • Total Order Weight (kg) = Case Weight x Number of Cases + Case Weight x Number of Items / Item per Case

  • Total Order Volume (m3) = Case Volume x Number of Cases + Case Volume x Number of Items / Item per Case

  • (*): The data of this field is directly affected by the delivery result that the driver actually submitted on the Mobile App:

  • Actual Total Revenue = Planned Total Revenue, if the delivery result was submitted as Completed

  • Actual Total Revenue < Planned Total Revenue, if the delivery result was submitted as Partly Delivered

  • The data cell is left blank, if the delivery result was submitted as Not Completed

ST04 - Routes By Single Driver

Information fieldDescriptionData typeUnit
"Driver Code"Management code of DriverString (text, number and special characters)_
"Driver Name"Full name of the driverText_
"Planned Distance"Distance covered by the vehicle as plannedNumberKilometer (km)
"Actual Distance"Actual distance covered by the vehicleNumberKilometer (km)
"Number of Orders"Number of orders assigned to the vehicleNumber_
"Fulfilled Orders"The number of orders successfully deliveredNumber_
"Perfect Order Rate"Average rate of successfully delivered orders to number of orders assigned to a driver within a selected time periodNumberPercentage (%)
"Total Order Weight"Total weight of the orders assigned to the vehicle. Data in this field is gathered from the total weight of the products in those ordersNumberKilogram (kg)
"Total Order Volume"Total volume of orders assigned to the vehicle. Data in this field is gathered from the total volume of the products in those ordersNumberCubic meter (m3)
"Number of Off-200m"Number of times when the distance between the vehicle check-in's location and the store is over 200 metersNumber_
"VFR by Trips"Average Vehicle Fill Rate of all vehicles by all trips (either by weight or volume, the one having the greater value will be displayed)NumberPercentage (%)

ST05 - Inventory By products

Information fieldDescriptionData typeUnit
"No."Numerical order of products according to DepotNumber_
"Organization Name"Name of the DepotText_
"Product Code"Management code of product.String (text, number and special characters) _
"Product Name"Product NameText_
"Product Unit"Product UnitText_
"Inventory Begin"Number of products in warehouse of the first day in date range selects to export the report.Number_
"Inventory Purchase"Total products in Purchase orderNumber_
"Inventory Sale"Total products in Sales order(only sales order whose status is shipped) and warehouse card (-)Number_
"Inventory End"Number of products in warehouse on the last day of selected date range to export the report.Number_
  • Calculation Formula
  • Inventory Begin = On-hand Quantity at 0h of the start of the selected date range
  • Inventory Purchase = The number of products in Purchase orders with status Put Away + Total Increase in the on-hand quantity of that product during the selected date range.
  • Inventory Sale = The number of products in Sale orders with status Shipped + Total Decrease in the on-hand quantity of that product during the selected date range.
  • Inventory End of a selected date range = Inventory Begin of the date range + Inventory Purchase during the selected date range - Inventory Sale during the selected date range

ST06 - Orders And Products

  • To download this report, first follow from Step 1 to Step 3 that have been described in the section General steps to generate and export report. Then, before you click on Download, please take the additional steps below.
  • Step 4: Select Information fields: Click on the field below the text Shown Columns, then select the appropriate information fields on the drop-down menu by clicking on the corresponding check box icon . When that icon turns to , that means an information field has been selected and will be presented on the report
19031903

Illustration (English)

19031903
  • Step 5: Select Driver: Click on the Select Driver field. Scroll the drop-down menu up and down to find the appropriate driver, or you could directly input the Username/Full Name of the desired driver into the search bar, then select from the drop down menu. If you want to export report for all drivers, click on the check box Choose All Drivers
18991899

Illustration (English)

18991899

Illustration (Vietnamese)

Information fieldDescriptionData TypeUnit
"No."Numerical order of ordersNumber_
"Order Code"Management code of the orderString (text, number and special characters)_
"Customer Code"Management code of the customerString (text, number and special characters)_
"Customer Name"Name of the customerText_
"Customer Mobile Number"Mobile number of the customerNumber_
"Customer Address"Address of the customerText and Number_
"Driver Code"Management code of the driverString (text, number and special characters)_
"Driver Name"Name of the driverText_
"Vehicle Code"Management code of the vehicleString (text, number and special characters)_
"Delivery Date"The scheduled execution date of the orderDate
(Format: YYYY/MM/DD)
_
"Due Date"The actual date on which the order is completedDate
(Format: YYYY/MM/DD)
_
"Product Code"Management code of a product loaded in the orderString (text, number and special characters)_
"Product Name"Name of a product loaded in the orderString (text, number and special characters)_
"Product Weight"Weight of a whole case of a product loaded in the orderNumberKilogram (kg)
"Product Volume"Volume of a whole case of a product loaded in the orderNumberCubic metre (m3)
"Case Price"Price of a whole case of a product loaded in the orderNumberCurrency unit based on the attribute Country configured at the Manufacturer
"Item Price"Price of a single item of a product loaded in the orderNumberCurrency unit based on the attribute Country configured at the Manufacturer
"Planned Items Delivered"Quantity of single items of a product that have been planned to be deliveredNumber_
"Actual Items Delivered"Quantity of single items of a product that have been actually deliveredNumber_
"Planned Cases Delivered"Quantity of whole cases of a product that have been planned to be deliveredNumber_
"Actual Cases Delivered"Quantity of whole cases of a product that have been actually deliveredNumber_
"Order Fulfillment Status"The delivery status of the order at the time the report is generated. Possible values are: Fulfilled; Unfulfilled; Not Yet Fulfillment; Partially FulfilledText_
"Order Notes"Short note attached with the orderString (text, number and special characters)_

ST07 - Customers and Orders by date and by a single driver

  • This report is designed specifically for orders of VRP model
Information fieldDescriptionData TypeUnit
"Customer Code"Customer codeString (text, number and special characters)_
"Customer Name"Name of the customerText_
"Customer Address"Customer addressText and Number_
"Organization Code"Organization code of customerString (text, number and special characters)_
"Last Visit Date"The delivery date that is closest to the date at which users export the report ST07.Date
(Format: YYYY-MM-DD)
_
"Number of Orders"Total Number of orders assigned to a driver within a selected date rangeNumber_
"Total Revenue"The total revenue generated from the order as planned. Data in this field is gathered directly from the order informationNumberCurrency unit based on the attribute Country configured at the Manufacturer
"Actual Revenue" (*)The actual total revenue of the order. Data in this field is gathered from the amount that was manually submitted by the driver on the Mobile App.NumberCurrency unit based on the attribute Country configured at the Manufacturer
"Total Number of Visits"Total number of driver's check-ins in customers' locationNumber_
  • (*): The data of this field is directly affected by the delivery result that the driver actually submitted on the Mobile App:
  • Actual Total Revenue = Planned Total Revenue, if the delivery result was submitted as Completed
  • Actual Total Revenue < Planned Total Revenue, if the delivery result was submitted as Partly Delivered
  • The data cell is left blank, if the delivery result was submitted as Not Completed

ST08 - Trip Utilization By Vehicles

  • This report demonstrates the average amount of weight and volume that were utilized per trip by all the vehicles of the organization. This will help you manage your fleet more effectively as it can tell whether there is a vehicle having a low utilization rate so that you can make adjustments.
Information fieldDescriptionData typeUnit
"Vehicle Code"Management code of the vehicleString (text, number and special characters)_
"License Plate"License plate of the vehicleText_
"Number of Trips"Number of trips operated by the vehicleNumber_
"Vehicle Weight Capacity"The maximum product capacity by weight that the vehicle can carryNumberKilogram (kg)
"Vehicle Volume Capacity"The maximum product capacity by volume that the vehicle can carryNumberCubic meter (m3)
"Planned Total Weight"The total weight of products that the vehicle was supposed to carry according to planNumberKilogram (kg)
"Planned Total Volume"The total volume of products that the vehicle was supposed to carry according to planNumberCubic meter (m3)
"Weight Utilization"An indicator of how much product weight was carried by the vehicle compared to its capacity per tripNumberPercentage (%)
"Volume Utilization"An indicator of how much product volume was carried by the vehicle compared to its capacity per tripNumberPercentage (%)
  • Calculation Formula
  • Weight Utilization = (Planned Total Weight / Vehicle Weight Capacity) / Number of Trips x 100%
  • Volume Utilization = (Planned Total Volume / Vehicle Volume Capacity) / Number of Trips x 100%

ST09 - Total Orders By All Vehicles

  • Dispatchers can refer to this type of report to see an overview of the orders assigned to each vehicle. In this report, you can know the amount of orders along with their weight and volume in total that each vehicle was in charge of. In addition, the number of orders is also divided into four categories based on the delivery results: Fulfilled Orders; Partially Fulfilled Orders; Unfulfilled Orders; Not Yet Fulfilled Orders
Information fieldDescriptionData typeUnit
"Vehicle Code"Management code of the vehicleString (text, number and special characters)_
"License Plate"License plate of the vehicleText_
"Number of Orders"Number of orders assigned to the vehicleNumber_
"Total Order Weight"Total weight of the orders assigned to the vehicle. Data in this field is gathered from the total weight of the products in those ordersNumberKilogram (kg)
"Total Order Volume"Total volume of orders assigned to the vehicle. Data in this field is gathered from the total volume of the products in those ordersNumberCubic meter (m3)
"Fulfilled Orders"Number of orders that have been successfully delivered by the vehicleNumber_
"Partially Fulfilled Orders"Number of orders that have been partially delivered by the vehicleNumber_
"Unfulfilled Orders"Numbers of orders that have not been delivered successfully by the vehicleNumber_
"Not Yet Fulfilled Orders"Number of orders that have not been delivered yet by the vehicleNumber_

ST10 - Total Routes By All Vehicles

  • This type of report is used for collecting key statistics of the routes assigned to each vehicle. Those statistics help dispatchers to see if the vehicle went according to plan, considering its traveling distance and time. Notably, they can also be aware of the vehicle's average speed, the time the drivers spent doing their tasks on the Mobile App and the number of times when the check-in location is more than 200 meters away from the store. This report is important when dispatchers want to keep track and know the efficiency of the drivers' daily delivery tasks
Information fieldDescriptionData typeUnit
"Vehicle Code"Management code of the vehicleString (text, number and special characters)_
"License Plate"License plate of the vehicleText_
"Planned Distance"Distance covered by the vehicle as plannedNumberKilometer (km)
"Planned Time"Travelling time of the vehicle as plannedNumberHour(s)
"Actual Distance"Actual distance covered by the vehicleNumberKilometer (km)
"Actual Time"Actual travelling time of the vehicleNumberHour(s)
"Total Working Time"The duration between the time when the driver submits the "Load Products" task and the time when he submits the "End day" taskNumberHour(s)
"Actual Average Speed"Actual speed of the vehicle on averageNumberKilometer per hour (km/h)
"Number of Off-200m"Number of times when the distance between the vehicle check-in's location and the store is over 200 metersNumber-
"VFR by Trips"Average Vehicle Fill Rate of all vehicles by all trips (either by weight or volume, the one having the greater value will be displayed)NumberPercentage (%)
  • Calculation Formula
  • Actual Average Speed = Actual Distance / Actual Time

ST11 - Route By Single Vehicle

  • This type of report gathers data from a single vehicle. Therefore, after selecting the Date Range, you have to select the vehicle from which you want information
28802880

Illustration Image (English)

28802880

Illustration Image (Vietnamese)

  • The purpose of this report is similar to that of the report ST10 - Routes By All Vehicles. The only difference is that this report uses the data of a single vehicle based on each of its delivery dates
Information fieldDescriptionData typeUnit
"No."Numerical orderNumber
"Delivery Date"Delivery date of the vehicleDate (Format: DD-MM-YY)_
"Vehicle Code"Management code of the vehicleString (text, number and special characters)_
"License Plate"License plate of the vehicleText_
"Planned Distance"Distance covered by the vehicle as plannedNumberKilometer (km)
"Planned Travelling Time"Travelling time of the vehicle as plannedNumberHour(s)
"Actual Distance"Actual distance covered by the vehicleNumberKilometer (km)
"Actual Travelling Time"Actual travelling time of the vehicleNumberHour(s)
"Actual Average Speed"Actual speed of the vehicle on averageNumberKilometer per hour (km/h)
"Number of Off-200m"Number of times when the distance between the vehicle check-in's location and the store is over 200 metersNumber_
"VFR by Trips"Average Vehicle Fill Rate of the vehicle by its trips (either by weight or volume, the one having the greater value will be displayed)NumberPercentage (%)
  • Calculation Formula
  • Actual Average Speed = Actual Distance / Actual Travelling Time

ST12 - Order Status

  • This type of report displays the detailed information of all the orders within the Date Range you have selected. Apart from the key information of the order such as its weight, volume, time window or fulfillment status , here you can also have a quick overview of who the customer of the order is, which driver is in charge of the order and which vehicle was assigned to deliver the order. Thus, the important objective of the report is to let the dispatchers notice the orders that have not been delivered on time, then they can trace back to the driver who is in charge and find out the possible reasons.
Information fieldDescriptionData typeUnit
"No."Numerical orderNumber_
"Order Code"Management code of the orderString (text, number and special characters)_
"Route ID"ID code of the route delivered (containing the username of the driver and the order date)Text_
"Customer Code"Management code of the customerString (text, number and special characters)_
"Customer Name"Name of the customerText_
"Delivery Date"Delivery date of the vehicleDate (Format: YYYY-MM-DD)_
"Vehicle Code"Management code of the vehicleString (text, number and special characters)_
"Driver Code"Username of the driverString (text, number and special characters)_
"Order Weight"Weight of the order. Data in this field is gathered from the total weight of the products in the orderNumberKilogram (kg)
"Order Volume"Volume of the order. Data in this field is gathered from the total volume of the products in the orderNumberCubic meter (m3)
"Delivery Status"The delivery status of the order at the time the report is generated. Possible values are: Fulfilled; Unfulfilled; Not Yet Fulfillment; Partially FulfilledText_
"Delivery Time Window"Delivery time window of the orderNumber_
"Actual Delivery Time"Actual delivery time of the orderDate & time (Format: DD-MM-YY hh:mm)_
"On Time (Yes/No)"This field indicates whether the order has been delivered within the time window or not. The data is left blank if the order has not been fulfilledText_

ST13 - Balance Sheet By Single Driver

  • You have to select a driver before downloading this type of report as it only uses the data of a single driver
28802880

Illustration Image (English)

28802880

Illustration Image (Vietnamese)

  • Dispatchers use this type of report to know the amount of money actually collected by each driver compared to the plan. This is crucial for cases when the amount of cash collected is not equal to the amount that drivers are supposed to collect. The dispatchers can know the cause for those cases based on the delivery status of the order, or they can look into more detail by contacting the driver in charge of the order as the information of the drivers and salesmen are also stated in this report
Information FieldDescriptionData TypeUnit
"No."Numerical orderNumber_
"Order Date"The date on which the order needs to be deliveredDate
(Format: YYYY-MM-DD)
_
"Implementation Date"The date on which the driver actually started submitting tasks of the order on the Mobile app.Data in this field will be blank if those tasks are not submitted by the driverDate
(Format: YYYY-MM-DD)
_
"Driver Code"Management code of the driverString (text, number and special characters)_
"Driver Name"Name of the driverText & Number_
"Customer Code"Management code of the customerString (text, number and special characters)_
"Customer Name"Name of the customerText & Number_
"Order Code"Management code of the driverString (text, number and special characters)_
"Salesman Code"Management code of the salesman who placed the orderString (text, number and special characters)_
"Planned Total Revenue"The total revenue generated from the order as planned. Data in this field is gathered directly from the order informationNumberCurrency unit based on the attribute Country configured at the Manufacturer
"Actual Total Revenue" (*)The actual total revenue of the order. Data in this field is gathered from the amount that was manually submitted by the driver on the Mobile App.NumberCurrency unit based on the attribute Country configured at the Manufacturer
"Fulfillment Status"The delivery status of the order at the time the report is generated. Possible values are: Fulfilled; Unfulfilled; Not Yet Fulfillment; Partially FulfilledText_
"Order Unfulfilled Reason"The reason why the order could not be delivered to the customer (If that happens). Data in this field is taken from the reason that the driver selected on the Mobile AppText_
  • (*): The data of this field is directly affected by the delivery result that the driver actually submitted on the Mobile App:
  • Actual Total Revenue = Planned Total Revenue, if the delivery result was submitted as Completed
  • Actual Total Revenue < Planned Total Revenue, if the delivery result was submitted as Partly Delivered
  • The data cell is left blank, if the delivery result was submitted as Not Completed

ST14 - Delivery Statistics

  • To download this type of report, after selecting the Date Range, you have to select Salesman in order for the report to gather data information of the salesman who placed the order. You can also tick the Choose All Salesman checkbox to gather data of all the salesmen who placed the orders within the chosen Date Range
28802880

Illustration Image (English)

28802880

Illustration Image (Vietnamese)

  • This type of report will help dispatchers be aware of which order was placed by which salesman as well as the revenue generated from that order. Therefore, it will be easier to keep track of the sales figures and assess the KPIs of each salesman
Information FieldDescriptionData TypeUnit
"No."Numerical orderNumber_
"Order Date"The date on which the order needs to be deliveredDate (Format: YYYY-MM-DD)_
"Implementation Date"The date on which the driver actually started submitting tasks of the order on the Mobile app.Data in this field will be blank if those tasks are not submitted by the driverDate
(Format: YYYY-MM-DD)
_
"Salesman Code"Management code of the salesman who placed the orderString (text, number and special characters)_
"Order Code"Management code of the orderString (text, number and special characters)_
"Planned Revenue"The total revenue generated from the order as planned. Data in this field is gathered directly from the order informationNumberCurrency unit based on the attribute Country configured at the Manufacturer
"Customer Code"Management code of the customerString (text, number and special characters)_
"Customer Name"Name of the customerText & Number_
"Driver Code"Management code of the driverString (text, number and special characters)_
"Driver Name"Name of the driverText_