Routers, mesh systems and switches: multi-band radio certification plus telecom registration schemes that target network gear specifically.
Routers concentrate the hardest part of radio certification: multiple bands (2.4, 5, sometimes 6 GHz) with region-specific rules per band, all of which must appear in the documentation and firmware. A router quoted for 2.4 GHz only is an incomplete scope.
Network equipment also attracts telecom-specific registration in several markets - India's MTCTE in addition to WPC approval, for example - which consumer gadget certifications never touch.
| Market | Typical requirements | Notes |
|---|---|---|
| United States | FCC ID certification for every band and mode (2.4/5/6 GHz); RF exposure (MPE); safety reports to UL 62368-1 framework often requested by retailers | 6 GHz (WiFi 6E) has its own rule sections - declare band support precisely |
| European Union | RED: EN 300 328 (2.4 GHz), EN 301 893 (5 GHz), 6 GHz standards as applicable; EMC, safety, RoHS | All supported bands and DFS behavior must be covered and match the firmware |
| India | WPC ETA for the radio; MTCTE mandatory testing and certification for network/telecom equipment | MTCTE is separate from WPC - routers often need both |
| Japan / Korea | TELEC (MIC) and KC radio approvals | Per-band rules differ from FCC/RED - plan separate reports |
Certifying a router or mesh system with several bands? Send the band/mode matrix and target markets - we will quote the full matrix, not just the easy bands.
Band count and mode count. A router may operate on three bands with multiple channel widths, DFS and mesh modes, and every combination must be declared and tested. A single-band Bluetooth device is a fraction of the matrix.
MTCTE is India's mandatory testing and certification regime for telecom equipment, run by TEC alongside WPC radio approval. Network equipment such as routers generally falls within its scope - plan it together with WPC, not after.
Changes that alter radio behavior (band support, power, antenna selection) do. Pure UI firmware changes usually do not. Define your change-control process before the grant, not after the first audit question.