Your input stays in this browser.
Identifier structure
EAN-13 is a GS1 retail identifier, not a price tag. Its first digits normally identify a GS1 company-prefix allocation; they do not reliably identify the country where an item was made. The following digits identify a company and then a trade item, while the thirteenth digit is a check digit. A legitimate number must be allocated by the relevant GS1 member organisation before it is printed on a product.
Worked numerical example
The check calculation alternates weights of 1 and 3, starting at the right of the twelve-digit body. For 400638133393 the weighted total is 4+0+0+18+3+24+1+9+3+9+9+9 = 82. The next multiple of ten is 90, so the check digit is 8. The finished symbol is 4006381333938. This page recalculates that digit rather than trusting a digit pasted with the body.
How the symbol encodes data
The bars are arranged as left guard, six left digits, a centre guard, six right digits and a right guard. The first digit is represented by the parity pattern of the six left encodings rather than its own seven-module digit pattern. That is why an EAN-13 reader can reject a visually plausible sequence when the parity is wrong.
Physical failure mode
Retail scanners need quiet zones, sufficient module width, clean vertical bars and a print process that does not close narrow spaces. Never crop the pale margin to make the symbol look wider. A small JPEG, glossy curve, low contrast background or a label seam can all defeat a correct number. Test the final exported SVG or print proof with the scanner used at receiving or checkout.
Operational boundary
EAN-13 is for globally traded retail items. UPC-A is its twelve-digit North American counterpart; its digits can be represented as EAN-13 by adding a leading zero. EAN-8 is a shorter retail symbol for small packages, whereas ITF-14 identifies outer cases. Those are different identifiers and should not be substituted merely because they share the same checksum family.
A format-specific proof
A useful EAN-13 proof compares three things: the twelve-digit source record, the calculated final digit, and a scan of the final shelf label. If the scan returns 4006381333938 but the catalogue expects another trade item, the bars did their job and the assignment must be corrected upstream. Conversely, do not repair an allocation dispute by replacing the check digit; that would make the number arithmetically invalid as well.
Worked check-digit example
The check calculation alternates weights of 1 and 3, starting at the right of the twelve-digit body. For 400638133393 the weighted total is 4+0+0+18+3+24+1+9+3+9+9+9 = 82. The next multiple of ten is 90, so the check digit is 8. The finished symbol is 4006381333938. This page recalculates that digit rather than trusting a digit pasted with the body.
How the bars carry data
The bars are arranged as left guard, six left digits, a centre guard, six right digits and a right guard. The first digit is represented by the parity pattern of the six left encodings rather than its own seven-module digit pattern. That is why an EAN-13 reader can reject a visually plausible sequence when the parity is wrong.
Printing and scanning limits
Retail scanners need quiet zones, sufficient module width, clean vertical bars and a print process that does not close narrow spaces. Never crop the pale margin to make the symbol look wider. A small JPEG, glossy curve, low contrast background or a label seam can all defeat a correct number. Test the final exported SVG or print proof with the scanner used at receiving or checkout.
When to use this format
EAN-13 is for globally traded retail items. UPC-A is its twelve-digit North American counterpart; its digits can be represented as EAN-13 by adding a leading zero. EAN-8 is a shorter retail symbol for small packages, whereas ITF-14 identifies outer cases. Those are different identifiers and should not be substituted merely because they share the same checksum family.
A retail proof starts with an allocated GTIN-13
For the 12-digit body 400638133393, alternate weights 1 and 3 from the right: the weighted sum is 82, so the next multiple of ten gives check digit 8 and the complete EAN-13 is 4006381333938. That arithmetic is useful for catching a transcription error, but it does not establish that the number belongs to a particular pack. GS1's retail implementation guideline identifies EAN-13 as the carrier for a GTIN-13 and distinguishes it from other GTIN representations: https://ref.gs1.org/guidelines/2d-in-retail/ . Keep the allocated GTIN, product description, country-market data and artwork revision in the product record; do not infer country of manufacture from the initial digits. A valid final 8 on a number copied from another product is still the wrong label.
Release the shelf unit, not a browser preview
Suppose a 500 mL bottle and its six-pack carton share a design review. The bottle's EAN-13 must scan into the consumer-unit point-of-sale record; the carton may need a different case-level identification route. Print the consumer symbol on the final bottle substrate, respecting its pale quiet zones and a flat panel away from the seam, then scan it at checkout. Compare all 13 characters returned with the approved value. A clean SVG on a laptop proves that the generator drew the modules; it does not prove that varnish, curvature, ink spread or the retail scanner preserve them. If the number scans but retrieves a wrong SKU, stop and correct master data. If it fails only after production print, retain the GTIN and investigate scale, contrast and placement. Recalculating the last digit addresses neither failure. This page's result is therefore an arithmetic and artwork input, not a product-registration service.
Check the human-readable digits after imposition
The number under an EAN-13 symbol gives an operator a last visual cross-check, but it must be compared with the bars after final imposition—not typed from memory. Review 4006381333938 character by character against the source record and scan the final PDF. A mismatch between digits and bars can arise when artwork is overlaid from two revisions; modulo-10 will not necessarily expose that production mistake.
Do not use the check digit as an allocation search
When an unknown 12-digit body yields a plausible thirteenth digit, record it as an unverified candidate and return to the GS1 or product-data owner. A calculator can complete every numerical body; that mathematical capability is exactly why it cannot decide whether a code may be placed on a saleable item. Keep allocation review and checksum review as separate signed steps. The release record should name the approver for each step, because they answer different questions.