What certifications does a wearable product need in 2026?

Share this article:

In 2026, wearable products typically need to meet a combination of legal requirements, conformity-assessment procedures, and sector-specific standards depending on where they are sold and what they do. In the EU, CE marking applies to most connected wearables through the Radio Equipment Directive, with additional MDR compliance required for medical wearables. In the US, FDA regulation applies to devices that meet the medical-device definition, while FCC authorization covers radio frequency emissions. The exact requirements depend on your product’s function and intended use, its wireless components, and the market you are entering. The sections below break down each of these dimensions so you can plan your regulatory path with confidence.

Table of Contents

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 in the same direct way.

More precisely, however, not every wearable needs a “certification”. Depending on the product and market, you may need to comply with specific regulations, complete a formal conformity-assessment procedure, meet technical standards, or obtain a specific approval or registration.

Required regulatory requirements 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 be subject primarily to general product requirements and radio-equipment requirements, while the latter may fall under the EU Medical Device Regulation (MDR) or FDA medical-device regulation.

It is useful to distinguish three different levels:

Product-level regulatory requirements and conformity assessment:

CE marking under applicable EU legislation
EU MDR for medical devices
Radio Equipment Directive (RED) for applicable radio equipment
ATEX for applicable equipment intended for potentially explosive atmospheres
PPE Regulation for applicable protective equipment
FCC authorization for applicable products in the US
FDA clearance, approval or other applicable regulatory pathways for medical devices in the US

Technical standards and testing:

IEC 60601-1 — medical electrical equipment safety, where applicable
ISO 10993 — biological evaluation of medical devices (biocompatibility), particularly relevant for skin-contact wearables and smart textiles
ISO 14971 — risk management for medical devices
IEC 62304 — software lifecycle processes for medical-device software, where applicable
IEC 62366 — usability engineering for medical devices, where applicable
IP ratings — ingress-protection classifications resulting from testing

Organisation-level quality management:

ISO 13485 — a quality-management-system standard for organisations involved in medical-device design, development, production and servicing

ISO 13485 is therefore fundamentally different from CE marking. It applies to the organisation’s quality-management system, not to an individual wearable. Holding an ISO 13485 certificate does not by itself make a product compliant with the MDR or give it a CE mark.

It’s also worth distinguishing ISO 13485 from ISO 10993, the standard covering biological evaluation of medical devices. (ISO 13485 helps you manage how you build safely, while ISO 10993 helps prove what you build is safe to wear) — the former governs your quality-management processes, the latter governs whether the materials in contact with skin are actually safe.

Since February 2026, the distinction has become particularly relevant in the US. The FDA’s Quality Management System Regulation (QMSR) incorporates ISO 13485:2016 by reference into the US medical-device quality-system requirements. This brings the US framework substantially closer to the international ISO 13485 model, although FDA compliance with QMSR is not the same thing as holding an ISO 13485 certificate.

The practical lesson: start by mapping your product’s intended use and claims, its wireless components, applicable regulations and the markets you intend to enter. That map tells you which requirements are legally mandatory, which standards are relevant, and what conformity-assessment route you will need.

What certifications does a wearable need in the EU?

In the EU, not every wearable automatically requires CE marking. CE marking is mandatory when the product falls under EU legislation that requires it.

For connected electronic wearables, the Radio Equipment Directive (RED) is often relevant. Other legislation may apply depending on the product, including the Medical Device Regulation (MDR), the Personal Protective Equipment (PPE) Regulation or ATEX legislation.

CE marking is not a certificate issued by the European Union. It is the manufacturer’s declaration that the product conforms to all applicable EU legislation requiring CE marking, following the relevant conformity-assessment procedure.

CE marking and the Radio Equipment Directive

Almost every connected wearable containing Bluetooth, Wi-Fi, cellular or another radio interface will fall within the scope of the Radio Equipment Directive when placed on the EU market.

RED covers the essential requirements applicable to radio equipment, including health and safety, electromagnetic compatibility and the effective use of radio spectrum.

For many products, the manufacturer can carry out the applicable conformity assessment using internal production control, supported by appropriate testing and technical documentation. Depending on the applicable conformity-assessment route, a notified body may also need to be involved.

An important recent development is the introduction of additional RED cybersecurity, privacy and anti-fraud requirements for certain categories of internet-connected radio equipment. These requirements became applicable from 1 August 2025. The EU regulatory framework is also evolving as the Cyber Resilience Act becomes applicable.

The manufacturer must prepare the required technical documentation and EU Declaration of Conformity before affixing the CE mark. The legal responsibility for conformity ultimately remains with the manufacturer.

EU MDR for medical wearables

MDR compliance is among the most demanding regulatory challenges in the EU wearable space. Under MDR, medical devices are classified as Class I, IIa, IIb or III according to their intended purpose and associated risk.

A wearable intended to monitor physiological parameters for medical purposes may fall into Class IIa, IIb or another classification depending on its intended purpose and the applicable MDR classification rules. The classification determines the applicable conformity-assessment route.

