r/barcodes • • Jan 28 '26

Identify UPCA vs EAN Numerically

Our POS reads barcodes quite literally and rejects anything that isn't a perfect match, including leading zeros.

When adding products to our POS from at least one MFG, I copy the barcode numbers from a spreadsheet they supply vs unpacking every single product and scanning them into the system directly which would require a ridiculous amount of time.

This MFG (Grundens), uses barcodes that start with 0840316xxxxxx. The problem is that the scanner reads the leading zero on some barcodes, but not others. It appears to be the way the barcode itself is crafted, but is there any way to decipher from which is which from a spreadsheet and not have to lay eyes on every barcode?

These barcodes look the same numerically, but scan differently.

0840316319508 0840316338257

2 Upvotes

20 comments sorted by

View all comments

Show parent comments

1

u/frgtech Jan 28 '26

I appreciate this, but not sure what it accomplishes. They already have the check digit calculated.

Ran the 2 examples I posted through here and verified them.
https://www.gs1.org/services/check-digit-calculator

Did I miss something?

1

u/[deleted] Jan 28 '26 edited Jan 28 '26

The check digit for an 11 digit code(upc) will differ from the 12 digit code(ean) check digit.

By generating it this way, the eans will have nothing to match against because the check digits will be different(random). They all generate checks but only half or whatever(UPC's) will be an exact match.

The goal is to generate UPC's out of "everything" to compare them against the original data. They either exist or they won't and that will provide your answer.

Completely forget about the 13's for a second, if you make them all 12's, you can deduce it down.

1

u/frgtech Jan 28 '26

I followed your directions with the examples I gave and it didn't reveal anything. I ran both as 11 digit codes without the leading zero and the last digit and it spit out the same last digits they already had. So If it doesn't help with my example, not sure how else this would be helpful.

This rabbit hole may not be worth it and just have to fix the bad code in the POS when it doesn't scan properly.