Roaming Sync Status on Sessions
We've expanded the visibility around the roaming hub delivery status for sessions authorised with roaming tokens. You can now identify and follow up on sessions that failed to sync without having to dig through individual records.
Filter by sync status: The Sessions page now supports filtering by roaming sync status, so you can quickly surface sessions that failed to deliver to the roaming hub.
Sync status in exports: Session exports now include the roaming sync status, allowing you to audit delivery state across your full session history outside the platform.
Configurable Default Operator Name
Private label customers can now have a default roaming operator name that does not need to match their Provider name. Previously, the default operator was always set to the name of the Provider. This works similarly to the existing default sub-operator settings, giving providers more flexibility in how operator information is presented across their infrastructure.
Note: This setting is configured by your CSM on request. It is not yet self-serve.
Map-SDK Improvements
We've made a set of general improvements for customers using mapsdk.road.io:
Opening hours on the map: Locations with configured opening hours now display them on the web map, handling common patterns including 24/7, varying hours per day, and exceptional closures. Hours are sourced both from direct configuration on the platform and from OCPI roaming feeds where available.
More powerful location filtering: The location search now supports more granular filters, helping operators narrow results down to what matters.
Report missing tariffs: Drivers can now flag locations where tariff information is missing, giving operators a direct signal to close data gaps.
Coming soon
Improved Session Cost Calculation for Negative Dynamic Pricing
With this change operators using dynamic energy pricing will see that the total session cost is capped at €0.00 when the energy price turns negative. Previously, our platform only zeroed out the energy component itself, but continued to apply surcharges on top, meaning drivers were still charged despite the underlying energy price being negative. With this improvement, surcharges are now consumed within the total session cost when the energy component turns negative — bringing the total down to €0.00 rather than leaving surcharges as an additional charge on top.
Note: Payouts to drivers (negative CDR values) are not in scope for this.
Timelines: This functionality will be released end of June.