EV charging management software connects charging infrastructure to the operational tools businesses need for monitoring, session management, billing and reporting. UnityCharge (Tecell CMS) provides charge point management capabilities, while ChargeSphere is a separate EV roaming hub for cross-network access. For Indian CPOs, fleet operators and property owners, the buying decision should start with charger compatibility, commercial workflows and site power requirements—not just a software feature list.
What is an EV charging management system?
A charge management system, commonly called a CMS, is the software layer used to oversee connected EV charging infrastructure. It brings station information, charging transactions and user access into a central operational environment, helping teams manage charging as a service rather than as isolated electrical equipment.
A charge point operator, or CPO, manages charging infrastructure and its day-to-day operation. An eMobility service provider, or eMSP, focuses on driver-facing services such as charging access and payment. A business can perform both roles, but its software requirements should distinguish infrastructure operations from customer access.
For background on these responsibilities, read Tecell’s guide to charge point operators and eMSPs. This distinction matters when assigning responsibility for maintenance, customer support, payment queries and network partnerships.
What UnityCharge (Tecell CMS) provides
The Tecell CMS website describes real-time station monitoring, automated billing, smart charging and analytics. It also lists mobile applications for iOS and Android, progressive web app capabilities, API integration and multi-role management for site owners, CPOs and eMSPs.
Tecell’s enterprise partnership information additionally describes dynamic pricing, load management and multi-tenant white-label capabilities. Treat these as starting points for a requirements discussion: confirm which capabilities, integrations and deployment responsibilities are included in your proposed agreement.
OCPP: the connection between chargers and the CMS
OCPP, the Open Charge Point Protocol, is a communication protocol between charging stations and a management backend. It allows compatible equipment and software to exchange operational information, rather than requiring every charger to depend on a proprietary management environment.
In a typical connected charging workflow, the backend receives charger status and transaction information. Depending on the implementation, it can also exchange authorisation information, configuration instructions and charging controls. However, support for a protocol does not mean every charger implements every optional capability.
Check versions and workflows, not just the OCPP label
The Tecell CMS website lists OCPP 1.6 and 2.0 support, while Tecell’s enterprise partnership page lists hardware support for OCPP 1.6 and 2.0.1. For procurement, ask Tecell to confirm the precise protocol version supported by your charger model, firmware and selected CMS deployment.
- Connectivity: establish how the charger reaches the backend and what happens when that connection is interrupted.
- Sessions: demonstrate authorisation, charging start, charging stop and transaction recording with the intended hardware.
- Meter information: verify that energy readings arrive correctly and support the billing workflow.
- Control: test the remote actions and charging limits your operations team actually requires.
Use your proposed hardware in the acceptance process wherever possible. A successful dashboard demonstration alone cannot establish that a specific charger, payment flow and site network will work together.
Monitoring and session management: look beyond online status
Real-time monitoring should help the operations team understand whether charging is usable, not simply whether equipment is connected. An online station may still have an unavailable connector, a payment problem or a charging transaction that fails to deliver energy.
Tecell’s guide to charging performance beyond uptime discusses successful charging sessions, availability, connector utilisation, revenue per connector, failed sessions and recovery time. These are useful measures to include in your operational reporting brief.
During evaluation, ask how staff can move from a failed transaction to the relevant station status, session information and diagnostic evidence. Also establish who handles the next action: the CPO helpdesk, a site representative, a hardware supplier or a field maintenance team.
For fleet charging management, the operational question is whether charging activity supports vehicle readiness. Ask which reports can connect charging transactions to drivers, vehicles or cost centres, and what additional integration is needed to relate charging records to dispatch plans.
Tariffs, billing and payment workflows
Charging management software must translate charging activity into a clear commercial record. That involves more than displaying a tariff: the operator needs to understand how prices are configured, how transactions are calculated, how payments are reconciled and how exceptions are resolved.
UnityCharge (Tecell CMS) lists billing automation, and Tecell’s partnership page describes dynamic pricing and payment options including UPI, cards and wallets through its application offering. Confirm the payment services and commercial arrangements included in your deployment rather than assuming every gateway is available by default.
Specify the charging business model first
A public CPO may need customer charging payments and site-owner reporting. A fleet may need internal cost allocation rather than retail payment collection. A residential property may need separate treatment for residents and visitors. Write down these requirements before comparing software proposals.
- Tariff structure: define the intended pricing basis, user categories and approval process for changes.
- Transaction visibility: establish what the driver sees before charging and after the session ends.
- Reconciliation: ask how session records, payment records and settlement reports are matched.
- Exceptions: demonstrate the handling of interrupted sessions, payment failures, refunds and disputed charges.
- Accounting handover: confirm reporting formats and any integration required by your finance team.
These are procurement questions, not a guarantee that every workflow is included in a standard plan. Request a demonstration against your billing rules and obtain written confirmation of any configuration or development required.
Smart charging and site load management
A CMS can coordinate charging demand, but software cannot replace an electrical assessment or protective equipment. Effective load management depends on the site’s available supply, charger control capabilities, electrical design and, where needed, information about other building loads.
Static load management applies predetermined limits. Dynamic load balancing adjusts allocation in response to changing conditions. Neither should be selected solely because it sounds more advanced: the appropriate approach depends on the charging schedule, electrical constraints and available measurements.
Tecell describes smart charging on its CMS website and dynamic load management in its enterprise offering. Ask how the proposed solution obtains site-load information, applies limits and behaves during communication failures. Fleet buyers should also discuss charging priorities and how those relate to departure requirements.
For a fuller explanation, read Tecell’s comparison of dynamic load balancing and static load management. Confirm the hardware, metering and configuration needed for your site before committing to a control strategy.
Multi-tenant and white-label EV charging software
Multi-tenant architecture allows separate operators or business entities to work within a shared platform while maintaining distinct operational environments. White-labelling concerns the branded customer experience. These requirements overlap, but branding alone does not establish separation of data or permissions.
Tecell’s partnership page lists multi-tenant white-label capabilities, custom-branded mobile applications and role-based access control. Its multi-tenant charging architecture guide explains the importance of independent branding, pricing, user access and tenant data separation.
Ask the vendor to demonstrate the boundaries between a platform administrator, a CPO, a site owner and a support user. Check who can view transactions, change tariffs, export information or manage users. For a white-label deployment, separately confirm application branding, publishing responsibilities, updates and ownership of the customer relationship.
UnityCharge versus ChargeSphere: management and roaming
UnityCharge (Tecell CMS) manages charging operations. Its role covers the software functions used to oversee connected stations, charging activity, billing and operational reporting.
ChargeSphere is Tecell’s EV roaming hub. The ChargeSphere overview describes connecting CPOs, eMSPs, EV OEMs and fleets for cross-network charging. Tecell’s partnership page lists OCPI-based roaming, tariff synchronisation and inter-network settlement capabilities.
OCPP and OCPI address different interfaces: OCPP connects charging equipment with a management backend, while OCPI supports exchanges between charging-network and mobility-service systems. A roaming arrangement does not remove the need to operate, maintain and manage the underlying charging infrastructure.
A depot-only fleet may prioritise CMS functionality without requiring public roaming. A CPO seeking access through external mobility providers may need both operational management and a roaming arrangement. Evaluate their integration scope and commercial terms separately.
When do you need a CMS rather than hardware alone?
Hardware-only charging can be appropriate where the business does not need central monitoring, remote administration or automated charging payments. A connected CMS becomes more relevant when staff must manage access, reconcile charging activity, oversee distributed sites or coordinate charging within power constraints.
The product descriptions illustrate this distinction. BluePlug Home Socket EV Charger 3.3 kW is described as having no connectivity. Tecell Smart Dual Socket and the Eris GSM and WiFi products explicitly describe charging service using OCPP and the Tecell Mobile App.
Do not treat an RFID card, a communications module or a charger power rating as proof of a complete software service. Confirm the actual backend connection, platform charges and included workflows for the selected product.
Relevant Tecell products and list prices
The following products provide a starting point for comparing software and hardware requirements. Power and type follow the supplied product names or descriptions; inclusion here does not confirm CMS compatibility for every model. Contact sales for installed pricing.
| Product | Power or type as listed | List price |
|---|---|---|
| CMS – Basic plan | CMS software plan; scope to be confirmed | Price on request |
| BluePlug Home Socket EV Charger 3.3 kW | 3.3 kW socket charger; no connectivity | Price on request |
| Tecell Smart Dual Socket | Dual socket; OCPP charging service | ₹15,000 |
| Tecell Eris X2 3.3kW (GSM) | 3.3 kW; GSM; OCPP charging service | ₹6,820 |
| Tecell Eris X6 3.3kW (WiFi) | 3.3 kW; WiFi; OCPP charging service | ₹4,680 |
| Tecell 22 kW AC EV Charging Station | 22 kW AC | ₹59,999 |
| Gale 30 kW | 30 kW DC; CCS2 | ₹4,00,000 |
The Eris X2 and Eris X6 descriptions state that an annual platform fee applies from the second year and that their quoted prices exclude GST and shipping. Ask for the applicable platform fee and a complete commercial proposal; the hardware list price is not a CMS subscription quote.
Buying checklist for CPOs and fleet operators
- Define the operating model. Identify who owns equipment, manages operations, collects payments and supports drivers.
- Inventory the equipment. Record charger models, firmware, connectors, communication methods and protocol support.
- Document commercial workflows. Specify user groups, tariff rules, billing responsibilities and accounting requirements.
- Assess site constraints. Establish available power, connectivity and any required load measurements.
- Set access boundaries. Define permissions for operators, site owners, finance staff and support teams.
- Choose deployment requirements. Discuss SaaS, private cloud or software ownership, including hosting, maintenance and update responsibilities.
- Test before acceptance. Include successful charging, failed authorisation, interrupted connectivity and billing reconciliation.
- Review the full contract. Confirm platform charges, integrations, support scope, data access, migration arrangements and acceptance criteria.
The Tecell CMS website lists SaaS subscription, private cloud deployment and software ownership models. Ask for a proposal matched to your operational requirements, rather than assuming those models have identical functionality or responsibility boundaries.
How Tecell can help
Tecell provides EV charging software and infrastructure, and its enterprise partnership offering covers CMS capabilities, hardware integration, applications, roaming and operations support. Use that breadth to discuss the complete charging workflow, while keeping each contracted component clearly defined.
Explore UnityCharge (Tecell CMS) capabilities for network management, or review ChargeSphere roaming options if cross-network access is part of your strategy. Tecell’s charging infrastructure case studies also describe residential deployments using connected monitoring, access and billing.
Contact Tecell for a CMS demonstration and project discussion. Share your charger inventory, site power constraints, billing model and branding requirements so the discussion can focus on compatibility, implementation scope and commercial terms.
Frequently asked questions
What does EV charging management software do?
It provides a central software environment for connected charging infrastructure, including monitoring, session information, access management, billing and reporting. The functions available depend on the selected platform, charger capabilities and implementation.
Is UnityCharge the same as ChargeSphere?
No. UnityCharge (Tecell CMS) is the charge management software for charging operations. ChargeSphere is Tecell’s EV roaming hub for connecting charging networks and mobility-service participants. Their roles are related but distinct.
Will every OCPP charger work with Tecell CMS?
Do not assume compatibility from the OCPP label alone. Confirm the charger model, firmware, protocol version and required functions with Tecell, then test charging, meter information, remote controls and billing before acceptance.
Can a fleet use a CMS without public roaming?
Yes. A fleet can require central charging monitoring, access controls, usage reporting and load management without offering public charging or roaming access. Whether roaming is needed depends on its off-site charging strategy.
Does Tecell offer white-label charging software?
Tecell’s enterprise partnership page lists multi-tenant white-label capabilities and custom-branded mobile applications. Confirm the proposed branding scope, tenant permissions, application responsibilities and commercial terms for your deployment.
How much does Tecell CMS cost?
The supplied CMS – Basic plan listing is Price on request. Request a proposal covering deployment, connected equipment, applications, integrations and support. Hardware list prices should not be treated as complete software or installed-project pricing.