Smart Watch Export: SAR, Battery and Health Claims

Let us put the conclusion first: a watch weighs only a few dozen grams, but it does not need fewer certifications than a phone. What actually stalls a project is not "there are too many items to do", but three wrong judgements — SAR (worn against the body), the battery (one line for transport, another for safety), and health claims (the medical device boundary). Get these three wrong and it is not a matter of adding one report; the whole plan has to be rebuilt and the delivery schedule rearranged.

Phones have been refined for more than a decade: reference designs, supply chains and certification templates are all mature, and much can be copied across. A watch is different: small batches, many models, fast iteration, the antenna squeezed into the lugs, the battery packed into the case, the sensor against the skin, and charging that depends on a dock. Change the mechanical structure and the "representativeness" of the certification changes with it.

These three areas fail so often because they share one trait: they look safe to handle by default, while every default needs evidence behind it. Low Bluetooth power does not equal an automatic SAR exemption; a cell with a certificate does not equal a passed whole-unit battery safety assessment; wording such as "for health reference" does not equal the absence of a medical claim. The sections below take each one apart in the order risk → trigger → response.

Start with the summary table: three risks → triggers → responses

Why a watch is different: small object, no fewer routes

Take a smart watch apart and the parts are roughly these: main control chip, Bluetooth/WiFi module, lithium battery, display, heart-rate/SpO2 sensor, charging dock. The certification core is therefore four blocks — radio frequency, worn-body SAR, battery safety, sensor compliance.

The key is that three of those four are amplified by the fact that the device is worn close to the body. A phone sits on a desk or in a hand for much of the day, and SAR applies only during the short stretch when it is held to the ear on a call; a watch is strapped to the wrist 24 hours a day, so SAR turns from "one particular usage posture" into "the default state". A phone battery has a full structural volume inside the body, while a watch battery is pressed into the case and also sits against the skin. Health features on a phone can be dismissed with "for reference only", but once a watch adds a sensor, marketing wants to turn it into a selling point.

Two structural factors then stack on top. First, the charging dock, which gives a DC product an extra AC-powered branch. Second, multiple sizes and materials in one series: which model is submitted and how coverage is justified directly determines how much reuse is left for every market afterwards. For the overall breakdown of the product route, see smart watch certification solutions.

SAR: worn on the body, the limb calculation is the one that counts

A watch is not held to the head, so the head SAR logic does not apply; it is assessed in the limb (wrist) scenario. This single judgement decides whether what follows is "one technical justification" or "a full round of testing".

• United States: assessed under FCC KDB 447498, wrist-worn devices use the limb SAR limit of 1.6 W/kg (10g average). Bluetooth power is usually lower and there are cases where an exemption applies; versions with WiFi plus cellular require full SAR testing.
• European Union: EN 62209-2 covers the wrist-worn scenario, with a limb SAR limit of 2.0 W/kg (10g average). Under the CE-RED framework a notified body may ask for a SAR report.
• Korea: RRA has a separate SAR assessment requirement for wearable devices, and it uses 1g averaging, not 10g averaging. This point is often missed: 1g and 10g readings are not the same ruler, so an EU report value cannot be compared against the Korean limit.

On exemptions, the saying that circulates in the industry is "Bluetooth watches do not need SAR". The more accurate version: Bluetooth versions usually sit at an output power in the ≤10 mW order, and under the FCC and EU frameworks an exemption can be applied for, but a power calculation and technical justification have to be submitted. In other words, an exemption is a conclusion that has to be argued, not a premise that can be assumed. What gets sent back in projects is often not a badly performed test, but the inability to find that justification in the file.

The genuinely difficult case is the WiFi + cellular version. Space in a watch is small, antenna efficiency suffers by nature, and to win connection performance back the RF design is pushed towards the power ceiling; the cumulative assessment with several transmitters active at once is one of the tighter margins in this kind of project. Strap material, worn spacing and wrist posture all affect the result, so leaving room for rework before submitting samples is far less trouble than tightening the structure afterwards. For country-specific requirements see the FCC knowledge base and the CE-RED knowledge base, or go straight to the service process for the United States and the European Union.

Two battery lines: UN38.3 covers transport, IEC 62133 / UL 1642 cover safety

This is one of the more widely misunderstood points in watch projects. Many assume "one battery report is enough", when in fact these are two entirely different lines serving two entirely different scenarios, and missing either will stop the shipment at some stage.

The transport line. UN38.3 comes from Section 38.3 of the UN Recommendations on the Transport of Dangerous Goods, enforced by IATA and IMO, and its purpose is that lithium batteries do not catch fire, explode or leak in transit. It is not a national certification but a globally applicable transport requirement — by air or by sea, whichever market you ship to, it is required. The testing consists of the eight items T.1 to T.8 simulating transport environments, and the accompanying documents are the UN38.3 report + MSDS + transport conditions identification report.

A watch uses a single-cell battery pack, so 20 samples are prepared (10 initial + 10 after cycling). "After cycling" means cells that have completed 50 charge/discharge cycles, and this item often delays the schedule: if cycled samples are not started early, the laboratory can only wait. The test cycle is usually 2-3 weeks (including sample cycling time), and the report stays valid long-term, but changes to the battery design (materials, structure, capacity and so on) require retesting. For details see the complete UN38.3 explanation.

The common failures are concentrated as well: T.5 external short circuit is a relatively frequent item, where the temperature after the short circuit rises high enough to cause fire, generally related to separator quality or protection circuit design; leakage after T.2 temperature cycling is fairly common on small pouch cells and points to a sealing process issue; T.7 overcharge points to insufficient margin in the protection board design.

