Use GS1-128 when the barcode must carry structured supply-chain data such as GTIN, lot, expiration date, quantity, or SSCC.
(01)09521234543213(10)ABC123AI (01) identifies the GTIN; AI (10) identifies a batch or lot value.
(00)000123456789012345AI (00) is commonly used for Serial Shipping Container Code data.
This generator does not issue GS1 prefixes, GTINs, SSCCs, or official identifiers. Use GS1 or your trading-partner process to obtain and validate those values.
Enter GS1-128 data with the required Application Identifiers, preview the barcode, then download it as PNG or SVG. For multiple supply-chain labels, paste one GS1-128 value per line or import CSV rows and export the batch as a ZIP file. This GS1-128 barcode generator is intended for structured logistics, carton, pallet, healthcare, food, and inventory labels that need more than a plain Code 128 value.
GS1-128 is a GS1 application standard built on the Code 128 barcode symbology. Unlike plain Code 128, GS1-128 uses FNC1 and GS1 Application Identifiers to define what each data element means. For example, an AI can indicate GTIN, batch or lot number, expiration date, count, weight, or SSCC. The barcode is not just a string; it carries structured supply-chain data.
GS1 Application Identifiers, often called AIs, are numeric prefixes that define the meaning and format of the data that follows. Common examples include (01) for GTIN, (10) for batch or lot number, (17) for expiration date, and (00) for SSCC. In human-readable text the AI is often shown in parentheses, but the barcode itself uses the GS1 data format and FNC1 handling.
No. This GS1-128 barcode generator creates barcode images from the data you enter; it does not issue, sell, register, or verify official GS1 company prefixes, GTINs, SSCCs, or other identifiers. If your label will be used with trading partners, retailers, distributors, or regulated workflows, obtain and validate the identifiers through the proper GS1 process before generating PNG, SVG, or ZIP files.
Parentheses are normally used in human-readable GS1 text to make Application Identifiers easier for people to read. They are not encoded as ordinary data characters in the same way as product text. Many generators accept parenthesized input such as (01)09521234543213(10)ABC123 and translate it into the proper GS1-128 structure. Always confirm the scanner output expected by your receiving system.
FNC1 is a function character used at the start of a GS1-128 barcode to signal that the symbol follows GS1 rules. It is also used as a separator after variable-length data fields when another Application Identifier follows. Users normally do not type FNC1 as visible text; the barcode generator or label software must handle it correctly based on the GS1 data string.
Use GS1-128 when the barcode must communicate structured supply-chain data such as GTIN, lot number, expiration date, quantity, weight, or SSCC. Use plain Code 128 when the barcode only needs to return an internal ID, order number, asset tag, or other unstructured value. GS1-128 is stricter, but that structure is what lets trading partners and software parse the barcode consistently.
Yes. Paste one GS1-128 value per line or import CSV data to create multiple GS1-128 barcode images in one batch. This is useful for carton labels, pallet labels, batch labels, healthcare labels, food distribution, and logistics preparation. Before exporting a ZIP file, review the previews and verify that each row uses the correct Application Identifiers, fixed-length fields, variable-length separators, and check digits where required.
Use SVG when the GS1-128 barcode will be placed into label software, carton artwork, pallet labels, or print workflows where scaling matters. Use PNG for previews and internal documentation. If you generate many GS1-128 barcodes from CSV, export a ZIP file so the label images can be reviewed together before printing or sharing with a trading partner.
Some scanners output symbology identifiers, group separators, or configured prefixes when reading GS1-128. This can look like extra characters even when the barcode is correct. Check the scanner profile, AIM ID settings, and receiving software parser. If variable-length Application Identifier data is involved, also verify that FNC1 separators are present where the GS1 data string requires them.