RFID Tags, identifiers and the SGTIN-96 control plane

The most common item-level encoding for retail serialized RAIN RFID is SGTIN-96. It carries the GTIN-derived item identity and a serial number within a compact, 96-bit EPC. According to the GS1 EPC Tag Data Standard material reviewed for this research, SGTIN-96 contains six fields: header, filter value, partition, company prefix, item reference and serial number. The header is 8 bits and, in that document, has the binary value 00110000. The filter value is 3 bits and is not part of the pure SGTIN identifier; it enables rapid filtering and logistics-type preselection. The partition value is also 3 bits and indicates where the company-prefix and item-reference fields are divided. [2]

The partition is not an arbitrary internal setting; it defines how the GS1 company prefix and item reference are parsed. An incorrect partition can turn a syntactically valid EPC into the wrong product identity. The company-prefix field encodes the GS1 company prefix, while the item-reference field encodes the GTIN item reference together with its indicator. The serial number makes the instance unique within that item identity. Suppliers should not allow encoding software to generate SGTINs from free-form strings without validating the GTIN length, check digit, leading zeros, partition and serial range.

GS1 serialization authority is an operational control, not an IT afterthought. Allocate serials centrally, never permit two plants to draw from the same range, and record every issued serial with its GTIN, PO, production order, label batch, printer, operator, pack and ship status. On reshipment, retain the identity rather than encoding a new random EPC unless the retailer’s process explicitly allows it. For reusable totes and Assets, the appropriate GS1 identifier may differ from the item or case identity; an SGTIN should not be reused as a returnable-asset code.

A pallet or case is not simply a “bigger item.” SSCC provides a unique serial identifier for a logistics unit. It is a separate identity from the GTINs inside the unit. GS1 material describes SSCC as identifying a logistics unit built for transport, storage or distribution, and states that scanning the SSCC lets a system match a physical unit movement to its electronic business message. [8] The ASN then communicates the hierarchical relationship: pallet contains cases, case contains serialized items. If a reader sees the SSCC but the ASN lists different contents, the shipment is not compliant.

Kill and lock settings must follow a negotiated policy, not a default checkbox. Gen2 tags commonly expose access, kill and other controls that can affect whether memory can be written or whether the tag can be permanently deactivated. For retail source tagging, the retailer may require open encoding at the factory, locked encoding after commissioning, or a secure access configuration for later updates. A brand must document who holds credentials, whether user memory is used, whether the EPC can be rewritten, and when a tag may be killed. “Lock everything” is not automatically safer if a DC, packaway or returns process needs to update a field. Nor is leaving default access credentials acceptable when the retailer expects controlled encoding.

EPCIS is the mechanism for sharing the business context of those identities. ISO/IEC 19987:2024 defines EPCIS 2.0 and states its purpose is to let separate applications create and share visibility-event data within and across enterprises, giving users a shared view of physical or digital objects in a relevant business context. [10] It can carry events for commissioning, shipping, receiving, aggregation and transformation. Its value to vendor compliance is that a serialized read becomes auditable: who packed it, where, when, in which case and under which business step.