Before approving a pilot with a China AI hardware manufacturer, verify one connected evidence chain: the registered company, the site doing the work, the people controlling the process, the exact sample revision, and the acceptance record you will use for the pilot. A supplier profile, certificate, video tour, or polished sample can support the decision, but none of them proves the whole chain by itself.
Start with the Chinese legal name and Unified Social Credit Code. Then connect that entity to the quotation, payment beneficiary, factory address, product process, and sample documentation. If a link is unclear, label it as an open item before money, tooling, firmware, or brand assets move.
The five-file check
You do not need a huge document room for the first screen. Ask for five files and test whether they agree.
| File | What to match | Decision signal |
|---|---|---|
| Business licence | Chinese legal name, code, registered address, status, business scope | The company exists and the record is current; this does not yet prove product capability |
| Quotation | Seller entity, product baseline, commercial scope, site, exclusions | You know who is contracting and what is actually included |
| Payment instructions | Beneficiary name, bank location, currency, change procedure | Any mismatch has a documented explanation and independent confirmation |
| Process map | Design, purchasing, assembly, programming, testing, packing, outsourced steps | The supplier's role and each external handoff are visible |
| Sample pack | BOM or configuration revision, firmware state, drawings, test results, deviations | The approved sample can become a controlled pilot baseline |
China's National Enterprise Credit Information Publicity System provides public registration information. An English-language Shanghai government FAQ explains that the national system can include the company name, Unified Social Credit Code, directors and shareholders, establishment date, registered address, and business scope. Search with the exact Chinese legal name or code, record the date, and save the result you relied on.
Separate identity, role, and capability
These are three different questions:
- Identity: Which legal entity is offering the project and receiving payment?
- Role: Is that entity the manufacturer, a solution integrator, a trading company, an affiliate, or a combination?
- Capability: Can the proposed team and production route deliver your specific product baseline?
A trading company is not automatically unsuitable, and a registered manufacturing scope is not proof that every quoted process happens at one site. What matters is clarity. Ask the supplier to mark each workstream as in-house, affiliate, or external: industrial design, electronics, firmware, tooling, PCB assembly, final assembly, programming, test, packaging, and after-sales handling.
Quick test: choose one critical step and ask for the site, process owner, current instruction, recent record, and acceptance result. If the answer jumps between entities or facilities, map the handoff before continuing.
Make the evidence product-specific
Generic capability decks are useful for orientation. They do not replace evidence tied to your product. For an AI recording device or wearable, the relevant path may include microphones, antennas, batteries, charging, memory, firmware programming, acoustic tests, radio tests, app pairing, serialisation, and packaging. Your own design will determine which controls matter.
Request one recent, redacted example from a similar process where confidentiality permits. Look for consistency across the instruction, equipment, operator or station, limit, result, unit or lot ID, reviewer, and disposition. You are testing whether the system can connect a requirement to an outcome, not collecting a large folder of unrelated certificates.
Freeze a sample baseline before the pilot
“Sample approved” is too vague. A useful approval identifies what was approved and what remains open. Create a one-page sample baseline with:
- model and physical sample IDs;
- hardware, enclosure, PCB, firmware, and app versions where applicable;
- critical components and approved alternatives;
- drawings, cosmetic standard, labels, accessories, and packaging revision;
- test methods, results, and any approved deviations;
- open actions, owners, due dates, and the rule for closing them;
- who can approve a change before and during the pilot.
Photographs help, but do not let them become the only specification. A photograph cannot define an electrical limit, firmware build, acoustic test, material grade, or acceptable cosmetic range.
Write pilot acceptance criteria before the build
The pilot should answer specific questions. It is not simply a smaller purchase order. Agree on the build objective, input revision, process route, quantity, data to capture, decision rules, and disposition of failed or reworked units.
| Acceptance area | Write this before the pilot | Evidence after the build |
|---|---|---|
| Configuration | Exact released hardware, firmware, materials, labels and packaging | Build record and serial or lot mapping |
| Critical functions | Method, setup, limits, sample rule and owner | Results linked to each tested unit |
| Workmanship and cosmetics | Defect definitions, viewing conditions and boundary samples | Inspection record and defect images |
| Yield and rework | What counts as first-pass, rework, retest and scrap | Unit-level failure and disposition log |
| Change control | No-change fields, notification threshold and approval owner | Deviation list and signed approvals |
| Release decision | Accept, conditionally accept, rebuild or stop criteria | Decision record with unresolved risk |
A small pilot may be useful for learning, but it does not establish a statistically strong defect rate by itself. Keep the claim proportional to the sample and test method. If your team needs an acceptance-sampling plan, reliability demonstration, compliance evidence, privacy review, or security assessment, involve the appropriate quality, engineering, regulatory, legal, and security owners.
Red flags that need a pause, not an argument
- The Chinese legal name, quotation entity, payment beneficiary, and factory host cannot be connected.
- The supplier will show equipment but not a product-specific process or recent record.
- Critical work is outsourced, but the provider, acceptance step, or change rule is unclear.
- The sample has no controlled revision, or later samples change without a deviation record.
- Pilot acceptance criteria are discussed only after units fail.
- A certificate is presented without checking its site, scope, validity, and relevance to the quoted work.
- Future hiring, equipment, tooling, or certification is described as current capability.
One red flag does not always end the project. It changes the next commitment. Ask for a dated correction, independent verification, a narrower scope, another sample, or a controlled pilot before increasing exposure.
Use a release ladder
Release information and money in stages. A simple ladder is: identity screen, capability screen, sample baseline, pilot approval, pilot review, and only then a larger commitment. Define what evidence unlocks each step. This keeps a good sales conversation from outrunning the technical and commercial facts.
NIST describes supplier due diligence as researching pertinent information so acquisition decisions can be informed. ISO guidance likewise emphasizes defined criteria, monitoring external providers, verifying requirements, and considering whether a certification's scope covers the goods or services being purchased. Neither source turns one check into permanent approval. Re-verify when the entity, site, process, component, firmware, tooling, or commercial arrangement changes.
Official references
- National Enterprise Credit Information Publicity System
- Shanghai government FAQ on China's national enterprise registration database
- ISO — How can you have confidence that your supplier meets ISO 9001?
- ISO 9001 Auditing Practices Group — External providers
- NIST SP 1326 — C-SCRM Due Diligence Assessment Quick-Start Guide
Your next step
Put the five files in one folder and highlight every name, address, site, revision, and account that does not match. Then send the supplier a short discrepancy list before scheduling the pilot. If the evidence chain closes, use the AI hardware supplier RFQ checklist to tighten the request, the manufacturer vs solution provider guide to clarify roles, and the manufacturer scorecard for the wider decision. Browse the AI Hardware Customization hub for the full sourcing sequence.
Planning an AI recording hardware project? WhatsApp Recolx at +85251718843 or email sale@recolx.ai.
