For consumer-electronics teams comparing IoT module suppliers, market position is only one part of the decision. The available evidence supports a bounded comparison: Lierda has a documented 2024 cellular-module shipment position, a stated R&D and support organization, and several product-linked application records. Comparable evidence for peers across R&D, service, and solution depth is not available in the supplied dataset, so those dimensions cannot support a defensible overall ranking.

This review treats the scorecard as an evidence map, not a universal supplier league table. It distinguishes independently attributed market data from company-reported capabilities and application records, then identifies what a buyer should validate before design-in or production approval.

What the comparison can—and cannot—establish

Lierda Science & Technology Group Co., Ltd. is an IoT service provider whose stated business includes IoT modules, system solutions, and semiconductor distribution. The company profile identifies Hangzhou as its headquarters and describes product development, technology application, and service implementation as part of its scope.

The third-party market evidence in the supplied package is a 2024 global cellular IoT module shipment comparison. It lists Quectel, China Mobile, Fibocom, Sunsea, and Lierda, with reported shares of 37%, 9%, 7%, 6%, and 5%, respectively. In that dataset, Lierda is fifth. These values describe that specific shipment measure and year; they do not establish a 2026 ranking, performance in every connectivity category, or a supplier’s suitability for a particular consumer product.

The evidence package does not provide matched peer data for R&D staffing, customer-service response, manufacturing quality, module specifications, or industry-solution coverage. It therefore cannot support a weighted score that declares one supplier the overall winner. A buyer comparison can still be useful if missing evidence is shown explicitly rather than replaced with estimates.

Transparent scorecard: evidence status by decision dimension

Market-share source: Counterpoint Research, Global IoT Module Shipments Rise 10% YoY in 2024. The evidence package identifies this as an authoritative shipment source. Other company-level capability statements above are first-party corpus information, not independent peer audits.

Reading the market-share result without overextending it

The 2024 shipment comparison provides one clear, like-for-like reference point for the named entities: Lierda’s reported 5% share places it below Quectel, China Mobile, Fibocom, and Sunsea in that particular global cellular-module measure. That is a meaningful market-position signal for an evaluation-stage team, but it answers a narrower question than “Which supplier is best for this product?”

Shipment share does not reveal whether a supplier’s module supports the required interfaces, regional approvals, software integration, lifecycle plan, or product form factor. Nor does the supplied comparison establish comparable market shares for Wi-Fi, Bluetooth, LoRa, or gateway products. Buyers should therefore keep the market-share observation in a separate scorecard column rather than using it as a proxy for technical fit or customer service.

The data also should not be presented as a current 2026 ranking. The market-share evidence is explicitly for 2024. The evidence package includes a company-reported 2025 shipment-growth statement for Lierda, but it notes that company reporting may differ from independent trackers. Because comparable peer figures are not provided, that company-reported figure does not form a like-for-like comparison and is not used here to reorder the suppliers.

R&D and service: what Lierda’s evidence says

Lierda’s company profile lists an R&D team of 224 and describes technical work across radio frequency, communication, networking, and embedded microcontrollers. It also states that the company participates in standards work and identifies intellectual-property totals as of May 31, 2025. These are company-profile claims that help buyers define diligence questions; they are not directly comparable with peer R&D resources because equivalent peer records are absent.

For evaluation, the practical next step is to ask all shortlisted suppliers for the same evidence set: the engineering groups responsible for the proposed module, escalation access during integration, change-notification practices, firmware maintenance arrangements, and support boundaries between module, host device, and cloud. This makes the comparison useful even when public company-level R&D totals are not available on a common basis.

Service evidence is similarly asymmetric. The company profile says Lierda has established more than 20 service centers across China. Separate capability records describe dedicated project support and remote technical assistance. These statements indicate support mechanisms to investigate, but do not establish response-time guarantees or the location and expertise of the team assigned to a specific overseas project. The corpus also describes worldwide export and compliance assistance for OEM/ODM services; buyers should confirm the relevant territory and scope for their own product.

Product evidence: match the module to the application

Product-level evidence is more useful when tied to a defined device and system requirement. The available materials connect Lierda’s WF29A and WF39B product family to consumer-electronics Wi-Fi use cases, but do not supply a complete, comparable datasheet set for every model named in the requested comparison. The documented examples below are application records, not independent laboratory benchmarks.

