Sourcing smart watches

The principle to hold on to: intended purpose, not components. Regulators in most developed markets classify by what a product is presented as doing. A sensor that produces a number is not automatically regulated; a statement that the number diagnoses, monitors or predicts a condition usually is what brings the product into scope.

So the factory's feature list is a compliance document you are inheriting. "Blood pressure monitoring", "ECG", "blood glucose", "arrhythmia detection", "blood oxygen for medical reference" — these phrases appear routinely on Chinese reference designs, and copying them into an overseas listing makes a claim your business has to stand behind. Decide, in writing, exactly which claims you will make and require the supplier to remove the rest from the packaging, the manual, the app and the firmware strings.

Consumer wording is not a loophole either. Describing a regulated function in casual language does not change what the product is presented as doing, and marketplaces increasingly enforce this independently of regulators — a listing takedown arrives faster than an inspector.

And the obligation follows your brand. Placing the product on the market under your own name generally makes you the manufacturer for regulatory purposes, so the technical documentation, the claims and the traceability attach to you rather than to the factory whose certificates you were shown.

Where a claim genuinely matters to your product, get specialist advice for your specific market before production — this page gives you the question to ask, deliberately not the answer, because the answer depends on the market, the wording and the version of the rules in force.

The platform and who owns it. Most smart watches are built on a chipset plus a reference design, and the firmware and the companion app usually belong to the design owner rather than to the assembler. Ask which platform, who can change the firmware, whose app it is and under whose developer accounts it is published. That single answer decides whether you have a product or a rebadge.

Display and glass. Type, brightness, and how the glass is bonded to the display — an air gap versus full bonding changes both readability and how well it survives a drop. Ask what happens in direct sunlight and test it outdoors, not in an office.

Sensors and how they are validated. Optical heart rate is affected by skin tone, tattoos, hair, fit and motion, and the honest specification is about the sensor part, the optical path and the strap tension rather than an accuracy percentage. No accuracy figure appears on this page; validate on several people, in motion, against a reference you trust.

Battery, charging and the case. Cell manufacturer, capacity, whether it is a proprietary charging puck (a spare-parts liability), and how the case is sealed. Then the water rating: an IP or depth rating is the result of a defined test on a defined unit, so ask which test, on which model, by whom — and specifically whether the rating survives after the strap lugs have been assembled.

Straps and lugs. This is the mechanical failure point in wearables — a lug that cracks or a quick-release pin that lets go loses the watch. Specify the lug material, the pin mechanism and a defined pull test.

Radio. A smart watch is an intentional radiator, usually Bluetooth and sometimes wi-fi, GNSS or cellular. Bluetooth needs qualification with a Declaration ID against a member company, and each destination market needs its own equipment approval on top. A cellular model adds network certification and, in some markets, operator approval — a substantially longer and more expensive path that is often discovered late.

Battery. Lithium cells mean transport documentation and the cell specification matters: name the cell maker, require new cells, and ask for the cell's own test report. Transport thresholds are deliberately not published here; the guides on watt-hour conversion and shipping lithium batteries by air carry them.

Data. A connected wearable collects personal data, and health-related data is treated as a specially sensitive category in most privacy regimes. Establish who operates the app and the backend, in which country the data is stored, what the retention is, whether there is a data-processing agreement you can actually sign, and what happens to your customers if the factory switches platform. If the app is the factory's and the account is the factory's, then your customers' data relationship is with a company they have never heard of and you cannot control — and you will still be the one answering for it.

App store publication. Establish whose developer accounts the companion app is published under before production. An app under the factory's account can be withdrawn, renamed or left un-updated, and every watch you sold depends on it.

Business licence and business scope (经营范围) first, then the platform question: own design or reference design, who changes firmware, whose app. Wearables have an unusually thick layer of assemblers around a small number of platforms, so this answer varies far more than the specification sheets do.

Wear the samples for a week, several people, in real life: showering if it claims water resistance, exercising, sleeping, in sunlight, and with the phone out of range and back. Most complaints in this category are about connection, battery drain overnight and notifications that do not arrive — none of which appears on a bench.

Test the app as a customer would. Set it up on a fresh phone, in your market's language, read what it asks permission for, and read its privacy policy. That is the part of the product your customer actually interacts with daily, and it is usually the part nobody sampled.

Then take one apart: battery marking and cell maker, how the case is sealed, the sensor assembly, the antenna and how the lugs are anchored.

Every supplier on this site is a manufacturer, and the registered-scope check is one of the things confirmed before a listing goes live.