IoT
IoT Device Compliance and Global Certification
Regulatory approval for sensors, gateways, trackers, and connected devices sold into many markets: radio, safety, battery, cybersecurity, and producer obligations, scoped for products with small volumes and tight margins.
The category
Many products, many markets, modest volumes each. The compliance math is unforgiving.
IoT manufacturers face a compliance problem shaped differently from consumer electronics. The devices are varied: environmental sensors, asset trackers, smart meters, gateways, industrial monitors, agricultural nodes, building controls. Each contains a radio, often a battery, sometimes a cellular module, and increasingly software that regulators care about. They're sold into many markets, frequently through enterprise or industrial channels, in volumes that don't justify a full country-by-country certification budget for each SKU.
That makes scoping everything. Using pre-certified modules and staying inside their grants. Designing one test program that serves many markets. Reusing evidence across a product family. Knowing which markets require local testing or local holders before deciding to sell there. Getting any of that wrong on a low-volume device turns a marginal product into a loss.
ORBIS Compliance works with IoT manufacturers to make global approval proportionate to the product. Our engineers scope the minimum evidence each market actually requires. Our regulatory professionals handle the filings and the local representation. ORBIS Intelligent Compliance keeps a growing device catalog's approvals visible and manageable as new variants and markets are added.
The IoT regulatory set
What connected devices are regulated for
Radio approval
Type approval in every market for the LPWAN, cellular, Wi-Fi, Bluetooth, or proprietary radio inside, with modular approval rules decided per market.
Cellular and carrier
For LTE-M, NB-IoT, and 5G devices: regulatory approval plus PTCRB or GCF certification and carrier acceptance where operators require it.
Safety and battery
Electrical safety for the device and any power supply, and battery safety and transport certification for the cells inside long-life sensors and trackers.
EMC and environmental
Emissions and immunity, plus ingress, climatic, and vibration evidence for devices deployed outdoors, on vehicles, or in industrial settings.
Cybersecurity
Baseline security requirements for connected devices arriving in the EU under the Radio Equipment Directive and Cyber Resilience Act, in the UK, the US, and elsewhere.
Producer obligations
WEEE, battery, and packaging registration and take-back financing in each market, which apply regardless of volume in most jurisdictions.
Cybersecurity is now a compliance requirement
Connected devices are being regulated for what they do on the network, not only on the spectrum.
Regulators have started treating IoT security as a market access condition. The EU's Radio Equipment Directive now includes cybersecurity requirements for internet-connected radio equipment, and the Cyber Resilience Act extends security obligations across products with digital elements. The UK requires baseline security for consumer connectable products. The US has introduced a voluntary labeling program and sector-specific rules. Other markets are following.
For IoT manufacturers, this means security design, vulnerability handling, update mechanisms, and documentation are now part of the approval file, alongside the radio and safety evidence. The requirements are new, the standards are still settling, and the enforcement practice is forming. Getting a clear reading of what applies to a specific device in a specific market often means engaging the regulator.
ORBIS tracks these requirements as they develop, assesses their impact on your devices through law impact analysis, and scopes the evidence needed alongside the rest of the approval program. Where the rules are ambiguous, we engage the authority rather than guess.
The catalog problem
Fifty device variants, thirty markets, and a spreadsheet nobody trusts.
IoT compliance fails at scale, not on any single approval. ORBIS Intelligent Compliance gives your team one view of every variant's status in every market, and flags the change that affects twelve of them at once.
Questions
IoT device compliance
Our volumes per country are small. Do producer registration and take-back rules still apply?
+
In most markets, yes. Many producer responsibility schemes have no minimum threshold, or one low enough that a small deployment triggers registration. Some offer simplified routes for small producers. Assuming volume exempts you is a common and costly mistake. ORBIS maps the obligation per market before you ship.
Can we certify a device family once and add variants later?
+
Often, with planning. Designing the program around a platform, with variants that differ in ways the approvals can accommodate, lets later variants be added through declarations or limited testing rather than full programs. That has to be built in from the start, which is part of ORBIS scoping.
How do we handle a market we only want to test with a pilot deployment?
+
Some regulators offer trial, experimental, or limited-quantity routes for pilots. Others require full approval regardless. ORBIS confirms the options per market so a pilot doesn't become an unapproved deployment.
Connect the device to every market it's meant for.
Bring the device, the radios, the battery, and the country list. We'll scope the approvals proportionately, tell you where the module grants carry, and keep the cost in line with the volume.
Book a Discussion