Why does every wireless technology have its own certification body?

Because two different systems are running at once and they answer different questions. Regulators ask whether the radio may lawfully transmit in a given country: the right band, the right power, no harm to other users. That question is answered once per market by a public authority, under the RED in Europe or the relevant FCC part in the United States. Industry alliances ask a separate question: does this product actually interoperate with the rest of the ecosystem, and may it therefore carry the name. Bluetooth SIG, Wi-Fi Alliance, the Connectivity Standards Alliance and the others exist to answer the second question, and they own the trademarks that make the answer matter commercially.

Is alliance certification legally mandatory?

No, and that distinction is real: no government requires a Bluetooth Qualification or a Wi-Fi CERTIFIED listing. What makes it effectively unavoidable is trademark law rather than product law. The words Bluetooth and Wi-Fi, and their logos, are protected marks. Using them on a product, its packaging, its manual or its web page without a licence is trademark infringement, and the licence is conditioned on completing the programme. So a manufacturer is free to ship an uncertified 2.4 GHz radio, and free to describe it only in generic terms. In practice distributors, retailers and operators write the certification into their purchasing specifications, which closes the remaining gap.

Which one do I need first?

Regulatory first, in almost every case. It is the one that can stop the product being sold at all, it usually has the longest lead time because it may involve a notified body or a foreign test house, and its test reports frequently feed the alliance submission. Alliance programmes also tend to assume a stable, near-final design, whereas regulatory pre-compliance is useful much earlier. The exception is when an alliance programme constrains the hardware itself, for instance a required chipset, module or security element, in which case that constraint has to be known at design time even though the certification comes later.

Does using a pre-certified module remove the need for both?

It reduces the work on both sides but removes neither. A module carrying its own regulatory approval can let the finished product inherit that approval, subject to strict conditions on antenna, firmware and integration, and those conditions are where most of the arguments happen. On the alliance side, several programmes allow a qualified design or component to be referenced rather than retested, but the finished product must still be declared, listed and licensed under the manufacturer's own account before the brand may be used. Inheriting a module's radio approval never inherits the right to print a logo.

Where do operator programmes like PTCRB and GCF fit?

They are a third layer, applying to cellular products and driven by network operators rather than by regulators or technology alliances. An operator's concern is whether the device will behave correctly on a live network, so the tests cover protocol conformance and network interaction rather than spectrum legality or logo eligibility. A cellular product therefore commonly needs all three: regulatory approval per market, cellular certification through PTCRB or GCF, and in many cases an individual operator's own acceptance on top.

Wireless certification: the law vs the logo

Author Hugues Orgitello Last updated 29 August 2026 ~5 min read

Guide, understanding wireless certification

A wireless product does not go through one certification. It goes through two, and often three, run by bodies that have nothing to do with each other. The confusion this causes is the single most common way a first wireless project loses a quarter. This page separates the layers, explains which of them the law actually compels, and shows why the ones it does not compel are usually unavoidable anyway.

Two systems, running in parallel

Ask "is my Bluetooth product certified?" and the question has two answers, because two organisations with different powers are involved.

The regulator asks whether the radio may lawfully transmit here. Correct band, power within the limit, spurious emissions controlled, no harm to other spectrum users. This is public law. Fail it, and the product cannot be placed on the market at all. In the European Union it is the Radio Equipment Directive, 2014/53/EU; in the United States it is the relevant part of 47 CFR; elsewhere it is a national type-approval scheme, which is what most of the regional guides cover.

The technology alliance asks whether the product genuinely interoperates with everything else claiming the same name, and therefore whether it may use that name. This is private, contractual, and enforced through trademark rather than through product law.

The two are independent. A radio can be perfectly lawful and completely uncertified by any alliance. It can also be fully qualified by an alliance and illegal to sell, if nobody did the regulatory work.

Who runs the logo programme

Each technology has its own body, which is why the landscape looks so crowded.

Technology	Body	Guide
Bluetooth, BLE	Bluetooth SIG	Bluetooth SIG qualification
Wi-Fi	Wi-Fi Alliance	Wi-Fi Alliance certification
Zigbee, Matter	Connectivity Standards Alliance	Zigbee and CSA, Matter
Thread	Thread Group	Thread Group certification
LoRaWAN	LoRa Alliance	LoRaWAN certification
NFC	NFC Forum	NFC Forum certification
USB-C, USB4, USB PD	USB-IF	USB-IF certification
Qi, Qi2 wireless charging	Wireless Power Consortium	Qi and WPC
UWB	FiRa Consortium	UWB and FiRa
DECT, ULE, NR+	DECT Forum	DECT Forum certification
Wi-SUN	Wi-SUN Alliance	Wi-SUN Alliance

"Voluntary" is the wrong word

Alliance programmes are routinely described as voluntary, and read literally that is true: no statute obliges anyone to qualify a Bluetooth product. Taken as practical advice it is badly misleading, for two reasons.

