EPC Gen2 describes how a UHF RFID reader and tag communicate. It does not, by itself, specify the meaning of every identifier, the business event created by a read, or all the features a particular product supports. Those distinctions explain many apparently puzzling compatibility failures.
A useful buying or integration question is therefore more specific than “Does it support RFID?” Ask which radio protocol, which identifier encoding, which reader interface and which application workflow are supported together.
Gen2, a revision of Gen2, and RAIN
The current GS1 EPC Generation-2 UHF air-interface standard, checked September 5, 2026, is release 3.0.1, ratified February 2026. Gen2 remains the name of the protocol family. “Version 3.0.1 of Gen2” is not a claim that the product uses a separate technology called Gen3.
The RAIN Alliance’s standards explanation relates RAIN to ISO/IEC 18000-63, also known as GS1 UHF Gen2, together with controlled tag numbering. RAIN is not a competing phone-tap protocol. Ordinary NFC support and RAIN support should be listed separately when comparing devices.
A specification’s publication date does not establish what an installed reader and tag implement. Gen2 includes mandatory and optional commands; vendor extensions can add further requirements. Ask for the exact firmware and tag-chip support statement for any feature that matters to your application.
Four layers answer four different questions
On a small screen, scroll the table sideways to read all columns.
| Layer | Question it answers | What it does not establish |
|---|---|---|
| Reader–tag air interface | Can this reader communicate with this tag using the required radio protocol? | Whether your inventory application recognizes the identifier. |
| Identifier and tag-data encoding | What identity does this bit pattern represent? | Whether the item was received, sold or returned. |
| Reader-to-software interface | How does client software configure the reader and receive observations? | The complete business meaning of each observation. |
| Business-event exchange | How are events shared with agreed context? | That every physical item was read correctly. |
GS1’s System Architecture places identifiers, data carriers and information exchange in a larger system. This separation is practical: you can investigate a radio problem without changing your product-numbering policy, and investigate an event-mapping problem without assuming the antenna needs replacement.
The Low Level Reader Protocol addresses communication between a reader and client software. Other products use vendor APIs or SDKs. Confirm the actual interface offered by your device and what metadata it exposes; a familiar radio-standard name does not select a software interface for you.
EPCIS supports sharing visibility events with business context. A raw observation needs interpretation before it becomes a useful receiving or shipping event. Your application must determine the appropriate read point, event time, business step and treatment of duplicates and exceptions.
An EPC is not simply “whatever number the reader shows”
The GS1 EPC Tag Data Standard defines EPC representations and encoding rules. For example, SGTIN identifies a serialized trade item; its encoding is more structured than copying a printed product number into arbitrary tag memory. Scheme, field lengths and serial-number constraints matter.
A product type and an individual instance are different identities. Two identical shirts can share a product identifier while requiring separate instance identifiers for an item count. If both tags carry the same supposedly unique identity, a system that counts unique values can merge them. More repeated reads will not resolve that numbering error.
Reader tools may display hexadecimal data, a decoded identity or other tag information. Preserve which representation you are recording. Leading zeros, case handling, field boundaries and serial formats can matter when transferring data between systems. Do not “clean up” a value in a spreadsheet until you know which representation it is.
For production encoding, use the applicable numbering authority and current specification, and validate with an independent decoder or verification tool. Test round trips between the original business identity, encoded tag data and decoded result. A readable tag is not necessarily a correctly encoded tag.
Check optional capabilities and regional operation
The RAIN Alliance’s tag description notes that chips differ in options such as security, user memory and battery assistance. Buy the feature you can demonstrate on the exact tag/reader combination. A security-related term on a product page is not evidence that authentication is enabled throughout your application.
A globally marketed reader also needs an appropriate regional model or configuration. Permitted bands and operating conditions are jurisdiction-specific. Use manufacturer approvals and current regulator information for the place of operation; the RAIN Alliance’s radio-regulations resources can help identify the relevant regional questions. Do not copy a frequency or power setting from a foreign installation.
Separate this approval check from a performance test. Approved equipment may still perform poorly with your packaging or layout. Conversely, a successful bench read does not establish that the chosen configuration is authorized for the deployment location.
A fictional failure that is not a radio failure
A different failure may occur one layer later: three distinct values reach the software, but its decoder expects a different scheme and rejects them. Retain the raw value, decoder error and declared encoding when troubleshooting. Avoid guessing a replacement identifier or quietly discarding the rejected records.
The Gen2 compatibility record provides fields for the tag, reader, firmware, region, encoding, software interface and tested capabilities. Pair it with the measured read-test guide so compatibility and physical performance are both checked before rollout.
Related resources
- Choose an RFID reader for the job
- Understand NFC and phone taps
- Review identifier and record privacy
- Explore all RFID resources
Researched and updated September 5, 2026. Check the linked official sources for specifications and policies that apply to your equipment and application.