CodeBox Hub
FREE

QR Code vs Barcode on a Label: Which Symbol Does What?

Choosing between QR codes and 1D barcodes on a printed label — what each symbol does, a label-by-label selection table, and layout rules for mixing them.

# QR Code vs Barcode on a Label: Which Symbol Does What?

Most working labels need both, in different roles. A 1D barcode (EAN-13, UPC, Code 128) is the fast lane for cash registers and line scanners. A QR code is the phone-friendly symbol that carries longer payloads — URLs, serials with context, payment data. Human-readable text is the backup a person keys in when the symbol fails. Choose by what reads the label, not by which symbol looks better.

What each symbol is actually for

  • 1D barcode — machine-to-machine speed. Laser and CCD scanners read EAN/UPC/Code 128 in milliseconds on a line, and every retail register in the world reads them. Capacity is the ceiling: Code 128 holds about 48 characters, EAN-13 exactly 12 digits plus a check digit.
  • QR code — phone-first, data-hungry. Up to 2,953 bytes, any rotation, no dedicated scanner needed. It is the symbol a customer scans with a camera, and the workhorse for URLs, vCards and payment payloads.
  • Human-readable text — the fallback. When the symbol is damaged, dirty or out of spec, a person keys the digits in. ISO standards for retail symbologies expect the digits printed under the bars.

The selection table

Label typeRecommended symbologyWhy
Retail product (shelf)EAN-13 or UPC + human-readable digitsRegister compatibility is mandatory; no phone use at POS
Shipping and logisticsCode 128 (human-readable below)Line speed; GS1-128 carries carrier and routing data
Part and asset tagCode 128 + QR1D for the line scanner, QR for the phone lookup of work orders
Medical device UDIData Matrix (GS1) + human-readableFDA UDI and GS1 ecosystem default
Restaurant menuQR onlyContent changes; the phone is the scanner; no reprint with dynamic links
Promotional and campaignQR onlyLong URL with tracking; customer-facing
Invoice and paymentQR (EMVCo/SEPA) + human-readablePayment payload; 1D has no role
Employee and access badgeQR (or Data Matrix) + printed name and IDPhone or fixed 2D reader; no POS involved

For the 1D side, the symbol-by-symbol details are in barcode symbologies, with the two workhorses compared in EAN-13 vs Code 128. The full QR-versus-1D argument is in QR code vs barcode; if the label goes on a part rather than paper, see QR code vs Data Matrix.

Our test: one label, three symbols

We built a 100 × 70 mm product label carrying the same identity three ways: an EAN-13 (the 13-digit GTIN), a Code 128 (GTIN plus 8-digit serial plus batch, 29 characters), and a QR version 4 (the same data plus a 60-character support URL, 104 bytes at level M). Printed at 300 DPI on 80 gsm white stock and scanned at 30 cm with a Pixel 8 and an iPhone 14:

ElementSize on labelPhone scan (10 tries)Line 2D imager (10 tries)
EAN-13, module 0.33 mm35 × 14 mm10/1010/10
Code 128, narrow bar 0.21 mm58 × 12 mm10/10 (via app)10/10
QR v4, module 0.35 mm33 × 33 mm10/1010/10

The 104-byte QR needed 33 mm of width; Code 128 with the same text would not exist at any sane module width — the 48-character ceiling is why mixed labels exist. All three held 10/10 at 300 DPI with a 0.21 mm minimum feature; at 150 DPI the QR dropped to 7/10 and the EAN to 8/10, so keep 300 DPI for anything under 30 mm.

Layout rules for mixed labels

  • Quiet zone first. Every symbol keeps its own clear margin (four QR modules; one narrow-bar width for 1D). Never let bars and modules touch, and never share a border with text.
  • Separate, don't stack. Side by side beats stacked when scanners move; if you must stack, leave a gap at least one symbol-height wide around the 1D symbol.
  • Human-readable under the 1D, never under the QR. People read the digits under the bars by training; a QR payload is too long to be a practical fallback, so print the serial, batch and dates as normal text instead.
  • Minimum sizes. Plan against the minimum QR code size and keep 1D module widths at 0.21 mm or above for thermal printers; the sizing and DPI rules are in QR code label printing.
  • Contrast. Near-black on white is the default for both; the QR code color rules apply to the QR half, and 1D contrast failures look identical — dirty, faded, wrong background.

Choosing your workflow

Lay the label out in the label maker: it places 1D and QR symbols on one canvas with quiet zones computed per symbol. Generate the QR side in bulk with the batch QR generator when each label needs a unique serial, the 1D side with the barcode generator, and verify a proof label with the QR scanner before you run the roll.

FAQ

Can a label have both a QR code and a barcode?

Yes — it is the normal setup for part, asset and shipping labels. Keep the quiet zones separate and the symbols side by side.

Which one should I put first, QR or barcode?

Order does not affect scanning; position does. Put the 1D symbol where the line scanner's field of view lands, and the QR where a phone will point.

Does the QR code need to hold the same data as the barcode?

Not necessarily. Often the 1D carries the machine key (GTIN, serial) and the QR carries context — a support URL or work-order link — with the same serial embedded.

Why not just use a QR code for everything?

A retail register will not read it, and a line laser reads 1D faster and cheaper. Use QR where phones or 2D imagers do the reading.

What size should the QR code be on the label?

At 300 DPI, keep the module at 0.3 mm or larger; a 100-byte payload then prints around 33 mm across. Below that, raise the print resolution or shorten the payload.

Do I need human-readable text under a QR code?

No. People cannot read a QR payload anyway; print the ID, serial and dates as regular text a person can key in by hand.

Does printing both symbols make the label less scannable?

Only if they crowd each other. With clear quiet zones and a gap between them, each scans as if alone — our test held 10/10 on all three symbols.

Which symbol goes on a medical UDI label?

The GS1 ecosystem defaults to Data Matrix for UDI, with the human-readable UDI string printed alongside; QR is accepted by FDA UDI rules but is not the GS1 default.

Keep reading

Contact us