Sourcing & Compliance

Factory Audit China: Two-Day Agenda for AI Wearables

Engineers at a development bench in the factory
Documentation is produced here, per model and hardware revision — not per marketing page. Reference photography from our production line or product set.
TITLE: Factory Audit China: Two-Day Agenda for AI Wearables DESC: A practical two-day factory audit agenda for AI wearables — what to request, in what order, and why video calls cannot verify QC gates, material traceability or test report authenticity. KEYWORDS: factory audit china, audit agenda, AI wearable supplier, QC evidence, compliance verification TAGS: sourcing, compliance, audit, quality control, wearables Q: What should I see on day one of a factory audit for AI wearables? A: Day one focuses on documentation integrity and process visibility: bill of materials with supplier tiering, firmware version logs, calibration records for test fixtures, and live access to the IQC and IPQC stations. Video calls cannot show material lot traceability or real-time defect tagging. Q: How do I confirm compliance claims without trusting a PDF? A: Ask to view original test reports on lab letterhead, cross-check serial numbers against device firmware versions, and request a live demo of the FQC station running AQL 2.5 sampling on your current build. The CE RED document checklist lists required clauses per test standard. Q: Why does my distributor reject samples even when the supplier says “all tests passed”? A: Because pass/fail is meaningless without context: sample rejection often traces to uncontrolled variables — inconsistent firmware signing, uncalibrated battery discharge testers, or missing EN 1811 nickel release data for rings. Review the how to vet a supplier guide before signing. Q: What question do most suppliers avoid when asked about audit readiness? A: “Can you open the firmware build log for the last three production batches and show me where the cryptographic signature was applied?” If they cannot, firmware integrity — and thus CE RED compliance — remains unverifiable.

Day One: Documentation and Process Walkthrough

Begin at the engineering office with full access to the BOM, firmware revision history, and calibration logs for all test equipment. Request printed copies of the latest CE RED document checklist signed and dated by the lab. Do not accept screenshots or watermarked PDFs. Observe IQC receiving raw materials: ask to scan a PCB lot number and trace it to its incoming inspection record, then to the firmware version burned onto that batch. A video call cannot show whether solder paste lot numbers are logged beside reflow oven temperature profiles.

Day Two: Live QC Gate Observation

Start at IPQC: watch operators use calibrated torque screwdrivers and multimeters on live assembly lines. Then move to FQC, where devices undergo functional testing against defined pass thresholds — not just “lights on”. Finally, witness OQC sampling using AQL 2.5 major / 4.0 minor, with rejected units physically tagged and logged. This is where video fails: remote observers cannot verify whether the same tester handles both pass and fail decisions, or whether the FQC station runs the exact firmware version shipped with your order. Cross-reference the how we build and test page for WingPhoenix’s internal gate definitions.

What a Video Call Cannot Prove

A video walkthrough shows surfaces, not systems. It cannot verify firmware signing keys, material certifications held by Tier 2 suppliers, or whether UN38.3 test summaries match the actual battery cells installed. It cannot confirm if the same technician who calibrates the RF test chamber also signs off on final EMC reports. It cannot reveal whether EN 1811 nickel release testing was performed on the finished ring housing — not just the raw alloy sample. For skin-contact items, this gap invalidates compliance. See the health smartwatch product page for how we apply EN 1811 across variants.

Compliance Evidence You Must See In Person

Ask for physical access to the document archive: CE RED reports must include test photos showing the exact antenna layout used, FCC Part 15 reports must list the precise modulation scheme and power output measured, and RoHS 3 declarations must reference lab-accredited screening of each plastic compound — not just “compliant material”. Battery SDS sheets must carry the watt-hour rating printed on every unit, as stated in our MOQ, sampling and lead times policy. No digital copy substitutes for seeing the ink stamp on the original UN38.3 summary.

The Hard Limit: What This Audit Does Not Cover

This two-day agenda does not assess algorithmic bias, model drift over time, or long-term firmware update support. It does not verify cloud API uptime, data residency claims or third-party SDK licensing status. It does not cover GMS certification — Google Mobile Services are not licensed by default, and no WingPhoenix device ships with pre-installed Play Store access unless explicitly quoted under OEM/ODM services. Nor does it evaluate health metric accuracy beyond wellness guidance: the product catalogue states clearly that health metrics are wellness guidance, never diagnosis. If a supplier offers “FDA-cleared sleep apnoea detection”, walk away — that claim falls outside our published scope and violates EU and UK regulatory boundaries.

Procurement Decision Checklist

Checkpoint Evidence Required Why It Matters
Firmware Build Log Timestamped, signed log showing cryptographic hash per build Verifies firmware integrity for CE RED and cybersecurity claims
Battery UN38.3 + SDS Original lab report + SDS with WH rating printed on unit Mandatory for air freight; mismatch voids DDP liability
EN 1811 Nickel Release Report on finished ring housing, not raw alloy Required for all skin-contact items; packaging age grading triggers enforcement
Toy Safety Scope Lab booking confirmation matching age grade on packaging EN 71-1/-2/-3 applies only if packaging declares “3+” or similar
AQL Sampling Records Physical FQC/OQC logs with operator signatures and timestamps Proves statistical sampling was executed, not assumed
Calibration Certificates Accredited lab stamps on torque drivers, multimeters, RF chambers Uncalibrated tools invalidate all test results
Material Traceability Lot numbers from PCB to firmware to final packaging box Enables recall precision and root-cause analysis
  1. Review the OEM versus ODM comparison to align expectations on firmware control and liability
  2. Confirm MOQ and lead time alignment using the MOQ, sampling and lead times page
  3. Book lab testing scopes early — especially for service robots requiring laser classification and risk assessment
  4. Verify importer responsibilities: WEEE, BattG, DEEE/Triman and EORI/VAT duties sit with the importer, not WingPhoenix
  5. Use the buyer resources hub to download editable checklists and policy summaries

Audits protect procurement integrity — not just compliance. If your next supplier refuses live access to firmware logs or calibrated test equipment, pause the engagement. To begin planning your own two-day agenda, send us the specification and reference your target audit window. We will supply the factory map, gate schedule and document index 10 working days in advance.

Questions buyers ask

What should I see on day one of a factory audit for AI wearables?

Day one focuses on documentation integrity and process visibility: bill of materials with supplier tiering, firmware version logs, calibration records for test fixtures, and live access to the IQC and IPQC stations. Video calls cannot show material lot traceability or real-time defect tagging.

How do I confirm compliance claims without trusting a PDF?

Ask to view original test reports on lab letterhead, cross-check serial numbers against device firmware versions, and request a live demo of the FQC station running AQL 2.5 sampling on your current build. The <a href="https://wingphoenixai.com/resources/ce-red-compliance-smart-watches/">CE RED document checklist</a> lists required clauses per test standard.

Why does my distributor reject samples even when the supplier says “all tests passed”?

Because pass/fail is meaningless without context: sample rejection often traces to uncontrolled variables — inconsistent firmware signing, uncalibrated battery discharge testers, or missing EN 1811 nickel release data for rings. Review the <a href="https://wingphoenixai.com/resources/how-to-choose-ai-wearable-supplier/">how to vet a supplier</a> guide before signing.

What question do most suppliers avoid when asked about audit readiness?

“Can you open the firmware build log for the last three production batches and show me where the cryptographic signature was applied?” If they cannot, firmware integrity — and thus CE RED compliance — remains unverifiable.

Related: more on sourcing & compliance · buyer guides · customisation tiers