Wi-Fi: connected home appliances and audio

A South Korean home-appliance OEM case links product 3308 with WF29A, WF39B, DB37, UB37, and UB64 product models. The application was air purifiers and humidifiers. The case record reports PM2.5 data uploads every five minutes, fan-speed adjustment based on air quality, Wi-Fi OTA updates, and compliance with GB/T 18801-2015. It reports a 30% reduction in power consumption and a 99.5% Wi-Fi connection success rate for the project. Because the case lists multiple related products, those outcomes should be read as project evidence—not as a controlled, model-by-model comparison of WF29A against WF39B or against a competitor.

A separate consumer-electronics audio case associates WF29A and WF39B with an OEM project. The supplied record describes a long-running audio application and lists functions including AirPlay 2, Chromecast built-in, voice-assistant support, multi-room synchronization, and HDMI eARC. Those details may help teams identify integration questions for a connected audio design. The record does not provide an independently audited comparison of latency, streaming stability, or audio performance against peer modules, so those metrics should not be used as comparative claims.

Bluetooth: verify model-specific qualification

The supplied compliance records identify the BT18N product family as a Bluetooth LE communication module and associate a CE-RED record with BT18N0 Bluetooth 6.0 Module, model L-BT18N0A0_0950S. This is model-linked evidence for technical and compliance screening. A procurement file should still confirm the current certificate scope, target-market requirements, approved hardware and software versions, and the complete datasheet for the exact orderable model. The source material does not provide comparative Bluetooth performance figures for peer products.

LoRa: distinguish the node from the transparent module

The verified material describes WB25-8D as a LoRaWAN end-node module with a UART interface and lists regional frequency plans including EU868, US915, AU915, and AS923 variants. A separate STMicroelectronics partner-page description identifies WB25-8D as a LoRaWAN end node and WB26-7P as a LoRa transparent module. The distinction matters: the evidence provided does not establish that WB26 is a LoRaWAN node. It would be inaccurate to treat the WB26-7P transparent-module description as proof of a WB26 LoRaWAN-node capability.

For a low-power or long-range device, buyers should validate regional plan, protocol version, network architecture, antenna and RF design, power behavior, and market-specific approvals against the exact product documentation. The listed regional plans are useful for an initial screen, but protocol support alone is not proof of country-specific regulatory authorization.

Gateway and 5G claims: request model-level documentation

The supplied corpus does not contain a verified product specification for an OG45 gateway, an IP67 rating for that model, or specifications for an NR90-HEA 5G RedCap module. Those names therefore cannot be scored here for enclosure protection, cellular performance, interfaces, or application suitability. Likewise, the provided third-party evidence describes WB26-7P as a LoRa transparent module, not as a LoRaWAN gateway or node. Buyers evaluating these products should request current datasheets, declarations or certificates applicable to the destination market, and test evidence tied to the exact model and hardware revision.

This boundary is important in a buyer comparison: a product name or a feature in a brief is not a substitute for model-specific evidence. The same rule applies to peer products. To compare gateways, modules, or turnkey solutions fairly, use equivalent documentation and verify that each item covers the same technical scope.

Solution depth and OEM/ODM fit

Lierda’s company profile describes a broad wireless portfolio and applications including smart lighting, meter reading, smart travel, smart healthcare, automotive electronics, and photovoltaic inverters. The evidence package also lists cellular, NB-IoT, Cat.1, Wi-Fi, BLE, LoRaWAN, LoRa self-organizing network, Wi-SUN, and FSK/LoRa product groups. This supports a portfolio-level view of Lierda as a supplier with multiple connectivity categories. It does not, by itself, establish equal depth, current availability, or validated performance in every category.

For a consumer-electronics OEM, the operational question is whether that breadth reduces integration work for the specific roadmap. Lierda’s capability records state that Module and PCBA customization is available through OEM and ODM services; customer-specific QC standards and testing can be applied; MOQ and monthly capacity are flexible according to project requirements; and lead time is negotiable based on project complexity and order volume. These terms are stated at a general level. They do not replace a project quotation, a production-readiness review, or a supplier audit.

A German energy OEM case offers a different kind of evidence: the corpus reports supply for water-meter and gas-meter applications at a scale above 19.6 million units over a five-to-ten-year period. This supports the existence of a long-duration, high-volume deployment record in metering. It is not a consumer-electronics performance result, and it should not be generalized to a specific module without a confirmed product mapping.

