UCODE 9 / SL3S1206 (UCODE 9) / SL3S1216 (UCODE 9xe) / SL3S1005 (UCODE 9xm) Reference
NXP UCODE 9
UHF Chip Technical Encyclopedia (Memory, Commands, Sensitivity, Deployment)
Quick answer
UCODE 9 (NXP SL3S1206, with UCODE 9xe = SL3S1216 and UCODE 9xm = SL3S1005) is the workhorse UHF inlay chip of the item-level retail era. Shipping since 2020, it extends the EPC Gen2 v2 standard with a best-in-class read sensitivity (-23.5 dBm), a self-adjust sensitivity mode, a fast Session-0-to-Session-2 transition, optional Untraceable and Authenticate commands, and sufficient user memory for a 96-bit EPC plus backup serial data. It is the chip behind most of the retail apparel, linen-management, supply-chain, and library RFID volume shipped since 2021.
- Read sensitivity -23.5 dBm best-in-class — ~1.4 dB better than Monza R6 (-22.1 dBm) and ~0.5 dB better than UCODE 8 (-23 dBm), translating to ~15% longer practical read range on the same tag antenna design. At 30 dBm reader output on a 6 dBi circular antenna over free air, that is the difference between a 10-12 m UCODE 9 read envelope and an 8-10 m UCODE 8 envelope — critical for retail POS portal read rates (the typical retail requirement is >99% first-pass read on a 20-item basket at 1-1.5 m gate distance) and for dock-door portal reads on mixed-product logistics pallets where liquid or metallized SKUs shorten every other chip's range.
- EPC Gen2 v2 full feature set. Untraceable, Authenticate, Challenge and File Open commands supported, with the stronger Gen2 v2 crypto suite 0x0002 (extended 128-bit challenge HMAC) available alongside the short-form suite 0x0001. Untraceable enables privacy-preserving read modes required by the CEN CWA 16924 EU retail framework and anticipated EU retail deregulation updates; Authenticate enables chip-level authenticity checks for brand-protection overlays on pharmaceutical, luxury-goods and cosmetics programs.
- Self-Adjust Sensitivity: a unique UCODE 9 feature that calibrates the chip's sensitivity to the antenna impedance in-situ at first power-up. Converters use it to normalize performance across SKU-specific inlay layouts without retuning the chip's reference parameters, which in practice adds 0.5-1.5 dB of useful forward-link margin on antennas that are mechanically constrained (small-format inlays, anti-metal foils with narrow bandwidth) and cannot be perfectly impedance-matched to the chip.
At a glance
Use these short answers to decide whether this page matches the project before moving into the detail.
Key takeaway
Read sensitivity -23.5 dBm best-in-class — ~1.4 dB better than Monza R6 (-22.1 dBm) and ~0.5 dB better than UCODE 8 (-23 dBm), translating to ~15% longer practical read range on the same tag antenna design. At 30 dBm reader output on a 6 dBi circular antenna over free air, that is the difference between a 10-12 m UCODE 9 read envelope and an 8-10 m UCODE 8 envelope — critical for retail POS portal read rates (the typical retail requirement is >99% first-pass read on a 20-item basket at 1-1.5 m gate distance) and for dock-door portal reads on mixed-product logistics pallets where liquid or metallized SKUs shorten every other chip's range.
Family and part numbers
UCODE 9 — NXP part number SL3S1206 (per the SL3S1206 product data sheet). The baseline UCODE 9 chip with up to 96-bit EPC, 32-bit user memory option, 32-bit Kill passwor...
Next step
Ready to move forward? Start your inquiry to get specific answers for this project.
Request UCODE 9 inlay samplesFamily and part numbers
- UCODE 9 — NXP part number SL3S1206 (per the SL3S1206 product data sheet). The baseline UCODE 9 chip with up to 96-bit EPC, 32-bit user memory option, 32-bit Kill password, 32-bit Access password and a 96-bit factory-unique TID. Launched in 2020; -23.5 dBm best-in-class read sensitivity, -18 dBm write sensitivity per the datasheet's RF characteristics section.
- UCODE 9xe — NXP part number SL3S1216 (per the SL3S1216 Rev. 3.3 product data sheet, 12 February 2025). Extended-EPC variant supporting 128 bits of EPC memory (vs 96-bit on UCODE 9 base) plus the standard UCODE 9 feature set, no user memory. Targeting deployments that need a longer identifier encoding (DoD MIL-STD-130N UII, GS1 SGTIN-198, defense / aerospace 128-bit identifiers).
- UCODE 9xm — NXP part number SL3S1005 (per the SL3S1005 Rev. 3.1 product data sheet, 12 February 2025). Configurable-memory industrial variant with up to 496 bits EPC and up to 752 bits user memory in three customer-selectable allocations, targeting industrial and supply-chain applications that need a serialized item record beyond the EPC alone. Typical uses include full GTIN + expiry + lot + maintenance-counter encoding on aerospace spares or a per-item care-label record for hospitality linen programs with multi-vendor laundry processing.
- Strap form factors: NXP sells UCODE 9 as wafer, tested die on 12" wafers (migrated from 8" in 2023 to meet demand), or as pre-assembled straps from Smartrac, Avery Dennison, Arizon, Beontag and other licensed strap assemblers. Inlays are then converted by dozens of downstream inlay houses including Proud Tek's partner network; reference antennas with official UCODE 9 tuning include Avery's AD-Dogbone (UCODE 9 revision), AD-172u9 apparel inlay, AD-356u9, Smartrac DogBone-r6 (dual UCODE 8 / UCODE 9 compatible), MiniWeb, and Arizon AZ-9662 / AZ-9762.
- EPC Gen2 v2 compliance — full. Supports all the new v2 commands (Untraceable, Authenticate with both crypto suites, Challenge, File Open / File Privilege, ReadProtect subset) per the June 2018 GS1 v2.1 conformance test suite. This is the practical difference between UCODE 9 and pre-2018 chips — retailers requiring v2 Untraceable for privacy compliance specifically call out UCODE 9 or later silicon in their tender documents, and the ISO/IEC 18000-63:2019 certification is maintained.
- Operating temperature — -40 °C to +85 °C for normal operation, up to +125 °C for short excursions during cure-press or autoclave cycles (NXP specifies max 30 minutes cumulative lifetime exposure at peak). For sustained high-temperature use (tire-cure at 200 °C/40 min, autoclave 134 °C/18 min repeated hundreds of times) use the UCODE 9xe extended variant where available, or specify Monza R6-P which has documented tire-cure performance and Alien Higgs-9 for higher-temperature industrial work.
- Counterfeit watch — the UCODE 9 silicon is specific; chips marked 'UCODE-compatible' often ship as unmarked Impinj Monza R6 or NXP UCODE 7/7xm silicon with relabeled packaging, or — increasingly since 2024 — as cloned wafers produced by unauthorized Chinese fabs lacking the full Gen2 v2 Authenticate implementation. Authentic UCODE 9 returns TID with EPC class identifier 0xE2 in bits 00-07 plus the NXP mask designer prefix in bits 08-19, followed by an NXP-assigned model-ID field per the SL3S1206 datasheet's TID structure section. Incoming inspection should verify the model ID against the NXP datasheet, sample 200-500 tags per lot for serial uniqueness, and occasionally round-trip the Authenticate command against a known-good reader key to confirm crypto suite support — clones often fail this check.
Memory architecture
- Four EPC Gen2 memory banks addressed per ISO/IEC 18000-63 Section 6.3.2.1.2. Bank 00 = Reserved (Kill password at bit 0-31, Access password at bit 32-63, both 32 bits). Bank 01 = EPC (CRC-16 bits 0-15 + Protocol Control bits 16-31 + EPC starting at bit 32). Bank 10 = TID (Tag ID, read-only, 96 bits). Bank 11 = User memory (32 bits on SL3S4011, 96 bits on SL3S4021).
- EPC memory bank 01 — 16 bits CRC + 16 bits Protocol Control + 96 bits EPC by default. Readers can extend the stored EPC to 128 or more bits by reconfiguring the PC word's Length field (bits 21-15 encoding length in 16-bit words up to 31 words / 496 bits), at the cost of reducing the effective bank allocation for other Gen2 v2 extensions (XPC_W1, XPC_W2 extensions live in the same address space per the GS1 v2.1 spec Section 6.3.2.1.2.3).
- TID memory bank 10 — 96 bits, factory-programmed, read-only, verified at final test before the wafer leaves NXP fab. Structure per the SL3S1206 datasheet: bits 00–07 = 0xE2 (EPC class identifier per Gen2 v2), bits 08–19 = NXP mask designer prefix, bits 20–31 = chip-specific TID model number (consult the SL3S1206 / SL3S1216 / SL3S1005 datasheets for the exact model-ID values for UCODE 9, UCODE 9xe and UCODE 9xm respectively), bits 32–95 = unique serial number plus embedded manufacturing metadata.
- User memory: SL3S1206 (UCODE 9) supports a 32-bit user-memory option, SL3S1005 (UCODE 9xm) supports up to 752 bits user memory in customer-configurable allocations alongside up to 496 bits EPC. Enough for a backup serial number, factory lot ID, a minimal sensor-data buffer (typical use: encode a 16-bit last-maintenance date and a 16-bit status bitmap), or multiple Gen2 v2 File Open files on the xm variant.
- PSRAM: no persistent battery-backed memory. UCODE 9 is a fully passive tag; state is lost when the RF field drops, except for the Session flags (S0, S1, S2, S3) which persist per EPC Gen2 spec Tables 6.15-6.17 (S0 loses state immediately at power-off, S1 persists for 500 ms to 5 s, S2 and S3 persist for 2+ seconds), and the Kill / Access / Untraceable bit flags which are non-volatile and persist indefinitely.
- Write cycles: ≥ 100,000 writes per memory location per the data sheet. In practice this is effectively unlimited for retail and logistics programs (one encoding event plus zero field rewrites); becomes a factor only for laundry-cycle counter applications writing every cycle, where 100k writes ≈ 5-7 years at 30 washes/week cadence. Data retention ≥ 20 years at 25 °C room temperature per Arrhenius testing; retention degrades above 55 °C sustained, which is why high-temperature variants have dedicated characterization.
EPC Gen2 v2 command set as implemented
- Core Gen2 commands — Query, QueryAdjust, QueryRep, ACK, NAK, Req_RN, Read, Write, Kill, Lock, Access, BlockWrite, BlockErase, BlockPermalock, BlockReadEx, Select (with Target M=2 for Session transitions). Every EPC Gen2 reader implements this set; UCODE 9 is fully compliant with the GS1 v2.1 conformance suite.
- Untraceable: hides the TID bank (returning only the class identifier bits) and optionally shortens or hides the EPC response. When Untraceable is activated, the tag returns a shortened EPC (or no EPC) in response to generic Query commands, preventing post-sale tracking after a customer leaves the store. UCODE 9 uniquely supports a 'range reduction' Untraceable submode where the tag continues to respond at reduced sensitivity (typically -10 to -15 dBm forward-link). Useful for in-store returns processing that needs short-range reads post-sale.
- Authenticate: tag-authentication mode. UCODE 9 supports both crypto suite 0x0001 (short-form, 64-bit challenge, same as UCODE 8) and suite 0x0002 (extended, 128-bit challenge with longer HMAC output. Approximately a 2^64 security factor versus 2^32 for suite 0x0001). Suite selection is per-tag configurable via the Authenticate command parameters; brand-authenticity programs should specify suite 0x0002 for meaningful security.
- Challenge: a reader-initiated pre-authentication command that asks the tag to prove it knows its access password, without transmitting the password in clear. Prevents password-interception attacks on pre-authorized reader networks. Combined with suite 0x0002 Authenticate, UCODE 9 gives a reasonable security envelope for medium-risk UHF anti-counterfeiting at a fraction of the cost of NTAG424 DNA at HF.
- File Open / File Privilege. File-level access control over user memory. Partition the user memory into up to 4 files (FileID 0-3), each with its own 32-bit Access password and independent Lock/BlockPermalock state. Rare in UCODE 9 deployments because user memory is only 32 bits (effectively one file); very common on UCODE 9xm with 96 bits of user memory where multi-vendor programs need a 'vendor A writes File 0, vendor B writes File 1, maintenance writes File 2' access separation.
- ReadProtect: subset supported. ReadProtect allows a tag to refuse to respond to Read commands without the Access password, protecting user-memory contents from unauthorized dumping. Useful for anti-counterfeiting and medical-device applications where the user memory holds sensitive lot or patient data.
- Read/Write performance: UCODE 9 sustains ~700 tags/sec in Dense-Reader Mode at 640 kbps backscatter, limited in practice by the reader's anti-collision algorithm (Impinj R700: 1200 tags/sec theoretical / 800 sustained, Zebra FX9600: 700 sustained, Alien ALR-F800: 500 sustained) rather than the chip. BlockWrite at 32-bit granularity (two 16-bit words per command) is supported for multi-word EPC updates in a single transaction, reducing encoding-line throughput time by ~40% versus 16-bit-at-a-time Write.
Read sensitivity and the -23.5 dBm number
- Forward-link sensitivity of -23.5 dBm best-in-class (chip input power required to power up and decode a reader command) is the headline UCODE 9 number, per the NXP UCODE 9 (SL3S1206 / 9xe SL3S1216 / 9xm SL3S1005) product data sheets. Benchmarked under ISO/IEC 18046-3 conditions with a 50-ohm reference antenna, reader output 30 dBm, measured on Voyantic Tagformance free-air test setup. This is ~1 dB better than UCODE 8 (-22.5 dBm), ~1.4 dB better than Monza R6 (-22.1 dBm per the IPJ-W1700-K00 datasheet), and roughly matching Alien Higgs-9 (-23.2 dBm per the Higgs-9 datasheet). Impinj M730 (-22.6 dBm) trails by ~1 dB; M830 / M850 (-25.5 dBm) leads UCODE 9 by ~2 dB.
- In practice this translates to ~10-12 m read range on a reference UHF dipole antenna (Impinj SpeedwayR420 with Laird A9028 reader antennas at 30 dBm / 1 W ERP, retail shelf environment over dry cardboard boxes). Monza R6 measures ~8-9 m on the same setup; UCODE 8 measures ~7-8 m. In cluttered retail backroom environments with dense shelving and liquid products the actual read envelope compresses to 5-7 m for all chips but UCODE 9 retains the 20-30% advantage.
- Write sensitivity -18 dBm per the SL3S1206 data sheet — the power required at the chip to successfully program memory. Combined with forward-link sensitivity this determines the practical encoding range and read range; UCODE 9's balance of the two is what makes it effective at POS-gate deployments where both the reader's transmit budget and the portal's receive SNR are constrained.
- Self-Adjust Sensitivity: factory-enabled feature that calibrates the chip to its specific antenna impedance during the first power-up in a reader field. The chip measures the power-up voltage over 8-16 RF cycles and adjusts its internal threshold to match. Converters use this to compensate for antenna-tuning tolerances (+/- 3-5% typical) across SKU-specific inlay layouts without the traditional chip-side retuning step. For AEIC (Anti-Electromagnetic-Interference Coating) inlays on metalized retail packaging it gives ~1 dB additional margin; for standard Dogbone-class inlays the effect is closer to 0.3-0.5 dB, useful but not transformative.
- Frequency response across 860-960 MHz — characterized in the SL3S4011 data sheet Figure 12; peak sensitivity at ~915 MHz (FCC center), degrading by ~0.5 dB at the 865-868 MHz ETSI band and ~1 dB at the 920-925 MHz Japan band. Inlays pre-tuned for ETSI-only operation recover the ETSI-specific degradation; pure global-tuned inlays split the difference.
- Deep-dive data: see the UCODE 9 datasheet SL3S4011_4021 sections 8.1-8.3 for the complete sensitivity vs. frequency characterization across the 860-960 MHz band, plus the Voyantic Tagformance public database which publishes measurement sweeps for all major reference inlays at standardized test conditions.
Antenna design considerations
- Chip impedance at 915 MHz — approximately 11-j200 ohms (real part 11 Ω, imaginary -200 Ω, highly capacitive). Most commercial UCODE 9 antenna designs target a complex conjugate impedance of 11+j200 for maximum power transfer. This is materially different from UCODE 8's 11-j120 ohm impedance, which is why drop-in substituting UCODE 9 silicon onto a UCODE 8-tuned antenna degrades sensitivity by 2-4 dB; converters maintain separate UCODE 8 and UCODE 9 antenna revisions of common inlay references (Dogbone, MiniWeb, etc).
- Dipole layouts: the most common UCODE 9 inlay is a T-match or H-slot dipole of 70-95 mm overall length, with the chip bonded at the T-match junction. Smartrac Dogbone (the reference-design inlay shipped in billions of units) uses UCODE 8 historically and UCODE 9 in current production runs; the current 'Dogbone U9' has antenna dimensions essentially identical to the U8 but with retuned meander-line feed to match the different capacitive impedance.
- Anti-metal designs: UCODE 9 works on a 0.2-1 mm PET/ferrite spacer mount but the tag radiation pattern narrows and forward-link sensitivity degrades by 2-4 dB. Consider Impinj Monza R6 specifically when anti-metal performance at low cost dominates. Monza R6's lower impedance (11-j150 ohms at 915 MHz) is slightly easier to match into the narrowband patch antennas typical of anti-metal designs. For premium on-metal performance (yard asset tags, industrial metal shelving), specify Confidex Ironside or Xerafy Global Trak with UCODE 9 silicon; read range on metal is 6-10 m at 30 dBm.
- High-temperature deployments: UCODE 9 survives 125 °C peak excursions (30 min cumulative lifetime); sustained 85 °C is fine. For tire-cure or autoclave applications specify UCODE 9xe if available from your strap vendor (limited supply. Most converters prefer to quote Monza R6-P for tire-cure), or move to Monza R6-P which carries a higher peak rating (200 °C / 40 min sustained, tested to the AIAG tire-industry spec).
- ISO/IEC 18000-63 regional frequency compliance. UCODE 9 tunes across the global 860-960 MHz band. Deployment-specific retuning is an antenna consideration, not a chip one; the chip accepts the full ETSI 865-868 MHz, FCC 902-928 MHz, Japan 916.8-920.4 MHz and China 920.5-924.5 MHz ranges transparently. For India (865-867 MHz) and Korea (917-920.8 MHz) the same chip works with the appropriate region-tuned antenna.
Commercial deployments and application fit
- Retail apparel item-level tagging. UCODE 9 is the volume-driving chip. Major retailers (Zara / Inditex since 2014 for UCODE 8, transitioned to UCODE 9 by 2022; H&M 2022 onwards; Decathlon from 2019 UCODE 8 and UCODE 9 dual-source since 2023; Target, Macy's, Walmart Tier-2 mandate) specify UCODE 9 or equivalent sensitivity as a minimum for new SKU encoding projects since 2022. Sensitivity budget makes it compatible with overhead portal readers at POS (Impinj Xarray / xSpan) and with handheld replenishment readers (Zebra RFD8500, Impinj R1000) on the sales floor; typical first-pass read rate 98-99.5% at a 20-item basket.
- Supply-chain and logistics. Carton and pallet tagging where read-through-material performance matters. UCODE 9's read sensitivity gives margin for stack effects when pallets carry RF-lossy products (liquids, metalized packaging); Walmart's Tier-2 carton mandate (2022-2026) explicitly approves UCODE 8 or UCODE 9, but cartons shipping into high-throughput DCs (Walmart #6094 Bentonville, Amazon IXD facilities) increasingly specify UCODE 9 to hit the 99.5% dock-door read rate SLA.
- Library and asset tracking. Library RFID systems (Bibliotheca / formerly 3M, Envisionware, P.V. Supa, Checkpoint-successor D-Tech) specify UCODE 9 for new inlay runs. Enough user memory (32 bits) for a 13-digit library barcode encoded base-64 or a patron-book link; the Authenticate command supports 'book-this-library-only' theft protection clauses.
- Linen and laundry (medium-temperature). Hospital linen, uniform tracking and hotel laundry use UCODE 9 on silicone or PPS tags (e.g., Datamars PPS-Air, Fujitsu WT-A533N). Sensitivity headroom lets the laundry tunnel reader identify all tags in a 50+ item batch at once while the linen is compressed and wet, which is where -23.5 dBm beats the -19 dBm floor badly.
- Anti-counterfeit overlays: the Authenticate (suite 0x0002) and Challenge commands support a 'prove you know your access password and compute a valid HMAC' handshake for medium-risk brand authentication (cosmetics, wine, mid-tier apparel). Not as strong as NTAG424 DNA's AES-128 CMAC and SUN (Secure Unique NFC) at HF, but cheap and useful for UHF item-level programs that also need authenticity verification at retail scanning distances.
- Where UCODE 9 is not the right choice. High-temperature tire-cure (>150 °C, specify Monza R6-P), harsh industrial with moisture/dust beyond IP68 (specify Alien Higgs-9 with specialized encapsulation), or ultra-low-cost promotional campaigns where the per-unit cost has to be under 2 cents at scale (specify UCODE 8 with basic antenna). HF-only privacy use cases (contactless payment cards, passports) are ISO 14443 / 15693 and require dedicated HF silicon. UCODE 9 is UHF only and does not interoperate with NFC phones.
- EUDR / traceability programs: UCODE 9's TID uniqueness satisfies the GS1 EPCIS capture requirements for individual-item traceability in EU deforestation regulation (EUDR, Regulation 2023/1115, enforcement from December 2025 for large operators) and similar due-diligence frameworks (UFLPA in the US since 2022, CSDDD transposition in EU member states 2026-2028).
NXP reference documents
- NXP UCODE 9 product data sheets: SL3S1206 (UCODE 9), SL3S1216 (UCODE 9xe extended-EPC), and SL3S1005 (UCODE 9xm configurable-memory). Available at nxp.com/docs/en/data-sheet/SL3S1206.pdf and equivalent paths. Authority for the -23.5 dBm best-in-class read sensitivity, -18 dBm write sensitivity, memory organization, command set, and application notes/pinning.
- AN11808 — UCODE 9 personalization and encoding guide. Covers EPC encoding conventions, TID-based serialization, the Self-Adjust Sensitivity calibration flow, and the Gen2 v2 File Open / File Privilege configuration sequences.
- GS1 EPC Generation-2 v2.1 Air Interface Protocol. The standard UCODE 9 implements. Commands and state transitions are defined here; UCODE 9 is compliant with the 2018 revision plus the 2023 errata.
- ISO/IEC 18000-63:2019 — UHF RFID air interface. UCODE 9 is certified compliant; the certification statement is required for ISO-preference markets (Japan METI procurement, Korea K-RFID, certain EU public procurement frameworks).
- NXP AN13290 — UCODE 9 crypto-suite application note. Details the Authenticate (suite 0x0001 short-form and suite 0x0002 extended) and Challenge command sequences, including the HMAC-family algorithm used and test vectors for reader-side implementation.
- GS1 Tag Data Standard 1.13 — EPC encoding conventions for SGTIN-96 (apparel item-level), SSCC-96 (logistics carton/pallet), GIAI-96 (assets), GRAI-96 (returnable assets). Specifies exactly what bytes to write into bank 01 for each application and the ASN.1-derived URI representation.
Strap ecosystem, pricing mechanics and UCODE 9 supply-chain posture
Beyond the silicon specifications, the UCODE 9 deployment decision is shaped by the strap-assembly ecosystem, the inlay-converter landscape, the current strap pricing regime and the supply-chain posture NXP has maintained through the 2022-2025 capacity cycle. Procurement teams that understand this context negotiate better terms, avoid grey-market exposure, and architect multi-year programmes that don't fall over on chip-level scarcity.
- Wafer fab and process node. NXP produces UCODE 9 at its Kirchheim-Teck (Germany) and Singapore fabs on a 180 nm RF-CMOS process, migrated from earlier UCODE 8 production on 300 nm. The node shift delivers the improved rectifier efficiency that underpins the -23.5 dBm best-in-class sensitivity. Capacity expansion announced in 2023 doubled UCODE 9 wafer starts by Q3 2024 in response to retail-apparel demand; supply has been stable since late 2024 with 12-16 week lead times on strap orders.
- Strap assembly ecosystem: authorised strap assemblers include Smartrac (now Avery Dennison Smartrac post-2020), Invengo (China-based, significant UCODE 9 volume), Arizon (Taiwan, specialist in thin-film antennas), Beontag (Brazil and Europe), Xerafy (hard-tag focused), Hana Micron (Korea) and Checkpoint-successor CCL Industries. NXP's authorized-partner list is published at nxp.com/products/rfid-nfc; sourcing outside this list materially increases the grey-market risk profile.
- Strap-level pricing trajectory — 2022 peak shortage pricing hit USD 0.040-0.055 per strap at 100M-unit volumes. 2023 corrections brought pricing to USD 0.028-0.040. Current 2025-2026 posture has strap pricing at USD 0.022-0.032 depending on volume commitment, antenna reference and converter-specific arrangements. For context, UCODE 8 straps quote USD 0.018-0.026 and Monza R6 USD 0.020-0.030 at equivalent volume. UCODE 9's premium is 10-25% over UCODE 8 and roughly at parity with Monza R6 at the low end.
- Finished inlay pricing: adding antenna substrate (USD 0.010-0.015 at 100M volume), strap-to-antenna lamination (USD 0.005-0.010), roll-to-roll die-cut and release-liner (USD 0.003-0.007), and converter margin (15-25%) produces landed inlay pricing for UCODE 9 retail-apparel SKUs at USD 0.055-0.085 at 100M volume. Smaller programmes (10M-50M volume) typically pay a 15-30% premium; bespoke anti-metal or specialty-substrate SKUs land at USD 0.25-0.80 per finished tag depending on complexity.
- Converter-landscape depth: Avery Dennison Smartrac (largest UCODE 9 converter, ~35% of volume), Invengo Information Technology, Beontag (with the PaperTag product line), Arizon RFID (AZ-9662/9762 for apparel, AZ-G3 for small-format), SATO (Japan-focused), Honeywell-acquired Intermec inlay line, Checkpoint Systems (CCL), Confidex (Nordic industrial), HID Global FLeX (ticketing variant), and regional specialists like Identiv (US, specialist programmes), Xerafy (hard tags). Each has a characteristic pricing posture, lead-time profile, and antenna-reference library.
- Authorised-distributor channel: Smartrac / Avery Dennison through its global network, Arrow Electronics as a catalog distributor for bare die and straps, Richardson RFPD for industrial specialist bookings, and direct NXP allocation for converters with USD 5M+ annual strap spend. Distribution margin adds 5-10% at the strap layer; direct-allocation converters usually pass half of that saving through to large end-customer programmes as pricing concessions.
- Semiconductor-shortage aftermath: the 2020-2022 supply crunch put UCODE 9 on 6-9 month lead times at peak and triggered a wave of dual-sourcing across retail programmes (UCODE 9 + Impinj M730 as equivalent substitutes). That dual-sourcing posture has persisted into 2026 even after supply recovered, for negotiation leverage and for continuity-of-supply insurance. Most large retailers carry both chip families in their approved-inlay list and split volume 60/40 or 50/50 across the pair.
- Counterfeit and grey-market exposure. UCODE 9's success has made it a target for grey-market re-marking. The 2023-2024 period saw notable counterfeit lots circulating through unauthorised Asian distribution, usually sold at 30-40% below legitimate pricing and often failing the Authenticate suite-0x0002 round-trip test or showing TID model ID 0x104 (UCODE 7xm re-marked as 9) rather than 0x110. NXP's Product Serialization Programme and the authorised-distributor Certificate of Conformance paperwork are the audit defence; reputable converters refuse to source outside authorised channels because a single contaminated lot can disqualify an entire programme in a customer audit.
- NXP PSIRT and product-update channel. NXP maintains a Product Security Incident Response Team (psirt@nxp.com) that publishes advisory bulletins when cryptanalysis or implementation issues are identified. UCODE 9's Authenticate suite 0x0002 has not had a published vulnerability as of early 2026, but mature procurement subscribes to the PSIRT bulletin feed to ensure they are notified if that changes. For NTAG and DESFire chips in the same portfolio, PSIRT bulletins have been issued 2-4 times per year historically.
- Multi-year supply commitments. Retail programmes with 200M+ annual inlay consumption negotiate 2-3 year supply agreements with converters that include strap-allocation guarantees (a committed share of NXP's UCODE 9 wafer starts), price floors, lead-time SLAs, and grey-market indemnity clauses. Smaller programmes take the spot market and pay the volatility premium; larger programmes lock in predictable pricing at the cost of volume commitments that may exceed actual demand in a down year.
- Migration posture vs UCODE 10 — NXP's next-generation UCODE is expected in the 2027-2028 timeframe with further sensitivity and security improvements. Retail programmes currently specifying UCODE 9 have a natural 3-5 year window before needing to consider migration; the installed-base consistency argument and the encoded-EPC governance typically delay migration until the next major RFP cycle regardless of silicon advance. Early-moving procurement teams include UCODE 10 readiness in current RFP language to ensure forward compatibility when it ships.
Specifications at a glance
| Parameter | UCODE 9 (SL3S1206) | UCODE 9xm (SL3S1005) |
|---|---|---|
| Operating frequency | 860–960 MHz | 860–960 MHz |
| Air-interface standard | EPC Gen2 v2 / ISO 18000-63 | EPC Gen2 v2 / ISO 18000-63 |
| EPC memory | Up to 96 bits | Up to 496 bits (configurable) |
| User memory | Up to 32 bits | Up to 752 bits (configurable) |
| TID memory | 96 bits (read-only, unique) | 96 bits (read-only, unique) |
| Kill/Access passwords | 32 bits each | 32 bits each |
| Forward-link (read) sensitivity | -23.5 dBm | -23.5 dBm |
| Write sensitivity | -18 dBm | -18 dBm |
| Chip impedance at 915 MHz | ~11-j200 Ω | ~11-j200 Ω |
| Anti-collision rate (typical) | ~700 tags/sec | ~700 tags/sec |
| Self-Adjust Sensitivity | Yes | Yes |
| Untraceable support | Yes (with range-reduction submode) | Yes (with range-reduction submode) |
| Authenticate / Challenge | Yes (suites 0x0001 and 0x0002) | Yes (suites 0x0001 and 0x0002) |
| File Open / File Privilege | 1 file (32-bit) | Up to 4 files (96-bit) |
| Operating temperature | -40 °C to +85 °C | -40 °C to +85 °C |
| Peak temperature | 125 °C (short excursion) | 125 °C (short excursion) |
| Data retention | ≥ 20 years | ≥ 20 years |
| Endurance (writes) | 100,000 cycles | 100,000 cycles |
Useful next pages
Use these linked product, guide and comparison pages to keep the next click specific and practical.
UCODE 9 product pages
Proud Tek UHF SKUs built on NXP UCODE 9 silicon.
Related comparisons and guides
UHF chip-family context and UCODE 9 in-depth.
Authoritative external references
NXP, GS1 and ISO documents that define UCODE 9.
FAQ
Is UCODE 9 worth the cost premium over UCODE 8?
For new deployments at meaningful scale, yes. The ~5 dB forward-link sensitivity improvement and ~7 dB backscatter improvement translate to 20-30% more read range on the same tag antenna and 3-5 percentage points fewer missed reads at retail POS portals. Which compounds to a 40-60% reduction in manual-rescan events at the POS. The per-unit chip cost premium at volume (100M+ strap orders) is typically 0.3-0.5 cents — trivial compared to the operational cost of portal read errors, which industry research (Auburn RFID Lab's retail benchmarks) prices at US$0.50-2.00 per missed read depending on whether the error surfaces at checkout or at inventory audit. UCODE 8 remains appropriate for budget-dominated consumer-goods programs where the tag is discarded at first sale (event wristbands, disposable transit tickets, single-use tickets) and where the read environment is controlled enough that UCODE 8's -19 dBm is sufficient. Hybrid specification is common: UCODE 9 for apparel and durables, UCODE 8m for promotional and tertiary packaging, both under a common EPC encoding so the back-end software is chip-agnostic.
Does UCODE 9 support EU privacy requirements for retail?
Yes, via the EPC Gen2 v2 Untraceable command (Section 6.3.2.5 of the v2.1 spec). Once Untraceable is activated (typically at the POS terminal via an Access-password-authenticated command sequence), the tag stops responding with the full EPC in response to generic Query commands and instead responds with a shortened, non-unique identifier. Or optionally no EPC at all. UCODE 9 uniquely supports a 'range reduction' Untraceable submode in addition to the standard 'hide EPC' mode: in range-reduction the tag continues to respond to readers within ~20-30 cm but suppresses response at longer ranges, which is useful for in-store returns processing post-sale without reopening full-range tracking. This gives the customer privacy after the item leaves the store while keeping the tag's inventory and reverse-logistics utility. UCODE 9 was the first mass-volume chip to implement both Untraceable submodes, and the CEN CWA 16924 EU retail RFID framework recognizes it as meeting the GDPR-aligned privacy expectation for item-level apparel RFID.
What is the TID value I should see on authentic UCODE 9 silicon?
Per the NXP SL3S1206 product data sheet (Rev. 3.5, 12 Feb 2025), bits 00-07 of TID bank 10 = 0xE2 (EPC class identifier per Gen2 v2) and bits 08-19 carry the NXP mask-designer prefix, followed by the NXP-assigned model-ID field and the per-chip unique serial. Incoming-inspection scripts should read the full 96-bit TID and verify: (1) class identifier == 0xE2, (2) NXP mask-designer prefix matches the value documented in the SL3S1206 / SL3S1216 / SL3S1005 datasheets for the variant ordered, (3) the model-ID field matches the variant per NXP's datasheet TID structure section, (4) serials are unique across a sample of 200-500 tags per lot, (5) optionally round-trip an Authenticate suite-0x0002 command to confirm the crypto engine actually computes the expected HMAC (most clones fail this check even if they return a plausible TID). Anything else indicates a re-marked chip or a different silicon (most commonly Impinj Monza R6 or an unauthorized-clone wafer) being passed off as UCODE 9.
Can UCODE 9 be used on metal surfaces?
Yes with a suitable anti-metal mount. Typically 0.5-1 mm PET spacer plus a ferrite absorber (Material MnZn ferrite sheet, 0.1-0.3 mm thickness), or a fully-designed anti-metal hardshell tag (e.g., Confidex Ironside Classic, Xerafy Global Trak 2, HID IN1301). Expect 2-4 dB forward-link sensitivity penalty compared to free-air performance on the thin-spacer mount, or near-free-air performance on a properly-designed anti-metal patch antenna with internal ferrite absorber stackup. Practical read ranges: 4-6 m on a thin spacer-mounted inlay, 6-10 m on a purpose-designed anti-metal tag at 30 dBm reader output. For demanding metal applications (automotive brake-disc tracking, mining asset tags, oil-and-gas pipeline components), consider Impinj Monza R6 which has reference anti-metal antenna designs from multiple strap vendors optimized for its slightly different impedance, or go to a fully-encapsulated IP68/IP69K hardshell with UCODE 9 silicon.
What is Self-Adjust Sensitivity and do I need to configure it?
Self-Adjust Sensitivity (SAS) is a UCODE 9-exclusive feature that tunes the chip's internal sensitivity threshold to match its antenna impedance during the first power-up in an RF field. Mechanically, the chip measures the rectified voltage over the first 8-16 RF cycles of its initial wake-up and adjusts a reference threshold by 1-3 dB to land on the target sensitivity envelope. For standard reference-design inlays (Dogbone, M730, Miniweb. All with antennas tuned within +/- 3% of the chip's target impedance) no configuration is needed: the chip calibrates automatically and the effect is 0.3-0.5 dB of 'free' margin. For custom antenna layouts with wider tuning tolerance (small-format inlays, anti-metal with narrow bandwidth) the converter may need to invoke the SAS calibration mode explicitly via a specific BlockWrite sequence during manufacturing test, which can yield 1-1.5 dB of additional margin. NXP AN11808 documents the exact command sequence. SAS is always on for UCODE 9 in current wafer production; there is no need to 'enable' it at deployment time.
How many Read commands per second can UCODE 9 sustain in a busy RFID portal?
Up to ~700 tags/sec in Dense-Reader Mode at 640 kbps backscatter rate, per chip. The practical throughput at a retail POS portal is limited by the anti-collision algorithm (Q-protocol slot negotiation), the reader's RF session management (Session 0 / 1 / 2 / 3 selection), and the reader's processing speed rather than the chip. For typical retail POS deployments with Impinj SpeedwayR420 or Zebra FX9600 readers, UCODE 9 sustains the full reader throughput (~500-700 sustained tags/sec in a busy gate) without becoming the bottleneck. At warehouse dock-door portals with Impinj R700 / R2000 hardware and four antennas, aggregate throughput of 1200-2000 tags/sec across all antennas is the typical operating regime and UCODE 9 keeps up; what breaks first is the reader's upstream network bandwidth or the middleware's EPC de-duplication pipeline.
Is UCODE 9 backwards-compatible with readers that only implement Gen2 v1?
Yes for core operations. The v1 Query/Read/Write/Lock/Kill flow works unchanged on UCODE 9 — a legacy reader encoding EPCs on UCODE 9 tags will see them as standard EPC Gen2 Class 1 Gen 2 tags and can perform normal inventory and write operations. Only the v2-specific commands (Untraceable, Authenticate, Challenge, File Open, ReadProtect) require a v2-capable reader firmware; a Gen2 v1 reader simply cannot invoke these commands. In practice all major RFID reader vendors (Impinj from OctaneSDK 5.x onwards, Zebra from ZIH 3.x onwards, Alien from ALR 18.x onwards) have shipped v2 firmware since 2018-2019, so the v1/v2 compatibility question typically only arises on legacy hardware from 2015-era deployments that hasn't had a firmware refresh. On any modern reader purchased 2020 or later, all UCODE 9 v2 features are available.
Sources & references
Primary standards, OEM datasheets and regulatory documents cited by this article. All URLs were verified on the access date shown below.
- NXP SL3S1206 UCODE 9 Product Data Sheet, Rev. 3.5 (12 February 2025)
Canonical NXP datasheet for UCODE 9 — authority for the -23.5 dBm best-in-class read sensitivity, -18 dBm write sensitivity, 96-bit EPC + 32-bit user memory, anti-tear / Self-Adjust features and the EPC Gen2 v2 command support that this guide references.
- NXP SL3S1216 UCODE 9xe Product Data Sheet, Rev. 3.3 (12 February 2025)
Datasheet for UCODE 9xe extended-EPC variant supporting up to 448 bits of EPC memory.
- NXP SL3S1005 UCODE 9xm Product Data Sheet, Rev. 3.1 (12 February 2025)
Datasheet for UCODE 9xm configurable-memory variant supporting up to 496 bits EPC and up to 752 bits user memory across three customer-selectable allocations.
- NXP AN11809 — UCODE 9 Commands and Features
NXP application note covering UCODE 9 command flow, Truncation field, Self-Adjust initialization, and Brand Protection features (ASICID / originality signature) used in anti-counterfeit deployments.
- ISO/IEC 18000-63:2015 — Parameters for air interface communications at 860-960 MHz Type C
ISO-balloted UHF Gen2 air-interface standard under which UCODE 9 operates — baseline reference for Query / Inventory / Access command behaviour.
- GS1 EPC Radio-Frequency Identity Protocols — Generation-2 UHF RFID Standard (Gen2v2)
Industry-authored Gen2 specification defining the v2 Untraceable, Authenticate, Challenge, File Open and ReadProtect commands that UCODE 9 implements.
- FCC Rules and Regulations, Title 47 CFR Part 15.247
US regulatory authority for the 902-928 MHz band in which UCODE 9 is deployed. Sets interrogator EIRP and FHSS requirements.
Proud Tek is a Shenzhen-based RFID & NFC manufacturer supplying hotel chains, transit operators, event venues and retail brands worldwide. Every order includes free samples, RF testing and dedicated project support.
Get a Quick Quote
Tell us about your project and we'll respond within one business day. Fields marked (asterisk) are required.
