will failBC-05barcode

GS1-128 barcode rejected for wrong bar width

The bar width is outside the GS1-128 range (0.495 mm to 0.940 mm, 0.495 mm target). At 203 dpi that means ^BY 4 or greater.

Raise ^BY to at least 4 at 203 dpi, or 6 at 300 dpi.

A label that trips it
^XA^BY2^FO50,50^BCN,254,Y,N,N,D^FD>;>8010001234567890^FS^XZ
What the check looks for

Profile is GS1 and the X-dimension implied by ^BY falls outside 0.495 mm – 0.940 mm.

What Labelproof says about it3 findings · BC-05 highlighted
will failLY-02^XA · offset 0 · label 1

Neither ^PW nor ^LL is set. Both fall back to a value stored in the individual printer, not to a value in the spec — so the same ZPL prints differently on two printers of the same model.

Set ^PW and ^LL explicitly in every format.

the rule on this page
will failBC-05^BY · offset 7 · label 1

The bar width is outside the GS1-128 range (0.495 mm to 0.940 mm, 0.495 mm target). At 203 dpi that means ^BY 4 or greater.

Raise ^BY to at least 4 at 203 dpi, or 6 at 300 dpi.

At 203 dpi ^BY2 — the power-up default — and ^BY3 both fail GS1.

will failFLD-C128C-ODD-001^BC · offset 7 · label 1

Subset C encodes digits in pairs. This payload has an odd number of digits, so the last one is dropped — the barcode prints, scans cleanly, and returns one digit short of the data underneath it.

Pad to an even digit count, switch to Subset B (>:), or let ZPL auto-select the subset.

Cloud Retailer help desk, "Zebra Label Missing Last Digit and/or Not Scanning All Digits in Barcode": odd-length codes such as EAN-13 lose the final digit — "subset C cannot process single digits, it MUST be in a pair." A customer-reported production failure, documented by a vendor.

Why this matters

At 203 dpi ^BY2 — the power-up default — and ^BY3 both fail GS1.

Check your own label

No signup, and we do not store your labels.

Open the linter