From one accepted charger to a repeatable rollout

1. Record what actually passed the pilot

Give the accepted pilot a dated reference record. Identify the charger model and variant, hardware revision, firmware version, connector configuration, agreed accessories and relevant settings. Link the actual test report and its open exceptions. Record which backend, authorization or payment arrangement was used rather than writing only “OCPP tested”. Keep credentials and sensitive network information in controlled systems, not a shared purchase-order attachment.

Distinguish a demonstrated feature from a contractual requirement. If the pilot used one vehicle, one connector and a test backend, do not silently extend that result to all vehicle variants, all concurrent sessions or a different production platform. Use the mixed-fleet pilot checklist for the actual test population and the simultaneous-output matrix where multiple connectors matter.

Record limitations in the same place as the successful result. A temporary manual workaround, missing accessory or untested offline scenario should remain visible when purchasing approves the next quantity. “Pilot accepted with exceptions” and “all requirements verified” are different decisions.

2. Create one configuration sheet for the purchase order

The following is a suggested buyer record, not a universal compliance form. Agree who maintains each field and which changes must be notified before manufacture, shipment or field deployment.

Do not require a supplier to publish unrestricted proprietary design files merely to establish traceability. A project can agree the document identifiers and controlled information necessary for purchasing, assembly and service without transferring every drawing or source-code right.

3. Treat version information as evidence, not paperwork

The Open Charge Alliance certification programme describes independent testing for OCPP conformance and provides different certification paths by protocol version. Buyers should verify the actual applicable product evidence; a protocol label alone does not establish every site function or destination-market approval.

A concrete manufacturer example is Alfen's AHP firmware 2.1.0 release note. It identifies the supported hardware platform, release version and changes including protocol support and operational fixes. The lesson is to request a release note and applicability information for the equipment you buy. Alfen's functions, firmware and certification do not apply to Xiaochong equipment, and this example is not an endorsement.

For your project, ask which agreed requirements a proposed release affects. The right response may be targeted regression evidence, updated documentation or a repeat of selected pilot checks. The responsible technical team must define that scope; this guide does not assert that every change requires full recertification or that any particular change is exempt.

4. Make substitutions a controlled decision

A parts shortage or locally available alternative can create pressure to accept a “similar” component. Request the proposed part identifier, reason for the change, affected assemblies, compatibility assessment and document revisions. Ask the responsible engineering and compliance teams what evidence is needed. Similar appearance or an isolated nameplate rating does not establish interchangeability.

Separate the proposal, approval and implementation records. A supplier email suggesting an option is not proof that the buyer approved it or that every unit contains it. The agreement should identify who has authority to accept a deviation and how its effect on cost, delivery, support and acceptance is recorded.

Do not make configuration control a reason to suppress needed security or safety action. Define an urgent escalation route, authorized decision-makers and model-specific validation or recovery plans. Avoid uncontrolled field experiments, unsupported downgrades or bypassing protections in order to reproduce the old pilot state.

5. Keep AC and DC SKD tracks traceable separately

For AC EV charger SKD kits and technical documentation, agree the selected variant, supplied component scope, approved locally sourced items, assembly-document revisions and qualified quality checks. Link the assembled unit to the parts and document versions used. Do not infer an AC product's rating or certification from a photograph of its mainboard.

For DC EV charger SKD kits and technical documentation, agree the power/control component scope, integration dependencies, relevant software configuration, approved test evidence and maintenance documentation. A change to one subsystem must be reviewed for the actual product; the kit label alone does not prove the completed assembly matches the pilot.

Both tracks need an explicit supplied-versus-local responsibility list. Clarify who updates drawings, trains qualified personnel, controls superseded instructions and supports revision-specific spare parts. Confirm software-use permissions and access rights in the project agreement. A free technical-information offer does not mean unrestricted source code or all intellectual property is included.

6. Release batches with a short exception report

Before shipment, ask for a record that maps the proposed batch to the accepted baseline. List deviations, approval references, relevant validation results and outstanding actions. Use the same identifiers in the receiving record so the local team can recognize what was ordered and what arrived.

For example, imagine a pilot identified as hardware revision A and firmware release X. If a later batch uses revision B or release Y, the buyer should be able to find the change description, responsible review and acceptance evidence without reconstructing the decision from scattered messages. These are fictional identifiers illustrating the record structure, not Xiaochong model designations.

Agree how mixed revisions will be supported in the field. The maintenance team needs to identify the installed configuration before ordering spares or choosing instructions. Keep public marketing claims separate from the controlled service record. See the local spare-parts checklist and delivery handover guide.

7. Compare the cost of an accepted batch

A lower unit quotation may have a different document, validation, training or support scope. Compare those inclusions before assuming that two batch offers are equivalent. Record the commercial treatment of approved changes, additional reviews and unresolved exceptions in the actual agreement; no saving percentage follows automatically from using this checklist.

Start with the free RFQ brief builder, then attach the baseline and change-review requirements. The tool is a planning aid, not engineering, regulatory, contractual or installation approval. Keep the factory/site acceptance plan aligned with the configuration being supplied.

Buyer FAQ

Does a successful pilot automatically approve every later charger batch?

No. Compare each batch with the accepted hardware, firmware, configuration and document baseline. Review differences and agree the necessary evidence before release.

Can an apparently equivalent SKD component be substituted without review?

Do not assume equivalence from appearance or a similar rating. Request a documented impact review and approval under the agreed project process before substitution.

Does configuration control mean never updating charger firmware?

No. It means identifying the change, reviewing its impact, agreeing appropriate validation and keeping traceable records. Urgent security or safety changes need a defined escalation path, not indefinite delay.

Discuss a repeatable AC or DC supply programme

Xiaochong Energy Technology (Zhongshan) Co., Ltd., China supports commercial charging projects and recruits overseas local-production and assembly partners. Send your country, company, AC or DC track, pilot/annual quantity and required configuration. Discuss SKD components, production/assembly support, professional repair and maintenance skills and available training videos.

Free AC or DC technical documentation is available on request. State the required language; confirm the actual model, document/drawing revisions, permitted use, training, testing and support scope. Hardware, all training, repair labour, certification and unrestricted IP are not automatically free. Xiaochong has helped multiple customers work toward required certifications; contact the project team for model- and market-specific evidence, not an assumption that every model holds every approval.

Review the official partner programme, AC/DC SKD technical-output scope and procurement guide.

xc0225888@163.com · Sales 1: +86 137 1772 6888 · Sales 2: +86 134 2580 6997