What certifications does a wearable product need in 2026?

In 2026, wearable products typically need a combination of legally required certifications and sector-specific approvals depending on where they are sold and what they do. In the EU, CE marking is mandatory across most wearable categories, with additional MDR compliance required for medical wearables. In the US, FDA clearance or registration applies to health-related devices, while FCC approval covers radio frequency emissions. The exact requirements depend on your product’s function, the body part it sits on, and the market you are entering. The sections below break down each of these dimensions so you can plan your certification path with confidence.

Which certifications are legally required versus optional for wearables?

The distinction between required and optional certifications for wearables comes down to one question: does your product make a medical claim, emit radio frequency signals, or fall under a regulated product category? If yes to any of these, at least one certification is legally mandatory before you can sell. Optional certifications, such as ISO quality management standards or sector-specific safety marks, add credibility but are not enforced by law.

Required certifications are determined by product function and target market, not by form factor alone. A wristband that tracks steps is treated very differently from one that monitors cardiac arrhythmia. The former may only require CE marking and FCC approval for its wireless chip. The latter triggers the EU Medical Device Regulation (MDR) or FDA oversight, which carry far more demanding technical and clinical requirements.

Optional certifications worth considering include:

• ISO 13485 (quality management for medical devices) — not legally required in all jurisdictions but often expected by hospital procurement teams and large-scale buyers
• IEC 60601-1 (medical electrical equipment safety) — required in some markets, voluntary in others, but widely adopted as a benchmark for body-worn electronics
• IP ratings (ingress protection for dust and water) — not mandatory, but practically essential for sports, industrial, and military wearables
• ATEX certification — only relevant for wearables used in explosive or hazardous environments, but legally required in those contexts

The practical lesson: start by mapping your product’s claims, its wireless components, and the markets you intend to sell in. That map tells you which certifications are non-negotiable and which are strategic choices.

What certifications does a wearable need in the EU?

In the EU, all wearable products placed on the market must carry CE marking, which demonstrates conformity with relevant EU directives and regulations. The specific directives that apply depend on the product’s function. A wearable with Bluetooth or other wireless technology must comply with the Radio Equipment Directive (RED). A wearable that makes a medical claim or is intended to diagnose, monitor, or treat a condition falls under the EU Medical Device Regulation (MDR 2017/745).

CE marking and the Radio Equipment Directive

Almost every connected wearable sold in the EU requires RED compliance. This covers radio frequency emissions, electromagnetic compatibility (EMC), and electrical safety. Manufacturers must produce a Declaration of Conformity and, for most product types, can self-certify after conducting the required testing through an accredited laboratory. For higher-risk categories, a Notified Body must be involved.

EU MDR for medical wearables

MDR compliance is the most demanding certification challenge in the EU wearable space. Under MDR, devices are classified into Class I, IIa, IIb, or III depending on risk level. A wearable ECG monitor, for example, typically falls into Class IIa or IIb, which requires a Notified Body to audit your technical documentation, clinical evidence, and quality management system before you can affix the CE mark. Class I devices with a measuring function still require specific documentation and, in some cases, Notified Body involvement. MDR also introduces post-market surveillance obligations that continue long after launch.

For wearables operating in hazardous environments, ATEX certification under the ATEX Directive (2014/34/EU) is also legally required. Military wearables follow separate procurement and qualification standards set by the relevant defence authority rather than a single EU-wide framework.

What certifications does a wearable need in the US?

In the US, wearables with wireless functionality require FCC authorization, which verifies that the device does not cause harmful interference with other radio frequency equipment. Wearables that make health or medical claims are subject to FDA oversight, with the regulatory pathway depending on whether the device is classified as a medical device under the Federal Food, Drug, and Cosmetic Act.

FCC authorization is handled through one of three routes: Certification (most common for intentional radiators like Bluetooth devices), Supplier’s Declaration of Conformity (SDoC), or Verification. Most wearables with Bluetooth, ANT+, or Wi-Fi will need FCC Certification, which requires testing at an accredited laboratory.

On the FDA side, the key question is whether your wearable meets the definition of a medical device. If it does, you will need to determine its classification:

• Class I devices (low risk, such as general wellness trackers) are often exempt from premarket review but must still register with the FDA and comply with general controls
• Class II devices (moderate risk, such as ECG monitors or blood oxygen wearables) typically require a 510(k) premarket notification, demonstrating substantial equivalence to a predicate device
• Class III devices (high risk, such as implantable or life-sustaining devices) require Premarket Approval (PMA), which is the most rigorous pathway

The FDA’s Digital Health Center of Excellence has published guidance on software as a medical device (SaMD) and mobile medical applications, which is increasingly relevant for wearables where the algorithm, not just the hardware, drives the clinical function.

How does a wearable’s product category change its certification requirements?

A wearable’s product category is the single biggest driver of its certification burden. The same physical form factor – a chest-worn device, for example – can require entirely different regulatory pathways depending on whether it measures heart rate for athletic performance, monitors ECG for a cardiologist, or detects gas exposure in a mining environment. Function determines classification, and classification determines the regulatory route.

Consider how certification requirements shift across common wearable categories:

