Buyer checklist

STB Buyer's Checklist: what to verify before choosing boxes

A good set-top box is not just a chipset and a price. It is the hardware, firmware, apps, content protection, remote control, fleet management, support and logistics that keep a TV service working after the first shipment lands.

Use this checklist before sample validation, vendor shortlisting or a bulk order. It is written for ISPs, IPTV and OTT operators, telcos, hospitality and MDU projects, and distributors evaluating boxes for operator clients.

Hardware + software stack
Sample before bulk order
Fleet management matters

Start here

Buy the service platform, not just the box

A low-cost retail Android box can look attractive on a spreadsheet, but managed TV buyers need a device that can be branded, provisioned, locked, updated and supported across thousands of homes, hotel rooms or partner deployments.

The right STB depends on the service model: managed IPTV on a private network, OTT-first streaming, hybrid IPTV and OTT, hospitality or MDU television, or distributor resale. The checklist is the same, but the weight of each item changes.

The practical rule

If a requirement affects subscriber experience, content access, support cost or fleet control, verify it on a real sample before signing off the order.

Use cases

Match the box to the service you run

The same model can serve several projects, but the buying criteria are different. Start with the service, then choose the hardware tier.

Managed IPTV

Prioritize Ethernet, multicast support, stable firmware, a simple launcher, remote diagnostics and predictable decoding for live TV.

OTT-first TV

Prioritize app performance, DRM readiness, storage headroom, Wi-Fi behavior, adaptive streaming and a subscriber-friendly remote.

Hybrid IPTV and OTT

Check that one device can move between multicast live TV, unicast VOD, catch-up, portals and operator apps without confusing the viewer.

Hospitality and MDU

Look for locked-down UX, no personal-account dependency, centralized settings, bulk provisioning and easy replacement in the field.

Distributor evaluation

Validate packaging, accessory options, warranty process, localization, logistics and whether the vendor can support operator-specific builds.

The checklist

What to verify before buying STBs

Treat every row as a sample-test item, not a brochure claim. A good vendor should be able to prove the answer on real hardware.

  1. Chipset and platform maturity

    Why it matters
    The SoC defines decoding, DRM tier, driver stability, thermals and how long firmware can be maintained.
    Buyer note
    Ask what platform the vendor already ships at scale, not only what can be built as a one-off.
  2. RAM and storage

    Why it matters
    Too little memory makes launchers and OTT apps feel slow; too little storage limits apps, logs and updates.
    Buyer note
    Lean IPTV can run lighter. App-heavy Android deployments need more headroom.
  3. Video, audio and 4K requirements

    Why it matters
    Codec, HDR, resolution and audio support decide whether the service plays smoothly on the TVs subscribers actually use.
    Buyer note
    Test real live channels and VOD assets, not only demo clips.
  4. Ethernet and multicast behavior

    Why it matters
    Managed IPTV and hospitality networks often depend on wired Ethernet, IGMP and stable multicast playback.
    Buyer note
    If multicast matters, test it on the target switch and network design.
  5. Wi-Fi and off-net OTT

    Why it matters
    OTT, secondary rooms and many residential installs rely on Wi-Fi quality, roaming behavior and adaptive streaming.
    Buyer note
    Test weak-signal rooms and congested apartments, not only a clean lab.
  6. DRM and CAS readiness

    Why it matters
    Premium content needs the right DRM level, key provisioning, partner integration and sometimes CAS support.
    Buyer note
    Confirm the actual content path: Widevine, Verimatrix, portal app, operator agreement and factory provisioning.
  7. Operating system and app strategy

    Why it matters
    AOSP, certified Android TV and Linux each change app availability, certification cost, update control and launch speed.
    Buyer note
    Choose the OS around the apps and control model, not around a generic platform preference.
  8. Device management and OTA

    Why it matters
    Without remote provisioning, diagnostics, staged updates and locking, every field issue becomes expensive.
    Buyer note
    Ask to see the DMS workflow before approving the device.
  9. Remote control and daily UX

    Why it matters
    The remote, launcher, boot flow and settings screens shape the subscriber's daily experience more than a spec sheet does.
    Buyer note
    Test with non-technical users and check button layout, IR/Bluetooth behavior and localization.
  10. Branding, packaging and accessories

    Why it matters
    The box, remote, power supply, HDMI cable, labels and quick-start guide all affect support and perceived quality.
    Buyer note
    Confirm plugs, languages, labels, carton layout and spare accessory availability early.
  11. Warranty, spares and logistics

    Why it matters
    Bulk hardware is an operations program: lead times, RMA, spare units and shipment routing matter after launch.
    Buyer note
    Separate evaluation-sample shipping from production-order logistics.
  12. Vendor support and lifecycle

    Why it matters
    A box that works today still needs firmware, app updates, security fixes and replacement planning later.
    Buyer note
    Prefer vendors that can explain the support path for the whole device life.

The best choice is usually the device that removes the most launch and support risk, not the one with the longest spec list.

Red flags

Warning signs before a bulk order

Most STB problems are visible during evaluation if the buyer tests the right things.

  • The vendor offers a retail Android box with no operator firmware, launcher control or fleet management.
  • DRM, CAS or premium-app support is described vaguely, without a clear provisioning and agreement path.
  • OTA updates are manual, all-at-once or depend on subscribers doing the right thing.
  • There is no way to lock, suspend, reconfigure or diagnose devices remotely.
  • Ethernet, multicast or Wi-Fi behavior is promised but not demonstrated on the target network.
  • Packaging, accessories, plugs, labels or manuals are treated as afterthoughts.
  • The supplier cannot explain warranty handling, spare units, firmware lifecycle or production logistics.

Sample validation

What to test on the sample box

A sample is not a souvenir. It is the proof that the device can become a managed fleet.

Cold boot into the branded launcher and confirm the first-screen experience.
Play live IPTV, OTT streams, VOD and catch-up from the real service sources.
Test multicast or portal behavior on the target network, not only in a lab.
Verify DRM-protected content and any premium apps that the service requires.
Push an app or firmware update through the management system.
Confirm the device appears in DMS with diagnostics, groups and remote actions.
Try suspend, net-lock or kiosk/app-lock behavior if the commercial model needs it.
Check remote-control feel, button mapping, pairing and support calls a subscriber might make.
Run the box long enough to catch heat, reboot, Wi-Fi or memory issues.
Review packaging, plugs, labels, accessories and localized quick-start materials.

Where inext fits

We help validate the whole stack

inext supplies the hardware, firmware, launcher, IPTV app, Alcatraz DMS, OTA, branding and worldwide B2B logistics as one managed STB stack. That means the same vendor can answer the hardware question, the software question and the rollout question before a bulk order.

FAQ

Common questions

Talk to us

Validate the box before the rollout

Tell us your service model, network, app requirements and target price tier. We'll help choose the right inext STB, customize a sample and prove the stack before a production order.