In the industry, “IC certification” formally refers to ISED radio equipment approval – you apply through the SMS system to obtain an IC ID. ICES‑003 is a separate standard for interference‑causing equipment, following the SDoC (Supplier’s Declaration of Conformity) path – it is not part of the IC approval process.
1.1 What products require ISED approval?
ISED’s Radiocommunication Act covers any device that emits RF signals in Canada – Wi‑Fi, Bluetooth, cellular 4G/5G, NFC, UWB, millimetre‑wave radar, C‑V2X, and even low‑power intermittent transmitters like remote key fobs.
Pure receivers – GPS‑only, FM‑radio‑only – are exempt by default. However, if a module includes a Bluetooth debug transmit path and production firmware does not permanently disable RF emission, it is considered an intermittent transmitter and requires ISED approval. Conversely, if the debug port is hardware‑reserved but production firmware permanently disables transmission, you may submit a declaration to request exemption.
Do not assume that no antenna connector means it is not a transmitter.
1.2 How to recognise an IC ID
An ISED certificate number follows the format: IC: XXXXX‑YYYYY – the colon after “IC” is mandatory, the first five digits are the Company Number assigned by ISED, and the last five are the Unique Product Number (UPN).
RSS‑Gen Issue 5 specifies the colon format. Many products use a space instead – but ISED audits and customs have already rejected such cases. For new projects, use the colon.
2. SMS System Registration and Company Filing
2.1 Obtain an ISED Company Number
The first step is not testing – it is registration. Submit your company information on the ISED SMS website. Overseas manufacturers can register directly and apply for a Company Number independently – no need to borrow a local agent’s entity for IC ID filing. Many agents force clients to share – creating ownership risks later.
Registration review is manual – typically 3–10 working days, longer during peak seasons. Register at least two weeks before the project starts.
2.2 Legal role of the local agent
You can apply with your own account, but Canadian regulations require a Local Representative (LR) – responsible for regulatory liaison and document retention – when placing products on the Canadian market. The filing account holder and the LR can be two different legal entities.
The LR must have a formal signed authorisation agreement – not just a name on paper. They bear statutory responsibility for wireless compliance in Canada and are the direct contact for market surveillance. The agreement must clearly state the HVIN scope and applicable RSS standards – vague terms will be rejected by ISED audits.
3. Test Preparation – Do Not Skip
3.1 Determine the applicable RSS standards
ISED radio approval uses the RSS series. General devices start with RSS‑Gen plus band‑specific standards. Bluetooth and 2.4 GHz Wi‑Fi → RSS‑247; 5 GHz Wi‑Fi adds the DFS sections of RSS‑247.
Band distinction: traditional 5 GHz RLAN uses RSS‑247, but the newer 5.925–7.125 GHz band follows RSS‑248 – not RSS‑247. Do not assume all 5 GHz bands fall under RSS‑247.
EMC uses ICES‑003 – a separate SDoC process, not part of the SMS approval system – do not call it “IC test”. The current edition is Issue 7 – new projects should use it. Issue 7 adds Canada‑specific limits for wireless charging and high‑frequency spurious – not a simple copy of FCC Part 15‑B.
3.2 Choosing a test lab
ISED accepts reports from ISO 17025 labs under the ILAC‑MRA framework – the scope must cover the specific RSS standard numbers. ILAC alone is not enough – the report format must comply with ISED’s TR‑LRD specification – non‑compliant templates will be rejected.
Qualified domestic labs can issue ISED‑accepted reports – RF and EMC do not need to be sent to Canada. RSS‑102 (RF exposure) SAR assessment is more demanding – wearables have stricter multi‑posture MPE requirements than FCC – confirm that your lab has experience with ISED‑specific SAR.
3.3 Samples and documents
Submit at least 2–3 samples – firmware must be locked to the mass‑production version – no debug versions on the test bench. Technical documents: schematics clearly marking RF traces and antenna feed paths, antenna datasheets with gain/type for each antenna, BOM, and a draft compliance declaration.
The most frequently missed item is the antenna specification – internal and external antennas must be listed separately, and detachable antenna gain limits must be separately documented. Missing antenna documents mean the lab cannot run full radiated spurious tests.
4. Formal Testing
4.1 Conducted RF first
Conducted metrics – RF power, bandwidth, spurious – are the foundation. If any band is dirty, everything else fails. Only after conducted passes do you move to radiated – this is the practical order.
RSS‑247 frequency‑hopping devices have special requirements – channel occupancy time, hopping sequence, and bandwidth occupancy – domestic labs may have less experience – confirm the test software environment in advance.
4.2 Radiated spurious and DFS
Radiated spurious are run in an anechoic chamber – both antenna polarisations. ISED has strict chamber noise‑floor requirements – not every chamber meets the baseline.
5 GHz Wi‑Fi DFS radar detection follows RSS‑247 appendices – different from FCC DFS. You cannot directly transfer FCC DFS data – ISED uses independent parameters for pulse width, detection duration, and channel‑switch logic – that path does not work.
4.3 SAR and MPE RF exposure
Devices exceeding RSS‑102 exemption thresholds must undergo SAR or MPE assessment. Wearables are particularly challenging – missing multi‑posture test records will be rejected. ISED limits and test configurations are not identical to FCC – you cannot substitute FCC SAR reports.
4.4 ICES‑003 EMC testing
RF approval and ICES‑003 SDoC testing are independent – no mandatory order. Practically, it makes sense to stabilise RF first before running EMC, so labs often place EMC last. ICES‑003 Issue 7’s new wireless‑charging high‑frequency spurious tests are a frequent cause of returns in recent years – using an old issue will trigger a version‑upgrade request.
5. Submission, Review, and Feedback
5.1 SMS online submission
Once all test data and reports are complete, submit the formal application via the ISED SMS system. The HVIN (Hardware Version Identification Number) must exactly match the product nameplate – not a single character off. Emission type and frequency band descriptions must be precise – modulation and range.
5.2 Review timeline and resubmissions
ISED’s official target is 8–12 weeks – not a binding deadline. With complete documents and no obvious technical defects, you can expect 6–8 weeks. Multi‑band projects with SAR and DFS typically take longer. Each resubmission round adds 1–2 weeks.
Most common resubmission reasons: inconsistent antenna‑gain declarations, outdated RSS standard versions, using an old ICES‑003 edition, or inaccurate French‑translation compliance statements. Double‑check these before submission – it saves significant time.
6. After Certification – Ongoing Obligations
6.1 Label placement
The IC ID must be on the product body – indelible and legible. Very small devices may apply for label exemption – but then you must have an electronic label and print the ID on the outer packaging. The electronic label must be directly viewable in the user menu – not hidden in engineering mode, encrypted, or password‑protected.
6.2 Changes – how to handle
ISED change classification has four tiers:
·C1PC – mildest – only label, packaging, or manual text changes that do not affect electrical/RF performance. HVIN changes are not C1PC.
·C2PC / C3PC – require difference testing.
·C4PC – requires a new IC ID – for RF chip changes, major antenna redesign, or RF board re‑layout.
Firmware changes – be very careful. UI/indicator‑logic changes do not require a new ID. But if firmware changes transmit power, operating bands, or modulation – that is a substantive RF change and requires a change assessment – depending on scope, you may need difference testing or even full retesting – do not assume a simple C3PC will suffice; severe cases fall under C4PC.
6.3 Document retention and market surveillance
ISED’s baseline is to retain records for at least 5 years from the last batch placed on the Canadian market. SAR/MPE exposure documents are high‑risk – keep them permanently, though no statutory “permanent retention” clause exists.
ISED has the right to request full documentation from the Canadian importer within 30 days during audits – if the agent cannot be reached or documents are not available, the IC ID will be frozen.
For ISED IC certification, contact BlueAsia at 13534225140 (King) or king.guo@cblueasia.com.
相关新闻
