InPlay IN120: The $0.50 BLE Chip That Could Replace Passive RFID

InPlay IN120 BLE chip on a smart label, positioned as a low-cost active alternative to passive RFID tags

Every passive RFID tag you’ve ever deployed is invisible until it passes within arm’s reach of a dedicated reader. You’ve accepted this for years because the alternative, sticking a BLE SoC on a disposable label, was absurd. An nRF52 costs $1.50+, sits in a 5×5mm QFN, and demands a power budget that laughs at thin-film batteries. You kept buying UHF RFID inlays at a dime apiece, kept installing fixed reader portals, and kept explaining to product managers why no, the customer’s iPhone can’t just “see” the tag.

The InPlay IN120 NanoBeacon changes this math. At roughly $0.50 in volume, in a 1.8 × 1.4mm wafer-level package, it broadcasts standard BLE advertisements that any smartphone or gateway within 50 meters can receive. No dedicated readers. No app with NFC-tap interaction. Just BLE.

But $0.50 BLE silicon doesn’t come without trade-offs, and the ones here are structural, not incidental. Before you rip RFID out of your next design, you need to understand exactly what this chip is, what it deliberately isn’t, and where those deliberate omissions will either liberate your design or sabotage it.

Disclosure: InPlay is not a sponsor of this publication. This is an independent technical evaluation.

What the NanoBeacon IN120 Actually Is (and Isn’t)

The IN120 is a transmit-only BLE beacon SoC. Read that again: transmit-only. There is no receive chain. No connection support. No GATT server, no pairing, no scan responses initiated by a remote device, no OTA firmware updates. It broadcasts BLE advertisements on a configurable interval, and that’s it.

This isn’t a cost-reduction compromise. It’s the entire architectural thesis. Removing the Rx path is what collapses the die size, the power consumption, and the price simultaneously. Every microamp you’d spend on listen windows, every square millimeter of Rx front-end silicon, every gate of connection-state management logic: gone. What remains is a tightly scoped transmitter with just enough peripherals to be useful.

Key specs that matter for your design:

  • Package: 1.8 × 1.4 mm WLCSP, smaller than most passive components on your BOM
  • Operating voltage: 1.1V to 3.6V. The 1.1V floor is the critical number, purpose-built for printed and thin-film battery compatibility
  • TX power: Configurable, with options suitable for 10–50+ meter range depending on antenna and environment
  • Advertising interval: Configurable from milliseconds to seconds
  • On-chip peripherals: GPIO, ADC, I²C, enough to read a thermistor, a humidity sensor, or a tamper switch and encode that data into the advertisement payload
  • Configuration: OTP (one-time programmable) registers, set at manufacturing. What you program on the line is what the chip does for its entire life.

Here’s how it stacks up against the obvious alternatives:

┌──────────────────────┬────────────────┬─────────────────┬──────────────┐
│ Parameter            │ IN120          │ Passive UHF RFID│ nRF52810     │
├──────────────────────┼────────────────┼─────────────────┼──────────────┤
│ Unit Cost (volume)   │ ~$0.50         │ ~$0.05–0.15     │ ~$1.50–2.00  │
│ Package Size         │ 1.8×1.4 mm     │ IC: ~0.5×0.5 mm │ 5×5 mm QFN   │
│ Read/Detect Range    │ 10–50+ m       │ 1–10 m (UHF)    │ 10–100+ m    │
│ Requires Battery     │ Yes (tiny)     │ No               │ Yes          │
│ Bidirectional Comms  │ No             │ Limited          │ Yes          │
│ Smartphone Readable  │ Yes (native)   │ No (needs UHF   │ Yes (native) │
│                      │                │  reader)         │              │
│ Sensor Integration   │ Yes (ADC, I²C) │ No               │ Yes (full)   │
│ In-Field Reconfig    │ No (OTP)       │ Limited          │ Yes (OTA)    │
└──────────────────────┴────────────────┴─────────────────┴──────────────┘

