EV Charging Software FAQs

EV charging software covers charger communication, driver access, sessions, pricing, payments and reporting. A charging point management system (CPMS), also called a CSMS, is the operator-facing part that monitors and controls chargers. TrendPower can combine the CPMS with a branded driver app, payment workflows and energy management in one project. EV charging software vs CPMS: key differences →

TrendPower works with OCPP 1.6J and OCPP 2.0.1 project requirements. OCPP 1.6J remains common in deployed networks; OCPP 2.0.1 provides a broader framework for device management, security and smart charging. Available functions depend on the charger firmware, implemented profiles and integration tests. Compare OCPP versions →

OCPP 2.1 is a newer specification, but it should not be assumed to be included in an OCPP 2.0.1 integration. Share your charger model, firmware and required OCPP 2.1 functions; TrendPower can assess the integration scope and roadmap before quoting.

Yes, for chargers that pass project compatibility testing. TrendPower reviews OCPP messages and tests authorization, start and stop, status, meter values, faults and any required smart-charging functions for each model and firmware version. A charger’s OCPP claim alone is not a substitute for commissioning tests.

OCPP connects the charger to its backend. OCPI exchanges locations, tariffs, sessions and charging records between roaming partners. ISO 15118 governs communication between a vehicle and charger and can enable Plug & Charge. They solve different parts of a charging journey and need separate integration decisions.

TrendPower can scope OCPI 2.2.1 roaming integrations and ISO 15118-related workflows for suitable projects. Roaming requires partner agreements and interface testing; Plug & Charge also requires compatible vehicles, chargers and certificate infrastructure. Neither feature is enabled simply by choosing an OCPP version.

A project can combine a charger management dashboard, branded driver app or web app, site-host portal, payment and billing workflows, analytics and energy-management functions. TrendPower offers modules independently or as an integrated platform; the scope is set around your network and operating model. Explore TrendPower services →

TrendPower offers white-label interfaces for a driver app, web portal and operator dashboard. Branding can cover the name, logo, colors, domain and selected user journeys. App-store accounts, domain ownership, language coverage and ongoing updates should be defined in the project agreement. Explore white-label software →

Integration can be planned through project-specific APIs and data exchange. Share the systems, API documentation, authentication method and required events such as session completion, invoicing or customer updates. TrendPower can then define the data flow, responsibilities and test plan.

Migration starts with an inventory of charger models, firmware, OCPP endpoints, credentials, users, tariffs and historical data. TrendPower can plan a pilot, charger reconnection, data mapping and staged cutover. The ability to transfer historic sessions or retain an existing app depends on access to the current provider and export formats.

Multi-role access can separate network administration, site operation and partner reporting. Define which users may change prices, see driver information, monitor equipment or view revenue before configuration; tenant structure and site-host reporting are specified for each project.

A project can offer QR-code guest checkout through a mobile web page, subject to the selected payment gateway and local requirements. TrendPower can also scope app payments, RFID authorization or payment terminals where the market requires them. See charging payment options →

Payment options depend on the country, merchant account and processor. TrendPower can assess card, mobile-wallet, local-gateway and terminal integrations during solution design; confirm supported methods, fees, refunds, currencies and payout responsibility with the chosen provider before launch.

TrendPower can configure pricing rules based on energy, time, sessions, site, customer group and peak or off-peak windows. Idle fees, grace periods and promotional rules can be scoped as needed. Metering, tax and price-disclosure requirements should be validated in the target market.

The platform can link charging sessions and payments to reporting for operators and site partners. Define the split formula, payment provider, taxes, refunds, invoice owner and payout schedule at the start; settlement is then configured around those commercial rules.

There is no useful flat price without a project scope. Cost depends on charger count, modules, hosting model, app branding, payment and third-party integrations, localization and support. Ask TrendPower for a proposal that separates implementation, recurring platform fees, payment-provider fees and optional customization.

These are contract terms, not automatic features of a white-label package. The proposal should specify customer data access and export, app-store and domain accounts, hosting, custom deliverables, source-code licensing and exit assistance. TrendPower can discuss enterprise licensing requirements during solution planning.

