What Does a Pre-Certified Radio Module's Certification Cover — and What Doesn't It?

Detailed Explanation

Australian hardware engineers building connected IoT products routinely use pre-certified radio modules — ESP32-WROOM modules, Nordic nRF52840 modules, Quectel cellular modems — and reasonably assume that a module already in the ACMA compliance labelling database substantially reduces the compliance burden. It does, in one specific way: it removes the need to certify the radio transmitter's intentional emissions from scratch. But it does not eliminate the need for EMC testing of the complete product.

Understanding exactly where the certification boundary lies is the most common compliance knowledge gap among Australian IoT product developers. This page covers what the module's certification actually covers, what it does not cover, and what you must still do before placing the complete product on the Australian market. For the end-to-end RCM certification process — from standards selection, NATA lab testing, and Declaration of Conformity through to ACMA registration — that page covers the complete picture.

What the Module Certification Covers

A radio module that appears in the ACMA compliance labelling database, or that has been certified under the Radiocommunications Act 1992, has been assessed for its intentional radio transmitter emissions — the signals the radio deliberately generates and emits to communicate.

Specifically, the certification covers:

The intentional radio transmissions from the module's own RF front-end. For an ESP32-WROOM-32E, this means the 2.4 GHz Wi-Fi and Bluetooth signals. For an nRF52840 module, this means the BLE 5.0 transmissions. For a cellular module such as the Quectel SIM7080G, this means the LTE-M and NB-IoT transmissions.

Under the specific test conditions of the module's certification. The module was tested on the module manufacturer's reference host board — a specific PCB design with defined ground plane dimensions, specific component values, specified antenna placement, and specific operating firmware. The certification is valid under those conditions.

Only the module's own radio output. The test confirms that the intentional radio signals are within the power and spectral mask limits set by the relevant standards under the Radiocommunications (Electromagnetic Compatibility) Standard 2017.

This certification is what allows the module to be incorporated into a product without requiring the responsible supplier to separately certify the radio transmitter's intentional signals.

What the Module Certification Does Not Cover

The module certification is scoped narrowly to the module's radio transmitter under the module's test conditions. It does not cover:

Non-intentional electromagnetic emissions from the host board. When the module is placed on your PCB, your circuit generates emissions entirely separate from the radio transmitter:

• MCU clock harmonics — a microcontroller running at 240 MHz generates harmonic emissions at integer multiples of that frequency, potentially falling across the CISPR 32 radiated emissions test range (typically 30 MHz to 1 GHz for Class B products)
• Switching power supply noise — the switching node of a buck or boost converter on your host board generates conducted and radiated noise at the switching frequency and its harmonics, typically in the 100 kHz – 30 MHz conducted range and above
• Crystal oscillator emissions — the crystal fundamental and its harmonics are among the most common emission peaks observed during pre-compliance scans
• High-speed digital buses — I2S, SPI, MIPI DSI, or fast UART lines running at multi-MHz rates generate radiated emissions from trace-acting-as-antenna effects
• Cable common-mode noise — cables attached to your product (USB, serial, power, sensor wires) pick up common-mode noise from the board and radiate in the conducted and radiated test ranges

Your obligation as the responsible supplier. The module manufacturer's ACMA registration makes them the responsible supplier for that module as a product. When you incorporate the module into your product and supply the complete product to Australian customers, you become the responsible supplier for the complete product. Your Declaration of Conformity must cover the complete product — not the module's existing registration. For the full documentation requirements, see Declaration of Conformity requirements for RCM.

Why the Complete Product Still Needs CISPR 32 Testing

CISPR 32 (adopted by Australia as AS/NZS CISPR 32) sets limits on electromagnetic emissions from multimedia equipment and commercial electronics. The standard tests the complete system as supplied — the full assembled product including all attached cables, in normal operating configuration.

The test covers two separate emissions paths (see conducted and radiated emissions for a full explanation):

