Verify store shelf and product labels on screen, before they fail to scan at the checkout.
In retail a label error shows up directly at the checkout: the barcode does not scan, the queue waits, the cashier types the code by hand. On shelf labels, a price or product name that does not fit the template turns the label into a pointer to the wrong product. All of it is copied from a single template onto hundreds of labels, and once they are distributed to the store, fixing them means collecting them by hand.
EAN-13 and UPC-A barcodes are drawn exactly as produced; a narrow module or a clipped quiet zone is caught before the label leaves for the store.
A long product name and a many-digit price overflow the template. Preview with your longest product name and find the field limit on screen, not on the shelf.
EAN-13 and UPC-A carry a check digit. If you get it wrong you get a warning that names the digit you sent, the correct one, and the number the barcode was actually produced with.
Produce shelf, product and markdown labels of different sizes through a single API endpoint.
This image was produced from the ZPL beside it with the Labelixa engine.
Try your own ZPL code →^XA
^FO25,20^A0N,28,26^FDCOFFEE BEANS 250 G^FS
^FO25,58^A0N,20,18^FDSKU: 44-1902^FS
^FO25,92^A0N,64,56^FD$18.90^FS
^BY3,3,70^FO25,170^BEN,70,Y,N^FD8691234567890^FS
^FO25,265^A0N,18,16^FDShelf: 07 / Aisle: COFFEE^FS
^XZEuropean retail product barcode
SYMBOLOGYUPC-ANorth American retail product barcode
SYMBOLOGYCode 128Internal stock codes and shelf labels
No: send 12 digits and the check digit is calculated. Send 13 with a wrong last digit and you get a warning naming the expected digit and the number the barcode was produced with.
Yes. Text fields are processed as UTF-8, so German and Turkish characters are drawn.
No. You can render the same ZPL at different sizes and fill the fields with variables.