Editorial Policy

A barcode that fails at the point of sale or in a warehouse scanner costs real money, so encoding accuracy matters. This page explains which specifications our generators follow, how they are verified, and what to do if you find a symbol that doesn't behave as expected.

Sources we use

• Retail symbols (UPC-A, UPC-E, EAN-13, EAN-8) — GS1 General Specifications: fixed digit counts, modulo-10 check digit, and minimum quiet zones.
• Logistics symbols (ITF-14, SSCC, GS1-128) — GS1 Application Identifier definitions and carton-marking guidance.
• Linear symbologies (Code 128, Code 39, Code 93) — ISO/IEC 15417, 16388 and the published character sets for each subset.
• 2D symbologies (Data Matrix, GS1 DataMatrix, PDF417, Aztec) — ISO/IEC 16022, 15438 and 24778 encoding rules.
• Publishing codes (ISBN, ISSN) — ISO 2108 and ISO 3297, including the ISSN modulo-11 check character.

How encoding is verified

Symbols are drawn by a widely used, independently maintained encoding library rather than hand-rolled bar patterns. Input is validated first — length, character set and check digit — so an invalid value produces an explicit error instead of a symbol that scans to the wrong data. Automated tests cover the validation rules and check-digit maths for every supported standard.

What we don't do

• We don't issue, sell or register GTINs, company prefixes or ISBNs. Those come from GS1 and national agencies.
• We don't upload your codes: encoding, previews and downloads all happen in your browser.
• We don't take payment for placement, and we don't watermark downloads.

Corrections

If a symbol fails verification against a scanner or a printer's specification, email info@businestools.online with the standard, the exact input and what your scanner returned. Confirmed fixes ship as soon as they are verified.

Learn more about who's behind the site or contact us.