Factory Acceptance Test
OCPP Charger Pre-Shipment Testing Checklist (Factory Acceptance Test)
A buyer-side FAT checklist for importers and distributors who need an agreed charger acceptance scope before shipment.
Request an OCPP FAT scope before shipment
Agree the OCPP version, target CSMS environment, RFID or payment workflow, pass criteria and evidence format before the shipment gate.
Short answer
A defined factory acceptance test can check chargers before they leave the factory: the agreed OCPP workflows, a charging session, access or payment flow, functional options, firmware identity, safety records, labels, documents and packaging. FAT does not replace final on-site commissioning, but it can identify agreed acceptance issues before shipment.
FAT and backend integration testing have different jobs
This page covers buyer-side factory acceptance before goods ship. The OCPP backend testing checklist covers charger-to-CSMS integration and operator workflows. Use both when the project needs them: FAT controls the shipment gate, while backend testing validates the target CSMS behavior.
| OCPP check | What to verify | Example acceptance evidence |
|---|---|---|
| Boot or registration | The selected charger and firmware register with the agreed CSMS environment. | Timestamped online record with the expected charger identity. |
| Heartbeat | The agreed heartbeat behavior remains stable during the test window. | No unexplained repeated disconnects in the saved test record. |
| Authorization | The agreed RFID, app or user authorization flow. | Accepted and rejected test credentials produce the expected result. |
| Transaction start | The version-appropriate transaction-start workflow. | The session starts and is recorded by the CSMS. |
| Meter values | The agreed energy or power fields during the session. | Values are captured for comparison with the agreed meter evidence or tolerance, when applicable. |
| Transaction stop | The version-appropriate transaction-end workflow. | The session closes and the record is retained. |
| Status changes | Agreed availability, charging, fault and unavailable state transitions. | The target CSMS receives the expected state changes. |
| Remote commands | Only the remote functions included in the selected model and project scope. | The agreed commands return the expected response and result. |
Functional checks
Where included in the selected model and order, the FAT scope can cover charging output, connector lock and unlock, emergency stop, display states, language, RFID, QR or app workflow, cable handling, cooling behavior and configured power-sharing logic.
Safety records, labels and packaging
Ask which insulation, earth continuity, leakage protection and protection-function records can be supplied for the selected model and applicable project scope. Check the agreed nameplate, serial numbers, manuals, accessories, packing list and carton protection. Certification or test documents should be tied to the exact model and order scope, not inferred from a similar enclosure.
Pre-shipment checklist
- Selected charger model, firmware and OCPP version identified.
- Target CSMS environment and network method agreed.
- Applicable OCPP workflows and acceptance evidence defined.
- A charging session and agreed meter fields recorded.
- Applicable emergency-stop and protection records reviewed.
- Configuration, labels and serial-number scope recorded.
- Manuals, packing list and accessories checked.
- Photos, video, FAT report or independent inspection evidence agreed.
- Open deviations and the shipment-release decision documented.
How to request the FAT
FAT is not OCPP certification
A project FAT checks the behavior and evidence agreed for a specific order. It must not be presented as Open Charge Alliance certification. Any certification claim requires separate model- and version-specific evidence.
Authoritative references
These references support test-scope preparation; linking to them does not state that a SUNFULL model has Open Charge Alliance certification.
Supplier risk to watch
Risk signs include a broad "OCPP supported" statement without a version, model, firmware or test scope; no charger identity list; no saved CSMS evidence; or refusal to agree acceptance criteria before shipment. Ask for evidence tied to the selected model and batch.
Confirm the available SUNFULL evidence for the selected order
For a selected model and order, ask SUNFULL to confirm which FAT steps and evidence can be included. Protocol version, CSMS access method, functional options and report format must be agreed before the order. Model-specific documents or reports that are not published on the website can be requested through the sales team.
Need an OCPP FAT scope before shipment?
Send the charger model, OCPP version, target CSMS platform, required access workflow, quantity and evidence format. Any test credentials should be transferred only through an agreed secure channel.
Buyer FAQ
What is a pre-shipment FAT test for EV chargers?
A factory acceptance test uses an agreed scope to check OCPP workflows, charging functions, safety records, labels, documents and packaging before goods leave the factory.
Which OCPP messages should be tested before shipment?
The agreed test matrix can cover boot or registration, authorization, transaction start and stop, meter values, status, heartbeat and applicable remote commands for the selected OCPP version and project scope.
Should I test against my own CSMS?
Where possible, yes. Testing against a staging environment for the target CSMS can identify integration issues earlier. Final commissioning is still required after installation.
Can I use third-party inspection?
Yes. An independent inspection provider can witness the FAT when its scope, sampling method, access and evidence format are agreed before shipment.
What documents should I receive?
Agree the required FAT report, photos or video, firmware record, serial-number list, manuals, packing list and any model-specific document scope included in the order.
Does FAT replace on-site commissioning?
No. FAT reduces shipment risk, while on-site commissioning validates local power, network, vehicle and CSMS conditions.