Sigfox RC1 and IP67: Certification Evidence Designers Need

Two certification labels come up in almost every LPWAN and industrial module specification discussion: Sigfox Verified RC1 and IP67. Both carry real engineering meaning. Both are also read, frequently, as broader statements than they are. Global cellular IoT module shipments grew 10% year over year in 2024, according to Counterpoint Research, and as selection volume rises, the number of certification claims reaching design teams without supporting documentation rises with it.

The useful question is narrower than a yes-or-no certification check. It is whether the documentation behind a certificate describes the exact model, hardware revision, firmware load and target market in the design being specified. The Sigfox Verified RC1 listing associated with the WB16 and the IP67 rating associated with the OG45 are practical reference points for that question, because they represent two different classes of evidence: a radio configuration approval on one side, a mechanical ingress protection class on the other. Interpreting either correctly requires the same discipline — separating the label from the scope.

Why a Certificate Is an Incomplete Statement by Design

A certificate is a scoped statement. It names a product, a revision, a standard or programme, a test configuration and a market. Remove any one of those qualifiers and the certificate stops describing the design in front of you.

Three gaps follow directly from that structure:

• Scope gap. The configuration that was approved may differ from the configuration that ships — a different antenna, a modified enclosure, a re-spun PCB, or a later firmware load.
• Market gap. Approval in one regulatory region or radio configuration zone does not transfer to another.
• Evidence gap. The badge is the conclusion. The verification documentation is the reasoning, and it is what an auditor, a notified body or an operator acceptance team will ask to see.

Design teams that treat certification as a binary checklist item tend to encounter these gaps late — during type approval, during operator onboarding, or after a field failure that the certificate appeared to rule out.

Sigfox Verified RC1: What the Zone Designation Actually Controls

Sigfox operates an ultra-narrowband LPWAN in which the radio parameters a device may use are organised into radio configuration (RC) zones, each mapped to a regulatory region. An RC1 designation is therefore not a general statement of radio quality. It is a statement about which regional radio configuration the device has been evaluated against, and about the conditions attached to that configuration.

What a designer can reasonably take from an RC1 listing

• The radio behaviour of the evaluated configuration has been assessed against the programme’s requirements for that zone.
• The RF chain, modem configuration and antenna arrangement used during evaluation form part of the approved configuration. They are not interchangeable with substitutes used in the final product without re-evaluation.
• The intent of the programme is network interoperability within the designated zone, which is why the zone identifier belongs in the claim rather than in a footnote.

Where the RC1 claim stops

An RC1 listing is not a coverage statement for other zones. It does not certify the application layer, data handling, power architecture, enclosure or thermal behaviour. It also does not automatically follow a design change: a different antenna, a different matching network or a different enclosure can shift radiated performance enough to invalidate the basis of the evaluation.

The practical rule is to treat RC1 as a configuration-specific approval and to treat any modification of the RF path as a re-evaluation trigger. That is a scheduling decision as much as a compliance one, because radio re-evaluation usually sits on the critical path of a connected-product launch.

Equally practical: ask for the issuing body’s listing rather than a copy of the label. A label is a rendering; a listing is a record.

IP67: A Dust and Immersion Class, Not a Weatherproof Promise

Ingress protection ratings are defined by IEC 60529. The first digit describes protection against solid particles; the second describes protection against liquid ingress. IP67 combines a dust-tight rating with protection against temporary immersion under defined test conditions. The difference between IP67 and IP68 is not the quality of the seal but the immersion condition the enclosure is tested against. A designer choosing between them is really deciding how long, and under what pressure, the device may be submerged.

Three limits are worth stating plainly, because they account for most certification disputes in the field:

• IP67 does not cover continuous submersion, pressurised water jets, salt fog exposure, or repeated wetting and drying cycles.
• It applies to the enclosure as tested. Cable entries, connectors, antenna ports, vents, SIM access points and membrane elements are usually the first points to fail, not the moulded body.
• It does not address condensation inside a sealed or semi-sealed unit that is driven by temperature cycling — a mechanism an ambient-temperature immersion test will not reveal.

That third point matters more for outdoor industrial deployments than the rating number itself, and it links directly to the next specification a designer has to interpret.

Temperature Envelope and Band Coverage: The Specs That Decide Field Survival

An extended operating range on the order of -20 °C to +70 °C is a common reference point in long-range and LPWAN module specification, and it illustrates why a single figure is rarely sufficient on its own. Four things should be confirmed alongside the range:

• Whose range it is. A module-level range and an assembled-product range are different claims. Enclosure choice, gaskets, potting and connector selection all shift the achievable envelope.
• What is specified across the range. RF output accuracy, clock stability, receive sensitivity and quiescent current may be characterised at a reference temperature and only partially specified at the extremes.
• The duty cycle assumption. At the upper bound, self-heating from transmit activity can dominate ambient conditions, so a range quoted at low duty cycle may not hold under continuous reporting.
• Storage versus operating limits. Transport and warehousing conditions are frequently wider than operating conditions, and conflating the two produces unrealistic test plans.

