In February 2025, I sat in a weekly product review and watched our hardware lead draw a box on the whiteboard. Inside the box he wrote 'EC25.' I asked what it was. He said, 'Quectel LTE module.' I wrote down two words in my notebook: 'Quectel. Why?' That meeting turned into a three-week evaluation of Quectel, several other module vendors, and the difference between the lowest unit price and the lowest total cost.
What Is Quectel and What Products Do They Offer?
The first thing I did was ask the obvious question: what is Quectel and what products do they offer? I had heard the name, but I didn't have a mental map of the catalog. So I did what any cost controller would do. I opened a spreadsheet and started listing products.
Quectel is an IoT module maker. They don't sell phones or gateways to end users. They sell the embedded radio that goes into those devices. Their catalog covers 5G modules like the RM500Q, 4G LTE modules like the EC25, NB-IoT and LTE-M modules like the BG95 and BG77, GNSS modules like the L80, plus antennas, modems, and even some chips. If a product needs to connect to a cellular network, there is probably a Quectel module designed for it.
What does that look like in the real world? Think of a transparent smartphone concept shown at a trade show. The radio inside that prototype is not a full smartphone board. It's a small module, often about the size of a postage stamp. Or think of a rugged field phone like the DuraXV Extreme. A device in that category has to survive drops, temperature swings, and weak signal conditions. The radio matters as much as the case. And when I looked at industrial temperature loggers from Top Therm, I saw the same pattern: a connectivity module at the heart of the product is what lets the device send its readings without someone driving out to collect them.
I won't pretend to know which module those specific products use. I'm just saying that when I searched for 'Quectel LTE module' to understand our own choice, I kept seeing that this is how the IoT supply chain works.
The Search for a Cheaper Alternative
Now, my role is not to say yes to the first technical requirement. Our annual connectivity and component budget sits around $180,000. I've managed that budget for six years, which means I've been burned enough times to know that 'standard' does not mean 'interchangeable.'
So after the meeting, I compared six vendors over three months. Actually, let me correct that. I compared eight vendors. Two were just white-label versions of the same reference design, which is exactly the kind of thing that hides in a comparison table.
One vendor quoted a module that was $8.20 cheaper per unit than the EC25. In volume, that worked out to a theoretical saving of $41,000 across a 5,000-unit production run. That number got the CEO's attention. It got my attention too. But then I ran the TCO.
To keep the comparison fair, I pulled the FCC ID database for each module, checked the datasheet for band lists, and used the list prices that were publicly available on reseller sites in January 2025. I don't want to quote a specific module price here because channel pricing moves, and the volume we were talking about would get a private quote anyway. But I can tell you the gap was real.
The Cheap Module That Wasn't Cheaper
The cheaper module had a narrower band set. That meant we would need to build a regional variant for Europe, another for North America, and possibly a third for Asia. The EC25 had a global-band version that could ship everywhere with one part number.
The cheaper module's antenna reference design was less forgiving. Engineering estimated two extra weeks of antenna tuning. That doesn't sound like a lot until you multiply two weeks of an RF engineer's time by a loaded hourly rate. I had that figure in front of me, and it was $6,900. It doesn't sound like a lot until you add the certification risk.
Here's where the story gets expensive. The cheaper module did not have a pre-certified FCC ID on the exact variant we wanted. We could have used it, but only if we, as the device manufacturer, assumed the responsibility and cost for certification testing. Our engineering lead pulled up a rough quote for FCC, ISED, and CE testing. It was $18,400, with a best-case timeline of nine weeks. The EC25, by contrast, had certification evidence we could reference from Quectel, and some carriers had already tested it. We still had to do our own product-level certification, but we were not starting from zero.
Let me put that in plain numbers. The $8.20 per-unit saving across 5,000 units was $41,000. The extra engineering, the longer antenna tuning, and the certification risk stacked up to about $25,300 before the first prototype was even built. And that didn't include the cost of a two-month launch delay, which our sales team estimated at roughly $60,000 in late bookings. The so-called cheap module would have lost us money in every realistic scenario.
I should add one more thing: the $41,000 saving assumed the cheaper module would perform identically in production. It wouldn't. The module had a different thermal profile, and the enclosure would need a heat-dissipating pad, adding $0.35 per unit in assembly material and labor. That's another $1,750. Small line items add up.
The lowest quote is not the lowest cost. Certification time, band support, reference design quality, thermal behavior, engineering support—those are not soft factors. They are line items.
The Decision and the Night After
We chose the EC25. In procurement terms, we chose value over price. It was not the lowest quote. It was the lowest total cost.
Even after choosing Quectel, I kept second-guessing. What if the price gap was real and I was overcomplicating it? What if I got too attached to the TCO spreadsheet and missed a negotiation angle? The three weeks between order and delivery were stressful. I won't pretend otherwise.
Then the first samples arrived and our lab ran a basic RF test. The EC25 pulled signal in a test chamber where the cheaper module had failed two weeks earlier during an internal evaluation. Our engineering lead looked at the screen and said, 'Maybe we should just spec this one everywhere.' I didn't say 'I told you so.' I just updated the vendor scorecard.
It took me six years and about 340 purchase orders to learn that vendor relationships and certifications are part of product cost. That lesson didn't come from a single dramatic failure. It came from a hundred small surprises: a rush fee for a late datasheet, a rework because the reference design was incomplete, a sales team that couldn't explain a test report. The Quectel decision was the first time I could see the whole cost curve before signing, not after.
What I Would Tell Another Procurement Manager
The lesson was not 'Quectel is the best module vendor.' I don't make broad claims like that. Modular products are context-dependent. The lesson was that the cheapest quote is not the same as the cheapest decision.
When someone asks me what Quectel is and what products they offer, I answer with two things. First, they have one of the widest IoT module catalogs in the industry, from 5G down to NB-IoT, with GNSS and antenna products in between. Second, and more important to me as a buyer, the value is in the certified reference designs and the global-band coverage. That's what turns a line item into a product that can ship on time.
I've also learned to write down the cost assumptions before I make the buying decision. My procurement policy now requires quotes from at least three vendors, but more importantly, it requires a one-page TCO note. If there's more than a 10% price gap between two options, I have to explain where the extra money would go—or where the savings would come from. The $8.20 cheaper module looked great in a quote. It didn't look great in a TCO spreadsheet.
If you're evaluating a Quectel LTE module for your own product, don't ask 'Is the price fair?' Ask 'What does the total cost curve look like?' Certification time, band support, reference design quality, thermal behavior, engineering support—those are not soft factors. They are line items. And they show up on someone's P&L sooner or later.
