LoRaWAN Certified^CM

LoRaWAN (Long Range Wide Area Network) certification is a process that ensures end devices comply with the technical specifications established by the LoRa Alliance. This certification helps ensure devices are interoperable, secure, and can communicate effectively within a LoRaWAN network.

Certification is crucial because it assures users that the device will function correctly within a LoRaWAN network. It simplifies the integration of devices from different manufacturers, minimizes compatibility issues, promotes best practices, and adds credibility to the product in the market.

1. Pre-Certification Assessment: A preliminary evaluation of the end-device to identify potential issues.
2. Testing: Comprehensive testing in an authorized test lab or by self-testing according to the LoRaWAN certification test plan.
3. Submission of Documentation: Providing necessary documentation regarding design, performance, and compliance.
4. Certification Decision: Following successful testing and review, a certification decision is made.
5. Issuance of Certification: A certificate is issued, allowing the end-device to be labeled as LoRaWAN certified.

Pre-certification testing with the LCTT conveniently takes place at the OEM’s facility. See below for details.

Self-testing would take place at the OEM’s facility.

Should you choose to use a LoRa Alliance Authorized Test Lab, that would take place at that lab’s facility. Each ATL selected by the LoRa Alliance has met the requirements for ISO/IEC10725 and is recognized by international accreditation bodies.

Find your preferred Authorized Test Lab here.

The LCTT (LoRAWAN Certification Test Tool) was developed by the LoRa Alliance to automate
testing of LoRaWAN end devices. The LCTT is provided to members who wish to pre-test and
troubleshoot their devices prior to submitting them to an ATL for certification testing.

The LoRa Alliance offers the Self-Test program to those members who qualify. The Self-Test program allows those members who have been approved to test their own end-devices and submit the test results for certification.

Self-testing your end-device can speed up the certification process. It allows the manufacturer to correct issues and rapidly retest. Self-testing, of course, can save money by not having to pay an ATL to test their end-device.

However, ATL’s offer a great depth of experience testing LoRaWAN end-devices and are able to help members resolve issues they may experience during testing. ATL’s can also help to avoid issues which may prevent the certification of your end-device.

ATL’s provide functionalities beyond what self-testing can achieve:

• Comprehensive RF Testing
  • Validate RF performance across both end-devices and gateways with precision.
• Expert Guidance on LoRaWAN Stack
  • Get fast support for software-specific issues—and direct access to the right solutions.
• Full-Scale Testing Environment
  • Leverage 64-channel gateways and a professionally configured setup to ensure your end-device is ready for deployment.
• Stay Ahead of Regional Requirements
  • Provide timely updates on evolving parameters and compliance needs for every market your device targets.
• Exclusive Feature Certification
  • Only Authorized Test Labs (ATLs) can certify advanced LoRaWAN features like Relay, SCHC, and FUOTA—ensuring your device meets the highest interoperability standards.

Members can find the most current information here.

Yes. Only LoRa Alliance members can have their end-devices LoRaWAN certified. The LoRa Alliance offers several tiers of membership which would allow your company to certify their devices. Learn more about membership here.

The duration of the end-device certification process can vary based on several factors, including the complexity of the end-device, the responsiveness of the manufacturer in providing necessary documentation, and the availability of testing resources. On average, the process could take anywhere from 3 days to 2 weeks.

Costs can vary based on the test lab, the complexity of the end-device, and the scope of the testing required. Manufacturers should budget for test lab testing fees, certification fees, and potential re-testing of the device in the event issues are identified. If the LoRa Alliance member is authorized for self-testing and self-tests their end-device, the test lab fees would not apply. However, the certification fees assessed by the LoRa Alliance do still apply.

The certification license fee is a one-time payment made upon the issuance of a device’s certificate of compliance which is good for the duration of the certification.  A certificate of compliance is valid for 5 years from issuance.   The only exception occurs if there are significant operational or functional changes to the device that impact its certification status, necessitating a re-certification.

The following table shows LoRa Alliance^® certification license fees for certifying LoRaWAN^® end devices.

Licenses Fees charged by the LoRa Alliance^® are not related to the testing fees charged by ATL’s.

End Device Certification License Fees

(Paid to the LoRa Alliance)

