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

Both sides previous revision Previous revision
Next revision
Previous revision
en:guide:alacarte [2011/10/03 01:04]
emreeren
en:guide:alacarte [2012/09/07 09:30] (current)
Line 1: Line 1:
 +====== 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: ​ 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
Line 19: Line 21:
 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: 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&​ |}}+{{:​en:​guide:​new-departments.png?​nolink&​|}}
  
 **Department Name** **Department Name**
Line 25: Line 27:
  
 **POS Menu** **POS Menu**
- ​indicates the menu used by the [[POS application]] for this department. ​+ ​indicates the menu used by the [[posclients|POS application]] for this department. ​
  
 **Terminal Menu** **Terminal Menu**
- ​indicates the menu that is displayed by the [[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. ​+ ​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** **POS Tables View**
Line 34: Line 36:
  
 **Terminal Tables View** **Terminal Tables View**
- is the default table view on [[terminal application]].+ is the default table view on [[posclients|terminal application]].
  
 **Price Tag** **Price Tag**
Line 40: Line 42:
  
 **Open Tickets View** **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 [[POS application]] and the terminal default tag is for the [[terminal application]].+ 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** **Department Type**
Line 49: Line 51:
  
 **Ticket Tags** **Ticket Tags**
- ​list ​is the active [[ticket tags|tickettags]] for this department. ​+ ​list ​contains ​the active [[ticket tags]]. Use add / remove buttons for choosing tag groups ​for this department.
  
en/guide/alacarte.1317589491.txt.gz ยท Last modified: 2012/09/07 09:30 (external edit)