The first is trademark. Bluetooth and Wi-Fi are protected marks, not generic descriptions. Printing either on a product, its box, its manual or its web page requires a licence, and the licence is granted only on completion of the programme. A manufacturer really is free to ship an uncertified 2.4 GHz radio, and really is free to describe it as "2.4 GHz wireless" and nothing more. Whether that product sells is a different question.

The second is the purchasing chain. Distributors, retailers and network operators write these certifications into their specifications. A product that cannot show the listing frequently cannot get onto the shelf, whatever the law says.

So the accurate framing is not voluntary versus mandatory. It is compelled by law versus compelled by contract, with much the same commercial result and very different consequences for getting it wrong. Missing regulatory approval is an offence. Missing an alliance listing is a broken deal.

The third layer: operators

Cellular adds one more. Network operators need confidence that a device will behave on a live network, which is neither a spectrum question nor a logo question. That is what PTCRB and GCF exist for, and many operators run an individual acceptance programme on top of those.

A cellular IoT product therefore commonly carries three certifications in parallel: regulatory approval per market, PTCRB or GCF, and named operator acceptance.

What order to do them in

Regulatory work comes first in nearly every project. It is the layer that can stop the product being sold outright, it carries the longest lead times, and its test reports often feed the alliance submission.

Alliance programmes generally assume a stable design and a near-final firmware build, so starting them early wastes money on retests. The exception is any alliance requirement that constrains the hardware itself, such as a mandated security element or a qualified chipset. Those must be known at design time even though certification happens much later.

Operator acceptance comes last, because it usually requires the other two to be complete.

What beginners usually get wrong

Assuming the module's certification covers everything. A pre-certified module can pass its regulatory approval to the finished product under strict conditions on antenna, firmware and integration. It never passes on the right to use a logo: the finished product must be declared and licensed under your own account.

Budgeting for one certification. Three parallel programmes, three fee schedules, three schedules to coordinate. A first-time project that budgeted for the regulatory line alone is the most common way this work overruns. See certification costs for realistic ranges.

Leaving the alliance work until after launch. Packaging, manuals and marketing pages all carry the logos, and they are printed long before shipping. The licence must exist before the artwork is committed.

Treating the technology name as a description. "Bluetooth compatible" on an unlicensed product is a trademark problem, not a marketing shortcut.

Key takeaways

Two independent systems apply, one public and one private, and a product usually needs both.
The regulator governs whether you may transmit; the alliance governs whether you may use the name.
Voluntary is the wrong word. Alliance programmes are compelled by trademark and by purchasing specifications rather than by statute.
Cellular adds a third layer, operator-driven, and it usually depends on the first two being finished.
Regulatory first. It gates market access, has the longest lead time, and feeds the other submissions.

Frequently asked questions

Why does every wireless technology have its own certification body?: Because two different systems are running at once and they answer different questions. Regulators ask whether the radio may lawfully transmit in a given country: the right band, the right power, no harm to other users. That question is answered once per market by a public authority, under the RED in Europe or the relevant FCC part in the United States. Industry alliances ask a separate question: does this product actually interoperate with the rest of the ecosystem, and may it therefore carry the name. Bluetooth SIG, Wi-Fi Alliance, the Connectivity Standards Alliance and the others exist to answer the second question, and they own the trademarks that make the answer matter commercially.
Is alliance certification legally mandatory?: No, and that distinction is real: no government requires a Bluetooth Qualification or a Wi-Fi CERTIFIED listing. What makes it effectively unavoidable is trademark law rather than product law. The words Bluetooth and Wi-Fi, and their logos, are protected marks. Using them on a product, its packaging, its manual or its web page without a licence is trademark infringement, and the licence is conditioned on completing the programme. So a manufacturer is free to ship an uncertified 2.4 GHz radio, and free to describe it only in generic terms. In practice distributors, retailers and operators write the certification into their purchasing specifications, which closes the remaining gap.
Which one do I need first?: Regulatory first, in almost every case. It is the one that can stop the product being sold at all, it usually has the longest lead time because it may involve a notified body or a foreign test house, and its test reports frequently feed the alliance submission. Alliance programmes also tend to assume a stable, near-final design, whereas regulatory pre-compliance is useful much earlier. The exception is when an alliance programme constrains the hardware itself, for instance a required chipset, module or security element, in which case that constraint has to be known at design time even though the certification comes later.
Does using a pre-certified module remove the need for both?: It reduces the work on both sides but removes neither. A module carrying its own regulatory approval can let the finished product inherit that approval, subject to strict conditions on antenna, firmware and integration, and those conditions are where most of the arguments happen. On the alliance side, several programmes allow a qualified design or component to be referenced rather than retested, but the finished product must still be declared, listed and licensed under the manufacturer's own account before the brand may be used. Inheriting a module's radio approval never inherits the right to print a logo.
Where do operator programmes like PTCRB and GCF fit?: They are a third layer, applying to cellular products and driven by network operators rather than by regulators or technology alliances. An operator's concern is whether the device will behave correctly on a live network, so the tests cover protocol conformance and network interaction rather than spectrum legality or logo eligibility. A cellular product therefore commonly needs all three: regulatory approval per market, cellular certification through PTCRB or GCF, and in many cases an individual operator's own acceptance on top.