Which Barcode Type Should I Use? EAN-13, UPC-A, Code 128 & More

Quick barcode type comparison

Start with where the code will be scanned and what the receiving system expects. The table below is a practical first filter, not a replacement for retailer, standards-body or trading-partner requirements.

For retail products: start with the assigned GTIN

EAN-13 and UPC-A belong to the GS1 EAN/UPC family used at retail point-of-sale. GS1 describes UPC / GTIN-12 as most common in North America and EAN / GTIN-13 as most common in Europe and the rest of the world. GS1 also notes that EAN and UPC symbols are accepted globally, while individual retailers may still impose their own buying-guide requirements.

The key point is that the barcode image and the product identifier are not the same thing. A generator can render a number as bars, but it does not allocate the GTIN, establish ownership of the number or register the product with a retailer.

For a GTIN-12 / UPC workflow: use UPC-A when that is the required symbol

UPC-A carries a 12-digit GTIN-12 and remains strongly associated with North American retail workflows. Do not switch barcode types simply because another format looks more international. If a retailer, marketplace or trading partner gives you a specification, follow that specification.

If you already have the correct UPC value, BarcodeBatch can render UPC-A directly. It will not invent, pad or repair the retail identifier for you.

For internal inventory, SKUs and serial numbers: Code 128 is a strong default

When the barcode is for your own stockroom, bins, equipment, serial numbers or internal product codes, you usually do not need a retail EAN/UPC symbol. Code 128 is compact and flexible enough for letters, numbers and common symbols, which makes it a practical choice for many internal workflows.

Generic Code 128 and GS1-128 are not interchangeable terms. GS1-128 is a GS1-specific subset of Code 128 that uses FNC1 and GS1 Application Identifiers. If a logistics partner requests GS1-128, follow that specification rather than treating any Code 128 symbol as equivalent.

Use Code 39 when compatibility matters more than density

Code 39 remains common in older industrial, asset and internal systems. It is less data-dense than Code 128 and supports a more limited character set in its standard form, so it is usually chosen because an existing scanner, label specification or downstream application requires it.

If you control both the label and receiving software and do not have a legacy constraint, Code 128 is often the more flexible option. If the system documentation says Code 39, match the system instead of changing formats for convenience.

Five questions to answer before choosing a barcode

A correct choice usually becomes obvious once the scanning environment is defined. Answer these questions before printing a large batch.

• Will the code be scanned at a retail point-of-sale or only inside your own business?
• Has a GTIN already been assigned to the trade item?
• Does a retailer, marketplace, warehouse or customer specify the exact symbology?
• Do you need letters and symbols, or only a fixed-length numeric identifier?
• Will you generate one label or hundreds of rows from an Excel workbook?