AI Hardware Suppliers: Six Questions That Separate a Factory From a Reseller
1. SMT Lines: Where Is the First Solder Joint Made?
If a supplier cannot describe their SMT line by placement speed, reflow profile range or stencil thickness tolerance, they do not own the line. WingPhoenix operates two dedicated SMT lines in Shenzhen, each calibrated for fine-pitch AI SoCs and sensor arrays. We publish how we build and test, including IPC-A-610 Class 2 acceptance criteria and real-time SPI data logging. A reseller may quote “in-house SMT”, but cannot show you the line’s daily first-article report or explain how they adjust for thermal mass variance between AI glasses and smart rings.
2. QC Lab: What Does “AQL 2.5 Major” Actually Cover?
AQL is meaningless without defined defect categories and sampling plans per gate. Our QC lab performs IQC on incoming PCBAs, IPQC at firmware burn-in and FQC on final assembly — all documented per revision. The factory page details how we define “major” for AI wearables: misaligned IMU mounting, uncalibrated mic gain, or missing Bluetooth SIG qualification ID. A reseller may say “we test everything”, but cannot produce the OQC checklist used on your last AI device line order — because they never ran it.
3. Business Scope: What Is Legally Permitted on the Packaging?
Business scope is not marketing copy — it is the registered activity on the company licence. WingPhoenix’s scope covers R&D, PCB assembly, firmware integration and EMC testing. It does not include medical device manufacturing, glucose monitoring or emergency call routing. This defines what claims can appear on packaging — and which tests must be booked. For example, AI learning devices carry EN 71-1/-2/-3 only if the age grading on the box matches the lab’s test scope. A reseller often extends scope verbally — but cannot show you the licence excerpt matching your product category.
4. NDA Enforcement: Who Signs, and Where Is the Breach Tracked?
An NDA signed by a sales agent means nothing. At WingPhoenix, NDAs are signed by the General Manager and the Head of Firmware Engineering — and cover firmware binaries, sensor calibration logs and BOM cost structure. Breach clauses reference Shenzhen courts and specify liquidated damages tied to development cost recovery. We enforce this through version-controlled access logs in our firmware repository — visible during a technical audit. Reviewing the OEM/ODM services page shows how NDA terms bind every stage from schematic review to white-label app handover.
5. Audit Readiness: Can You Walk the Line Tomorrow?
Any supplier can pass a pre-announced audit. WingPhoenix publishes its how to vet a supplier guide to help buyers distinguish preparation from capability. We allow unannounced production line walks — provided importers share their EORI/VAT number and sign our site access agreement. If a supplier says “audits require three months’ notice”, they are outsourcing assembly or using shared lab capacity. That delay is not logistics — it is dependency.
6. What This Process Cannot Do
This verification process cannot confirm regulatory approval before testing is complete. No CE RED or UKCA certificate exists until the accredited lab issues it for the exact hardware revision — including PCB layout, antenna placement and firmware build. WingPhoenix books these tests per revision, but cannot issue a certificate retroactively or transfer one from another client’s build. If a supplier offers “CE-ready firmware” or “pre-certified modules”, they are either misrepresenting the directive’s requirement for system-level testing — or relying on a certificate that does not cover your configuration. Importers should refuse any claim that bypasses revision-specific test booking with an accredited body. Full policy is outlined in our OEM versus ODM resource and referenced in every product catalogue entry.
| Decision Point | Factory Evidence | Reseller Red Flag |
|---|---|---|
| SMT Ownership | Line uptime reports, stencil vendor contracts, reflow profile logs per batch | “We partner with top-tier SMT houses” — no line naming or shift schedule |
| QC Lab Scope | OQC checklist signed by lab manager, AQL sampling plan per model family | Generic “100% functional test” — no defect taxonomy or gate definitions |
| Business Scope Match | Company licence excerpt showing R&D, assembly and EMC testing | Scope lists “electronics trading” or “import/export agency” |
| NDA Signatory | Signature of engineering and operations leadership, breach clause with jurisdiction | Signed by sales coordinator, no technical enforcement mechanism |
| Audit Access | Published walk-through protocol, unannounced access permitted under agreement | “All audits scheduled via procurement” — no site access policy published |
| Certification Booking | Lab booking confirmation with revision ID, test standard and scope | “CE compliant per module datasheet” — no system-level test evidence |
- Review the how we build and test page for SMT and QC lab documentation standards
- Compare MOQs and lead times against your category in the AI device line and AI learning devices
- Verify that firmware white-label requests meet the 2,000-unit threshold in our OEM/ODM services policy
- Check whether your product falls under toy, wearable or service robot scope using our how to vet a supplier guide
- Confirm importer duties (WEEE, BattG, DEEE/Triman) are assigned correctly — none are covered by WingPhoenix per our the journal policy notes
Before sending your specification, download our buyer resources pack — it includes the full factory policy, test scope templates and a revision-tracking checklist. Then send us the specification with your hardware revision ID, target certification standards and intended distribution channel. We will respond within 48 hours with the lab booking confirmation, SMT line assignment and QC gate plan — all tied to your build.
Questions buyers ask
How do I confirm an AI hardware supplier is actually a factory — not a reseller with a glossy website?
Ask six specific questions about physical infrastructure, test scope, legal boundaries and revision-level documentation — then check whether answers align with published policy and verifiable evidence.
What does finance need to know before approving a deposit on a new AI hardware supplier?
Whether MOQs, lead times and warranty terms are fixed per model type, and whether CE, FCC and battery certifications are booked per hardware revision — not assumed or shared across SKUs.
Why did our distributor reject the last AI ring sample after third-party testing?
Because the supplier claimed EN 1811 nickel release compliance but shipped units without skin-contact build validation — a gap only exposed when reviewing the test scope against the actual build.
What question do most AI hardware suppliers avoid — and why does it matter?
“Which accredited laboratory is testing this exact hardware revision for CE RED and EN 62368-1?” Because no certificate exists until that test is booked, paid for and completed — and a reseller cannot book it in your name.
Related: more on ai smart hardware · buyer guides · customisation tiers