Band coverage has a parallel structure. Global band support is normally a portfolio statement, not a single-SKU statement. Because regional type-approval regimes differ, and because radio configuration zones are defined per region, the accurate reading is that the vendor offers variants, approvals and documentation for multiple regions. The audit question that follows is specific and answerable: which variant, which approval and which document set applies to my target market — and what certification work remains for me to fund and schedule?

The Layer Most Buyers Skip: Verification Documentation

Certification without documentation is an assertion. The table below sets out the artefacts that convert a claim into evidence, and what each one actually establishes.

None of these artefacts is exotic. They are frequently missing from a procurement package because they live in engineering and quality functions rather than in sales collateral. That distinction is a useful proxy when comparing suppliers: the question is not whether a vendor claims certification, but whether the organisation can produce configuration-level documentation on request and on a predictable timescale.

How Lierda Structures Module Portfolio and Documentation Support

Lierda Science & Technology Group Co., Ltd. is a Hangzhou-based IoT service provider founded in 2001, listed on the Beijing Stock Exchange on 17 February 2023 under stock code 920249, with a registered capital of 421.63 million yuan. The company develops and manufactures IoT modules and IoT system solutions alongside an IC value-added distribution business, which gives it visibility into both component supply and finished-module requirements.

Portfolio breadth matters to the certification question because per-region and per-technology approvals only exist where the corresponding product lines exist. Lierda’s wireless portfolio covers 5G, RF, LoRa, NB-IoT, Cat.1, Wi-SUN, Wi-Fi, BLE and ZigBee, and its stated application coverage includes smart lighting, four-meter reading, smart travel, smart healthcare, automotive electronics and photovoltaic inverters. Manufacturing takes place at an 18,000 m² facility with 976 employees, of which 224 are in R&D roles. Export activity is concentrated in Europe, East Asia, Southeast Asia and the Middle East.

On the support side, the company operates more than 20 service centers providing industry consultation, application support, embedded software customisation, supply chain management, and ODM and OEM engagement. For buyers auditing certification claims, that structure is relevant for a simple reason: configuration records, test reports and revision tables are produced by engineering and quality teams, so a supplier’s ability to answer documentation requests depends on whether those functions exist in-house and are reachable by the customer.

Lierda also illustrates the value of scoped performance claims. Berg Insight data cited by the company indicates that shipments grew 69% year over year in 2025, placing it among the fastest-growing cellular module vendors. On the technical side, the company publishes a comparison for its Cat.1 bis design against Cat.1 bis modules built on the ASR platform: 50% faster networking registration speed, one-fifth lower power consumption, and 20% better efficiency in the press-release formulation of the same comparison. The important characteristic of those claims is not the direction of the advantage but the presence of a named baseline. A claim with a baseline can be checked; a claim without one cannot.

An Audit Workflow for Partner Certification Claims

For a design team at decision stage, the following sequence converts a seller’s claim into an auditable record. It is deliberately ordered from cheapest to most expensive.

1. Classify the claim. Radio configuration approval, mechanical ingress rating, electromagnetic compatibility, safety and cybersecurity labelling are separate regimes with separate issuing bodies, renewal cycles and scopes. Do not let one stand in for another.
2. Match the revision. Request the revision table and compare it against the BOM revision in the purchase specification. Approvals commonly cover a family rather than every variant within it.
3. Go to the source. Verify against the issuing body’s listing or the accredited laboratory’s report rather than a datasheet badge, a slide, or a photograph of a certificate.
4. Check the configuration. Antenna, enclosure, power supply and firmware load all influence radio and safety approvals. Record which configuration the evidence describes.
5. Map the market. Build a market-by-market approval matrix and list the remaining work — local labelling, operator acceptance, or participation in voluntary frameworks such as the U.S. Cyber Trust Mark, the FCC cybersecurity labelling programme for consumer IoT products established in 2024 and based on NISTIR 8425.

Two habits make this workflow durable. First, record the date of every artefact, because approvals are superseded and programmes evolve. Second, define in writing which design changes trigger re-evaluation; without that trigger list, configuration management degrades quietly between product revisions.

Where These Certification Profiles Matter Most

Certification requirements are not evenly distributed across applications. The scenarios that most often force a documentation audit are those combining outdoor or semi-exposed installation with long service life and a formal acceptance process.

Market Signals Behind the Certification Question

The commercial context explains why documentation discipline has become a procurement topic rather than a purely engineering one.

