Community Mailinglisten Archive
Re: Odoo to manage a supermarket.durch
Materialized View Strategies Using PostgreSQL...
Materialized Views aren't a gimmick and so check them out... Those plpgsql triggers could be written in PL/Python just as easily...
If you've got a packtpub account, you can find PL/Python and Plpgsql trigger examples here.
I advise you not to do this.
We tried to implement odoo POS in a supermarket, but it was not a successful project. We have concluded that the POS is more suited to commerce/stores with a small amount of products and no problems with things like speed and efficiency.
These are the critical problems we faced with our customer:
· Hardware integration, specifically barcode readers, if you rely on keyboard mode, you will end up with missed scans, if you rely on software servers, you are affecting speed and will have latency problems
· Session starting and closing: with thousands of products this takes too much time
· Secondary display integration ( LCD/LED )
· Overall speed and reactivity feel
· Lack of touch keyboards
We ended up scraping the odoo POS module and building a brand new standalone POS client, that is integrated with odoo and has native hardware support ( Barcode reader communicating via serial/usb interface instead of keyboard mode ) and is highly reactive/efficient with instant session starting/closing.
Here are a couple of screenshots:
Chief Technology Officer @ IBS North Africa
M +212 666 048 931 O +212 539 990 682
Please, can I have your feedback on the implementation of Odoo for a supermarket with several POS and less than 100 000 product references (or more)?
Thanks in advance