IllustrationYou can plan an AI wearable certification by order of dependency, even without published durations. Decide module reuse first, test the radio, assemble the FCC package, check for a pre-approval wait, qualify Bluetooth before you sell, and control late changes after the grant. Official sources give no timelines, so get dated lab quotes.
A product manager needs two answers from certification: which steps come in which order, and what makes the schedule slip. The official FCC and Bluetooth SIG sources answer the first and part of the second. They do not give durations or fees, so this guide gives none. It orders the steps by what each one depends on, shows where the rules create waits and rework, and lists what to measure on your own program.
This is an engineering team's summary of public rules, as of October 31, 2026. It does not constitute legal advice. Ask a lawyer to confirm how the rules apply to your product. It covers FCC radio certification and Bluetooth qualification. It does not cover battery or product safety standards, markets outside the United States, or wearable RF exposure details.
In what order do the steps run?
The order comes from the dependencies in each rule. Elapsed time for each step is vendor and lab specific, and the official pages do not publish it.
| Step | What the rule says | Depends on | Source |
|---|---|---|---|
| 1. Decide: reuse a certified module, or certify the whole device | A module can be certified on its own only if it meets the listed conditions in 47 CFR 15.212. Your wearable either meets them or the whole device is certified. | Nothing before it. Every later step depends on this answer. | 47 CFR 15.212, as of October 31, 2026 |
| 2. Test the radio in the configurations the rule names | For a modular transmitter, 15.212 requires a stand-alone test. Plan the host-device configuration as well. | Step 1, and a build that can be tested. | 47 CFR 15.212, as of October 31, 2026 |
| 3. Assemble the application package | Form 731 with all questions answered, a measurement report, exterior and construction photographs, and a legible FCC identifier label or a sample label. | Step 2 results, and final-looking hardware for the photographs. | 47 CFR 2.1033, as of October 31, 2026 |
| 4. Check whether your category needs a pre-approval wait | For equipment on the FCC Pre-approval Guidance list, the certification body does an initial review and waits for the Commission to concur before it grants. Whether your wearable is on that list is a question for your certification body. | Step 3 package, filed through a certification body. | 47 CFR 2.964, as of October 31, 2026 |
| 5. Qualify Bluetooth | Every Bluetooth product must be qualified on or before the day you begin to sell or distribute it. The product name and model number entered must match your marketing and sales. | Final product name and model number. | Bluetooth SIG, Qualify a product, as of October 31, 2026 |
| 6. Control late hardware changes after the grant | After a grant, a Class I permissive change needs no filing. A Class II change must not be marketed under the existing grant until the change is acknowledged. Only the grant holder may make these changes. | A granted device and a change request, such as a new antenna or battery. | 47 CFR 2.1043, as of October 31, 2026 |
The table has no duration column on purpose. Neither the FCC rules nor the Bluetooth SIG pages publish how long a lab, a certification body or a review takes. Put a duration in your schedule only with a dated written quote.
Can your wearable reuse a certified module?
This decision comes first because it changes the scope of every later step. A module can be certified separately only if it meets the conditions of 47 CFR 15.212. The table lists the conditions we checked and a question to put to your own layout (source, as of October 31, 2026).
| Condition | Rule text, paraphrased | Question for your design | Source |
|---|---|---|---|
| Shielding | The radio elements of the modular transmitter must have their own shielding. | Does your radio sit in its own shield, or share one with the rest of the board? | 47 CFR 15.212, as of October 31, 2026 |
| Power supply regulation | The module must have its own power supply regulation. | Does the module regulate its own supply, or run from a rail the host regulates? | 47 CFR 15.212, as of October 31, 2026 |
| Antenna coupling | The module must use a permanent or unique antenna coupler. | Can a ring, band or pendant antenna layout still use the coupler the module was certified with? | 47 CFR 15.212, as of October 31, 2026 |
| Stand-alone test | The modular transmitter must be tested in a stand-alone configuration. | Was the module tested alone, and do you hold that report? | 47 CFR 15.212, as of October 31, 2026 |
| Label | The module needs an FCC ID label or an electronic display of it. | Where does the ID appear once the module sits inside a closed wearable housing? | 47 CFR 15.212, as of October 31, 2026 |
| RF exposure | The module must comply with RF exposure rules. | Does the body-worn use case match the use case the module was assessed for? Ask your test lab. We did not review wearable RF exposure rules for this article. | 47 CFR 15.212, as of October 31, 2026 |
If one row fails, the module route is closed and you plan on certifying the whole device. A wearable often shrinks the board and moves the antenna, so check these conditions against your final layout, not against the module datasheet alone.
What makes the schedule slip?
Each row follows from the rule text linked in it. It is engineering reasoning about how the rules behave. It is not an account of any company's project.
| Trigger | Why it slips | Source |
|---|---|---|
| Late antenna or battery change | After a grant, the rule separates a change that needs no filing (Class I) from one that cannot be marketed under the existing grant until acknowledged (Class II). Which one a change falls into is decided by the rule text and your certification body. | 47 CFR 2.1043, as of October 31, 2026 |
| Module fails a modular condition | If the design does not meet a 15.212 condition, such as its own shielding or its own power regulation, the module route is closed and the whole device goes through certification. | 47 CFR 15.212, as of October 31, 2026 |
| No room for the compliance statement | The statement "This device complies with part 15 of the FCC Rules." belongs on the device. If the device is too small, it can go in the user manual plus on the packaging or a removable label. | 47 CFR 15.19, as of October 31, 2026 |
| Product name differs from the Bluetooth entry | The name and model number entered at qualification must match what you use in marketing and sales. A product that appears unqualified can be impounded by customs. | Bluetooth SIG knowledge base, as of October 31, 2026 |
| Pre-approval wait | For categories on the Pre-approval Guidance list, the grant waits for the Commission to concur. The official sources give no duration for this wait. | 47 CFR 2.964, as of October 31, 2026 |
| Photos or label not ready | The application needs exterior and construction photographs and a legible FCC identifier label or sample label. A build that cannot yet produce them cannot file. | 47 CFR 2.1033, as of October 31, 2026 |
Which documents should the pre-test build produce?
The FCC application rule names the core package (47 CFR 2.1033, as of October 31, 2026). The last three items come from the rules and Bluetooth pages linked elsewhere in this guide.
- FCC Form 731, with all questions answered.
- A measurement report for the radio.
- Exterior and construction photographs of the device.
- A legible FCC identifier label, or a sample label.
- The stand-alone test report, if you rely on a modular transmitter.
- A label plan that shows where the Part 15 compliance statement goes, including the manual and packaging route for small devices.
- The Bluetooth qualification record, with the product name and model number you use in sales.
- If you buy a Bluetooth module, the module maker's QDID, passed on to you with the design.
What are the common traps?
These follow from the facts above. This is engineering reasoning. None of it describes a real incident at any company.
- Treating a module as a free pass. 15.212 lists conditions the module must meet. A wearable layout that moves the antenna or shares a power rail can fail a condition the module met in its own report.
- Freezing the antenna and battery last. After a grant, a Class II change cannot be marketed under the existing grant until it is acknowledged. A late battery or antenna swap can therefore hold up shipments.
- Putting the label on the schedule at the end. A ring or small band has little surface. The rule allows the manual, packaging or a removable label for devices too small to carry the statement, but the application still needs a legible FCC identifier label or sample label.
- Renaming the product after qualification. The Bluetooth entry must match your marketing and sales names. A late rename creates a mismatch that you then have to correct.
- Putting a duration on the pre-approval step. The rule describes a wait for the Commission to concur. It gives no length. Any week count in a plan for that step is a guess.
- Assuming one standard covers everything. This article covers FCC radio rules and Bluetooth qualification. It does not cover battery or product safety standards, wireless rules outside the United States, or wearable RF exposure details. Source those separately before you set a launch date.
What should you measure on your own program?
The official sources give no durations, fees or results, and we have measured none for you. These are measurements you run on your own board and your own program. Set each pass line from your launch requirements and write it down before you start.
| What to measure | How | How to set the pass line |
|---|---|---|
| Which route applies | List each 15.212 condition in a table. For each one, attach the drawing, layout or module report that shows it is met, or mark it open. | Set the rule yourself: every condition needs a document, and one open row means you plan for whole-device certification. |
| Time from change request to a filed answer | Keep a dated log of every late hardware change request from first request to written answer from your certification body, and tag each as Class I or Class II once it is decided. | Write the maximum delay your launch can absorb before you start the log. Compare the log against it at every design freeze. |
| Build readiness for the package | Run a dry run on the pre-test build: take the exterior and construction photographs, fit the label, and fill in Form 731. Record each item that could not be produced. | Pass only when every item can be produced. The count of open items is the number to drive to zero. |
| Label space | Place the compliance statement and FCC ID on a real unit or a full-size mockup at the size the rule and your lab accept, and test legibility with your intended reader. | Decide in advance what counts as legible. If it cannot fit, document the manual, packaging or removable label route. |
| Name consistency | Export the product name and model number from your Bluetooth entry, your packaging artwork, your store listing and your marketing files, and compare them as text. | Pass only on an exact match across all four sources. |
| Pre-approval wait | Ask your certification body in writing whether your category is on the Pre-approval Guidance list. Record the date asked and the date answered. | The official sources give no duration, so the wait stays a labeled unknown in your schedule until a body gives you a dated quote. |
What should you ask before you submit?
Take this list to your engineering lead, your certification body and any partner who plans the program for you.
- Does our radio meet each 15.212 condition, and which document shows it?
- Are we certifying a module, or the whole device, and who decided?
- Which hardware items are frozen before the test build, and what happens if an antenna or battery changes afterward?
- Is our category on the FCC Pre-approval Guidance list, and who confirmed that in writing?
- Where does the FCC ID and the compliance statement appear on the finished device, and what is the fallback for a small body?
- Who is the grant holder? Only the grant holder may make permissive changes.
- What product name and model number are in the Bluetooth entry, and do they match our packaging and store listing?
- If we use a module, did the module maker pass the QDID to us?
- Which certification steps outside this article apply to us, such as battery safety and markets outside the United States, and who owns them?
- Which dates in our schedule come from a dated quote, and which are guesses?
Questions about certification planning
How many weeks does certification take?
The official FCC and Bluetooth SIG sources do not publish durations or lab fees, so this article gives none. Laboratory and certification body queues are quoted by those organizations. Ask for a dated written quote and mark every duration in your plan with its source and date.
Can a wearable reuse a certified module?
Only if the module meets the conditions in 47 CFR 15.212, as of October 31, 2026. They include its own shielding, its own power supply regulation, a permanent or unique antenna coupler, stand-alone testing, an FCC ID label or electronic display, and RF exposure compliance. Check each one against your layout.
Do I need to print the Bluetooth QDID on the product?
Bluetooth SIG says there is no requirement to display the QDID or Declaration ID on the product. Packaging and marketing must match the product information in Launch Studio, and a product that appears unqualified can be impounded by customs (Bluetooth SIG knowledge base, as of October 31, 2026).
What happens if I change the antenna or battery after the grant?
47 CFR 2.1043 sorts changes into Class I, where no filing is required, and Class II, where the modified equipment must not be marketed under the existing grant until the change is acknowledged. Which class applies to your change is a decision for the grant holder and the certification body. This is an engineering summary and does not constitute legal advice. Ask a lawyer to confirm.
Does Duobay certify the device for me?
We plan FCC, lab and module rules from Gate 0 and manage the process with the labs, while the client pays certification and lab fees. We do not hold your grant for you and we do not publish prices. Tell us about your device.
If you want certification rules planned into your device from the start, tell us about your device. You can also read how our engineering gates sequence the work.
Primary sources
All pages below were accessed on 2026-10-31. Rules and pages change, so confirm the text on the live pages.
- eCFR, 47 CFR 15.212, Modular transmitters: https://www.ecfr.gov/current/title-47/part-15/section-15.212 (accessed 2026-10-31)
- eCFR, 47 CFR 2.1043, Changes in certificated equipment: https://www.ecfr.gov/current/title-47/part-2/section-2.1043 (accessed 2026-10-31)
- eCFR, 47 CFR 2.964, Pre-approval guidance: https://www.ecfr.gov/current/title-47/part-2/section-2.964 (accessed 2026-10-31)
- eCFR, 47 CFR 2.1033, Application for certification: https://www.ecfr.gov/current/title-47/part-2/section-2.1033 (accessed 2026-10-31)
- eCFR, 47 CFR 15.19, Labeling requirements: https://www.ecfr.gov/current/title-47/part-15/section-15.19 (accessed 2026-10-31)
- Bluetooth SIG, Qualify a product: https://www.bluetooth.com/develop-with-bluetooth/qualify/ (accessed 2026-10-31)
- Bluetooth SIG knowledge base, QDID and Declaration ID display requirements: https://kb.bluetooth.com/hc/en-us/articles/360049492911 (accessed 2026-10-31)
Planning a device like this? Tell us what it needs to do. A Duobay engineer replies within 1 business day. Send a project brief →