Bringing Your Device to North America: What European Tech Companies Get Wrong
FCC is just the start. European tech companies entering North America face ISED, FDA, FAA, PTCRB, carrier approvals, and dual-use export controls. Here's how to navigate without costly surprises.
By Paal Selnaes, Norseman Projects Ltd
FCC authorisation is the one most European tech companies know they need. It is also roughly a quarter of the actual regulatory surface for a connected device entering the North American market. The rest — ISED in Canada, FDA for anything touching health, FAA for anything that flies, PTCRB and carrier approval for cellular products, and EAR/ITAR for dual-use technology — tends to surface late, cost more than anticipated, and delay launches in ways that could have been avoided with earlier planning.
The Full Regulatory Stack
Depending on your device category, target market, and intended application, your product may need to satisfy some or all of the following. The interactions between them — not any single requirement — are where projects typically stall.
| Body / Standard | Scope | Status |
|---|---|---|
| FCC | Radio frequency emissions — intentional and unintentional radiators, RF exposure (SAR), modular approvals | Required |
| ISED (Canada) | Canadian radio and terminal equipment certification — separate from FCC, distinct filing process | Required |
| PTCRB | Cellular protocol conformance testing for 3GPP devices on US and Canadian carrier networks | Required |
| Carrier Approvals | AT&T, T-Mobile, Verizon device approval programmes — queue-dependent, not controllable by applicant | Required |
| FDA | Medical devices, radiation-emitting electronics, digital health software with wellness or clinical claims | Conditional |
| FAA / Part 107 | Unmanned aircraft systems — Remote ID compliance, Declaration of Conformance or type certification | Conditional |
| UL / ANSI Safety | Electrical safety standards for powered devices — often required by retailers and enterprise procurement | Conditional |
| EAR / ITAR | Export controls for encryption, dual-use RF technologies, precision sensors, and defence-relevant capabilities | Situational |
⚠ Where Projects Typically Stall
The most common — and costly — failure mode is not missing a single certification. It is discovering regulatory overlap late in development: a health-adjacent wearable that triggers FDA scrutiny, a drone payload that requires both FCC and FAA coordination, or a dual-use RF module that creates export control exposure nobody anticipated at architecture stage. These are not edge cases. They are patterns we see repeatedly.
What Each Body Actually Requires
FCC Part 15 covers intentional and unintentional radiators — essentially any device with a radio or a clock above a certain frequency. The authorisation pathway (Supplier's Declaration of Conformity, Certification, or Verification) depends on device category, and the testing labs must be on the FCC-recognised accreditation list.
What catches companies late: RF exposure (SAR) requirements for devices worn near the body; software-defined radio restrictions that affect over-the-air update architectures; and the distinction between modular approval and host device approval. A certified radio module does not automatically confer FCC authorisation on the end product in all configurations.
Lead Time Warning
Planning around a four-week turnaround and getting a twelve-week queue is a real risk at accredited labs. Lead times are longer than they were three years ago and have not recovered.
ISED administers the Canadian equivalent of FCC under the Radio Equipment List and RSS standards. CE marking and FCC authorisation do not transfer. ISED requires its own conformity assessment, and while the technical standards are closely aligned with FCC in many areas, the regulatory process is distinct and the labelling requirements differ.
Companies that treat North America as a single market and plan a single certification programme discover the Canadian requirement when they are already in distribution. The fix is straightforward — ISED approval can run in parallel with FCC — but only if it is scoped in before testing begins. Retrofitting it after FCC authorisation typically means a second round of lab time and a filing delay.
Any device using cellular connectivity sold through or used on US carrier networks requires carrier approval in addition to FCC authorisation. PTCRB certification covers protocol conformance testing for 3GPP-based devices; individual carriers — AT&T, T-Mobile, Verizon — then have their own approval processes that certify the device for use on their specific network infrastructure.
IoT devices using LTE-M or NB-IoT have their own certification requirements distinct from handset-class devices. The timeline for carrier approval is not controlled by the applicant.
Most Underestimated Timeline Item
Carrier review periods can extend from six to sixteen weeks depending on device category and the carrier's current workload. It cannot be expedited. Companies that plan FCC lead time but not carrier approval lead time routinely miss launch windows by a quarter or more.
The FDA's jurisdiction is broader than most non-US companies assume. Medical devices are the obvious category, but FDA oversight also covers radiation-emitting electronic products (including certain imaging devices and laser systems), products that make health or wellness claims in software, and — under the 2026 guidance — AI-driven tools where the intended use determines regulatory classification.
The classification question matters most for connected health products positioned in the wellness category. The FDA's general wellness exemption removes the premarket review requirement — but only where the intended use is genuinely wellness-only. Products that make diagnostic or clinical claims, or that are used as accessories to regulated devices, fall into 510(k), De Novo, or PMA pathways depending on risk classification.
Product Strategy Input, Not a Legal Question
The intended use language in marketing materials, software, and sales collateral determines regulatory classification. Legal review after the go-to-market strategy is set is too late. This needs to happen while positioning decisions are still being made.
Drones, UAVs, and any device that can be operated in US airspace fall under FAA jurisdiction. The Remote ID rule — mandatory broadcast of identification and location data — is in effect and applies to all UAS operating in US airspace above 0.55 lbs. FAA authorisation for certain operational categories requires either a Declaration of Compliance or type certification, depending on intended use.
For European UAV manufacturers entering the US market, CE marking under the EU drone regulation (EU 2019/945) does not satisfy FAA requirements. The two frameworks have different technical standards for Remote ID, different operational category definitions, and different authorisation processes. A product that is fully compliant in Europe requires a separate authorisation programme for the US market.
The Export Administration Regulations (EAR) and International Traffic in Arms Regulations (ITAR) govern the export of technology with potential dual-use or defence applications. For most European tech companies, the relevant framework is EAR — but the answer depends on what the product contains and what it can do.
Products incorporating encryption above certain key lengths require classification under EAR and, in most cases, a one-time encryption registration or review with BIS before export. This is frequently underestimated: almost all connected products contain encryption, and the registration requirement applies even to mass-market consumer products.
Highest-Risk Failure Mode
Misclassification is the most common source of export control problems. A product assumed to be EAR99 that is actually controlled requires a licence before it can be shipped. Certain RF technologies, high-precision sensors, imaging systems, and software with specific capabilities fall under the Commerce Control List. The penalty structure is severe. Classification review before product launch is not optional.
How to Approach This Without Costly Surprises
Map the full regulatory surface at product concept stage
The applicable requirements are deterministic — they follow from what the product does, where it transmits, what claims it makes, and what it contains. A one-day scoping exercise at concept stage prevents a multi-month remediation programme after development is complete.
Scope Canada in parallel with the US from the start
ISED approval runs on similar technical foundations to FCC. Addressing it in the same lab engagement adds marginal cost and no timeline impact. Addressing it after FCC authorisation adds both.
Build carrier approval lead time into the launch plan
This is the timeline item most consistently underestimated by non-US teams. Carrier approval cannot be expedited. It needs to be started early — before the rest of the launch schedule is locked.
Conduct an EAR classification review before finalising the BOM
Component choices — particularly for RF, encryption, and sensing — affect classification. It is easier to swap a component than to apply for a licence under schedule pressure.
Treat FDA classification as a product strategy input
The intended use language in marketing, software UI, and sales collateral determines regulatory classification. Legal review after go-to-market strategy is set is too late.
What We Need From You
Getting started requires no lengthy forms and no upfront commitment. A high-level bill of materials, a brief technical specification, or a short description of your use case and target market is enough for us to give you a meaningful first read. From that, we can tell you quickly whether the path ahead is straightforward or whether there are regulatory intersections worth addressing before your next development milestone.
We have guided European technology companies through this journey — from early-stage prototypes to full-scale carrier-approved launches across medical, defence, wireless, and IoT sectors. The consistent finding: the earlier the regulatory picture is understood, the lower the total cost of getting to market.
Need a tailored market-entry or regulatory strategy?
We help European technology companies translate complex U.S. and Canadian regulatory pathways into executable plans — from FCC and PTCRB through FDA and ITAR/EAR.