25 Transactions
Simphony has two types of transactions: sales transactions and non-sales transactions.
Sales Transactions
A sales transaction is the action or set of actions taken to record revenue generating business. A transaction may represent the start of new business, or it may be a continuation of business in the form of picking up an existing guest check. Sales transactions may be performed by an operator like a server, bartender, or cashier. A guest using a kiosk performs a self-service sales transaction. An Application Programming Interface (API) processes sales transactions from guests placing orders online. A transaction ends either by service totaling, tendering, or canceling the transaction.
-
Guest Check Transactions
A guest check transaction is a sales transaction created using a Begin Check key or by service totaling a fast transaction. The Begin Check key or other configuration may require certain information, such as entering a table number or the number of guests when beginning the check. Check numbers are automatically assigned to transactions by default. The operator can assign check numbers if desired.
Guest checks are commonly used in table service restaurants, though they may be used in other operations as well. An operator may access a guest check at a workstation as many times as needed to service the guest. A service round occurs each time the check is accessed at the workstation. The first service round may be used to order drinks and appetizers. The operator may access the check a second time to order the entrees, and a third time to order dessert. When the check is paid in full, it is closed and no further service rounds may occur unless the check is reopened.
Guest check transactions may print a guest check, which is a printed record of the transaction.
-
Fast Transactions
A fast transaction is a sales transaction consisting of a single service round that ends with the sale being tendered. An operator starts a fast transaction by selecting a menu item key or scanning an item. No Begin Check key is used. When the first menu item is ordered, a guest check number is automatically assigned. A fast transaction ends when the transaction is paid in full. Alternately, a fast transaction may be converted to a guest check transaction using a Service Total key.
Fast transactions are often used by bartenders or cashiers in quick service restaurants. They may be restricted for use by specific operators in specific revenue centers.
Fast transactions may print a customer receipt when the transaction is paid in full, or if the guest asks for a receipt on demand once the transaction ends.
Non-sales Transactions
-
Media Loan
-
Media Pickup
-
Direct Tips
-
Indirect Tips
-
Cash Management Transactions
These transactions may generate a validation receipt to document the transaction. Most non-sales transactions post to the journal for auditing purposes.
- Check Numbers
- Headers and Trailers
- Service Total
- Pickup Next Check Functions
- Configuring the Purge Order Threshold for Open Checks
- Configuring Zero-Payment Transactions
- Configuring Fast Transactions
- Full Seat Checks
- Splitting Off an Item
- Adding the Assign Opera Account Button
- Conversational Ordering
- Autofire
- Refire
- Suspend and Resume
- Follow Me
- Order Handling on Open Checks
- Team Service
- Allowing Employees to Edit Guest Check ID on Open Check
- Closed Guest Check Operations
- Allowing Employees to Manually Replay Checks Through the Workstation
- Check Add/Transfer
- Seat Filtering and Memo Checks