Summary: FCC documentation should be mapped from the finished device, not from a product name or a laboratory report title. Identify every intentional transmitter, unintentional radiator, receiver, antenna, and operating mode, then map the complete product to the applicable FCC rule part, authorization procedure, testing path, labeling requirements, and responsible party. This reference page explains the evidence boundary between SDoC, Verification, and Certification, and provides a practical review sequence for modules, e-labels, product pages, and change control. The applicable rule, grant conditions, and current OET guidance remain controlling for each SKU.
1. Start with the device, the rule part, and the authorization path
Part 15 distinguishes intentional radiators, unintentional radiators, and incidental radiators. An intentional radiator is a device that intentionally generates and emits radio-frequency energy by radiation or induction. An unintentional radiator may generate RF energy while its digital circuits operate, but is not designed to emit it by radiation or induction. A product should not be classified by one slogan such as “it has a wireless chip” or “it operates above 9 kHz.” Review the complete radio design: transmitters, receivers, frequency bands, power, antennas, simultaneous modes, firmware controls, intended use, and any licensed-service or product-specific rule part.
The authorization procedure is also not a universal “light, medium, and strict” ladder. Part 2 Subpart J and the applicable technical rule determine the route. Many Part 15 intentional transmitters use Certification, but “every transmitter always follows Certification” is not a substitute for checking the rule and the device. Conversely, the presence of a digital circuit does not allow an SDoC to cover a transmitter that was never mapped and tested.
2. Evidence differences between SDoC, Verification, and Certification
| Procedure | Core evidence | Review focus |
|---|---|---|
| SDoC | The responsible party makes a Supplier’s Declaration of Conformity based on measurements and other steps required by the rules, and supplies the required compliance information. | Confirm that the rule part permits SDoC; align the responsible party, representative sample, test report, declaration wording, and user information. SDoC does not create an FCC ID. |
| Verification | The manufacturer or importer performs the measurements or other steps needed to show compliance and keeps supporting records. | Use it only where the current rule still permits Verification. Do not mix Verification, SDoC, and legacy “Declaration of Conformity” labels in the same file set. |
| Certification | The application and test data follow an FCC-recognized TCB/FCC equipment-authorization route. Once granted, the authorization is associated with an FCC ID. | Check the FCC ID, applicant, model, equipment class, rule sections, antennas, and RF-exposure conditions. A finished-device change cannot be justified merely by the title of a module or an older grant. |
Laboratory competence and authorization roles are separate. FCC materials explain that laboratories may perform testing used for Certification, but an ISO/IEC 17025 certificate by itself does not allow a laboratory to issue an FCC Grant. Grant review and issuance belong to the TCB/FCC equipment-authorization process. OET KDB publications are staff guidance; they do not replace the rules, and example figures in a KDB document should not be copied into every product as universal legal thresholds.
3. Map the finished product: one report cannot cover an unidentified transmitter
| Product or function | First questions | Evidence action |
|---|---|---|
| Bluetooth, Wi-Fi, Zigbee, Thread, LoRa, or other transmitters | What are the bands, modulation, maximum power, antennas, simultaneous modes, and applicable rule parts? | Put each transmitter in a product-level matrix. Confirm Certification, FCC ID, RF-exposure, and software-configuration requirements where applicable. A Part 15B digital-device report cannot replace authorization for an unreviewed transmitter. |
| Cellular, satellite, medical, or other service-specific radio | Does the product also fall under Parts 22, 24, 27, 25, 95, or another service-specific rule? Does the finished-device grant list every radio function? | Map each service, band, power, bandwidth, exposure, and labeling requirement separately. A Wi-Fi FCC ID does not prove that a cellular or other radio in the same product is authorized. |
| Wireless power transfer or near-field communication | Does the transmitter communicate control, authentication, or data between the power transmitter and the powered device? Which Part applies? | Use the OET Wireless Power Transfer guidance, KDB 680106, as an entry point. WPT equipment that transmits information generally needs to be evaluated under the applicable intentional-radiator rules; an AC-DC power-supply SDoC is not a complete answer. |
| Receive-only or digital-only equipment | Is there truly no return link, pairing, ranging, location, telemetry, or other transmit mode? | Confirm the receiver, digital section, and other applicable rules. Keep a block diagram, firmware feature description, test modes, and model scope so “receive-only” is not based only on sales copy. |
4. A module FCC ID is not automatically a finished-device FCC ID
For a pre-certified module, start with the module’s Grant Detail, installation instructions, and host-integrator responsibilities. KDB 996369 currently points to the Module Certification Guide, Module Q&A, OEM Manual, Module Integration Guide, and Split Module guidance. The module’s approval type, permitted antennas and host conditions, shielding and power arrangements, RF-exposure limits, labeling method, and any host-level filing must be checked against the actual Grant and the applicable rules.
A host that adds another transmitter, changes the antenna or RF path, changes power or firmware controls, exceeds the installation conditions, or cannot show that the integrated product remains representative of the authorization cannot simply print the module FCC ID on the finished product. The responsible party and TCB must determine whether the change is a permissive change, can reference existing data, or requires finished-device Certification. There is no universal “80%,” “±0.5 dB,” or fixed-fee rule that replaces review of the actual Grant.
5. Labels, user information, and product-page wording
For a Certification product, the FCC ID, model, and label location should match the Grant, label artwork, and production unit. Part 15 devices also need the applicable user statement. 47 CFR §15.19 specifies different statements and explains how information may be supplied when a device is too small for the required text and has no usable display. Marketing language such as “FCC SDoC ID” or “FCC approved” should not replace the required wording. For e-labeling, review the current FCC KDB 784748 guidance item by item: the compliance information must be accessible through the device’s own compliance interface; a companion-phone app is not a universal substitute for every product. The applicable rule, device design, and authorization documents control.
Keep product pages, packaging, manuals, and platform fields precise about the difference between “tested,” “SDoC,” “Certification,” and “FCC ID.” Do not present a laboratory test as an FCC authorization, describe a module ID as proof that the complete product is certified, or make unsupported promises about pass rates, customs clearance, listing outcomes, penalties, or fixed review times.
6. Pre-launch evidence checklist
- Product decomposition: BOM, schematic, RF chips, antennas, bands, power, modulation, simultaneous modes, and firmware-lock records.
- Rule mapping: target market, applicable FCC Parts, equipment class, authorization procedure, and any RF-exposure or software-configuration review.
- Document alignment: test reports, declaration, Grant, FCC ID, model suffixes, applicant/responsible party, antennas, and label artwork.
- Module integration: module grant type, installation limits, host environment, antenna and power changes, change route, and TCB conclusion.
- Production and page review: inspect randomly selected finished units against the label, manual, firmware, and product-page statements.
- Change control: reassess authorization impact when the chip, antenna, power, band, firmware, enclosure, model, or supplier changes, and retain version records.
Boundary note: This is an evidence-review framework. It does not state that any SKU is authorized, importable, saleable, or accepted by a platform. Products with multiple radio standards, integrated modules, near-field power/data transfer, or service-specific bands require item-by-item review against current FCC rules, relevant OET KDB guidance, test data, and the final Grant.
Sources and review entry points
- 47 CFR Part 15 Subpart A: device definitions, general conditions, and Part 15 labeling information.
- FCC OET Knowledge Database: KDB is OET guidance and must be used with the specific rule and device facts.
- KDB 996369: module certification and host-integration entry point.
- KDB 680106: Wireless Power Transfer authorization guidance entry point.
- FCC Major Guidance Publications: includes the KDB 784748 labeling and user-information guidance entry.
- FCC TCB Search and EAS data description: entry points for reviewing TCB, grantee, and public authorization records.
