Electronics supplier verification in China: what to check before an order
Editorial illustration
GURI Journal · Published 31 October 2026
A supplier can be a real business and still be a poor fit for a particular electronics project. It may sell the product without controlling its firmware, assemble a platform designed elsewhere, or depend on a component that is about to change. Verifying the company is only the beginning of understanding the proposed supply chain.
GURI treats verification as a decision process. The useful outcome is a documented basis for the next step, with unresolved questions still visible. A broad statement that a supplier is reliable says little unless it identifies what was checked, when and for which product.
Establish who is selling and who is communicating
Obtain the seller's legal identity and registration details, then compare them with the proposed contract and invoice. A website brand may differ from the legal company name. The difference needs an explanation and supporting evidence, rather than an immediate assumption either way.
Confirm that the contact represents the business through an independently established channel. Clarify who can approve commercial terms and who can authorize technical changes. A sales representative passing on an engineer's answer is not necessarily authorized to change the specification.
If payment instructions change, verify them through a previously trusted contact. The FBI's guidance on business email compromise explains why apparently familiar correspondence can be used to redirect payments. A reply in the same questionable email thread is not an independent check.
Map the work behind the finished device
Ask who designs the board, sources components, loads firmware, assembles the housing, tests the product and handles support. A trading company may coordinate these activities effectively, while an assembly factory may depend on external design expertise. Evaluate the arrangement against your project requirements.
Identify the actual production location and significant subcontracted activities. A factory visit should have a product-specific purpose. Seeing a working line does not establish that your order will use that line or that the necessary test process is available.
Where access is limited, record the limitation. Photographs, video and documents can help narrow questions, but they do not provide the same evidence as observing a defined operation on site.
Check control of hardware revisions
The commercial model name may remain unchanged while the memory, controller, radio module or battery changes. Ask how the supplier identifies the approved configuration and traces it to production batches.
Agree which substitutions require your approval and what information accompanies a proposed change. The phrase “equivalent component” leaves important questions unanswered: compatibility, support, performance and the relevance of existing technical evidence.
You do not necessarily need unrestricted access to every internal manufacturing record. You do need a workable way to identify affected units if a problem emerges. Decide what information will be available to the buyer and how it can be obtained.
Investigate software ownership and support
Find out who can correct a firmware defect and who maintains any required application or cloud service. A seller's willingness to promise support is different from its ability to deliver it.
Clarify supported environments, regional dependencies, accounts, subscriptions and the boundary between a correction and a paid feature change. Use an agreed test environment for demonstrations. Real customer data is unnecessary for checking ordinary product functions.
For a customized project, establish what deliverables you receive and what remains dependent on the supplier. The right arrangement depends on the project, but the dependency should be a conscious decision.
Connect technical evidence to the proposed product
Review complete documents, including relevant attachments, and compare model, manufacturer and configuration. Evidence for another product sharing the same housing is not automatically applicable.
Determine the requirements of the intended market with a competent specialist. A list of logos in a catalogue does not resolve product compliance, and a supplier visit is not a substitute for specialist testing.
Intertek describes component checks before production and inspections at later stages. The practical lesson is to choose work that answers a specific question. An assessment of manufacturing capability and an inspection of a finished shipment are different assignments.
Use a defined trial to test the working relationship
Give shortlisted suppliers the same technical request and ask them to identify deviations. Compare the clarity of their answers, their handling of revisions and their ability to reproduce an issue.
For example, if sales promises an interface that engineering says requires a different board, resolve the configuration before comparing prices. The discrepancy may be manageable; ignoring it is what makes the quotation misleading.
Record each conclusion as supported, inconsistent or unresolved, with its evidence and date. A successful sample or small order provides useful information within its scope. It does not prove that every future volume and version will perform equally well. Revisit the relevant checks when the product, production site or participants change.