What's new in Release 26.23 (November 2026) – Powerfleet Knowledge

On-Road IoT

The driver import now supports Additional driver details. The import template now includes Additional driver details columns for any custom fields added to your organization's settings. Drivers with identical full names can now be imported, and a matching name no longer blocks the import.
Toyota Halo is now supported as an OEM integration in Australia. It applies to vehicle assets with an embedded Toyota DCM, connected through the Toyota TL-OBD aftermarket device. You can now enable the Toyota Halo data connector for your organization, sync assets, and receive an email when the sync completes. Toyota Halo assets now commission as active assets and are removed from active reporting when decommissioned. Their position now displays on Live Tracking, their trips now display in Trip History, and their odometer values are now reported.

This update is for Powerfleet staff only. The Health Check page shows the status of an organization's assets.

Health Check: Clicking a failed health check (red cross) on the Health Check page now opens an Error Details modal. The modal shows the asset description and site, and a Failure Reason section you can select and copy. You no longer need to log a Salesforce investigation to see why a check failed. Support teams can now see failure details directly on this page, including organizations where the Salesforce integration isn’t enabled or supported.

The Self Service Portal now supports batch submissions, so you can submit vehicles as soon as they are assigned to bundles. Submitted vehicles are now locked and can't be edited or moved to another bundle. You can now add optional Make, Model, Year, and VIN to your vehicle import, and these details are sent to On-Road IoT and Salesforce. Admins who manage more than one organization can now choose and switch between them from a single login.