LoRa Compliance and Certification: What Manufacturers Need to Know
LoRa and LoRaWAN are widely used for IoT applications, from smart metering and asset tracking to industrial sensors and smart city infrastructure.
For manufacturers, however, integrating a LoRa or LoRaWAN module is only one part of the overall compliance process.
A LoRa product may need to meet not only the requirements of the LoRaWAN ecosystem, but also the applicable regulatory requirements for radio, EMC, RF exposure, safety and other product requirements in each target market.
The key point is:
LoRa and LoRaWAN are not a single worldwide regulatory approval.
Frequency bands, transmit power, channel arrangements and other regulatory requirements vary between regions.
Understanding these differences early is essential when defining the compliance scope of a LoRa-based product.
What is LoRa?
LoRa stands for Long Range and refers to a proprietary radio modulation technology designed for low-power, long-range communication.
LoRa uses a form of Chirp Spread Spectrum (CSS) modulation.
LoRaWAN builds on LoRa and defines a network protocol for low-power wide-area network applications.
The two terms are often used interchangeably, but technically they describe different things:
LoRa = radio modulation / physical layer
LoRaWAN = network protocol
From a regulatory perspective, what matters is how the actual radio interface is implemented in the product.
LoRa Is Not the Same Everywhere – The Frequency Region Matters
One of the most common mistakes when developing a LoRa product is assuming that the same RF configuration can be used worldwide.
In practice, this is generally not the case.
LoRaWAN defines regional parameters through its Regional Parameters, taking the relevant regional requirements into account.
Common LoRaWAN regions include:
- EU868
- US915
- AU915
- AS923
- IN865
- KR920
- RU864
These regional designations correspond to different frequency plans.
A product designed for Europe therefore cannot automatically use the same RF configuration in the United States, Australia or India.
EU868 vs. US915
A simple example illustrates why the regional configuration matters.
A typical European LoRaWAN product operates in the EU868 frequency range.
A product intended for the United States will typically use the US915 frequency range.
The differences are not limited to frequency.
Parameters such as:
- Channel structure
- Bandwidth
- Transmit power
- Duty-cycle requirements
- Frequency-hopping requirements
- Permitted operating modes
can also differ.
The regulatory assessment therefore needs to be based on the actual regional configuration of the product.
Which Requirements Should Manufacturers Consider?
A LoRa product can involve several different compliance areas.
Depending on the product and target market, these may include:
Radio / Spectrum
EMC
RF Exposure
Electrical Safety
Cybersecurity
Product-specific regulatory requirements
LoRaWAN certification
Not every requirement applies to every product. The actual scope needs to be determined based on the product architecture and target market.
Radio Requirements for LoRa Products
Radio compliance is one of the central elements of the assessment.
Depending on the market and implementation, parameters such as the following may need to be considered:
- Frequency range
- Channel spacing
- Bandwidth
- Transmit power
- ERP or EIRP
- Antenna gain
- Modulation parameters
- Duty cycle
- Occupied bandwidth
- Spurious emissions
- Receiver performance
- Frequency stability
The exact requirements depend on the target market and regional implementation.
For a European product, for example, it is not sufficient to state that the product operates at “868 MHz.”
The actual frequency, transmit power, bandwidth, channel configuration and operating mode also need to be considered.
Duty Cycle Can Be Critical
One important difference between regulatory regions is how channel occupancy is controlled.
In certain European applications, duty-cycle limits play an important role.
In simple terms, this limits the percentage of time a transmitter may occupy a channel within a defined period.
For manufacturers, this can have a direct impact on product design.
Higher data requirements can raise questions such as:
- How often can the device transmit?
- What payload size is used?
- How many retransmissions are required?
- Which spreading factors are used?
- How long does each transmission take?
- How does ADR affect the operating behaviour?
These parameters can affect not only network performance but also the regulatory assessment.
LoRaWAN and Adaptive Data Rate
LoRaWAN can use Adaptive Data Rate (ADR) to adjust transmission parameters according to network conditions.
This can result in changes to parameters such as the spreading factor and data rate.
From a compliance perspective, it is important to understand which operating conditions the product actually supports.
The assessment should therefore not necessarily be based on a single nominal RF configuration.
Instead, the possible combinations of:
- Frequency
- Bandwidth
- Spreading factor
- Transmit power
- Data rate
should be considered where relevant.
Pre-Certified LoRa Modules
As with Wi-Fi, Bluetooth and other wireless technologies, many manufacturers use pre-certified radio modules.
This can significantly simplify the compliance process.
However, module certification does not automatically mean that the complete end product is covered.
Factors that may be relevant include:
- Module installation
- Antenna type
- Antenna gain
- Antenna cable
- Enclosure
- Ground plane
- Output power
- Firmware
- Regional configuration
- Separation distance from users
- Simultaneous operation of other transmitters
The antenna is particularly important.
If a different antenna is used from the one covered by the original certification, the manufacturer needs to determine whether the existing approval remains applicable.
Antenna Design and LoRa Compliance
LoRa products are commonly equipped with external or integrated antennas.
The antenna can have a significant effect on the regulatory assessment.
Relevant parameters can include:
- Antenna type
- Antenna gain
- Antenna location
- Antenna clearance
- Cable losses
- Matching
- Influence of the enclosure
Changing the antenna can change the effective radiated power of the product.
Therefore:
An antenna change should always be treated as a potentially relevant compliance change.
RF Exposure for LoRa Products
RF exposure may also need to be considered for LoRa products.
Whether an assessment is required, and which assessment applies, depends on factors such as:
- Transmit power
- Frequency
- Antenna gain
- Duty cycle
- Separation distance
- Installation method
- Intended use
A fixed industrial sensor, for example, presents a different exposure scenario from a portable or body-worn product.
If several radio technologies are integrated into the same product, it may also be necessary to determine whether multiple transmitters can operate simultaneously.
LoRa Plus Bluetooth or Wi-Fi
Many modern IoT products do not use LoRa as their only wireless technology.
A product may contain:
- LoRa
- Bluetooth LE
- Wi-Fi
- GNSS
- Cellular
This increases the complexity of the compliance assessment.
One particularly important question is:
Which transmitters can operate simultaneously?
A device containing LoRa and Bluetooth is not necessarily regulatorily equivalent to simply adding the two individual module certifications together.
Depending on the market and product configuration, additional assessments may be required for:
- Simultaneous transmission
- RF exposure
- EMC
- Antenna configuration
EMC Testing
In addition to radio requirements, the electromagnetic compatibility of the finished product needs to be considered.
Depending on the product, this may include:
- Radiated emissions
- Conducted emissions
- Radiated immunity
- Conducted immunity
- ESD
- EFT/Burst
- Surge
IoT products can combine radio modules, microcontrollers, displays, sensors, power supplies and other digital circuitry.
The complete system therefore needs to be considered.
The fact that the LoRa module itself has already been certified does not automatically mean that the finished product meets all applicable EMC requirements.
LoRaWAN Certification vs. Regulatory Compliance
These two topics should be clearly separated.
LoRaWAN Certification
The LoRa Alliance operates a certification program for LoRaWAN products.
This certification focuses on compliance with the relevant LoRaWAN requirements and interoperability within the LoRaWAN ecosystem.
Regulatory Compliance
Regulatory compliance is determined by the legislation and technical requirements applicable in the target market.
This can include requirements relating to:
- Spectrum
- Transmit power
- Emissions
- EMC
- RF exposure
- Safety
- Other regulatory requirements
A product can therefore be LoRaWAN-certified while still requiring additional regulatory compliance activities.
LoRaWAN certification and regulatory compliance are two different things.
LoRa in the European Union
For a LoRa product containing radio functionality, the Radio Equipment Directive (RED) is particularly relevant in the European Union.
The exact technical assessment depends on the frequency, radio technology and characteristics of the product.
For a typical EU868 device, the applicable requirements for Short Range Devices need to be considered.
Depending on the implementation, requirements relating to:
- Frequency use
- Transmit power
- Occupied bandwidth
- Out-of-band emissions
- Spurious emissions
- Receiver performance
- EMC
- Safety
may be relevant.
The applicable standards need to be determined based on the specific product configuration and the current regulatory status.
LoRa in the United States
The regulatory framework in the United States is different.
LoRa devices operating in the relevant sub-GHz bands may, for example, fall under applicable FCC requirements for unlicensed intentional radiators.
Depending on the implementation, parameters such as frequency range, bandwidth, output power, emissions and operating mode need to be assessed.
An EU868 design therefore cannot simply be treated as a US915 product.
The US configuration needs to be evaluated separately.
LoRa in Other Markets
The situation becomes more complex when launching a product globally.
Manufacturers may need to consider regional implementations for:
- Europe
- United States
- Canada
- Australia
- Japan
- India
- Korea
- Other markets
The differences are not limited to frequency bands.
Regulatory limits, channel arrangements, transmit power and technical requirements can also vary between countries.
A global LoRa product strategy should therefore be considered during hardware and firmware development.
What Happens When a LoRa Product Changes?
Product changes can have a direct impact on the compliance scope.
Examples:
Changing the antenna
→ Potential change to RF output characteristics
Increasing transmit power
→ Potential additional RF or exposure assessment
Adding a new regional configuration
→ Potential additional regulatory requirements
Adding Bluetooth
→ Additional radio technology
Enabling simultaneous transmission
→ Potential additional RF and exposure assessment
Changing the enclosure
→ Potential impact on antenna and RF performance
Changing the power supply
→ Potential impact on EMC and safety
Every significant technical change should therefore be reviewed against the existing compliance scope.
A Practical Compliance Workflow for LoRa Products
1. Define the Product and Use Case
First establish:
- Product type
- Application
- Installation method
- Target markets
- Power supply
- Intended operating scenario
- Separation distance from users
2. Define the Radio Architecture
Document:
- LoRa / LoRaWAN
- Frequency region
- Supported channels
- Bandwidths
- Spreading factors
- Maximum transmit power
- Antenna
3. Identify Additional Radio Technologies
Check whether the product also contains:
- Bluetooth
- Wi-Fi
- GNSS
- Cellular
- NFC
- Other transmitters
4. Determine Simultaneous Transmission
Document which transmitters can operate at the same time.
5. Review Module Certifications
For each radio module, review:
- Existing certifications
- Permitted antennas
- Maximum power
- Installation conditions
- Regional variants
- Restrictions
6. Define the Target Markets
The regulatory assessment should be performed separately for each target market.
For example:
EU → EU868
USA → US915
Australia → AU915
A single RF configuration should not be assumed to automatically cover all markets.
7. Build the Test Plan
Once the product architecture, RF parameters and target markets are defined, the final test plan can be established.
This helps avoid both missing required tests and commissioning unnecessary tests.
Common Mistakes With LoRa Products
Mistake 1: “LoRa means 868 MHz”
LoRa can operate across different frequency ranges and regional configurations.
The actual frequency region must be defined.
Mistake 2: Using EU868 Worldwide
Regional regulatory requirements differ.
A global product therefore requires an assessment of the applicable requirements in each target market.
Mistake 3: Treating Module Certification as End-Product Compliance
The module is only one component of the finished product.
Mistake 4: Changing the Antenna at the Last Minute
A different antenna can change the RF characteristics of the product and potentially affect the regulatory approval.
Mistake 5: Ignoring Bluetooth or Wi-Fi
Additional radio technologies can change the overall compliance assessment.
Mistake 6: Treating Duty Cycle as Only a Software Issue
Permitted transmission time can be directly related to regulatory requirements and the actual operating parameters of the product.
LoRa Is a System-Level Decision
Compliance should not be considered only shortly before laboratory testing.
Decisions regarding:
- Frequency region
- Radio module
- Antenna
- Transmit power
- Firmware
- Regional variants
- Additional radio technologies
can all influence the eventual testing and approval effort.
An early compliance assessment allows manufacturers to consider technical architecture and regulatory requirements together.
Conclusion
LoRa provides an efficient wireless solution for many IoT applications. For manufacturers, however, using LoRa or LoRaWAN does not automatically create a single, worldwide compliance process.
The key factors include:
LoRa / LoRaWAN → Frequency region → RF parameters → Antenna → EMC → RF Exposure → Safety → Market-specific requirements
In addition, manufacturers need to distinguish between LoRaWAN certification and regulatory compliance.
The key question is therefore not simply:
“Is my product LoRaWAN-compatible?”
It is:
“What regulatory requirements does my specific LoRa implementation have to meet in each target market?”
Defining this scope early can help manufacturers identify missing requirements, avoid unnecessary testing and plan the laboratory work more efficiently.
How ScopeRight Helps
ScopeRight helps manufacturers define the RF, EMC and Safety compliance scope of their products.
Based on product-specific information, ScopeRight can identify relevant standards, required tests and estimated laboratory effort.
This gives manufacturers a structured test plan before approaching a laboratory and starting the actual testing process.
Control the Scope. Control the Cost.