News analysis · Business
EPC and TID identify different things. Traceability needs both decisions made explicitly
The item identifier and silicon identifier can coexist on a RAIN tag, but neither alone establishes product custody or authenticity.
What the sources establish
The GS1 EPC Tag Data Standard describes encodings for serialized item identifiers including SGTIN and covers tag identification memory-bank contents. These are separate parts of the specification. In its RAIN RFID technology explainer, chipmaker Impinj says endpoint ICs have a manufacturer-programmed tag identifier, TID, and a memory bank for an item tracking identifier, EPC. The company also describes passive tags powered by a reader’s radio signal. Its range and productivity figures are vendor claims and are not a basis for a universal business case.
The GS1 EPCIS 2.0 specification defines visibility events that add business context to identified objects. An EPC or TID in isolation is not an event history.
RFIDWire analysis
A TID may help distinguish a physical chip from another chip. An EPC is typically how the application identifies an item or asset. Which field matters depends on the question. Inventory software generally needs to know which item was counted; a provenance or anti-swap check may also need to know which tag it was associated with. Neither field automatically proves that the tag remains on the original item, or that a legitimate owner performed every step in a journey.
Design the association explicitly. At commissioning, record the item identifier, tag identity if used, time, place and responsible process. At handoff, specify which observation is sufficient to update custody. If two readers encounter the same identifier, preserve enough context to distinguish a duplicate observation from an actual movement. If a label is replaced, keep an auditable reason rather than quietly overwriting the relationship.
A serialized EPC can be encoded correctly but mapped to the wrong item in the enterprise system. Conversely, a genuine TID can be scanned on a tag that has been moved. Businesses should not purchase a field name as though it were a complete control. Test the end-to-end process: commission, pack, transfer, receive, dispute and retire. Ask whether an exception can be reconstructed after the fact, not only whether an antenna read was successful.
Questions and limits
Is the EPC serialized or a class-level identifier? Does the proposed TID implementation meet the required uniqueness and serialization rules? Who can change the EPC memory? What evidence binds the tag to the item? Which business events are required to substantiate a custody claim?
The standards explain representations and event models; Impinj explains its product architecture. They do not independently validate a specific deployment’s chain of custody or protection against tampering. The process design above is RFIDWire analysis, not a claimed field result.