LINKMINT PRACTICAL GUIDE

Code 128 Inventory Labels: A Practical Setup Guide

Code 128 can encode compact internal identifiers, but the label succeeds only when the value rules, printer, scanner and inventory system agree.

Published and reviewed 5 October 2026 · By the LinkMint Editorial Team · How we test and review

Code 128 is useful for internal inventory because it can encode numbers, letters and common punctuation. It is a barcode symbology, not an inventory database. Before printing labels, define what each value means and how the receiving software will use it.

Design the identifier first

A good internal value is unique, stable and short. Values such as SKU-10482, BIN-A-014 or ASSET-002731 are readable by people and scanners. Avoid putting changeable information such as price, stock count or employee name directly in the identifier. Store those details in the inventory system and use the barcode as the lookup key.

Write down rules for prefixes, length, allowed characters and leading zeros. Decide whether sku-15 and SKU-15 are different in your software. Once labels are distributed, changing the identifier format creates duplicate records and relabelling work.

Map the scan to a workflow

Label target	Example value	Expected action after scan
Product unit	SKU-10482	Open or add the matching stock item
Storage bin	BIN-A-014	Select a warehouse location
Reusable asset	ASSET-002731	Open maintenance or assignment history
Work order	WO-2026-1842	Open a job or production record

Prepare the label

Keep dark bars on a light, uniform background and preserve blank space at the left and right. Do not stretch the image to fit a box: horizontal distortion changes the bar widths that carry the data. SVG is suitable when the label editor handles vectors correctly; a sufficiently large PNG works in common office and label applications.

Human-readable text below the symbol lets staff type the value when a label is damaged. The printed text should match the encoded value exactly. Add a plain-language item name separately if operators need it, but keep surrounding graphics away from the barcode area.

Test the complete path

Create several realistic identifiers, including the longest allowed value.
Print them on the actual printer, label stock and quality setting.
Scan with every scanner model used at the site.
Verify the exact characters received by the application, including case and leading zeros.
Test a handled or lightly worn label.
Confirm that a duplicate scan produces the intended system response.

Code 128 versus retail EAN or UPC

Code 128 is flexible for internal operations. Retail channels commonly require assigned GTIN identifiers represented in EAN or UPC symbols. Generating Code 128 from a SKU does not create a retail product number. Follow the requirements of the marketplace, retailer or trading partner that receives the item.

Create a sample with the Barcode Generator, then compare other formats in the barcode format guide.

Reference: GS1 General Specifications for GS1 identification and barcode requirements. For an internal non-GS1 workflow, your scanner and inventory application specifications are the controlling requirements.