I Used to Think a Lower Invoice Was a Win
In my first year managing purchasing for a mid-sized IoT hardware company, I celebrated like I'd won a prize. I'd found a distributor offering the Semtech SX1276 LoRa transceiver at $0.45 less per unit than our usual supplier. For a 5,000-unit order, that was $2,250 straight to the bottom line. Or so I thought.
The $0.45 quote turned into somewhat more than that. After adding minimum order quantities, a separate shipping fee from a different warehouse, a $75 'documentation fee' for the Certificate of Origin, and a $45 charge for a customs-compliant commercial invoice (the second time they sent it), the so-called savings evaporated. That $2,250 gain? Gone. Actually, worse. It cost us roughly $180 more than if I'd just placed the order with our regular vendor.
It wasn't the supplier's fault. It was mine. I was looking at the wrong number.
What I Thought I Was Buying vs. What Was Actually on the Table
When I took over purchasing in 2020, my mandate was simple: reduce component costs. The engineering team needed Semtech LoRa transceivers (the SX1262 for our new sensor line) and, after the Sierra Wireless acquisition by Semtech, we started integrating cellular modules too. The procurement directive was clear—get the best price.
It took me about 18 months and three separate purchasing embarrassments to realize the difference between a low unit price and a low total cost of ownership (TCO).
The first embarrassment was the SX1276 order I mentioned. The second came when we switched to a budget supplier for Airlink routers. They were $40 cheaper per unit. But they didn't provide pre-paid shipping labels for returns, had a 14-day lead time vs. our usual 5-day, and their invoicing system didn't support our ERP integration. Our accounting team spent 6 extra hours per order manually matching invoices to POs. Six hours. For 12 orders that year. That's 72 hours of someone's salary to 'save' $480 on routers.
The Problems I Didn't See Until They Hit My Budget
The third embarrassment was the worst. We needed 2,500 units of the Semtech SX1272 for a production run. A new vendor offered what looked like an incredible price—$0.78 less per unit. I jumped. I didn't check their lead time guarantee properly. They shipped late. The production line stopped for 36 hours. Our VP of Operations had to explain to the client why the delivery date slipped. That conversation cost us goodwill I can't price on a spreadsheet.
Now I keep a running list of hidden costs that I check before signing any PO:
- Inventory carrying cost: Buying bulk to get a lower unit price means cash tied up on the shelf. For us, carrying cost runs about 18-25% of the component value annually.
- Administrative friction: Non-standard invoices, manual data entry, inconsistent part numbering. If a vendor can't talk to my ERP, that's a cost.
- Testing & revalidation: We switched to a cheaper batch of Gennum signal integrity chips once. They worked in 98% of units. That 2% failure rate cost us $12,000 in rework and 3 days of delay.
- Opportunity cost of my time: Chasing a 5% saving on RClamp protection diodes that took me 8 hours to evaluate vs. just ordering from the regular vendor for 2% more. Not worth it.
The Real Cost of Switching Semtech Suppliers
It's tempting to think that switching a LoRa module supplier is a straightforward price comparison. The SX1262 is the SX1262, right? Pin-compatible, same specs. But identical specs from different vendors can result in wildly different outcomes when you factor in:
- Stock reliability: Our regular distributor kept 3,000+ SX1262s in their on-hand inventory. The discount vendor had to special order from Semtech—adding 4 weeks to lead time.
- Warranty & RMA process: One supplier replaced defective modules within 48 hours. The other required a 10-day evaluation before they'd ship replacements.
- Consistent component sourcing: The discount source sometimes sent SX1262 chips from different date codes or batches, requiring us to re-certify them in our design.
In my 2024 vendor consolidation project, I cut from 12 suppliers to 6. We lost some unit price advantages. But our total procurement cost dropped by roughly 14% when I accounted for the reduced admin overhead, fewer RMAs, and less time wasted. The most expensive supplier on paper turned out to be the cheapest in practice.
What I Do Now (Simple Changes, Big Difference)
After 5 years of managing these relationships, I've settled on a simple checklist before comparing quotes:
- Specs, timeline, payment terms. In that order. Get those locked before talking price.
- Check the hidden fees. Shipping, setup, documentation, testing. Ask upfront.
- Calculate total cycle time. From order to received. Days matter more than dollars sometimes.
- One test-run order. Never switch a critical component (like LoRa transceivers for a live product) without a small test order first.
The $500 quote that turned into $800 after rush fees, separate shipping, and a revision charge? The $650 all-inclusive quote from our trusted supplier was actually cheaper. Period.
Now I calculate TCO before comparing any vendor quotes for Semtech products. I'm not saying you should always go with the most expensive option. But if you haven't accounted for what happens after the transaction, you're not comparing costs. You're guessing. And guessing cost me thousands before I learned.
