In October 2025, GS1 released TDS 2.3, an update to the RFID Tag Data Standard that quietly rewrote the definition of an RFID tag. The tag is no longer just an identifier. It is now a web-resolvable address. Each tagged item has its own URL, which can phone home to a source-managed endpoint for authoritative real-time data. Most retail coverage missed it.
In several deployments across the United States and Latin America, we have seen retailers spend years building proprietary middleware to translate RFID reads into useful business data. As of late 2025, that middleware became optional. The tag itself now contains the address of the authoritative data source. That is not a feature update. Rather, it is the moment RAIN RFID became web-native.
RFID is no longer just an inventory-tracking technology. With TDS 2.3, every tagged item became its own API endpoint. The retailers who understand that shift will rebuild their supply chain. The ones who do not will keep paying for middleware that no longer needs to exist.
What TDS 2.3 Actually Does
The mechanics matter, so let me explain them in operational language rather than standards language.
Before TDS 2.3, an RFID tag stored an Electronic Product Code (EPC), which is a unique identifier that meant nothing without a separate lookup system to translate it into business data. Every retailer with an RFID deployment built or bought middleware to do that translation. The middleware connected the EPC to the supplier’s product catalog, the retailer’s inventory system, the loyalty platform, and, in some cases, the manufacturer’s authentication service. Each integration was custom. Each integration was brittle.
With TDS 2.3, the tag itself now carries a domain name alongside the EPC. When a reader scans the tag, it does not just return an identifier. Instead, it resolves directly to a web URI that points to a live, authoritative endpoint. As Jonathan Gregory, senior director of global standards at GS1 US, put it, a pallet of goods can now “phone home” to a source website or web service at any point in its journey.
The architectural implication is significant. The data layer between the physical item and the digital record collapses. There is no longer a translation step. The tag is the URL. The URL is the data source. And every party in the supply chain reads the same authoritative data without having to rely on proprietary integrations between them.
Why This Is a Bigger Shift Than the Walmart Mandate
I wrote earlier this year about the Walmart RFID mandate and what it means for suppliers. The mandate is about adoption at scale. TDS 2.3 is about something different. It is about what the technology becomes once everyone has it.
The Walmart mandate forced suppliers to source-tag their products. That solved the inventory visibility problem inside Walmart’s four walls. However, the data trapped inside each retailer’s middleware never flowed back upstream to suppliers, manufacturers, regulators, or customers in any standardized way. Each retailer’s RFID data was an island unto itself.
TDS 2.3 connects the islands. The same tag, scanned at Walmart, at a Target distribution center, at customs in Long Beach, or at a returns desk in Mexico City, resolves to the same authoritative URL. Specifically, that URL can return product information, authentication data, sustainability credentials, recall status, or any other information the data owner publishes. The tag becomes a portable digital identity for the product.
For retailers running closed RFID systems built between 2018 and 2024, this is uncomfortable. Those systems were never designed to interoperate. Therefore, the strategic question now is whether to keep paying middleware vendors for translation work that the standard now does for free.
The Adoption Layer: What Has to Change Operationally
This is the part standards bodies do not put on a slide. Adopting TDS 2.3 is not a tag procurement decision. It is an operating model change that affects IT architecture, supplier relationships, store operations, and data governance simultaneously.
Day 1: The IT Architecture Question
Most retailers with RFID deployed today are running an architecture that assumes the tag is a dumb identifier. The middleware does the work. With TDS 2.3, the architecture inverts. Furthermore, the tag is now the integration layer. As a result, the IT decision is whether to retrofit existing middleware to consume web-resolvable EPCs or to migrate to a stack that bypasses the middleware entirely. Both paths have costs. The wrong path locks the retailer into legacy infrastructure for another five years.
Day 30: The Supplier Conversation
The web-resolvable URL on the tag points somewhere. That somewhere is typically a supplier-managed endpoint, an industry consortium service, or a GS1-operated resolver. As a result, the supplier decides what data the tag exposes and to whom. For retailers used to controlling the entire data layer downstream of their distribution centers, this is a governance shift. The supplier is no longer just a manufacturer. Rather, the supplier is now a data operator for every product on the shelf.
Day 90: The False Success Mode
The most common failure pattern with TDS 2.3 in 2026 will be retailers ordering tags with the new encoding schemes, declaring the upgrade complete, and never updating their middleware or supplier agreements to actually use the web-resolvable layer. The tags will work. The legacy lookups will still run. Encoding is not architecture. Compliance is not capability. Tags are not data.
Therefore, the retailers who will extract real value from TDS 2.3 are the ones who treat the standard as an operating-model trigger, not a procurement update. The hardware did not change. What changed is what the hardware can do once the architecture above it changes, too.
Three Use Cases That Become Real in 2026
The TDS 2.3 capability has been technically possible since October 2025. The real question is which use cases retailers will operationalize in the next 18 months.
Anti-Counterfeiting and Cargo Theft Recovery
According to the RFID Journal coverage of the TDS 2.3 release, organized retail crime and cargo theft are the highest-impact early use cases. A web-resolvable tag scanned at a port, a warehouse, or a secondary marketplace can immediately confirm whether the item is authentic and whether it was reported stolen. For high-value categories such as apparel, electronics, and pharmaceuticals, this is a step change in recovery capability.
Digital Product Passport Compliance
The EU Digital Product Passport regulation is approaching enforcement for several categories starting in 2027. Specifically, every product sold in the EU will need a digital record of its materials, origin, and sustainability credentials. TDS 2.3 is the cleanest path to compliance because the tag itself becomes the access point to the passport. Retailers operating across the U.S., Latin America, and the EU will soon face this regulation. The tag architecture they choose now will determine whether they are compliant on day one or scrambling.
Returns, Authentication, and Resale Markets
Returns fraud and resale-market authentication are growing categories of loss for apparel and luxury retailers. A web-resolvable tag at the returns desk can confirm in real time whether the item is the one originally sold, whether it has been returned before, and whether it has been listed on a secondary marketplace. As a result, that capability used to require expensive proprietary systems. The standard now makes it native.
What This Means for LatAm Retailers
Latin American retailers are in a unique position with TDS 2.3. The region’s RFID adoption lags the U.S. by 2 to 3 years, which is typically a disadvantage. However, in this case, it is the opposite. Retailers who have not yet deployed legacy RFID middleware can skip an entire generation of architecture.
From the deployment side, I have walked stores in Mexico, Colombia, and Chile where ESL is deploying ahead of RFID, and where the RFID conversation is happening in parallel with the connected store conversation. For those retailers, TDS 2.3 means the architecture decision becomes simpler. The tag is web-resolvable from day one. Therefore, the middleware layer is thinner. The supplier conversation is different. The total cost over a five-year horizon is materially lower than in retailers that deployed RFID in 2020.
For LatAm grocers, apparel chains, and department stores, the strategic question is not “should we deploy RFID?” Rather, it is “given that we are deploying RFID anyway, should we anchor our architecture in TDS 2.3 from day one and skip the middleware era entirely?” The answer is almost always yes. Importantly, the conversation should take place at the CIO and CFO level, not at the procurement level.
Where to Start
The sequencing playbook for retail leaders evaluating TDS 2.3 over the next 12 to 18 months is concrete.
Next 30 Days: Audit Your RFID Architecture
First, identify every RFID middleware layer in your current stack. Document what each layer translates, what it costs annually, and which suppliers feed data into it. The size of that surface area is the size of the simplification opportunity. Retailers running mature RFID programs are often surprised by how much custom integration sits between the tag and the inventory system.
Two Quarters Out: Pilot a Web-Resolvable Category
Next, pilot TDS 2.3 in a single category where the value is concrete. Apparel and high-margin general merchandise are natural starting points because the supplier base is already RFID-mature and the use cases (anti-counterfeiting, returns authentication) are well-defined. Importantly, measure what the supplier-managed endpoint enables operationally, not just the tag itself.
The 18 Month Horizon: Rebuild the Data Governance Model
Finally, the bigger change is governance. When the tag is web-resolvable, the data owner is the entity that controls the endpoint. As a result, there is a different relationship between retailer, supplier, and customer than the one most retail organizations are structured around today. The retailers who think about this in 2026 will operate a different supply chain in 2028. The ones who treat TDS 2.3 as just another standards update will not.
In conclusion, the retailers who treat RFID as a tracking technology will keep paying for middleware. By contrast, retailers who treat it as an item-level web layer will compound their advantage year after year through cleaner integrations, faster compliance, and lower fraud.
The tag is no longer a barcode with a battery. It is a web address with a body. The retailers who understand that will own a supply chain that their competitors cannot copy.
If you are evaluating an RFID architecture for your retail network or planning a TDS 2.3 migration, connect with me here or reach me on LinkedIn. I am happy to walk through the deployment framework we use across the U.S. and Latin America.
Adriana Rivas is a retail technology executive and AI strategist, and the founder of a U.S.-based hardware company specializing in self-service kiosks, POS systems, electronic shelf labels, and digital signage deployed across the United States and Latin America. She is the award-winning author of How to Implement Self-Service Without Failing (Amazon #1 Hot New Release, Silver Nonfiction Book Award 2025) and recipient of the Gold Stevie® Award — Thought Leader of the Year 2026. She is also recognized by Thinkers360 as a Top 10 Thought Leader – Retail and a Certified Expert – Retail.