Generic barcode field needed over EAN13

[Kyle Waid]

EAN13 is a European standard. Other parts of the world do not use EAN13. This field provided by OpenERP is not generic enough. IMO, EAN13 should be in a separate module that can be installed on demand. There should also be a generic barcode field that supports more standardized barcode formats like 3of9, UPC, CODE128, etc

It just doesnt make sense to have a field EAN13 and call it the fits all solution, when really this only makes sense if you are in Europe, Not to mention, because EAN13 requires 13 digits it makes it impossible to use any other type of code.

[Nhomar - Vauxoo (nhomar)]

You are right,

Just to add information in ALL our implementation we have solved this behaviour programming some specific solutions.

IMHO we should have solution for EAN13 AND other ones, UPC is used in America, and probably have more than this 2 one,

Im agreed i confirm it is a must to have, considering we have a POS solution out of the box.

REgards.

[Amit Parik (amit-parik)]

Hello kyle,

Such a nice suggestion that "EAN13 should be in a separate module that can be installed on demand" and I agreed with that.

But before implementing this first take the suggestions/Opinion from community.
As per my Opinion it's good improvement and we have to consider it.

That's why I am setting this as an "Opinion".

Thanks and more suggestions are welcomed!

[开阖软件 Jeff Wang (jeff.osbzr.com)]

Any Geo specific feature should be implement in OpenERP as separate module, just do it.

[Eric Caudal - www.elico-corp.com (elicoidal)]

+1

[Normunds (Alistek) (3pm)]

+1

[jclopezar (juancristobal)]

+1 , should be in a separated module. IMHO a generic onee that ask wich barcode is needed.

[Raphaël Valyi - http://www.akretion.com (rvalyi)]

Hello,

I don't know about the quality of this module, but I just want to mention
there are the tr_barcode* modules by Techreceptives and Julius, see
http://techreceptives.com/?q=blog/openerp-barcode-module
and
http://bazaar.launchpad.net/~stock-logistic-core-editors/stock-logistic-barcode/6.1/files/head:/
offering the choice of what type of barcode you want. May be that EAN13
field should be merged inside that more generic barcode module and dropped
from the core?

Regards.

--
Raphaël Valyi
Founder and consultant
http://twitter.com/rvalyi <http://twitter.com/#!/rvalyi>
[phone]
www.akretion.com

On Mon, Nov 26, 2012 at 9:34 AM, jclopezar <email address hidden> wrote:

> +1 , should be in a separated module. IMHO a generic onee that ask wich
> barcode is needed.
>
> --
> You received this bug notification because you are subscribed to OpenERP
> Addons.
> https://bugs.launchpad.net/bugs/1082981
>
> Title:
> Generic barcode field needed over EAN13
>
> Status in OpenERP Addons (modules):
> Confirmed
>
> Bug description:
> EAN13 is a European standard. Other parts of the world do not use
> EAN13. This field provided by OpenERP is not generic enough. IMO,
> EAN13 should be in a separate module that can be installed on demand.
> There should also be a generic barcode field that supports more
> standardized barcode formats like 3of9, UPC, CODE128, etc
>
>
> It just doesnt make sense to have a field EAN13 and call it the fits all
> solution, when really this only makes sense if you are in Europe, Not to
> mention, because EAN13 requires 13 digits it makes it impossible to use any
> other type of code.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/openobject-addons/+bug/1082981/+subscriptions
>

[Ken Roberts (alisonken1)]

IIRC, to validate UPC, the EAN checksum validator can be used by prepending "0"; i.e.:

if len(barcode) == 12:
  ean_validate("0%s" % barcode)
else:
  ean_validate(barcode)

Not sure about the other types, though. Being on the other side of the pond we pretty much just use UPC.

[Ken Roberts (alisonken1)]

Sorry - Attached is the proper patch file ( I hope)

[WhyteHorse (whytehorse)]

This bug is still affecting me. I use 16 digit barcodes so ean13 truncates them. How hard is it to make the field bigger? Pfffft, it's probably like 5min of coding but then "somebody" won't make money selling plugins...

[Kyle Waid (midwest)]

Just dont use that field. I think its stupid the software comes only with
the field EAN13 for barcode, when that format is only used in Europe. Just
create another field called anything and use it on the product record. All
the field is a field.char() with some custom terribly written validation
code. Case closed.

On Sat, Nov 21, 2015 at 8:29 PM, WhyteHorse <email address hidden> wrote:

> This bug is still affecting me. I use 16 digit barcodes so ean13
> truncates them. How hard is it to make the field bigger? Pfffft, it's
> probably like 5min of coding but then "somebody" won't make money
> selling plugins...
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1082981
>
> Title:
> Generic barcode field needed over EAN13
>
> Status in Odoo Addons (MOVED TO GITHUB):
> Confirmed
>
> Bug description:
> EAN13 is a European standard. Other parts of the world do not use
> EAN13. This field provided by OpenERP is not generic enough. IMO,
> EAN13 should be in a separate module that can be installed on demand.
> There should also be a generic barcode field that supports more
> standardized barcode formats like 3of9, UPC, CODE128, etc
>
>
> It just doesnt make sense to have a field EAN13 and call it the fits all
> solution, when really this only makes sense if you are in Europe, Not to
> mention, because EAN13 requires 13 digits it makes it impossible to use any
> other type of code.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/openobject-addons/+bug/1082981/+subscriptions
>