Release Notes 3.0 (pending)

Release Notes 3.0 (pending)

Release Date

Hub, API, and mobile app:

May 29, 2025

Bug fixes.  

New Features

Key

Summary

Description

Key

Summary

Description

IBALDEV-6464

IBALDEV-6466

IBALDEV-6473

IBALDEV-6706

Hub:

  • Redesign of Subscriptions page.

  • Returning of Free level.

  • Returning ads for Free level.

  • Possibility to turn on Free level again once subscription expires.

  • Renaming paid levels to Pro, Advanced, Enterprise.

  • Limiting access to features depending on subscription level.

Subscriptions page in Hub has been redesigned to highlight the key benefits of each paid level. You can now explore in details which features are available on both the mobile app and the web-based Hub across all levels. We also offer three paid subscription levels: Pro, Advanced, and Enterprise. Here’s how the changes will affect existing customers:

  • Customers on the Essential level will be moved to Pro.

  • Customers on the Advanced level will remain on the same level.

  • Customers on the Premium level will be moved to Enterprise.

  • Customers already on the Enterprise level will remain unchanged.

No action is required. These updates will be applied automatically.

Additionally, we're bringing back the Free level. If a subscription expires, you can choose to extend it or continue using Geo2 for free with one user per organization. Free level is supported by ads.

Learn more about subscriptions in Geo2 Hub.

IBALDEV-6484

IBALDEV-6488

Mobile app:

  • In-app purchasing.

  • Limiting access to features depending on subscription level.

Subscriptions can now be purchased directly within the mobile app - 1-user Pro and Advanced subscriptions. These app-based subscriptions are managed through your device and app store settings, but the benefits apply across the entire Geo2 platform, both mobile and web.

IBALDEV-3907

Mobile app: Creating organization and environment during account registration.

If you register a new account in the mobile app and you haven’t been invited to any existing organization, a new organization along with its first environment are automatically created in the background. Default settings are applied, including display preferences, route settings (such as default start time and stop duration), templates for Public tracking and POD emails, as well as failure reason codes for POD's.

IBALDEV-3981

Mobile app: Redesign of Settings layout. “Routes” settings.

You can now customize display preferences such as units for distance, weight, and length, adjust route settings like default stop duration and route start time, enable vehicle checks on route start and completion, and easily contact our Support Team by submitting a form when needed.

IBALDEV-4896

Mobile app: “Vehicles” setting.

Inside the app, by pressing Settings → Vehicles, you can add, edit, or delete vehicles. When adding a new vehicle, you can enter details such as its key, registration number, vehicle type, and dimensions including gross weight, height, width, and length. Vehicle measures will be used to avoid height-restricted bridges, narrow roads, and weight-limited areas during route optimization and calibration.

Learn more about “Vehicles” setting in Hub.

IBALDEV-3979

Mobile app: “Failure reason codes” setting.

When a new environment is created, default failure reason codes are automatically generated. However, you can customize them at any time by going to Settings → Failure reason codes in the app. There, you can add new codes or update existing ones by specifying a code (shown on the Create POD and POD history pages) and description (for internal usage only).

Learn more about “Failure reason codes” setting in Hub.

IBALDEV-3977

Mobile app: “POD notifications” setting.

In Settings → POD notifications within the app, you can edit the email templates sent to recipients for both successful and failed POD's, as well as enable or disable these notifications. You also have the option to use tokens such as order key, recipient name, and POD tracking link which will be automatically replaced with real data when the email is sent.

Learn more about “POD notifications” setting in Hub.

IBALDEV-3978

Mobile app: “Public tracking notifications” setting.

In Settings -> Public tracking notifications within the app, you can edit email templates sent to recipients for order live tracking, as well as enable or disable these notifications on different route statuses. You also have the option to use tokens such as order key, recipient name, and public tracking link which will be automatically replaced with real data when the email is sent.

Learn more about “Public tracking notifications” setting in Hub.

IBALDEV-6411

Mobile app: “Users” setting.

In Settings → Users within the app, you can invite new users to your organization (and its environment), as well as edit or remove existing ones. To invite a user, simply enter their full name, email address, role, and assign a subscription. When editing a user, you can update their role and modify or remove their subscription.

Learn more about inviting users to your organization Hub.

IBALDEV-6430

IBALDEV-6436

Mobile app: Improved address input for orders and POD’s.

On Create/Edit order and Create POD pages, you can find the Recipient address field. Click on it and simply start typing an address. Suggestions appear as you type, so there’s no need to enter the full address manually. If none of the suggestions match what you’re looking for, just tap “Can’t find address” to enter it manually. It’s all about saving time while keeping flexibility in your hands.

IBALDEV-4647

Hub: Adding latitude and longitude as optional fields for order import.

When importing orders, you now have the option to include recipient coordinates - longitude and latitude - in addition to the address. These fields are located at the end of the recipient address section. If provided, the geocoding icon will indicate the location as Accurate.

Learn more about order import.

 

Related content