• Sports and fitness wearables that make no medical claims typically need CE marking (RED compliance) in the EU and FCC authorization in the US. No medical device regulation applies unless health claims are introduced
• Medical wearables (ECG monitors, continuous glucose monitors, respiratory rate sensors) trigger MDR in the EU and FDA oversight in the US. Clinical evidence, technical documentation, and in many cases Notified Body or FDA review are required
• Industrial and safety wearables used in workplaces may fall under the EU Personal Protective Equipment (PPE) Regulation (2016/425) if they are designed to protect the wearer from hazards. PPE regulation introduces its own conformity assessment requirements
• Military wearables follow defence procurement standards set by national defence ministries rather than commercial regulatory frameworks
• Wearables in hazardous environments require ATEX certification if deployed in areas with explosive atmospheres

The practical implication is that adding or removing a single product claim can move your wearable from one regulatory category to another. Teams building custom wearable products should define the intended use and any claims precisely before hardware design begins, because those decisions lock in the certification path.

How long does wearable certification typically take?

Wearable certification timelines vary significantly by product category and target market. For a straightforward consumer wearable requiring only CE marking and FCC authorization, the process can take between two and four months if the product is well-designed from the outset. For a medical wearable requiring EU MDR compliance with Notified Body involvement, the timeline is typically twelve to twenty-four months, and in some cases longer.

The main variables that affect certification duration are:

• Device classification — Class I medical devices move faster than Class IIa or IIb, which require Notified Body review queues that can add months
• Completeness of technical documentation — incomplete submissions are returned, restarting the clock
• Laboratory availability — accredited test labs for EMC, RED, and IEC 60601 testing often have lead times of four to eight weeks
• Design compliance — hardware that was not designed with certification requirements in mind frequently fails initial testing, requiring redesign and retesting cycles
• Notified Body capacity — since MDR came into full effect, Notified Body capacity in Europe has been under pressure, adding to review timelines

Teams that treat certification as a final step rather than a design constraint consistently face the longest delays. Those that build to certification requirements from the first prototype reduce both timeline and cost substantially.

When should certification planning start in a wearable development project?

Certification planning should start at the very beginning of a wearable development project, ideally during the feasibility phase before any hardware decisions are made. The certification route determines which components are permissible, what testing the product must survive, what documentation must be generated throughout development, and what clinical or performance evidence is required. Making those decisions late means revisiting architecture, materials, and firmware under time and budget pressure.

The most costly mistake in custom wearable product development is treating regulatory compliance as a post-development activity. Hardware choices made without certification in mind, such as selecting a radio module without checking its regulatory status in target markets, or choosing a sensor that cannot be validated against a clinical reference standard, create expensive rework cycles late in the project.

A practical certification planning timeline looks like this:

1. Feasibility phase: Define intended use, identify product classification, and map the regulatory pathway for each target market
2. Proof of concept: Confirm component choices are compatible with certification requirements; begin generating design documentation
3. Prototype development: Conduct pre-compliance EMC and safety testing; identify gaps early while redesign is still low-cost
4. Pilot production: Submit for formal certification testing; engage Notified Body if required
5. Market launch: Certification complete; post-market surveillance and vigilance obligations begin (for medical devices)

For medical wearables specifically, clinical evidence generation is a parallel workstream that must begin long before the final product is locked. Waiting until the hardware is finalised to start clinical validation is one of the most common and expensive planning errors in the sector.

How Elitac Wearables helps with wearable certification

Certification is where many wearable development projects stall, and it is almost always because compliance was not built into the design from the start. Elitac Wearables integrates certification planning into every phase of its six-stage development process, from the initial feasibility check through to production. The team brings direct experience with EU MDR compliance for Class I and Class II medical wearables, CE marking, ATEX, and military qualification requirements, developed through real projects including the BalanceBelt medical wearable and the Mission Navigation Belt for the Royal Netherlands Army.

For B2B clients, the practical value of this approach is risk reduction and timeline control. Elitac’s in-house multi-disciplinary team, covering hardware, firmware, textile integration, and human factors, designs to certification requirements rather than retrofitting compliance after the fact. Specific ways the team supports certification-ready development include:

• Mapping the regulatory pathway for your product category and target markets before hardware decisions are made
• Selecting components and architectures that are compatible with relevant directives and standards
• Generating technical documentation throughout development rather than reconstructing it at the end
• Coordinating pre-compliance testing and supporting formal submissions with accredited laboratories and Notified Bodies
• Advising on clinical evidence requirements for medical wearables and supporting validation planning

If your wearable development project is approaching a certification decision point, or if you are starting a new project and want to avoid the rework that comes from planning compliance too late, speak with the Elitac team. A focused conversation about your product’s intended use and target markets is the fastest way to understand what your certification path looks like and how to build toward it from day one.

Related Articles

• What happens when wearable product development goes over budget, and how do you prevent it?
• What are the hidden costs of wearable product development that most vendors won't tell you?
• What are the regulatory risks that can stall a wearable product launch, and how do you mitigate them?
• What is the role of AI in modern wearable product development?
• What role does firmware play in wearable product development?