Openbravo Issue Tracking System - Java Client POS
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0003906Java Client POS(No Category)public2006-10-09 14:432008-10-07 11:56
Reporteruser71 
Assigned Touser71 
PrioritynormalSeverityminorReproducibilityalways
StatusacknowledgedResolutionopen 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Regression date
Regression introduced by commit
Regression level
Review Assigned To
OBNetwork customer
Support ticket
Regression introduced in release
Summary0003906: MUST HAVES FOR COMMERCIAL USE
DescriptionPrinting:

Each product/item should be associated to at least one
printer. Most restaurants have at least three
printers: a receipt printer, a bar printer and a
kitchen printer. Drikns should print in the bar, meals
should print in the kitchen and bills/receipts should
print on the receipt printer. You also need to have
a "Balance" or "Print notifications" button - this
would print the items just added to the bill at the
appropriate printers. This is not a print of the
receipt/bill it is a docket to tell the people working
in the kitchen/bar to make the meal or drink.

Modifiers:

Should have modifiers and modifier groups - eg
modifier group - Cooking. Modifier - well done / rare
etc... Modifiers should be associated to modifier
groups (one to one relationship). You should also be
able to have a free text modifier. You should be able
to apply modifiers/modifier groups to products or
categories. Eg the product Steak could have the
modifier group Cooking associated to it. Then when you
select a steak it should prompt you if you would like
it well done / rare etc...The product category Coffees
could have the modifier group Coffee Instructions
associated with it etc...

Security:

Waiters should not be able to remove items from the
table that have already had the print notifications
printed in the kitchen or bar. Only a manager should
have this privelidge. This removes the ability to void
items that have already been cooked and taken to the
table.

Multiple Work Stations:

Must have support for more than one register using a
central database, or local databases that are
frequently updated from a central database. Note THIS
SHOULD BE A LAST PRIORITY! Get everything else working
to a point where restaurant owners can use the
application in real life first.

Thank you!
Steps To Reproduce
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2008-10-07 11:56adrianromeroStatusnew => acknowledged
2012-11-07 09:40priyamCategory01 - General => (No Category)

Notes
(0007630)
user71   
2005-06-01 00:00   
(edited on: 2008-06-12 10:12)
This bug was originally reported in SourceForge bug tracker and then migrated to Mantis.

You can see the original bug report in:
https://sourceforge.net/support/tracker.php?aid=1573704 [^]
(0007461)
user71   
2006-10-14 02:28   
(edited on: 2008-06-12 10:08)
Logged In: NO

I agree I think that modifying dinner items is very popular
in Restaurants
(0007462)
user71   
2007-09-17 20:18   
(edited on: 2008-06-12 10:08)
Logged In: YES
user_id=1881928
Originator: NO

I applaud this! However, we also need multiple tickets per table! This is a basic feature that can not be overlooked!

And the multiple work stations shouldn't be disregarded, we need to replace our current systems because our hand terminals, after 15 years of hard work, are finally DIEING. These are immensely expensive and buying a hand computer would be cheaper then to replace them.