This is the list we build from. Each item says what has to be proven before we call it shipped. Until it passes, it stays on this page and gets no check mark anywhere on this site. No dates: we publish the order, not promises.
What an operator can use now. “Supported” means it works on the platform; nothing here is independently certified unless it says so.
Being built first. Each one is a precondition for operators moving whole networks onto MobiFLO.
MobiFLO supports OCPP 1.6J and 2.0.1. It is not independently certified.
The exact e-flo PRO model and firmware are certified, and we publish the certificate, the tested profiles and the firmware version. Supported features stay clearly separate from independently certified ones.
Roaming runs on OCPI 2.2.1, in both CPO and eMSP roles, and through Hubject.
Existing partner connections keep working through version negotiation. Credentials, locations, tariffs, tokens, sessions, charge detail records, commands and the AFIR / National Access Point export fields are validated. A live partner pilot shows that retries and outages never duplicate records, billed sessions reconcile to CDRs, and rollback works.
Moving chargers from another backend is planned by hand with our team, using the per-brand steps on /switch.
Operators get a repeatable inventory, configuration, cutover and rollback process, proven on a pilot site: charger access is preserved and no session is missing or billed twice.
Load management is calculated in the platform.
Shown on physical chargers: the site stays within its configured limit when the internet or the CPMS drops, with what each connector was allocated recorded before, during and after reconnection.
Queued behind the four above.
Any charger that speaks OCPP 1.6J or 2.0.1 can connect. There is no published model-and-firmware matrix yet.
A published model-and-firmware compatibility matrix. It shows which chargers accept external power limits, what they actually deliver, and whether a failed session was caused by the charger, communications or the backend.
The e-flo PRO supports ISO 15118 natively and is Plug & Charge ready.
Certificate-based charging proven end to end on a named vehicle and charger combination.
Drivers can start a session by QR code.
A time-limited QR payment shown working from price display to receipt, including rejection of an expired code.
Not available.
A site or portfolio moves between operator accounts with explicit permissions, an audit trail and a clear billing cutoff. This is separate from moving chargers between backends.
Not available.
One maintenance system, chosen with a parking operator, connected: a charger fault creates one work order, repeated alerts do not create duplicates, and technician updates and closure sync back to the charger record. Accounting, fleet and BI connectors follow in order of customer demand.
Not available.
The operator / site-owner split is set per agreement, and a monthly statement traces to sessions, fees, refunds and adjustments. Where automated payouts are on, a retry can never pay twice. MobiFLO takes no share: the feature distributes the operator’s revenue under the operator’s own contract.
Every roaming partner is offered the same published tariff.
An operator sets an agreement with one eMSP, scoped to chosen sites or customer accounts, as a markup, a discount or a fixed price, with start and end dates. When agreements overlap, the one that applies is explicit, and partners without an agreement keep paying the published tariff. Every session and charge detail record keeps the version of the agreement that priced it. Overlapping agreements, expiry, refunds and reconciliation are tested before release.
e-flo PRO chargers arrive pre-provisioned, already pointing at the platform.
A job is assigned through an expiring, job-specific link that grants no CPMS admin access. The installer captures serial number, checklist, readings, photos, parts and costs; a handover record is exported, and later repairs stay on the same charger history.
Scoped, not started.
Tariffs per kWh, per minute, idle fees, member rates and time bands.
The driver sees the price that applies, and the receipt matches it.
Not supported.
Scoped and tested after OCPP 2.0.1 certification. Until then we do not claim it.
We do not publish dates we might not keep. The order is above: the four items under “Now” come first. An item moves to “Shipping today” when its test passes, and this page changes the same day.
Because operators comparing platforms should see exactly where each one stands. Every item here would otherwise surface in a pilot or a contract review. It is cheaper for both sides to read it here first.
Not yet. MobiFLO supports OCPP 1.6J and 2.0.1, and its security was checked against the Open Charge Alliance’s Security Operations Guide v2.0. Independent certification of the e-flo PRO model and firmware is the first item on this roadmap.
No. The operator programme has no percentage of revenue. The planned site-owner settlement distributes the operator’s revenue under the operator’s own agreement, and MobiFLO takes no share of it.