Depending on the classification and device characteristics, a notified body may need to assess aspects of the quality management system and technical documentation before the manufacturer can affix the CE marking.

Medical-device compliance can involve technical documentation, risk management, clinical evaluation, biocompatibility of materials in contact with the skin, usability engineering, verification and validation, and post-market surveillance. The exact evidence required depends on the device and its intended purpose.

Class I devices are generally subject to manufacturer self-declaration, but important exceptions exist. For example, Class I devices that are sterile, have a measuring function or are reusable surgical instruments require notified-body involvement for the relevant aspects of conformity assessment.

For medical devices, compliance therefore does not end at market launch. Manufacturers must maintain post-market surveillance and vigilance activities throughout the product lifecycle.

For wearables intended for use in potentially explosive atmospheres, ATEX requirements may also apply. Military wearables can additionally be subject to defence-specific procurement, qualification and technical standards, depending on the customer and application.

What certifications does a wearable need in the US?

In the US, the regulatory pathway is similarly determined by what the product does and how it is marketed.

Wearables with radio functionality may require FCC equipment authorization. Medical devices may fall under FDA regulation, while low-risk general-wellness products may fall outside active FDA device regulation.

It is therefore important to distinguish between FDA registration and listing, FDA clearance and FDA approval. These are not interchangeable terms, and not every medical wearable requires a 510(k) or PMA.

FCC authorization

FCC authorization for most modern wearables comes down to two practical paths: Certification and Supplier’s Declaration of Conformity (SDoC).

FCC Certification is generally required for intentional radiators such as Bluetooth, Wi-Fi and cellular transmitters. The equipment is tested against the applicable FCC requirements and the certification is issued through the FCC’s equipment-authorization process.

SDoC is used for certain types of equipment, particularly many unintentional radiators, where the responsible party declares compliance based on the required testing and records.

The older Verification route still exists for a narrow set of equipment categories, but it is not the normal route for modern connected wearables.

In practice, most Bluetooth- or Wi-Fi-enabled wearables will need FCC Certification for their radio functionality.

FDA regulation of medical wearables

On the FDA side, the key question is whether the wearable meets the US definition of a medical device and what its intended use is.

Low-risk products intended solely for general wellness may fall under the FDA’s general-wellness policy rather than active device regulation.

If a product is a medical device, the regulatory pathway depends on its classification:

Class I — generally subject to general controls. Many Class I devices are exempt from 510(k) premarket notification, although other regulatory requirements still apply.
Class II — subject to general and special controls. Many Class II devices require a 510(k) premarket notification demonstrating substantial equivalence to a legally marketed predicate device, although exemptions exist.
Class III — generally subject to the most stringent controls and, where applicable, Premarket Approval (PMA).

FDA registration and listing should therefore not be described as equivalent to “FDA approval”. The applicable regulatory pathway needs to be determined from the product’s intended use and classification.

The FDA’s Quality Management System Regulation and ISO 13485

A significant recent change is that, as of 2 February 2026, the FDA’s Quality Management System Regulation (QMSR) replaced the previous Quality System Regulation and incorporated ISO 13485:2016 by reference into the US medical-device quality-system requirements.

This brings US quality-system expectations substantially closer to the international ISO 13485 framework. However, FDA compliance with QMSR is not the same as holding an ISO 13485 certificate. FDA assesses compliance through its own regulatory and inspection framework.

For a medical-device manufacturer supplying both the EU and US markets, an ISO 13485-based quality-management system can therefore provide a common foundation for both markets, while the specific regulatory and conformity-assessment requirements remain different.

The FDA’s Digital Health Center of Excellence has also published guidance on software and digital health technologies, which is increasingly relevant for wearables where algorithms or software contribute to the clinical function.

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

A wearable’s intended purpose and product category are major drivers of its regulatory 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 medical purpose, or detects gas exposure in a mining environment.

Function and intended purpose determine the applicable regulatory framework, while classification determines the specific regulatory route.

Consider how requirements can differ across common wearable categories:

Sports and fitness wearables that make no medical claims may be subject primarily to general product requirements and, where applicable, radio-equipment requirements such as RED in the EU and FCC requirements in the US.
Medical wearables such as ECG monitors or continuous glucose monitors can fall under the MDR in the EU and FDA medical-device regulation in the US. The applicable evidence and conformity-assessment route depend on the intended purpose and classification.
Industrial and safety wearables may fall under the EU Personal Protective Equipment (PPE) Regulation if they are intended to protect the wearer against specified risks. A device that only monitors or alerts to a hazard, without itself providing protection, may not automatically qualify as PPE.
Military wearables can be subject to defence procurement specifications and qualification requirements in addition to any commercial regulatory requirements applicable to the product.
Wearables for hazardous environments may fall under ATEX requirements when intended for use in potentially explosive atmospheres.

The practical implication is that changing a product’s intended purpose or claims can change its regulatory classification and therefore its compliance pathway. Teams developing custom wearable products should define the intended use and claims as early as possible, because these decisions can influence hardware architecture, sensors, materials, software, testing and documentation.

