RAIN RFID Explained

What RAIN RFID is — brand, alliance, standard stack and the problem it solves

Every few years the RFID industry rebrands the same radio waves and waits to see whether the new name sticks. RAIN is the rare case where it did, and deserved to: before it, 'just buy some UHF RFID tags' was a sentence that could end in a stockroom full of tags that read perfectly — on exactly one reader brand, the one your supplier happened to favor. RAIN RFID is not a new protocol; it is the industry brand and certification programme that sits on top of the existing UHF RFID standard stack. Understanding the relationship between RAIN the brand, EPC Gen2 the specification, ISO/IEC 18000-63 the international standard, and GS1 the data-standard body is the foundation for understanding how the ecosystem hangs together and why compatibility across vendors is not accidental.

• Brand versus protocol distinction. RAIN RFID is the industry brand name administered by the RAIN Alliance, analogous to Wi-Fi being the brand for IEEE 802.11 wireless LAN. The underlying technical specification is GS1 EPC Gen2v2, formally standardized as ISO/IEC 18000-63 at the international level. A product advertised as 'RAIN RFID' is an EPC Gen2v2 / ISO 18000-63 product that has been certified for interoperability through the RAIN programme.
• Standard-stack layering: the stack has four layers: the air-interface protocol (EPC Gen2v2 / ISO 18000-63) governs reader-to-tag radio communication; the data-encoding standards (GS1 SGTIN-96, SSCC-96, GRAI-96) govern what the EPC bytes mean; the application-level interfaces (LLRP, EPCIS) govern how readers talk to middleware and how events exchange between trading partners; and RAIN branding certifies that implementations conform at each layer.
• Problem it solves: before RAIN branding emerged, buyers faced a fragmented UHF RFID market with multiple conflicting protocol generations, inconsistent certification, and vendor-specific data-encoding practices. Retailers could not mandate 'UHF RFID tags' meaningfully because suppliers shipped tags that read reliably only on the tag vendor's preferred reader. RAIN solved the branding and certification problem and created the single global ecosystem that large-scale retailer mandates require.
• Frequency range and global operation. RAIN RFID operates across the 860-960 MHz global UHF band, with regional sub-allocations (865-868 MHz in Europe under EN 302 208, 902-928 MHz in North America under FCC Part 15.247, 916.7-923.5 MHz in Japan, 920-925 MHz in China). Modern RAIN chips are designed to operate across the full band for global supply-chain compatibility.
• Read/write at scale. RAIN readers scan hundreds to thousands of tagged items per second through cardboard, plastic and fabric without line-of-sight. The protocol supports read-only inventory operations (the common case), field encoding (writing new EPC values after manufacture), user-memory updates (maintenance data, inspection records) and lock/kill commands (permanent enforcement or deactivation).
• Cloud and enterprise integration. RAIN readers connect via standard network protocols (Ethernet, Wi-Fi, USB-host) and expose LLRP or proprietary APIs to middleware that in turn writes to ERP, WMS, POS, EPCIS repositories and cloud platforms. The enterprise integration layer has matured to the point where RAIN events flow into retail and logistics systems without custom-integration effort per deployment.

The RAIN Alliance — membership structure, certification programme and governance

The RAIN Alliance is a non-profit industry association whose members span the entire value chain of the RAIN RFID ecosystem. Understanding the membership structure and the Alliance's certification mechanics helps buyers interpret vendor claims and helps suppliers understand where to invest in credentialing for large-account sales.

