New! Transflo Mobile+ 6.7 Release Notes

In Release 6.7, drivers can now use the native built-in Share functionality in Android and iOS to upload a document file. Instead of opening Transflo Mobile+ first and then remembering where they last saw a load document file such as a BOL or fuel receipt, drivers can simply go to any load document or image file and tap the Share button or menu item to upload it through Transflo.

With native mobile operating system (OS) file sharing (native meaning originating in the mobile OS as opposed to a proprietary feature in any single app), users can select the Transflo Mobile+ app as the destination for any file on their device that they want to share (and ultimately submit to any preset fleet ID or broker ID). The shared document (for example, a fuel receipt PNG image or a BOL PDF file if supported by your fleet) is now ready to join any additional uploaded files and new photos in your next submitted batch of load documents.

To learn more about this new ability to share a file directly on your phone or tablet as an alternative way to upload it into the latest Transflo Mobile+ app, see New! Share a Load Document with the Mobile+ App.

Release 6.5 introduced a new scanned image auto-save-to-gallery feature that received mixed responses from our users. Some users liked the convenience of having copies of their recently submitted load documents on their local device. They could keep them temporarily and remove them at a later time. However, a majority of users did not want their recently scanned images taking up additional storage space on their phones or tablets.

Although subject to change, Release 6.7 will undo the auto-save to my gallery behavior on Android devices and no longer save copies of recently scanned document images among your local device files.

Apple iOS users will no longer receive the following message:

New images were saved to your gallery during the previous session. Do you want to delete them from the gallery?

Both iOS and Android users can always view your sent documents again up to 2 days (48 hours) later in the document queue on their local device and up to 14 days later in the cloud. Go to transfloexpress.com and enter your confirmation number. The Status column shows Delivered when all load documents have been submitted.

Additional bug fixes and enhancements were made to improve app behavior and functionality on smartphones and tablets running release 15 of the Android mobile operating system. A future release of Transflo Mobile+ will target improvements to better support Android 16 devices. Many of these developer verification requirements and best practices are established by the Google Android platform team and implemented by Transflo to promote quality, compatibility, performance, and security.

Additional bug fixes and enhancements were made to improve app behavior and functionality in a special 6.7.1 update for iPhones and iPads running iOS.

Release 6.7 also includes additional enhancements and fixes to improve the overall stability and performance of the app on both iOS and Android devices.

Starting with Release 6.7, the Mobile+ app will gradually introduce drivers working at select fleets to the new features in Transflo User Workflows (also known as Loads 2.0 as distinguished from the original load features, known simply as Loads 1.0, classic loads, or legacy loads).

The classic features in Loads 1.0 will be upgraded to a completely new and improved Loads 2.0 driver workflow experience in phased migrations from November 2025 through June 2026.

• As a fleet manager, you will receive an initial e-mail notification about your migration timeline from Transflo.

• By the end of your fleet-specific cut-over period (late 2025 or early 2026), your drivers will now be using the new Transflo Load Workflows 2.0 features on their Mobile+ app to manage all the required and optional steps to deliver their loads, run less-than-load (LTL) routes, submit load documents, and complete any other assigned steps.

• To learn more about the Load Workflow 2.0 in-app features, design studio, API, and SDK for drivers, fleet administrators, and system developers, see the New! Transflo Loads 2.0 KB.

• As a driver, contact your supervisor to determine when your fleet will upgrade from Loads 1.0 to Loads 2.0. As a general rule, use the KB articles that match the screens and steps you see in your Mobile+ app, either Loads 1.0 or Loads 2.0 (user workflows).

• As a fleet driver, the app will continue to fully support Loads 1.0 until you finish your last load in the legacy screens and are automatically migrated to the new Loads 2.0 screens.

• You do not need to do anything to get the new features. Everything is made available to you in alignment with your fleet.

• White label apps such as Crete, KLLM, Decker, Averitt, and many more as well as tablets running the in-cab edition will continue to use the same trusted Loads 1.0 features until they are updated to Loads 2.0 in Summer 2026.

Traditional radial geofences—where a preset radius of say 300 yards was used to define a circle at or near a driver destination—are now considered somewhat lacking in precision. Older radial geofences are still supported but can sometimes be inaccurate and leave too large a margin of error, especially when the point-of-interest (POI) location or site is particularly large.

