Community mailing list archives

community@mail.odoo.com

Re: POS Module and Barcodes

by
Rob North
- 03/04/2015 19:06:48
Fabrice,
I seem to have raised your hackles, and that was not my intent. But FUD? Really?  What I am guilty of is hijacking a thread without contributing any solutions to the original posters problem. For that I apologize.

 Although I probably could have made my point better, I was trying to give you a heads up on what my initial reactions were when evaluating Odoo against a dozen other solutions.  To provide you feedback on a stumbling block I found in that process that nearly eliminated an otherwise great solution from consideration.  When I first evaluated V7, I got to the EAN13 field and my first reaction was we don’t use EAN13, how is this going to work? Let’s test some of our codes. Nope, won’t work.  Maybe there is a configuration setting I can turn it off. Nope, can’t find one. Oh well, on to the next solution.

When V8 came out, it had functionality in it that was compelling enough for me to revisit odoo. That’s when I talked to other experts and found that my EAN13 issue was not the insurmountable hurdle I perceived it to be.  The point I’m trying to make is that If I had that perception, others do too, and it’s causing a lower adoption rate than odoo deserves.
A simple solution might be as easy as adding a tool tip to the Internal Reference that says “Used for any non-EA13 compliant product lookup code.” Or possibly just renaming the Internal Reference field to something more descriptive like “Look-up Code.”

As far as your reminders, I found them a little condescending, and maybe I deserved that. But my personality will not let them go by unchallenged.

Reminder1: A missing feature is not a bug.
 I understand that, but we’re not talking about a missing feature. We’re talking about a perceived forced constraint. If that feature causes operational issues, or in this case, issues with the sales process, it’s a bug the same as a piece of code not working correctly.
 
Reminder2: a software application without limitations doesn't exist.
You’re preaching to the choir here. But why we’re on the subject, here are some things to consider for the future:
1) True Product Information Management. Today we need to maintain more info on products than how many we have in stock and how to get more. Extended attributes, sales copy, videos, brands, and the ability to control what is displayed on the product webpage right from the product record.
2) Ability to create recurring events
3) More intuitive accounting interface (I guess we get some improvements in the next version, so Kudos)
4) Ad-hoc reporting.
5) Documentation
I have others, but there is probably a better place to record these.

Reminder3: talk to experts before starting custom developments.
Did that.  Talked to people in your office. Solicited bids only from agencies listed on your website. My developers have been very good about explaining any requirement that was already handled natively by the software. As for the EAN13 concerns, they have assured me that when an employee scans a barcode or types the product code in the search box of the POS, the correct product will appear. That’s all I really want and care about. They will also remove the EAN13 from the product page so nothing is accidentally entered in that field. Still, it would be more elegant if that were handled natively through configuration.

So you can write off my comments as FUD if you want to. I have provided you some insightful feedback. Mine it for the gold it is, or ignore it, either way I have done my duty.

Rob North


On Tuesday, March 3, 2015 3:40 PM, Fabrice Henrion <fhe@odoo.com> wrote:


Hi Rob,

Please avoid FUD. You are making everyone believe that it doesn't work in the US and it is not true. It works out of the box (tested with a Honeywell Eclipse directly on laptop has well as through POSbox).

Regarding the POS:
In v8:
EAN-13 must be entered in the barcode field on the product form
EAN-8 must be entered in the internal reference on the product form
UPC must be entered in the barcode field on the product form with a leading 0 (to get to 13 digits).

In SaaS-6 and above:
EAN-13 must be entered in the barcode field on the product form
EAN-8 must be entered in the barcode field on the product form
UPC must be entered in the barcode field on the product form
Additionally, there is a full barcode management in POS for more than just products, see https://twitter.com/fheodoo/status/565737973342560259


Regarding the WMS barcode interface:
In v8:
EAN-13 must be entered in the barcode field on the product form (same as for POS)
UPC must be entered in the internal reference on the product form without the leading 0 (12 digits total)

In SaaS-6 and above:
The WMS barcode interface will work for EAN-13 and UPC with the same config as for POS.


Reminder1: A missing feature is not a bug.
Reminder2: a software application without limitations doesn't exist.
Reminder3: talk to experts before starting custom developments.


We have several US retail clients using Odoo POS and WMS in prod (and on the Odoo cloud).
Thank you,
__
Fabrice Henrion
Director Americas
Odoo Inc.
51 Federal Street – Suite 401
San Francisco, CA 94107
Tel: +1 (650) 307-6736
On Tue Mar 3 15 12:47 PM, Rob North wrote:
<blockquote cite="mid:2045090334.814190.1425415396839.JavaMail.yahoo@mail.yahoo.com" type="cite">
Unfortunately Transforming is not a solution for retail, particularly if you are targeting the US. That would require a secondary step of printing out new barcodes and sticking them over the printed barcode supplied by the manufacturer. This adds additional costs and opens up a greater possibility for error.

I understand that this product was developed in Europe, and much of the world moved to EAN13 a long time ago, but in the states not all manufacturers are EAN13 compliant. About 10% of the products I carry do not conform. Forcing EAN13 barcodes is very shortsighted on the part of the Odoo team. Why would you force any kind of restriction like this on a product that is touted for its flexibility? It should be a configuration setting allowing the functionality to be turned on or off. My developers are working on a alternative, but this constraint nearly caused us to exclude odoo from consideration. The odoo folks will find it a challenge to increase their market share with US retailers with this feature (bug) in place, if that is indeed a goal.

Rob North


On Tuesday, March 3, 2015 10:55 AM, Marco Antonio Cruz Andrade <marco.cruz@optimus-software.com> wrote:


Fermin

When loading the products there an option to transform any barcode to a valid EAN13 is below the barcode option in more details .

regards,
Marco Cruz

Sin nada más a que hacer referencia me despido respetuosamente.
Marco Antonio Cruz Andrade
Desarrollo de Aplicaciones, Ingenieria de la Información, Inteligencia de Negocio.
Servicio de Mensajeria, SMS Marketing, Automatización de la Fuerza de Venta
Telefono: (+58) 0276 4237885
Pagina web: www.optimus-software.com 
Optimus Software & Consultoria C.A
2015-03-03 13:27 GMT-05:00 Fermin Arellano <ferminarellano.hn@gmail.com>:
Hi community,

I am using Odoo v8 with the POS for a retail store. I am trying to use the barcode scanner but I am having trouble since the products on my store have barcodes of 8,11,12,13 and 14 characters and Odoo only works with valid ean13 codes. 

Is there a way to bypass all these checks and validations and just have it compare the barcodes of the scanned product with the one stored in my product catalog. 

Greetings,
_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe

_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe


_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe

_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe