Ride-End Charging Policy
The ride-end charging policy lets you nudge — or require — riders to plug a vehicle into a charging station before they finish their ride. It is designed for fleets that use charging hubs or docking stations and want vehicles returned charged and ready for the next rider.
Overview
The policy is set per fleet (subaccount) and has three modes:
| Mode | What the rider sees | Blocks ride end? |
|---|---|---|
| Disabled (default) | Nothing — rides end as usual | No |
| Show reminder only | A "Plug in scooter" prompt before the ride ends | No — advisory only |
| Require charging before ride end | A prompt, and the ride end is held until charging is detected | Yes — until charging is detected (with safeguards) |
Off by default
Every fleet starts on Disabled. The reminder and require-charging modes only take effect after you turn them on for a fleet.
Which vehicles this works with
This is the most important thing to understand before turning on Require charging: the policy only applies to vehicles whose onboard device reports charging state. It is limited to a specific allowlist of IoT device types — every other vehicle is exempt and ends normally.
| Device type | Supported? |
|---|---|
| OKAI (ES400, ES400B) | ✅ Yes |
| Segway (API Max, Max Plus) | ✅ Yes |
| Queclink ZK-series (ZK115MGC, ZK105LSC, ZK105L) | ✅ Yes |
| Zimo | ✅ Yes |
| Omni DM01 controller | ✅ Yes |
| Acton | ❌ Exempt |
| Omni locks (OMNI_LOCK, with-cable) | ❌ Exempt |
| BLE-only / manual / no-IoT vehicles | ❌ Exempt |
Unsupported vehicles are exempt automatically
You don't need to manage this per vehicle. If a vehicle isn't on a supported device type, the Require charging gate simply does not apply to it — that ride ends normally. So turning the policy on for a mixed fleet only affects vehicles that can actually satisfy it, and it can never block a rider on a vehicle that has no way to report charging.
Eligibility is decided by the vehicle's IoT device model, not by its display name. New OKAI, Segway, and Queclink ZK models are covered automatically; other manufacturers are added to the supported list as their charging reporting is verified.
How charging is detected
When a rider tries to end a ride under Require charging, the system checks the vehicle's most recent charging signal from two sources:
- The vehicle's current charging status
- The latest charging reading in the vehicle's telemetry
The reading must be fresh — observed within the telemetry freshness window (default 10 minutes, configurable from 1–60). A stale reading is treated as "not charging" so an old "was charging yesterday" signal can't be used to end a ride that isn't actually plugged in now.
What the rider experiences
Reminder mode
Before the ride ends, the rider sees a prompt:
Plug in scooter — Please plug the scooter into the charging station before ending your ride.
They can tap "I've plugged it in" to continue, or Cancel. This mode never blocks the ride — it's a courtesy nudge, so it's safe to use on any fleet.
Require charging mode
The rider sees the same prompt. When they continue, the ride end is held until charging is detected:
Plug in scooter — Please plug the scooter into the charging station, wait a moment for charging to be detected, and try ending the ride again.
Once they plug in and the vehicle reports charging (within the freshness window), the ride ends normally.
Rider safeguards — no one gets stuck
Requiring charging introduces a risk: a broken charger, an offline IoT device, or a flaky charging sensor could otherwise leave a rider unable to end their ride while the meter keeps running. The policy has three layers that prevent this:
Incompatible vehicles are skipped
If the vehicle can't report charging at all, the requirement doesn't apply and the ride ends normally (see above).
Riders are always let through after a couple of attempts
If charging still isn't detected, the rider is asked to plug in for the first couple of end attempts, and then the ride is guaranteed to end on the next attempt. A charging problem can never trap a rider in an open, still-billing ride.
Stuck minutes are auto-refunded
If a rider was genuinely held up trying to plug in, the minutes they were billed during that window are automatically refunded when the ride completes — the same mechanism used for the parking-photo gate. No support ticket required.
A rider can always end their trip
The charging requirement is for accountability, never a permanent gate. These safeguards are built in and always on when Require charging is active.
Configuring the policy
Open Settings
In the dashboard, go to Settings and select the Other tab.
Find Ride-end charging reminder
Scroll to the Ride-end charging reminder section.
Choose a mode
Set Charging policy to Disabled, Show reminder only, or Require charging before ride end.
(Require charging only) Set the freshness window
Choose how recent a charging reading must be — in minutes (1–60, default 10). A shorter window is stricter; a longer window tolerates slower-reporting devices.
Save
Save your settings. The change applies to new ride-end attempts across the fleet.
Roll out with Reminder first
Start on Show reminder only for a week or two. It builds the plug-in habit with zero risk of blocking anyone, and it lets you confirm your charging stations and vehicles report charging reliably before you switch to Require charging.
Choosing the right mode
- Disabled — Free-floating fleets, or any fleet without charging stations.
- Show reminder only — You want vehicles returned charged but won't hold up a rider who can't or won't plug in. Good default for most station-based fleets.
- Require charging before ride end — Dedicated charging hubs where plugging in is part of the return process, and your vehicles reliably report charging state. The safeguards above keep it from ever trapping a rider.
Troubleshooting
Riders on Require charging are never blocked
- Confirm the fleet is actually set to Require charging (not Reminder) under Settings → Other.
- Check the vehicle's device type. If it isn't a supported model (OKAI, Segway, Queclink ZK, Zimo, Omni DM01), it's exempt by design and will end normally — Acton, lock-only, BLE-only, and manual/no-IoT vehicles are not gated.
A rider says they plugged in but still got the prompt
- The charging reading may not be fresh yet. Ask them to wait a moment after plugging in and try again — the vehicle needs to report charging within the freshness window.
- If the charging station or the vehicle's device is slow to report, increase the freshness window (e.g. 10 → 20 minutes).
- After a couple of attempts the ride will end regardless, and any minutes billed during the wait are auto-refunded.
I turned on Require charging but it doesn't seem to do anything
- Your fleet's vehicles may be on device types that aren't supported (e.g. Acton, BLE-only, or manual vehicles), so the requirement is exempting them automatically. Use Reminder mode instead, which still shows the plug-in prompt on every vehicle.