Security can include encrypted transport, role-based access and project-specific credential or certificate management. OCPP 2.0.1 security features depend on the selected charger and its implemented profiles. Review access, logging, firmware and incident processes with the TrendPower team before deployment.

TrendPower can discuss regional hosting, access control and data-handling workflows as part of the architecture. Legal compliance depends on the countries involved, the roles of each party, payment partners and your operating procedures; agree on retention, deletion and processor responsibilities during scoping.

A German deployment needs a compatible certified meter, signed measurement data, suitable charger firmware and the required driver-verification and billing flow. TrendPower can assess the relevant data and interface work for a proposed hardware combination; compliance must be confirmed for the complete local implementation.

OCPP compatibility and formal OCA certification are different claims. Ask for the exact product, protocol version, certified profiles and certificate if certification is a procurement requirement. TrendPower can share project compatibility details and test scope for the chargers you plan to use.

Depending on project needs, TrendPower can scope SaaS, public-cloud, private-cloud, on-premises or hybrid deployment. The proposal should define infrastructure ownership, backups, updates, security responsibilities and data location for your chosen model.

The outcome depends on charger firmware and configured offline authorization. A compatible charger may allow approved local credentials and store session data for later synchronization; live monitoring and remote commands will be unavailable until the link returns. Test outage and recovery behavior with the actual hardware.

The CPMS can present charger status, alerts, session history and supported diagnostics so staff can distinguish connection, authorization and equipment issues. Remote actions depend on the charger’s OCPP implementation; physical faults still require a field technician or manufacturer.

A typical TrendPower project starts with requirements and hardware review, then interface design, charger and payment integration, configuration, testing, deployment, training and operational support. Pilot testing with the intended charger models and payment flow helps identify issues before wider rollout.

TrendPower provides operational support as part of its software services. Before signing, agree on support hours, response priorities, update responsibilities, escalation contacts and any service-level commitments in writing; the exact support package varies by project.

TrendPower offers fleet charging software for depot operations. Project scope may include vehicle and driver authorization, scheduled departures, charger visibility, energy allocation and operational reporting. Provide the fleet size, vehicle schedules, charger ratings and site power limit for a practical design. Explore fleet management →

A site controller or meter can provide available-power data, allowing compatible chargers to receive adjusted charging limits. Allocation can follow site caps, schedules and vehicle priorities. Meter access, network reliability and charger support must be checked during engineering; software does not increase the electrical connection capacity.

A fleet project can link eligible home-charging sessions to a driver or vehicle and produce reimbursement reports. Accurate reimbursement requires an agreed metering method, tariff policy, eligibility rules and local tax treatment.

TrendPower’s zero-carbon park solution can combine PV, energy storage, charging and site-demand data for monitoring and scheduling. Actual dispatch depends on equipment interfaces, site control permissions and engineering design. Explore PV–ESS–charging integration →

Yes. A residential or workplace project can define access for residents, employees, visitors or tenants, along with authorization and site-specific pricing. Confirm parking rules, meter allocation and who bills each user before building the workflow.

TrendPower also offers e-bike and micromobility charging and shared battery-swapping software. These projects use different devices and operational flows from car charging; share cabinet or charger protocols, rental rules and payment needs for a tailored assessment. Explore battery swapping →

TrendPower can localize interface language, currency, time zones and operating workflows. Payment methods, taxes, data hosting and regulatory obligations must be designed for each market, so a multi-country rollout should use a country-by-country requirements list.

Founded in 2005, TrendPower develops digital-energy and EV charging software for charge point operators, charger manufacturers, property groups, fleets and energy companies. Its published company profile describes a team of more than 100 professionals focused on AI, IoT and energy digitalization. Meet TrendPower →

Both approaches are available. TrendPower’s services cover charger management, branded user journeys, payments, micromobility, PV–ESS–charging and intelligent operations; modules may be deployed independently or combined. This lets a project start with essential workflows and add integrations as needs become clear.

Send your country, business model, expected charger count and growth plan, charger brand and OCPP version, required app and payment flows, deployment preference and desired launch date. Include existing system APIs, site power constraints and any regulatory requirements so TrendPower can propose a meaningful pilot and scope. Contact TrendPower →