UCODE 8 / SL3S1205 / SL3S1215 Reference

NXP UCODE 8

UHF Chip Technical Encyclopedia (Memory, Commands, Cost Profile, Deployment)

UHF RFID inlay representative — NXP UCODE 8 chip technical encyclopedia

Quick answer

UCODE 8 (NXP SL3S1203 / SL3S1213) has been the cost-of-gravity UHF inlay chip since its 2017 launch. Shipping in billions of units per year, it powers the majority of promotional, event, single-use and cost-sensitive UHF deployments still converting today. This encyclopedia documents UCODE 8's memory layout, EPC Gen2 v2 command support, sensitivity envelope, the UCODE 8 versus UCODE 8m distinction, and the specific deployment classes where UCODE 8 remains the correct choice in 2026 even as UCODE 9 takes the sensitivity crown.

  • Industry cost anchor: UCODE 8 is the reference chip against which every other UHF chip's price is benchmarked. At strap-volume orders (100M+ units) the per-unit chip cost is approximately half a US cent, the finished dry-inlay converts at roughly US$0.025-0.040 depending on antenna substrate, and a standard Dogbone wet-inlay label lands in the US$0.045-0.065 range. That pricing envelope is the only silicon that works economically for billion-unit-per-year promotional, transit-ticket and supply-chain programs where the marginal cost of a tag has to clear a hurdle of a fraction of a cent per read event.
  • EPC Gen2 v2 support — Untraceable and Authenticate commands are present (though simpler than UCODE 9), providing forward compatibility with EU retail privacy requirements (Gen2 v2 Section 6.3.2.5 Untraceable and Section 6.3.2.10 short-form Authenticate) at the cost-optimized end of the market. That means UCODE 8 is the lowest-cost silicon in production today that a retailer can legally deploy under the GDPR-aligned interpretation of the EU retail RFID industrial framework recommended by the European RFID Research Centre for item-level clothing.
  • Two main variants per the NXP SL3S1205_15 product data sheet: UCODE 8 (SL3S1205, 128-bit EPC memory, no user memory) and UCODE 8m (SL3S1215, 96-bit EPC + 32-bit user memory). Both are factory-interchangeable from a reader perspective (the air-interface behavior is identical for Query, ACK and Read commands) so the variant decision is driven purely by whether the application needs the 32 bits of user memory. NXP's official read sensitivity for both variants is -23 dBm (per SL3S1205_15 Rev. 3.6 datasheet, Dec 2021), with -18 dBm write sensitivity.
10+ Years ISO 9001 500+ Clients 50+ Countries

At a glance

Use these short answers to decide whether this page matches the project before moving into the detail.

Key takeaway

Industry cost anchor: UCODE 8 is the reference chip against which every other UHF chip's price is benchmarked. At strap-volume orders (100M+ units) the per-unit chip cost is approximately half a US cent, the finished dry-inlay converts at roughly US$0.025-0.040 depending on antenna substrate, and a standard Dogbone wet-inlay label lands in the US$0.045-0.065 range. That pricing envelope is the only silicon that works economically for billion-unit-per-year promotional, transit-ticket and supply-chain programs where the marginal cost of a tag has to clear a hurdle of a fraction of a cent per read event.

Family and part numbers

UCODE 8 — NXP part number SL3S1205 (per the SL3S1205_15 Rev. 3.6 product data sheet, December 2021). 128-bit EPC, no user memory, 32-bit Kill password, 32-bit Access pas...

