NXP has launched UCODE Nxm, the newest member of its UCODE RAIN RFID family β a chip built around one idea: more data lives on the tag itself. The chip carries 880 bits of memory that can be split between the EPC and user memory banks, and NXP is positioning it squarely for Digital Product Passport (DPP), traceability, and industrial IoT programs.
If you buy UHF RFID labels, here's the short version of what changed this week β and what didn't.
The Specs That Matter
| Parameter | UCODE Nxm | Why a buyer cares |
|---|---|---|
| Total memory | 880 bits, shared between EPC & user banks | Room for lifecycle data, not just a serial number |
| Configurations | 3 options, chosen at encoding (up to 496-bit EPC or 752-bit user memory) | One part number can serve several applications |
| Read sensitivity | β24 dBm (write β22 dBm) | Reliable reads in marginal RF environments |
| Data integrity | Memory Safeguard with ECC; TID parity protection | On-tag data survives bit errors without a database lookup |
| Privacy | Standards-based Untraceable command | Mask sensitive fields post-sale without killing the tag |
| Endurance | 100K write cycles, 20-year data retention, β40 Β°C to +85 Β°C | Survives industrial and outdoor duty cycles |
All figures are from NXP's launch materials and product page β verify against the official datasheet before designing anything in. That's the same advice we give for every chip.
Why NXP Built This Now
The driver is regulation. The EU's Digital Product Passport program will require many product categories to carry lifecycle and sustainability data accessible at the item level. Most DPP implementations lean on a QR code or NFC tap that resolves to a cloud record β but UHF RAIN RFID has a structural advantage in logistics: a single reader can process hundreds of thousands of tagged items per hour without line of sight. The gap has been memory: a standard 96-bit EPC holds a serial number, not a data record.
UCODE Nxm is NXP's answer: enough on-tag memory to store build records, lot numbers, status updates, and compliance data locally β readable even when the network isn't. NXP is also running a public webinar on the chip on September 8, 2026, which tells you they expect this to move beyond engineering blogs into procurement conversations.
What It Means for Buyers β Three Practical Takeaways
1. If you ship to the EU, start asking about memory budgets
You don't need to redesign anything today. But if your category is on a DPP roadmap β textiles, batteries, electronics, apparel are the early movers β add one line to your next RFQ: "Must support β₯512-bit user memory with a migration path." Tags live in supply chains for years; specifying 96-bit-only EPC in 2026 for a program shipping in 2028 is how requalification costs get created.
2. One chip, fewer SKUs β the quiet cost win
Because the EPC/user split is configured at encoding rather than fixed in silicon, a converter can stock one inlay and serve multiple applications. For you, that eventually means fewer minimum-order quantities to stitch together and less risk of a discontinued part number mid-program. This is the same consolidation logic the industry saw with UCODE 9, now extended to high-memory designs.
3. Encoding competence matters more than it used to
When memory configuration happens at encoding, your tag supplier's encoding process stops being a commodity step. Configurable memory written wrong is worse than small memory written right. If a factory can't show you their encoding verification workflow β write, read-back, 100% functional test β that's a reason to keep shopping, regardless of whose chip is inside.
The Context Buyers Should Know
The Nxm doesn't arrive alone. NXP launched UCODE X in January 2026, and by mid-August Avery Dennison was already shipping ARC-certified inlays built on it β including a globally tuned 42 Γ 16 mm part that covers the full 860β960 MHz band with one SKU. The lesson for procurement: new silicon now reaches catalog, ARC-certified inlays in months, not years. Waiting for "the chip to mature" before asking your supplier about it is no longer a safe default β the qualification queue is the bottleneck, not the chip availability.
What We're Doing About It
We build UHF labels on both NXP UCODE and Impinj Monza family inlays from our roll-to-roll line in Xiamen. For current programs, standard UCODE-class parts remain the shipping workhorse β proven, ARC-covered where needed, and cost-effective at volume. As Nxm-based inlays reach converters, we'll run them through the same qualification path we use for every new inlay: read-range testing on the target materials, encoding verification, and full-batch QC before anything ships.
If you're planning a DPP-pilot or a data-rich tracking program, tell us the target category and region β we'll spec the memory budget with you and quote the current best-fit chip honestly, including when the honest answer is "today's standard chip is enough."
Planning a data-rich RFID program?
Factory-direct UHF labels with inlay selection advice, pre-encoding, and 100% QC β quote back within 24 hours.
Get a Quote within 24h