• Membership composition: over 180 member companies covering chip manufacturers (NXP, Impinj, STMicroelectronics, Infineon, Farsens), tag and inlay manufacturers (Avery Dennison, SATO, Checkpoint, HID, Proud Tek and many others), reader manufacturers (Zebra, Impinj, Honeywell, Alien, Nordic ID), integrators and software providers, and end-user brand operators in retail, logistics and healthcare.
• Working groups and governance. The Alliance operates technical working groups for retail, logistics, automotive, pharmaceutical, airline and IoT verticals, each producing application-guidance documents, use-case white papers and test specifications. The working-group output is where vertical-specific interoperability requirements are codified ahead of broader standardization.
• Certification programme: the Alliance operates a conformance-testing programme where member products are tested against the EPC Gen2v2 specification at accredited labs. Certified products receive a Certification ID and are listed in the public Certified Products Database. Buyers can verify a vendor's specific product-model conformance before purchase.
• Interoperability plug-fests: in addition to lab-based certification, the Alliance sponsors periodic interoperability events where vendors bring their products and test them against each other's latest implementations. Plug-fests surface edge-case issues (dense-reader-mode coexistence, unusual protocol corners) that lab testing may not exercise.
• Marketing and adoption role. Alongside technical certification, the Alliance runs vertical-market education, presents at industry events (NRF, IATA AVSEC, HIMSS, retail-industry conferences) and maintains the tag-volume statistics that are the public measure of ecosystem growth. The marketing function is non-trivial because enterprise RAIN adoption requires buyer education as much as technical readiness.
• Member-directed roadmap: the Alliance's technical roadmap reflects the priorities of its chip, tag, reader and end-user members, rather than a single vendor's product strategy. The member-directed governance is the mechanism by which the ecosystem avoids the 'winner-takes-all' dynamics that have fragmented other IoT technologies.
• Relationship with GS1 — the Alliance works closely with GS1, the data-standards body that owns the GS1 Company Prefix system, the SGTIN-96/SSCC-96/GRAI-96 encoding standards, the EPCIS event-envelope specification, and the original EPC Gen2 standard that became ISO 18000-63. GS1 owns the data layer; RAIN Alliance owns the technology-brand and certification layer.

Market drivers — why RAIN RFID has compounded to tens of billions of tags annually

RAIN's multi-year market trajectory (45.5B chips in 2023, 52.8B in 2024, 42.7B in 2025) is the consequence of overlapping adoption drivers, not a single retailer mandate. Understanding the driver portfolio helps operators anticipate where demand will come from next and helps suppliers prioritize capacity and capability investments. Each driver has its own timing and adoption curve, and together they produced the approximately 50 percent four-year market growth from 2022-2025 (RAIN Alliance) that smoothed through the 2025 macroeconomic and inventory-cycle dip.

• Retail item-level mandates. Walmart's expanding mandate across apparel, home goods, consumer electronics, sporting goods and other categories through 2026 is the largest single driver in North America. Target, Nordstrom, Macy's, Kohl's, BJ's and others run parallel programmes. Inditex/Zara, UNIQLO, Decathlon and major European retailers run long-running item-level programmes at similar scale.
• Omnichannel fulfillment: ship-from-store, buy-online-pick-up-in-store and in-store-return-online workflows depend on accurate item-level inventory, and the RAIN-enabled inventory accuracy of 95-99% makes these workflows economically viable. Retailers without item-level RFID struggle to compete on omnichannel fulfilment speed and reliability.
• Airline baggage IATA Resolution 753 — requires airlines to track passenger baggage at key points throughout the journey. RAIN RFID is one of several tracking technologies adopted under the resolution alongside optical barcode (still the most widely deployed at over 90 percent of qualifying airports) and OCR. Per IATA's 2025 implementation report, approximately 27 percent of surveyed airports use RFID, with adoption notably higher at mega-hubs (around 54 percent) where Delta, Lufthansa, Air France-KLM, Qantas and others have deployed at scale and reported material reductions in mishandled-bag rates.
• Healthcare asset tracking: surgical instrument trays, medical devices, IV pumps, infusion sets and pharmaceutical inventory all adopt RAIN RFID for inventory accuracy, sterilization cycle tracking, utilization measurement and regulatory recordkeeping. DSCSA pharmaceutical serialization extends the adoption into drug-package level for specific programmes.
• Automotive parts and manufacturing. Automotive OEMs and tier-1 suppliers use RAIN RFID for work-in-progress tracking, parts-kitting verification, returnable-packaging tracking and finished-vehicle dwell-time measurement at plants and distribution yards. The industrial-scale of automotive creates multi-million-tag annual programmes at single customers.
• EU Digital Product Passport. The ESPR-driven DPP obligation for textiles, electronics, furniture, construction and other categories adds RAIN demand where dual-technology NFC+UHF labels satisfy both consumer-tap DPP and supply-chain UHF visibility on one label.
• Tag-cost decline: RAIN inlay prices have fallen below $0.05 at volume, with the chip cost approaching $0.015-0.02 in high volume. The cost curve enables tagging of items valued at $5-10, expanding the addressable SKU base from the historic $30+ apparel threshold to a materially wider portfolio.