• Child = Region or Similar Device¹
• Region = Channel Plan
• A Certified by Similarity (CbS) device can be the same end device as the parent but operating on a different channel plan¹.
• AS923-1, AS923-2, AS923-3 and AS923-4 are considered one region if supported in the same device hardware.
• If an end device which supports all regions is certified the total License Fees = $6,150
• Child devices do not have to be certified at the same time as the Parent device¹.

¹ Details on CbS can be found in Section 18.3 Pre-conditions For Certification by Similarity of the Program Management Document.

Module Certification License Fees

(Paid to the LoRa Alliance)

• Modules are unable to be certified using Certification by Similarity (CbS). 

Once a LoRaWAN product has been certified by the LoRa Alliance, it will be certified for a period of 5 (five) years unless and until the LoRa Alliance revokes the certification or the product is modified as to impact its continued compliance with the grant of the Certification of Compliance. All devices which are certified after June 3, 2024, will be subject to the 5 year certification period. Devices certified prior to June 3, 2024, will retain their certification as long as they continue to meet the requirements which were in effect at the time of certification.

Yes, the LoRa Alliance Certification program provides a certification path for these and similar circumstances called Certified by Similarity or CbS. The rules for the program are described in the LoRaWAN Certification Program Management Document.

Pre-conditions For Certification by Similarity

A.) A similar product (from same OEM or module from different OEM) has already been certified.

B.) OEM applies for certification of a variant product by referring to the already certified product. There are two different cases that are possible (see below figure):

1. Module Integration: The variant product to be certified embeds a LoRaWAN certified module.
2. Similar Product: A variant product uses the same LoRaWAN design of an already LoRaWAN certified product (Parent).
   • Same LoRaWAN transceiver.
   • Variant is submitted for CbS within 5 years of certification of the Parent.
   • LCTT shall be used to confirm conformity to the same LoRaWAN specification as the Parent. May have different enclosure.
   • May provide a different sensor.
   • The same LoRaWAN protocol SW version.
   • The same MCU Core.

NOTE: An OEM cannot claim a product to be CbS if the original certifying OEM is no longer a LoRa Alliance member in good standing.

All LoRa Alliance member companies are allowed one free LCTT license per year. Each additional license can be purchased for a fee of $1000 USD per license.  Please contact certify@lora-alliance.com for license purchasing information.

Yes, manufacturers can appeal a certification decision through the established procedures described within the LoRaWAN Certification Program Management Document.

Proper RF performance testing prevents costly field failures and ensures devices operate as intended, minimizing interference with other wireless systems and meeting crucial regulatory compliance standards. 

It goes beyond simply avoiding failures, delivering several benefits for product development and market success:

• Improved Product Reliability: Rigorous RF testing identifies potential weaknesses and vulnerabilities in the design, enabling manufacturers to build robust devices that perform reliably under various real-world conditions.
• Faster Time-to-Market: Catching and addressing RF issues early in the development cycle, during prototyping and design validation, avoids costly rework and delays that arise from late-stage fixes, 
• Ensuring Safety: By verifying adherence to RF exposure limits and standards, testing safeguards users from potential health risks associated with excessive electromagnetic emissions.
• Compliance with Regulatory Requirements: RF testing is essential for meeting the regulations set by bodies like the FCC in the U.S. and ETSI in Europe, allowing products to be legally sold in various markets and avoiding fines or product recalls.
• Enhanced User Experience: Devices optimized through proper testing provide users with reliable and seamless wireless communication, minimizing dropped connections, degraded performance, and connectivity issues.
• Competitive Edge: Companies that prioritize comprehensive RF testing deliver high-quality, dependable products that stand out in the crowded wireless market, fostering customer trust and loyalty. 

By catching issues early, verifying compliance, and enhancing device performance, proper RF testing becomes a critical investment, ensuring the long-term success of LoRaWAN wireless products. 

Member Portal Links (Available to Members Only)

Certification by Similarity

General resource documents for all regions and specifications:

• LoRaWAN® Certification Program Management and Development (PMD)
• LoRaWAN® Certification-by-Similarity Declaration v1.1 
• GitHub link to reference code 

LoRaWAN Specification 1.0.4 Resources:

• LoRaWAN® Gateway Test and Measurement Guidelines
• White Paper on Radio Coexistence Issues and Solutions