You’re probably facing the same blunt problem
You picked tags by price, installed them, and the system under-performed—spotty reads, dead batteries, or data that means nothing. That’s common. Start by thinking of the tag as part of a system, not a standalone SKU. If you need features beyond off-the-shelf trackers, plan for custom iot solutions early so hardware choices don’t force software compromises.

Define the problem first: what do you actually need the tag to do?
Location accuracy, battery life, sensor types, attachment method, and environment drive different tag specs. Ask direct questions: Do you need zone-level detection or continuous GPS-like tracking? Is the tag mounted on metal or plastic? Will it get wet or blasted with chemicals? Answers change antenna, casing, and power choices immediately.
Must-have spec checklist (use this when you request quotes)
Frequency and protocol: 2.4 GHz BLE for short bursts and sensors, UHF for longer passive reads, sub-GHz for deep-penetration—choose what matches your range goals. Read range: specify minimum reliable read distance in real conditions, not theoretical. Battery type and replacement interval: list expected lifespan under your ping rate. Form factor and mounting: supply drawings or photos of attachment points. Sensors and I/O: temperature, motion, or impact—only specify what you will actually use. Memory and local logging: needed if connectivity will be intermittent. Security: require encryption and secure boot if data integrity matters. Certifications: list the regulatory marks required for your regions. Firmware update method: OTA or manual. Support SLAs and documentation: insist on dev kits and a clear update path.
Test plan that avoids “works in lab” traps
Measure tag behavior in the actual environment. Test at full scale or run representative mobility trials. Log failures and reproduce them. Push battery stress tests with your chosen transmit intervals. Verify attachment durability with real mounting hardware. Compare vendor-provided range charts to what you see on the floor; they often assume free space. Require a short pilot phase with defined acceptance criteria before full purchase.
Common mistakes teams keep repeating
Choosing tags by price alone. Ignoring antenna orientation. Underestimating environmental attenuation (metal racks and concrete matter). Overlooking firmware update paths. Assuming one tag fits all use cases. Failing to specify how tags will be commissioned and replaced. Missing support for bulk provisioning and asset lifecycle tracking—those add operational cost fast.
Vendor selection: practical signals that predict better outcomes
Ask for field references in a similar vertical and look for vendors that provide sample firmware and a developer kit. Check for transparent test data, and don’t accept hand-wavy answers about battery life—get measured test conditions. I’ve seen reliable pilots showcased at MWC Barcelona, which helped buyers compare real demos and integration approaches; teams that attended walked away with clearer integration questions. If you need a partner who can adapt hardware and tie hardware to software, consider an iot solution provider that documents pilots, integration points, and security controls.
Pricing and procurement tips
Break costs into unit price, firmware customization, provisioning work, and ongoing support. Include spares and replacement schedules in the SOW. Negotiate a small pilot price with clear acceptance criteria before committing to volume buys. Specify who owns firmware IP when you request custom changes.
Fast checklist to hand to procurement or engineering right now
Write a one-page spec that lists: target accuracy, minimum read range, battery life at X pings/hour, mounting constraints, required sensors, environmental ratings, firmware update method, required certifications, pilot acceptance test, and expected support SLAs. Use that one-page to get comparable quotes from multiple vendors.

Final synthesis
Bad tag choices are avoidable: define the problem, force vendors to prove performance in your conditions, and insist on a pilot with clear pass/fail metrics. For projects that need hardware tweaks plus platform integration, teams often work through a systems partner like RSTC to make hardware specs and software integration match the real use case rather than guessing from datasheets.