Vertical-market portfolio — apparel, logistics, healthcare, aviation, industrial and beyond

RAIN RFID's vertical portfolio has expanded well beyond its apparel-retail origins. Each vertical has its own reference architectures, tag-form-factor preferences and integration patterns. Understanding the vertical landscape helps buyers benchmark their own deployment against peer-best-practice and helps suppliers target capability investments to vertical-specific requirements.

• Apparel retail: item-level tags on hang-tags or care-label inlays, portal reads at receiving, handheld cycle-counts on the sales floor, POS-lane deactivation or pass-through reads at checkout. Accuracy targets of 95-99% at the item level, with inventory-accuracy-to-sales-lift correlation documented across multiple peer-reviewed studies.
• Logistics and 3PL — case and pallet SSCC-96 tagging, portal reads at dock doors, automated ASN reconciliation at receiving, shipment-integrity verification at outbound. Integrates with WMS and TMS for automated receiving and shipping event recording, supporting both retailer-mandate compliance and operational efficiency.
• Healthcare: surgical instrument tray tags, medical device serial tracking, IV pump and infusion equipment asset management, specimen and blood-bag traceability, pharmaceutical case-level and unit-level serialization. Integrates with hospital asset management systems and increasingly with sterilization-cycle tracking and clinical engineering.
• Airline baggage and cargo. IATA Resolution 753 baggage tags, unit-load-device (ULD) tracking for air-cargo asset management, aircraft-part and rotable-component tracking for MRO operations. Baggage read rates now exceed 99% at major carrier hubs, and ULD tracking reduces lost-asset rates materially.
• Industrial asset management: tool cribs, returnable-packaging fleets, pallet pools, rental equipment tracking, and high-value-asset serialization for manufacturing and construction. Typical ROI driven by reduction in asset loss, improved utilization and labour savings on manual inventory.
• Automotive and aerospace: in-plant WIP tracking, parts-kitting verification, finished-vehicle yard management, returnable-container tracking. Aerospace adds parts-lifecycle tracking where individual components are serialized from manufacture through multiple maintenance cycles over decades of service.
• Emerging categories: food and agriculture traceability under FSMA 204, consumer-product EU Digital Product Passport implementations, rental and shared-goods platforms, event ticketing and access control, library materials management, and a growing list of vertical applications as the tag-cost and integration-cost curves continue to decline.

Coexistence with NFC, BLE and other wireless technologies

Vendor marketing loves a cage match — RAIN versus NFC, NFC versus QR, everything versus everything — because a single winner is easier to sell than a Venn diagram. The reality below is less dramatic and considerably more useful. RAIN RFID is one of several short- and long-range wireless identification technologies, and understanding where RAIN fits versus NFC, BLE, QR codes and active RFID helps buyers select the right technology for each use case. The technologies are complementary more often than they are competitive, and many mature deployments use multiple carrier technologies tuned to different use cases within the same product lifecycle.