For context: the Dialog (now Renesas) DA14531 SmartBond TINY is the closest BLE competitor in the ultra-low-cost tier at roughly $0.80–1.00+, but it’s significantly larger and includes an Rx path with full connection support. More capable, but a different category. The IN120 targets applications where the DA14531 is still too much chip.

Form Factors That Were Previously RFID-Only Territory

This is where the IN120 earns its place as a legitimate BLE smart label chip. The combination of sub-2mm IC, 1.1V operating voltage, and on-chip ADC/I²C unlocks specific product designs that were previously stuck in RFID-or-nothing land:

Smart pharmaceutical labels. A thin-film battery (Enfucell, Blue Spark, or similar) plus the IN120 and a thermistor on a flex PCB, laminated into existing medication packaging. The label broadcasts temperature excursion data throughout the cold chain. Any BLE gateway in a warehouse or pharmacy receives it passively, with no handheld RFID reader and no line-of-sight requirement. The 1.1V minimum voltage is specifically what makes printed battery compatibility realistic here.

Disposable medical device tags. Single-use surgical instruments or implant packaging that broadcasts a unique device identifier and tamper status. Sterilization cycle tracking via a simple GPIO-based seal sensor. The form factor fits within existing sterile packaging without redesign.

Retail smart labels on high-value goods. Replace static UHF RFID tags with active BLE beacons that work with existing in-store BLE infrastructure and customer smartphones. Inventory visibility without dedicated RFID reader portals. This is the use case where existing BLE gateway deployments (already common for indoor positioning) create immediate infrastructure reuse.

Embedded-in-packaging freshness indicators. Food packaging with a printed battery and a simple ADC-based gas sensor or colorimetric indicator, broadcasting freshness status that a consumer’s phone can read.

An honest caveat: the pharmaceutical and freshness-indicator applications are near-horizon. Printed battery supply chains and flex PCB manufacturing for these form factors are maturing but not yet commodity. Retail smart labels and medical device tags on rigid-flex substrates are closer to production-ready today.

The Power Reality Check

Every engineer evaluating the IN120 asks the same question within 30 seconds: what powers it and for how long?

Coin cell (CR1225 or smaller): The proven path. A CR1225 delivers roughly 50 mAh. At a 1-second advertising interval with modest TX power, you’re looking at months of operation, potentially over a year at relaxed intervals. This is the safe choice for asset tags and reusable packaging.

Printed/thin-film batteries: This is the IN120’s design-center use case, and it’s where honesty matters. Printed batteries typically offer 1–10 mAh of capacity. At a 1-second advertising interval, a 5 mAh printed battery will last days to low weeks, not months. You need to match the power source to the application’s required lifetime. A pharmaceutical shipment that needs 72 hours of cold-chain monitoring? Feasible. A retail shelf tag that needs six months? Not with a printed battery alone.

Energy harvesting: Technically possible given the 1.1V operating floor, but the IN120 has no integrated harvesting circuitry. You’d add an external harvesting front-end plus a storage capacitor or micro-battery, which adds BOM cost, board area, and design complexity, partially eroding the IN120’s size and cost advantages.

The irreducible truth: any power source, no matter how minimal, is more than the zero-power requirement of passive RFID. This is the fundamental cost of going active. If your application genuinely cannot tolerate a battery, conceptually, economically, or physically, the IN120 is not your chip.

Where the IN120 Replaces Passive RFID (and Where It Doesn’t)

Time for a clear position.

The IN120 wins when:

  • Assets move through open or semi-structured environments (warehouses, retail floors, hospitals, logistics hubs) where installing dedicated RFID reader portals at every chokepoint is impractical or cost-prohibitive
  • Smartphone readability is a requirement, whether consumer-facing (product authentication, freshness checks) or field-service (technicians scanning with their phones instead of carrying RFID guns)
  • You need sensor data attached to the tag (temperature, humidity, tamper detection, usage state) not just a static identifier
  • Read range beyond 1 meter matters and you cannot guarantee reader proximity
  • Your deployment already has BLE gateway infrastructure or you’re planning to deploy it for other reasons (indoor positioning, occupancy sensing)

Passive RFID still wins when:

  • Assets never leave a tightly controlled chokepoint environment: library circulation, closed-loop manufacturing, portal-based dock-door logistics
  • Per-unit cost absolutely must be below $0.20. RFID inlays at $0.05–0.15 are 3–10× cheaper
  • Zero maintenance and effectively infinite shelf life are non-negotiable. No battery means no battery death, ever
  • The environment already has dense RFID reader infrastructure and zero BLE gateways
  • Read throughput is extreme, with hundreds of tags per second flying through a portal. UHF RFID’s anti-collision protocols are purpose-built for this scenario; BLE advertising on three channels is not

Use this as a decision framework:

Does the tag need to broadcast sensor data?
  ├─ YES → IN120
  └─ NO
      Does the tag need smartphone readability without dedicated hardware?
        ├─ YES → IN120
        └─ NO
            Is read range >1m required without fixed reader infrastructure?
              ├─ YES → IN120
              └─ NO
                  Is zero-power / infinite shelf life required?
                    ├─ YES → Passive RFID
                    └─ NO
                        Is unit cost <$0.20 mandatory?
                          ├─ YES → Passive RFID
                          └─ NO → IN120 (default to more capability)

A note on NFC (NXP NTAG and similar): if your use case is a deliberate tap-to-read interaction at <4cm range, NFC remains the right tool. That’s a fundamentally different interaction model than BLE broadcast. The IN120 doesn’t compete there; it competes where passive broadcast over distance matters.

Design Constraints You Must Internalize Before Committing

No receive path means no acknowledgment. You broadcast and hope a listener is in range. There is no delivery confirmation, no retry triggered by a NAK, no handshake. Your system architecture must assume eventual consistency. If you need transactional certainty that a specific tag was read at a specific moment, you need either RFID portal density or a full BLE SoC with connection support.

OTP configuration is permanent. Whatever advertising structure, interval, TX power, and sensor-mapping logic you program at the factory is fixed for the life of the device. The data in the advertisement can be dynamic: the ADC reads a thermistor and the current temperature value updates in the payload automatically. But the behavior (which sensor maps to which byte, the advertising interval, the TX power level) is burned in. Your manufacturing test and programming flow becomes critical. Get it wrong and you scrap the unit.

The antenna dominates your solution size. This is the most common misconception. The IN120 is 1.8 × 1.4 mm. A 2.4 GHz PCB trace antenna is 10–15 mm long. A chip antenna is 3–5 mm. The antenna, not the IC, sets your minimum form factor:

IN120 Total Solution (conceptual):

  ┌─────────────────────────────────┐
  │        PCB Trace Antenna        │  ~10–15 mm
  │         ~~~~~~~~~~~~            │
  │                                 │
  │   ┌───┐                        │
  │   │IN │ 1.8×1.4 mm             │
  │   │120│                        │
  │   └───┘    ┌────────────┐      │
  │            │ Thin-Film   │      │
  │            │ Battery     │      │
  │            └────────────┘      │
  └─────────────────────────────────┘

  The antenna and battery dominate total
  solution size, not the IC.

No protocol flexibility. This is BLE advertising only. No Bluetooth Mesh. No direction finding (AoA/AoD). No Coded PHY for extended range. If your roadmap requires any of these, you need different silicon.

Specifying the IN120 Into Your Next Design

The InPlay IN120 doesn’t replace all passive RFID. It creates a category that didn’t previously exist: active, sensor-capable, BLE-native tags at near-RFID economics. For hardware engineers, the decision framework is specific, not universal. Does your application need the intelligence, range, and ecosystem compatibility that BLE provides? Can you tolerate a power source, even a tiny, disposable one? If both answers are yes, the IN120 makes form factors possible that were genuinely impossible six months ago.

If your world is chokepoint readers, sub-dime unit costs, and zero-power mandates, passive RFID remains the correct choice. That’s not a consolation. It’s an engineering decision. Know your application, know your constraints, and pick the technology that actually fits.

Hubble Network connects BLE tags like the IN120 directly to satellites—no gateways, no terrestrial infrastructure. See how it works →