CashRegister in PyQt5 with barcode logon and 32 programmable buttons
1–10 of 29 posts
Re: CashRegister in PyQt5 with barcode logon and 32 programmable buttons
#2
Re: CashRegister in PyQt5 with barcode logon and 32 programmable buttons
#3How this compares to commercial software solutions? Seems very interesting.
Re: CashRegister in PyQt5 with barcode logon and 32 programmable buttons
#4How this compares to commercial software solutions? Seems very interesting.
I have not compared with commercial applications
I made this as open source for the community.
I have no background in retail.
Re: CashRegister in PyQt5 with barcode logon and 32 programmable buttons
#5How this compares to commercial software solutions? Seems very interesting.
Poorly. I can't imagine using this in a fast-paced retail environment.
Re: CashRegister in PyQt5 with barcode logon and 32 programmable buttons
#6How this compares to commercial software solutions? Seems very interesting.
Poorly. I can't imagine using this in a fast-paced retail environment.
Any specific reasons why you think it would compare poorly to other commercial applications. I have tried the ones at Walmart and they are sometimes very slow to respond .
Re: CashRegister in PyQt5 with barcode logon and 32 programmable buttons
#7Programmer who also works in retail, uh no, this layout highlights all the wrong things. The list of items is half the screen, my current system has it at about 1/4 and buttons are enormous, very easy to use and rarely ever miss a button or hit the wrong one, this looks like that will happen all the time. Also we have a lot of colour in buttons that relate to use (payment buttons red, department buttons green, account buttons yellow), this has grey and grey and grey. It might work but I pity anyone using this system. I think with some more UI considerations for the actual use cases (what do register users need the item barcode for? I might enter it but once the item name pops up I don't need it taking up my screen) this could get good. I also don't need whitespace between buttons, have them as big as you can.
Re: CashRegister in PyQt5 with barcode logon and 32 programmable buttons
#8Earlier quoted context omitted.
Poorly. I can't imagine using this in a fast-paced retail environment.
Any specific reasons why you think it would compare poorly to other commercial applications. I have tried the ones at Walmart and they are sometimes very slow to respond .
To be fair, some commercial systems suck on UX too, but some of them are much better than this.
If you compare it to eposnow[0] for instance, and see the adoption of large clear buttons.
The real differences, as I see it, between this and commercial systems are
1) most commercial tills are clients that poll a server that allows central management of stock, prices, and extraction of sales data by api
2) commercial tills can integrate with card machines, so the price comes up on the machine automatically, and successful payments are registered on the till. In a busy store this stops under/over errors.
The world needs a decent, hackable, open source till, because there are many situations where you need small but important extra features. Without the above I would say appeal is going to be limited, but good luck to the author
[0]:https://www.eposnow.com/uk
Edit:formatting
Re: CashRegister in PyQt5 with barcode logon and 32 programmable buttons
#9How this compares to commercial software solutions? Seems very interesting.
Poorly. I can't imagine using this in a fast-paced retail environment.
I did not design this for big environments.
But maybe persons can use it for non profit organisations,
for instance little shops in elderly homes. I worked as a volunteer in such an environment and i saw the struggle with
other volunteers by payments.
So this could be a solution for those situations.
And by the way it's really fast for not too big environments.
Re: CashRegister in PyQt5 with barcode logon and 32 programmable buttons
#10Programmer who also works in retail, uh no, this layout highlights all the wrong things. The list of items is half the screen, my current system has it at about 1/4 and buttons are enormous, very easy to use and rarely ever miss a button or hit the wrong one, this looks like that will happen all the time. Also we have a lot of colour in buttons that relate to use (payment buttons red, department buttons green, accoun…
You should not compare this with a commercial program, I'am
a hobbyist and not a professional.
I think it's a good effort for an open source product.