• RAIN versus NFC: NFC operates at 13.56 MHz with ~4 cm read range and requires a smartphone or dedicated reader for tap-proximity interaction. RAIN operates at UHF with 3-15 meter read range and requires dedicated UHF reader infrastructure. NFC is consumer-tap; RAIN is supply-chain-read. Dual-technology NFC+UHF labels serve both use cases on a single product.
• RAIN versus BLE: Bluetooth Low Energy uses battery-powered beacons with active transmission and ranges of 10-100 meters. BLE is suited for tracking battery-tolerant assets (laptops, equipment, people carrying phones) and for live-location use cases; RAIN is suited for passive (no-battery) item-level tagging at high density. The two coexist in asset tracking programmes where some assets carry BLE beacons and many more carry passive RAIN tags.
• RAIN versus active RFID. Active RFID systems use battery-powered tags transmitting at intervals, with ranges up to 100+ meters. Active systems are much higher cost per tag ($5-50+) and suit high-value-asset or real-time-location applications. RAIN passive tags at sub-dollar cost are the right choice for high-volume item-level tagging.
• RAIN versus QR: QR codes are printed, consumer-scannable and essentially free at volume. RAIN tags are electronic, require reader infrastructure and cost cents per tag. QR is right for one-time consumer-tap applications with no supply-chain visibility requirement; RAIN is right when high-volume automated reading or anti-counterfeiting-grade authentication is required.
• RAIN versus LoRa and cellular IoT. Wide-area IoT technologies (LoRaWAN, Cat-M1, NB-IoT) serve asset tracking across kilometer-scale distances with battery-powered transmitters. RAIN serves passive, no-battery, meter-scale identification at high density. The technologies are complementary rather than substitutes. RAIN for item-level passive tagging, wide-area IoT for asset-level active tracking.
• Sensor-integrated RAIN: newer RAIN chips integrate temperature, humidity, tamper and accelerometer sensors into the passive tag, blurring the boundary between pure identification and sensor-IoT applications. Sensor-RAIN tags serve cold-chain monitoring, structural-health monitoring and other applications where passive-tag economics combine with sensor data capture.
• Dual-technology label architectures. Single labels carrying NFC + UHF or UHF + BLE are increasingly common in mature deployments where different lifecycle stages benefit from different technologies. Understanding the coexistence architecture helps programme planners avoid the either-or framing that is sometimes presented in vendor marketing.

RAIN chip generations — Impinj Monza, NXP UCODE, Alien Higgs and the evolution to Gen2v2

The RAIN ecosystem includes several chip manufacturers whose successive chip generations have driven the cost and performance curve of the technology. Understanding the chip landscape and the specific capabilities of current-generation chips (Impinj M700/M800, NXP UCODE 9 and UCODE DNA, Alien Higgs-9) helps buyers specify tags appropriately for their performance and feature requirements.

• Impinj Monza and M-series. The Monza family, succeeded by the M700 and M800 series, is the most widely deployed RAIN chip in retail. The M700 series (M730, M750, M770, M775) offers strong general-purpose performance with AutoTune V2, Integra V2 self-check, Enduro IC bonding and Gen2X uplift; the M800 series (M830, M850) is Impinj's current high-performance line with read sensitivity around -25.5 dBm (about 1.5 dB better than M700 and roughly 30 percent lower power consumption per the manufacturer datasheet). The M775 specifically integrates cryptographic support paired with the Impinj Authentication Service for brand-protection workloads.
• NXP UCODE family: UCODE 9, UCODE 8, UCODE 9xc and the UCODE DNA sub-family with integrated cryptographic authentication. UCODE DNA provides per-tag authentication that complements retail and brand-authentication applications, with the DNA family being NXP's answer to authenticated passive RFID for anti-counterfeiting.
• Alien Higgs family: Higgs-9, Higgs-EC and Higgs-3 cover the performance and cost curve for general-purpose RAIN applications. Alien's positioning is often price-competitive on high-volume general applications where specialized features of M-series or UCODE DNA are not required.
• Gen2v2 feature set: ratified in 2013, Gen2v2 extends the original Gen2 protocol with authenticated commands (crypto-suite support), encrypted memory access, file management with structured data organization, and untraceable mode for consumer-privacy applications. Modern chips (M700 series, UCODE 9xc, UCODE DNA) implement Gen2v2; older chips are Gen2 only and lack the extended feature set.
• Specialized sensor chips: Farsens' Rocky 100 family and similar sensor-integrated chips add temperature, humidity, tamper, strain and other sensor readings to passive RAIN tags. Applications include cold-chain, structural health monitoring and industrial condition monitoring.
• Chip-pick guidance: standard retail and general-purpose applications typically select from M700-class chips or UCODE 9 for the balance of performance and cost. Brand-authentication applications select DNA-family chips. Harsh-environment and anti-metal applications often require specific chip-antenna combinations tuned to the application substrate rather than a generic chip choice.
• Custom encoding and bespoke chips. High-volume customers sometimes specify custom TID prefixes, specific user-memory configurations, or factory pre-encoding to reduce downstream encoding costs. Credible suppliers support these customizations and coordinate with chip manufacturers on qualification and production planning.

