Invalid barcode output with EAN13/UPC about barby HOT 5 CLOSED

0 is the check digit for this number. If your scanner is UPC-specific it will probably discard the first 0; try changing the number, scanning it and comparing with the check digit (barcode.checksum) and see if it is the case.

from barby.

It appears that certain applications scan it correctly, others don't. However, the resulting barcode is different than the one I received pre-generated from the company I purchased the UPC from. Do you know why that might be?

Edit:
The others that are scanning it "correctly" are still appending a 0. Something is definitely off...

from barby.

Can you show the pregeneratrd one?
On Nov 24, 2015 11:58 PM, "jheathco" [email protected] wrote:

It appears that certain applications scan it correctly, others don't.
However, the resulting barcode is different than the one I received
pre-generated from the company I purchased the UPC from. Do you know why
that might be?

—
Reply to this email directly or view it on GitHub
#54 (comment).

from barby.

Sure.

http://drop.johnheathco.com/ryAjV

Here is the one Barby is generating:

http://drop.johnheathco.com/tT4hy

from barby.

The initial 0 is part of the number, not a UPC designator. This should generate the correct version:

Barby::EAN13.new('009103795804')

or

Barby::UPCA.new('09103795804')

from barby.