Family and part numbers

  • UCODE 8 — NXP part number SL3S1205 (per the SL3S1205_15 Rev. 3.6 product data sheet, December 2021). 128-bit EPC, no user memory, 32-bit Kill password, 32-bit Access password, 96-bit factory-unique TID. Optimized for applications where the EPC itself carries all the identity information (SGTIN-96, SGTIN-198, SSCC-96, GIAI-96) and no additional item-specific data needs to live on the tag. The 128-bit EPC bank is the distinguishing feature versus the -m variant and suits retailers who use non-standard proprietary encoding beyond the GS1 96-bit family.
  • UCODE 8m — NXP part number SL3S1215. 96-bit EPC plus 32 bits of user memory, same 32-bit passwords and 96-bit unique TID. Same silicon family and sensitivity envelope per NXP's combined SL3S1205_15 datasheet, with the memory partition configured differently at manufacturing. The added 32 bits of user memory (two 16-bit words at bank 11 addresses 0x00 and 0x01) provide space for a backup serial, a factory lot code, a care-instruction index, an authentication password salt, or a hospitality-chain laundry-cycle counter.
  • Strap and inlay availability. UCODE 8 has been shipped on flip-chip straps and wire-bond strapped formats by every major inlay vendor (Smartrac / Avery Dennison / Arizon / Neology / SATO / Identiv / Beontag) in a full range of standard reference-design antennas: the Avery AD-Dogbone (U8 variant), AD-Frog 3D, AD-383u7 apparel inlay, AD-Minute small-format, the Smartrac DogBone, Miniweb, and ShortDipole, the Arizon AZ-9629 / AZ-9654, and the Beontag PaperTag. For most of these antennas a UCODE 9 drop-in variant now exists, but converters maintain UCODE 8 SKUs indefinitely for the cost-sensitive programs still ordering billions of units per year.
  • Operating temperature — -40 °C to +85 °C normal range per the NXP short data sheet, with peak 125 °C permitted for short excursions (minutes, not hours — typical specification is 30 minutes cumulative over the chip's life). Not suitable for tire-cure (where Monza R6-P is the reference choice with sustained 200 °C compatibility for 40 minutes), sustained autoclave at 134 °C for 18 minutes, or Pirelli/Michelin-class tire-pressure internal tags where ambient exceeds 100 °C for extended periods.
  • Counterfeit watch: authentic UCODE 8 returns TID with EPC class identifier 0xE2 in bits 00-07 plus NXP mask designer prefix 0x801 in bits 08-19, followed by an NXP model-ID field. Clones marketed as 'UCODE 8 compatible' (most commonly produced by unauthorized Chinese fabs) often present with a zero or randomized model ID, an incorrect mask-designer segment, or a non-unique TID serial (revealed by scanning 500+ tags and finding repeats). Incoming inspection should script-verify the full 96-bit TID pattern against the NXP SL3S1205_15 datasheet's TID structure section and cross-reference any model-ID claims against NXP's publicly published TID model assignments. The most common counterfeit pattern in 2024-2025 is UCODE 7 silicon (SL3S1204) re-marked or relabeled as UCODE 8.

Memory architecture

  • Four standard EPC Gen2 memory banks, addressed per ISO/IEC 18000-63 Section 6.3.2.1.2. Bank 00 = Reserved (kill and access passwords, 32 bits each). Bank 01 = EPC bank (Stored PC + EPC + optional Stored CRC). Bank 10 = TID bank. Bank 11 = User memory bank. Bank selection is via the 2-bit MemBank field in the Read, Write, BlockWrite, BlockErase, BlockPermalock and BlockReadEx commands.
  • EPC memory bank 01 — structure is Stored CRC-16 (bits 0-15) + Stored PC (bits 16-31) + EPC (bits 32+). On UCODE 8 (SL3S1205), the EPC segment is up to 128 bits (total bank size 160 bits), making it suitable for longer identifiers without dipping into other banks. On UCODE 8m (SL3S1215), 96 bits standard EPC (total bank size 128 bits). The PC word's Length field (bits 21-15) indicates the actual EPC length to the reader at Query time.
  • TID memory bank 10 — 96 bits read-only, factory-programmed, cannot be altered post-manufacturing. Structure: bits 0-15 = TID allocation class identifier (0xE280 for EPC Gen2 v2 Class 1 with user memory), bits 16-27 = NXP mask-designer and model-ID field, bits 28-95 = per-chip unique 64-bit serial number. Uniqueness across the entire UCODE 8 population is guaranteed by the manufacturing process and documented in NXP AN11734; the TID is the anchor used for Authenticate challenges and cloning detection.
  • User memory bank 11 — 0 bits on SL3S1205 (bank does not exist; writes fail with Gen2 error code 'non-existent memory location'), 32 bits on SL3S1215. The user memory on SL3S1215 is aligned at bit 0 of bank 11 and addressable in 16-bit words (word 0x00 and word 0x01). File-based segmentation per Gen2 v2 File Open is not supported on SL3S1205; SL3S1215 exposes one File (ID 0x00) covering the full 32 bits.
  • Kill and Access passwords — 32 bits each, factory default all-zeros, writeable in bank 00 (addresses 0x00-0x1F for Kill, 0x20-0x3F for Access) by a Gen2 Write or BlockWrite command after a successful Req_RN / Access exchange. Once the Access password is non-zero and the Access Password Lock bit is set, subsequent password reads return all-zeros to protect against interrogator-side harvesting. Kill is one-shot: once successfully Killed, the chip is permanently inactive and cannot be recovered.
  • Write endurance — 100,000 writes per location per the short data sheet, which under a typical retail use case (one encoding event and zero field rewrites) is effectively infinite; for laundry-cycle applications writing a counter every cycle, the bound becomes visible at roughly 5-7 year life depending on wash frequency. Data retention ≥ 10 years at 55 °C (per NXP data sheet Figure 8 Arrhenius curve) and ≥ 20 years at 25 °C, enabling passive archival applications where the tag may not be read for over a decade between events.

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. UCODE 8 is fully v2 compliant for the core set and was certified by GS1 EPCglobal in 2017 at launch; the conformance document lists the mandatory and optional command support matrix.
  • Untraceable: supported on both SL3S1203 and SL3S1213. When activated (typically via a Gen2 v2 Untraceable command issued at the POS with the Access password), the tag shortens its EPC response to a non-unique pattern, restricts TID access to the allocation class identifier (so downstream readers cannot derive the chip model) and may suppress response to user-memory reads. Useful for EU retail privacy compliance per the CEN/TC 225 CWA 16924 workshop agreement; syntax identical to UCODE 9's Untraceable (one functional difference: UCODE 9 offers a finer-grained 'range reduction' mode where the tag continues to respond but with reduced sensitivity forcing short-range-only reads).
  • Authenticate: supported, with a 64-bit challenge-response. The implementation on UCODE 8 is the lightweight variant specified in GS1 Gen2 v2 Section 6.3.2.10 (short-form Authenticate, crypto suite 0x00 01) rather than the extended form on UCODE 9 (which adds suite 0x00 02 for a stronger HMAC variant with 128-bit challenge). For most deployments both are sufficient; anti-counterfeiting programs that demand extended challenge length and longer MAC output should specify UCODE 9 or NXP UCODE DNA.
  • Challenge: supported. Returns a 64-bit response derived from a key stored in the chip's secure memory area. Primarily used for pre-authentication of the tag before committing to an Authenticate round-trip, reducing reader airtime consumption in deployment scenarios where most tags in range are not of interest.
  • File Open / File Privilege — partially supported. UCODE 8m exposes one file (FileID 0x00 covering the user-memory bank) with a per-file access password (32 bits). UCODE 8 (SL3S1203, no user memory) does not expose the File mechanism meaningfully. Applications that need multi-file segmentation of user memory (e.g., separate slots for vendor-a, vendor-b and maintenance data) should use UCODE 9xm which supports multiple FileIDs with independent locks.
  • Not supported on UCODE 8 but available on UCODE 9 — the crypto suite 0x00 02 (stronger HMAC variant with extended challenge), the ISO/IEC 29167-11 ChaCha20-based crypto suite, some of the File Privilege fine-grained modes (per-file access/perma-lock), and the Self-Adjust Sensitivity calibration command that lets the tag dynamically adjust its forward-link sensitivity at field edges. Applications needing these features should specify UCODE 9. Also not supported: the Gen2 v2 'ReadProtect' privacy command (UCODE 9 implements a subset; UCODE 8 does not).
  • Anti-collision performance: ~500 tags/sec sustained in Dense-Reader Mode at 640 kbps link rate (Tari = 6.25 µs, M=2). Sufficient for retail POS (typically 20-50 items/second demanded) and logistics dock-door portal throughput (200-400 items/second typical for pallet scans). On the same reader UCODE 9 achieves ~700 tags/sec because of its faster response Delay_T1 tolerance at lower signal strength, which is where UCODE 9's edge shows up in portal applications with marginal signal.

Read sensitivity and read-range expectations

  • Forward-link (read) sensitivity -23 dBm per the NXP UCODE 8 (SL3S1205 / SL3S1215) product data sheet (reference inlay, free-air conditions). About 0.5 dB less sensitive than UCODE 9 (-23.5 dBm best-in-class per the NXP SL3S1206 / 9xe / 9xm datasheets) and ~0.9 dB more sensitive than Monza R6 (-22.1 dBm per IPJ-W1700-K00). Impinj M730 sits at -22.6 dBm per Impinj's M730 product brief — UCODE 9 and M830/M850 (-25.5 dBm) are the genuine sensitivity step-ups vs UCODE 8.
  • Write sensitivity -18 dBm. The practical limit for write operations is set by the reader, not the chip, for all but the longest-range deployments; UCODE 8 keeps up with any commercial reader (Impinj R700/R2000/Xspan, Zebra FX9600, Alien ALR-F800) at typical retail and logistics distances. The marginal performance gap between UCODE 8 and UCODE 9 becomes measurable only at ranges beyond 8 m from the reader antenna.
  • Practical read range: ~8-10 m on a reference dipole inlay (e.g., Avery AD-Dogbone U8) at 30 dBm (1 W ERP) reader output on a 6 dBi circular-polarized antenna, in free-air over dry cardboard. Approximately 1-2 m short of UCODE 9 (typically 10-12 m on the same antenna setup) and at parity with Monza R6 (-22.1 dBm read sensitivity per the IPJ-W1700-K00 datasheet), adequate for the applications UCODE 8 is typically used in (POS item-level at <1 m, event wristbands at <2 m, promotional inserts at <3 m, dock-door portals at <5 m).
  • Temperature sensitivity: stable from -40 °C to +85 °C; beyond 85 °C the forward-link sensitivity degrades approximately 0.05 dB per degree C per NXP's high-temperature characterization report. Below -40 °C the chip continues to function in most fabs but is out of warranted specification. Not a concern for retail or indoor-industrial deployments; becomes a factor only for outdoor yard-tracking in arid climates where tag surface temperature can exceed 85 °C in direct sun.
  • Antenna match: chip impedance at 915 MHz is approximately 11-j120 ohms (real part 11, imaginary part -120 ohms, capacitive). Most commercial UCODE 8 dipoles target an antenna impedance of 11+j120 (conjugate match) for maximum power transfer. The majority of reference inlay designs in circulation are tuned for UCODE 8's impedance rather than UCODE 9's (which is ~11-j200 ohms at 915 MHz — meaningfully different), which is why drop-in substituting UCODE 9 silicon onto an antenna designed for UCODE 8 almost always requires antenna retuning.
  • Frequency response across the global RAIN bands. Characterized across 860-960 MHz by NXP; peak sensitivity is at ~915 MHz (FCC and ETSI). Within the ETSI 865-868 MHz band the sensitivity degrades by roughly 0.5-1.0 dB versus the FCC 902-928 MHz band because the reference antenna is typically tuned to 915 MHz; inlay converters selling into pure-EU programs occasionally offer an ETSI-tuned variant with retuned antenna to close that gap.

When UCODE 8 is the right choice in 2026

  • Billion-unit promotional campaigns. Event tickets (Olympics badge inlays, Taylor Swift Eras Tour wristband program class), conference badges, single-use retail inserts, festival wristbands. Cost dominates; the tag's life is measured in days or a single use. UCODE 9's sensitivity upgrade doesn't justify the 30-50% cost premium at the scale these programs operate (typical cost delta ~US$0.015-0.025 per unit, multiplied by 500M-2B units annually = US$7.5M-50M program cost swing).
  • Library RFID replacement inlays. Existing deployments with millions of UCODE 8 tags in circulation (major university systems, national libraries, the UK's Bibliotheca deployments) continue to specify UCODE 8 for replacement inlays to maintain read consistency across the installed base. Mixing UCODE 9 and UCODE 8 in the same collection creates noticeable read-rate variance at self-service kiosks, increasing the false-negative rate enough that librarians push back; fleet consistency trumps per-tag performance.
  • Transport ticketing: mass-transit disposable fare cards (e.g., Paris RATP Navigo Easy, selected São Paulo municipal ticketing, many one-day tourist-pass formats) and event venue ticket strips. Read range requirements are modest (10-20 cm at a gate reader operating at 18 dBm ETSI-compliant output); UCODE 8's performance envelope is comfortable and the cost difference on a 100M-unit annual run is material to the agency budget.
  • Asset-labeling programs where the reader network is already sized for UCODE 8 — upgrading mid-program to UCODE 9 often introduces unintended read-rate variance (UCODE 9's better sensitivity causes it to respond from unintended distances or through packaging the RF model wasn't calibrated for, increasing duplicate-read events) that can complicate portal calibration. Consistency across the tag population matters more than per-tag maximum range; most large retailers formalize this by 'freezing' chip selection for a given SKU family for 3-5 years.
  • Supply-chain tertiary packaging. Outer carton and pallet tags where the read distance is short (dock-door portal <2 m tag-to-antenna) and cost scales with the number of cartons. UCODE 8 at sub-cent chip cost is appropriate. Walmart's Tier-2 mandate (2022-2026) specifies UCODE 8 or UCODE 9 interchangeably; the majority of non-apparel compliant inlay SKUs ship on UCODE 8 for cost reasons.
  • When UCODE 8 is wrong (retail POS portals with high read-rate requirements (use UCODE 9 where the 3-5 percentage-point first-pass read improvement translates to fewer manual rescans), harsh industrial with >85 °C ambient (use Monza R6-P or industrial-rated variants), high-counterfeit-risk brand authentication (use NTAG424 DNA at HF or UCODE DNA at UHF) the Authenticate strength on UCODE 8 short-form is insufficient), ultra-long-range yard/warehouse (use Impinj M800 class silicon at -25.5 dBm forward-link sensitivity), and tire-cure or autoclave applications (use Monza R6-P with tested 200 °C tolerance).

UCODE 8 vs UCODE 8m vs UCODE 9 selection

  • Need extra memory for a serialized backup? — UCODE 8m (SL3S1215) with 32 bits user memory. Most common for hospitality/linen applications that serialize items at the wash cycle and want a backup on-tag beyond the central database. A typical encoding uses 16 bits for a wash-cycle counter and 16 bits for a garment-class code. Also the default choice for rental-equipment programs that need a minimal on-tag record when the back-office database is temporarily unreachable.
  • Need longer EPC (128-bit SGTIN-198 truncated or similar)? — UCODE 8 (SL3S1205) with 128-bit EPC. Less common in mainstream retail; most retailers use 96-bit SGTIN-96 or SSCC-96 encodings. SL3S1205 shows up for defense/aerospace programs using custom 128-bit proprietary identifiers, and for some pharmaceutical track-and-trace programs encoding full GTIN plus expiry plus lot code in the EPC bank.
  • Need best-in-class sensitivity for POS portal performance? — UCODE 9 (SL3S1206) at -23.5 dBm best-in-class forward-link sensitivity. The ~0.5 dB advantage over UCODE 8 plus stronger anti-tear and Self-Adjust features can move a portal from 97% to 99% first-pass read in marginal RF environments. Typical retailer rule-of-thumb: at <US$0.15/item chip-cost-neutral threshold, specify UCODE 9; at >US$0.15 economic sensitivity, specify UCODE 8m. For maximum-memory industrial deployments use UCODE 9xm (SL3S1005, up to 752 bits user memory) or UCODE 9xe (SL3S1216, extended EPC up to 448 bits).
  • Need Untraceable / Authenticate for EU retail privacy? — both UCODE 8m and UCODE 9 support it. Either works under the CEN CWA 16924 recommendation. If no other driver, UCODE 8m is the cost-optimal choice; if the retailer also wants the stronger crypto suite 0x00 02 and range-reduction privacy mode, upgrade to UCODE 9.
  • Need high-temperature tolerance? — neither UCODE 8 nor UCODE 9 is suitable for sustained operation beyond 85 °C. Specify Monza R6-P (for tire-cure at 200 °C/40 min), Alien Higgs-EC / Higgs-9 (industrial temperature), or a UHF chip specifically rated for automotive/industrial temperature ranges. UCODE 8 is acceptable only for brief 125 °C excursions (total lifetime exposure <30 minutes cumulative).
  • Need cost parity with the lowest-possible chip in market? — UCODE 8 SL3S1203 is still typically the global cost floor in 2026, with EM Microelectronic's em|echo series and Alien Higgs-3 closing the gap by a fraction of a cent but not displacing UCODE 8 for most converter supply agreements. Multi-source is straightforward: UCODE 8 / Higgs-3 / Monza R6 are all drop-in on a properly-tuned wide-band reference antenna at a small performance penalty.

NXP reference documents

  • UCODE 8/8m SL3S1205_15 Product Data Sheet (doc ID SL3S1205_15, Rev. 3.6, 2 December 2021). Memory organization, command set, sensitivity characterization across 860-960 MHz, electrical characteristics tables, package information. Available at nxp.com/docs/en/data-sheet/SL3S1205_15.pdf.
  • AN11734 — UCODE 8 personalization guide. EPC encoding examples (SGTIN-96, SGTIN-128, SSCC-96, GIAI-96), TID-based serialization workflow, password management flow, recommended Lock command sequence for tamper protection.
  • AN12126 — UCODE 8 privacy features: Untraceable and short-form Authenticate command sequences with test vectors, recommended POS integration flow for EU retail privacy compliance.
  • GS1 EPC Gen2 v2.1 Air Interface Protocol (Release 2.1, August 2015 with errata through 2023). The specification UCODE 8 implements. UCODE 8 was one of the first v2-compliant chips to reach cost-sensitive retail volume, and GS1's v2 conformance program listed it at launch.
  • ISO/IEC 18000-63:2015 — the ISO air-interface equivalent of Gen2 v2. UCODE 8 carries full ISO certification, relevant for markets (Japan, Korea, certain Latin American procurement frameworks) that require ISO rather than GS1 certification statements in the tender documentation.

UCODE 8 commercial posture, legacy-program economics and long-tail supply reality

UCODE 8 has been the cost-of-gravity UHF silicon for so long that a generation of inlay converters, retailer RFID managers and library-system integrators have built their operating models around its specific performance envelope, pricing curve and multi-source availability. Understanding the commercial dynamics (how UCODE 8 shipped through the 2020-2022 shortage, how the pricing curve has moved in the UCODE 9 era, and why several large programs still lock SKUs to UCODE 8 through the end of the decade) is essential for procurement, program engineering and strategic-sourcing decisions in 2026.

  • Wafer fab and process node. UCODE 8 is produced at NXP Kirchheim-Teck (Germany) and Singapore fab sites on a 300 nm RF-CMOS process node, the same node that carried UCODE 7 and UCODE 7xm production. The 300 nm geometry is modest by modern standards but economically efficient for the sub-1-mm² die sizes typical of UHF RFID silicon (where the chip is dominated by RF front-end analog area, not digital logic). UCODE 9's migration to 180 nm gave it both the sensitivity uplift and a smaller die, but the 300 nm UCODE 8 line remains cost-advantaged for the foreseeable future because the depreciated 300 nm wafer-fab capacity has effectively zero marginal capital cost to NXP. Internal NXP conference disclosures through 2024 indicate UCODE 8 will run on the 300 nm line through at least 2028.
  • 2020-2022 semiconductor shortage and UCODE 8 allocation — the pandemic-era wafer-capacity crunch that disrupted automotive and consumer-electronics silicon hit UHF RFID unevenly: UCODE 8 was partially insulated because its 300 nm process ran in legacy fabs not competing for advanced-node capacity, but the strap-assembly bottleneck (limited flip-chip capacity at Smartrac, Avery Dennison, Arizon, Muhlbauer) squeezed availability. Strap lead times stretched from 4-6 weeks baseline to 20-30 weeks at peak Q2-2022; finished inlay prices rose 40-60% on spot buys and 15-25% on quarterly agreements. The aftermath has been a structural shift toward dual-sourcing (UCODE 8 + Impinj Monza R6 + Alien Higgs-3) at converter level and multi-year supply commitments (18-36 months) at enterprise buyer level for Walmart, Tesco, Zara and Decathlon tier-1 mandate programs.
  • Strap pricing trajectory and 2026 economic reality — 2019 baseline UCODE 8 strap pricing was approximately USD 0.015-0.025 per unit at 100M+ volume. 2022 peak pricing reached USD 0.025-0.040 during the shortage. 2025-2026 normalized pricing is in the USD 0.010-0.018 range as UCODE 9 volume ramp relieved allocation pressure on UCODE 8 and the 300 nm line returned to full utilization. Finished dry-inlay pricing at 100M volume is USD 0.025-0.040 per tag; finished wet-inlay (PSA-backed label ready for thermal printing) is USD 0.045-0.065 per tag. These price points are the floor for any UHF RFID application. No other cost-focused chip (EM Microelectronic em|echo, Alien Higgs-3, Fudan Microelectronics FM-13DL family) materially undercuts UCODE 8 at these volumes in 2026, and the pricing has anchored the industry-wide per-unit floor for retail apparel tertiary tags, library inlays and transit-ticket substrates.
  • Authorized converter landscape: NXP's authorized strap-assembler list for UCODE 8 runs through Smartrac/Avery Dennison (the largest single volume customer globally post their 2020 acquisition merge), Invengo, Arizon, Beontag, Xerafy (specialized in industrial form factors), Hana Micron (Korea-centric), CCL Industries (after the 2022 Checkpoint Systems reacquisition realignment), and Muhlbauer (equipment-led with some direct strap-assembly capacity). Downstream inlay converter landscape for finished inlays: Avery Dennison ~40% global UHF finished-inlay share (UCODE 8 and UCODE 9 combined), Beontag 10-12% (strong in LATAM and EU), Arizon 8-10% (strong in APAC), SATO 6-8% (strong in APAC), Honeywell/Intermec, Checkpoint, Confidex (industrial), HID FLeX (industrial/government), Identiv, Xerafy (industrial). Proud Tek sources UCODE 8 inlays from Avery Dennison, Smartrac, Arizon and a verified Chinese converter network with chip-authenticity clauses in the master-supply agreements.
  • Authorized distribution and counterfeit exposure. Authorized NXP UCODE 8 distribution moves through Arrow Electronics and Richardson RFPD in the Americas and Europe, and through a small number of NXP direct accounts at USD 5M+ annual threshold. Chip purchases outside this authorized channel (particularly through Shenzhen Huaqiangbei distributors, Taobao/1688 direct sellers and some Middle-Eastern resellers) frequently turn up with TID-field anomalies indicating counterfeit re-marking: UCODE 7 (TID model ID 0x030) re-marked as UCODE 8 (0x070/0x050) is the most common pattern in 2023-2025 incoming-inspection data. Authentic UCODE 8 returns TID prefix 0xE280 + correct model ID and passes a random-serial-uniqueness test (scan 500+ tags, confirm no repeating serials within the lot). Authenticate round-trip verification is available but seldom deployed at incoming inspection because of the extra reader workflow required.
  • Legacy-program freeze and SKU-lock dynamics. Several large UCODE-8-specified programs explicitly freeze chip selection for 3-5 years to maintain read-rate consistency across the installed tag population. Bibliotheca's library-RFID installed base (UK, Scandinavia, Benelux) continues to specify UCODE 8 replacement inlays; Paris RATP's Navigo Easy fare-card format is UCODE-8-spec through the 2026 contract renewal window; most major US retail Tier-2 mandate suppliers still deliver on UCODE 8 for case and pallet tertiary packaging. The freeze is rational engineering (UCODE 9's stronger sensitivity would create false-read and over-range issues in reader networks calibrated for UCODE 8's envelope) but it also means UCODE 8 production demand remains structurally high through at least 2028 independent of new-deployment preference for UCODE 9.
  • Sourcing strategy for 2026 buyers — single-source UCODE 8 procurement was acceptable through 2019, then dangerous through 2022, and in 2026 is typically a dual-source specification (UCODE 8 primary + Monza R6 or Higgs-3 qualified alternate, both validated on the same reference inlay antenna family). Triple-sourcing (adding Alien Higgs-9 or a Fudan/Quanray Chinese-origin chip) is increasingly common for buyers who experienced severe 2021-2022 shortage impact. Chinese-origin UHF silicon from Fudan Microelectronics (FM-13DL series) and Quanray Electronics has closed a substantial portion of the sensitivity gap with UCODE 8 at slightly lower unit cost and is qualified into the converter stacks of Beontag, SATO and some HID FLeX programs, though Western-domiciled buyers sometimes decline to qualify Chinese-origin silicon for geopolitical-supply-chain policy reasons (US CHIPS Act, EU Chips Act, UK National Security and Investment Act 2021).
  • EOL posture and UCODE 8 transition timing. NXP has not announced UCODE 8 end-of-life and has signaled at converter-partner conferences through 2024 that UCODE 8 production will continue through at least 2028. The transition to UCODE 10 (expected 2027-2028, rumored 180 nm RF-CMOS with ~1 dB additional sensitivity over UCODE 9 plus expanded in-chip temperature sensor and crypto-agility features) is expected to displace UCODE 9 first, then gradually flow down to displace UCODE 8 in low-cost tiers around 2030. Buyers specifying new 2026-2028 programs should generally default to UCODE 9 for any SKU above the USD 0.15/unit cost-neutral threshold and default to UCODE 8 or UCODE 8m for below-threshold SKUs, with a planned 2028-2030 re-spec-to-UCODE 9 review as UCODE 8 supply naturally tails off.
  • Proud Tek converter stance and buyer-support posture. Proud Tek maintains UCODE 8 and UCODE 9 side-by-side on our reference antenna families (standard Dogbone, Miniweb, Short Dipole, apparel AD-383u7-class, anti-metal Ironside-class), enabling drop-in chip substitution with minimal antenna retuning where the retailer mandate permits interchangeability. Our master purchase agreements with NXP authorized strap assemblers include chip-authenticity clauses with penalty terms for TID-mismatch failures, incoming-inspection TID-field validation on every strap lot, and sample-unit retention for 24 months post-delivery in case of downstream compliance disputes. Buyers specifying UCODE 8 for legacy-program continuity can expect consistent silicon authenticity, stable per-unit pricing at the 100M+ volume tier, and the option to qualify UCODE 9 or alternative-source chips into the same SKU family as a future migration path.

Specifications at a glance

Parameter UCODE 8 (SL3S1205) UCODE 8m (SL3S1215)
Operating frequency 860–960 MHz860–960 MHz
Air-interface standard EPC Gen2 v2 / ISO 18000-63EPC Gen2 v2 / ISO 18000-63
EPC memory 128 bits96 bits
User memory 032 bits
TID memory 96 bits unique96 bits unique
Kill/Access passwords 32 bits each32 bits each
Forward-link sensitivity -23 dBm-23 dBm
Write sensitivity -18 dBm-18 dBm
Untraceable support Yes (Gen2 v2 §6.3.2.5)Yes (Gen2 v2 §6.3.2.5)
Authenticate (short-form) Yes (suite 0x0001)Yes (suite 0x0001)
Anti-collision rate (typical) ~500 tags/sec~500 tags/sec
Chip impedance at 915 MHz ~11-j120 Ω~11-j120 Ω
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 at 25 °C≥ 20 years at 25 °C
Endurance (writes) 100,000 cycles100,000 cycles
Typical unit cost (at strap volume) Lowest in class~10% premium over SL3S1205

Useful next pages

Use these linked product, guide and comparison pages to keep the next click specific and practical.

FAQ

Should I specify UCODE 8 or UCODE 9 for a new retail deployment?

UCODE 9 for new deployments at any meaningful scale where POS portal performance matters. The sensitivity upgrade (~0.5 dB forward-link improvement from -23 dBm to -23.5 dBm best-in-class, plus better Self-Adjust tuning and the range-reduction Untraceable submode) pays back in portal read-rate improvement, typically 1-3 percentage points of first-pass read in marginal RF environments. Operationally, that time saving is worth far more than the typical per-chip cost premium on any SKU above roughly US$0.15 retail. UCODE 8 remains appropriate for billion-unit promotional and single-use programs (conference badges, disposable transit tickets, event wristbands, festival access) where the tag is discarded quickly, the read environment is controlled, and per-unit cost dominates the economics. That cohort is still where the majority of UCODE 8 silicon ships in 2026. A common hybrid strategy: UCODE 9 for apparel and durables, UCODE 8m for promotional and packaging tertiary, both deployed under the same EPC encoding scheme so the back-end software is chip-agnostic.

What is the difference between UCODE 8 (SL3S1203) and UCODE 8m (SL3S1213)?

User memory. SL3S1205 has a 128-bit EPC with no user memory: maximum encoding flexibility at the expense of on-tag item-specific data. SL3S1215 has a 96-bit EPC plus 32 bits of user memory (two 16-bit words at bank 11 addresses 0x00 and 0x01), which is the more common choice for applications that want a backup serial, a factory lot code, or item-level metadata on the tag itself. Typical usage is 16 bits for a wash-cycle or maintenance counter and 16 bits for a class/category identifier. Both chips have identical sensitivity (-23 dBm forward-link, -18 dBm write per the SL3S1205_15 datasheet), temperature envelope (-40 °C to +85 °C), command support (Untraceable / short-form Authenticate / File Open with one FileID) and anti-collision performance; the only functional difference reader-side is the memory partition. Price delta is typically 5-10% at strap volume.

Can UCODE 8 be used for EU retail deployments that require privacy compliance?

Yes. UCODE 8 supports the EPC Gen2 v2 Untraceable command (Section 6.3.2.5), which when activated at the POS with the Access password shortens the tag's response to a non-unique pattern, restricts TID bank reads to the allocation class identifier, and suppresses user-memory reads. Giving the customer privacy after the item leaves the store. Syntax is the same as UCODE 9's Untraceable command. Short-form Authenticate (suite 0x0001) is also supported for anti-counterfeiting. The CEN CWA 16924 workshop agreement (the EU retail RFID industrial framework) recognizes Gen2 v2 Untraceable as the minimum acceptable privacy mechanism for item-level RFID at retail, and UCODE 8m is the lowest-cost silicon in production that meets it. For retailers where UHF RFID is a 2024+ deployment, UCODE 9 is the more common specification for new inlay runs (it adds a 'range reduction' privacy mode that continues to allow short-range reads post-sale for returns), but UCODE 8 with Untraceable satisfies the privacy requirement at a roughly 30% lower silicon cost.

How do I detect counterfeit chips being sold as UCODE 8?

Read the full 96-bit TID. Authentic UCODE 8 returns: first 8 bits = 0xE2 (EPC class identifier per Gen2 v2), next 12 bits = 0x801 (NXP mask designer prefix), then a 12-bit NXP model-ID field, with the remaining bits forming the per-chip unique serial. Chinese-OEM clones marketed as 'UCODE 8 compatible' frequently return an incorrect model ID, an incorrect mask-designer field, or non-unique TID serials revealed by scanning 500+ tags and finding repeat serials within a single lot. The most common counterfeit pattern in 2024-2025 is UCODE 7 silicon (SL3S1204) re-marked as UCODE 8. Incoming-inspection scripts should: (1) verify the 8-bit class identifier = 0xE2, (2) verify the mask-designer field matches the NXP-registered prefix, (3) verify the model-ID field per the NXP SL3S1205_15 datasheet's TID structure section, (4) sample 200-500 tags per incoming lot and confirm all serials are unique, (5) cross-validate with the converter's supply-chain audit documents showing authorised NXP strap receipt. Most serious counterfeit issues historically trace to smaller converters bidding on very high-volume jobs at sub-market pricing; maintain chip-level authenticity clauses in master purchase agreements with penalty terms for TID mismatches.

Does UCODE 8 work on metal surfaces?

Only with a dedicated anti-metal inlay design. Typically 0.5-1 mm PET, foam spacer, or ferrite absorber between the antenna and the metal substrate. Standard UCODE 8 inlays laminated directly onto metal detune to the point of non-functionality (the metal effectively short-circuits the antenna's near-field). Proud Tek stocks anti-metal UCODE 8 variants for cost-sensitive applications (waste-bin tags, laundry hangers, metal shelving labels) typically 5-8 m read range on 30 dBm reader output with a purpose-designed antenna. For performance-critical metal applications (automotive assembly-line asset tracking, mining equipment, oil-and-gas pipeline assets) use Monza R6 or Monza R6-P on a reference anti-metal antenna (e.g., Xerafy Global Trak, Confidex Ironside) where the combination of higher chip sensitivity and optimized antenna geometry delivers 8-12 m practical range. For extreme cases (embedded-in-metal), use an on-metal tag with a resonant-cavity antenna. Here chip selection matters less than antenna design.

What is the longest EPC I can encode on UCODE 8 (SL3S1203)?

128 bits, which accommodates SGTIN-96 (96 bits), SSCC-96 (96 bits), GIAI-96 (96 bits), GRAI-96 (96 bits), SGTIN-198 truncated forms (variable up to 140 bits, practically limited to 128 on SL3S1205), or a custom 128-bit company-private encoding (used in defense, aerospace and certain pharmaceutical track-and-trace deployments). The 128-bit EPC bank lets you encode longer identifiers than the 96-bit-only variant without dipping into user memory (which SL3S1205 doesn't have). For deployments that need both a long EPC and user memory (e.g., GIAI-202 plus a maintenance log), UCODE 9xm (SL3S1005 — supports up to 752 bits user memory in three configurable allocations) is typically the correct choice. Note that the Gen2 PC word's 5-bit Length field encodes EPC length in 16-bit words up to 31 words (496 bits), so the chip-level 128-bit limit is the binding constraint on SL3S1205, not the protocol.

Is UCODE 8 still in production, or has NXP EOL'd it?

Still in full production in 2026 with no EOL announcement. UCODE 8 ships in volumes measured in tens of billions of units per year globally (NXP's 2024 UHF RFID silicon revenue commentary identified UCODE 8 as still the single largest volume product in the UCODE family despite UCODE 9 gaining share on new high-value deployments) and NXP has informally signaled continued production through at least 2028 based on converter-side product-lifecycle discussions. UCODE 9 (SL3S1206, launched 2020) is the successor for high-sensitivity applications but does not displace UCODE 8 at the cost-optimized end of the market. EOL concerns should focus on older products (UCODE 7 SL3S1204, UCODE G2iL/G2iL+ SL3S1203_1213, UCODE G2XM/G2XL) rather than UCODE 8; converters routinely offer UCODE 8 and UCODE 9 on the same reference antenna family as drop-in alternatives, giving buyers flexibility to move between them based on price and performance tradeoffs.

Sources & references

Primary standards, OEM datasheets and regulatory documents cited by this article. All URLs were verified on the access date shown below.

  1. NXP UCODE 8 / 8m Product Page (SL3S1205-15)NXP Semiconductors · accessed May 10, 2026

    Canonical NXP product page for UCODE 8 / 8m — authority for the -23 dBm read sensitivity, 96-bit / 128-bit EPC memory variants, and the Self-Adjust / Brand Protection feature set referenced throughout the encyclopedia. (Note: SL3S1204 is UCODE 7, not UCODE 8.)

  2. NXP SL3S1205_15 UCODE 8/8m Product Data Sheet, Rev. 3.6 (2 December 2021)NXP Semiconductors · accessed May 10, 2026

    Authoritative datasheet specifying the -23 dBm read / -18 dBm write sensitivity, electrical characteristics, memory bank layout (128-bit EPC on SL3S1205, 96-bit EPC + 32-bit user on SL3S1215), supported EPC Gen2 v2 commands and lock structure used in the chip-specification tables.

  3. NXP AN11809 — UCODE 8 Features and HintsNXP Semiconductors · accessed Apr 20, 2026

    NXP application note covering command flow, Self-Adjust initialization, and Brand Protection origins. Referenced in the operational-features section.

  4. ISO/IEC 18000-63:2015 — Parameters for air interface communications at 860-960 MHz Type CISO · Dec 1, 2015 · accessed Apr 20, 2026

    UHF Gen2 air-interface standard that UCODE 8 implements — baseline for protocol conformance claims.

  5. GS1 EPC Radio-Frequency Identity Protocols — Generation-2 UHF RFID Standard (Gen2v2)GS1 · Jul 1, 2018 · accessed Apr 20, 2026

    Industry-authored Gen2 specification — cited in the v1 vs v2 command-support discussion for UCODE 8 variants.

  6. FCC Rules and Regulations, Title 47 CFR Part 15.247U.S. Federal Communications Commission (FCC) · accessed Apr 20, 2026

    US regulatory authority: referenced in the FCC-tuned inlay-variant discussion.

  7. ETSI EN 302 208 — RFID Equipment in the 865-868 MHz and 915-921 MHz bandsEuropean Telecommunications Standards Institute (ETSI) · accessed Apr 20, 2026

    European harmonized standard: referenced in the ETSI-tuned inlay-variant discussion.

  8. RAIN Alliance — Certified Product DirectoryRAIN Alliance · accessed Apr 20, 2026

    Tag-level certification programme for UHF RFID inlays. Cited where the guide discusses conformance beyond chip-level pre-conformance.

10+ Years RFID Manufacturing
ISO 9001 Certified Factory
500+ Enterprise Clients
50+ Countries Served

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.

We'll only use this to reply to your inquiry.
Optional, but helps us route your inquiry faster.
e.g. 5,000 pcs
e.g. hotel, event, asset tracking
Chip preference, timeline, special requirements...

Next step

Ready to discuss your project?

Use the contact route when you are ready for pricing, samples, or compatibility help, or continue into the linked product and comparison pages below.