This release allows ELD fleet customers to use more precise new Geotab polygon zones in new driver workflows. Key benefits include:

• More accurate automated arrivals and departures.

• More precise nested geofences for specific areas within a yard or site.

• Geofence areas can now be configured with multiple points, allowing for complex shapes.

Fleets can use both radial or circular geofence shapes and polygons:

• Circular Shapes: You set the radius around a point on a map or a street address. For example, 300 yards.

  Example A:

  

• Polygons: You draw a custom shape to define the geofence around a building, terminal, or site.

  Example B:

  

You can create your geofence zones manually on the map or import them using a template in Excel or a similar spreadsheet. To get the most value out of your geofences, don't forget to use the geofence triggers in your load workflow steps and actions in Transflo Loads 2.0.

To learn more, see New! Define Geofence Polygon Borders Around a Location.

The new features implemented in this special edition will continue to be considered BETA software. This KB article describes new features under development in the 2025-2026 pre-release BETA edition of Transflo Loads Workflow 2.0. All KB articles are subject to change with or without notice and will be updated to align with future product development. When calling Support, be sure to identify your company fleet and type of handheld device.

The Mobile+ app has been configured to support one or more major new fleet customers with integrated mobile hardware running Android OS. Geotab log-in credentials are used for authentication to both Transflo Mobile+ and Geotab ELD, HOS, and Telematics features.

When drivers are prompted to log in on special pre-configured Honeywell handsets, instruct them to enter their Geotab user ID and password and then tap Login.

Example: This example shows the new Loads 2.0 workflow and user login features in Transflo Mobile+ R6.7 embedded edition running on a mobile handset engineered for freight shipping and delivery personnel.

As a driver, your user ID should be the same for your Transflo Mobile+ and Geotab HOS/ELD registrations. Use the same user ID and password for those two (2) separate driver accounts. Later, when you tap HOS Login, an easy single-sign on (SSO) process automatically authorizes you and logs you in based on the User ID you already entered when you logged in to the Mobile+ app.

To learn more about this special edition of Release 6.7, see New! Transflo Mobile+ 6.7 Embedded Handset Release Notes.

In June 2025, Transflo introduced a new platform service that automatically synchronizes assets between Geotab and Drivewyze removing hours of manual data upkeep. Although this feature is not exclusively a Mobile+ app feature, it is listed here because it is related and certainly welcome in eliminating the prior manual spreadsheet process.

In September 2025, the new service was updated (coinciding with Release 6.7). Because it was cumbersome to update drivers and vehicles with manually uploaded spreadsheets, Transflo developed a Cloud Agent service that automatically pulls driver and vehicle information from Geotab and pushes it to Drivewyze.

Drivewyze covers 900 sites in 47 states and Canada and is available in the Mobile+ app. To learn more, see Drivewyze in the Transflo Mobile+ App.

The Scheduler feature has always provided a convenient way for fleets to schedule calendar events for drivers and for drivers to organize their own work and personal events. In this release, a new Scheduler API opens the Scheduler to allow optional integrations with external systems.

For example, your fleet can remind drivers about various required appointments, maintenance activities, and other types of events configured by your fleet administrator. Examples include load assignments, fuel reminders, calls, rest, maintenance, truck wash, submit paperwork, HR compliance, and personal events.

As a driver or dispatcher, to learn more about the in-app Scheduler, see Scheduler Event Calendar.

As a developer or fleet administrator, to learn more about the Scheduler API, follow these steps:

1. Navigate to https://svc.transflomobile.com/integration/sdk

2. Choose Scheduler API in the drop-down menu.

3. Click the Explore button.

New McLeod integration options from Transflo offer improvements for carriers, fleet drivers, brokers, and back-office staff.

New McLeod integration API support has been added to the Transflo Mobile+ app and Transflo Workflow AI platform to help drivers and back-end staff manage load documentation.

• Drivers can send load documents through the Mobile+ app (using the same trusted steps they always used) and back-end staff can be confident these loads and all associated documents are received and processed through both Workflow AI and legacy McLeod systems.

