Thanks, Iām really excited to hear that.
what about :
Hi @ganas
Thanks for your feedback, see my comment inline
We will keep this options under menu list of the POS
Considering category as a group which is already available, weāll add pagination to view more items in the item list view of the POS
yes I mean category as in group, but instead of searching group manualy in search box, you have select box that is populated with groups from Item Group Tree.
In usability last thing you wanna have in POS interface is using keyboard or going through heading menus or lots of unneeded popup boxes
Dear @rohit_w
I donāt really understand your post. As I see it, this thread (and the related bounty) isnāt only about new features. It is about a new POS interface with the mentioned features. This is also what @ganas mockup and his last posts were about:
and
On the other hand your post seems kind of the other way around:
So maybe Iām misunderstanding your posts. Could you explain further?
I would understand having the same DNA and feel of erpnext that who it supposed to be, but that doesnāt mean you treat POS as the other models in the system or as working with a doctype.
The goal first was to refresh the interface then add features. The current POS packs lots of features, yet when it comes to usability it lacks behind
Most POS use nowadays is on touch screens, thats why in the design we avoid showing up the touch keyboard and use soft pad instead. Even thats why we position some elements like add/edit user elements to be on the top part to not be covered by touch keyboard .
The tab navigation for POS feels more natural approach. Everything is exactly one touch away, no dropdown menus or alert boxes ā¦ the retail user can see everything yet the screen is not in anyway crowded.
For POS every second counts, thats affected by clicking through hidden menus , closing popup boxes, hiding touch keyboard ā¦etc and the current interface doesnāt consider any of that.
the retail users not always technical people, so the interface should be tailored for them in first place.
The current POS interface makes it really hard to expand POS future features like customers queen, customer insights and history, returns ā¦
When as a community came up with new interface design, it took many iterations and many inputs which are based on real life daily usage. Also borrowed ideas from many popular POS systems.
@ganas we will priority usability and features first. It may not look like what you showed but it should address all concerns one way or another!
UI will be consistent with the Frappe UI. Sorry we wonāt compromise on consitency. If you want a colourful UI, maybe it could be a community app 
Maybe all those who contributed can vote whether this fulfills the bounty or not! We are happy either ways with the feedback!
Yes, I agree with you It has to be consistent when comes to colors and choice of ui components (no one mention colors or different CSS or any of that sort, the colors that was used on the prototype were just mockup ). Iām talking about the design itself, the navigation through the interface ā¦ E.g. using tabs instead of nested menus and popup boxes ā¦
We donāt use Tabs anywhere in the UI - most people find tabs counter intuitive. and there is no good solution if there are too many of them. The only place the work is if you have to full width. And that place is already taken by the web browser.
I am not sure we would want to use them here, unless the alternative is really bad. We will implement it without tabs at least to start with.
Navigation, functionality and usability are different things. The fact that same patterns are used over and over again and the user feels comfortable in any part of the system. Hence we are very focussed on consistency. I donāt think tabs are either used in iOS or Android either.
Either ways any further discussion should happen only after there is some implementation to look at.
I think the concept youāre trying to communicate is having more of a ātouch centricā UI rather than just a ātouch capableā UI. While ERPNext works across many devices, it is not touch centric. Reconciling that is not going to happen in the main ERPNext app, but either through a full redesign of all the modules, or a standalone POS Interface which uses an API to connect to ERPNext.
Hi @ganasā¦Seems that the design and financing of the POS is really community drivenā¦Do you (or @rushabh_mehta ) can judge how much money we would approximately need??
Have some comments based on the current POSā¦
As this seems to be a major overhaulā¦maybe the design team can think aheadā¦and make the design such that is becomes restaurant readyā¦tables and customers become a kind of the same thingā¦and the waiting list would than be idealā¦tables1 to 10ā¦just at a coke at table 3 if this is orderedā¦and one step more (not related to POS)ā¦recipes would but BOMsā¦that would give the manager detailed insightā¦
Rgds Robert
see also my contribution of todayā¦add under menu ā¦safe and switch the sales invoiceā¦
Now you are talking business
Someone please start a bounty for that!
great @rohit_wā¦really appreciateā¦dont see it yet as i am a cloud userā¦but looking forward, rgds robert
Seriously???
@olamide_shodunke we have been dying to get our hands on electron. We will definitely do something in the next 3 months. A bounty makes it even more interesting
Coming from a manufacturerās point of view -
Would really like to use POS in our warehouse. Most of our customers work on credit. Can we add a Pay Later button? So pressing the pay later button would mean- sales invoice or delivery note is created and accounts receivable entry added against the customer. This along with default mode being user definable should be great!
Another function that we could use is prioritizing customers/ orders.
An email or update being sent automatically to customer email/phone should be a great feature!
Is it possible to hide prices from certain users in POS?
Your point 1 can already be doneā¦Just set payed amount to zero,
Well depending on yr contribution to bountysource the developers may consider yr wish list
phew! thx Rushabh for keeping an eye on UI/UX
I see too many buttons, colors, tabs and fields, especially if itās gonna work for touchā¦!
I believe any UI intended for use on the shop-floor or in a store-environment should be self explanatory. Rather few and huge buttons with ultra-snappy response to navigate hierarchies than one UI does it all (and requires a manual + glasses to use it)
Maybe interesting for you? Progresive web apps and electron
https://dev.opera.com/articles/pwa-resources/
https://dev.opera.com/articles/pwa-desktop/
Hello All,
Kindly share your feedback on new changes of the POS
Thanks,
Rohit