
Booking Calendar Improvements for Station Operators: Two improvements make the booking calendar significantly faster to work with for operators managing large station networks: pending request bookings are now visible in their own calendar row before approval, and the station dropdown remembers its scroll position between selections. Together, these changes cut the repetitive navigation that slows down high-volume station reviews.
Requires the latest app version. Contact your Customer Success Manager for details.
Reliable payment method confirmation after external checkout: When an end user adds a payment method on the payment provider’s browser page and returns to the app, the app now confirms the card within seconds and moves them straight to the next sign-up step. It keeps checking until the card is confirmed, so they are never sent back to add a payment method again.
Nearby vehicles stay visible after closing a point of interest: Closing a point of interest while a vehicle is selected no longer hides the vehicle and the nearby vehicle list, so riders no longer need to restart the app to continue.
Point-of-interest navigation improvements: The in-app point-of-interest experience is now more consistent for operators who use deep-linked locations. The point of interest stays open when a user opens an external website or stays in on-demand mode, and closes only when switching to pre-booking mode. The map centers on the relevant booking station when the station sheet is closed, keeping context visible. A configurable website label translation field (urlLabel) is now available in the back office so operators can localise the link label independently per language.
Station details, including opening hours, in the booking flow
When choosing a start or return station in the booking flow, end users can now tap the info icon on any station to see its details: address, opening hours, location guidelines and directions. Opening hours are visible before a pickup or return time is chosen, and the station can be selected straight from its details.
Date picker no longer offers days with no available time slots: The booking calendar no longer shows fully booked days as selectable. If a station has no bookable start time on a given date, that date is greyed out consistently, preventing users from reaching a dead end in the flow.
Promo code confirmation sheet now uses the correct heading: During registration, applying a valid promo code now shows a confirmation sheet with a heading specific to promo codes. Previously, the sheet displayed "Ride passes", the wrong label for a different voucherable type. The heading now uses its own translation key Profile.signUpPromotionTitle) so operators can configure the wording independently.
Station dropdown in the booking calendar remembers its scroll position: When operators switch between stations in the booking calendar, the station dropdown now reopens at the position it was last at rather than jumping back to the top. For operators managing large station networks, this removes the need to scroll through hundreds of entries on every station change.
Pending request bookings visible in the calendar before approval: Unapproved request bookings now appear in the station calendar in their own row, separate from confirmed bookings. Operators can see how a pending request fits into the existing schedule before deciding whether to approve it, rather than having to open the approval flow just to assess timing.
Ops Map items open with a tap on a phone: On a phone, tapping a vehicle on the Ops Map in goDash now opens its side panel, just as a click does on a desktop. Station and point-of-interest pins open with a tap in the same way.
Booking cooldown conflicts now flagged before saving: Adding an end-station cooldown that overlaps a following booking now shows a conflict warning in the edit form before the operator saves. Previously, the conflict only appeared on the calendar after saving, requiring an extra corrective step.
Bookings calendar no longer offers a time slot that triggers a false conflict warning: The bookings calendar no longer generates a conflict warning for the earliest available overbooking slot when a request arrives at the boundary of a clock minute. The availability picker and the overbooking gate now agree on the current time, so valid slots are accepted without requiring the user to retry.
Rental end details now visible in the activity log: The back office activity log now shows rental end details, giving operators and support agents a clear record of how and when a rental was closed, including any operator overrides to the end time. This makes it straightforward to investigate disputes or billing questions without relying on informal communication.
"Add Login Method" action now supports email code sign-in: Operators can now add the email code login method to an existing user account directly from the back office, without needing an API call. The previous "Allow login via email" action required a password and did not support email-code sign-in.
Invoice status transitions expanded for dispute outcomes: Invoices in DISPUTE_LOST status can now be moved to COLLECTION or LOST directly from the back office. Previously, no status-change option appeared for these invoices, requiring manual workarounds for finance teams processing dispute outcomes.
Verification queue date picker no longer renders behind other UI elements: The date picker in the manual verification flow of the verification queue now appears correctly in front of all other UI components. Previously, it rendered behind the page and required scrolling to interact with, slowing down verification workflows.
Voucher scope changes now apply to all newly issued vouchers: After an operator edits a sold product's branches or vehicle categories, vouchers issued from that product now correctly carry the updated scope.
Voucher and localisation screens no longer corrupt translation links on activation: Creating or editing voucherable items and their localisation settings no longer overwrites translation links for inactive passes. All passes, active and inactive, now display the correct translated names and descriptions rather than falling back to placeholder text.
Vehicle commands now have a time limit: Every command the platform sends to a vehicle, such as start, stop, lock and unlock, now waits at most 40 seconds for the vehicle to answer, and a rental start waits no more than 10 seconds for a vehicle busy with another action. A rental start therefore resolves within a minute, with the app and goDash agreeing on the result. If your fleet had a longer command timeout configured, it now runs at 40 seconds.
Bluetooth park and resume no longer drop subsequent vehicle events: When a Bluetooth park or resume operation cannot run because another action on the rental is already in progress, the failure is now recorded correctly and the remaining Bluetooth events in the same status update continue to be processed. Previously, the error interrupted processing entirely, silently dropping subsequent events.
Auto-secure lock action now works for INVERS-connected cars: The platform now stores the lock state that INVERS-connected cars report, enabling the auto-secure feature to lock cars left unlocked after a rental. Previously, the lock state was not retained for these vehicles, so auto-secure could not be enabled for them.
Speed limits now enforced in slow zones and no-ride zones for Evolve pilot scooters: Scooters on the Evolve pilot fleet now receive speed limit commands when entering a slow zone (10 km/h) or no-ride zone (5 km/h). Previously, no command was sent and vehicles did not slow down in either zone type.
OC33 lock commands now use the correct protocol instruction: The platform now sends the S5 instruction to OC33 locks rather than S6, following a protocol update from the lock's cloud provider. The previous instruction was never acknowledged by OC33 hardware, meaning lock commands appeared to succeed but did not execute. Affected fleets on this lock type will now see reliable lock operation.
Creating a pricing bundle no longer overwrites an existing bundle's version: A bug that caused a new pricing bundle to take over a version belonging to a different bundle has been fixed. Bundle creation now adds a clean draft version to the new bundle without touching any other bundle's data.
Adyen 3DS redirect no longer returns a server error when the payment detail call fails: The redirect handler for Adyen 3DS charges no longer throws an unhandled error when the payment details call cannot be completed. Previously, this produced an HTTP 500 response that interrupted the payment flow; the handler now resolves the redirect without a crash.
GBFS geofencing zones feed corrected and fed from branch areas
The geofencing zones feed now passes the GBFS v2.2 validator and is built from each on-demand branch’s business and no-parking areas in the dashboard, so MaaS partners always see where vehicles may ride and park. Speed-limited areas are not published.
Vehicle telemetry now reports window, sunroof and convertible roof state
The Operations API vehicle telemetry endpoint now returns the state of the windows, the sunroof and the convertible roof as open, closed or unset. A value is present only for cars whose telematics actually report that part. INVERS-connected cars only.
Booking stations list now includes station state
Each station in the booking stations list now carries its state: Operational, Out of business, In preparation, Maintenance or Hibernation