For wireless products exported to Canada, the most-asked question is how long to get the certificate. There is no single number; the cycle depends on complexity and whether the first round passes. The structure is regular, so breaking it down by phase beats trusting a vague "about four weeks".
Wireless vs non-wireless are different things
After the 2016 agency reorganisation, the old IC certification merged into ISED, but the label still keeps the legacy IC:XXXXX-YYYYY format, which is officially accepted — no need to change it.
(1) Wireless transmitters take an IC ID, fall under the RSS series, count as Category I, and uniformly follow Certification, issued by ISED's engineering bureau or a recognised CB/FCB.
(2) Non-wireless EMC-only products follow ICES-003 type SDoC, with a short cycle — usually one to two weeks for the report.
Wireless has no third Verification path
Category I intentional radiators have only Certification. Verification is old history; now intentional radiation follows Certification, while unintentional radiation in Category II follows SDoC. Wrong mode choice costs money or wastes waiting.
How to match the standard
RSS-247 is the core for wireless LAN, under Category I. DFS follows RSS-247's own clauses; methodologically ISED references FCC KDB 905462 and ETSI EN 301 893 (5600–5650 MHz restricted to ETSI), not a single document. The procedure references ANSI C63.10.
2. The clock does not start on sample submission day
The Company Number must exist first
First-time applicants request a Company Number from ISED; it is the IC ID prefix. Most online approvals take one or two business days, but manual review stretches it — not everything is one or two days. Later products share this prefix; without it you cannot even submit.
A local agent is a hard prerequisite
Foreign companies must appoint a Canadian local agent to receive official notices and liaise with the regulator; the information goes into the application. The agent must have a physical Canadian address verifiable by the authority; a pure-email agent with no physical address is rejected outright. Finding the agent, signing authorisation and preparing the address all take real time.
Sort out product models first
ISED has explicit rules for multiple marketing models (PMN) under one hardware version (HVIN): each PMN is listed separately, not crammed into one field with commas or pauses. Multiple PMNs under one HVIN go through a Family application submitted together — not separate single-model filings, and not model lines split across spreadsheet rows. Mishandle this layer and it bounces back, commonly costing one to two weeks of rework.
3. The time accounts for four phases
Preparation, one to two weeks
Define classification and standard, prepare technical files — schematics, PCB layout, block diagram, BOM, antenna specification, bilingual (English/French) user manual, and photos. The bilingual manual is most underestimated; machine-translated compliance statements are often non-compliant and bounce back, costing real time.
Testing, two to four weeks
This is the big chunk. Low-risk with few items takes one to two weeks; ordinary Bluetooth/Wi-Fi running full RF plus EMC takes two to three weeks; adding DFS or RF exposure assessment adds three to five days. The lab must be ISED-recognised; new applications use the current ANSI C63.10, old reports are rejected; existing derivative changes with unchanged RF hardware can reuse old-standard reports.
Submission and review, two to three weeks
After testing, the certification body compiles and submits. Review watches consistency closely; mismatched parameters or wrong model format bounce back directly.
Rework is the biggest variable
Re-test after fixes typically compresses to about half the original — a lab rule of thumb, not a regulation; some failures require a full re-test of the complete set, close to the initial duration. Specifically:
① EMC fail — swap filters, adjust shielding.
② SAR exceedance — adjust antenna and transmit power.
③ Document bounce — re-submit with consistent wording.
Spending an extra one to two weeks on rework is common.
4. Situations that slow the cycle
Standard change colliding with the project
A mandatory standard change means projects straddling the node re-test to the new version. Confirm the current valid version with the lab upfront to avoid this.
Added-band testing
Canada has adjusted Wi-Fi open bands; products with newly opened bands run DFS dynamic frequency selection to avoid radar, adding extra test days.
RF exposure for body-worn devices
Body-worn products like phones and smartwatches require RF exposure assessment. Methods split into SAR measurement and MPE calculation; body-worn usually does SAR, some use MPE — not everything does SAR measurement. Scope requirements keep updating, so plan early.
Inconsistent document wording
Spec sheet, manual, application form and test report parameters not matching is a high-frequency bounce. Verify item by item before submission; it saves more time than post-hoc supplements.
5. Practical ways to compress the cycle
Reuse FCC test data
FCC and ISED are not directly mutually recognised, but under the US–Canada APEC-TEL MRA framework, FCC reports from an FCB that meets conditions can be accepted by ISED: the body must hold both FCC and ISED recognition, also do the Canadian-band difference analysis and add the difference items; independent requirements like DFS/AFC cannot be replaced by FCC data. Copying directly gets rejected; doing it properly saves one to two weeks.
Run a design review first
Before formal submission, hand schematics, PCB layout and BOM to the intended lab for a paid design review; engineers flag incomplete component certification, likely EMC failures and SAR exceedance risks in advance. Spending days buys weeks later — worth it.
Lock the schedule early
Lab schedules tighten in peak season; book the slot two to three weeks ahead. Lock it at project start rather than jumping the queue later.
Keep the sample consistent with mass production
Submitting a modified engineering sample yields invalid data; the sample must be pre-mass-production with final firmware. Later changes to RF-related firmware parameters need change filing; UI-only upper-layer changes do not.
6. Certificate validity, stated upfront
The IC ID certificate itself has no expiry; with unchanged RF hardware and firmware it stays valid indefinitely, unlike systems that periodically reissue. Clients often mistake it for renewal every few years; what actually needs handling is standard change or change filing, not certificate expiry.
BlueAsia handles wireless certification and helps clients align ISED, FCC and other North American approvals in one plan so the schedule stays predictable.
Contact: King Email: king.guo@cblueasia.comAddress: Building C, Hongjingda Industrial Park, No. 107 Beihuan Road, Shiyan Street, Bao'an District, Shenzhen, China BlueAsia delivers more than service!
相关新闻
