SambaPOS

Open Source Restaurant POS Software

User Tools

Site Tools


Writing /var/www/doc.sambapos.org/public_html/data/cache/7/79524b604eb68d3e561ef2449d62ea3c.metadata failed
en:guide:alacarte
Writing /var/www/doc.sambapos.org/public_html/data/cache/e/eb7fc120dc3be87c26bd12dc6f1ead1f.xhtml failed

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
en:guide:alacarte [2011/10/02 18:19]
aloupos created
en:guide:alacarte [2012/09/07 09:30] (current)
Line 1: Line 1:
-The **A-la ​Cart** department type represents the dine-in portion of our example restaurant. ​ This designation is important, because it models the kind of workflow needed to run the dining room.  When implementing a POS, you must consider, from a pure process perspective,​ the events that occur from the time a customer enters the establishment and indicates that he or she wants to eat-in, until the time that customer pays and departs. ​ Each operation is slightly different, but most conform to the following processes: ​+====== A-la Carte ====== 
 + 
 +The **A-la ​Carte** department type represents the dine-in portion of our example restaurant. ​ This designation is important, because it models the kind of workflow needed to run the dining room.  When implementing a POS, you must consider, from a pure process perspective,​ the events that occur from the time a customer enters the establishment and indicates that he or she wants to eat-in, until the time that customer pays and departs. ​ Each operation is slightly different, but most conform to the following processes: ​
   - Tell the host/​hostess they want to eat-in   - Tell the host/​hostess they want to eat-in
   - Customer is seated, given menus   - Customer is seated, given menus
Line 8: Line 10:
   - Food is delivered to table from the kitchen   - Food is delivered to table from the kitchen
   - If the customer orders addition food or drink   - If the customer orders addition food or drink
-  -   ​Additional order printed to the Kitchen ticket printer+  - Additional order printed to the Kitchen ticket printer 
 +  - Customer requests bill 
 +  - Bill printed to the Ticket printer 
 +  - Table is colored to indicate the customer requested the bill
   - Bill is given to the customer   - Bill is given to the customer
   - Customer puts cash or credit card or voucher in the bill   - Customer puts cash or credit card or voucher in the bill
   - Server captures the payment in the POS, settling the bill   - Server captures the payment in the POS, settling the bill
   - Table returns to open status in the table view   - Table returns to open status in the table view
 +
 +These steps are modeled in different areas of Sambapos configuration,​ but start in the departments designation. ​ The following screenshot is an example of an in-production a-la cart department:
 +
 +{{:​en:​guide:​new-departments.png?​nolink&​|}}
 +
 +**Department Name**
 + is the name of the department of the restaurant. This name becomes the text on the bottom of the POS screen that the server clicks/​touches to switch between delivery, dine-in, and take out departments. Larger operations can have seperate terminals for each of these departments if needed. This functionality is covered in the "​Terminals"​ configuration screen.
 +
 +**POS Menu**
 + ​indicates the menu used by the [[posclients|POS application]] for this department. ​
 +
 +**Terminal Menu**
 + ​indicates the menu that is displayed by the [[posclients|terminal application]]. In some configurations,​ the terminal menu might be a subset of the POS menu, or might be formatted differently for a different screen. ​
 +
 +**POS Tables View**
 + is the default graphical layout of tables within the restaurant. Laying out tables graphically can help new servers find a table faster, as the layout can be relative to the POS physical position within the restaurant. It also looks better :) 
 +
 +**Terminal Tables View**
 + is the default table view on [[posclients|terminal application]].
 +
 +**Price Tag**
 + ​defines the active price list. If you have [[multiple price lists]] set the active price list here. 
 +
 +**Open Tickets View**
 + sets the configuration for the view of tickets within the POS software. Open Tickets View is a special ticket view that appears when you close ticket view or if you doesn'​t use a table view. It displays only open (active) tickets. Here, you set the number of columns, and if you use [[ticket tags]] you can set the default tag that groups the open tickets by their tag. POS default tag is for the [[posclients|POS application]] and the terminal default tag is for the [[posclients|terminal application]].
 +
 +**Department Type**
 + ​indicates the type of the department, as documented in [[departments]].
 +
 +**Numerators**
 + ​specifies the internal counters for tickets and orders. ​ Each ticket and each order get's a unique number, generated in sequence, to help the software (and the operator) identify a particular ticket.
 +
 +**Ticket Tags**
 + list contains the active [[ticket tags]]. Use add / remove buttons for choosing tag groups for this department.
 +
en/guide/alacarte.1317565171.txt.gz · Last modified: 2012/09/07 09:30 (external edit)