# What goes in the EPC

> A UHF tag answers with 96 bits. Take one apart field by field, and see why the length of your company prefix is the number to get right.

- **Page** - https://iotready.com/insights/what-goes-in-the-epc
- **Author** - Tej Pochiraju
- **Published** - 2026-11-06
- **Topics** - Technology, Inventory Management

Here's what a reader shows you for one tag:

`3066C4409047E140075BCD15`

Twenty-four hex characters. That's the tag's whole answer, 96 bits, and on its own it's a number. Is it a carton? A pallet? A drill? Whose?

Inside your own building you can write anything into it. An asset number, a row from a spreadsheet, the date. Plenty of factories run that way for years and nothing breaks.

Then a pallet goes to a customer, and their reader has to make sense of your bits.

Film: [What goes in the 96 bits of an RFID tag, in 90 seconds](/media/rfid-10-what-goes-in-the-epc.mp4)

_A tag says a 96-bit number. GS1's Tag Data Standard lays those bits out like a form: which scheme, what kind of thing, whose company, which product, which one._

## The form

GS1's EPC Tag Data Standard exists for that moment. It says what each bit means, so anybody's reader can turn your hex back into the same barcode number you already use. For a single trade item the scheme is called SGTIN-96, and the 96 bits are cut up like this:

- 8 bits of header. `30` in hex means SGTIN-96. `31` means SSCC-96, a pallet or shipping case. Other headers name returnable assets, individual assets, locations and a few more.
- 3 bits of filter. What kind of thing the tag is on: `1` is a point-of-sale item, `2` a full case, `6` a unit load. A reader at a dock door can use it to skip the cartons and count the pallets.
- 3 bits of partition. More on this one below.
- 44 bits shared between your company prefix and the product.
- 38 bits of serial.

Take the tag above. The header is `30`, so it's an SGTIN-96. The filter is 3, which the standard holds in reserve, so a real tag wouldn't use it. The company prefix is 95060001343, the item reference is 05, and the serial is 123456789. Put the check digit back and you have the GTIN 09506000134352 with serial 123456789. That's one of the standard's own worked examples, and the [encoder](https://iotready.com/tools/epc-encoder) gives the same answer.

The check digit isn't stored. It's worked out again on the way back.

## The partition is the trap

Your company prefix, the number GS1 licenses to you, runs from 6 to 12 digits.

Those digits and the item reference share 44 bits. The longer your prefix, the fewer bits the product gets. A 12-digit prefix leaves 4 bits for the item, which is one digit. A 6-digit prefix leaves 24, which is seven.

The partition says where the split falls. Nothing else in the 96 bits does. Take `0614141` followed by `12345`. It could be a 7-digit prefix and a 5-digit item, or a 6-digit prefix and a 6-digit item.

So whoever sets up the printer has to type your prefix length, and it's on your GS1 licence. Get it wrong and the hex still decodes. It decodes to a different, perfectly valid-looking GTIN. That's the worst kind of wrong, because nothing complains.

## The serial

38 bits is 274,877,906,944 values, so you can number every one of a product from 0 to 274,877,906,943. A serial in this scheme is a whole number and can't start with a zero, because leading zeros are lost in binary. If your serials are `00417`, or have letters in them, you want SGTIN-198 instead. That's 198 bits and a longer tag memory.

And it's one number per item. The barcode on the carton says what the product is. The EPC says which carton.

## Two numbers on one chip

There's a second number on the chip that you didn't choose. The TID is written at the factory and the chip maker locks it. It says what silicon this is, and on most chips it carries a serial of its own. The EPC is yours.

You can't use the TID instead of an EPC, because it knows nothing about your product. And you shouldn't trust the EPC alone to prove a tag is genuine, because anyone can write one.

The EPC is written when the label is printed. The printer's encoding profile holds your prefix length, the filter and the scheme. Nobody types a hex string at the dock. So one wrong setting in a profile gives you a roll of labels, every one of them wrong, every one of them a plausible number.

## What the tool does

[The EPC encoder](https://iotready.com/tools/epc-encoder) goes both ways. Paste the 24 characters a reader shows and it splits them into the fields, with the GTIN or SSCC, the pure identity URI and the tag URI. Or type a GTIN and a serial and get the hex a printer should write.

It takes SGTIN-96 and SSCC-96 apart in full. The other 96-bit schemes it names from the header and stops. It doesn't talk to a tag.

I checked it against release 2.3 of the standard (October 2025): the header values, the SGTIN and SSCC partition tables, the filter values, and the worked examples in appendix E.3. Table numbers move between releases, so check the one you're building to.

If your hex doesn't decode, that's useful too. A header outside the GS1 range often means someone wrote their own number into the tag, and it was never meant for anyone else's reader.

For where EPC sits in a wider traceability setup, see [RFID manufacturer? You really should know about GS1 / EPC standards](https://iotready.com/insights/rfid-stds.md).

Look up your prefix length before you print the first roll.