How long does wearable certification typically take?

Wearable regulatory and conformity-assessment timelines vary significantly by product category, technical complexity, target market and the required assessment route.

For a relatively straightforward consumer wearable, the regulatory testing and documentation process may be completed within a few months if the product has been designed with the applicable requirements in mind. Medical-device projects can take considerably longer, particularly where clinical evidence, extensive verification and validation, quality-system assessment or notified-body involvement are required.

These should be treated as project-planning estimates rather than fixed regulatory timelines.

The main variables that affect the duration are:

Device classification and regulatory pathway — higher-risk medical devices generally require more extensive conformity assessment and evidence.
Completeness of technical documentation — missing or inconsistent documentation can lead to additional review cycles.
Laboratory availability — EMC, radio, electrical safety and other specialist testing can introduce scheduling constraints.
Design compliance — hardware that was not designed with applicable standards in mind can fail testing and require redesign and retesting.
Quality management system readiness — medical-device projects may require a mature QMS and associated records before formal assessment.
Notified body capacity — notified-body availability and review cycles can affect the overall project schedule.
Clinical evidence requirements — medical wearables may require substantial clinical evaluation or clinical investigation depending on their intended purpose and existing evidence.

Teams that treat regulatory compliance as a final step rather than a design constraint are more likely to encounter expensive redesign and testing cycles. Building the applicable requirements into the development process at the appropriate stage can substantially reduce this risk.

When should certification planning start in a wearable development project?

Regulatory planning should start early in a wearable development project, ideally during the feasibility phase.

This does not mean that a development team needs to run a full certification process from the first prototype. Early on, the goal is to understand the intended use, claims, target markets and the regulatory constraints that could affect fundamental architecture decisions.

Detailed compliance engineering and certification preparation can then start at the appropriate point in the development process.

For example, at Elitac Wearables, regulatory and certification work is normally fully integrated from Phase 4 – Engineering & Validation onwards. This allows the earlier research and concept-development phases to remain lean and fast, while ensuring that the engineering phase is explicitly designed toward the requirements that will ultimately need to be demonstrated.

The regulatory route can influence which components are appropriate, what testing the product must undergo, what documentation needs to be generated, and what clinical or performance evidence may be required.

Making these decisions too late can mean revisiting architecture, materials, firmware and mechanical design under time and budget pressure. Starting the detailed compliance work too early, however, can also create unnecessary process and documentation around concepts that may still change.

A practical regulatory planning timeline looks like this:

Feasibility phase: Define intended use and claims, identify applicable regulations and standards, determine the likely classification and map the regulatory pathway for each target market.
Concept and early development: Identify regulatory constraints that could affect architecture, component selection, materials or system design.
Engineering phase: Integrate applicable standards and regulatory requirements into the detailed design; generate the required technical documentation and perform appropriate pre-compliance testing.
Verification and validation: Generate the evidence required to demonstrate that the final design meets its defined requirements.
Formal conformity assessment: Complete the applicable testing, documentation and, where required, notified-body or regulatory submissions.
Market launch: Complete the applicable conformity assessment and documentation before placing the product on the market, then maintain the required post-market surveillance and vigilance activities.

For medical wearables specifically, clinical evaluation should be treated as a parallel workstream rather than something that starts after the hardware is finished. The MDR requires manufacturers to plan and document clinical evaluation and to maintain appropriate post-market surveillance throughout the product lifecycle.

How Elitac Wearables helps with wearable certification

Certification and regulatory compliance are often where wearable development projects become more complex, particularly when requirements were not considered during the early design stages.

Elitac Wearables approaches this in two stages: understand the regulatory path early, then engineer toward it at the right point in development.

During feasibility and concept development, Elitac Wearables can help identify the intended regulatory pathway, relevant standards and potential constraints. From Phase 4 – Engineering, these requirements are normally integrated more deeply into the product architecture, detailed design, testing and documentation. This keeps the early R&D process lean and fast while still building the product toward its eventual compliance requirements.

The team brings experience with EU MDR compliance for medical wearables, CE marking, ATEX-related requirements and military qualification requirements through 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 reducing technical and regulatory rework while keeping the development path aligned with the intended market.

Elitac’s multidisciplinary team, covering hardware, firmware, textile integration and human factors, can support certification-ready product development by:

Mapping the regulatory pathway for your product’s intended use, claims and target markets
Identifying applicable regulations and standards before key hardware decisions are made
Assessing the biocompatibility of materials in prolonged skin contact, in line with ISO 10993
Selecting components and architectures that support the intended compliance pathway
Integrating relevant standards and regulatory requirements into the engineering process
Generating technical documentation throughout development rather than reconstructing it at the end
Planning and coordinating pre-compliance testing with appropriate laboratories
Supporting verification and validation activities required for the final product
Supporting preparation for formal conformity assessment and interaction with notified bodies or other assessment organisations
Advising on clinical evidence requirements for medical wearables and supporting validation planning

If your wearable development project is approaching a regulatory 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, claims and target markets can help clarify the applicable regulatory pathway and how to build toward it from day one.