Reader and gateway landscape — fixed portals, handhelds, overhead, embedded and the RAIN Alliance RF-Control API

The reader side of the RAIN ecosystem is as diverse as the chip side, with fixed four-port and eight-port readers, handheld scanners, overhead RTLS gateways, embedded modules for OEM integration, and a growing class of cloud-connected REST/MQTT gateways. Understanding the reader landscape helps buyers specify infrastructure that matches the deployment geometry and helps specifiers avoid over- or under-sizing infrastructure at the design stage.

• Fixed multi-port readers. The workhorse category covers Zebra FX9600 (eight-port, Linux-based), Zebra FX7500 (four-port, compact), Impinj R700 (four-port, RESTful API native), Impinj R720 (four-port, higher-performance), Alien ALR-F800 and Nordic ID Sampo S3. These are the default choice for dock-door portals, conveyor lines, stockroom stations and any deployment with structured read geometry and sustained high throughput.
• Handheld and sled readers. Zebra MC3330xR, Zebra RFD40 sled on TC series mobile computers, Honeywell IH25/IH40 handhelds, Nordic ID Merlin handhelds and TSL 1128 Bluetooth sleds. Handhelds serve cycle counting, picking verification, ad-hoc inventory and mobile receiving applications where portal infrastructure is impractical. Read rates of 300-900 tags/sec on modern sleds make full-store cycle counts in 45-90 minutes realistic for a typical apparel store.
• Overhead RTLS gateways: Impinj xArray, Impinj xSpan and Zebra ATR7000 are ceiling-mounted readers that cover zones from above with multi-beam antennas. They serve stockroom inventory visibility, retail backroom-to-sales-floor flow and hospital asset tracking applications where continuous passive visibility is valuable without per-door portals.
• Rugged outdoor and portal readers. Zebra FXR90 (IP65/IP67, outdoor-rated), Impinj R720 with outdoor antenna kit, Nordic ID Stix and similar industrial-rated readers serve outdoor yard management, truck-gate drive-throughs, cold storage and washdown environments where standard indoor readers cannot survive.
• Embedded OEM modules: ThingMagic (Novanta) M6e, M6e-Micro, Nano and Izar modules, Impinj Indy R2000/R500/E310/E710 reader chips, and Alien ALR-9650 OEM reader are the integration modules that vending machines, kiosks, medical devices and custom-fixtures use to embed RAIN reading inside a larger product. Deployment volume for embedded modules is smaller per SKU but spans a wider installed base than fixed readers.
• Antenna selection: circularly polarized antennas (5-9 dBic gain typical) for portal and general applications; linearly polarized high-gain antennas (9-12 dBi) for narrow lanes and long-range reads; patch antennas for overhead RTLS; near-field antennas for liquid and metal-adjacent applications. Cable loss on long LMR-400 or LMR-600 runs must be accounted for in link-budget calculation; premium low-loss cable and tight connector practice materially affect real-world range.
• Cloud and gateway architectures. Modern deployments increasingly use lightweight gateway devices (Impinj IoT Device Interface, Zebra Savanna gateways, Nordic ID Cloud) that abstract reader hardware behind a cloud-friendly REST/MQTT API. The architecture decouples deployment-site reader hardware from cloud middleware and simplifies multi-vendor reader fleet management for large enterprises.
• RAIN Alliance RF-Control API. The emerging standardized HTTPS+OAuth2 reader API (target GA Q4 2026 per Alliance working group) aims to unify reader configuration, inventory operations and event streaming across Impinj, Zebra, Nordic ID and other major brands. Early adopters in 2025-2026 are testing the specification; production use is expected 2026-2028. For new deployments, specifying RF-Control API support in reader RFQs future-proofs the infrastructure against vendor lock-in.

Performance envelopes — read rates, range, EIRP limits and interference tuning

