Short answer
An OCPP backend test should prove that the exact EV charger model can connect to the target CSMS, authorize users, start and stop sessions, upload meter values, report faults, accept remote commands and support the planned payment or RFID workflow. For commercial orders, run this test before batch shipment, not after site installation.
Why OCPP backend testing matters
The Open Charge Alliance defines OCPP as the open communication protocol between charging stations and charging management systems. In procurement, however, a datasheet line that says "OCPP supported" is not enough. Buyers need proof that the charger, firmware, network method, security profile and target CSMS work together.
This checklist is written for distributors, CPOs, fleet operators, parking operators and OEM buyers who need practical acceptance steps before importing DC fast chargers or smart AC chargers.
Test setup before connecting the charger
| Setup item | What to confirm | Why it matters |
|---|---|---|
| Charger identity | Charge point ID, serial number, connector count and firmware version. | The CSMS must recognize the exact device that will ship. |
| Backend URL | WebSocket endpoint, port, TLS setting and network route. | Wrong URLs and blocked ports are common commissioning failures. |
| OCPP version | OCPP 1.6J, OCPP 2.0.1 or both by model and firmware. | Message names and security expectations differ by version. |
| Security profile | Password, TLS server certificate or mutual certificate workflow. | Commercial networks often require stronger security than a basic demo. |
| User workflow | RFID, app account, QR, POS, fleet card or free charging mode. | Authorization must match real site operation. |
Core OCPP test checklist
Use the target CSMS, not a generic demo server, whenever possible. If the buyer does not have a CSMS yet, first define whether the project will use SUNFULL support, a third-party CPO platform or the buyer's own backend.
| Test step | Expected result | Evidence to save |
|---|---|---|
| Boot and heartbeat | Charger appears online and keeps a stable heartbeat. | CSMS screenshot and charger log. |
| Status notification | Each connector changes status correctly: available, preparing, charging, finishing and faulted where applicable. | Connector status timeline. |
| Authorization | RFID, app token or backend authorization allows and rejects users correctly. | Accepted and rejected user test records. |
| Start / stop transaction | OCPP 1.6J StartTransaction / StopTransaction or OCPP 2.0.1 TransactionEvent records match the session. | Transaction ID, connector ID and session timestamps. |
| Meter values | Energy, current, voltage and session data upload at the agreed interval. | Meter value export from CSMS. |
| Remote commands | Remote start, stop, reset and availability control work as expected. | Command log and charger response. |
| Fault and offline behavior | Fault alarms and offline recovery are visible to the operator. | Alarm log and recovery note. |
| Firmware workflow | Firmware version can be checked and update process is defined. | Version record and supplier update procedure. |
Payment and access tests
For paid charging, backend testing should include access and payment logic. RFID, QR and POS workflows are not the same thing. A charger may support OCPP but still need extra configuration for the operator's payment process.
- RFID: test authorized card, blocked card and unknown card behavior.
- QR or app: test user account start, session stop and record export.
- POS or card terminal: confirm who owns payment compliance, settlement and receipt logic.
- Fleet account: test driver groups, vehicle tags and monthly report export.
- Tariff: test price per kWh, time fee, idle fee or free charging rule.
Acceptance checklist for buyers
| Acceptance item | Pass condition | Who should confirm |
|---|---|---|
| Connection stability | Charger remains online during the test window. | Buyer IT / CSMS operator |
| Session data | Energy data, session ID and connector ID match charger display and CSMS record. | Buyer operations |
| Payment or access | RFID, QR, app or POS workflow starts and stops charging correctly. | CPO / parking operator |
| Remote maintenance | Remote reset, alarm review and support workflow are clear. | Supplier and buyer technical team |
| Export records | Reports can be exported for billing, accounting or fleet review. | Finance / operations |
RFQ information to send SUNFULL
Before requesting an OCPP compatibility confirmation, send this information so the test can be specific to your project.
- Target country, charger power and connector standard.
- Charger model or expected AC/DC charger mix.
- OCPP version required by the project.
- Target CSMS platform and backend URL if available.
- Network method: Ethernet, WiFi, 4G or SIM provider.
- Access method: RFID, app, QR, POS, fleet account or free charging.
- Required reports: session export, revenue, uptime, alarm log or energy data.
Procurement warning
If a project depends on a third-party CSMS, do not approve a batch order based only on a standard OCPP statement. Ask for a remote pre-shipment test using the target backend or a documented acceptance test with comparable settings.
FAQ
What should be tested before ordering OCPP EV chargers?
Buyers should test charger boot, backend connection, authorization, start and stop transaction, meter values, status changes, fault alarms, remote reset, firmware workflow, RFID or payment logic and report export with the target CSMS.
Is OCPP support enough without backend testing?
No. OCPP support should be verified with the exact charger model, firmware version, network method, security profile and CSMS platform that will be used in the project.
Should OCPP testing happen before shipment?
Yes. Pre-shipment OCPP testing reduces commissioning risk because the buyer can confirm charger identity, backend URL, RFID or payment workflow and remote commands before goods leave the factory.
What is the difference between OCPP testing and CSMS testing?
OCPP testing verifies charger-to-backend message behavior. CSMS testing verifies the operator workflow such as users, tariffs, payment, reporting, alarms and maintenance actions.
Official references
Related SUNFULL pages
Need an OCPP backend test before ordering?
Send your target CSMS, OCPP version, charger power, connector type and payment method. SUNFULL can help define a practical pre-shipment test plan.