Welcome to the 5.22 release notes. This release focuses on CO2 emissions reporting and swap consignments, along with several fixes and improvements.
What's new
CO2 emissions reporting
CO2 emissions reporting estimates each run's CO2 emissions from its planned mileage. Each vehicle starts with a default of 891.21 gCO2/km, which you can replace with the vehicle's real figure.
To replace the default value, click Settings, then click Vehicles.
You can also:
Exclude third-party vehicles from the calculation.
Set electric vehicles to zero so they show clearly in reports.
View planned CO2 above the planning timeline, with shift totals and per-run values in the table view.
Download run-level and order-level estimates from Reports.
Use the API to set vehicle CO2 values and return planned CO2 for each run.
For more information, see vehicle CO2 emissions.
Swap consignments
Swap consignments link a delivery and a collection at the same location, so both run on the same vehicle. The delivery is planned first.
On the run, the vehicle begins with the delivery's load on board and finishes at the end location once the collection is complete.
đ¤Tip: Swap suits exchanges, returns and replacements.
To create a swap consignment, you can:
Link two orders from the order card.
Set
consignmentTypetoSwapthrough the API.
đNote: CSV import doesn't support swap consignments yet.
For more information, see swap consignments.
How to access this update
This update releases on [release date]. [Add how customers receive the update, for example automatic update or update file request.]
Additional information
This update also includes the following fixes and improvements:
Increased the character limit of additional instructions to 3000 characters in the API and UI.
Increased vehicle requirements in APIv6 up to 100.
Fixed the
shiftDateFromandshiftDateToparameters inGET /orders.Fixed the On-time report so actual mileage is grouped by location.
Fixed track and trace GPS showing driver app data when linked to telematics.