• Conducted emissions (150 kHz to 30 MHz): Measured at the product's power input via a Line Impedance Stabilisation Network (LISN). Captures noise injected back into the supply from switching power conversion.
• Radiated emissions (30 MHz to at least 1 GHz): Measured in a semi-anechoic chamber or open area test site. Captures electromagnetic fields radiated from the PCB and cables.

The pre-certified module's intentional radio transmissions at 2.4 GHz sit above this radiated emissions test window, and are covered by the radio certification. What CISPR 32 catches are the non-intentional emissions from host board circuitry — exactly the category the module certification does not cover.

The responsible supplier's Declaration of Conformity must declare conformity of the complete product against the applicable CISPR standard. It references the accredited test report for the complete product — not the module's ACMA registration number.

Compliance Status by Module Type

The principle is consistent across all pre-certified module types, though regulatory details vary:

Wi-Fi / BLE combination modules (ESP32-WROOM-32E, ESP32-MINI-1, ESP32-S3-WROOM-1)

• What the module's certification covers: intentional 2.4 GHz Wi-Fi and BT/BLE emissions, registered in the ACMA compliance labelling database
• What the host board still needs: CISPR 32 testing of the complete product; ACMA compliance labelling registration for the complete product as a separate entry under the host product's responsible supplier
• Key integration requirement: follow Espressif's PCB layout guidelines for antenna keepout zone and ground clearance under the module antenna area

Bluetooth Low Energy modules (Nordic nRF52840 module variants, u-blox NINA-B31, Actinius Icarus)

• What the module's certification covers: BLE 5.0 intentional transmitter emissions, registered with ACMA
• What the host board still needs: CISPR 32 testing of the complete product; ACMA registration as responsible supplier
• Note on the bare nRF52840 chip: the nRF52840 SoC itself is not a pre-certified module — if you use the bare chip with your own antenna design, no modular radio certification applies, and full radio certification under the Radiocommunications Act is required

Cellular IoT modules (Quectel SIM7080G, SIM7600, u-blox SARA-R410M, Murata Type 1SC)

• What the module's certification covers: PTCRB and ACMA certification for the cellular bands (typically LTE-M Band 28, NB-IoT, and any additional bands the module supports)
• EMC standard for the host board: CISPR 32 for commercial multimedia equipment or IEC 61000-6-4 for industrial equipment — the applicable standard depends on product category; see which Australian EMC standard applies to your product for the category decision framework
• What the host board still needs: formal EMC testing under the applicable standard; ACMA compliance labelling registration as responsible supplier for the complete product

LoRa / LPWAN modules (RFM95W, u-blox SARA-R412M, Murata LPWAN modules)

• What the module's certification covers: ACMA registration for the AU915 frequency band (verify this for each specific module — not all LoRa modules are ACMA-registered for AU915 specifically)
• What the host board still needs: CISPR 32 testing; ACMA registration for the complete product

For the broader question of which wireless protocol to use for an Australian IoT product — including regulatory notes for each option — see Bluetooth vs Wi-Fi vs LoRa vs Zigbee: Which Protocol Should You Use?.

Raspberry Pi Compute Module (CM4, CM5)

• What the module's certification covers: ACMA registration for the integrated 2.4 GHz Wi-Fi (802.11ac) and Bluetooth 5.0 radio in the BCM2711 SoC (CM4), under Raspberry Pi's reference conditions
• What the host board still needs: CISPR 32 testing of the complete product (CM4 + custom carrier board + enclosure); ACMA compliance labelling registration for the complete product, with the carrier board designer or product manufacturer as the responsible supplier
• Key difference from pure radio modules: The CM4 is a full compute module — the custom carrier board adds DDR memory buses, PCIe, HDMI, MIPI interfaces, and switching regulators that generate substantial non-intentional emissions well beyond what a simple radio module introduces. Budget accordingly for pre-compliance scanning and formal CISPR 32 testing. For carrier board design and certification scope in detail, see Should You Use the Raspberry Pi CM4 in a Product?

The Reference Host Board Condition

