UPC-A VS. EAN-13 The scanner-recognized
barcodes:
Table Of Contents:
1. Definitions, interpretations, contexts
2. Why is it required to difference
between human-eye visible barcode text and
scanner-recognized barcodes ?
3. The scanner in use
4. The discussion
5. Statements, arguments
6. The conclusion: Based on statements and
arguments
7. Contra arguments
8. Facts and evidences
9. Why use only an EAN scanner?
Helpful Informations:
10. What can you do, if you don't have a
scanner and the check digit is probably omitted from the barcode text (not
visible on the HRT), so it’s unknown?
11. How do you check, that a UPC / an EAN scanned
barcode is valid or invalid?
12. Official informations from the web
1. Definitions, interpretations, contexts
1.1 Barcode symbology:
Black
and white bars pattern, horizontally across the bars. Different
thicknesses vertical black lines and white spaces define expresses the
information.
An information field on the release without the barcode text (human readable text) digits. The information cannot be interpreted by the human eye, therefore requires a scanner (barcode reader).
An information field on the release without the barcode text (human readable text) digits. The information cannot be interpreted by the human eye, therefore requires a scanner (barcode reader).
1.2 Scanner (Barcode Reader):
A hardware, which can recognize only the
printed barcode symbologies. From the barcode symbology decode the information
into alphanumeric digits. Creates a unique identifier (ID) number and send it to the computer, which automatically
typing the digits, so it displayed on the monitor. The scanner can't recognize the
barcode text (human readable text) digits, only the information of the printed barcode
symbology.
The scanner by alone yet don't know which
code it will recognize from the barcode symbology information: a UPC or an EAN
barcode.
Also means a scanner: a smartphone or tablet
with free scanner application.
1.2.1 If you have a scanner with UPC
standard-support: The recognized barcode contains always 12 digits,
independently from how many digits (13 digits or less with leading zero "0") includes the barcode text (human readable text), that you see on the release.
1.3 Barcode (Text), also known as Human Readable Text (HRT):
Printed digits on the release - around
the barcode symbology - that You factually see with your eyes. Contains usually between 10 - 13 digits. Just an auxiliary
information for human, who don’t have a scanner.
Interpreted as:
Barcode (Text): "As it appears on the
release (on the HRT) by the human eye." It must be the exact number, that the barcode
text factually shows.
Based on a full image of the release,
that the user or somebody else already uploaded to a website.
"Release" = a cover or / and a
label, sometimes a added sticker on the cover or label.
The Human Readable Text (HRT) never cannot
be called a scanned barcode, because the scanner can't recognize
nothing from the printed barcode text (HRT) digits information.
1.3.1 If the barcode text (HRT)
include 13 digits, and the first digit is not zero "0", in this case if there is no misspelling error, then the scanner-recognized barcode will always be exactly the same as the barcode text
(HRT) number.
1.3.2 If the barcode text (HRT) include 13
digits (looks like an EAN-type barcode), but the first digit is a leading zero
("0") or the barcode text include only 12 digits or
less, then the scanner-recognized barcode actually can be both (a UPC with 12 digits or an EAN with 13 digits), depending on the standards
supported by the scanner, that you use.
For example:
Barcode (Text) (HRT): 0 035627 423321 (13
digits)
Barcode "Scanned" (Without UPC standard support): 0035627423321 (EAN 13
digits)
Barcode "Scanned" (With UPC standard support): 035627423321 (UPC 12 digits)
Barcode "Scanned" (With UPC standard support): 035627423321 (UPC 12 digits)
1.4 Barcode (Scanned) (UPC or EAN):
The scanner-recognized barcode identify the release based on the information from printed barcode symbology.
USB scanner with UPC/EAN standard-support: Each EAN barcode - as scanned barcode - contains 13 digits.
Exception: If the printed barcode text on the release contains 13 digits (so looks like an EAN-type barcode), but the first digit of the barcode text is zero („0)”, then the scannad barcode is actually just a UPC-type barcode with 12 digits, so the scanner leaving the leading zero ”(0)”.
USB scanner with UPC/EAN standard-support: Each UPC barcode - as scanned barcode - contains 12 digits.
All "free" scanner application - without UPC standard-support - automatically add a leading zero (0) to all 12-digit UPC barcodes. 0 + UPC = EAN
So: Each UPC scanned barcode contains 12 or 13 digits with leading zero ("0"), depends on wich standards supported the scanner, so how the scanner-software is configured.
Scanned barcode: As it appears on the monitor, display of the smartphone or tablet.
The essence of the scanner-recognized barcode is to identify the release based on a valid unique identifier (ID) number, which also visible by the human eye.
The scanner-recognized barcode shouldn’t be incorrect data.
The checksum - wich is the last digit of the scanned barcode - checks, that the full barcode is valid or invalid.
The last digit of a barcode number is a computer check digit which makes sure the barcode is correctly composed.
The scanner-recognized barcode can only be valid. The validity of all barcode can be checked:
USB scanner with UPC/EAN standard-support: Each EAN barcode - as scanned barcode - contains 13 digits.
Exception: If the printed barcode text on the release contains 13 digits (so looks like an EAN-type barcode), but the first digit of the barcode text is zero („0)”, then the scannad barcode is actually just a UPC-type barcode with 12 digits, so the scanner leaving the leading zero ”(0)”.
USB scanner with UPC/EAN standard-support: Each UPC barcode - as scanned barcode - contains 12 digits.
All "free" scanner application - without UPC standard-support - automatically add a leading zero (0) to all 12-digit UPC barcodes. 0 + UPC = EAN
So: Each UPC scanned barcode contains 12 or 13 digits with leading zero ("0"), depends on wich standards supported the scanner, so how the scanner-software is configured.
Scanned barcode: As it appears on the monitor, display of the smartphone or tablet.
The essence of the scanner-recognized barcode is to identify the release based on a valid unique identifier (ID) number, which also visible by the human eye.
The scanner-recognized barcode shouldn’t be incorrect data.
The checksum - wich is the last digit of the scanned barcode - checks, that the full barcode is valid or invalid.
The last digit of a barcode number is a computer check digit which makes sure the barcode is correctly composed.
The scanner-recognized barcode can only be valid. The validity of all barcode can be checked:
1.4.1 UPC (UPC-A) barcode: Scanner with
UPC standard-support can encode only 12 digits based on the information of the
printed barcode symbology.
1.4.2 EAN (EAN-13) barcode: Scanner without UPC standard-support defines 13 digit coding variants based on the information
of the printed barcode symbology.
1.4.3 Each UPC barcode is also an EAN
barcode, because the EAN barcode based on the UPC standard support. The UPC-A barcode
is a subset of the EAN-13 barcode. This means that any software or
hardware can recognize an EAN-13 symbol will automatically be able to read also
an UPC-A barcode.
Generate a UPC barcode. Make an EAN
barcode with leading "0" and the remainder digits should be exactly the same as the
digits of the UPC bacode.
So: If the first digit on the EAN-13
barcode is zero ("0"), then the remaining digits (2-13 digits) and
the 12 digits of the UPC-A barcode will always be exactly the same.
For example:
Barcode (Text) without the check digit:
1234567890 = Human eye visible
Barcode (Scanned) with the check digit:
012345678905 = UPC-A Standard support
0012345678905 = Without UPC-A (EAN-13) Standard support
The valuie is always be exactly the same, just the standard is different.
The UPC and the EAN barcode is a simple logical
system, like this:
Text:
1 = 1 Human eye visible
With the standard-support:
1 = 01 (Based on standard "A")
1 = 001 (Based on standard "B")
etc.
The valuie is always be exactly the same, just the standard is different.
1.4.4 In certain cases, each EAN barcode
is also a UPC barcode:
If the first digit of EAN-13 barcode is
zero ("0"), also the scanner with UPC standard-support can recognize it
perfectly based on the barcode symbology information.
If the first digit of EAN-13 barcode is not zero "0", in this case the scanner only with UPC standard-support will never recognize the information of barcode symbology.
1.4.5 Because the scanner is recognize the
barcode based on the printed barcode symbology information, therefore
this argument cannot always be accepted:
"Barcode (Scanned)" = "As it appears on the release by the human eye just without space"
"Barcode (Scanned)" = "As it appears on the release by the human eye just without space"
Interpreted as:
Barcode (Scanned): "As the scanner
recognzes." It must be the exact number, that the scanner factually
shows.
Based on the user's own scanner or
somebody else's scanner-recognized barcode database on the web.
All around the world if two or more people
use the scanner based on the same copies of the same release, the scanned
barcode is always exactly the same.
1.5 The database
Web database based on scanner-recognized barcodes:
Web database based on scanner-recognized barcodes:
Huge pile data from a reliable (valid)
source based on somebody else's scanner informations.
Out of the discogs.com big corporations and companies, whose millions of releases has already been sold out in the past, - based on scanner-recognized EAN barcodes - had been built a huge database on the web.
The
possibility of any human error occurring is completely excluded in the
scanner-created barcode database, because not a human, but the scanner is typed the barcode into the database.
The scanner-recognized barcode can only be valid and the validity of all barcode (UPC / EAN) can be checked.
The last digit of the barcode the so-called check digit. This digit checks, that the full barcode is valid or invalid.
If you don’t have a „real” scanner in your hand, don't worry, it is not problem. The database is public, and anybody can to find any scanned barcode from any release.
The scanner-recognized barcode can only be valid and the validity of all barcode (UPC / EAN) can be checked.
The last digit of the barcode the so-called check digit. This digit checks, that the full barcode is valid or invalid.
If you don’t have a „real” scanner in your hand, don't worry, it is not problem. The database is public, and anybody can to find any scanned barcode from any release.
2. Why is it required to difference
between human-eye visible barcode text and
scanner-recognized barcodes?
2.1 The barcode text (human readable text)
sometimes doesn't include all the digits, that the scanner recognizes based on
the printed barcode symbology information.
Sometimes not sure, that the
scanner-recognized barcode will always be exactly the same as the barcode text on the release.
2.2 Until the early 1990’s only for UPC barcodes, the so-called check digit - which is the last digit of the scanned barcode - often was omitted from the barcode text (human readable text).
Therefore it is not visible by the human eye, but the check digit is part of the barcode symbology (bars) and is basically required for scanners. In this case the barcode text contain only 10 or 11 digits.
For example:
Barcode (Text) (HRT): 0 90204 00381 (11
digits)
Barcode (Scanned UPC): 090204003815 (12 digits)
Barcode (Scanned EAN): 0090204003815 (13 digits)
or
Barcode (Text) (HRT): 0 7777-94310-2 (11
digits)
Barcode (Scanned UPC): 077779431021 (12
digits)
Barcode (Scanned EAN): 0077779431021 (13 digits)
Barcode (Scanned EAN): 0077779431021 (13 digits)
If the database is not included the last (check) digit of the scanned barcode, then in vain you use the scanner (barcode-reader), there will be no results found in the database.
2.3 From the mid 1990's generallys the barcode text (HRT) is the same with the UPC / EAN barcode, so already included the barcode last (check) digit. In this case the barcode text contains 12 or 13 digits.
2.3 From the mid 1990's generallys the barcode text (HRT) is the same with the UPC / EAN barcode, so already included the barcode last (check) digit. In this case the barcode text contains 12 or 13 digits.
2.4 Mythbusting
2,4,1 Frequent misinterpret: most people
are misinterpret the concept of scanner-recognized barcode, they think so, that
the scanned barcode - without a space - are always exactly the same as
barcode text (HRT).
This is not true!
The truth is that, the scanned barcode - without a space - are not always exactly the same as barcode text
(HRT).
2.4.2 The number of digits by the
scanner-recognized barcode not depend on the number of digits by the barcode
text or on the type of the barcode symbology, but only depending on the
standards-supported by the scanner, that you use.
You have a scanner with a UPC or an EAN standard support?
You have a scanner with a UPC or an EAN standard support?
It is not the barcode symbology or the number of the barcode text digits is defines, that the scanner-recognized barcode will be
a UPC (with 12 digits) or an EAN (with 13 digits). This is defines by the scanner standards-support.
If the barcode text (HRT) already include
13 digits, and the first digit is not zero "0" then the EAN
scanner-recognized barcode will always be exactly the same as the barcode text
(HRT) on the release.
The UPC / EAN scanner-recognized barcode
is not a human-created number, the human (user) just entered the barcode into the database.
2.5 Essence of:
Barcode (Text) = Printed numbers on the
release - around the barcode symbology - that actually visible by the human eyes.
Contains between 10 - 13 digits.
Interpreted as: "As it appears on the
release (on the HRT) by the human eye." It must be the exact number, that the barcode
text factually shows. Based on a full image from the release, that the
user or somebody else already uploaded to a website.
Barcode (Scannad UPC) = Scanner-recognized
number with 12 digits, as it appears on the monitor (display) based on the
printed barcode symbology information.
Barcode (Scannad EAN) = Scanner-recognized
number with 13 digits, as it appears on the monitor, or display of the
smartphone or tablet, based on the printed barcode symbology information.
Interpreted as: "As the scanner
recognzes." It must be the exact number, that the scanner factually
shows. Based on the user's own scanner or somebody else's scanner-recognized
barcode database on the web.
3. The scanner in use
For example:
This is a US release:
The barcode text (HRT) of this release
originally contains only 10 digits.
„7567-97161-0” (10 digits) as Barcode
(Text)
If you have a scanner with a UPC standard
support, the scanner will recognize the following barcode based on the
barcode symbology information:
“075679616104” (12 digits) as Barcode
(Scanned UPC)
The first digit (0) and the last (check)
digit (4) from the scanner-recognized barcode is not visible by the human eye on the release.
If you have a scanner without a UPC standard
support, the scanner will recognize the following barcode based on the
barcode symbology information:
“0075679616104” (13 digits) as Barcode
(Scanned EAN)
The first two digits (00) and the last
(check) digit (4) from the scanner-recognized barcode also is
not visible by the naked eye on the release.
4. The discussion:
What is the subject of this discussion?
If the barcode text (human readable text)
on the release contains only 12 digits or less, that is the type of the
barcode-symbology is UPC, then the recognized barcode - based on an EAN
standard-supported scanner - can it be interpreted as an EAN scanned barcode
with 13 digits, or interpreted only as a UPC barcode with 12 digits?
The scanned barcode is it allowed
entering into the database with 13 digits?
How to interpret it the term: "Barcode (Scanned)"?
"As the scanner recognzes".
Scanner with an EAN standard support = 13 digits
Scanner with a UPC standard support = 12
digits
or
"As the barcode-symbology shows".
For example:
US release.
Barcode (Text): 0 3119-80123-1 5 (12 digits)
Barcode -symbology on the release: UPC
Scanner: an EAN standard supported (13 digits)
With an EAN standard support the
scanner-recognized barcode will factually be:
0031198012315 (13 digits) as
Barcode (Scanned EAN)
With a UPC standard support the scanner-recognized barcode will factually be:
031198012315 (12 digits) as Barcode
(Scanned UPC)
The question is:
What to type into the database?
A. 0031198012315 (13 digits) as Barcode (Scanned EAN)
"As the scanner recognzes".
Interpreted as: It must be the exact number, that the scanner factually shows.
The essence of the "Barcode (Scanned)" as a definition: The scanner identifying the release and creates a valid unique identifier (ID) number, which also visible by the naked eye, therefore no matter what is the type (UPC or EAN) of the barcode-symbology.
B. 031198012315 (12 digits) as Barcode (Scanned UPC)
"As the barcode-symbology shows".
Interpreted as: If the type of the barcode-symbology is factually UPC, no matter what kind the standard-support of the scanner (EAN or UPC), so the scanner-recognized barcode can only be a UPC with 12 digits.
"It would be confusing to refer to an "EAN" on a release which has a UPC-A type of barcode, even though the bars can be interpreted as a 13-digit EAN string.”
C. Both scanned barcodes is correct, because the barcode-symbology is UPC, but the scanner standard-support is EAN.
So, if we say: "Barcode (Scanned)" like a valid number, then what does it really matter?
If we say: The identification of the release. What is the essence? What is the basis for identification?
The scanner-recognized valid unique identifier (ID) number, or the type of the barcode-symbology?
5. Statements, arguments:
"User adding invented EAN barcodes to
items.
Items have no EAN’s (on the HRT), yet he's
added EAN’s.
If it's not on the release (on the HRT),,
it shouldn't be added.
What you're doing is converting UPC to EAN
and adding that info to releases. Like I said in the history, that's like
adding Chinese translations to the titles to make it easier for
Chinese-speakers to find things. We do not do that. We keep with the info
that's on the release. ”
or
„List as it appears on the release. If it
looks like a UPC barcode (on the HRT), don't make it an EAN scanned barcode”
or
„If they don't exist on the release (on
the HRT) Entirely Incorrect vote away.”
or
„when an entry has an "made up"
EAN-barcode listed, another user he might think it's a different release and
adds it as a different database entry, polluting the database with false
duplicates”
or
„As I see it, somapeti2 is unilaterally
adding variations in formatting in a misguided attempt to be helpful.
The correctness of the information is
irrelevant; it is unwanted because it is redundant.
Management has stated somewhere in this forum that the intent of RSG §5.2.a is such that we are not allowed to enter any more variations of the same barcode.
Management has stated somewhere in this forum that the intent of RSG §5.2.a is such that we are not allowed to enter any more variations of the same barcode.
You are violating guidelines, policies,
and forum consensus when you make edits to add "EAN" versions of
scanned, already-entered UPC barcodes. Adding redundant data is creating
clutter and the possibility of error, and is the wrong approach to solve a
problem with search engine indexing.
When the 12-digit format has already been
entered, you cannot add the 13-digit EAN format too.
It is not a real scanner.
The GS1 standard dictates that a UPC-A
barcode may be decoded as a 13-digit EAN by adding an implied leading
zero to the GTIN-12. Because of this, and because of the way
scanners and vendor databases operate, it is arguably valid
to say:
Each item has an "EAN" which is
the 13-digit interpretation of the bars.
This overlap and ambiguity in
the terminology makes it difficult to precisely describe Barcode fields on
Discogs. A description of "EAN", for example, may refer to the type
of barcode image, or it may refer to a given scanner's numeric interpretation
of the bars.It would be confusing to refer to an
"EAN" on a release which has a UPC-A type of barcode, even
though the bars can be interpreted as a 13-digit EAN string.”
6. The conclusion: based on statements and
arguments:
These arguments suggest, that if the
barcode text (human readable text) that you see on the release contains only 12
digits or less, that is the type of the
barcode-symbology is UPC, the following facts do not matter:
- The scanner with EAN standard support
can perfectly recognize any UPC barcode, and
- Many companies or databases
factually refer only to the EAN barcode with 13 digits based on millions of
releases on the web.
In this case despite
the facts to the contrary:
- the scanner-recognized barcode with 13
digits can't be interpreted as an EAN barcode, because the type of
barcode symbology on the release is UPC.
- not allowed to use a scanner with an EAN
standard-support,
- the EAN scanned barcode with 13 digits
not a real (valid) barcode,
- not allowed the EAN scanned barcode
entering into the database, therefore
- the entered EAN is incorrect.
7. Contra arguments:
"EAN is a superset of UPC. Any UPC is
also an EAN depending how the scanner software is configured. The scanning app
on my phone interprets all UPC as EAN. It’s not incorrect. "
"Having said that, I think taking a
12-digit scan and prefixing it with 0 constitutes a preference edit.
"
"Barcodes exist to be scanned. If the
number when scanned is 012345678905, but the human readable text for whatever
reason shows e.g. 666-SATAN-IS-OUR-MASTER-666, the barcode is still factually
012345678905.
The complication here is that, as EAN is a
superset of UPC, a scanner might interpret that code as 012345678905 UPC-A or
0012345678905 EAN. Both are correct. "
"The Bar-Code app for iOS always
prefixes UPC-A with 0, and yes, it is a real scanner."
8. Facts and evidences:
8.1 Facts and evidence, that the barcode text (HRT) with 12 digits or less can be interpreted as an EAN scanned barcode with 13 digits:
Not
arguable fact:
8.1.1 The scanner with an EAN standard support can recognizes any UPC and EAN barcode perfectly, and decodes an alphanumeric number always with 13 digits based on the barcode symbology information. The created valid unique identifier (ID) number can only be valid. The validity of all barcode can be checked.
8.1.2. Nowadays already nobody use a
scanner only with a UPC standard support anymore, because if the first digit of
the EAN-13 barcode is not zero "0", then the scanner will never
recognize the barcode-symbology information.
8.1.3. Many companies or databases
factually refer only to the EAN barcode with 13 digits based on millions of
releases on the web:
EAN 0031198012315 (13 digits)
EAN: 0090204003815 (13 digits)
Barcode (EAN): 0031198012315 (13
digits)
JAN: 0031198012315 (13 digits)
JAN: 0090204003815 (13 digits)
Product name for EAN 0031198012315: direkt
link to amazon.com:
The US Amazon can also interpret the EAN
barcode, please visit to website:
Enter in the search box the following EAN
barcode: „0031198012315” and after click ont he search button.
Amazon US says: 1 result for
"0031198012315"
EPMD - Strictly Business 12” vinyl
So the Amazon.com also can interpret the
EAN barcode with 13 digits.
8.1.4 Discogs Guidelines
Barcodes can be sourced from both:
1. the barcode text (the numbers printed
below the barcode field)
2. by reading the barcode itself
with a barcode scanner.
If there is a discrepancy between these
two sources, both barcode variations can be entered into separate barcode
fields.
The 'Description' field can be used to
indicate the source of the barcode.
For example:
"Text" (the numbers printed
below the barcode field)
and
"Scanned" (when using a barcode
scanner to read the code).
In the case of multiple barcodes on a
release, they can all be entered in separate barcode fields - please use the
'Description' field to provide any further information, if possible.
8.2 As for the arguments that If the barcode text HRT contains 12 digits or less, then - with the help of a scanner with an EAN standard support - shouldn't ever be interpreted as an EAN scanned barcode with 13 digits, only interpreted as a UPC barcode with 12 digits, these are not acceptable.
8.2.1 If necessary, you needs to check,
that a certain release is already exist in the discogs database:
Shouldn't ever to check the scanned
barcode because the naked eye doesn’t always see all the numbers on the
release.
In this case, only the barcode text (HRT)
number needs to checked, because the naked eye can see only that.
8.2.2 The argument, that a certain release
has no an EAN barcode, false statement.
The EAN, as a scanned barcode is a
standardized barcode with 13 digits.
Therefore each item has an EAN barcode.
The scanner with an EAN standard support generates this barcode.
8.2.3 Nowhere is a rule written, which
clearly prohibits, that both, but different scanned barcodes (UPC; EAN)
shouldn't ever to appears parallel in the database.
The RSG §5.2.a.not included: If the
barcode text (HRT) contains only 12 digits or less, you never use a scanner
with an EAN standard support.
There is no rational argument, that why is
it a problem to enter both, but different types of scanned barcodes?
A UPC scanned barcode with 12 digits and
an EAN scanned barcode with 13 digits is not the same type of barcodes, even
then if the last 12 digits are exactly the same.
The RSG §5.2.a.also not included: If
someone only have a scanner with an EAN standard support shouldn't ever to
enter the scanned barcode with 13 digits into the database, because a other
user - who has only a scanner with UPC standard support - already before has
entered the scanned barcode with 12 digits.
8.2.4 The RSG §5.2.a.also not included,
that it create a "confusion" for example when a release has a UPC-A
type of barcode on it (UPC: 031198012315), yet you fill in the BAOI description
fields so that it reads (EAN: 0031198012315).
The question: Why create a
"confusion"???
Till now no evidence, that:
"The GS1 standard dictates that a
UPC-A barcode may be decoded as a 13-digit EAN number by adding an implied
leading zero to the GTIN-12. Because of this, and because of the way scanners
operate, it is arguably valid to say:
Each item has an "EAN" which is
the 13-digit interpretation of the bars.
It would be confusing to
refer to an "EAN" on a release which has a UPC-A type of barcode,
even though the bars can be interpreted as a 13-digit EAN string.”
This is just a personal opinion without rational arguments.
The barcode is
manually entered into the database, there is no opportunity to click on this
information, therefore a confusion is excluded.
What is the problem? In this case why not
allow typing the EAN barcode into the database?
What kind of confusion any valid data, that manually entered into the database?
Barcode (Scanned) as
the essence of the definition: The scanner identifying the release with a valid
number, which also visible by the naked eye.
If the scanner work
perfectly (the recognized barcode is valid), there is no matter:
- What kind of type
of barcode field (UPC or EAN)?
- What does the bars
of barcode symbology refer to?
- What contains the
barcode text?
- How many digits
contain the barcode text?
No matter.
Only that matters:
The scanner works perfectly, that is can recognize the
barcode symbology and creates a valid number.
Barcode
(Scanned) It must be the exact number, that the scanner factually shows.
If the
scanner-recognized barcode will be: 0031198012315 (13
digits), no matter:
- How many digits
contain originally the barcode text? 10, 11 or 12
digits?
- What contains
originally the barcode text?
- What does the bars
of barcode symbology refer to originally?
- What kind of type
of barcode symbology originally (UPC or EAN)?
No matter.
The essence of the
scanned barcode: The scanner identifying the release with a valid number, which
also visible by the naked eye.
Based on law any
discussion must be deemed closed, when we find an explanation to all contradictions with rational arguments.
While for contradictions they try to find explanations based on only arbitrary statements - instead of rational arguments - the discussion can never be considered as closed, it is still open.
Justify it with rational arguments!
Without rational arguments just an
arbitrary statement! Nothing else!
Just to you don't like it something
without rational arguments! Done!
If I don't like
something for whathever reason, i can say to anybody without rational
arguments:
This thing will create a
"confusion" in the "system"
9. Why use only a scanner with an EAN standard
support?
If the first digit of EAN-13 barcode is
not zero "0", then the scanner only with a UPC standard support will
never recognize the barcode -symbology information.
For this reason therefore nowadays already
nobody use a scanner only with a UPC standard support anymore.
Who would like to use a scanner that
cannot recognize all barcodes?
Recommended always use a scanner with an
EAN standard support.
Scanner with an EAN standard support can
read perfectly also any UPC-A barcode, therefore each item has an
"EAN" barcode which is the 13-digit interpretation of the
barcode barcode-symbology information.
The scanner with an EAN standard support
can't do anything else, than recognize a barcode with 13 digits from
each barcode barcode-symbology, no matter how many digits contains the
barcode text (HRT) on the release.
In all cases the EAN barcode, as a
scanner-recognized barcode is not incorrect information.
The EAN barcode not a
- misguided attempt,
- Chinese translation,
- added value,
- wrong approach,
- irrelevant, unwanted and redundant information,
- false data,
- invented (fictional) code.
The EAN barcode
- doesn”t violate our guidelines and policies,
- doesn”t violate the consensus within the forum,
- doesn”t create confusion, clutter and any errors.
Helpful Informations:
10. What can you do, if you don't have a
scanner and the check digit is probably omitted from the barcode text (not
visible on the HRT), so it’s unknown?
Don't worry, here is the solution:
You can visit this webpage:
You can enter the digits from the release (only 11 or 12 digits) without the check digit and click the „Calculate” button. If you see only 10 digits, enter a leading zero "0" as the first digit.
Do not use spaces, dashes or other
caracters between the digits.
The page will show you with red coloured
character what is the check digit.
Important:
The „system” can’t check, that the entered data is valid, because the last digit is at the moment yet unknown. Therefore the „system” always „gives” a digit, even if the entered data was already incorrect.
After, that you received the complete barcode number (with check digit) you can already to check, that the UPC or EAN barcode is valid.
11. How do you check that a UPC or an EAN scanned barcode is valid or invalid?
The good news is, that you don’t need a
“real” scanner to check this.
Don't worry, here is the solutions:
11.1 First solution:
Please visit this website:
This website is a database with millions of UPC / EAN scanned (!!!) barcodes.
This website contains completely correct valid information. The possibility of error is completely excluded.
Important:
This website never does not interpret the barcode text (HRT) data on the release, but instead shows the scanned barcode (EAN) numbers, which the real scanner can recognize from the barcode field.
Enter or copy - paste the scanned barcode numbers (only 12 or 13 digits) from any release in the search box, and click on the “Chercher’” (search) button.
If found results, the entered scanned barcode number is valid, and the page will show you what is the EAN 13, as scanned barcode number of the certain release.
If the number of entered digits is 11 or less, 14 or more: the search is fault and never found any results.
For example:
11.1.1 Search by UPC code:
Barcode text (HRT): 0 7464-45400-2
Barcode (Scanned UPC): 074644540024
Entered the scanned UPC barcode „074644540024” in the search box.
Good news is, if that having is one or more spaces, dashes, lines, dots or other characters between any digits this is not a problem.
For example: “07 4644 5400 24” or
„0-7464-45400-24”
Please click on the “Chercher’” (Search) button.
The result: “Michael Jackson - Dangerous CD.”
EAN barcode (always without spaces): „0074644540024”.
So the entered UPC scanned barcode number is valid.
11.1.2 Search by EAN code:
Enter the following EAN scanned barcode: „0074644540024”, „00-7464-45400-24” or „007 4644 540 024” and click the search button.
The result and the EAN scanned barcode is the same, so the entered EAN scanned barcode is valid.
11.1.3 What happens with a misspelled digit?
Enter the following misspelled numbers: „174644540024” or „0174644540024” and click tthe search button.
The result (with brown coloured character):
„Identifiant invalide: 0174644540024
Oups ! Il doit y avoir une erreur de saisie, cet identifiant n'est pas valide. Pouvez-vous vérifier s'il vous plaît ? Merci.”
“Invalid identifier: 0174644540024
Oops! There must be an entry error, this identifier (ISBN or EAN) is not valid. Can you check please? Thank you.”
So the entered UPC / EAN scanned barcode is invalid.
11.1.4 What happens if omnit the check digit?
Please re-enter the valid scanned barcode numbers (UPC or EAN), but now without the last (check) digit (4), which on this certain release only the scanner recognizes from the barcode field, but is not visible to the human eye: “07464454002” or „007464454002”
The result (with brown coloured character) also is the same:
„Identifiant invalide / Invalid identifier”
So the entered UPC / EAN scanned barcode is also invalid without the last (check) digit (4), which on this certain release only the scanner recognizes from the barcode field, but is not visible to the human eye.
11.1.5 What happens with a rare or in few copies published release?
Finally enter the UPC / EAN scanned barcode of a very rare or in few copies published release.
For example:
Barcode (Scanned UPC): 743214480120
Barcode (Scanned EAN): 0743214480120
Enter or copy the UPC or EAN scanned barcode number: „7 43214 48012 0” or „743214480120” or „0743214480120”
The result in august of 2019:
Aucun résultat trouvé pour “ 0743214480120” dans le catalogue.
No results found for "0743214480120" in the catalog.
Importtant!
The message means that the entered UPC / EAN scanned barcode otherwise is correct, that is valid, only no results found in the database, probably because this certain release is very rare or in few copies published.
11.2 Second solution:
You can visit this webpage:
You can enter the received UPC or EAN barcode (only 12 or 13 digits) without spaces and click the „Validate” button.
The page show you what is the result:
Green colour: the code is valid.
or
Red colour: the code is invalid (incorrect).
If the barcode is incorrect, then the original barcode (without check digit) was already invalid.
12. Official informations from the web:
What is EAN – European Article Number
For a long time, we assumed that products
manufactured within US and Canada would sell in these territories alone. We
also thought that manufacturers would produce these goods locally as
well.
Common knowledge and time have shown that this is often not the case, hence the need for an EAN. The EAN is the same as a UPC, except it has a single digit country code prefixed to it, thus making it 13 digits long.
If your customer base resides in the US and Canada, stick to a UPC as most older barcode readers can only recognize the 12 digit UPC.
If you’re selling internationally, you’ll need an EAN.
What is the difference between UPC and EAN?
EAN (13 digits) can be used anywhere
around the world even USA and Canada in some cases but UPC (12 digits) are
mainly used in USA and Canada.
Difference between EAN-13 and UPC-A barcodes
UPC-A barcodes are effectively a subset of
EAN-13 barcodes. If the first digit on the EAN-13 number is a ‘0’, then the
bars will be of both the EAN-13 and the UPC-A (without the leading ‘0’) will be
identical. The displacement of the human readable numbers below differ between
the UPC-A and EAN-13 barcodes however, this is the biggest difference. Both
barcodes can be scanned by the majority of scanners easily.
When should You use an EAN-13 vs a UPC-A?
UPC-A format barcodes have traditionally
been used in the USA, whereas EAN-13 format barcodes have been used throughout
the rest of the world. Nowadays, the majority of stores throughout the world
accept barcodes in either format. Howevers there may be some older systems that
only accept one or the other. This means that if your product is being sold in
the USA , the UPC-A format barcodes are best, however if your product is
international, or sold in a country other than the USA, an EAN-13 barcode is
best.
If you come across a store that has difficulty reading your EAN-13 or UPC-A barcode, they can either ignore the leading ‘0’ or add a leading ‘0’ depending on how many digits their system prefers. If this is done, the barcode will read exactly the same as the opposite format (as the bars are identical regardless), and will still be globally unique.
Scanners manufactured after 2004 can read
any UPC/EAN, and will internally interpret the bars as a 13-digit string.
However, if the first digit is zero, then depending on how the reader is
configured, it may report the string as an EAN-13 with all 13 digits, or for
compatibility with old UPC systems, it may drop the initial zero and report the
string as a 12-digit UPC-A.
Free barcode-reading apps for smartphones and tablets often just report everything as EAN-13.
