Guides
Barcode Format Selection Guide
Choose the right barcode standard before you generate artwork by matching your workflow, content constraints, scanner environment, and compatibility target.
Once you choose a format, use the Barcode Generator to validate checksums and export artwork.
Ranked formats
Complete the assessment to rank barcode formats for your workflow before you generate artwork.
Barcode format cheat sheet
Use this quick reference to understand where each format fits before you move into payload validation and barcode generation.
Code 128
Best for: Flexible internal IDs, logistics labels, and mixed-content tracking values.
Limit: Not the usual consumer retail checkout standard.
- Supports letters, numbers, and symbols.
- Good default for internal operations when retail compatibility is not required.
- Can become dense when long values are printed in a small space.
EAN-13
Best for: Global retail product labels when the item needs a standard consumer barcode.
Limit: Digits only and typically needs more space than EAN-8.
- Common international retail format.
- Works well when the consumer unit needs checkout compatibility beyond U.S. and Canada.
- Uses a checksum to validate the base digits.
EAN-8
Best for: Small retail packaging where label space is unusually constrained.
Limit: Only suitable when a short retail identifier is appropriate.
- Compact retail format for small items.
- Digits only with checksum validation.
- Best used when EAN-13 or UPC would be too wide for the label area.
UPC
Best for: Retail product labels that mainly target U.S. and Canada checkout systems.
Limit: Less universal than EAN-13 for international retail workflows.
- Standard consumer retail format in U.S. and Canada.
- Digits only with checksum validation.
- Strong choice when local checkout compatibility matters most.
ITF-14
Best for: Outer cartons and shipping packaging rather than the individual consumer item.
Limit: Not intended for the unit scanned at retail checkout.
- Packaging-friendly format for carton-level labeling.
- Digits only with checksum validation.
- Usually fits better on larger labels than compact consumer packaging.
MSI
Best for: Some numeric-only inventory systems and niche warehouse workflows.
Limit: Scanner and software support can be less universal than Code 128.
- Numeric-only format used in some inventory environments.
- Most useful when an existing system already expects MSI.
- Verify support before standardizing on it for new workflows.
How to use this guide
Treat the output as a standards-based shortlist, then confirm final trading-partner, scanner, or packaging requirements before production use.
How ranking and confidence work
The guide ranks formats based on your workflow, content constraints, scanner environment, and compatibility target. Confidence reflects how clearly your answers point toward one standard over the others.
- Higher score means better fit for your stated workflow, not a universal best barcode.
- Confidence is highest when your answers map cleanly to one standards-driven use case.
- Excluded formats are shown when they fail a hard requirement such as retail checkout or character support.
Retail, internal, and packaging barcodes solve different problems
The right standard depends less on preference and more on where the label must scan successfully and what data it needs to carry.
- Retail product labels usually need UPC, EAN-13, or EAN-8 rather than general-purpose formats.
- Internal labels often benefit from Code 128 because it supports letters, numbers, and symbols.
- Outer cartons usually need a packaging-friendly format rather than the same barcode used on the consumer unit.
Use the selector before you generate artwork
Choosing the correct standard first prevents avoidable scanner failures, checksum confusion, and rework in packaging or inventory systems.
- Pick the standard before adjusting bar width, height, margin, or text display.
- Validate whether your system expects retail compatibility, internal tracking flexibility, or carton-level labeling.
- Use the generator after selection to build valid payloads and test checksum behavior.
FAQ
Why does this guide sometimes exclude formats instead of just ranking them lower?
Some formats fail hard requirements. For example, retail checkout standards do not support letters and symbols the way Code 128 does, and ITF-14 is for outer packaging rather than the consumer unit.
Is Code 128 always the safest default?
No. It is flexible for internal workflows, but flexibility does not replace checkout compatibility. If the barcode must work at retail POS, standards like UPC or EAN are usually more appropriate.
When should I choose EAN-8 over EAN-13 or UPC?
Choose EAN-8 when you truly need a compact retail barcode because the label is very small. If space is not unusually limited, EAN-13 or UPC is often easier to support operationally.
Does this guide tell me which barcode my retailer requires?
No. It gives a standards-based recommendation based on your answers. Always confirm retailer, marketplace, scanner, or packaging requirements before production printing.
Why is MSI rarely the top recommendation?
MSI is more niche than Code 128 for modern internal workflows. It becomes more relevant when you have a numeric-only legacy inventory system that already supports it.
Should cartons use the same barcode as the item inside?
Not necessarily. The consumer unit and the outer carton often serve different scanning workflows. Carton labels commonly use a packaging-oriented standard instead of the unit retail barcode.
Does confidence mean the recommendation is guaranteed to work everywhere?
No. Confidence only reflects how clearly your answers align with common standards and workflow assumptions. Final compatibility still depends on your actual scanner, software, and trading-partner requirements.
Related tools: Barcode Generator and QR Code Generator for payload creation and export workflows.