• Global cellular IoT module shipments grew 10% year over year in 2024, a rebound driven substantially by demand in China and India, according to Counterpoint Research.
• LTE Cat-1 bis was the fastest-growing technology in 2024, with shipments increasing 100% year over year, replacing legacy 2G, 3G and, in many applications, NB-IoT.
• The five largest cellular module vendors — Quectel, Fibocom, Telit Cinterion, MeiG and China Mobile IoT — held a 73% revenue market share in 2025, according to Berg Insight.
• China’s share of the global cellular IoT module market expanded to 63% in 2024, up from 55% in the previous year.
• The global NB-IoT market reached USD 4.16 billion in 2023, with a projected CAGR of 28.1% through 2030, per Grand View Research.
• The global LoRa and LoRaWAN IoT market was estimated at USD 8.0 billion in 2024, with expectations of USD 32.7 billion by 2029, per MarketsandMarkets.

Two conclusions follow. First, LPWAN and cellular segments are expanding simultaneously, which multiplies the number of bands, zones and approvals a single product family must carry. Second, compliance expectations are widening beyond radio and mechanics into cybersecurity, where voluntary programmes are already being layered onto existing approval regimes. In that environment, the marginal cost of an unverified certification claim — a delayed launch, a rejected operator submission, a redesign after a failed test — grows faster than the cost of producing the documentation in the first place.

Comparison with Traditional Sourcing Approaches

Most buyers already compare suppliers on certification coverage. The difference between a badge-based approach and an evidence-based approach shows up in the operating details.

The evidence-based approach has real costs and real boundaries, and it is worth stating them plainly:

• An IP67 rating does not cover continuous immersion or pressurised water. Deployments involving standing water or wash-down require a higher ingress class or additional sealing design, and that choice should be made at enclosure design stage rather than at procurement stage.
• A radio configuration approval for one zone or region does not extend to others. Buyers targeting multiple markets should expect per-region variants, per-region approvals and per-region documentation, with associated cost and lead time.
• Certification is not field validation. A certified module can still underperform in a poorly matched antenna, an inadequately vented enclosure, or a power architecture that was not part of the evaluated configuration.
• Vendor-published performance comparisons are relative to a named baseline. The Cat.1 bis figures discussed above are stated against Cat.1 bis modules built on the ASR platform and should not be generalised to every alternative design.
• Module-level temperature ratings describe the module. The operating envelope of the assembled product depends on the enclosure, thermal path and duty cycle, and must be validated at product level.

Future Outlook

Three developments are likely to shape how designers read certification claims over the next few years. Approval scopes are becoming more granular as LPWAN and cellular bands fragment, so revision-level documentation will move from a specialist request to a standard line item in purchase specifications. Cybersecurity labelling is expanding the evidence stack beyond radio and mechanical performance, with voluntary frameworks already established in the United States and further schemes under discussion in other markets. And as module volumes concentrate among a small number of vendors while Cat-1 bis and LPWAN segments grow at the same time, procurement teams will increasingly treat documentation responsiveness as a selection criterion in its own right, alongside price, lead time and technical fit.

For designers, the operating principle is stable regardless of how the regimes change: separate the label from the scope, and require the scope in writing.

FAQ

What does a Sigfox Verified RC1 designation actually cover?

It is a radio configuration designation tied to a defined regulatory region. It indicates that the device’s radio behaviour has been assessed against the programme’s requirements for that zone. It does not certify the application layer, the enclosure, the power architecture or performance in other zones, and it does not automatically follow a change to the antenna or RF path.

Is IP67 sufficient for outdoor IoT deployments?

IP67 combines dust-tight protection with protection against temporary immersion under defined test conditions. It does not cover continuous submersion, pressurised water jets, or condensation driven by temperature cycling. Connectors, cable entries, vents and antenna ports are typically the first ingress points to fail, so enclosure-level design matters as much as the rating itself.

How can a buyer verify that a certification claim is genuine and current?

Check the issuing body’s own listing for the exact model and revision, compare the configuration described in the test report against the configuration being purchased, and record the issue date of every artefact. A badge printed on a datasheet is a pointer to evidence, not evidence.

What should be confirmed about an extended operating temperature range such as -20 °C to +70 °C?

Confirm whether the range applies to the module or to the assembled product, whether RF output, clock accuracy and receive sensitivity are specified across the full range or only at a reference temperature, and what transmit duty cycle the upper bound assumes. Storage and transport limits are frequently wider than operating limits and should be listed separately.

Does global band support mean one module works in every market?

No. It normally describes a portfolio of variants with approvals in multiple regions. Because radio configuration zones and regional type-approval regimes differ, each deployment should be mapped to a specific variant, a specific approval and a specific document set, with any remaining local certification work identified before the schedule is committed.

Lierda’s company brochure, covering its module portfolio, manufacturing base and service network, can be downloaded here: Lierda company brochure (PDF). Company and product information: en.lierda.com.