A charger supplier is chosen on evidence, not impressions: the documents that prove capability, the samples that demonstrate quality and the track record that predicts reorder behavior. The evaluation runs the same standard against every candidate, and the record supports the decision. This guide covers the documents that prove capability, sample quality as a signal, factory audit essentials, the red flags that end the shortlist, and testing samples before volume.
Key takeaways
- The evaluation is an evidence test: documents, samples and track record.
- Sample quality is the physical signal behind the paper claims.
- The red flags are visible before the order, if the evaluation looks for them.
Content updated: August 2026 — confirm current standards editions and supplier details before ordering.
Scope note: This guide is general sourcing guidance; supplier and document details are confirmed per candidate.
Documents That Prove Capability
The document set is the supplier's capability statement: model-specific certificates and test reports, the quality system description and batch record samples. Each item is checked against the configuration the program needs.
The review follows the model-match rule: the certificate must name the exact configuration and standard edition, the report must cover the same model and the batch records must exist for actual shipments. Evidence that names a similar product is context, not proof.
The document review also checks dates. Standards are revised and certificates are refreshed, so the evaluation records when each item was reviewed and which edition it cites. A dated evidence file is the audit-ready record.
The document review also checks the currency of the batch records. A certificate describes a design; the batch records describe a shipment, and both must be current for the order in question. The evaluation connects the two.
The document set is also the program's baseline. The same evidence that qualifies the supplier at the start is applied at each reorder, so the relationship stays on the standard rather than drifting. The record is the baseline.
Sample Quality as a Signal
The sample is the physical signal behind the paper claims. A sample that matches its spec, behaves with the real device and ships with its documents is a candidate with substance; one that drifts from the spec is a warning.
The sample test follows a plan written in advance:
- Functional check against the profile table.
- Real-device test at the duty cycle.
- Thermal check in the expected environment.
- Document match for the sample configuration.
The sample plan is the same for every candidate, and the results are recorded. The sample is the supplier's product in miniature.
The sample also reveals the supplier's documentation habit. A sample that arrives with its certificate and report, naming the configuration, is a supplier running the process; one that arrives without them is a supplier running a scramble.
The sample comparison is the fair test: the same devices, the same conditions and the same plan for every candidate. The comparison is a decision, not a first impression.
Factory Audit Essentials
The audit verifies what the documents describe:
- The production flow matches the described stages.
- The test equipment exists, is calibrated and is used.
- The batch records match the shipments.
- The warehouse keeps configurations segregated.
The audit also includes the failure story: where failed units are kept, how they are reviewed and what happens after correction. The failure process reveals the system's real shape.
The audit findings are written up and filed with the documents. A visit without a written finding is a tour; the finding is what the decision reads.
The audit also covers the quality system's failure side. How are rejected batches handled, how are field complaints reviewed and how do corrections feed back? The failure story reveals the real system.
The audit is matched to the program's risk. A stock purchase warrants a lighter check; a branded or volume program warrants the full visit. The depth follows the risk.
Red Flags That End the Shortlist
Some signals remove a candidate before the evaluation completes:
| Signal | What it means |
|---|---|
| Documents never arrive | The evidence does not exist |
| Certificates name different models | The configuration is not covered |
| Samples drift from the spec | The process is not controlled |
| Batch records are unavailable | Traceability is not running |
| Technical questions get marketing answers | The depth is not there |
The signals are the same for every candidate, and the same standard makes the shortlist fair. A candidate that fails a signal has failed the evidence test.
The signals are also the communication test. A supplier that answers the technical questions with specifics has engineering depth; one that answers with adjectives has a sales story. The interview is part of the evaluation.
The red-flag review is written down, not improvised. Each candidate's performance against the signals is recorded, and the record is what the shortlist decision reads. The signals are the filter.
Testing Samples Before Volume
The sample test is also the volume gate. Before the first volume order, the approved sample becomes the reference, and the production batch is checked against it:
- Compare the batch units with the golden sample.
- Confirm the documents name the configuration.
- Check the batch records for the shipment.
- Gate the volume on the evidence.
The gate is the same discipline as the rest of the cluster: the sample is the reference, and the reorder carries its own evidence.
The volume gate also includes the commercial check. The MOQ, the lead time and the terms are confirmed against the configuration, and the order file records them. The commercial layer is part of the gate.
The supplier evaluation closes with the same discipline as the rest of the cluster: the documents are verified, the sample is tested with a written plan, the factory is audited and the volume is gated on evidence. The supplier is chosen the same way every time — against the standard, with the record attached.
For the sourcing team starting out, the practical first step is the evidence request written down: the certificates, the reports, the batch records and the sample plan, sent to every candidate identically. The responses, the samples and the audit findings then fall into place, and the comparison is a decision rather than a first impression. The supplier evaluation is a process, and every program benefits from running it the same way — because a supplier chosen on evidence is a supplier that keeps delivering evidence, order after order.
The same evidence standard also protects the program when the market or the product changes. A new market re-checks the certificate coverage, a new configuration re-tests the sample and a new volume re-gates the batch records, all against the same baseline. The evaluation is not a one-time event at the start of the relationship; it is the standing discipline that keeps every reorder as defensible as the first — and that is what turns a supplier shortlist into a supply chain.
The practical outcome of the discipline is visible in the order file: the evidence request, the sample results, the audit findings and the batch records all live in one versioned record, and every decision reads from it. When the next review asks why this supplier and not another, the file answers with documents instead of impressions. A supplier evaluation built on evidence is the quiet difference between a relationship that works and one that is rediscovered — and the file is what makes it work, order after order.
A verification note for sourcing teams: The first document is the certificate with the model match, and the first hardware check is the sample with the real device. The evaluation is an evidence test, and the record is the deliverable.
Supplier evaluation starts with the WECENT homepage for the company and product background, then uses the Factory page for the manufacturing and quality context and the Quality Control page for the production test flow and records. To run the evaluation for a candidate, request the evidence set from WECENT's project engineering team — the review returns the certificates, test flow and batch record approach for the program.
Frequently Asked Questions
What is the first document to request from a supplier?
The certificate for the exact configuration, with the test report behind it. The model-match rule — documents naming the precise SKU and standard edition — is the starting evidence.
How do I test a sample?
With a plan written in advance: functional check, real-device test, thermal check and document match. The same plan runs against every candidate.
Is a factory visit required?
For a volume or branded program, yes, or a detailed remote audit. The production flow and test equipment are verified in practice.
What signal should end the shortlist?
Documents that never arrive, certificates naming different models or samples that drift from the spec. Those are evidence failures, not fixable gaps.
How do I gate the volume order?
Compare the production batch with the golden sample, confirm the documents and check the batch records. The volume gate is the sample gate at scale.