1. Start with external requirements
If a retailer, healthcare standard, customer specification or GS1 application requires a particular data carrier, that requirement outranks personal preference. Determine whether the identifier and data structure are prescribed before choosing a symbol.
2. Define the data
A simple internal asset number has different needs from a GTIN plus lot, expiration date and serial number. Numeric-only data may fit a specialized linear code; structured variable data often favors Code 128/GS1-128 or a 2D carrier.
3. Measure the available marking area
Linear symbols grow primarily in width as data increases. Matrix symbols can store more data in a compact square or rectangular area, but their module size must still be printable and readable.
4. Consider scanners and workflow
Existing laser scanners can strongly influence a legacy application. A new system using camera-based imagers has more 2D options. Consider reading distance, conveyor speed, mobile devices, direct-part marking and damaged-label conditions.
Common starting points
| Need | Symbologies to investigate |
|---|---|
| Retail POS trade item | UPC-A, UPC-E, EAN-13, EAN-8 as applicable |
| General internal alphanumeric ID | Code 128; Code 39 for compatible legacy systems |
| GS1 logistics / variable element strings | GS1-128 |
| Compact GS1 2D marking | GS1 DataMatrix or an applicable GS1 2D carrier |
| Consumer URL / mobile interaction | QR Code |
| High-capacity document use | PDF417 where the application specifies it |
Try the selection wizard
The interactive wizard asks a few application questions and points you toward symbologies worth investigating. It is an educational shortlist, not a substitute for an industry specification.