The module's radio certification was performed by the module manufacturer on a specific reference board — typically a simple evaluation PCB designed to demonstrate the module's radio performance under defined conditions. The reference board specification states:

• Ground plane dimensions and the required clearance below and around the antenna
• PCB layer stackup
• Keepout zones: areas where no copper fill, traces, or components are permitted near the antenna
• Operating firmware and test mode configuration

When your host PCB differs from the reference conditions — as most production designs do — the module's radio performance on your board may differ from what the datasheet specifies. Most test labs evaluate radio performance separately from CISPR compliance testing, but integration differences can affect whether the module remains within its certified parameters:

• Antenna keepout violations — copper fills, traces, or components within the required keepout zone can detune the antenna and alter the module's radiation pattern or effective radiated power
• Ground plane changes — modules with PCB trace antennas typically require a specific ground plane clearance below the antenna; reducing it significantly can shift the antenna's resonant frequency
• Metallic or metallo-plastic enclosures — a metallic enclosure placed close to the antenna can detune it; module datasheets typically note when re-testing is recommended in enclosed configurations

These considerations do not eliminate the need for CISPR 32 testing, but they reinforce why following the module manufacturer's RF PCB layout guidelines for the antenna section is essential — both for radio performance and to remain within the conditions the module's certification was validated under.

The Practical Compliance Path

For a responsible supplier building an Australian IoT product using a pre-certified radio module, the compliance steps are:

1. Confirm the module is in the ACMA compliance labelling database. Search the ACMA register to verify the specific module part number appears and that the registration is active. A module with CE or FCC certification only — without an ACMA registration — is not pre-certified for the Australian market.

2. Design the host board following the module's integration requirements. Follow the module datasheet's PCB layout guidelines: antenna keepout zone, ground clearance, required layer stackup near the module. This preserves the module's radio performance and ensures the host board integration does not invalidate the module's certification.

3. Conduct pre-compliance EMC scanning on the complete product. Before booking formal NATA-accredited testing, use a near-field probe and spectrum analyser to identify dominant emission sources on the host board. This step catches the switching regulator harmonic, the MCU clock radiation, or the cable coupling issue before it causes a formal test failure. See how to conduct EMC pre-compliance testing for the procedure and equipment needed.

4. NATA-accredited CISPR 32 testing on the complete product. The formal test, conducted by a NATA-accredited laboratory, produces the test report that supports the Declaration of Conformity. It covers conducted emissions (150 kHz – 30 MHz) and radiated emissions (30 MHz – at least 1 GHz) for the complete assembled product including all cables.

5. Prepare the Declaration of Conformity for the complete product. The DoC declares that your product — identified by its own product name and model number — conforms to AS/NZS CISPR 32. It references your NATA-accredited test report, not the module's ACMA registration number. It identifies you as the responsible supplier with an Australian or New Zealand address.

6. Register the complete product in the ACMA compliance labelling database. Your complete product registration is a distinct entry in the ACMA system with you as the responsible supplier. The module's existing database entry is separate and remains the module manufacturer's registration.

7. Apply the RCM mark to the product and its packaging.

Pre-Certified Module vs Custom Radio Design

Using a pre-certified module is a deliberate choice with compliance implications:

Pre-certified module: Radio transmitter certification is already complete. The host board requires CISPR 32. The total compliance path is substantially shorter — typically 4–8 weeks from pre-compliance scan to RCM marking, depending on lab availability and whether any design iterations are needed.

Custom radio design (bare SoC + your own antenna): The Radiocommunications Act 1992 requires full radio certification by a Recognised Testing Laboratory (RTL) accredited by ACMA. This is a separate, more extensive process than CISPR 32 — involving transmitter power, spectral mask, spurious emissions, and carrier frequency accuracy testing — and can add 4–12 weeks and significant cost. The total compliance burden is substantially higher.

For most commercial IoT products at typical volumes, using a pre-certified module is the correct architectural choice from a compliance perspective. It shifts the radio transmitter certification risk to the module manufacturer and compresses the compliance timeline.