• By leveraging the legacy McLeod API endpoints, Transflo Mobile+ drivers and Transflo Workflow AI clerical office staff users enjoy seamless integrated document processing.

 This API integration functionality is considered a BETA feature at this time. To explore accelerated product implementation opportunities to leverage these new capabilities, contact our New Product BETA Sales and Professional Services teams.

In addition, the Transflo Mobile+ app offers limited new integration options with the comprehensive McLeod TMS platform for optimized freight management. In this release, to help McLeod users migrate to the new Symphony Mobile Communications Service (SMCS) API from their legacy brokerage API, Transflo has created an integration API between the Transflo Mobile+ app and the new McLeod Symphony API.

As a user of both Transflo Mobile+ and the new McLeod SMCS API, with the proper integrated implementation and configuration settings, you can now perform the following actions:

• Automatically create and update loads in your McLeod environment and reliably make them visible for drivers to deliver in their Transflo Mobile+ app.

• Drivers can use the Mobile+ app on their phone or in-cab tablet to send and receive messages with dispatchers.

• Dispatchers can send and receive these messages in their McLeod systems.

 This API integration functionality is considered a BETA feature at this time. To explore accelerated product implementation opportunities to leverage these new capabilities, contact our New Product BETA Sales and Professional Services teams.

To support both common and unique customer concerns about safety, compliance, and general FMCSA form and manner Form and manner is a common type of FMCSA violation category where a driver or carrier might have omitted or made errors in their Records of Duty Status (RODS) or hours-of-service (HOS) data such as missing dates, locations, mileage, trailers, shipping document numbers, or signatures. To minimize your compliance risk, carriers must establish safety management controls and procedures to ensure that drivers comply with HOS requirements as set forth in 49 CFR Part 395. Your safety management system must ensure that your drivers comply with HOS requirements and do not exceed maximum driving times. You must establish safety management controls and procedures to require drivers to prepare and submit records of duty status and associated supporting documents as required, ensure that driver records of duty status are checked, ensure that your drivers are not violating HOS requirements, ensure drivers do not falsify records of duty status, and ensure that each driver accurately completes records of duty status in the form and manner required under 49 CFR Part 395. requirements, the following improvements are now available or will soon be available in various integrated back-end updates and the newest Transflo Mobile+ app:

• To reduce driver data entry errors, the Mobile+ app can leverage API calls to pull TMS data that will, in turn, populate several fields in E-Trip Sheet, Detention, and other forms.

• The Mobile+ app has been enhanced for select customer fleet configurations to support Depart Shipper, Empty Load, and other new custom forms.

• To reduce the amount of time drivers spend manually entering data and to reduce potential data-entry errors, the Mobile+ app can now support one or more new web forms that retrieve data from integrated internal and external systems. The integrated data is used to pre-fill field values on in-app forms to assist drivers.

• To assist certain customer fleets improve the accuracy of their trailer and shipment information, the Mobile+ app can support an expanded set of new in-app driver forms including Begin Trip, Depart Shipper, Empty Call, notification forms for Relay, Pickup Trailer, Dropped Trailer, and more.

• Many of these new form and manner requirements for drivers and fleets can be automated in the new Transflo Load Workflow 2.0 solution.

• These evolving new features are carrier-specific and are likely to be phased over the next few releases, for example, 6.7, 6.7.1, 7.0, or 7.1. To learn more, work with your Transflo Customer Success Manager (CSM).

When the Allow Single Load In-Transit setting is enabled for your fleet, load data will be accessible to help drivers when completing on-screen forms. In previous releases, drivers often input incorrect data by mistake when filling out forms on the main dashboard or other places in the app that are not directly on the load.

This feature offers the following benefits:

• Adds ability to retrieve data for auto-populating webforms from the dashboard with active load data.

• Adds options for forms to be on the dashboard where they are easily accessible.

• Reduces driver error.

This feature (also known as Auto Population of Forms from Active Loads) might or might not be available to your fleet at this time. It is associated with the new user workflows. As of November 2025, your fleet might not have transitioned to the new user workflows (also known as migrating from Loads 1.0 to Loads 2.0).

When this feature is enabled, select web forms in user workflows and menu items as seen on the Home screen or Dashboard can be pre-filled with load details for the currently active load with no driver intervention required.