SGTIN-96 EPC Encoder / Decoder

Translate an approved GTIN and numeric serial into the 24-character hexadecimal EPC used by an RFID encoder, or decode the read-back value for release QA.

ModeDecode mode uses the EPC hex field and ignores the source identity fields. GTIN-14Use the approved 14-digit GTIN including its check digit. GS1 Company Prefix digitsTake this licensed length from the data owner; it cannot be inferred safely from GTIN alone. Numeric serialSGTIN-96 permits 0–274,877,906,943 with no leading zeros. Filter valueFollow the customer's GS1/RFID capture policy; filter is not part of item identity. EPC hex for decodePaste exactly 24 hexadecimal characters from the physical tag read-back.

Enter the approved identity fields or a read-back EPC.

What this calculator solves

RFID printer software normally expects hexadecimal data, while the job ticket is built around a GTIN and serialized item identity. This tool exposes the GS1 partition and field values between those two forms. It also decodes the tag actually read after encoding, so production can compare the physical result with the approved source rather than trusting the outbound command.

How to choose the inputs

The GTIN must contain 14 digits with a correct check digit. Company Prefix length comes from the organization's GS1 licence; different lengths change the binary partition even when the visible GTIN stays the same. SGTIN-96 serials are numeric, contain no leading zero except the single value 0, and must fit the 38-bit range. Filter values support reader selection but do not make two otherwise identical EPCs unique.

How the calculation works

The 96 bits contain the SGTIN header 0x30, three filter bits, three partition bits, a company-prefix field, an item-reference field and a 38-bit serial. Company and item bit lengths follow the GS1 partition table. The output includes hexadecimal, EPC Tag URI and Pure Identity URI so the job ticket can retain both machine and human-auditable forms.

Worked production example

GTIN 00614141123452 with a seven-digit Company Prefix, filter 1 and serial 100000001 encodes as 3034257BF40C0E4005F5E101. Decoding that same 24-character read-back returns the original GTIN and serial. The operator should still scan the printed barcode and reconcile it with those decoded fields.

How to interpret the result

Copy the hexadecimal EPC into the approved printer/encoder template, encode one test tag, read it back, and run decode mode on the returned value. Freeze the verified vector with the artwork proof and serialization range. The Encoding Throughput Planner then turns measured pilot yield into production quantity and time.

Common production mistakes

Do not guess Company Prefix length from familiar barcode patterns, retain the GTIN check digit inside the item reference, add leading zeros to the serial, or treat a filter change as a new item identity. Never commission duplicate EPCs because a print file was restarted; serialization state must be controlled outside this calculator.

Production assumptions and limitations

This implementation covers legacy SGTIN-96 only. It does not generate SGTIN-198, newer EPC+ schemes, SSCC, access passwords, user memory, RF power or printer commands. It validates binary structure, not the ownership or authorization of the entered GS1 identifiers.

Related production workflow and source

Continue with the Encode Position Converter and Smart Label Production Guide. Encoding follows the GS1 EPC Tag Data Standard; compare critical vectors with the official GS1 EPC Encoder/Decoder. Last reviewed: 2026-09-02.