RFID standards help tags, readers and software work together. This guide explains EPC Gen2, ISO/IEC 18000-63, HF and NFC protocols, and the data standards that matter when choosing RFID products for a business project.
For buyers and system integrators, the key is to specify the complete system: radio protocol, identifier format, reader interface, operating region and performance on the actual item. A matching protocol is the starting point for compatibility; it does not guarantee a successful installation.
Use EPC Gen2 / ISO/IEC 18000-63 as the starting point for passive UHF projects. Check ISO/IEC 14443, ISO/IEC 15693 and the relevant NFC specifications for HF applications. Define encoding and software integration separately, then validate the finished tag in its intended environment.
RFID Standards at a Glance
Different standards solve different problems. An air-interface specification controls radio communication, while an identifier standard determines what the stored data means. Keeping these layers separate makes an RFID requirement easier to write and test.
| Layer | Main references | What to confirm |
|---|---|---|
| Tag-to-reader communication | EPC Gen2; ISO/IEC 18000-63 | Supported frequency band, mandatory commands and required optional features. |
| Tag identifiers and encoding | GS1 EPC Tag Data Standard (TDS) | Identifier scheme, bit length, serialization and memory content. |
| Reader-to-software interface | Low Level Reader Protocol (LLRP) | Reader configuration, access operations and tag reports. |
| Business event sharing | EPCIS and Core Business Vocabulary (CBV) | How identification events are described and exchanged. |
| HF and NFC | ISO/IEC 14443; ISO/IEC 15693; NFC Forum specifications | Exact card or tag technology, reader support and data format. |
| Animal identification | ISO 11784; ISO 11785 | Code structure, communication technology and applicable scheme requirements. |
| Radio operation | Applicable national radio rules and equipment requirements | Approved reader region, channels, power and required conformity evidence. |
Standards support interoperability and supplier flexibility, but antennas, chips, memory, materials and environmental durability still vary. Start with the required standard, then select the right physical product.
EPC Gen2 and ISO/IEC 18000-63
What does EPC Gen2 define?
The GS1 EPC Generation-2 standard defines communication between passive UHF tags and readers. It covers signaling, backscatter responses, inventory rounds, anti-collision behavior, sessions, memory access and protocol commands.
As checked on September 8, 2026, the GS1 Gen2 archive lists version 3.0.1 as current. State the version and optional features required by your project rather than assuming that a general “Gen2” claim includes every capability.
How is ISO/IEC 18000-63 related?
ISO/IEC 18000-63 specifies the Type C UHF air interface and is closely aligned with EPC Gen2. The names refer to related specifications rather than competing RFID technologies. Product sheets may also use the older ISO 18000-6C terminology; ask the supplier to confirm the implemented standard and edition.
ISO/IEC 18000-63 covers the 860–960 MHz range. That does not mean a reader may transmit across the entire range in every country. Local operating channels and equipment requirements must be checked separately.
What does protocol compliance leave open?
EPC Gen2 does not specify the finished label size, adhesive, face material, wash resistance or read distance on your item. For ordinary packaging, explore UHF RFID labels. For metal equipment, review flexible on-metal RFID tags and test the selected construction on the actual surface.
EPC Encoding and Tag Memory
The Electronic Product Code identifies an object or another entity. It is not the complete product record, the printed barcode image or necessarily the chip’s factory identifier. Business information usually remains in software and is retrieved using the identifier.
The EPC Tag Data Standard
The GS1 EPC Tag Data Standard defines EPC schemes and how data is represented in Gen2 tag memory. The GS1 TDS archive lists version 2.3.0 as current at the time of this review. Agree on the scheme, bit length and uniqueness rules before encoding production tags.
For example, a serialized trade item and a reusable asset may require different identifier schemes. A custom value written to EPC memory is not automatically a correctly encoded GS1 EPC. Confirm how the reader and software display and interpret the stored bits.
| Memory bank | Typical purpose | Buyer check |
|---|---|---|
| Reserved | Access and kill passwords, where implemented. | Password policy, supported security features and lock settings. |
| EPC | Application identifier and associated protocol-control data. | Required identifier length, encoding scheme and verification method. |
| TID | Manufacturer-assigned tag or chip identification data. | Whether the chip provides the serialized TID your application requires. |
| User | Optional application data. | Availability, capacity, access permissions and write endurance. |
Do not assume that all chips have user memory or a unique serialized TID. Validate the exact chip specification and verify both printed and encoded identifiers during production.
Reader Integration and Event Data
LLRP connects readers to software
Low Level Reader Protocol provides a standardized interface for configuring readers and receiving reports. It can cover antenna settings, inventory operations, filtering and tag access. Confirm the reader’s supported LLRP version and extensions against the client software; vendor-specific features may still require additional integration.
Compare fixed RFID readers for controlled read points with handheld RFID readers for mobile checks. A protocol-compatible reader still needs suitable antennas, installation settings and a tested software connection.
EPCIS and CBV describe business events
A tag read becomes useful when software knows what was observed, when and where it happened, and how it relates to a business process. EPCIS supports visibility-event sharing within and between organizations. CBV supplies consistent business vocabulary so trading partners can interpret those events.
In RFID warehouse management, receiving, put-away and dispatch are different events even when they involve the same tag. Define those events and their business context as part of the project, rather than treating raw reader reports as finished inventory transactions.
HF, NFC and Animal RFID Standards
ISO/IEC 14443: proximity cards
ISO/IEC 14443 covers proximity-card technologies used in many contactless credential systems. Specify the supported type, chip, authentication method and application software. RF compatibility alone does not make a credential suitable for a particular access or payment system.
See RFID contactless cards and the RFID office access control solution for related product and workflow options.
ISO/IEC 15693 and NFC specifications
ISO/IEC 15693-based HF technologies are used in library and item-identification projects. NFC Forum specifications define interoperable tag and device behavior, including how supported devices access NDEF messages. Check the exact NFC tag type and phone or reader support.
HF and NFC use 13.56 MHz, but sharing a frequency does not guarantee compatibility. Review HF/NFC RFID labels against the required protocol and data format. Library projects may also require a specific library data model or national profile.
ISO 11784 and ISO 11785: animal identification
ISO 11784 defines the animal identification code structure; ISO 11785 addresses the technical communication concept. For RFID animal tags, confirm the identification scheme, supported technology and reader compatibility, together with any registration or approval requirements applicable to the destination market.
Regional Requirements and Application Testing
An air-interface standard does not replace local radio requirements. Ask the equipment supplier or integrator to confirm the permitted channels, radiated power and required equipment conformity for the country of installation. Configure readers for that destination before commissioning.
| Check | What it establishes |
|---|---|
| Protocol conformance | The device implements the specified protocol behavior. |
| Interoperability | The selected readers and tags work together with the required functions. |
| Application performance | The finished tag meets the project criteria on the real item and in the real process. |
| Environmental durability | The tag and attachment survive the relevant temperature, cleaning, wear or exposure. |
A compliant tag can still fail because of metal, liquids, orientation, dense packing or adhesive failure. For example, IT asset tracking requires careful metal-surface selection, while industrial laundry tracking also requires a tag and attachment suited to the washing process.
Choose Standards Around the Application
Use the application to decide which standards and product features deserve attention. The following routes connect this guide to relevant GSRFID solutions and product ranges.
| Application | Key questions | Explore the solution |
|---|---|---|
| Retail and apparel | UHF protocol, unique item encoding, retailer requirements and tag placement. | RFID apparel tracking Apparel RFID tags |
| Warehouse and logistics | Reader coverage, serialized identifiers and software event mapping. | RFID warehouse management Inventory RFID tags |
| Metal equipment and IT assets | On-metal construction, mounting and application-specific read tests. | RFID IT asset tracking Anti-metal RFID tags |
| Access control | Card protocol, chip security and access-system compatibility. | RFID office access control Contactless cards |
| Laundry and textiles | Protocol, washing conditions, attachment and durability validation. | RFID industrial laundry RFID laundry tags |
| Medical equipment | Item material, cleaning conditions and equipment-specific performance. | RFID medical equipment tracking |
For other use cases, browse all RFID industry solutions, including manufacturing, education, animal and livestock, hospitality, aviation and energy applications.
RFID Standards Checklist for Your RFQ
A clear request for quotation reduces avoidable changes after sampling. Include the following information when asking for RFID labels, tags, cards or readers:
- Application and destination: the item, workflow, installation country and target operating environment.
- Frequency and protocol: the exact standard, required edition and optional features.
- Chip and memory: EPC capacity, user memory, TID requirements and write or lock behavior.
- Encoding: identifier scheme, serialization source, bit length and duplicate-prevention rules.
- Physical construction: size, material, mounting surface, adhesive or mechanical attachment.
- Reader and software: reader model, antennas, interfaces and any required LLRP support.
- Print and verification: barcode, QR code, visible serial number and agreement between printed and encoded data.
- Acceptance criteria: test setup, read reliability, environmental conditions and sampling plan.
Share your application, operating region, reader model, item material and encoding requirements. GSRFID can help narrow the label or tag options and prepare samples for evaluation.
Discuss Your RFID ProjectFrequently Asked Questions
Are EPC Gen2 and ISO/IEC 18000-63 the same?
They are closely aligned specifications for passive UHF Type C communication. EPC Gen2 is maintained by GS1, while ISO/IEC 18000-63 is the corresponding ISO/IEC standard. Confirm the edition and features implemented by the selected equipment.
Does every Gen2 reader read every Gen2 tag?
Core protocol compatibility is the starting point. Regional settings, optional commands, antenna performance, memory functions and reader implementation still need checking. Test the selected combination on the actual item.
Is EPC the same as TID?
No. EPC memory usually holds the item or application identifier, while TID memory contains manufacturer-assigned chip or tag identification data. Their purposes and uniqueness properties differ.
Can an NFC phone read a UHF RFID label?
A phone’s built-in NFC interface uses 13.56 MHz and does not directly read ordinary passive UHF labels. A compatible external UHF reader is required for that workflow.
Does standards compliance guarantee read distance?
No. Read performance depends on the finished tag, item material, reader power, antenna setup, orientation and surroundings. Define a repeatable application test instead of relying only on a quoted maximum distance.