The practical performance of a RAIN deployment is determined by the interaction of tag-chip sensitivity, reader power, antenna gain, regional EIRP regulations, tag density and environment. Buyers who understand the performance envelope can size infrastructure accurately and troubleshoot read-rate issues without relying on vendor marketing claims. The following envelope figures represent production-tested ranges rather than specification maxima.

• Read rate per antenna. A single four-port reader with four antennas typically achieves 700-1500 unique tag reads per second at moderate population (100-500 tags in field), rising to 2000-4000 reads per second with dense-reader-mode optimization on newer readers (Impinj R700/R720, Zebra FX9600 firmware 3.0+) in high-population scenarios (1000-5000 tags in field).
• Tag population scaling: inventory rounds for populations above 10000 tags in field are feasible with modern readers but require session tuning (typically Session 2 or Session 3 to prevent re-reads within the round), Q-adjust algorithms tuned to the expected population, and multi-antenna scheduling. Typical full-inventory time for 10000-20000 tags in a retail backroom is 2-6 minutes depending on geometry.
• Range and EIRP regulations. North America (FCC Part 15.247) allows 4 W EIRP for frequency-hopping systems, translating to typical 10-15 meter practical read range for case-level products on a good portal. Europe (ETSI EN 302 208) allows 2 W EIRP in the 865-868 MHz band, producing practical range of 6-10 meters. Japan (ARIB T106/T107) limits further to roughly 1 W EIRP. Regional power limits materially affect portal-design distance and tag-selection performance class.
• Chip sensitivity: read-sensitivity figures measured in dBm define how weak a reader signal the tag can wake up on. Impinj M800 (M830 / M850) achieves -25.5 dBm best-in-class read sensitivity per Impinj's product brief; NXP UCODE 9 sits at -23.5 dBm best-in-class; Alien Higgs-9 at -23.2 dBm; Impinj M730 / M770 at -22.6 dBm; M750 at -22.1 dBm; NXP UCODE 8 at -23 dBm; Monza R6 at -22.1 dBm per IPJ-W1700-K00. Each 3 dB of sensitivity improvement translates to approximately 40% additional range at identical transmit power, so chip choice has first-order effect on real-world read geometry.
• Orientation sensitivity: linear tags read optimally when tag dipole is aligned with reader antenna polarization; misaligned orientation causes 10-20 dB of polarization loss that collapses read range. For applications where product orientation is uncontrolled (retail hangers, tumbled cases), circularly polarized antennas and dual-dipole tag designs minimize orientation penalty.
• Interference and coexistence: multi-reader deployments require frequency planning (in Europe the 865-868 MHz band has only 4 channels, in North America 50 channels under FHSS). Dense Reader Mode (DRM) separates reader-transmit and reader-listen frequencies to reduce reader-to-reader interference. ETSI's Listen-Before-Talk polls channels before transmission and can reduce effective duty cycle below 100% in dense deployments; FCC FHSS is less affected. Deployments of 8+ readers in close proximity should model RF coexistence at design rather than discovering issues at commissioning.
• Environmental effects: metal shelving within 20 cm of tags detunes antennas and reduces read rate 20-50%; water and hydrated product (fresh meat, wet textiles) absorbs UHF energy and reduces range by similar margins. RF-friendly tag selection (anti-metal tags, on-metal tags, moisture-tolerant designs) is essential for environments where these conditions are structural rather than occasional.
• Measuring and tuning in the field. Link-budget calculators estimate theoretical range from chip sensitivity, antenna gain, cable loss, reader power and regional EIRP. Real-world commissioning should measure read rate per antenna in the actual deployment with a representative tag population, compare to link-budget prediction, and tune antenna angle, transmit power and Q algorithm based on the measured performance. Continuous monitoring in production catches drift (antenna cable corrosion, reader firmware rollback, changes to surrounding inventory density) that would otherwise silently degrade performance over time.

Gen2v3 protocol release (January 2025) — what's new and what it means for buyers

After more than a decade of stability around Gen2v2 (ratified 2013), the GS1 / RAIN Alliance technical working group published Gen2v3 in January 2025 as the first major UHF EPC air-interface revision since the original 2004 release. Buyers planning multi-year deployments need to understand what Gen2v3 adds, what migrates and what stays the same, so that procurement and infrastructure decisions made in 2025-2026 are aligned with where the ecosystem is heading.

