This page is also available in French. Switch to French

This page is also available in Spanish. Switch to Spanish

How to choose EV charging management software: 15 questions

The software that runs your chargers decides who controls the hardware, where the money goes and how easily you can leave. These 15 questions work for any provider: what to ask, what a good answer looks like, and how to check it in the demo.

How to use these questions

Send the questions that apply to you to every provider in writing, before the demo, so the answers can be compared side by side.

In the demo, ask to see each answer, not hear it: a price change, a remote reset, an export of last month's sessions.

Score each answer from 0 to 3. 0: not available, or no clear answer. 1: partly, or only through support or at extra cost. 2: shown in the demo. 3: shown, documented and written into the contract.

One warning sign applies to every question: a routine task, such as a new price, a new RFID card or an export, that needs a support ticket.

Chargers and protocol

  • 1. Will it run the chargers I have, and the ones I will buy next?

    OCPP is the open protocol between chargers and their management software. Because it is open, an owner can switch to another charging network without necessarily replacing the chargers (OCPP 2.0.1 Part 0, §1). Ask for the list of supported models from several makers, add one of your own chargers during the demo, and make sure the charger settings and credentials stay yours. Warning sign: chargers sold only with a multi-year software term.

    What OCPP is
  • 2. Which OCPP versions, and which features in each?

    “Supports OCPP” is not a yes-or-no answer. OCPP 2.0.1 is not backward compatible with 1.6, and it changes security, session reporting and remote configuration (OCPP 2.0.1 Part 0, §2). The US minimum standards for NEVI projects and other publicly accessible chargers funded under Title 23 require OCPP 2.0.1 (23 CFR 680.108). Ask for a written list of the operations supported on each version, and which security profile your chargers will use.

    OCPP 1.6 vs 2.0.1

Operations

  • 3. How will I know a charger is down before a driver tells me?

    Look for live status per connector, not only per charger, with faults and their history. Ask who is alerted, how, and how a charger that is online but fails sessions shows up. Warning sign: “online” that only means the charger still reaches the server.

  • 4. What can I fix from a desk?

    Remote start and stop, availability changes, resets, firmware updates, configuration and the local authorization list should be a few clicks away, by role, with every command logged. Run a reset during the demo, and ask how chargers and RFID cards behave when the network drops.

    OCPP error codes

Prices, payments and drivers

  • 5. Can the pricing match how I want to charge?

    Check rates per kWh, per hour and free, time-of-use prices, idle fees with a grace period, session limits, and different prices for different groups of drivers. Ask the provider to build your real rate during the demo, and what a price change does to sessions already running.

  • 6. Can I bill by the kWh where my chargers are?

    Selling charging by the kWh can bring metering and receipt rules that differ by country, state and province. Ask your charger maker whether each model is approved for billing by energy where you operate, and ask the provider which time-based options it offers if it is not. This is not legal advice.

    How to charge residents
  • 7. Who holds the money, and what does each session cost me?

    Payments either go straight into your own account or pass through the provider first. Ask whose account a driver's payment lands in, when you are paid, and for every fee in writing, with the provider's fee shown apart from card processing. Warning sign: one blended percentage.

  • 8. Can a driver charge without an app or an account?

    Visitors and guests rarely want another app. Ask whether a driver can scan a QR code, see the price, pay by card and charge from the browser, and whether a QR code can be revoked if a sticker is tampered with. Test it on a phone that has never used the provider's app.

  • 9. How do I control who charges, when and at what price?

    Condos and workplaces need rules for residents or employees, visitors and schedules. Look for driver groups with their own prices, RFID cards you issue and revoke yourself, and control over whether a location shows on a public map. Create a group with a free rate during the demo and compare a member's session with a visitor's.

Electrical capacity

  • 10. Will it protect my electrical service?

    Load balancing lets several chargers share one circuit's limit. Ask for the limit to be set in amps, for single-phase and three-phase support, how the limit is shared between cars, and what a charger does if it loses its link to the software. Have your electrician confirm the limit you enter.

    What load balancing is

Data, security and exit

  • 11. Can I answer business questions without a spreadsheet project?

    You should see sessions, energy and revenue per location and period, paid sessions apart from free ones, and payments that reconcile with your payment provider. Export last month's payments for one location during the demo and check the columns.

  • 12. If I leave, what do I take with me?

    Ask who owns your session, payment and user data under the contract, whether you can export it yourself at any time, and how chargers are moved to another provider. Read the termination clause before the demo, not after.

    An exit plan in 10 questions
  • 13. How are my data and my drivers' data protected?

    Ask about encryption in transit and at rest, roles and individual logins instead of one shared account, where data is hosted, and how each charger proves its identity to the server. Ask how security is verified and who answers your security questions, and remove a user's access during the demo.

    5 security questions
  • 14. What works with it today, and what is only planned?

    Ask for two lists: integrations that are live today, such as accounting exports or utility programs, and those that are planned. A planned feature is not a feature. If you depend on one, put it in the contract with a date.

Cost

  • 15. What will it cost over five years?

    The price per port is rarely the whole cost. Add transaction fees or a share of revenue, card processing, onboarding, migration, support tiers, paid add-ons such as load management or reports, and what leaving would cost. Ask for every fee in writing and for references of a similar size.

Scoring and knock-outs

