How to Verify a DC Charger Manufacturer in China: Factory Audit, FAT and SAT Checklist
Turn supplier claims into a verified chain of legal identity, exact SKU, production control and acceptance evidence.
Direct answer: Verify a DC charger manufacturer through a controlled evidence chain, not a showroom visit or a certificate logo. Match the legal supplier, exact SKU, rating label, technical documents, production build, firmware, connector, destination requirements and acceptance tests. A factory can be real while a quoted configuration remains unverified; the purchase decision should stop until both are proven.
Why a factory visit alone is not enough
An on-site visit can show people, equipment and activity. It cannot by itself prove that the entity on the quotation owns the quoted product design, that the certificate covers the exact model, that the supplied build will match the sample, or that the charger will work with the intended vehicles and charging-management system.
For DC charging, the important question is not “Is there a factory?” It is “Can this supplier repeatedly deliver the exact configuration that this project needs, with evidence that survives document review, factory testing and site acceptance?”
The Four Evidence Planes
Four evidence planes must connect
| Evidence plane | Question the buyer must answer | Minimum artifact | What it cannot prove alone |
|---|---|---|---|
| Company | Who is contractually responsible for this offer? | legal entity name, address, signing authority | exact product compliance or production ownership |
| Product | What exact charger is being quoted? | model, rating basis, connector, drawing and revision | field interoperability or destination approval |
| Production | Can the approved build be repeated? | inspection points, serial traceability, approved substitutions | the product works at the buyer’s site |
| Operations | Does the ordered system perform in the intended workflow? | FAT, pilot/SAT plan, vehicle/CSMS test records | future uptime or universal compatibility |
Use a hard-stop gate before weighted scoring
Many supplier scorecards give points for price, lead time, certificates and appearance. That can hide a critical mismatch. Apply hard stops first:
| Hard-stop question | Stop the decision when | Evidence needed to continue |
|---|---|---|
| Legal identity | quote, contract, certificate and invoice identities do not reconcile | documented legal/contract responsibility map |
| Exact SKU | the quote has no stable model/rating/connector definition | configuration sheet and label/drawing match |
| Destination route | applicable market/use requirements are unknown | destination compliance and responsible-party checklist |
| Certificate scope | product designation, report, standard or version does not match | certificate/DoC/report field match |
| Integration | vehicle/connector/CSMS behavior is only promised verbally | defined pilot/FAT/SAT test case |
| Change control | supplier may substitute components/firmware without notice | approved-substitution and retest rule |
Only after the hard stops pass should a buyer compare commercial variables such as payment, spare parts, delivery plan or training scope.
The Five-Link Supplier Evidence Chain
Link 1: market rule
Start with the destination, use case and responsible party. Public paid charging, private fleet charging, workplace equipment and export distribution can have different requirements for electrical safety, metering, payment, data, installation and local approval. A document from one market cannot be assumed to clear another.
Link 2: exact SKU
Freeze the exact product identity before asking “Does it comply?” Record the model, DC output basis, connector, cabinet/dispenser relationship, input assumptions, environmental configuration, cable, communication option and visible label fields. For a multi-output product, state whether the kW figure is cabinet total, per output, or dynamically shared.
Link 3: build
The buyer should match the technical file, declaration, reports, drawings, firmware baseline and backend profile to the frozen SKU. A generic product catalogue is helpful context; it is not a controlled configuration record.
Link 4: repeatable production
Audit how the supplier records serial numbers, incoming inspection, in-process checks, final tests, non-conformities, rework and approved substitutions. Do not ask for a “factory capacity” claim unless the supplier can provide a defined, auditable basis and scope.
Link 5: acceptance and change control
Turn the intended operation into FAT, pilot and SAT test cases. Add written triggers for a material change: firmware, power module, connector, meter, communication board, safety component, enclosure or approved manufacturing location. A change may require document review, retest or both.
Build a Claim-to-Artifact Matrix
| Supplier claim | Artifact to request | Fields that must match | Verification route | Change/retest trigger |
|---|---|---|---|---|
| “We manufacture this charger” | legal entity and contractual responsibility record | supplier name/address, signatory, contract party | legal/entity review | entity or production responsibility changes |
| “This model is compliant” | DoC, certificate/report, technical file | exact model, variant, standards, date, report reference | issuer/official database where applicable | model, standard, critical component or market changes |
| “OCPP supported/certified” | OCA certificate/product record plus integration scope | product designation, version, certificate holder | OCA official verification plus CSMS test | firmware, product designation or backend profile changes |
| “480 kW charger” | configuration sheet, drawing and rating label | total/per-output basis, voltage/current, connector, sharing rule | FAT against order | output architecture or sharing logic changes |
| “Same as approved sample” | serial traceability and approved-substitution list | BOM/revision, firmware, critical parts | sample-to-production comparison | any unapproved substitution |
The European Commission explains that the manufacturer is responsible for conformity assessment, technical documentation, the EU Declaration of Conformity and CE marking. For a buyer, the practical lesson is to match those records to the exact ordered product—not to treat a CE logo as a blanket approval. European Commission manufacturer guidance
Check the quote against the physical charger
Before shipment, inspect an agreed sample or FAT build with the configuration sheet in hand.
| Quote field | Physical/document check | What fails if it does not match |
|---|---|---|
| Model and serial number | label, unit record, test report and packing list | traceability disappears |
| Output basis | cabinet, dispenser, connector and sharing configuration | power expectation becomes ambiguous |
| Connector/cable | connector type, cable reach and marking | vehicle/site interface mismatch |
| Input and protection | drawing, label and site single-line assumptions | electrical integration risk |
| Firmware/backend | version, endpoint/profile, access/authorization logic | system may not operate with CSMS |
| Documents | revision/date/model references across manual, report and declaration | certificate or manual may cover another build |
Do not accept a document bundle merely because the filenames look correct. The matching fields are the evidence.
The Three-Sample Gate
Three samples must agree before a bulk release
→
→
→
Passing one sample alone does not prove the next. The same configuration identity must travel through all three stages.
Paper sample
Review the quote, product configuration, drawing, standards, reports, declaration, warranty responsibility and delivery scope. This is where mismatched names, models and scope are cheapest to correct.
Physical sample
At FAT or pilot inspection, match the actual cabinet/terminal, labels, connectors, visible wiring or modules where contractually accessible, serial record and software build to the approved documentation.
Operational sample
Exercise the intended vehicle, connector, authorization, CSMS, alarms, power-allocation behavior, stop/recovery sequence and session-data workflow. OCPP certification or support language is not a substitute for the actual project integration test. Open Charge Alliance provides a route to verify official OCPP certificates and certified product identity. OCA certificate verification
Define FAT and SAT before a purchase order
| Stage | Purpose | Minimum recorded fields |
|---|---|---|
| Document review | lock the ordered configuration | model, revision, connector, rating basis, standards, responsible party |
| FAT | exercise factory-testable functions of the ordered build | serial number, test equipment, date, results, exceptions, firmware |
| Pilot / integration | prove the actual vehicle and backend workflow | vehicle/model context, connector, CSMS profile, transaction and fault results |
| SAT | prove site installation and handover state | site input, communications, protection, session, alarm/recovery and open items |
| Close-out | control residual risks and changes | defect owner, due date, retest result, document revision |
A pass/fail box without test conditions, unit identity and exception handling is difficult to audit later. Define who witnesses each test, which evidence is retained and who accepts a deviation.
Control firmware, BOM and substitutions
The same exterior enclosure can conceal a different firmware, power-sharing rule, communications board, connector assembly or critical safety part. The purchase order should define:
- approved model/configuration and document revision;
- firmware baseline and approved CSMS/backend profile;
- which parts may not be substituted without written approval;
- notification period for material changes;
- whether the change needs document review, FAT repeat, pilot repeat or SAT confirmation;
- serial number and build record supplied with each unit;
- spare-parts, warranty and escalation responsibilities.
This is not bureaucracy. It is the bridge between a successful sample and repeatable project delivery.
Red flags and the next verification step
| Red flag | Likely missing boundary | Next action |
|---|---|---|
| Certificate has a familiar logo but no exact product designation | certificate scope | request issuer/product/report field match |
| Quote says 240 kW but does not say cabinet or connector basis | power allocation | require configuration and sharing statement |
| Supplier says “all protocols supported” | implementation scope | define exact vehicle, CSMS, version and test workflow |
| Factory video shows equipment but not the quoted unit | build identity | request serial/rating/configuration evidence at FAT |
| Sample works but bulk changes are not controlled | change management | add approved-substitution and retest clause |
| Project acceptance is left to “commissioning” | operational evidence | attach FAT/pilot/SAT protocol to contract |
HG Power evidence and configuration scope
HG Power’s approved public DC portfolio context is 40–480 kW. An exact configuration still requires the target connector, output basis, voltage/current envelope, sharing behavior, market evidence, communication scope and site conditions.
For example, the reviewed CCS1 manual applies to named 120/180/240/360/480 kW models; it is not evidence for all 40–480 kW products, other connector families or every export market. A reviewed 480 kW Split DC Charging Station certificate demonstrates why buyers should inspect product designation, model family, report reference and its stated one-sample limitation. It must not be presented as portfolio-wide certification or production assessment.
HG Power can provide a model-specific Supplier Evidence Pack for a defined RFQ. The pack should be reviewed as evidence for the quoted configuration, not as a universal promise about every product or market.
Request a supplier-audit and RFQ pack
Send these inputs before comparing suppliers:
- destination country, installation/use case and responsible project party;
- vehicle models/markets and connector requirements;
- DC output target, cabinet-versus-connector basis and concurrent sessions;
- input/site assumptions, environment and installation constraints;
- CSMS/OCPP, payment/authorization and data requirements;
- required declarations, certificates, reports and destination approvals;
- FAT, pilot and SAT witness/acceptance requirements;
- change-control, spare-parts and warranty responsibility expectations.
Use the same input pack for every supplier. It is the fastest way to expose unequal quotations before price becomes the deciding variable.
Frequently asked questions
How do I know whether an EV charger supplier is a real factory?
Verify the contractual entity, exact product evidence, production traceability and operational acceptance plan. A legal entity or factory visit is useful evidence, but neither alone proves that the quoted DC charger can be repeatedly built and accepted for your project.
Does ISO 9001 prove a DC charger is certified?
No. ISO 9001 relates to a quality-management system. It can be a useful process-audit input, but it does not prove an exact charger model’s compliance, connector configuration or destination-market approval.
Does an OCPP certificate guarantee the charger works with my backend?
No. Verify the official certificate/product identity and then run the actual CSMS, authorization, transaction, alarm and recovery test for the project configuration.
What is the difference between FAT and SAT for a DC charger?
FAT tests the agreed build before shipment in a controlled setting. SAT confirms the installed system at the actual site. Both need defined test cases, unit identity, recorded results, exceptions and acceptance responsibility.
Should I choose a supplier only by price and rated kW?
No. First match legal responsibility, exact configuration, document scope, production/change control and acceptance evidence. Price becomes comparable only after the quotations describe the same technical and contractual boundary.
Related guides
- Commercial EV charger buyer guide
- DC fast charger station engineering guide
- HPC vs DC charging
- Fleet EV charging
- GB/T EV charger guide
Sources
- European Commission: manufacturer responsibilities for CE marking
- Open Charge Alliance: OCPP certificate verification
- Open Charge Alliance: certification programme
- ISO 9001 explained
- UL Product iQ
- NIST Handbook 44
Technical review: Marvin. This guide is procurement guidance, not a substitute for destination-market legal review, local electrical engineering, vehicle OEM requirements or a project-specific conformity assessment.