The safety line. IEC 62133 / UL 1642 cover the safety of the cell itself, plus the whole-unit charging protection circuit assessment and overcharge/over-discharge/short-circuit verification. A watch battery has small capacity, is sealed inside the case and sits against the skin, with little room for pressure relief or heat dissipation — this line is not something to sign off with "my cell supplier holds certificates". Freezing the cell, cycling samples, and running transport and safety tests in parallel is the more stable arrangement.

The charging dock and safety: the other half of whole-unit approval

The watch body runs on DC, but once the dock is plugged into a wall socket the nature changes. This single accessory decides whether whole-unit safety work "follows the unit" or "takes a separate route".

• Charging-only dock with no data transfer: tested for safety together with the unit as an accessory, with no separate RF certification needed.
• AC-powered dock: additional LVD / UL assessment and energy efficiency confirmation are needed. In the Chinese market the charging dock also involves CCC.
• EMC has to be measured in the plugged-in mode: radiated disturbance, conducted disturbance, electrostatic discharge and radiated immunity all have to cover the working state with the dock plugged in. Testing the battery-powered mode only, and running a second round once the dock is connected, is a gap that keeps appearing in document review.

Two structural details are worth a look before tooling: short circuit and foreign-object attraction at the magnetic contacts, and the temperature rise of the dock in operation. Neither changes whether certification is required, but both change how many rounds it takes. The overall safety route can be broken down by market under certification services.

Health sensors and the medical boundary: wellness and medical are two routes

First make one technical fact clear: heart-rate and SpO2 sensors do not themselves transmit radio frequency and do not need a separate wireless certification. They do bring two other issues.

One is light. If the LED optical power is on the high side, an IEC 62471 photobiological safety assessment is needed. This belongs to product safety and has nothing to do with wireless certification, but it is an item that has to be producible within the whole-unit documentation.

The other is claims, which is also where trouble is more likely. The same heart-rate sensor, and the cost of the two routes is far apart:

So the order should be: fix the target market first, then the functions and claims, and only then talk about testing. Done the other way round, discovering after the hardware is frozen that the route has to change usually costs more than extra testing can solve.

Water resistance and IP rating: the declared value must match the test conditions

An IP rating is not a certificate; it is the manufacturer's declaration of protection capability, supported by measured data. It does not enter the "certification checklist", but its damage potential in export is of the same kind as health claims: one wrong sentence and it is a claims problem.

A watch has at least three states that have to be considered separately: worn on the wrist, placed on the charging dock and plugged in, and after water ingress. The water resistance test conditions and the marketing wording must agree — if the manual says "can be used for swimming", "shower-proof" or "dive-proof", then once that goes beyond the conditions actually verified, the nature is no longer "writing the parameter a little conservatively" but making an unsupported promise about product performance.

In practice, do two things: write the IP claim into the test request so the conclusion can be quoted directly, and do not substitute a "structural design description" for measurement; and run a consistency pass over the water resistance wording on the website, product pages, packaging, manual and app. Water ingress failures also involve warranty and liability allocation, and that cost is usually higher than the test fee.

Multi-country packaging: how one dataset supports several certificates

A watch has many certification items, but a good deal of the underlying data can be reused. Mapping the reuse relationships clearly saves a large amount of repeat sampling.

• RF: Bluetooth/WiFi RF test data can be reused across FCC, CE, MIC and KC, because the underlying technical requirements of the national standards are highly consistent. The approach is the same as in the six-market comparison for TWS earphones: submit once, test to the stricter standard, issue reports separately.
• SAR: partly reusable. The FCC and EU test methods differ (both use 10g averaging, but the applicable standards and assessment frameworks differ), and the test data can be cross-referenced as supporting information; Korea uses 1g averaging and Japan has separate requirements for wearables, with FCC/EU data partly acceptable. Do not assume here that "one report covers everything"; confirm market by market.
• Battery: UN38.3 is globally applicable, one test supports all markets, and it is one of the higher-reuse items.
• Safety: test once to IEC 62368-1, then convert for national differences (UL 62368-1, EN 62368-1 and so on).
• Environmental and documentation: RoHS / REACH / WEEE, Prop 65, J-MOSS, KC RoHS, China RoHS and UK RoHS are each independent; beyond those come documentation requirements such as the EU representative, Japanese and Korean manuals, and the technical conformity mark.

The scheduling experience is: start with the more demanding market and cover the others with delta testing. Specific timelines and cost depend on the number of models, the transmit modes and whether rework is needed, and are subject to the assessment of the relevant body. For the Korean market route see Korea KC services and the KC knowledge base; if you are unsure whether a given item applies in a given country, run a first pass through the certification quick lookup.

Common pitfalls: six that keep coming back in document review

Action checklist: tick each item before shipping

1. List every transmit mode (BLE, WiFi, cellular) and its output power, and turn it into one power table.
2. Use the power table to make the SAR judgement: does it fall into a case where an exemption can be applied for, and is a technical justification required.
3. Fix the cell specification and the protection board design, and confirm at the same time whether local battery requirements such as GB 31241 apply.
4. Schedule samples as a single-cell battery pack of 20 (10 + 10 after cycling), and start the cycled samples first.
5. Confirm safety and energy efficiency for the charging dock along the two routes, AC and DC, and cover the plugged-in mode in EMC.
6. Go through all health wording on the website, product pages, packaging, manual and app, and mark each sentence as wellness / medical.
7. For ECG and blood pressure functions, fix the market first and the route second, instead of building hardware first.
8. Align the water resistance wording with the conditions actually tested, and write the IP claim into the test request.
9. Schedule the more demanding market first, and submit samples once for RF, EMC and safety where possible.
10. Before shipping, confirm with the forwarder the format and validity requirements for the UN38.3 report, together with the MSDS and transport identification report.