GS1 TDS 2.0 & Data Standards
EPC-96 Converter (Hex, Binary, Tag URI & Pure Identity)
4-Way bidirectional encoding tool with interactive bit-field breakdown for SGTIN-96, SSCC, and industrial RFID tags
GS1 TDS 2.0 & EPCglobal Multi-Format Decoder
EPC-96 Converter (Hex ↔ Binary ↔ Tag URI ↔ Pure Identity)
24 / 24 hex characters
Try Samples:
1. GS1 Tag URIHardware Level
urn:epc:tag:sgtin-96:3.0614141.024824.1
2. GS1 Pure Identity URIERP / WMS Level
urn:epc:id:sgtin:0614141.024824.1
3. Raw 96-Bit Binary StringAir-Interface RF Backscatter
00110000 01110100 00100101 01111011 11110100 00011000 00111110 00000000 00000000 00000000 00000000 00000001
Bit-Field Breakdown: SGTIN-96 (Serialized Global Trade Item Number)96 Bits Total
Header (8-bit):0x30
Filter (3-bit):3Reserved (3)
Company Prefix:0614141
Item Ref / Serial:024824 / 1
📐 Engineering Formulation & Open API
POST /api/v1/gs1/encode-sgtin GS1 SGTIN-96 Bit-Field Partition & Encoding Specification
Developer & Systems Context:
Programmatically generate thousands of verified EPC hex codes to batch-feed into Zebra ZT411 or Sato CL4NX RFID label printers.
Governing Formula
EPC_96_Bits = Header[8] + Filter[3] + Partition[3] + CompanyPrefix[20..40] + ItemRef[24..4] + Serial[38]
Encodes 96-bit contiguous bitstreams conforming to GS1 Tag Data Standard (TDS 2.0) with modulo-10 check digit recalculation.
cURL / Request Schema JSON
{
"gtin": "08901234567897",
"serialNumber": "10048291",
"filterValue": 3,
"partition": 5
} Response Data HTTP 200 OK
{
"epcHex": "3074257BF4000B4000994FBB",
"tagUri": "urn:epc:tag:sgtin-96:3.8901234.56789.10048291",
"pureIdentityUri": "urn:epc:id:sgtin:8901234.56789.10048291",
"status": "VALID_GS1_EPC"
}GS1 EPCglobal Tag Data Standard (TDS) Architecture
The 96-bit Electronic Product Code (EPC-96) is the international standard governing serialized item-level supply chain identification. By establishing deterministic partition tables and company prefix bit lengths, GS1 TDS eliminates identity collisions across global manufacturing, logistics, and retail ecosystems.
SGTIN-96 Bit Allocation Structure
| Bit Range | Field Name | Bit Length | Description / Example |
|---|---|---|---|
| 0 – 7 | Header | 8 bits | `00110000` (0x30) identifies SGTIN-96 scheme |
| 8 – 10 | Filter Value | 3 bits | Packaging level: 1 = Item, 2 = Case, 5 = Pallet |
| 11 – 13 | Partition Table | 3 bits | Specifies bit split between Company Prefix and Item Ref |
| 14 – (14+M-1) | Company Prefix | 20 to 40 bits | GS1 assigned company prefix (e.g., 0614141) |
| (14+M) – 57 | Item Reference | 24 to 4 bits | SKU indicator and item reference number |
| 58 – 95 | Serial Number | 38 bits | Unique integer serial (0 up to 274,877,906,943) |
GS1 TDS SGTIN-96 Partition Table Reference
| Partition Value | Company Prefix Bits | Company Prefix Digits | Item Reference Bits | Item Reference Digits |
|---|---|---|---|---|
| 0 | 40 bits | 12 digits | 4 bits | 1 digit |
| 1 | 37 bits | 11 digits | 7 bits | 2 digits |
| 2 | 34 bits | 10 digits | 10 bits | 3 digits |
| 3 | 30 bits | 9 digits | 14 bits | 4 digits |
| 4 | 27 bits | 8 digits | 17 bits | 5 digits |
| 5 | 24 bits | 7 digits | 20 bits | 6 digits |
| 6 | 20 bits | 6 digits | 24 bits | 7 digits |
Frequently Asked Questions
What is the exact bit-level structure of an SGTIN-96 Electronic Product Code?
An SGTIN-96 identifier consists of 96 contiguous bits: (1) 8-bit Header (0x30 for SGTIN-96), (2) 3-bit Filter Value (defining packaging level: item, case, pallet), (3) 3-bit Partition Value (defining company prefix vs item reference bit split), (4) Variable-length Company Prefix (20–40 bits, 6–12 decimal digits), (5) Variable-length Item Reference (24–4 bits, 7–1 decimal digits including indicator digit), and (6) 38-bit Serial Number (supporting numeric serials up to 274,877,906,943).
What is the difference between a Tag URI and a Pure Identity URI?
A Tag URI (e.g., urn:epc:tag:sgtin-96:3.0614141.812345.1001) encodes the physical RFID tag representation, including the specific TDS encoding scheme (sgtin-96) and the filter value (3 = case level). A Pure Identity URI (e.g., urn:epc:id:sgtin:0614141.812345.1001) represents the canonical logical business asset without any hardware-level encoding or filter artifacts, used within ERP and EPCIS event repositories.
How do partition values allocate bits between Company Prefix and Item Reference?
GS1 TDS defines 7 standard partition values (0 through 6). For instance, Partition 5 allocates 24 bits (7 decimal digits) to the Company Prefix and 20 bits (6 decimal digits) to the Item Reference. Partition 2 allocates 34 bits (10 digits) to Company Prefix and 10 bits (3 digits) to Item Reference, ensuring 44 bits total for prefix + item ref.
What are the valid GS1 EPC-96 Filter Values?
Standard SGTIN filter values defined by GS1 TDS 2.0 include: 0 (All Others), 1 (Point of Sale / Retail Consumer Unit), 2 (Full Case for Transport), 3 (Reserved / Inner Pack), 4 (Outer Shipping Case), 5 (Pallet / Unit Load), 6 (Component / Assembly part), and 7 (Reserved).
Can any 24-character hex string be converted into SGTIN-96?
No. Only 24-character (96-bit) hex strings beginning with standard GS1 binary headers can be partitioned into SGTIN (0x30), SSCC-96 (0x31), SGLN-96 (0x32), or GRAI-96 (0x33). Custom or proprietary 96-bit identifiers (e.g., raw numeric sequential barcodes) do not have valid GS1 company prefix allocations.
How is the GS1 Check Digit handled during EPC-96 encoding?
The standard 1-digit Modulo-10 check digit at the end of a GTIN-12, GTIN-13, or GTIN-14 barcode is not encoded into the EPC binary stream. Because the EPC bitstream is an exact mathematical representation, the check digit is redundant and is recalculated algorithmically when reconstructing the GTIN string from an EPC.
What happens if a serial number exceeds 38 bits?
The 38-bit binary serial field in SGTIN-96 can represent decimal serial numbers from 0 to 2^38 - 1 (274,877,906,943). If alphanumeric serial numbers (e.g. "SN-A94-F12") or values exceeding 274 billion are required, you must migrate to SGTIN-198, which stores alphanumeric serials up to 20 characters in 7-bit ASCII format.
How does this converter relate to RFID tag encoding software?
Our converter outputs the exact 24-hex EPC payload required by industrial RFID printer-encoders (e.g., Zebra ZT411, Sato CL4NX, Honeywell PM43) and fixed reader write commands (e.g., Impinj Octane SDK, LLRP
ClientRequestOp).