Industry · EV charging

Running EV charging operations in one Odoo dashboard

Station telemetry, asset management and billing often live in three separate places. This is how to unify all three inside Odoo, and what the architecture looks like under the hood.

By Octagotech Team7 min read

Key takeaways

  • A small, stateless bridge turns station messages into Odoo records. All state lives in Odoo.
  • The Odoo sale order joins app session data to station telemetry and flags mismatches before an invoice goes out.
  • A fault event can open a maintenance request on the station's equipment record, with recent session data attached.
  • Map vendor-specific OCPP fault codes to a normalized set before you build the bridge.

EV infrastructure operators face an unusual data problem. Their physical assets, charging stations, are inherently IoT devices, generating a continuous stream of telemetry: connector state, power draw, session start and end times, fault codes. At the same time, those assets need to be managed like any other piece of capital equipment: scheduled for preventive maintenance, depreciated, insured, dispatched for repair. And every charging session has a billing implication that has to reconcile with a customer account.

For the EV charging operator behind our EV charging case study, user management, device tracking, billing and hardware communication each ran in a disconnected system, and energy bills and device data were reconciled by hand. The pattern is common. In a typical setup, operations use a vendor-supplied monitoring portal, billing runs through the mobile app's backend plus manual exports into spreadsheets, and maintenance dispatching is tracked in a third tool. None of them talk to each other.

This article shows how to unify telemetry, asset management and billing inside Odoo, and what the architecture looks like under the hood. The platform in the case study connects to its chargers over OCPP; the pattern below applies more widely.


The problem with three sources of truth

In a typical setup, the operations team starts every morning by pulling a status report from the monitoring portal, cross-referencing it against a billing export from the app backend, and manually flagging any sessions that ended without a corresponding invoice. On a day with network issues or charger faults, that work can consume most of the morning.

Billing disputes are the most painful consequence. When a driver reports a session that didn't charge their account correctly, the support team has to hunt across three systems to reconstruct what actually happened: did the session complete? At what power level? Did the charger report an error that aborted the session early? The answers live in different places, and pulling them together takes longer than the dispute is worth.

Maintenance is similarly fragmented. Technicians receive work orders through a generic ticketing tool with no link to station history, so they can arrive on site without knowing the station has already logged repeated faults.

The integration architecture

The core challenge is bridging two fundamentally different communication patterns: the real-time, high-frequency telemetry from the charging stations (usually OCPP or MQTT, the standard protocols for charger and IoT device messaging) and the transactional, request-response model that Odoo uses internally.

How the data reaches Odoo

Station telemetry

  1. Charging stationsStatus, sessions, faults
  2. Bridge serviceStateless, runs beside Odoo
  3. Odoo event recordsAutomation rules react
  4. Maintenance requestOn the station's equipment record

Driver mobile app

  1. App backendExisting, kept in place
  2. Odoo APIAuthenticated with an API key
  3. Sale orderThe join point for each session
  4. InvoiceAfter payment confirmation

A typical design uses a lightweight bridge service, such as a small Python process running alongside the Odoo instance. It subscribes to the station telemetry and translates incoming messages into event records in Odoo, posted through Odoo's API. Odoo automation rules can then react to those records. Keeping the logic in Odoo means you build on its standard tools rather than inventing something bespoke.

The bridge handles three categories of messages:

  • Status updates: connector availability (available, occupied, faulted, offline), updated on each heartbeat from the station firmware
  • Session events: session start, session stop, energy delivered (kWh), and the driver or vehicle identifier from the RFID or app authentication
  • Fault events: OCPP error codes, which the bridge maps to a normalized fault taxonomy agreed with the operator's field team

Each station can be represented in Odoo as an equipment record in the Maintenance app, with custom fields for its EVSE identifier, physical address, connector count, and firmware version. In the case study platform, each charger is likewise a device record with maintenance history and fault records linked to it. When the bridge posts a fault event, an automation rule can create a maintenance request against that record, pre-populated with the fault code and recent session data as context. Technicians see what happened before they get in the van.

Key architectural decision: Keep the bridge stateless. It translates and forwards; it does not store. All state lives in Odoo. If the bridge restarts, the only risk is a gap in telemetry during the downtime, and there is no separate database to fall out of sync.

Connecting the driver-facing mobile app

Many operators already have a mobile app that drivers use to start and stop charging sessions, view their session history, and manage their account. Replacing it is often out of scope and unnecessary. What you need is for session data from the app to flow into Odoo so it can be reconciled against the telemetry record from the physical station.

Have the app's existing backend call Odoo at three points in a session's lifecycle: session initiation (creates a draft sale order in Odoo), session completion (updates the order with actual kWh delivered and duration), and payment confirmation (triggers Odoo's invoice creation flow). The calls can go through Odoo's external API (the JSON-2 API with an API key on Odoo 19 and later) or through a few endpoints in a custom module. Our guide to integrating a mobile app with Odoo covers the options.

The Odoo sale order record becomes the authoritative join point. It holds the app-side session ID, the station EVSE identifier, the kWh figure from both the app and the station telemetry (they should match within a small tolerance), and the customer account. When they don't match, because of a network gap, a meter calibration issue, or a session that the station considers incomplete but the app marked as finished, the record flags automatically for review rather than silently billing the wrong amount.

The point of this reconciliation logic is that billing mismatches surface when the session closes, not when a driver complains. The operations team reviews a queue of flagged sessions instead of discovering problems weeks later through chargebacks.

The operations dashboard

With all three data streams landing in Odoo, the dashboard is the most straightforward part. Odoo's built-in reporting, extended with a few custom views, can give the operations team a single screen that shows:

  • Live station status, color-coded by connector state and refreshed by a simple polling call
  • Active sessions count and aggregate power draw across the network
  • Open maintenance requests by station, with fault history inline
  • Billing queue: sessions pending reconciliation review
  • Revenue summary for the current day, week, and month, pulled directly from Odoo's accounting

The aim is that operations open one tool each morning instead of three, and that the morning reconciliation becomes a quick scan of the billing queue.

Fleet and maintenance management

Beyond day-to-day operations, this design gives you a usable maintenance history for every station.

Because every fault event creates a maintenance record in Odoo, and every maintenance record is linked to the asset, you can see the full fault and repair history for any station in a few clicks. That data can feed preventive maintenance scheduling, for example by flagging stations that log more than a threshold number of connector faults in a rolling window for inspection before they fail completely.

Spare parts management improves too. The Odoo Inventory app can track the components used in each maintenance job, which gives you actual consumption data to drive reorder rules for common replacement parts (contactors, cable assemblies, display modules) rather than ordering based on gut feel.

Worth noting for similar projects: The OCPP fault code taxonomy varies between charger manufacturers. Before building the bridge, spend time with the client's field engineers mapping vendor-specific codes to a normalized set your team and theirs actually understand. Skipping this step produces a maintenance module full of cryptic codes that nobody acts on.

What to take from this

Odoo's value here comes from what happens downstream of the IoT integration. Any monitoring platform can display live station status. In Odoo, a station fault can also create a maintenance work order, update the asset record, and trigger a customer notification, because those apps already exist and are already connected. The integration work is what buys you all of that.

If you're running EV infrastructure, energy assets, or any operation where physical devices generate data that eventually has billing and maintenance implications, talk to us. This is the kind of integration work our Ahmedabad engineering team does, and we're happy to walk through what the architecture would look like for your specific setup, with no commitment required.

Put your device data to work in Odoo

The first call takes 30 minutes.

Or email sales@octagotech.com