Fiber ONT Buying: 8 Questions I Ask Before I Sign an ONT Device Price Quote

When I started buying ONT hardware in 2019, I assumed a spec sheet was a product description. It isn't. It's a wish list, and two factories can interpret the same wish list in opposite directions while both staying technically accurate.

Six years, 40-odd vendors and a $2.4M annual CPE budget later, I have a fixed set of questions I run before I sign anything on an ont device price quote. These are the ones that actually move the number at the bottom of the sheet.

• What actually makes up the unit price?
• Is the lowest quote the one to sign?
• What do I verify before comparing prices at all?
• What is a "spectrum fiber ONT" and can anyone guarantee carrier compatibility?
• Why do identical specs come back 30% apart?
• What costs never appear on the quote?
• When should you not buy through a sourcing partner?
• How do I structure the comparison so I'm not fooling myself?

1. What actually makes up an ONT device price?

Ask for a line-level BOM, not a datasheet. On an indoor ONT, two lines do most of the work: the optical subassembly (BOSA) and the SoC. A tier-one BOSA and a reworked one look identical on a spec sheet, and the spread between them is often 15–25% of unit cost.

Then memory, radio, adapter, firmware. Here's something vendors won't tell you: the first quote is almost never the final price for an ongoing relationship, and it's frequently not even a complete price. I've had quotes where the power adapter was a separate line and quotes where it wasn't, and the two looked 8% apart until I added it back in. Plug type alone has killed more of my rollouts than chipset selection.

2. Is the lowest fiber ONT device quote the one to sign?

In Q3 2023 I ran a 4,000-unit indoor ONT tender. Low bid: $23.40 per unit, DDP. Middle bid: $27.90. I took the low one. Landed cost came out near $29.10 after replacement power adapters (quoted units shipped with EU plugs, we deploy in the US), a firmware reflash on the first 600 units, a 5.8% DOA rate, and return freight on the failures.

The "expensive" bid had included US adapters and a 2% spare pool. So the cheap quote cost me more, and cost me three weeks. Not great, not terrible. Expensive.

We now require every quote in landed cost per unit — freight, duty, adapters, spares, stated DOA allowance — before anything gets compared. That single policy change is the most valuable thing I've done in this job.

3. What do I verify before I compare prices at all?

PON type first. GPON, XG-PON, XGS-PON and EPON are not interchangeable, and I've watched a buyer order 2,000 units against a G.987 OLT because the spec sheet said "10G capable."

Per ITU-T G.984.2, GPON runs 2.488 Gbit/s downstream and 1.244 Gbit/s upstream, with upstream in the 1260–1360 nm band, downstream at 1480–1500 nm, and video overlay at 1550–1560 nm. XG-PON (G.987.2) moves to 9.953/2.488 Gbit/s; XGS-PON (G.9807.2) is 9.953 Gbit/s symmetric; EPON (IEEE 802.3ah) runs a 1.25 Gbit/s line rate.

Then: UNI port count, WiFi standard (802.11ac vs ax matters on unit price), management stack (OMCI per G.988, TR-069), laser safety class (IEC 60825-1 Class 1 for the optics), RoHS 2011/65/EU, and FCC Part 15 Subpart B Class B if you're deploying US residential. Ask for an interoperability report against the OLT you actually run, not one they ran in 2021.

4. What is a "spectrum fiber ont" — and can anyone guarantee carrier compatibility?

The phrase "spectrum fiber ont" gets used for two different things, and suppliers rarely say which. Sometimes it means the wavelength plan — the optical bands the unit's transceiver has to sit inside, per G.984.2. Sometimes it means an ONT built for a named carrier's network, in this case Spectrum (Charter). Those are very different asks.

If you need units certified on a specific carrier's network, you need that carrier's certification or an ODM test report showing the model passed it. A sourcing partner can't manufacture that paper. Any supplier promising guaranteed compatibility with every ISP is telling you they haven't tested — and I'd rather hear "here's what we can prove, here's what we can't" than a reassurance I can't put in a contract.

5. Why do two vendors quote the same ont device fiber spec 30% apart?

Usually four reasons. Chipset generation — a two-generation-old part costs less and behaves differently under concurrent load. Memory actually installed versus memory on the sheet. Whether the BOSA is new or reworked. And incoterms: EXW versus DDP is 10–15% by itself once freight and duty land.

Force the same revision and the same incoterm, and the 30% gap usually compresses to 8–12%. That residual difference is real and you can negotiate it. The first number was noise.

6. What costs never appear on the quote?

Interoperability and lab testing, which runs a few thousand dollars per model if you do it properly. Firmware customization for your management platform — cheap once, brutal across eight SKUs. The spare pool, budget 2–3%. RMA freight, which you eat in both directions. Certification per SKU, per market. Tariff changes, which nobody forecasts and everybody absorbs. And engineering time, which never appears in anyone's spreadsheet but shows up in your P&L as a project that slipped a quarter.

I now carry an explicit per-unit line for "support and failure handling." It's ugly. It's also the line that made me stop trusting sticker prices.

7. When should you not buy through a sourcing partner?

Three cases, and I'll say them plainly.

One: you need under roughly 200 units, once. The qualification overhead — samples, testing, documentation, the four weeks of back-and-forth — costs more than the delta you'd save. Buy local at the premium.

Two: you need a named carrier's certification held in your supplier's name, not just a test report. If a contract clause depends on it, a sourcing intermediary like LinkScope Sourcing 08 isn't the right counterparty for that requirement.

Three: your support model requires next-day replacement from local stock. That's a stocking commitment, not a sourcing one.

To be fair, none of this is a knock on sourcing partners. Moving containers and holding inventory in your metro are just different businesses, and pretending otherwise is how procurement people get fired.

8. How do I structure the comparison so I'm not fooling myself?

Columns: unit price, incoterm, landed cost per unit, stated DOA allowance, firmware revision, certification evidence, spare pool cost, lead time, payment terms, and one column I added after a bad February — who do I call at 2 a.m. and what do they actually do.

Minimum three vendors, same revision, same incoterm. Buy 5–10 samples before the big order; it's cheap and it catches the adapter-plug problem before the adapter-plug problem catches you. Then track the real numbers after deployment, not just the quote — my 2023 spreadsheet said $23.40 and my 2024 invoice history said $29.10, and only one of those is a fact.

Did the process save money? Yes. Was it worth the six weeks of tender work? Ask me after the next rollout.