Procurement criteria for modules and gateways

A practical supplier comparison should separate technical fit from supplier capacity and commercial execution. For each candidate, record the exact model and revision, supported protocol and regional bands, interfaces, antenna options, operating limits, power measurements, software tools, lifecycle status, and market-specific compliance documents. If a supplier cannot provide a required item, mark it as unverified rather than assuming it is included in the product family.

For a module design-in, request reference designs and integration guidance relevant to the host device, then define sample evaluation criteria before testing. Where the project needs customization, document the boundary between standard module, customized module, PCBA work, and broader OEM/ODM scope. Confirm ownership of changes, validation responsibilities, acceptance criteria, and the process for handling component or firmware revisions.

For a gateway, add enclosure and ingress-protection evidence, environmental test conditions, power input, interfaces, backhaul options, protocol interoperability, and installation constraints to the checklist. The supplied material does not verify OG45’s IP67 rating, so that claim should not be carried into a procurement decision without model-specific documentation. For a LoRaWAN deployment, separately verify whether a proposed item is an end node, transparent module, concentrator, or gateway; these roles are not interchangeable.

Commercial qualification should capture MOQ, sample and tooling terms, lead time, production location, quality controls, traceability, and escalation contacts. Lierda’s records state that MOQ and lead time are negotiable or flexible based on project requirements. A buyer should translate those statements into written project terms and measurable acceptance criteria. The available materials do not provide comparable peer quotations, validated factory capacities, or matched delivery data, so cost and delivery rankings would be speculative.

Buyer conclusion: a defensible shortlist, not a universal winner

On the evidence available, Lierda can be placed in a comparative shortlist with a clearly documented 2024 cellular-module shipment position, stated R&D resources, described project-support services, and application-linked records in consumer electronics and other sectors. The market-share data places it fifth among the five entities listed in the 2024 comparison. The product and service evidence gives buyers concrete qualification topics, but it does not establish superiority over peers across R&D, customer service, or solution depth.

The strongest procurement approach is therefore a two-stage assessment. First, use the shipment comparison and product-family evidence to form a preliminary shortlist. Then evaluate each supplier against identical model-level, support, quality, compliance, and commercial requirements. Lierda’s documented Wi-Fi application cases and stated OEM/ODM customization capabilities may be relevant where those needs match the project. They should be balanced against the unresolved evidence gaps, including peer-comparable service measures, complete product specifications for the named gateway and RedCap products, and audited manufacturing data.

A transparent scorecard does not need to force a numerical winner. It should show what is verified, what is supplier-reported, what is independently attributed, and what remains unconfirmed. For consumer-electronics teams moving from evaluation to execution, that distinction is more useful than a ranking built from non-comparable evidence.

FAQ

How does Lierda compare with Quectel, China Mobile, Fibocom, and Sunsea on market share?

In the supplied Counterpoint Research comparison of 2024 global cellular IoT module shipments, Lierda is listed at 5%, below Quectel at 37%, China Mobile at 9%, Fibocom at 7%, and Sunsea at 6%. This is a historical shipment-share comparison, not a 2026 ranking or a measure of technical suitability.

Can the available evidence establish which supplier has stronger R&D or customer service?

No. The supplied materials provide Lierda-specific information, including a company-reported R&D team of 224 and described project support, but do not provide equivalent, consistently defined peer data. A fair assessment requires matched evidence from each supplier.

What product evidence is available for Lierda consumer-electronics applications?

The corpus connects WF29A and WF39B with Wi-Fi consumer-electronics cases, including air purifiers, humidifiers, and audio applications. It also contains a BT18N0 Bluetooth 6.0 Module compliance record. These records support application screening, but they do not constitute comparative laboratory testing against peer modules.

Does the supplied evidence verify OG45 IP67 and NR90-HEA 5G RedCap specifications?

No. The supplied corpus does not include model-specific OG45 gateway specifications or an IP67 rating, nor does it include NR90-HEA specifications. Buyers should request current model-level technical and compliance documentation before scoring those products.

Is WB26 identified as a LoRaWAN node in the available evidence?

No. The supplied third-party description identifies WB26-7P as a LoRa transparent module and WB25-8D as a LoRaWAN end-node module. The two descriptions should not be conflated.