EV charger software fees: compare the renewal bill before ordering the hardware

1. Separate the communication protocol from the paid service

The Open Charge Alliance describes OCPP as the communication protocol between charging stations and charging management systems. That describes a technical interface, not the price or commercial licence of a particular management platform.

Request three distinct answers from a bidder: what the selected charger can communicate, which management features the quotation includes, and what ongoing services the buyer must purchase. Keep the charger model, firmware, backend and protocol version attached to that answer. A general “OCPP supported” statement is not a substitute for the chosen system's integration evidence or a written software agreement.

2. Define the billing unit before comparing monthly prices

Ask each provider to identify exactly what creates a billable unit. The word “charger” is not precise enough for a comparison involving cabinets, multiple outputs, sites and user accounts. Require the provider's definition, an example inventory and a sample invoice using your own proposed equipment arrangement.

• Is a licence charged per site, station, charging point, connector, user or another defined unit?
• Does the quotation distinguish hardware identifiers from software billing identifiers?
• Are test equipment, inactive ports, replacement controllers and spare units counted?
• Does adding a second site create an additional minimum charge?
• Are there minimum quantities, volume tiers or fixed platform fees?

These are questions to resolve, not claims that every provider uses those charges. Mark each item as included, excluded, not applicable or awaiting confirmation. Keep unanswered items visible instead of treating them as zero-cost.

3. Build a fee register with four cost groups

Use one shared comparison sheet for all bidders. For each line, record the provider, charging unit, trigger date, quoted amount and currency, included quantity, exclusions and document reference.

• One-off setup: account provisioning, integration, agreed configuration, commissioning support and any branding work.
• Recurring services: platform access, hosting, connectivity, reporting, updates and agreed support.
• Usage-dependent services: any transaction, payment, roaming, messaging or API charges that apply to the proposed workflow.
• Change and exit work: adding sites, changing operators, exporting records, transferring administration or decommissioning accounts.

Do not add every possible fee automatically. Ask the bidder to confirm whether it applies and who invoices it. A payment processor, mobile-network provider and software supplier may have separate agreements; identify the actual contracting party for each required service. Request a redacted or synthetic sample invoice rather than another customer's private financial records.

4. Agree the activation event and delayed-site treatment

Record the exact milestone that starts each recurring charge. Possibilities to clarify with a provider include account creation, equipment registration, shipment, commissioning or operational acceptance. The buyer should not assume one applies unless it is written into the quotation.

Ask for worked scenarios covering a delayed installation, a pilot that does not expand, a replacement controller and a temporarily closed site. Which identifiers stay billable? Who can request suspension? What happens to agreed monitoring, data access and support? Require a documented answer without experimenting on production equipment or allowing required services to lapse.

For the separate responsibilities of connectivity providers, see the site network and SIM checklist.

5. Compare the same operating scenario over the same period

Give bidders the same equipment inventory, proposed commissioning dates, intended management features and comparison period. Request separate low-use, expected-use and expansion scenarios. These should be labelled planning assumptions, not forecasts or promised charging demand.

A useful comparison separates one-off confirmed charges, recurring charges over the chosen period, usage-dependent charges under the stated assumptions, and confirmed change or exit charges. Keep taxes, currency conversion and any unresolved exclusions visible for qualified commercial review. Do not claim a payback period from a software-fee comparison alone.

Ask who owns the spreadsheet and who approves updates when quantities change. For staged sites, show each activation date rather than multiplying the final equipment count across every month from day one.

6. Put renewal and expiry decisions on the project calendar

Ask for the contract period, renewal process, notice requirements, price-change mechanism and contact responsible for decisions. Record where the authoritative terms are stored and who receives renewal notices. Have the buyer's authorised reviewer confirm the wording; this checklist does not interpret or override a supplier contract.

Also request a feature-by-feature explanation of what happens at expiry or suspension. Do not assume that charging, payment, monitoring, reporting, exports or support continue unchanged. Agree an orderly continuity plan before any planned transition. The backend exit-readiness guide covers the technical handover as a separate task.

7. Accept the software scope with a practical demonstration

Before approving the agreed milestone, have authorised project staff demonstrate the purchased functions in the approved test environment or commissioning process. Confirm that the buyer's nominated administrators can access the promised reports and export a sample in the agreed format. Record configuration, acceptance date, unresolved items and responsible parties.

Check the first invoice against the agreed equipment register. Review discrepancies before expanding the rollout. Commercial acceptance should refer to the actual quoted feature list, not a product demo containing unpurchased options. Add the fee schedule request to your RFQ brief; the tool is a planning aid, not contract approval.

AC and DC SKD: keep documentation and software rights separate

For AC EV charger SKD kits and technical documentation, define the controller/component package, assembly instructions and any firmware or management-software rights for the selected configuration.

For DC EV charger SKD kits and technical documentation, separately agree the power/control integration scope, document revisions, software interfaces and qualified testing and service responsibilities.

Xiaochong recruits local production and assembly partners and offers project-scoped SKD components, assembly technical support and professional repair and maintenance skills support. Request available technical documentation free and specify the drawings, languages and training videos your team needs. Confirm availability and exact deliverables for the selected model. Free documents do not mean free hardware, hosting, all training, repair labour, certification or unrestricted source-code and intellectual-property rights.

Buyer FAQ

Does OCPP support mean the management software is free?

No. Protocol support and commercial software terms are separate. Request the exact feature set, licence scope, recurring charges and integration evidence for your selected configuration.

When should software billing begin?

Agree a specific contractual milestone and which identifiers become billable. Ask how pilot equipment, unopened sites, delayed commissioning and spare controllers are treated; do not assume they are exempt.

Are free SKD technical documents the same as a software licence?

No. Available AC or DC technical documentation can be requested free, while software licences, source-code rights, hosting, training and support scope require separate project agreement.

Request a complete hardware and software scope

Send Xiaochong Energy Technology (Zhongshan) Co., Ltd., China your country, AC or DC track, pilot quantity, proposed sites, intended backend and required software functions. Request free available AC or DC technical documents and state the languages needed by your qualified team.

Review the official partner programme, AC/DC SKD package and procurement guide. Confirm model-specific capabilities, licences and service obligations in the quotation.

xc0225888@163.com · Sales 1: +86 137 1772 6888 · Sales 2: +86 134 2580 6997