AI Wearables

EU Declaration of Conformity for Wearables: What Importers Require

9 Oct 20261024 wordsWingPhoenix AI factory team

Smartwatch production line inside the factory — Line view: where burn-in and functional test sit in the build sequence. Reference photography from our production line or product set.

TITLE: EU Declaration of Conformity for Wearables: What Importers Require DESC: A line-by-line breakdown of the mandatory content in a valid EU DoC — and why incomplete versions trigger customs delays or market withdrawal. KEYWORDS: eu declaration of conformity wearable, doc contents, responsible person, harmonised standards TAGS: compliance, wearables, CE marking, importer duty, RED directive Q: Why do some Declarations of Conformity get rejected at EU borders even when testing reports are present? A: Because the DoC is a standalone legal instrument — not a summary of test results. Missing or misstated elements invalidate the entire document regardless of lab data. Q: Who must be named as the responsible person on the DoC for a wearable built in Shenzhen? A: The EU-based importer or authorised representative, not WingPhoenix AI. The manufacturer’s role is limited to supplying complete technical documentation and supporting evidence per revision.

A Declaration of Conformity (DoC) is not a formality — it is the importer’s primary legal affirmation that a wearable meets applicable EU requirements. For devices like the health smartwatch, the GPS sport watch, or the AI health ring, an incomplete DoC creates liability for the importer and blocks placement on the market. Unlike test reports or certificates, the DoC must reflect the exact hardware revision, list every applicable directive and harmonised standard by full EN number, and name only the legally responsible party within the EU. This applies equally to products in the AI wearables line and those under the broader Health & Wellness line.

What Must Appear — and Where It Fails Most Often

The DoC must contain seven non-negotiable elements, each traceable to Regulation (EU) 2019/1020. First, the full product name and model identifier — not a marketing name, but the version-controlled designation used in the technical file. Second, the manufacturer’s name and address — WingPhoenix AI’s Shenzhen address only, never a trading company or forwarder. Third, the EU importer’s name and registered address — this cannot be left blank or replaced with “to be appointed”. Fourth, the list of directives applied: RED (2014/53/EU), EMC (2014/30/EU), LVD (2014/35/EU), RoHS (2011/65/EU), and, where relevant, the Toy Safety Directive (2009/48/EC) for age-graded items like certain companion models. Fifth, the harmonised standards cited must match exactly those tested and reported — e.g., EN 300 328 v2.2.2, not “EN 300 328” alone. Sixth, a statement of sole responsibility by the signatory. Seventh, date and signature — handwritten or qualified electronic, never typed.

The Role of Harmonised Standards

Harmonised standards define the presumption of conformity. For wearables, this includes EN 301 489-1/-17 for EMC, EN 62368-1 for safety, and EN 1811 for nickel release in skin-contact items such as the smart ring with charging case. WingPhoenix AI supplies test summaries against these standards per hardware revision, but the DoC must cite them explicitly — including version numbers and publication dates. A reference to “applicable parts of EN 62368-1” is insufficient. The standard must be listed in full, and its scope must align with the device’s function, power source and user interface. This is verified during the factory’s OQC gate, not after shipment.

Responsible Person: Not the Manufacturer

WingPhoenix AI is the manufacturer — not the responsible person under EU law. That role belongs exclusively to the EU-based importer or their appointed authorised representative. The DoC must carry the importer’s legal name, registered office and contact details. WingPhoenix AI supports this process by providing complete technical documentation, including test reports, risk assessments and lab summaries, but does not sign or issue the DoC on behalf of the importer. This distinction is critical for devices covered by multiple directives, such as service robots requiring both EMC and low-voltage assessment, or AI glasses where laser classification (IEC 60825-1) must be declared separately. The importer remains fully liable for accuracy and retention of the DoC for ten years.

Where Documentation Alignment Breaks Down

Discrepancies most commonly arise between the DoC, the test report and the actual unit shipped. Examples include citing EN 300 328 without specifying the version used in testing, listing a battery standard (e.g., UN38.3) without including the watt-hour rating printed on the unit, or omitting EN 1811 for rings or watches despite direct skin contact. These omissions invalidate the DoC even if all underlying tests passed. WingPhoenix AI books certification scopes per hardware revision with accredited laboratories — meaning each new PCB layout, antenna design or housing material requires updated test evidence and a revised DoC. This process is detailed in the CE RED document checklist.

Marketing name only (e.g., “VitaRing”) or no revisionForwarder address or incomplete city/postcode“To be confirmed” or WingPhoenix AI’s EU office (none exists)Omitting RoHS or listing “EMC Directive” without 2014/30/EUVague references (“EN 301 489 series”) or outdated versionsTyped name or date after shipment beginsMissing WH rating or mismatched between DoC and physical unit

Element	Required Content	Common Error
Product Identification	Exact model name + hardware revision (e.g., R1-RING-V3.2)
Manufacturer Address	WingPhoenix AI, Shenzhen, China — full registered address
EU Responsible Person	Importer’s full legal name and EU-registered address
Directives Cited	RED, EMC, LVD, RoHS — each with full year/directive number
Standards Listed	Full EN numbers with version (e.g., EN 301 489-17 v3.2.1)
Signature & Date	Handwritten or QES signature + dated before first placing on market
Battery Declaration	UN38.3 + SDS + watt-hour value matching label on unit

Confirm the EU importer is named — not WingPhoenix AI — and that their address is legally registered.
Verify every harmonised standard in the DoC matches the version tested and reported in the lab summary.
Cross-check battery watt-hour values between the DoC, SDS, UN38.3 summary and the printed label on the unit.
Ensure the model identifier in the DoC matches the firmware version, PCB revision and packaging SKU.
Retain signed copies for ten years — the importer, not WingPhoenix AI, holds this obligation.

WingPhoenix AI provides all necessary technical documentation per hardware revision, including test summaries for EN 300 328, EN 62368-1 and EN 1811, as well as support for toy-grade assessments where age grading applies. To begin preparing your DoC, review the MOQ, sampling and lead times for your chosen model, then request the latest revision-specific documentation pack via your account manager. Do not proceed to customs clearance until the DoC has been validated against this checklist.

Questions buyers ask

Why do some Declarations of Conformity get rejected at EU borders even when testing reports are present?

Because the DoC is a standalone legal instrument — not a summary of test results. Missing or misstated elements invalidate the entire document regardless of lab data.

Who must be named as the responsible person on the DoC for a wearable built in Shenzhen?

The EU-based importer or authorised representative, not WingPhoenix AI. The manufacturer’s role is limited to supplying complete technical documentation and supporting evidence per revision.

Request a Quote Browse products