Your OCPP software, also called a CSMS (Charging Station Management System), is the tool you will use every day to run your chargers. It decides how quickly you see a fault, how easily you add a new site, and how much control you have over your own data. Changing it later is possible, but it takes effort, so it pays to choose carefully.
This guide gives you a 12-point checklist for evaluating OCPP software, a list of red flags, and a simple scorecard you can use to compare providers side by side. It is written for charge point operators, fleet managers, facility managers and installers.
- Protocol support and hardware independence come first: the software must work with the chargers you have and the chargers you will buy.
- Daily operations depend on fast onboarding, live monitoring, remote commands and clear alerts.
- An API, webhooks and full data export protect your investment and let you leave if you need to.
- Understand the pricing model in detail, including setup fees and any commission on your charging revenue.
Why the choice of OCPP software matters
Chargers are only as useful as the system that manages them. Good software lets a small team operate many sites, because problems are visible and many of them can be solved remotely. Weak software creates manual work, missing data and unhappy drivers.
The choice also affects your independence. OCPP is an open protocol, so in theory you can change software at any time. In practice, you depend on how easily you can export your data, reconnect your chargers and replace integrations. Keep this in mind throughout the evaluation.
The 12-point evaluation checklist
1. Protocol versions
The software should support OCPP 1.6J, 2.0.1 and 2.1, ideally in the same dashboard. Most networks contain chargers of different ages, and you do not want separate systems for each generation. For background, see our comparison of OCPP 1.6J, 2.0.1 and 2.1.
2. Hardware independence
Ask which charger brands and models have been connected successfully. A hardware-agnostic system lets you choose the best charger for each site. Be careful with software that only works well with one manufacturer.
3. Onboarding
Adding a charger should be quick and should not require a support ticket. Check how the connection URL is provided, how charge point IDs are handled, and whether unknown chargers that connect are shown so you can add them.
4. Live monitoring
You should see connector status, current power, energy and, where the charger reports it, the vehicle state of charge. A map view helps when you manage many locations.
5. Remote commands
Check which OCPP commands are available: soft and hard reset, remote stop, unlock connector, change availability, change configuration and trigger message. Each command result should be logged so you can see what happened.
6. Access control
You need RFID card management, the ability to block or suspend cards, and rules for which drivers may use which stations. A clear list of rejected authorizations, with the reason, saves a lot of time when drivers call support.
7. Energy rules and limits
For fleets, workplaces and residential sites, kWh quotas per driver or vehicle are often more useful than prices. Check whether limits can be daily, weekly or monthly, and whether they stop charging or only warn. Also ask what is available today and what is only planned, for example dynamic load management.
8. Reporting
Reports should show energy by station, driver, vehicle and date, and should export to formats your accounting team uses. Session history must be searchable with filters.
9. API and webhooks
A documented REST API lets you connect ERP, fleet or BI systems. Webhooks push events such as session start and stop to your systems in real time. Ask for public API documentation and check how webhooks are secured, for example with signatures.
10. Security
The software should support encrypted wss:// connections with TLS, role-based access for team members and searchable OCPP message logs. Ask where data is hosted and how access is controlled.
11. Languages and usability
If your team, customers or drivers speak different languages, check which languages the dashboard and driver app support, including right-to-left languages if needed. A clear interface reduces training time.
12. Pricing model and data ownership
Understand every cost: setup fees, per-connector or per-station fees, transaction fees and any commission on your charging revenue. Then check the exit path: can you export all sessions, drivers and cards, and can you move your chargers to another system by changing one URL?
Red flags to watch for
- The provider cannot say clearly which OCPP versions and charger models are supported.
- Roadmap features are presented as available. Ask for a live demonstration of every feature you need.
- There is no public API documentation, or the API is only available on request.
- You cannot export your data in a standard format.
- The software takes a percentage of your charging revenue without a clear reason.
- Chargers must be reconfigured by the provider for every change.
- There are no message logs, so every problem requires a support ticket.
A simple scorecard for comparing providers
Score each provider from 0 to 3 for every criterion, where 0 means "not available" and 3 means "fully meets our needs". Weight the criteria according to your business model. A fleet operator will value limits and reporting more; a public CPO will value monitoring and uptime more.
| Criterion | What to check | Provider A | Provider B |
|---|---|---|---|
| Protocol versions | 1.6J, 2.0.1, 2.1 in one dashboard | ||
| Hardware independence | Brands and models tested | ||
| Onboarding | Time and effort to add a charger | ||
| Monitoring | Live status, power, energy, map | ||
| Remote commands | Reset, stop, unlock, availability, logging | ||
| Access control | RFID, blocking, station rules, rejection reasons | ||
| Energy rules | kWh limits per driver or vehicle | ||
| Reporting | Filters, exports, PDF and spreadsheet | ||
| API and webhooks | Public docs, signed webhooks | ||
| Security | TLS, roles, message logs | ||
| Languages | Dashboard and driver app | ||
| Pricing and exit | Fees, commission, data export |
How Üreticy fits this checklist
Üreticy is a cloud OCPP software designed around these points. It supports OCPP 1.6J, 2.0.1 and 2.1 over WS and WSS in one dashboard. Each customer receives a personal OCPP URL, and unknown chargers that connect appear as pending so you can add them with one click.
The dashboard shows live status, power and energy on a map, supports remote commands with logged results, and manages RFID cards, drivers, vehicles and kWh limit rules. Reports export to Excel (CSV) and branded PDF. A REST API with HMAC-signed webhooks and public documentation is available, and the dashboard is available in six languages. Pricing is a per-connector subscription with no setup fee and no commission on your charging revenue.
Dynamic load management, OCPI roaming and online payments are on the roadmap, so check whether you need them today. You can compare the full list on the features page.
How to run a fair evaluation
- Write down your must-have and nice-to-have requirements before you talk to providers.
- Shortlist two or three providers that meet the must-haves.
- Connect at least one real charger of each model you use during a trial.
- Test a full day of operations: onboarding, a charging session, a rejected card, a remote reset and a report export.
- Read the API documentation with your developer, if you plan integrations.
- Compare scores and total cost over several years, not only the first month.
Frequently asked questions
What is the difference between OCPP software and a CSMS?
In practice, they mean the same thing. CSMS stands for Charging Station Management System, the term used in OCPP 2.0.1 and later. OCPP software is a common everyday term for the same kind of system that manages chargers through the OCPP protocol.
Can I change my OCPP software later?
Yes. Because OCPP is open, you can usually move chargers to a new system by changing the server URL in the charger settings. Before you switch, export your session history, drivers and cards, and plan the change site by site.
Is cloud OCPP software secure?
It can be very secure if it supports encrypted WSS connections with TLS, role-based access for team members and message logs. Ask the provider how access is controlled and use TLS on every charger that supports it.
Should I pay a commission on charging revenue?
That depends on the value you receive, but you should understand the model clearly. A commission grows as your revenue grows, while a per-connector subscription stays predictable. Compare the total cost for your expected network size over several years.
How long does a proper evaluation take?
It depends on your network size and requirements. A focused trial with real chargers and a written checklist gives you much better information than a sales demonstration alone. Plan enough time to test daily operations, not only the setup.
Want to test the checklist on real chargers? Explore Üreticy OCPP software and see the per-connector pricing.