Usability problems in stock_inventory_barcode

[zeroheure]

I'm currently using stock_inventory_barcode to help my wife with her inventory which is around 3000 different products in 3 places. She is scanning and I am in front of the screen, tabbing from field to field in stock_inventory_barcode wizard.

I have quickly enhanced the module UI to reduce tabs key and dismiss some errors. So this bug report is about the use of tab keys to go in a field and about errors that can happened. Obviously this is keyboard driven. I am currently using the 10.0 version, but problems are the same in 14.0 :

• It is faster with focus on the product_id field. User quickly learn how to deal with some inconvenient of the Many2One field.
• It is easier, faster and error prone to have field add_qty before change_qty because:
  • the most common case after scanning is to tell the operator how much products there is to add
  • currently, the operator can accidentally erase the previous recorded quantity or add to much products if he type the new number next to the previous one instead of replacing.
• there is really a need to focus the input at wizard launch on the first needed field (product_id or product_code), just use stock_inventory_barcode module with web_dialog_size module installed and you will understand (at least in Odoo 10)...

Using product_id to search for barcode creates another usability problem: In product_id field, current barcode search works with exact match and is case sensitive. This is wrong because in retail industry not each product's variant own a barcode, sometimes variants share the same barcode. In this common case, retailers around me simply add a letter after each product barcode to differentiate variant (for example B for blue, G for green, etc.). Odoo POS works like a charm with it. But not stock_inventory_barcode.

[github-actions[bot]]

There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days. If you want this issue to never become stale, please ask a PSC member to apply the "no stale" label.