EV Charging Orchestration Platform: If You Are Not a CPO, You Should Not Be Building One

The conclusion first: EV charging orchestration platforms are being sold to, and built by, the wrong companies. A CSMS — a charging station management system — is a tool designed for CPOs who own physical charging infrastructure and need software to operate it. Every other company in the value chain — fleets, OEMs, mobility platforms, fintechs, wallets, super-apps, insurance providers, corporate benefits companies — has been convinced they need their own version of this infrastructure, at a cost that is often disproportionate to the return. They do not. What they need is a Distribution channel: one integration, free to join, a small per-session commission or discount, and immediate access to every public CPO network that matters. NetworkCore is that distribution channel.

What an EV Charging Orchestration Platform Actually Is

The term orchestration platform is used in the EV charging industry to describe software that coordinates the moving parts of a charging operation: communication with charger hardware, session management, pricing configuration, energy management, payment processing, user interfaces, roaming connectivity, and the various back-office functions that keep a charging network running. In practice, the category overlaps substantially with what CPOs call a CSMS — Charging Station Management System.

For a CPO, this kind of platform is essential infrastructure. Running a network of physical chargers requires operational software. Firmware updates, real-time monitoring, fault detection, energy load balancing, tariff management, regulatory reporting — all of this happens inside the CSMS, and the CPO's operational viability depends on having one that works.

For a company that does not own physical chargers, building or licensing this infrastructure makes considerably less sense than the market has been suggesting. The platform solves problems that the non-CPO does not have. The cost is real. The benefit is hypothetical — contingent on the non-CPO eventually acquiring the physical infrastructure that would make a CSMS operationally necessary, which most of them will never do and most of them should never do.

The gap between the capability being sold and the capability being needed is where the industry has accumulated a large amount of unnecessary complexity. Clarifying that gap is the purpose of this post.

The Companies Currently Being Mis-Sold CSMS-Style Orchestration

The list is longer than it should be. In every case, the logic of the sale is similar: the company has EV-driving users or a mobility-adjacent product, charging is relevant to their proposition, and the available tooling presents itself as the obvious way to integrate. The non-CPO buyer signs up for a platform that was built for someone else's business and starts paying for capabilities they do not need.

Fleet operators buying charging orchestration platforms to manage public charging access for their vehicles are acquiring software built to manage chargers, not to manage drivers of chargers. What they actually need is a single way to give their drivers access to every CPO network, with consolidated invoicing and reporting back to the fleet. That is a distribution relationship, not an operations platform.

OEMs building proprietary charging apps with backend orchestration capability are vertically integrating into a function that is not part of their core product. The result is the cost profile this market has seen repeatedly: significant engineering overhead, a charging app that drivers use reluctantly, and a network that never covers the geography the OEM's drivers actually need. The alternative is open distribution through a transaction layer that settles every session correctly — the OEM earns on the sessions its drivers complete without operating the infrastructure that produced them. For more on that architecture, see EV Charging Transaction Platform.

Fintechs and wallets embedding mobility services are being offered integrations that assume they will manage the financial flows of charging sessions themselves — session authorisation, payment capture, revenue reconciliation, VAT across jurisdictions. These are adjacent products to what a fintech was built to do, but they are still distinct products with their own complexity. Acquiring them is a decision. The default should be outsourcing them entirely to infrastructure built for the purpose. We cover the model more broadly in embedded mobility services for fintechs.

Super-apps and ride-hailing platforms that have EV drivers in their user base are being pitched orchestration platforms as the way to bring charging into their product. The integration cost is real. The operational overhead of running it is real. The revenue, in almost every case, could be earned more efficiently by connecting to a distribution layer and letting the platform handle everything between the driver plugging in and the revenue share arriving.

Insurance providers, corporate benefits platforms, fuel card operators, and BNPL players are all variations on the same pattern. Each has EV drivers in their user base, each has a commercial rationale for offering charging, and each is being offered tooling built for a different type of company. The mismatch between the tooling and the need is consistent across the category.

The common thread: none of these companies own chargers. None of them should be investing in the infrastructure to operate chargers. And none of them need a CSMS.

What the Non-CPO Actually Needs

The actual requirement is straightforward and has nothing to do with operating physical infrastructure.

The non-CPO needs its EV-driving users to be able to charge at any public charger their platform identifies, through an experience that is native to the platform they already use, at the CPO's transparent public price, without the platform acquiring operational responsibility for the session. The revenue share per session should arrive automatically. The compliance should be handled in the jurisdictions where the sessions take place. The reconciliation should be audit-ready without manual work. The integration should be a single API, not a programme of protocol integrations, bilateral negotiations, and commercial contracts.

This is a distribution relationship. The non-CPO provides demand — users who charge — and earns a share of the sessions that result. The infrastructure that makes those sessions execute correctly — routing, pricing, payment capture, revenue allocation, settlement, FX, VAT, invoicing, compliance — sits in the layer between the non-CPO and the CPO, handled by the platform whose business is to handle it. For a related perspective, see offer EV charging without owning chargers.