• Query X and Query Y — advanced tag selection. The two new selection commands let the interrogator pre-filter the tag population on attributes more granular than the legacy Select command, including specific EPC schemes, EPC header values, vendor-specific feature flags and TID-encoded tag-class identifiers. The headline use case (called out in the RAIN Alliance announcement) is reading airport baggage tags when items inside the bag also carry RAIN tags; previously the interrogator could only filter by EPC bit-mask, while Query X / Y can target the specific EPC scheme used for baggage labels and ignore the rest.
• Modulated-power inventory for fringe-tag suppression. Gen2v3 lets the interrogator briefly lower its radiated field strength during portions of the inventory round so that only tags clearly within the intended read zone wake up. Tags on the outer edge of the field (the 'fringe' that historically caused phantom reads and dense-reader collisions) are temporarily under-powered and back off, then participate later if the application needs them. Effective dense-reader throughput improves and read-zone boundaries become sharper without retuning antennas.
• Read-Var — selective User and TID memory access. The new Read-Var command instructs a tag to backscatter exactly the subset of memory the reader requests, with start position and length parameters, rather than the all-or-nothing read patterns of Gen2v2. For applications that store lot, batch, expiry-date or serial extensions in User memory (pharmaceutical recalls, perishable-food rotation, cold-chain records), Read-Var captures only the relevant slice in a single round trip and reduces both air-time and middleware overhead.
• Backward compatibility commitment. Gen2v3 is strictly backward compatible. Existing Gen2v2 chips continue to operate on Gen2v3-aware readers (the readers fall back to Gen2v2 commands), and Gen2v3 chips operate on Gen2v2 readers (the new commands are simply not invoked). Solution providers may update their deployment implementation to take advantage of Gen2v3 features but are not required to do so. Reader manufacturers add support through firmware updates only — no hardware change is required on the reader side.
• Chip-vendor roadmap. Tag-chip silicon supporting Gen2v3 features started sampling through 2025 and is moving into production through 2026; STAR Systems International has shipped Gen2v3-class transponders for tolling, and the major tag-chip vendors (Impinj, NXP, EM Microelectronic, Shanghai Quanray) are aligning their next-generation product lines with Gen2v3. The Project Editor of ISO/IEC 18000-63 (Josef Preishuber-Pflügl of innobir) is the named technical lead, and the companion ISO/IEC 18000-63 update is being progressed through JTC 1/SC 31.
• Procurement guidance for 2026 and beyond. For new reader infrastructure RFQs, specify Gen2v3 firmware-upgrade support as a future-readiness clause. For new tag-chip qualifications planned for 2026-2027 production, evaluate Gen2v3-capable chips alongside the established Gen2v2 portfolio (M700/M800, UCODE 9 / 9xc / 9xe, Higgs-9). Existing deployments are not stranded by Gen2v3; the protocol's backward-compatibility property protects multi-year capital investments in installed reader and tag infrastructure.

RAIN-enabled smartphones — putting the reader in every pocket

The most strategically significant ecosystem development of 2025-2026 is the emergence of UHF-capable smartphones. Until now, reading a RAIN tag required dedicated reader hardware, which limited use cases to enterprise environments where reader infrastructure is justified. RAIN-enabled phones move the reader to the consumer device, opening a class of applications that were not previously addressable: the consumer scanning a tagged product to retrieve its Digital Product Passport, the field worker tracking assets from the device already in their pocket, and the in-store reader-equipped associate using the phone as a portable inventory tool.

