Paste a list of codes, product names and prices, and get a printable sheet of barcode labels, invalid codes are flagged with a reason, not drawn.
Codes can be 12-digit UPC-A or 13-digit EAN-13. The check digit is verified, and invalid codes are flagged with a reason instead of being drawn.
Each line holds a code, a product name and a price, separated by commas. Twelve-digit codes are drawn as UPC-A and thirteen-digit codes as EAN-13 using the JsBarcode library, loaded from a public CDN. Before drawing, the tool verifies the check digit, the last digit of a UPC or EAN is calculated from the others, so a mistyped code usually fails this check and is flagged with the reason instead of producing a label that will not scan. Valid labels are laid out in a 30-up sheet grid (three across, ten down on a full sheet) ready to print. A barcode that prints is not a guarantee a retailer will accept the product: codes must be legitimately assigned to the seller, and retailers and marketplaces make the final decision on which codes they accept.
Why was a code flagged as invalid? The usual reasons are length, UPC-A needs 12 digits and EAN-13 needs 13, non-digit characters, or a check digit mismatch, which means one of the digits was probably mistyped. The flag beside each code states which reason applies so the source list can be corrected.
Does a printed label guarantee the barcode will be accepted? No. This tool only draws a correctly formatted, checksum-valid barcode. Retailers and marketplaces make the final decision, and product codes are normally assigned through GS1, a self-invented number may scan but still be rejected.