Short answer
Before choosing an OCPP EV charger supplier, ask which OCPP version is supported, which CSMS platforms have been tested, how charger identity is configured, whether RFID/QR/POS workflows are supported, which security profile is used, what logs can be exported and whether pre-shipment backend testing is included.
Many chargers claim OCPP support. Procurement teams need to know whether that means a basic demo connection, tested firmware, target CSMS compatibility, payment workflow support, security profile setup and after-sales troubleshooting.
Supplier questions that matter
| Question | Good supplier answer | Procurement risk |
|---|---|---|
| Which OCPP version? | Model-specific support for OCPP 1.6J, OCPP 2.0.1 or both. | Generic support statement may not match the exact model. |
| Which CSMS was tested? | Named CSMS platforms or a defined remote test process with buyer backend. | Untested backend can delay site commissioning. |
| How is charger ID configured? | Clear charge point ID, serial, connector count and firmware record. | CSMS may reject or duplicate charger identities. |
| What access methods work? | RFID, QR, app, POS, free charging or fleet account workflows. | Commercial operation may fail despite basic charging working. |
| What logs are available? | Boot, heartbeat, status, transaction, meter value, alarm and command records. | Troubleshooting becomes slow after installation. |
OCPP supplier evidence to request
Ask for a firmware version record, OCPP version statement, backend connection screenshot, transaction test record, RFID or payment workflow note, meter value export and remote command evidence. If the project uses a third-party CSMS, request a pre-shipment compatibility test or a documented acceptance test plan.
This page is different from a pure backend test checklist. It helps you choose the supplier before the test starts.
When OCPP 2.0.1 matters
OCPP 1.6J is still widely used for commercial charging. OCPP 2.0.1 may matter when the operator needs stronger device management, security, transaction model updates or future-proof network planning. The right answer depends on the CSMS, tender requirement and local operator workflow.
If the buyer does not know which OCPP version to choose, ask the supplier to explain the difference by charger model, firmware roadmap and target backend.
Pre-shipment acceptance scope
| Test item | Minimum pass condition | Evidence |
|---|---|---|
| Boot and heartbeat | Charger comes online and remains stable. | CSMS screenshot and charger log. |
| Authorization | RFID, app or free mode starts and blocks sessions correctly. | Accepted and rejected user records. |
| Transaction | Start, stop and meter values match charger and backend. | Session export with timestamp and energy data. |
| Remote commands | Remote start, stop, reset and availability setting work. | Command response log. |
| Alarm handling | Fault or offline events are visible to operator. | Alarm screenshot and recovery note. |
RFQ details for OCPP suppliers
Send charger power, connector standard, OCPP version, CSMS name, backend URL if available, network method, RFID or payment method, report requirement and target launch date. If the project is a CPO site, include tariff rules, user groups and required monthly reports.
RFQ hook
Send charger model, OCPP version, CSMS platform, backend URL, access method and target site workflow. SUNFULL can prepare a compatibility checklist before shipment.
FAQ
Is an OCPP statement enough when choosing an EV charger supplier?
No. Buyers should ask for model-specific firmware information, CSMS compatibility evidence and a pre-shipment test plan.
What is the most common OCPP procurement mistake?
The most common mistake is approving a charger based on a datasheet OCPP line without testing the exact charger model, firmware, network and target CSMS together.
Should RFID and payment be discussed with the charger supplier?
Yes. RFID, QR, app, POS and tariff workflows affect firmware settings, backend testing and site acceptance.
Can SUNFULL test with a buyer CSMS?
SUNFULL can define a remote pre-shipment OCPP test when the buyer provides target backend details, OCPP version and access workflow.
Related SUNFULL pages
Need to check OCPP supplier fit?
Send charger model, OCPP version, CSMS platform, backend URL, access method and target site workflow. SUNFULL can prepare a compatibility checklist before shipment.
How should buyers compare OCPP EV charger suppliers?
Compare the exact charger model, firmware, OCPP version, CSMS test evidence, RFID/payment workflow, security profile, log export and after-sales process. A supplier saying "OCPP supported" is not enough for commercial parking, fleet, CPO or OEM projects.
AC wallbox, 60kW DC, 120kW DC, 150kW DC or mixed AC/DC site.
OCPP 1.6J or 2.0.1, backend URL, charger ID, RFID, QR, POS, user groups, tariffs and reports.
Pre-shipment test, logs, firmware update path, fault handling and who answers after installation.
Ask SUNFULL to review your OCPP supplier checklist
Send charger model, OCPP version, target CSMS, user access method, payment needs, country and quantity. We can help map the charger and backend RFQ scope.
Supplier comparison should include the test path
A strong OCPP supplier can define how the charger connects, what is tested before shipment, what evidence is saved and how support continues after installation. This is more useful than a datasheet claim alone.
Separate charger protocol from site business model
OCPP handles charger-to-backend communication. The site still needs decisions on payment, tariffs, user access, receipt, reporting, maintenance workflow and operator responsibilities.
Buyer FAQ
What is the first OCPP question to ask a supplier?
Ask which OCPP version and firmware are supported by the exact charger model, not only by the product family.
Should payment be included in OCPP supplier evaluation?
Yes. RFID, QR, app, POS and tariff workflows affect configuration and acceptance testing.
Can SUNFULL help with both AC and DC OCPP chargers?
Yes. SUNFULL can discuss OCPP-ready AC wallboxes and DC fast chargers, depending on charger model and target CSMS scope.