Give each question a weight for your site: 1 for nice to have, 2 for important, 3 for critical.

Multiply each score by its weight and add them up.

Whatever the total, treat a 0 on question 1, 7 or 12 as a reason to stop. These three decide whether you control your hardware, your revenue and your exit.

Then put the answers that matter into the contract. A sales call is not a commitment.

Contract checklist

  • Your data

    Who owns the session, payment and user data, and that you can export it yourself, at any time, in a standard format such as CSV.

  • Your chargers

    That charger settings and credentials are yours, and how the provider helps you move chargers to another provider.

  • The exit

    Notice period, any early-exit fee, an export window after the end, and written confirmation that your data has been deleted.

  • The money

    Whose account drivers' payments land in, when you are paid, what happens to funds in transit at the end, and the full fee schedule.

  • The protocol

    The OCPP versions and operations supported for your charger models.

  • Hosting and security

    Where data is hosted, who processes it on the provider's behalf, and how you are told about a security incident.

  • Support

    Support channels and hours, and any service levels with what you get if they are missed.

  • What you depend on

    Any feature or integration you rely on that is not live today, with a date, and the price protection for the first term.

Choosing EV charging software for a condo or HOA

For a condo or HOA board, four areas usually weigh most: who may charge and at what price (question 9), how residents pay and where the money goes (questions 5 to 7), how chargers share the building's electrical capacity (question 10), and how the board can leave a provider (question 12).

Boards and managers change, so ask how access is handed over when someone leaves: individual logins with roles, not one shared account.

If residents will pay per kWh, read the metering question (6) with your charger maker before you set a price.

How Connect Business answers

A pedestal charges a car, the driver's payment card at its screen. From the floor under the card the money runs as its own line straight to the door of the organization's building; the platform's servers stand apart, the other way, tied to the charger by a data line only.
48 ACharging Driver paymentsGoes toYour payment accountCard detailsNot stored
  • Chargers and protocol (1, 2)

    Connect Business works with OCPP 1.6 and 2.0.1 chargers from any manufacturer. For chargers that do not use OCPP, Kinethra can add the manufacturer's own protocol on its side.

  • Operations (3, 4)

    Chargers are monitored in real time: status, errors, online or offline. Staff get notifications by email and browser push, for example about charger faults, and notifications are configurable. Remote OCPP commands include start and stop, change availability, firmware update, read and change configuration, the local authorization list and Reset.

  • Prices and payments (5, 7)

    Fixed rates charge per kWh, per hour or nothing, and can vary by time of day and day of week. Fees include a security deposit, an activation fee, an idle fee with a free grace period and a per-minute price, and a reservation fee; session limits cap kWh or hours. Rate changes apply to new sessions, so sessions in progress are not interrupted. Each organization links its own Stripe account; drivers pay the organization directly, and Kinethra never holds the money or stores bank details. The Stripe country is chosen before the account is created and cannot be changed later.

  • Drivers and access (8, 9)

    Scanning a charger's QR code opens its Connect Go page with connector status, price and a start button, with no app. A QR code can be revoked, and a revoked code no longer starts charging. Driver groups, such as residents or employees, control who may charge, and different groups can have different prices. Without Stripe, chargers can run free for your own people, such as employees: the location stays off the public map and drivers reach it by QR code. To appear on the public map, a location needs Stripe linked, activated and verified.

  • Capacity and reports (10, 11)

    Load balancing lets several chargers share one circuit's limited capacity without exceeding it. Each group is single-phase or three-phase with a maximum group current in amps; on three-phase groups the limit applies to each phase. If a charger loses its link to the platform, by default it keeps its last current limit. Session analytics count sessions, revenue and energy, commercial and non-commercial, by day and cumulatively.

  • Exit and cost (12, 15)

    Sessions and payments export to CSV. OCPP chargers move to Connect Business without being replaced, with free migration. Connect Business is priced per port per month, quoted for your network, and Kinethra takes no commission on charging revenue.

Security and integrations in Kinethra (13, 14)

Every charger has its own unique OCPP authentication key and talks to the platform over a secure WebSocket channel (WSS).

The app, admin and API use TLS/HTTPS, and stored data is encrypted at rest.

Admin roles are Owner, Administrator, Manager, Technician and Read Only. Security questions are answered on request.

Integrations are tailored to your systems; talk to us.

Sources

  1. Open Charge Alliance (2025). OCPP 2.0.1 Edition 4, Part 0 – Introduction (opens in a new tab). §1 (switching networks without necessarily replacing chargers), §2 (not backward compatible with 1.6); accessed 2026-10-26.
  2. eCFR (2023). 23 CFR 680.108, Interoperability of electric vehicle charging infrastructure (opens in a new tab). §680.108(b); applicability per 680.100 and 680.102; accessed 2026-10-22.

Ask us these 15 questions

What happens next

  1. Tell us about your network.
  2. Meet a Kinethra specialist.
  3. Get your chargers live on Kinethra.
  • 40,000+ chargers onlineOn the Kinethra platform.
  • OCPP 1.6 and 2.0.1Kinethra works with OCPP chargers from any manufacturer.
  • No commission on charging revenueKinethra takes none.
  1. 01Contact
  2. 02Business
  3. 03Request

Step 1 of 3

We use your details to answer your request. See our Privacy Policy for details.