Practical Examples

Commercial BLE sensor using an ESP32-MINI-1: The ESP32-MINI-1 is registered in the ACMA compliance labelling database. The sensor board also has a 3.3 V buck converter, an I2C sensor, and a USB-C charging port. The buck converter's switching frequency and harmonics are the dominant expected emission source. Pre-compliance scanning identifies two peaks above CISPR 32 Class B conducted limits. The designer increases input-side decoupling and reduces the switching node copper area, bringing the peaks within limits. The formal NATA-accredited CISPR 32 test passes. The Australian company (responsible supplier) prepares a DoC declaring AS/NZS CISPR 32 compliance and registers the complete product in the ACMA database.

Industrial data logger using a u-blox SARA-R410M cellular module: The SARA-R410M has ACMA certification for LTE-M/NB-IoT. The data logger qualifies as industrial equipment — IEC 61000-6-4 applies rather than CISPR 32. The host board has a two-stage switching power chain. Pre-compliance scanning finds conducted emissions above IEC 61000-6-4 limits at the first switching stage. Adding an LC filter on the power input resolves the issue. The Australian importer (responsible supplier) registers the complete product in the ACMA database and prepares a DoC referencing the IEC 61000-6-4 test report.

Design Considerations

• Verify the specific module part number in the ACMA database before committing to a component. Not all radio modules carry ACMA registration — some have CE or FCC certification only. Module families often include variants, some ACMA-registered and some not. Check the exact part number, not just the product family.
• Follow the module's integration guidelines precisely for the antenna section of your PCB. A single copper fill inside the keepout zone can shift the antenna's resonant frequency enough to alter the module's radiation pattern. This is both a radio performance issue and a question of whether you remain within the conditions under which the module was certified.
• Budget time for CISPR 32 testing regardless of module selection. Using a pre-certified module does not compress the total EMC compliance timeline to zero. Formal testing (pre-compliance scan, board iterations, accredited lab test, report) typically takes 3–8 weeks from first pre-compliance scan to completed formal test report, depending on lab scheduling and whether design iterations are required.
• Complete ACMA registration before first supply in Australia. ACMA compliance labelling registration for the complete product must be completed before the product is supplied in Australia. Complete the CISPR 32 test and prepare the DoC first, then register — do not supply product while registration is in progress.
• For products targeting both the Australian and European markets, check whether the module carries both ACMA and CE (Radio Equipment Directive) certification. Where the test standards align (CISPR 32 / EN 55032), shared test data may be possible for the host board EMC test. Zeus Design's engineering team can help scope the compliance and testing strategy for Australian IoT products.

Common Mistakes

• Using the module's ACMA database entry as the complete product's compliance evidence. The module's registration belongs to the module manufacturer. The responsible supplier of the complete product must register the complete product separately. Supplying a product in Australia using only the module's registration, without a DoC referencing the complete product's own CISPR 32 test, is a compliance failure.
• Omitting CISPR 32 testing because the module is pre-certified. This is the central misconception. The module's certification scope is limited to its intentional transmitter emissions. CISPR 32 tests non-intentional emissions from the host board — a different test covering different emission types.
• Assuming the module integration guide replaces CISPR 32. Module integration guides describe PCB layout practices to preserve the module's radio performance. They do not constitute evidence of CISPR 32 compliance for the host board's non-intentional emissions.
• Not verifying the module is ACMA-registered for Australia specifically. CE marking and FCC Part 15 certification are not equivalent to ACMA registration. An EU-certified module requires separate ACMA registration before use in an Australian product. Verify the ACMA database, not the module datasheet's "regulatory approvals" list, which may show approvals for markets other than Australia.
• Violating the module's antenna keepout zone in the host board layout. The keepout zone is specified with exact dimensions in the module datasheet. Copper fills, traces, or components inside this zone can significantly alter antenna performance and potentially invalidate the conditions under which the module was certified.