• Enterprise handset shipments already underway. Leading mobile chipset suppliers are integrating RAIN reader silicon into both enterprise and consumer smartphone reference designs, and RAIN-enabled enterprise smartphones have been shipping for several quarters as of 2025-2026 per RAIN Alliance reporting. Enterprise deployments (logistics, retail-associate handhelds, asset-tracking field service) are the early adopter base where the device cost premium is justified by reader-replacement savings.
• Consumer demonstrations and retailer interest. Decathlon showcased live RAIN-enabled smartphone demonstrations at NRF and Euroshop 2026, with retailers signalling strong interest in consumer-facing use cases (in-store tag-scanning for product information, returns processing without dedicated reader hardware, loyalty and warranty interactions). RAIN Alliance member showcases continue through 2026 (RAIN in Action, Madrid, September 29 - October 1, 2026) with Experience Lab live demos.
• Use-case impact on the tag side. Consumer smartphone reading shifts the design centre of consumer-facing tags. Tags need to support reliable handheld read at 1-15 cm distance from the phone antenna (versus the 1-15 m of fixed readers), which favours small-form-factor antennas tuned for near-field operation, and the URL-routing logic that NDEF on NFC tags uses today extends naturally to RAIN with appropriate URI encoding via GS1 Digital Link. Many consumer-facing programmes will deploy dual-technology tags (NFC + UHF) on the same product to serve both legacy NFC-only phones and the emerging RAIN-enabled population.
• Digital Product Passport synergy. RAIN-enabled phones combine with the EU Digital Product Passport to create the consumer-scan-to-passport flow that the regulation contemplates. The consumer points the phone at the tagged product, the phone reads the encoded EPC, the GS1 Digital Link resolver maps the EPC URI to the brand's DPP endpoint, and the phone displays the sustainability and lifecycle data. RAIN's acceptance as a qualified DPP data carrier (RAIN Alliance accepted as CEN/CENELEC JTC24 liaison) is the standards-body anchor that makes the workflow regulatorily defensible.
• Procurement implications. For brand-side programme owners, the RAIN-enabled-phone trajectory argues for DPP-readiness in 2025-2026 tagging decisions: encode tags with GS1 Digital Link-compatible identifiers, deploy GS1 Digital Link resolvers, and treat the consumer-scan use case as a 2027-2030 design constraint rather than a 2030+ optionality. For the tag-supplier portfolio, the trajectory argues for dual-technology (NFC + UHF) capability and for tag designs validated at smartphone-reader-distance ranges in addition to fixed-reader portal performance.

Participating in the RAIN ecosystem as a supplier — Proud Tek's position

'RAIN ecosystem participant' is a line anyone can print on a brochure; the version that counts is the one backed by certified SKUs, plug-fest mileage, and a test report a customer can actually read. Proud Tek participates in the RAIN RFID ecosystem as an inlay and label manufacturer, with certified-product SKUs across the major chip families and deployment-specific customization for retail, logistics, healthcare and industrial applications. The supplier-side perspective clarifies what credible RAIN ecosystem participation looks like and what customers should expect from a supplier partner.

• Multi-chip portfolio: Proud Tek's RAIN product family spans Impinj M700, M750, M800 on various inlay designs, NXP UCODE 9 and UCODE DNA on authentication-focused SKUs, and Alien Higgs family for value-engineered applications. The multi-chip position lets customers select the right chip for each application without switching suppliers.
• Application-specific tag design. Different deployment environments (apparel care labels, cardboard cases, metal assets, medical instruments, laundry tags) demand different antenna designs. The application-engineering function designs and validates antenna tuning against the specific substrate and mounting condition.
• Certification and conformance testing. Production SKUs are tested for EPC Gen2v2 conformance and interoperability with major reader infrastructure (Impinj, Zebra, Honeywell, Alien). Customers receive the certification evidence as part of standard product documentation.
• Factory encoding and serialization. Production lines support factory-level EPC encoding per customer GS1 Company Prefix and SGTIN/SSCC/GRAI structure, with serialization databases exchanged back to the customer for their enterprise traceability system. Encoding at factory scale is materially cheaper than post-receipt encoding for most high-volume applications.
• Quality-management compliance: ISO 9001 quality-management system covering inlay assembly, encoding, test and label conversion. The quality system is the foundation for the consistent read-performance that enterprise customers expect across multi-year contracts.
• Pilot and sample programme. Small-quantity sample kits and pilot-volume programmes let customer engineering teams validate performance before committing to production volume. The sample programme is the on-ramp for new applications and new customers.
• Collaboration with RAIN Alliance programmes. Participation in Alliance working groups, plug-fests and certification events keeps the product portfolio aligned with the ecosystem's direction and surfaces new application opportunities as verticals mature.

FAQ