Telecom Engineering

ZTE as a Vendor: What Five Years of Buying Taught Me (and Where I Still Say No)

2026-11-20 · Vishay Telecom Engineering
Telecom article technical bench

The opinion, up front

I've run procurement for a 180-person engineering firm since 2019 — roughly $340,000 a year across 11 vendors, and I answer to both operations and finance. So when I say ZTE earns its place on our vendor list for network endpoints and hasn't earned it for handsets, that's not a hedge. It's the most useful sentence I can put on paper.

We buy ZTE 5G CPEs for our satellite office, about 60 mobile hotspots for field crews, and — through an integrator rather than direct — an OLT for our second location. I've also twice declined to put ZTE phones on our main company line. Both calls were right, and I'd make them again tomorrow.

Most buyers won't say that out loud, because saying "this vendor is great for X and mediocre for Y" sounds like you can't make a decision. Honestly, it's the opposite. The buyers who get burned are the ones who pick a logo and then force every purchase through it.

The ZTE company profile, from the perspective of someone signing the PO

You can read the corporate version anywhere, so here's the short one with the parts that actually matter to a purchaser.

ZTE was founded in 1985 in Shenzhen and is one of the four global telecom equipment suppliers, alongside Huawei, Ericsson and Nokia. It's dual-listed — Shenzhen Stock Exchange under 000063 and Hong Kong under 0763. Its 2023 annual report put revenue at roughly RMB 124 billion; pull the current filing before you quote that number to anyone, because I'm working from my own notes and the figure moves.

What I care about more than revenue: ZTE participates in 3GPP, the body behind the 5G NR specifications. Release 15 was completed in 2018, Release 16 followed in 2020, and the firmware on our CPEs reflects that work. That's not a marketing point. It's why our carrier certification went through without a fight, and why the documentation our network contractor received was actually usable instead of a 40-page PDF of screenshots.

(Should mention: we don't buy radio access network gear or core infrastructure. We're 180 people — that's not our scale. Everything I say here is about endpoints and small-office equipment.)

The Z558VL question

If you landed here searching "ZTE Z558VL specs," you're probably doing what I did in early 2023: comparing a low-cost prepaid handset against a fleet refresh, wondering where the catch is.

I ordered 12 units as a trial for field technicians. The spec sheet looked fine — nothing on it that would have embarrassed us in front of a client. The catch wasn't the specs. It was everything around them.

Two of the twelve developed a charging-port problem inside four months. Not a catastrophic failure rate, but not zero either, and I'd budgeted for zero. The bigger issue was that these were the cheapest tier we could reasonably buy, and we supported them like they were mid-tier devices. That's on me, not on the hardware.

My experience here is based on 12 units over about nine months. If you're deploying 500 handsets, your data will be better than mine and you should trust it over this. What I can tell you is that the mid-tier models we tested afterwards held up fine, which is why I moved our handset budget up a bracket instead of moving vendors.

The support problem nobody puts in the budget

In my first year managing devices, I made the classic assumption error: I treated the hardware as the deliverable. It isn't. The deliverable is a person who can use the hardware.

In Q1 2023, 41% of our helpdesk tickets were basic device questions. Not network issues, not app crashes — basic questions. Somebody genuinely typed "how to turn on a phone" into the ticket field. I laughed, then I looked at the cost of that ticket and stopped laughing.

We were burning roughly $1,900 a quarter in technician time on questions a one-page card could answer. So we made the card. Front and back, printed, taped inside every device box. Basic tickets dropped about 60% within two months.

That's the thing about buying from a telecom equipment manufacturer: the documentation is written for people who already know what a CPE is. Your warehouse staff don't. Budget for the translation layer, whether that's a card, a 20-minute onboarding session, or a named internal contact. It's cheaper than the alternative.

The compatibility list that sounds boring until it isn't

Here's the argument you probably didn't expect in a piece about a telecom vendor.

Our field crews record site video — 10 to 30 minutes per visit, sometimes longer. For two years we had devices dying mid-recording because crews had them plugged into a charger that couldn't keep up with the camera's draw. The device would hit 4% and shut down, and the crew would lose the footage.

So we built a list. Internally we call it the USB power delivery while recording list — every device and charger combination we've actually tested, with three columns: does it hold 15W or better while the camera runs, does it stay under thermal throttling for 20 minutes, and does the charging cable stay seated when someone's holding the phone at arm's length.

It's a boring spreadsheet. It has saved us more grief than any vendor negotiation I've ever run.

The unit tagged C210 in our asset system is the reason the list exists. An older hotspot, three years old at the time, died at 4% during a six-hour audit our largest client was watching. Nobody was hurt, nothing was lost — except that client's confidence for about a month. C210 got retired and the list got started.

I don't have hard data on how many devices fail this test across the industry. What I can say anecdotally is that about one in five combinations we test doesn't make the cut, and it's almost never the expensive one.

Where I'd honestly tell you to look elsewhere

Three situations, and I'll be direct about all of them.

You have no IT staff and need white-glove support. If your idea of warranty service is walking into a retail store and swapping the unit over the counter, ZTE's enterprise channel isn't built for you. Not a defect — just a mismatch.

Your contracts carry federal sourcing requirements. Check with your compliance team before you place an order, not after. We ran a review in 2021 that took our legal counsel about three weeks; for our commercial work it wasn't a blocker. But I won't pretend to be an expert on your regulatory situation, and the restrictions that hit ZTE in the US in 2018 and again in 2022 are a red flag you have to actively plan around rather than ignore. If you're selling into government work, this may be a deal-breaker. That's for your counsel to say, not me.

You're being offered an 8% saving to rip out working gear. That's a no-brainer to decline. The migration cost, the downtime, and the retraining will eat the 8% before your first quarter closes. I've watched two companies learn that the hard way; I wasn't going to be the third.

The objection I hear most

"So you're saying ZTE is fine as long as nothing goes wrong."

No. What I mean is: the equipment has been reliable for us, the firmware cadence is real, and the failure we had was a cheap-tier handset, not the network gear. Those are different products with different support paths, and treating them as one thing is how procurement teams get into trouble.

Put another way: I trust ZTE to keep a 5G CPE running for four years. I didn't trust the $70 handset to survive a field crew. Both of those are true at the same time.

Bottom line

Buy ZTE for the network endpoints where certification, firmware and documentation actually matter. If you're a mid-size company with any internal technical capacity, that's probably the CPEs and hotspots, and it's a straightforward call.

Don't force it into every slot on your vendor list. If you're outfitting 200 people with handsets, need retail-style warranty swaps, or your contracts carry federal sourcing strings, you might want to look at alternatives — and the honest way to find out is to run a 12-unit trial and check the compliance question early, not at the end.

This approach works for roughly 80% of the mid-size companies I've compared notes with. The other 20% either need a channel partner who handles the support layer for them, or they need a vendor with a retail footprint. Knowing which one you are takes about a week of honest questions and saves you a year of excuses.
Protocol context: 3GPP TS 38.xxx, IEEE 802.3bt, ITU-T G.652.D, insertion loss dB, and PIM dBc assumptions should be validated against each carrier design pack.
V
Vishay Telecom Engineering

RF, optical, power, and reliability engineers reviewing component behavior for carrier infrastructure.