What this is not: a CSMS. What this is not: a charging orchestration platform that the non-CPO operates, configures, or maintains. What this is not: an engineering project with long timelines and ongoing operational overhead. What this is not: a compliance function that the non-CPO has to staff.

The non-CPO signs up for a distribution channel. The channel does the rest.

NetworkCore Is That Distribution Channel

This is the position NetworkCore occupies, and it is worth being direct about it.

NetworkCore is not a CSMS. It is not a charging orchestration platform in the CSMS sense. It is the financial and commercial infrastructure that sits beneath every public charging session on the network — routing demand from the platforms that have drivers to the CPOs that have chargers, handling the complete transaction lifecycle of every session, and settling to all parties correctly within 48 hours.

For a company that is not a CPO, joining NetworkCore is free. There is no subscription fee. There is no minimum volume commitment. There is no annual contract or licence cost. The platform earns a small commission on each session that flows through it — a transparent per-session cost that the non-CPO should think of the way any business thinks about a distribution channel: a marginal cost of acquiring a transaction, proportional to the transaction value, payable only when the transaction occurs.

What the commission pays for is the entire infrastructure picture the non-CPO would otherwise have to build or licence: access to every CPO network on the platform, session routing, payment capture, public price enforcement, revenue allocation, 48-hour settlement, multi-currency FX, VAT calculation per jurisdiction per fee type, compliance with local invoicing and reporting requirements in every market the platform operates in, audit-ready evidence packs per session, AML and KYC onboarding, and the Demand Partner commercial layer that lets the non-CPO negotiate preferential rates with individual CPOs where relevant. You can see the operating model in How It Works and the partner view on Demand Partners.

The alternative — building or licensing a charging orchestration platform to do any significant portion of this internally — is an investment of engineering time, operational resource, legal and compliance effort, and ongoing platform maintenance that the non-CPO will struggle to justify once they have run the numbers honestly. The per-session commission on a distribution channel is a variable cost. The in-house platform is a large fixed cost with an extended payback horizon and no certainty that the payback will ever arrive.

The Simplest Way to Think About It

A CPO running physical chargers needs an orchestration platform to manage those chargers. That is a real operational requirement. A CPO without software to run their infrastructure is not running a charging network — they are running charging hardware that happens to be plugged into a wall.

A company that does not run chargers has no operational requirement for that kind of platform. What they have is a commercial requirement: to give their users access to charging and earn on the sessions those users generate. That requirement is met by a distribution relationship, not by an orchestration platform.

The question to ask, before any purchase decision involving CSMS-style tooling or charging platform licensing, is simple: do we own physical charging infrastructure? If the answer is no, the follow-up question is not "which platform should we license?" but "which distribution channel gives us the cleanest access to the demand outcomes we want?"

For most companies in this position, the answer is NetworkCore. Single integration. Free to join. Per-session commission. Distribution channel. Revenue share on every session, settled within 48 hours, with compliance handled across every jurisdiction their users charge in. What in-house engineering teams would spend 18 months building is already operating as infrastructure, for every company that chooses to connect to it.

What Connecting Actually Looks Like

One API integration. No ongoing platform management. No operational overhead after go-live. The non-CPO's product gains native access to every CPO on the network. Drivers charge. Sessions settle. The revenue share lands. Compliance happens in the background.

On the Demand Partner side, the platform handles authentication flows and session initiation in whatever form the non-CPO's product needs — a mobile app, a fleet management interface, a web platform, a super-app embedded experience, a point-of-sale for an OEM dealer network. The driver's experience is branded by the non-CPO. The transaction infrastructure is NetworkCore's.

On the CPO side, the platform routes the non-CPO's drivers to available chargers, captures payment, applies the CPO's published tariff without modification, and settles to the CPO daily within 48 hours. The CPO gains demand. The non-CPO earns on the sessions. Both parties benefit from the commercial alignment that only a proper distribution platform can deliver. For the commercial comparison with legacy connectivity models, see EV Charger Platform vs Roaming Hub.

This is, by some margin, the cleanest way to be in EV charging without being in the infrastructure business. And it is why the first CPO on the network joined not because they saw NetworkCore as a roaming hub or an orchestration tool, but — in their own words — because they considered the platform a distribution channel. The same framing applies, with equal accuracy, from the other side of the transaction.

The Position to Take

If your company is a CPO, an orchestration platform is the right conversation. Evaluate carefully, negotiate hard, and make sure the platform you choose is actually built for operating physical chargers rather than being a general-purpose tool adapted for the job.

If your company is not a CPO, stop evaluating orchestration platforms. They are not the category you are in. What you are looking for is a distribution channel — a way to give your users access to charging, earn on the sessions they produce, and let someone else handle the infrastructure between the driver plugging in and the money arriving in your account.

NetworkCore is that channel. It is free to join. The commission or discount is small and is only paid when you earn. The infrastructure does the work. The sessions flow. The revenue arrives. And you keep your engineering team working on the product you were actually built to ship, not on a charging platform you were never supposed to need.