Identify the barcode symbology
Specify UPC-A or the actual required symbol rather than asking for a generic barcode-looking font. Keep the identifier data and the output artwork as separate parts of the project. A resource designed for Code 39 is not automatically interchangeable with a UPC workflow.
Understand the readable numbers
GS1’s General Specifications describe human-readable digits below the main EAN/UPC symbol. They recommend OCR-B as a convenient standard typeface but allow reasonable alternatives where clearly legible. The guidance explicitly distinguishes those visible characters from machine reading of the barcode itself.
Preserve the required digit information
The same GS1 section states that all encoded digits for UPC-A, EAN-13 and EAN-8 are shown in human-readable form, with particular treatment for UPC-E. Use the relevant symbology’s actual instructions rather than shortening or rearranging the digits to suit a decorative label.
Keep the production handoff explicit
Record the identifier, symbology, output dimensions and source workflow alongside the chosen number appearance. Keep any separate display typography outside the barcode’s required layout. The Excel barcode guide explains a Code 39 example for contrast; its asterisk recipe is not a UPC encoder.
Your questions, answered.
Does selecting OCR-B create a UPC barcode?
No. GS1 discusses OCR-B for the human-readable digits; encoding the bars is a different task.
Can I reuse a Code 39 asterisk formula for UPC?
No. Those symbologies have different encoding requirements.
Sources & background
Sources supporting this page’s explanations. Practical examples are our editorial suggestions.