Openbravo Retail POS Web GUI
by Rob Goris
- 6,413 views
Conceptual design work for Openbravo Retail solution. This will integrate POS (Point of Sale) with ERP. The proposed solution is optimized for web and modern touch screens. Feedback welcome.
Conceptual design work for Openbravo Retail solution. This will integrate POS (Point of Sale) with ERP. The proposed solution is optimized for web and modern touch screens. Feedback welcome.
Accessibility
Categories
Upload Details
Uploaded via SlideShare as Adobe PDF
Usage Rights
© All Rights Reserved
Statistics
- Likes
- 0
- Downloads
- 95
- Comments
- 17
- Embed Views
- Views on SlideShare
- 6,405
- Total Views
- 6,413
More about the graphical design: http://openbravouxlab.blogspot.com.es/2012/03/web-pos-graphical-design.html 1 year ago
http://dl.dropbox.com/u/3993014/Openbravo-Retail-Web.zip
Note: Unzip it and run index.htm
I also produced an iPad version that runs in an app called Presentation Link (blogpost on process here: http://openbravouxlab.blogspot.com/2012/03/creating-interactive-mock-ups-on-ipad.html) -- here's the ZIP:
http://dl.dropbox.com/u/3993014/Openbravo%20POS%20V08.zip
Note: You need Presentation Link to run this file. 1 year ago
In a second comment, I will share a link to the the clickable mockup I have used for usability testing. Try it yourself - or even test it on other people! 1 year ago
There is however one key-scenario I'm missing in the concept as a whole: have you given any thought yet to - for example - visualizing and processing payment status/progress notifications of different payment (card) terminals, or the altogether different flow of selling vouchers/loyalty cards with configurable value from within pos?
I know it's probably low prio/ secondary stuff at this moment, compared to basic layout and interaction design features, but I'm just curious ;-) ....
Keep up the good work! Regards,
Simon James 1 year ago
slide 14 -> receipt is misspelled
RG: Yes, corrected now
The fact of clicking first the number and then quantity, or first the number and then the discount button can be tricky. Why is this order?
RG: It saves one click/tap compared to the standard sequence of (1) select what you want to do (2) select the amounts you want to use (3) confirn. Next time you set the alarm in the Openbravo office, you will see what I mean...
If i understood, to finish the ticket i need to click on the import, do i?
RG: Yes, but (since there is a learning curve) the PAY button that sits on top of it, also does the job.
Slide 12 -> i dont see when you insert the import of the voucher (255€). I would change the green color for something more 'warning' (not sure about red)
RG: Fair enough: I´ve added a subtle background hint every time you add an item
Slide 20 -> it would be nice to see the 30% of dicount in the line also (not just in the right part) so at first glance you see all discounts per line
RG: You are right, the line discount is too much hidden. I´ve now added it as a separate item in the ticket, much clearer.
Slide 25 -> i see redundant the tab 'TICKET DSC' or i maybe didnt understand the slides
RG: Yes and no, but I´ve just introduced a different solution: in the keypad you now see two buttons: Line Discount and Ticket Discount. The top toolbar button can now be removed (have not done it yet but will)
Slide 30 -> i don’t see how you get that panel
RG: Ah, did not realize this was not clear. I´ve added a step showing how to get there: you must tap the Keypad button in the top toolbar, this hides and shows the keypad/details panel. Once hidden, you see the product and categories columns.
Slide 33 -> why there is a product with a red circle on its price? to indicate there is a discount? Ok, so the discount is propagated from the product definition, but i see the discount is not applied per unit price, but total line amount. Therefore, does it make sense?
RG: See earlier about discounts, the solution was not optimal and is replaced now, showing line discounts as separate items in the ticket.
Slide 35 and 36 --> I don’t understand them
RG: I hear you (and others) but believe this needs a learning curve. The idea is that in the product list view you see the quantity of items you have already added to the ticket. This prevents you from accidentily adding an item double. Tapping the item itself, adds +1. Tapping the quantity does -1. This is a superuser trick though. Novice users would select the item in the ticket, and then press + or - or an amount in the keypad.
Slide 49 -> Splitting: does it make sense to add functionality of splitting a ticket in 4 equal parts for instance? (im imagining a restaurant scenario where there is a single ticket for 10 people, where they just pay the bill divided by 10)
RG: Great idea, although it´s restaurant specific. I´ve added it to the scenario, maybe nice for a restaurant module.
Slide 57 -> normally, refunds are not allowed if there is no ticket so i don’t see why this new functionality should be developed
RG: Some shops (e.g. in USA) allow returns w/h receipt. I think we should facilitate that. The other scenario (looking up a ticket) is much more common and I need to detail this still. 1 year ago