Aloha POS Enhancement Release v6.4

Transcription

POS Enhancement
Release v6.4
Last Modified: June 1, 2009
Table of Contents
The Purpose of This Document........................................................................................... 3
List of Enhancements by Product....................................................................................... 7
Printing Auto-Calculated Suggested Gratuities .............................................................. 11
Auditing Petty Cash Transactions ................................................................................... 16
Reporting Quantity of Comps, Promos, Non-Cash Payments on BOH Sales Report . 17
Enhancing the Aloha COM Interface for v6.4 .................................................................. 18
Supporting Performance Measures Over Dates ............................................................. 19
Printing BOH Audit Report in Landscape ........................................................................ 21
Limiting the Binaries Synchronized Between the File Server and the Terminal ......... 22
Exporting the BOH Audit Report to a CSV File ............................................................... 26
Filtering BOH Audit Report by Check Number ............................................................... 27
Canceling an Authorization When in a ‘Stuck’ State ...................................................... 28
Supporting Manager Approval for Deleting Payments .................................................. 30
Removing Disable Masking in Grind Files Option .......................................................... 34
Masking Credit and Debit Card Numbers on BOH Audit Report ................................... 35
Allowing Fractional Guest Count Weights ...................................................................... 37
Reporting Multi-Level Modifiers in Grind Files ............................................................... 40
Supporting Enhanced Breaks Functionality ................................................................... 41
Supporting Visual Indicators with Fingerprint Scanner ................................................. 43
Enhancing the Create Diagnostic File Utility for v6.4...................................................... 44
Disallowing Repeat with Weighed Items ......................................................................... 47
Adding Reason Code and Revenue Center to Chit File ................................................. 48
Suppressing Voucher Printing When Under Required Ceilings ................................... 49
Installing Service for MenuLink COM Changes .............................................................. 53
Using Common Terminology Between Aloha Manager and MenuLink ........................ 56
Removing Fastech as an Available PMS Type ................................................................ 59
Suppressing Cardholder Name on Credit Card Vouchers ............................................. 60
Enhancing the Create Diagnostic File Utility .................................................................. 62
Updating Aloha Fingerprint Scanner Software ............................................................... 63
Expanding Debugging Capabilities in Aloha Manager ................................................... 64
Supporting FACTA Requirements for US Upgrades ...................................................... 66
Suppressing Pipe Characters on Customer Survey ....................................................... 67
Encrypting Sensitive Information in Debouts with Debug FOH COM ........................... 68
Adding the Time Items Appear on the Guest Check Window in GndItem.dbf ............. 69
Supporting Radiant SRP-350 Series Printer .................................................................... 70
Page 1
Printing Two Lines Per Item on Guest Check ................................................................. 71
Assigning an eFrequency Customer by Barcode Scan ................................................. 73
Alternating Chit Names on a Video Screen for Dual Languages .................................. 75
Displaying Totals on FOH Flash Report .......................................................................... 78
Supporting Radiant MSR Interface ................................................................................... 79
Interfacing with ETT Tavern Tracker Software ................................................................ 82
Supporting Recipes in QuickService ............................................................................... 87
Supporting FOH Quick Lookup for Promotions ............................................................. 88
Printing Guest Count on Chits in QuickService ............................................................. 90
Temporarily Capturing Card Data Using Automatic Detection ..................................... 92
Enhancing QS Quick Combo Functionality and Design ................................................ 99
Requiring Manager Approval for Cash Drops ............................................................... 108
Reprinting a Credit Card Voucher .................................................................................. 111
Including Modifier Counts with Quantity-Priced Items ................................................ 114
Recalling the Oldest Open Check in the Queue ............................................................ 117
Refunding a Check with One Touch .............................................................................. 118
Supporting Deferred Modifiers ....................................................................................... 121
Displaying Upsell Prices on System-Generated Panels .............................................. 126
Making Beep Settings Available in QuickService ......................................................... 127
Supporting Included Modifiers ....................................................................................... 128
Displaying Modifier Code Bitmaps on Modifier Buttons .............................................. 132
Supporting Tipshare Distribution ................................................................................... 137
Applying a Payment to Amount Due Before Gratuity ................................................... 139
Rerouting Video Group by Revenue Center .................................................................. 143
Enhancing Gratuity on Sales .......................................................................................... 145
Requiring Guests to Pay Inclusive Taxes on Comps and Promotions ....................... 149
Customizing Submenus in TableService ....................................................................... 155
Supporting Smart Item and Smart Select in TableService ........................................... 162
Performing Petty Cash Transaction Using a Public Cash Drawer .............................. 169
Providing Access to Reroute Video Groups When Using QSR Video ........................ 173
Copyright ©2009, Radiant Systems, Inc. The information contained in this publication is confidential and
proprietary. No part of this document may be reproduced, disclosed to others, transmitted, stored in a
retrieval system, or translated into any language, in any form, by any means, without written permission of
Radiant Systems, Inc.
Radiant Systems, Inc. is not responsible for any technical inaccuracies or typographical errors contained in
this publication. Changes are periodically made to the information herein; these changes will be incorporated in new editions of this publication. Any reference to gender in this document is not meant to be discriminatory. The software described in this document is provided under a license agreement. The software
may be used or copied only in accordance with the terms of that agreement.
© Radiant Systems, Inc., 2009 All Rights Reserved. ALOHA® is a U.S. Registered Trademark of Radiant
Systems, Inc. MenuLink® is a U.S. Registered Trademark of Radiant Systems, Inc.
Page 2
The Purpose of This Document
This document contains instructions on how to set up and use the enhancements implemented in the POS
v6.4 enhancement release. In some instances, we combine features together to better explain the new
enhancements. When applicable, we include a scenario, how to configure the feature in the Back-of-House
(BOH), how to use the feature in the Front-of-House (FOH), and references to other materials to fully
implement the feature. This document is not intended to fully explain a particular function or other options
available or surrounding the function. For your convenience, the material for each enhancement begins on
a new page, so you can properly remove and distribute the material to the necessary recipients. This document does not guarantee the options are in the same location, nor that the functionality remains the same
due to enhancements implemented in future versions of the affected products.
What do I need to know before installing v6.4?
When you begin the standard installation process, it first performs checks on the operating system of the
BOH file server to determine if the following two conditions are true:
•
•
128-bit encryption is installed.
DCOM is installed, active, and its version is v1.3 or higher.
By using Microsoft® Windows© 2000 or later, the operating system satisfies these prerequisites, if all service packs and security patches are up to date. Installing Internet Explorer v6.0, normally installed as part
of the operating system, satisfies the 128-bit encryption prerequisite, as this installation updates the native
encryption libraries.
Although SetupPOS.exe for v6.x verifies the operating system of the BOH file server, it does not check the
operating system on your terminals. All computers on the Aloha network must use a supported operating
system to support this version of Aloha. If any of your FOH terminals use older operating systems, you
must upgrade them, in accordance with the list provided later in this section.
When you install Aloha v6.x from a CD, SetupPOS.exe installs Windows Installer v3.1, and
Vcredist_x86.exe as part of the installation process. If you perform a manual upgrade, however, you must
obtain and install these two components separately before you begin.
•
Windows Installer v3.1 — This installation upgrades the Windows Installer currently used by
SetupPOS.exe to install Aloha. Other installation programs also make use of the Windows
Installer. Obtain this installation file from Microsoft or Radiant Systems prior to attempting the
upgrade. Copy the installation file to a staging directory on the Aloha BOH file server, and install
it from that location.
•
Vcredist_x86.exe — This program file installs runtime components of Visual C++ libraries to
enable programs developed with Visual C++ to run, on systems that do not have Visual C++
installed. Obtain this file from Radiant Systems prior to attempting the upgrade. Copy the file to a
staging directory on the Aloha BOH file server, and run it from that location.
POS Enhancement Release v6.4
Page 3
What operating systems does this version of Aloha support?
Radiant Systems is maximizing its efforts to bring products to the market that leverage the latest in product
architecture, and maximize reliability in meeting customer needs. The Aloha BOH file server and all terminals must have one of the following operating systems installed, prior to installing Aloha QuickService or
TableService:
•
•
•
Windows 2000, Service Pack 3
Windows XP, Service Pack 2
Windows Server, 2003
If you attempt to install Aloha v6.4 or higher on a computer running an unsupported operating system, or if Windows Installer v3.1 is not installed, the Aloha
installation fails with no warning or error message. The installation process simply fails to start.
Windows XP Embedded, as provided as part of the original build on Radiant terminals, satisfies operating
system requirements. In rare cases, you may need to obtain an updated image from Radiant Systems, Inc.,
for a given terminal using this operating system.
Controlling Access to Aloha Manager and Aloha EDC
As security requirements intensify with regard to protecting payment card data, Radiant Systems, Inc. is
enhancing security for all Aloha products. Beginning with Aloha v6.4, we disabled the Alt+X method of
accessing Aloha Manager for Quick Service and Table Service, and Aloha EDC. You must access these
applications through the use of a unique user name and complex, expiring password. This makes PCI DSS
compliance easier at the site level, as requirements become ever more restrictive.
Our recommendation is to control access to Aloha Manager and Aloha EDC using Back Office Security
Levels.
•
•
Create a new Back Office Security Level, with access to functions, reports, and other activities
appropriate at the site level.
Assign this security level to specific, trusted personnel at the site level, and ensure that these
employees have unique user names and complex, expiring passwords. Employees assigned to this
security level can give permission to other employees to use new features that become available in
Aloha, beginning with v6.4.
Aloha Command Center is an excellent alternative to using Alt+X. Employing multi-factored
credentials along with enhanced logging, you can once again launch Aloha Manager and obtain
the same level of access the Alt+X functionality provided.
Page 4
Disabling Masking in Grind Files
Beginning with Aloha v6.4, we have completely removed the ‘Disable Masking in Grind File’ setting from
the Aloha Manager interface, in Aloha QuickService and TableService, as part of making the Aloha system
PCI compliant with PCI DSS. This setting is located in Maintenance > Payments > Tenders > Type tab.
You must examine each credit card and debit card tender record, and clear this setting, if currently enabled,
prior to the upgrade. If you are unable to make these changes prior to upgrading to v6.4 or higher, you
must obtain help from your Radiant representative to edit the payment card tenders and clear the ‘Disable
Masking in Grind File’ setting, now removed from the Aloha Manager user interface.
Disabling Expiration Date Printing
One important security change that occurs ‘behind the scenes’ as part of the v6.4 installation (or higher), is
that all settings relevant to printing the payment card expiration date automatically change to prevent printing this value in any location in the restaurant. This modification is in response to the requirements outlined in the Fair and Accurate Credit Transactions Act (FACTA). After you upgrade to Aloha v6.4 or
higher, we recommend you verify that Aloha does not print this information for all payment card types,
when processed.
Do I need to enable Remote File Storage?
After verifying your operating system meets all prerequisites, SetupPOS.exe asks if you want to enable
Remote File Storage (RFS), a new, more secure method of communicating data between the Front-ofHouse and Back-of-House. The installation process displays a message, at the appropriate time, asking if
you want to enable the RFS feature during installation. We recommend you do not enable RFS upon initial
installation, unless your Aloha network has already been running RFS, and you are reinstalling Aloha on
your BOH file server. After a successful installation, you can enable RFS in Aloha Manager by selecting
Maintenance > Store Settings > Security group > RFS tab. Using RFS is completely optional, unless you
are using more than nine terminals. You can make RFS active during the installation process, or you can
activate it any time after installation. SetupPOS.exe installs all files necessary for supporting RFS, including entries in the Windows Registry, on each computer in the Aloha network.
Refer to the ‘Installation for Aloha v6.x’ document and the Remote File Storage (RFS) Feature
Focus Guide for more information about installing Aloha 6.4, and configuring the Aloha system
to use RFS.
EDC Version Independence
With a stronger industry focus on payment application security, several of the larger card brands have created new specifications for communications (authorization and settlement) for payment applications. Since
the changes are security driven, the processors and banks involved have set mandatory deadlines for compliance with the new specifications.
Page 5
Radiant Systems has introduced a ‘version independent’ Aloha EDC program, separate from the POS
products. Beginning with v6.4.0, Aloha EDC v6.4 is releasable and compatible with Aloha POS v5.3.15,
and higher, to eliminate the need for full POS upgrades to comply with these new card brand or processor
requirements.
You must upgrade your HASP key to Aloha v6.4 to run Aloha EDC v6.4. This change in license
status does not require you to upgrade to Aloha v6.4. If you are running an earlier version of
Aloha, you can still run Aloha EDC v6.4. For example, with the proper license, you can run
Aloha EDC v6.4 with Aloha POS v5.3, or v6.1. Please make the necessary arrangements to
upgrade all site keys prior to upgrading EDC.
Refer to the v6.4 EDC Enhancement Release document for information on the EDC enhancements in v6.4.
Page 6
List of Enhancements by Product
Version
RFC Number Description
QuickService and TableService Enhancements
POS v6.4
RFC 02477
“Printing Auto-Calculated Suggested Gratuities” on page 11
POS v6.4
RFC 09867
“Auditing Petty Cash Transactions” on page 16
POS v6.4
RFC 11977
POS v6.4 +
RFC 21270
RFC 57126
RFC 61670
RFC 61701
RFC 65003
RFC 35581
RFC 65904
RFC 63937
RFC 24988
“Reporting Quantity of Comps, Promos, Non-Cash Payments on BOH
Sales Report” on page 1-17
“Enhancing the Aloha COM Interface for v6.4” on page 18
POS v6.4
“Supporting Performance Measures Over Dates” on page 19
POS v6.2
RFC 28268*
POS v6.4
POS v6.2.19 RFC 28656*
POS v6.4.9
POS v6.4
RFC 29582
“Printing BOH Audit Report in Landscape” on page 21
POS v6.4
RFC 29789
“Filtering BOH Audit Report by Check Number” on page 27
POS v6.4.7
RFC 30459
“Canceling an Authorization When in a ‘Stuck’ State” on page 28
POS v6.4
RFC 32084
“Supporting Manager Approval for Deleting Payments” on page 30
POS v6.4
RFC 43735
“Removing Disable Masking in Grind Files Option” on page 34
POS v6.4
RFC 43736
“Masking Credit and Debit Card Numbers on BOH Audit Report” on
page 35
“Allowing Fractional Guest Count Weights” on page 37
POS v6.2.17 RFC 46907*
POS v6.4.7 RFC 67013*
POS v6.5.1
POS v6.4
RFC 48191
“Limiting the Binaries Synchronized Between the File Server and the Terminal” on page 22
“Exporting the BOH Audit Report to a CSV File” on page 26
“Reporting Multi-Level Modifiers in Grind Files” on page 40
POS v6.4
RFC 48982
“Supporting Enhanced Breaks Functionality” on page 41
POS v6.4
RFC 53597
“Supporting Visual Indicators with Fingerprint Scanner” on page 43
Page 7
Version
POS v6.1
POS v6.2
POS v6.4
RFC 56063*
RFC 57087
RFC 57318
RFC 57322*
RFC 57615
RFC 58048
RFC 61886
RFC 69057
POS v6.2.11 RFC 56747*
POS v6.4.1
POS v6.4
RFC 56988
RFC 53689
POS v6.4
RFC 57151
“Enhancing the Create Diagnostic File Utility for v6.4” on page 44
“Disallowing Repeat with Weighed Items” on page 47
“Adding Reason Code and Revenue Center to Chit File” on page 48
“Suppressing Voucher Printing When Under Required Ceilings” on
page 49
“Installing Service for MenuLink COM Changes” on page 53
POS v6.4
RFC 57341
POS v6.4
RFC 57639
POS v6.2
POS v6.4
POS v6.2.3
POSv6.4
POS v6.2
RFC 58548*
“Using Common Terminology Between Aloha Manager and MenuLink” on
page 56
“Removing Fastech as an Available PMS Type” on page 59
RFC 58579
“Suppressing Cardholder Name on Credit Card Vouchers” on page 60
RFC 59137*
RFC 59217
RFC 59262
RFC 59633
RFC 59909
RFC 60288
RFC 60289
RFC 60290
RFC 60819*
“Enhancing the Create Diagnostic File Utility” on page 62
POS v6.4
POS v6.4
POS v6.2.8
POS v6.4
POS v6.1.15 RFC 61041*
POS v6.2.8
POS v6.4.0
POS v6.4
RFC 61421
POS v6.4
RFC 61555
POS v6.2.11 RFC 63288*
POS v6.4.1
POS v6.2.9 RFC 63351*
POS v6.4.1
POS v6.4.2 RFC 63871*
“Updating Aloha Fingerprint Scanner Software” on page 63
“Expanding Debugging Capabilities in Aloha Manager” on page 64
“Supporting FACTA Requirements for US Upgrades” on page 66
“Suppressing Pipe Characters on Customer Survey” on page 67
“Encrypting Sensitive Information in Debouts with Debug FOH COM” on
page 68
“Adding the Time Items Appear on the Guest Check Window in
GndItem.dbf” on page 69
“Supporting Radiant SRP-350 Series Printer” on page 70
“Assigning an eFrequency Customer by Barcode Scan” on page 73
POS v6.4.2
RFC 66310*
“Alternating Chit Names on a Video Screen for Dual Languages” on
page 75
“Displaying Totals on FOH Flash Report” on page 78
POS v6.4.9
RFC 68491
“Supporting Radiant MSR Interface” on page 79
Page 8
Version
POS v6.4.9
RFC 69767
“Interfacing with ETT Tavern Tracker Software” on page 82
QuickService Only Enhancements
POS v6.4
RFC 05184
“Supporting Recipes in QuickService” on page 87
POS v6.4
RFC 28789
“Supporting FOH Quick Lookup for Promotions” on page 88
POS v6.4
RFC 40664
“Printing Guest Count on Chits in QuickService” on page 90
POS v6.4.4
RFC 52370
“Temporarily Capturing Card Data Using Automatic Detection” on page 92
POS v6.4
RFC 52639
“Enhancing QS Quick Combo Functionality and Design” on page 99
POS v6.4
RFC 54586
“Requiring Manager Approval for Cash Drops” on page 108
POS v6.4.7
RFC 57208
“Reprinting a Credit Card Voucher” on page 111
POS v6.4
RFC 61162
“Including Modifier Counts with Quantity-Priced Items” on page 114
POS v6.1.19 RFC 64053
POS v6.2.12
POS v6.4.2
POS v6.4.6 RFC 66462
“Recalling the Oldest Open Check in the Queue” on page 117
POS v6.4.9
RFC 67389
“Supporting Deferred Modifiers” on page 121
POS v6.4.9
RFC 67407
“Displaying Upsell Prices on System-Generated Panels” on page 126
POS v6.4.8
RFC 69289*
“Making Beep Settings Available in QuickService” on page 127
POS v6.4.9
RFC 69392
RFC 69462
RFC 69459
“Supporting Included Modifiers” on page 128
POS v6.4.9
“Refunding a Check with One Touch” on page 118
“Displaying Modifier Code Bitmaps on Modifier Buttons” on page 132
TableService Only Enhancements
POS v6.4
RFC 14404
“Supporting Tipshare Distribution” on page 137
POS v6.4
RFC 24925
“Applying a Payment to Amount Due Before Gratuity” on page 139
POS v6.4.8
RFC 48748*
“Rerouting Video Group by Revenue Center” on page 143
POS v6.4
RFC 51197
“Enhancing Gratuity on Sales” on page 145
Page 9
Version
POS v6.4
RFC 51212
POS v6.4
RFC 54070
“Requiring Guests to Pay Inclusive Taxes on Comps and Promotions” on
page 149
“Customizing Submenus in TableService” on page 155
“Supporting Smart Item and Smart Select in TableService” on page 162
POS v6.4
RFC 57381
“Performing Petty Cash Transaction Using a Public Cash Drawer” on
page 169
POS v6.4
RFC 69924
“Providing Access to Reroute Video Groups When Using QSR Video” on
page 173
* Implemented in versions other than POS v6.4.
Page 10
Printing Auto-Calculated Suggested Gratuities
Version
RFC Number
Products
Audience
POS v6.4
RFC 02477
Aloha QuickService, Aloha TableService
Configuration Technician
End User
In the restaurant industry, the guest is often confronted with the dilemma of not knowing the appropriate
amount of gratuity to leave for the server. They are either not proficient in mathematics or unaware of what
is sufficient for good service. In v6.4 and higher, you can configure the system to automatically calculate
and print suggested gratuity amounts on the bottom of the guest check for the guest to use as a guideline
when leaving a gratuity for the server.
SCENARIO: The wait staff repeatedly claims they are under-tipped by the clientele so the restaurant configures the system to print auto-calculated suggested gratuity amounts on the guest check. Upon delivery
for payment, the guest notices the suggested gratuity amounts on the guest check. In doing so, this brings
awareness to the clientele and the wait staff receives a more accurate gratuity percentage.
Configuring Auto-Calculated Suggested Gratuities
Configuring auto-calculated suggested gratuities to print on the guest check requires you to create a guest
check message, using supported variables, and then set up an event to print the message on the guest check.
Configuring a Guest Check Message with Variables
To print auto-calculated suggested gratuities on the guest check, you must configure a customized guest
check message. You can use formulas that include variables, enclosed with lesser and greater than symbols, to insert system-generated information and calculated values. The following table lists the supported
variables you can use in guest check message formulas.
Variable
Description
$TIPSALE
#S
$S
#Snnnn
Tippable sales for the check.
Total count of all sales categories for the check.
Total amount of all sales categories for the check.
Total count of sales category nnnn for the check where nnnn is the ID number of the
category.
Total amount of sales category nnnn for the check where nnnn is the ID number of the
category.
Total count of guests for the check.
Total count of order mode charges for order mode nnnn for the check where nnnn is
the ID number of the order mode.
Total amount of order mode charges for order mode nnnn for the check where nnnn is
the ID number of the order mode.
Total count of entrees sold for the check.
Date of business.
The first name of the employee.
The last name of the employee.
$Snnnn
#GUESTS
#OMCnnnn
$OMCnnnn
#ENTREES
DOB
FIRSTNAME
LASTNAME
Page 11
Variable
Description
NICKNAME
FILL(x)
LEFT
RIGHT
( ), +, -, *, /
The nickname of the employee.
Inserts a line composed entirely of a single character, designated in parenthesis.
Left justify. By default, the printed text is centered.
Right justify. By default, the printed text is centered.
Standard algebraic operators. The * and / symbols have a higher precedence than +
and -.
Constant numbers, such as ‘1, 1.5, 2, 2.5, 3, etc’
Constant
The supported variables adhere to the following rules:
Variable Rules
All variables use the following format: <VARIABLE>. For example: <NICKNAME> inserts the nickname of
the employee. Any text outside of the less than and greater than symbols prints on the guest check as
typed.
All variables containing formulas use the following format: <VAL(width:formula)>.
• Width specifies the total number of digits to reserve for a value, not including a decimal point. The
width cannot be zero. If the width is smaller than the number of characters of the value, the system
prints the value. For example: <VAL(2:LASTNAME)> inserts the last name even if the last name is
more than two digits. If the width is larger than the number of characters of the value, the system prints
the value padded with blanks. For example, if you type <VAL(10:LASTNAME)> and the last name is
Smith, the system prints five empty spaces and then SMITH.
• Formula specifies the numeric value for the equation. If the formula contains a $ symbol, the value displays as currency, as defined for the system. If the formula contains a # symbol, the value displays as
a whole number with no decimals. If the formula contains any other character or includes an unsupported variable, the variable prints on the guest check as typed. For example: if you type
<VAL(5:$TIPSALE*0.20)> the system inserts the suggested 20% gratuity amount on the tippable
sales for the check, using a five digit format.
To configure the suggested gratuity message to print on guest checks:
1.
2.
3.
4.
Select Maintenance > Messages > Guest Check Messages.
Type an unused number in the ‘ID’ drop-down list and press Enter.
Type a name for the message, such as ‘Suggested Tip.’
Type a title for the message to appear at the top of the guest check, if desired. Include variables to
allow the system to automatically calculate values. Remember the title appears at the very first of
the guest check so you may not want to fill in the title. See the Variable table for the supported
variables you can use.
Page 12
5. Type the message to appear at the bottom of the check to indicate the suggested tip. Include variables to allow the system to automatically calculate values. See the Variable table for the supported
variables you can use.
Figure 1 Guest Check Message for Suggested Gratuity
6. Click Save. If any completed text line contains more than 30 characters, a warning appears. Some
lines may require long formulas; however, the output only prints a portion of the characters. Any
printed text over 30 characters might not print on the guest check as desired, depending on the
printer you are using.
Figure 2 30 Character Warning for Guest Check Text Lines
7. Click OK to continue.
8. Exit the Guest Check Messages function.
Using existing functionality, you can also configure your suggested gratuity message to print on all credit
card vouchers.
To configure the suggested gratuity message to print on credit card vouchers:
1.
2.
3.
4.
Select Maintenance > Store Settings > Credit Card group > Voucher Printing 1 tab.
Select Print Check Message on Vouchers.
Select the message to print from the ‘Message’ drop-down list.
Click Save and exit the Store Settings function.
Page 13
Activating a Suggested Gratuity Message
The system defaults to printing the guest check message defined with the lowest ID. Most likely, this message is already in use for a salutation message. If your suggested gratuity message is not the lowest ID, you
must configure the existing Set Guest Chk Msg event in System Events to activate and use the message.
When you perform a refund, the system assumes a ‘refund’ mode and enters items in negative
amounts, including the auto-calculated suggested gratuity. To avoid this, we recommend using
the existing Set Footer Message by Terminal event to activate your suggested gratuity message at
each terminal, except for one terminal that you designate as where you perform refunds.
To configure an event for printing the suggested gratuity message:
1.
2.
3.
4.
5.
6.
7.
Select Maintenance > System > Events. The System Events function tab appears.
Click Add Event. The Event Time & Type dialog box appears.
Select Set Guest Chk Msg from the ‘Event Type’ drop-down list.
Select Daily, or a time frequency of your choice.
Type the time the event will begin. To keep the event activated all day, leave the value at 00:00.
Click OK. The Set Guest Chk Msg dialog box appears.
Select the guest check message you created for suggested gratuity from the ‘ID’ drop-down list.
The message appears as a preview.
8. Click OK. The event is added as an event task.
9. Exit the System Events function.
Page 14
Using Auto-Calculated Suggested Gratuities
When the guest check or the credit card voucher prints, the system prints the message at the bottom of the
appropriate slip.
Figure 3 Guest Check with Auto-Calculated Suggested Gratuities
Page 15
Auditing Petty Cash Transactions
Auditing Petty Cash Transactions
Version
RFC Number
Products
Audience
POS v6.4
RFC 09867
Store Managers
Petty cash accounts allow you to define a tracking system for such things as paid in and paid out transactions. In v6.4, you can now run an audit report on these transactions.
To audit petty cash transactions:
1. Select Reports > Audits. The Select Date dialog box appears.
2. Select a date and click OK. The Select Transactions to Audit dialog box appears.
Figure 4 Select Transactions to Audit Dialog Box
3. Select Petty Cash.
Petty Cash — Reports transactions related to petty cash accounts.
4. Click View to view the report or click Print to print the report.
On the BOH Audit report, petty cash transactions report as follows:
Time
11:18
Page 16
Type
PETTY ACCOUNT
Transaction
Petty Account: 00001 Starting bank 20.00 (-)
Emp: 200 FRANCES Manager Emp: 101 APRIL
Reporting Quantity of Comps, Promos, Non-Cash Pay-
Reporting Quantity of Comps, Promos, Non-Cash
Payments on BOH Sales Report
Version
RFC Number
Products
Audience
POS v6.4
RFC 11977
Store Managers
The Aloha system now reports the quantity of applied comps, promotions, and non-cash payments, per
type, on the BOH Sales Summary report. This aides managers in obtaining a total count for reporting and
validation of slips received from employees. The quantity does not display on the BOH Sales Weekly
report.
Quantity of applied
comps, promotions, and non-cash
payments.
Figure 5 BOH Sales Summary Report Example
Page 17
Enhancing the Aloha COM Interface for v6.4
Enhancing the Aloha COM Interface for v6.4
Version
RFC Number
Products
Audience
POS v6.4
POS v6.4.1
POS v6.4.1
POS v6.4.1
POS v6.4.5
POS v6.4.7
RFC 21270
RFC 57126
RFC 61670
RFC 61701
RFC 65003
RFC 35581
Aloha QuickService
Aloha QuickService, Aloha TableService,
PMS
POS v6.4.7 RFC 65904
RFC 63937
We made the following enhancements to the Aloha COM Interface in v6.4. There is no configuration
required.
•
•
•
•
•
•
•
RFC 21270 - This enhancement allows QuickService and TableService users to use ‘Get Check’
and TableService users to use the ‘Team Get Check’ functionality through the Aloha COM interface.
RFC 35581 - This enhancement allows QuickSerivce and TableService users to use all BOH functions located on the PMS menu in EDC through the Aloha COM interface. These functions include
Post Charge, Inquire, Adjust Charge, Delete Charge, Debug Log, Charge Report, and Preauth.
RFC 57126 - This enhancement allows QuickService users to use the ‘Recall Check’ functionality
through the Aloha COM interface.
RFC 61701 - This enhancement allows QuickService and TableService users to processe debit
card transactions through the Aloha COM interface.
RFC 61670 - This enhancement allows QuickService and TableService users to use the ‘Split
Check’ functionality through the Aloha COM interface.
RFC 63937, 65904 - These enhancements allow QuickService and TableService users to use the
‘gift card balance inquiry’ and ‘card activation’ functions when using the Aloha COM interface.
RFC 65003 - This enhancement allows QuickService and TableService users to pass the seat name
through the Aloha COM interface. If no seat name is given, the system defaults to the label of
‘Seat.’
Page 18
Supporting Performance Measures Over Dates
Version
RFC Number
Products
Audience
POS v6.4
RFC 24988
When you view the Performance Measures report, the report is broken down by shift and does not have the
ability to generate a single performance number over a range of dates. You must add up all the values for
each shift, then divide by the number of shifts to achieve a performance measure for an employee. Starting
with v6.4, the Performance Measure report can now report a single performance measure for an employee
across a range of dates. This useful tool enables managers to evaluate their employees during a specific
time period for a more precise performance measurement.
To run a performance measure report over a range of dates:
1. Select Reports > Sales > Performance Measure. The Employee Performance Measure dialog
box appears.
2. Click Settings. The Performance Measures Report Settings dialog box appears.
Figure 6 Performance Measures Report Settings Dialog Box
3. Select either Employee or Performance Measure from the ‘Group By’ group box.
4. Select Print Detail Lines, if desired.
Print Detail Lines — Prints individual shift information in addition to totals.
5. Select Sort Detail Lines, if desired.
Sort Detail Lines — Prints individual shift information, sorted by date. Required Option: You
must select Print Detail Lines to enable this option.
Page 19
6. Select Print Subtotals, if desired.
Print Subtotals — Prints a subtotal for each performance measure.
7. Select a date, or a range of dates to report.
Figure 7 Emp Performance Measures Report with Print Subtotals Selected
Page 20
Printing BOH Audit Report in Landscape
Printing BOH Audit Report in Landscape
Version
RFC Number
Products
Audience
POS v6.2
RFC 28268
Configuration Technician,
Store Managers
For instances when a horizontal view is more appropriate than a vertical view, you can now print the BOH
Audit Report in landscape.
To print the BOH Audit Report in landscape format:
1. Select Reports > Audit. The Select Transactions to Audit dialog box appears:
Figure 8 Labor - Performance Measures Function
2. Select Print Landscape.
Print Landscape — Prints the report in landscape format.
Page 21
Limiting the Binaries Synchronized Between the File Server and the Terminal
Limiting the Binaries Synchronized Between the
File Server and the Terminal
Version
RFC Number
POS v6.2.19 RFC 28656
POS v6.4.9
Products
Audience
Store Managers
In order to better support POS terminals with limited drive space, the Aloha POS system versions 6.2.21
(and higher), 6.4.11 (and higher), and 6.5.3 (and higher) now support the ability to limit the contents of the
Bin folder that are synchronized to the Front-of-House (FOH) terminals. Whereas the Aloha POS previously synchronized the entire contents of the Aloha Bin folder on the Back-of-House (BOH) files server to
the Bin folder on the FOH terminal, the POS will now only synchronize the files that are specifically
required if you enable this feature. This feature is only enabled if both the Iberrq.dll and the Syncinclusionlist.cfg reside in the FOH terminal's Bin folder. If either file is missing, then the FOH terminal will
continue to synchronize all of the files in the Bin folder.
The Syncexclusionlist.cfg from previous versions is ignored and unused. You can delete it.
Radiant Systems uses the Iberrq.dll to define files that are required for core FOH functionality. The Aloha
POS system will include updated versions of the file with each release in order to include any new required
files. If the Iberrq.dll does not exist in the Bin folder on the file server along with the Syncinclusionlist.cfg, then the FOH will synchronize the entire contents of the Bin folder.
If the site's FOH terminals are utilizing files in their existing Bin folder that are not already included in the
Iberrq.dll, then you can use the Syncinclusionlist.cfg to define these files for synchronization. The Syncinclusionlist.cfg is not included with the Aloha POS software, so you must manually add it to the file server's
Bin folder in order to enable this feature.
If you are utilizing Bin files on the FOH terminals that are not included in the Iberrq.dll, then you
must add them to the Syncinclusionlist.cfg. Otherwise, Aloha will remove them from the Bin on
the FOH terminals.
In summary, once you upgrade to one of the supported Aloha versions, the FOH will continue to synchronize files as before. However, if you supplement the Iberrq.dll (installed with the upgrade) with a Syncinclusionlist.cfg, then the FOH terminals will not synchronize any files that are not included in either the
Iberrq.dll or the Syncinclusionlist.cfg. It will also purge any existing files that were synchronized prior to
upgrading that are not included in either list.
Editing the Syncinclusionlist.cfg
The attached Syncinclusionlist.cfg already includes all of the known Aloha binary files that could be
required on the FOH terminals for various non-core features such as Aloha Command Center, Aloha Loyalty, Aloha Stored Value, QSR KDS, biometric devices, and add-on customer displays (for example, C500
Page 22
Limiting the Binaries Synchronized Between the File
and C1200). Each of the files is currently enabled (included in the sync), but you can disable the files
(exclude them from the sync) by placing a semi-colon (;) in front of the file name. For example, to include
DevInfo.dll and HbUtil.exe, but exclude FOHAdm.exe and HbPopup.dll, you would use the following:
•
•
•
•
DevInfo.dll
FOHAdm.exe
HbUtil.exe
HbPopup.dll
You can add new files by just creating a new line anywhere in the list and defining the file name.
Since the Syncinclusionlist.cfg is not included in Aloha upgrade packages, then you do not risk overwriting it when performing future upgrades.
Preparing to Implement this Feature
Prior to implementing this feature, you should prepare the site by determining if the FOH terminals require
any non-core binaries. If so, then you must prepare and provide a suitable Syncinclusionlist.cfg. Only
apply the Syncinclusionlist.cfg to the Bin folder after ensuring that you have accounted for all of the necessary files.
The current versions' Iberrq.dll includes the following files:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
AddGCTip.exe
AlohaExtEnc.dll
alohagl.dll
calcedit.ocx
calib.exe
CB5.DLL
cb532.dll
cbrfs.dll
cbrfs80.dll
ChkInfo.exe
codepages.csv
commsgst.dll
dbghelp.dll
Elocalw.cpl
Elocalw.exe
Elocalw.fts
Elocalw.gid
Elocalw.hlp
Fastech.dll
fohadm.exe
Page 23
Limiting the Binaries Synchronized Between the File Server and the Terminal
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Iber.exe
Iberadm.dll
iberps.dll
Iberqs.exe
iberqsps.dll
ibersql.dll
iberstr.dll
InterAct.dll
Interceptactibitylib.dll
interceptprinting.dll
Interop.ALOHAMGRLib.dll
InterPrt.dll
mplay.exe
mplay2.exe
PayRecon.exe
printer.dll
PrtInter.dll
qwerty.ocx
radacctl.lic
regasm.exe
Regsvr32.exe
rfsclt80.dll
rfsclt80s.dll
rfsclts.dll
rfssvr.exe
rfssvrps.dll
shlwapi.dll
Shw32.dll
timezondstadjust.exe
timezoneencryptionfix.exe
tzdstadj.exe
videomx.dll
Page 24
Limiting the Binaries Synchronized Between the File
In Aloha POS versions 6.2.19, 6.2.20, 6.4.9, 6.4.10, and 6.5.2, with the exception of binaries contained in
the Iberrql.dll that are absolutely required for the FOH to function, you can only select files to exclude
from the Bin folder synchronization between the file server and the FOH terminals by using the Syncexclusionlist.cfg. The Syncexclusionlist.cfg, which resides in the Bin folder of the file server (and thus, gets
propagated to the FOH terminals), uses a format of one file per line. For example,
•
•
•
file1.exe
file2.exe
file2.exe
Any files included in the list are not synchronized with the file server (to the FOH terminal) and they are
deleted from the FOH terminal (if found). The FOH will ignore the Syncexclusionlist.cfg and continue to
synchronize the entire Bin folder if the Iberrq.dll file does not exist in the Bin folder. The Syncexclusionlist.cfg is ignored and unused in Aloha POS versions 6.2.21 (and higher), 6.4.11 (and higher), and 6.5.3
(and higher), where it is replaced by the Syncinclusionlist.cfg.
Page 25
Exporting the BOH Audit Report to a CSV File
Exporting the BOH Audit Report to a CSV File
Version
RFC Number
Products
Audience
POS v6.2
RFC 29582
Store Managers
To make the BOH Audit report more portable and configurable, you can now export the report to a comma
separated value (CSV) file. This gives you the ability to search, sort, and filter data for a variety of uses
with common programs, such as MSExcel.
To export the BOH Audit Report to a CSV file:
1. Select Reports > Audit. The Select Transactions to Audit dialog box appears:
Figure 9 Labor - Performance Measures Function
2. Click Export. The Save As dialog box appears. The name of the file defaults to Audit.txt.
Figure 10 Save As Dialog Box
3. Change the location and file name, if desired.
4. Click Save.
Page 26
Filtering BOH Audit Report by Check Number
Filtering BOH Audit Report by Check Number
Version
RFC Number
Products
Audience
POS v6.4
RFC 29789
Store Managers
Previously, you could filter the BOH Audit report by employee or job code only. You can now filter the
report by the check number. This is useful when you are trying to solve an issue related to a specific check
number.
To filter the BOH Audit report by check number:
1. Select Reports > Audits. The Select Date dialog box appears.
2. Select a date to report and click OK. The Select Transactions to Audit dialog box appears.
Figure 11 Select Transactions to Audit Dialog Box Filtered by Check Number
3. Select Check Number.
Check Number — Filters the report by check number. When selected, the corresponding list box
populates with all checks for the selected day, in ascending order, and disables all inapplicable
options not related to the check. If you are using the check counter feature, the system does not list
the alternate perpetual counter that numerates the check number across all terminals and all business days whenever the Counter.bin file is present.
4. Select the checks for which you want to report or click Select All to report on all checks in the
list.
5. Select the type of transactions you want to include in the report from the available options in the
‘Payments’ and ‘Other’ group boxes. The options that do not pertain to the check number are disabled.
6. Click View to view the report, click Print to print the report or click Export to export the report to
a .csv file.
Page 27
Canceling an Authorization When in a ‘Stuck’ State
Canceling an Authorization When in a ‘Stuck’
State
Version
RFC Number
POS v6.4.7 RFC 30459
Products
Audience
Configuration Technicians,
Store Managers, End User
In the rare occasion when an authorization is sent to the processor during the time the restaurant loses internet connectivity, or due to a faulty network setup, the transaction drops into a permanently ‘stuck’ state
until the End-of-Day (EOD) runs. This scenario does not allow you to close the check; thereby, forcing the
employee to remain on the clock and having the manager edit their punch. The system now minimizes the
impact of this occurrence by waiting 10 minutes once the authorization is in a fixed state and you can then
close the check and the employee can check out in a more timely manner. There is no configuration needed
for this enhancement.
To cancel an authorization when in a ‘stuck’ state:
1. With the active check in the guest check window and you are ready to apply a credit card payment,
touch the applicable credit card button, such as Visa.
2. Slide the customer’s card across the magnetic stripe reader. The system sends an authorization
request to the processor while the restaurant loses internet connectivity. A message stating the payment is in an authorizing state and you cannot delete the payment until 10 minutes appears.
Figure 12
3. Touch inside the box to clear the message.
4. To accommodate the guest, perform any of the following solutions:
Slide the credit card across the magnetic stripe reader again to see if the system can connect.
Ask for another form of payment from the guest, such as cash or another credit card type and apply
the payment to the check.
Start a new check, re-enter the items into the system, and apply a payment.
Page 28
Canceling an Authorization When in a ‘Stuck’ State
5. After 10 minutes has expired, a manager, or an employee with access, can recall the check, select
the ‘stuck’ transaction from the guest check window, and touch Delete. The authorization
attempt is removed.
The chance of an authorization in a ‘stuck’ state completing is very rare as most processor have a
timeout restriction.
Page 29
Supporting Manager Approval for Deleting Payments
Supporting Manager Approval for Deleting
Payments
Version
RFC Number
Products
Audience
POS v6.4
RFC 32084
Configuration Technicians
In the Aloha POS system, an employee can delete a payment on a check as long as the check is not closed.
Many sites want to require manager approval of this ability since the majority of credit card issuers now
monitor ‘suspicious’ activity when repeated authorizations are made within a short time period, resulting
in the card being placed on hold. Furthermore, in the Aloha TableService product, the Delete button on the
FOH Close screen is in a location that could cause the employee to accidentally delete the payment, which
causes a problem when the guest is not available to re-apply the payment. With v6.4, you can control the
employees who can delete payments without manager approval through the access level to which they are
assigned.
Configuring Manager Approval for Deleting Payments
Preventing or allowing an employee to delete a payment from a check is controlled by the access level
under which the employee clocks in. You must select or clear ‘Delete Payments’ in Maintenance > Labor >
Access Levels > Financial tab. If cleared, a manager must approve the deletion of the payment.
When you upgrade to v6.4, the Access Levels function now has an additional Financial 2 tab and
several options were moved to this new tab.
To configure manager approval for deleting payments:
1. Select Maintenance > Labor > Access Levels > Financial tab.
Figure 13 Maintenance > Labor > Access Levels > Financial Tab
Page 30
2. Select Delete Payments.
Delete Payments — Allows all employees clocked in with this access level to delete a payment
from a check. If cleared, the manager approval screen appears when an employee without sufficient access tries to delete a payment.
3. Click Save and exit the Store Settings function.
Using Manager Approval for Deleting Payments
When an employee who does not have sufficient access tries to delete a payment from a check, the manager approval screen appears. If the employee has sufficient access, the system allows the deletion of the
payment.
To prompt for manager approval for deleting a payment:
1. Locate the Delete button on the Aloha TableService FOH Close screen or the Aloha QuickService
tender panel. See Figure 14 for QuickService and Figure 15 for TableService.
The Delete button
is configurable in
Aloha QuickService
Figure 14 QuickService FOH Close Panel
Page 31
Delete button
Figure 15 TableService FOH Close Screen
2. Touch Delete. The manager approval screen appears.
Figure 16 FOH Manager Approval Screen for Deleting Payments
Page 32
3. A manager enters their password using the numeric keypad, and touches OK. Touch Cancel to
cancel the deletion. If the employee fraudulently tries to enter a password, or the manager does not
have sufficient access or is not clocked in, an error message appears.
Figure 17 FOH Insufficient Access Level Message
Reporting the Deletion of Payments
You can perform an audit on the deletion of payments in the BOH Audit report. For each instance, the system records the time, the employee approving the deletion, the employee performing the deletion, the table
and check number, the payment type, and the amount of the transaction.
Figure 18 Sample BOH Audit Report with Payments Deletions
Page 33
Removing Disable Masking in Grind Files Option
Removing Disable Masking in Grind Files Option
Version
RFC Number
Products
Audience
POS v6.4
RFC 43735
Store Managers
Aloha v6.4 eliminates the option, ‘Disable Masking in Grind Files,’ in Maintenance > Payments > Tenders,
on the Type tab. Clearing this option is a very important part of PCI DSS payment card security compliance, as it prevents storing cardholder information in the grind files. If you have any tenders with this
option selected, you must clear it prior to the upgrade, as the user interface will no longer give you the ability to modify its status.
If you fail to clear this setting for any tender, prior to the upgrade, you must edit Tdr.dbf to restore masking
in the grind files. You must locate the NoMaskCard column, and change any ‘Y’ appearing in that column
to an ‘N.’
Before you upgrade to v6.4, we recommend you clear ‘Disable Masking in Grind
Files’ for all tenders. In the event that you have a tender with this option enabled
after upgrading, you must use DBConfig to edit Tdr.dbf and manually clear the
option, since the option is no longer available in Aloha Manager. Contact Radiant
Systems Technical Support for help with editing this file, if you are not familiar
with this procedure.
As an added security measure, an error appears, with the tender name and ID, each time you use the Verify.txt function, until your system is in compliance.
Figure 19 Verify.txt with Non-compliant Tender
Page 34
Masking Credit and Debit Card Numbers on BOH Audit
Masking Credit and Debit Card Numbers on BOH
Audit Report
Version
RFC Number
Products
Audience
POS v6.4
RFC 43736
Store Managers
To meet PCI DSS standards, mandated by new regulations in the industry, POS systems must secure all
credit and debit card information by encrypting or masking the credit card numbers when they are stored or
viewed within the system after the transaction occurs. In v6.4, the credit card information is now masked
when you access the BOH Audit report.
The BOH Audit report
shows only the last four
digits of all credit and
debit card numbers.
Figure 20 BOH Audit Report Sample
When you run the BOH Audit report, the system creates the Report.txt file in the Aloha/Tmp directory.
When you close the preview window, the system deletes the existence of Report.txt, to ensure that credit
and debit card information is not left behind to pose a security risk.
When you upgrade to v6.4, the BOH Audit report masks credit and debit card information, by
default, to ensure the system is PCI DSS compliant.
PCI DSS does allow specific personnel to access this information for support reasons. In situations when
you must obtain the credit or debit card number, we recommend you configure a BOH employee to have
access to this information. To do this, you must select Run for the ‘Display Credit / Debit Card Numbers
Page 35
Masking Credit and Debit Card Numbers on BOH Audit Report
option for the back office security level assigned to the employee. When creating back office security levels, the system allows you to use standard starting levels from which you can build upon a level. By
default, the system uses the following starting levels for the ‘Display Credit / Debit Card Numbers option:
Start Level
Run
Add
Edit
Delete
Minimum
Typical
Maximum
Cleared
Cleared
Selected
NA
NA
NA
NA
NA
NA
NA
NA
NA
Viewing and printing credit and debit card information is not in compliance with
data security standards. Configure this feature for only the appropriate personnel,
such as employees who must resolve disputes as part of their job.
To display credit and debit card numbers on the BOH Audit report:
1. Select Maintenance > Labor > BO Security Levels. The Back Office Security Levels function
appears.
Figure 21 Back Office Security Levels Function
2. Select the level from the ‘ID’ drop-down list.
3. Scroll down the list of functions and select Display Credit / Debit Card Numbers.
4. Select Run to allow access to credit and debit card numbers on the BOH Audit report.
OR
Clear Run to mask credit and debit card numbers on the BOH Audit report.
5. Click Save and exit the Back Office Security Levels function.
When you enable the BOH Audit report to display credit and debit card numbers, the system appends the
message, “<user> has displayed full card numbers from <DOB>” where user is the name of the employee
and DOB is the date of business, in Debout.txt.
Page 36
Allowing Fractional Guest Count Weights
Version
RFC Number
Products
Audience
v6.2.17
v6.4.7
v6.5.1
RFC 46907
RFC 67013
Store Manager
When you determine your guest count based on the number of items ordered from a specific category, such
as entrees, the system takes the weight you define for your items in the specified category into consideration. For example, if you give an item in the guest count category a weight of ‘2,’ the guest count
increases by two each time a guest orders the item. Prior to v6.2.13, you could define the weight of an item
using whole numbers only. Beginning with v6.2.13, you can define the weight for an item using a fractional value, such as 0.25. The fractional value rounds to the nearest whole number, and does not carry
over to a separate guest check.
SCENARIO: A restaurant enables the ‘Use Entrees for Guest Counts’ feature and includes large-sized
appetizers that guests sometimes order as a meal, such as Super Nachos, in the guest count category; however, each time a guest orders Super Nachos to share with the table, the guest count becomes over-inflated
because the weight for the Super Nachos item cannot be less than 1.0. To receive a more accurate guest
count, the restaurant assigns a fractional weight of 0.25 to Super Nachos. When a party orders two Super
Nachos, the total weight is 0.50, so the system rounds the guest count to one. When a second party orders
one Super Nachos, the total weight is 0.25, so the guest count does not increase. It is important to note that
the guest count for this scenario is based on one guest check for the party. If each guest orders Super
Nachos, but wants a separate check, the guest count does not increase.
Configuring Fractional Guest Count Weights
To configure fractional guest count weights, you must enable the system to count guests by items in a category, define an item with a guest count weight, and configure fractional values to appear on reports that
display guest counts.
To enable the system to count guests by items in a category:
1. Select Maintenance > Store Settings > Order Entry group > Guest Counts tab.
2. Select Use Entrees for Guest Counts.
Use Entrees for Guest Counts — Automatically calculates the guest count using the number of
items sold from the category selected in the ‘Category’ drop-down list. Each time you order an
item from the selected category, the guest count increases based on the weight entered for the item.
The system does not prompt for a guest count. Typically, this is used for entrees but you can use
any category of items to count guests, such as drinks. Related Options: 1) To define items with a
guest count weight, enter a whole or fractional value in the ‘Guest Count Weight’ text box in
Maintenance > Menu > Items > Item tab. 2) To display fractional values on reports that include
guest counts totals, select ‘Reports Use Fractional Guest Counts’ in Maintenance > Store Settings
> Order Entry group > Guest Counts tab.
Page 37
To define an item with a guest count weight:
1. Select Maintenance > Menu > Items > Item tab.
2. Select an item from the ‘Number’ drop-down list and press Enter.
3. Type a whole or fractional value in the ‘Guest Count Weight’ text box.
Guest Count Weight — Establishes the weight value of the item, with a default value of one,
when counting guests by category. For example, you can set the guest count weight of an item
named ‘Fajitas for Two’ so that it increases the guest count by two when a customer orders it. Similarly, you can set the guest count weight of an appetizer item named ‘Onion Petal’ to 0.25 so that
it increases the guest count only when it is ordered twice. The fractional values round to the nearest whole number, per guest check, and do not carry over to a separate check nor to the next table.
Required Options: This option works in conjunction with the ‘Use Entrees for Guest Counts’
option in Maintenance > Store Settings > Order Entry group > Guest Counts tab. Related Options:
To display fractional values on reports that include guest counts totals, select ‘Reports Use Fractional Guest Counts’ in Maintenance > Store Settings > Order Entry group > Guest Counts tab.
4. Click Save.
5. Repeat this procedure for each item for which the guest count should be a fractional weight.
6. Click Save and exit the Items function.
To configure reports to display fractional guest counts:
1. Select Maintenance > Store Settings > Order Entry group > Guest Counts tab.
Figure 22 Store Settings - Order Entry Group - Guest Counts Tab
2. Select Reports Use Fractional Guest Count.
Reports Use Fractional Guest Counts — Displays guest count values with two decimal places
on the following reports: FOH Server Sales report, FOH Flash report, BOH Server Sales report,
BOH Sales by Revenue Center report, and the BOH Summary and Weekly Sales reports. The
guest count values display with decimal places only when an item defined as a fractional guest
Page 38
count weight is sold. Required Options: 1) To define items with a guest count weight, enter a
whole or fractional value in the ‘Guest Count Weight’ text box in Maintenance > Menu > Items >
Item tab. 2) You must select ‘Use Entrees for Guest Counts’ in Maintenance > Store Settings >
Order Entry group > Guest Counts tab to use fractional guest counts.
Reporting Fractional Guest Counts
When you view or print a report that contains guest counts, the values that contain a fractional value appear
with two decimal places, with an ending total. A guest count value that does not include an item defined as
a fractional guest count weight, or rounds up to the nearest whole number, displays on the reports as normal.
Figure 23 FOH Server Sales Report
Guest counts appear on the following reports:
•
•
•
•
•
•
FOH Flash report
FOH Server Sales report (shown)
BOH Server Sales report
BOH Sales by Revenue Center report
BOH Summary Sales report
BOH Weekly Sales report
Page 39
Reporting Multi-Level Modifiers in Grind Files
Reporting Multi-Level Modifiers in Grind Files
Version
RFC Number
Products
Audience
POS v6.4
RFC 48191
MenuLink
Store Managers
Prior to v6.4, the GndItemParent column of the GndItem file reports only the top level item as the parent of
all its associated modifiers. For example, when you enter the following, the system reports all modifiers
with the Burger item; however, Ranch is a modifier to Salad and Light is a modifier to Ranch.
Figure 24 Example of Multi-Level Modifiers
In v6.4, the GndItem file now reports modifiers with their corresponding parent item. This allows customers who create custom reports or use Enterprise or MenuLink to properly deplete the inventory for items
with multi-layered modifiers.
The following shows the genealogical relationship of the previous example. Notice that the parent modifier
for item ID 2003 (Ranch) is item ID 2002 (Salad) and the parent modifier for item ID 2004 (Light) is item
ID 2003 (Ranch).
Item ID Item
100
2000
2001
2002
2003
2004
Parent
Burger
Mayo
Tomatoes
Salad
Ranch
Light
0
100
100
100
100
100
ParentMod
0
100
100
100
2002
2003
The following information is new to the GndItem file:
Field Name
Field Description
ParentMod
Item ID number of the immediate parent item, even if the parent item is a modifier
to another item.
Page 40
Supporting Enhanced Breaks Functionality
Version
RFC Number
Products
Audience
POS v6.4
RFC 48982
Store Managers
An employee break is when an employee temporarily goes off the clock for a short time, usually 15 minutes for a rest, or 30 minutes to an hour for a meal, and then returns to work. These interruptions are controlled by the break rules you configure in the system. Break rules are governed by the jurisdiction in
which you reside, and depending on the jurisdiction, the restaurant is required by law to give the employee
an allotment of breaks or face stiff penalties enforced by labor boards or legal actions against the employee
themselves.
Purpose of this Document
The purpose of this document is not to dictate or interpret the intentions of the labor laws, but to offer a
comprehensive tool to make your restaurant compliant with the labor laws in your jurisdiction. It is your
responsibility to research and know your own laws that govern breaks in your area. Failure to do so, could
result in extensive fines and stiff penalties.
My Jurisdiction Does Not Require Breaks
If the jurisdiction in which you live does not require restaurants to give their employees breaks, you can
use the default paid and unpaid breaks configured in the system without any consequence. You do not have
to implement additional break features, such as placing enforcements on breaks, configuring waive break
and break reminder messages, and enabling penalty pay.
My Jurisdiction Does Require Breaks
If the jurisdiction in which you live does require restaurants to give their employees an allotment of breaks,
we highly recommend you configure, or at least view, the optional break features listed in this document.
Implementing only one break feature may satisfy some jurisdictions, where others may require you to
implement the full spectrum of break features.
Other factors may include break qualifiers, such as requiring minors to receive a different set of breaks,
restricting employees from starting a break outside of a specific time frame, and requiring employees to
work a specific number of hours before they can receive a break.
How This Document is Organized
This document is organized by feature, starting with implementing a very basic break rule to satisfy jurisdictions that do not require breaks, to implementing complex breaks to satisfy jurisdictions that require a
strenuous set of break rules. Once you configure the basic break rule, you can jump to the appropriate
break feature you want to build upon the break rule. You can define up to 99 break rules with a different set
of requirements, such as paid or unpaid, minors or regular employees, recurring or non-recurring, and by
region for corporations and franchise stores. The document also details the impact on break rules when you
edit an employee’s time.
Page 41
The following is only a sample of the tools available to you when configuring employee breaks:
•
•
•
•
•
•
•
•
•
Configure the break rule to either pay or not pay an employee for a break.
Configure the break rule to apply to specific jurisdictions.
Configure the break rule to force an employee to remain on a break for a designated number of
minutes. With this feature, a manager must override the enforcement when an employees returns
from a break early.
Configure the system to allow a manager to convert an unpaid break to paid, in the case where an
employee returns from their break early.
Configure the system to allow a manager to remove a break; indicating the employee never went
on the break, in the case where an employee returns from their break early.
Provide employees the opportunity to waive their meal period breaks with waive break messages.
Configure break reminder messages to remind employees to take their breaks.
Use the FOH Employee Breaks Report to aide managers in determining the status of breaks taken
by their employees.
Use the FOH Break Alert Report to aide managers in determining when their employees are due to
take their breaks in accordance with the system configuration.
Refer to the Employee Breaks Feature Focus Guide for complete information on configuring and
using employee breaks with break rules.
Page 42
Supporting Visual Indicators with Fingerprint Scanner
Supporting Visual Indicators with Fingerprint
Scanner
Version
RFC Number
Products
Audience
POS v6.4
RFC 53597
Store Managers
Depending on the size of the database, and the physical capabilities of the terminal in use, the process of
fingerprint enrollment can lag several seconds between swiping your finger across the scanner, and seeing
the results of that scan. Fingerprint enrollment screens include a visual indicator, to provide feedback to the
employee or the enrolling manager that the system is performing requested tasks.
Figure 25 Fingerprint Enrollment Screen, Showing Visual Indicator
As you move through the process, each successive screen contains a different message, reflecting the outcome of the current or previous request, and a different visual indicator to provide feedback as to the
results of scanning events.
Although the underlying basis for this visual indicator is part of Aloha v6.4, you must upgrade your fingerprint scanner software to enable it. Contact your Radiant Systems representative for help in obtaining this
upgrade.
Page 43
Enhancing the Create Diagnostic File Utility for v6.4
Enhancing the Create Diagnostic File Utility for
v6.4
Version
RFC Number
Products
Audience
POS v6.1
POS v6.2
POS v6.4
RFC 56063
RFC 57087
RFC 57318
RFC 57322
RFC 57615
RFC 58048
RFC 61886
RFC 69057
Aloha Time Clock, Aloha TakeOut, Aloha
Orderpoint
Store Managers
The following enhancements were implemented in regards to the creation of the diagnostic files that are
sent to the customer service center to help troubleshoot specific problems:
•
•
•
•
•
•
•
•
RFC 56063 Including Aloha Time Clock (ATC) Logs in the Diagnostic File
RFC 57087 Prompting for Existing Files in the Target Diag Folder
RFC 57318 Compressing Individual Diagnostic Files into Single Zip File
RFC 57322 Bypassing Downed Terminals with the Diagnostic Utility
RFC 57615 Collecting Terminal Debouts with the Diagnostic Utility
RFC 58048 Including Date of Business in Diagnostic File Name
RFC 61886 Including Orderpoint Configuration Files with the Diagnostic Utility
RFC 69057 Collecting Aloha Takeout Files from File Server with the Diagnostic Utility
RFC 56063 Including ATC Logs in the Diagnostic File
During normal operation of the Aloha system, the program interacts with the operating system to create
debout files, and to make entries in those files to record events as they happen in the system. These files are
seldom needed, so the information recorded in them is periodically overridden. However, when problems
occur, the information in these files may be invaluable in identifying the causes. Occasionally, it is necessary to obtain more information than the set of files normally available through the View Debugging File
feature. When more information is needed, the Create Diagnostic Files feature is invaluable in diagnosing
problems experienced in the system.
You can now include the logs from the RTC folder when using the Aloha Time Clock application. The
AppLog_yyyymmdd.log captures actions from the RTC folder. The ATCMGR_yyyymmdd.log captures
actions from the RTC Svr UI application.
Page 44
To include Aloha Time Clock logs in the diagnostic file:
1. Select Utilities > Create Diagnostic Files to display the Create Diagnostic Files function tab.
Figure 26 Create Diagnostic Files Function
2. Select Include ATC Logs.
Include ATC Logs — Lists all ATC logs when using the Aloha Time Clock application.
3. Click Generate to create the diagnostic file or click Cancel to cancel the function.
RFC 57087 Prompting for Existing Files in the Target Diag Folder
When using the Create Diagnostic Files utility and you click Generate, the system now checks if there are
any existing files in the target Diag folder. If there are files, the system prompts you with a message,
“There are existing files in your Diag folder from a previous generation of diagnostic files. Do you want to
delete them before generating new files?” Click ‘Yes’ to delete any existing files in the Diag folder or click
‘No’ to abort the action. If you want to keep any existing diagnostic files, move the file out of the Diag
folder.
RFC 57318 Compressing Individual Diagnostic Files into Single Zip File
The Create Diagnostic Files utility now compresses each individual file into a single zip file called
‘Diag.zip.’ This makes the files more portable and reduces the possibility of omitting files during transfer.
RFC 57322 Bypassing Downed Terminals with the Diagnostic Utility
When the Create Diagnostic Files utility gathers file information, the system may make multiple attempts
to access each terminal. If a terminal is down, this causes a delay in the zip process. The system now
bypasses the downed terminal after its initial attempt. This only occurs on the current instance of the generation and the next time you run the utility, the system attempts to access the downed terminal again.
Page 45
RFC 57615 Collecting Terminal Debouts with the Diagnostic Utility
The Create Diagnostic Files utility now collects the debouts from each terminal in the Trm_Deb.zip file it
creates.
RFC 58048 Including Date of Business in Diagnostic File Name
The Create Diagnostic Files utility now includes the date of business as the file name for each diagnostic
zip file it creates, in the form of ‘Diagyyyymmdd.zip,’ where yyyy is the four-digit year, mm is the twodigit month, and dd is the two-digit day. This allows files to have a unique name for sites that submit multiple diagnostic files.
RFC 61886 Including Aloha Orderpoint with the Diagnostic Utility
The Create Diagnostic Files utility now collects the .xml files in zipped up in a OrdPoint.zip file for troubleshooting the Aloha Orderpoint product. Many of the configuration files for Aloha Orderpoint are
already included in the Diagnostic utility.
RFC 69057 Collecting Aloha Takeout Files from File Server with the Diagnostic
Utility
The Create Diagnostic Files utility now collects the log files in the Aloha Takeout/Logs directory and the
data files in the Aloha Takeout/Data directory necessary to troubleshoot the Aloha Takeout product. The
utility only collects the files on the file server and not the files that reside on the FOH terminals.
Page 46
Disallowing Repeat with Weighed Items
Disallowing Repeat with Weighed Items
Version
RFC Number
POS v6.2.11 RFC 56747
POS v6.4.1
Products
Audience
In accordance with the National Conference on Weights and Measures, the use of the Repeat and Quantity
button functions for an item ordered by weight is no longer allowed. This is partly driven by the fact that
two weighted items seldom carry the same weight and adding the exact copy of an item to the guest check
would not be accurate most of the time. When you touch the Repeat or Quantity button for an item entered
by weight, the error message “You cannot repeat weighed items” appears.
Page 47
Adding Reason Code and Revenue Center to Chit File
Adding Reason Code and Revenue Center to Chit
File
Version
RFC Number
Products
Audience
POS v6.4
RFC 56988,
RFC 56989
The Aloha POS system creates text files with remote printer chit information for you to use in creating and
printing custom chits. You must create an application or batch file that processes and deletes the chit information files. The Aloha application does not offer any fault tolerance features for chit information files.
Chit information files are multi-line ASCII text files with the following format:
[keyword] [value(s)]
Keywords start in column one and values start in column 15. In v6.4, you can now use the following keywords.
Keyword
Values
Reason
Revenue Center
Reason ID, label
Revenue Center ID, label
Refer to RKS ID 6170 for complete information on using chit information files.
Page 48
Suppressing Voucher Printing When Under Required
Suppressing Voucher Printing When Under
Required Ceilings
Version
RFC Number
Products
Audience
POS v6.4
RFC 57151
Store Managers
In Aloha v5.3.26e or Aloha v6.0 and higher, we introduced the ability to configure a signature ceiling, so
that a customer only has to sign the voucher when a credit card transaction is over a specified amount, thus
increasing the speed of service for credit card transactions. In Aloha v6.4, you can suppress the printing of
the credit card voucher altogether, when the credit card transaction is less than the specified ceiling.
SCENARIO: During busy times, a restaurant experiences a large amount of credit card usage, and the
printing of the voucher causes a backup when guests pay and leave. Increase your speed of service by configuring the system so that the voucher does not print at all for credit card transactions that are less than
the specified ceiling amount.
Configuring Signature Ceilings for Credit Cards
To configure a ceiling for requiring credit card signatures, you must first define the signature rules and then
specify the tenders to which the rules apply. Refresh the system to update your configuration.
To configure the credit card ceiling:
1. Select Maintenance > Store Settings.
2. Select the Credit Card group > Options tab.
Figure 27 Store Settings - EDC Group - Options Tab
3. Type the ceiling amount in the ‘No Signature Required if less than ___’ text box.
Page 49
Suppressing Voucher Printing When Under Required Ceilings
No Signature Required if less than ___ — Specifies the minimum amount of credit card purchase to require a signature. When a credit card purchase is less than the defined amount, a signature line does not print on the voucher. Type 0 to indicate all credit cards require a signature.
Related Options: 1) To exclude specific tenders from these rules clear ‘Apply Signature Ceiling
Rules’ in Maintenance > Payments > Tenders > Type tab. 2) To suppress the voucher from printing
altogether for a specific tender, when ceiling conditions are met, select ‘Do Not Print Voucher’ in
Maintenance > Payments > Tenders > Type tab.
4. Select Manually Entered Cards, if necessary.
5. Select Swiped Cards, if necessary.
To configure a credit card tender to use signature ceiling rules:
1. Select Maintenance > Payments > Tenders.
2. Select the appropriate credit card tender and press Enter.
3. Select the Type tab.
Figure 28 Tenders - Type Tab
4. Select Apply Signature Ceiling Rules.
Apply Signature Ceiling Rules — Applies signature ceiling rules, as defined in Maintenance >
Store Settings > Credit Card group > Options tab, to the tender when it is used as a form of payment. Required Options: 1) You must select ‘Credit Card’ as the tender type to enable the ‘Apply
Signature Ceiling Rules’ option. 2) Define the ceiling amount to require a signature line in Maintenance > Store Settings > Credit Card group > Options tab. Related Options: 1) When you select
‘Apply Signature Ceiling Rules,’ the ‘Do Not Print Vouchers’ option, which applies to the tender
regardless if ceilings are used, is not available. 2) To suppress the signature line on the voucher
Page 50
Suppressing Voucher Printing When Under Required
when the amount is less than the ceiling amount, select ‘Do Not Print Signature Line.’ 3) To suppress the printing of the voucher altogether when the amount is less than the ceiling amount, select
‘Do Not Print Voucher.’
Upgrade Upon upgrading from a previous version, the ‘Apply Signature Line Rules for Vouchers’
Path
option is renamed to ‘Apply Signature Ceiling Rules.’ If selected, the ‘Do Not Print Signature
Line’ option is automatically selected as default.
5. Select one of the following options.
Do Not Print Signature Line — Suppresses the printing of the signature line on the voucher if
the credit card transaction is less than the amount specified for the ceiling. Required Options: You
must select ‘Apply Signature Ceiling Rules’ to enable this option. Related Options: This option
disables ‘Do Not Print Voucher.’
Do Not Print Voucher — Suppresses the printing of the voucher altogether if the credit card
transaction is less than the amount specified for the ceiling. Required Options: You must select
‘Apply Signature Ceiling Rules’ to enable this option. Related Options: This option disables ‘Do
Not Print Signature Line.’
6. Click Save.
7. Repeat this procedure for each credit card tender for which you want to apply signature ceiling
rules.
8. Exit the Tenders function.
Using Signature Ceilings
When you configure a credit card tender to use signature ceiling rules, the system prints the voucher with
the signature line when the charge meets or exceeds the ceiling amount. The following procedure assumes
the configuration requires a signature line for all credit cards, whether you use a mag stripe reader or manually enter the number.
For QuickService operations, you currently cannot reprint a credit card voucher.
For TableService operations, you can reprint the credit card voucher with the FOH
Reprint button, as needed.
To use the ceiling rules:
1. With the check appearing in the guest check window, touch the appropriate tender. The corresponding tender screen appears.
2. Enter the purchase amount and touch OK.
3. Slide the card across the reader, or use the numeric keypad to manually enter the card number.
The following actions occur:
• If ceiling rules with the ability to suppress the signature line are in use for the tender, and the
purchase amount exceeds the ceiling amount, the voucher prints with the signature line for
the guest to sign.
Page 51
Suppressing Voucher Printing When Under Required Ceilings
•
If ceiling rules with the ability to suppress the signature line are in use for the tender, and the
purchase amount does not exceed the ceiling amount, the voucher prints without the signature line.
• If ceiling rules with the ability to suppress the printing of the voucher are in use for the tender,
and the purchase amount exceeds the ceiling amount, the voucher prints with the signature
line for the guest to sign.
• If ceiling rules with the ability to suppress the printing of the voucher are in use for the tender,
and the purchase amount does not exceed the ceiling amount, the voucher does not print.
• If ceiling rules are not applied to the tender, the voucher prints with a signature line, as normal.
4. Close the check as normal.
Refund checks always print a voucher without a signature line, even if the tender used on the
refunded check has ceiling rules applied.
Page 52
Installing Service for MenuLink COM Changes
Version
RFC Number
Products
Audience
POS v6.4
RFC 57341
Store Managers, End Users
For customers using MenuLink and Aloha, you can install and utilize a new service, Aloha Database
Update, to update the POS system with changes made in third party back office systems, currently only
supported for MenuLink. The service regularly scans for changes made in the MenuLink product, such as
changes to employees, time clock edits, menu items, and more, and synchronizes the POS system with the
changes made via a COM interface. The system uses specific .xml files that manage and send the updates
directly into the respective .dbf and .ini files of the Aloha system.
To enable the Aloha Database Update Service from the installation CD:
1. When installing from the installation CD, you receive a prompt to install the Aloha DBUSvc service.
Figure 29 AlohaDBUSvc Service Installation Prompt
Click Enable AlohaDbuSvc. The AlohaDbuSvc Service Property dialog box appears.
Figure 30 Aloha DBUSvc Service Property Dialog Box
2. To register the service under the local system account, select Register Services Under The Local
System Account and continue to Step 7.
Page 53
Register Under the Local System Account — Registers the Aloha Database Service and operates under authentication of the local system network permissions account. This setting is appropriate for small networks not installed under a local domain name, and utilizing a BOH server with
fewer than ten terminals.
3. To register under a specific user account, select Register Under a Specific User Account.
Register Under a Specific User Account — Registers the Aloha Database Service and operates
under authentication of a specific network permissions account, created for the sole purpose of
registering the service. This setting is appropriate for larger networks, often, but not necessarily,
using a local domain. The user account must reside on all terminals and the BOH server, and use
the same password in each instance, if the network is not using a local domain. You must create the
user and common password, and make it operational on the network, prior to activating this setting.
4. Type name for the account.
Account Name — Holds the name of the specific AlohaDBUSvc user account used across the
network, to authenticate the AlohaDBUSvc Windows service.
5. Type a password to use for logging in.
Password — Holds the common password used for the specific AlohaDBUSvc user account. The
program masks the appearance of the password with asterisks. Remember to use a complex password, composed of mixed case letters, numbers, and special characters.
6. Re-type the password for confirmation.
Confirm Password — Requires you to repeat the password entered in the ‘Password’ text box, to
confirm its accuracy.
7. Click OK to complete the installation.
If you select ‘Do not enable AlohaDbuSvc’ upon installation, or upgrade to v6.4 via the Bin folder, you can
register the service manually.
To register and unregister the Aloha Database Update Service manually:
1. From a command line, navigate to the \Bin directory.
2. To register the Aloha Database Update Service, type alohadbusvc /service with any of the following switches:
/user xxxx (where xxxx is the account name) — Defines the user account name installed with
the service.
/pswd xxxx (where xxxx is the password) — Defines the user account password installed with
the service.
/s or /silent — Does not prompt you for a user name and password during installation. The system
assumes you are registering under a local system account.
Page 54
If you type ‘/service /user’ and do not provide a password, the AlohaDbuSvc Service Property dialog box appears so you can add a password (Figure 30).
If you type ‘/service /user /s or /silent,’ and do not provide a password, the system allows you to
register without a password.
To unregister the Aloha Database Update Service, type alohadbusvc /unregserver.
Upon installation, the Aloha Database Update Service creates the AlohaDBU directory under Aloha or
AlohaQS. Within the directory, the following folders are created:
Request — Holds the .xml files generated from MenuLink. The POS system immediately processes these
files, beginning with the first transaction found within the .xml file. The Aloha Database Update service
writes the request directly into the appropriate .dbf or .ini file on the POS system. The results of these
actions are written into the response .xml file.
Response — Holds the response .xml files after the POS system updates the database.
If a response .xml file is not created, or you have not installed the Aloha Database Update service, an informational error is written to the Debout.AlohaDBUSvc file.
Page 55
Using Common Terminology Between Aloha Manager and MenuLink
Using Common Terminology Between Aloha
Manager and MenuLink
Version
RFC Number
Products
Audience
POS v6.4
RFC 57639
MenuLink
Customers who use the Aloha and MenuLink products together must enter the same data into each program to maintain matching system configurations. This can cause confusion for customers, as the labels for
some options do not coincide between the two products. In an effort to integrate the two products, we have
relabeled some existing Aloha Manager options to coincide with the terminology used in the MenuLink
product. The functionality for each option remains the same.
The following options in Aloha Manager were relabeled.
Figure 31 Store Settings - System Group - Store Information Tab
Old Label
New Label
Unit No.
Unit
Telephone 1
Telephone 2
City/Town
Site ID
Site
Phone 1
Phone 2/Fax
City
Page 56
Using Common Terminology Between Aloha Manager
Figure 32 Store Settings - System Group - Date/Time Tab
Old Label
New Label
First Day of Week
Start of Week for Payroll
Figure 33 Store Settings - Labor Group - Employee Settings Tab
Old Label
New Label
Min Wage
Min Wage Tipped (TableService only)
Minimum Wage
Minimum Wage Tipped (TableService only)
Page 57
Using Common Terminology Between Aloha Manager and MenuLink
Figure 34 Maintenance - Menu - Items - Item Tab
Old Label
New Label
Cost
Recipe Cost
Page 58
Removing Fastech as an Available PMS Type
Removing Fastech as an Available PMS Type
Version
RFC Number
POS v6.2.2 RFC 58548
POS v6.4
Products
Audience
Originally, the Meal Accountability product interacted with the Aloha POS system via the PMS charge
posting interface known as Fastech. The Meal Accountability product has since become CIM/MAS and no
longer requires the Fastech PMS type to interface with Aloha; therefore, when you install v6.2.2, the
‘Fastech’ option in Maintenance > Store Settings > Hotel group > PMS tab is no longer available.
Page 59
Suppressing Cardholder Name on Credit Card Vouchers
Suppressing Cardholder Name on Credit Card
Vouchers
Version
RFC Number
POS v6.2.3 RFC 58579
POS v6.4
Products
Audience
Aloha EDC
In an effort to comply with the latest practices to prevent credit card fraud and the availability of sensitive
account information, the Aloha system is constantly being enhanced to ensure a secure and confident experience for the customer. When you configure the system to print extra credit card vouchers, such as for
merchant copies, the name of the cardholder appears. You can now suppress the printing of the cardholder
name on all credit card vouchers.
When you upgrade to v6.2, the Credit Card group in Store Settings has the following changes:
• The Credit Card function has a Voucher Printing 1 and Voucher Printing 2 tab.
• The ‘Credit Card Number Mask’ and ‘Suppress Expiration dates’ options moved to the
Voucher Printing 2 tab.
• The ‘Number of Voucher Copies’ option is now a drop-down list in which you can select
the number of vouchers to print, instead of a text box.
To suppress the cardholder name on credit card vouchers:
1. Select Maintenance > Store Settings > Credit Card group > Voucher Printing 1 tab.
Figure 35 Store Settings - Credit Card Group - Voucher Printing 1 Tab
2. Select the number of voucher copies you want to print.
Page 60
Suppressing Cardholder Name on Credit Card Vouch-
3. Select the Voucher Printing 2 Tab.
Figure 36 Store Settings - Credit Card Group - Voucher Printing 2 Tab
4. Select Suppress Cardholder Name.
Suppress Cardholder Name — Does not print the name of the cardholder on the credit card
voucher. When using a magnetic card reader, the system replaces the ‘Magnetic Card present:
<cardholder name>’ line on the voucher with ‘Magnetic Card present: Yes.’ Required Option:
You must select the number of vouchers to print from the ‘Number of Voucher Copies’ drop-down
list in Maintenance > Store Settings > Credit Card group > Voucher Printing 1 tab to utilize this
feature.
Page 61
Enhancing the Create Diagnostic File Utility
Enhancing the Create Diagnostic File Utility
Version
RFC Number
POS v6.4.0 RFC 59137
RFC 59217
Products
Audience
Store Managers
During normal operation of the Aloha system, the program interacts with the operating system to create
debout files, and record events in the files as they happen in the system. When a problem occurs, the information in these files may be invaluable in identifying the cause. Occasionally, it is necessary to obtain
more information than is normally available through the View Debugging File feature. When more information is needed, the Create Diagnostic Files feature is invaluable in diagnosing problems experienced in
the system.
The following enhancements were implemented in regards to the creation of the diagnostic files that are
sent to the customer service center to help troubleshoot specific problems:
•
•
RFC 59137 Including Windows Application, Security, and System Event Logs in the Diagnostic File - The diagnostic file now includes a WinLogs.zip file, which contains the Windows
application (Application.evt), security (Security.evt), and system (System.evt) event files.
RFC 59217 Including Thorn Versions in the Diagnostic File - Thorn versions are created from
an existing build and include an extended build number. They are created for special reasons. The
diagnostic file now includes any available thorn build numbers.
Page 62
Updating Aloha Fingerprint Scanner Software
Updating Aloha Fingerprint Scanner Software
Version
RFC Number
Products
Audience
POS v6.4
RFC 59262,
RFC 59633,
RFC 59909
We have updated the fingerprint scanner software and drivers to version 2.0, incorporating multiple benefits for sites using Radiant P1220 and P1520 terminals with integrated fingerprint scanners.
The new software incorporates the following improvements:
•
•
•
•
Faster search and response times.
Enhanced communication between the BOH file server and the FOH terminals, for more efficient
communication.
The appearance of a small, white hand, the standard Windows ‘link select’ pointer, while the fingerprint scanner software is busy identifying an employee or registering a new employee. A user
knows the terminal is busy, if the pointer is visible.
Support for using Authentec and UPEK fingerprint scanners together in the same network. This
version automatically detects the type of scanner in use on each terminal, and loads the appropriate
drivers on that terminal.
Obtain v2.0 from the Radiant FTP site, or from an appropriate Aloha installation CD. Contact your Radiant
representative for more information about how to upgrade your installation.
Page 63
Expanding Debugging Capabilities in Aloha Manager
Expanding Debugging Capabilities in Aloha
Manager
Version
RFC Number
POS v6.4.0 RFC 60288
RFC 60289
RFC 60290
RFC 60553
RFC 60554
Products
Audience
Store Managers
Debug information aides you and Aloha customer support in troubleshooting problems within the Aloha
system and communication passed to and from Aloha EDC and PMS. When an issue occurs, the site
enables debugging and reproduces the problem to write to the debout for the terminal. This process can
cause a significant delay in correcting the problem for the site.
The following enhancements were implemented in regards to the debugging of the Aloha POS system to
help troubleshoot specific problems:
RFC 60288 - Relocating Debugging Options in Aloha Manager
To centralize the debugging options in Aloha Manager, as well as any future options related to debugging,
there is a new tab in Maintenance > Store Settings > System group > Troubleshooting tab. All options were
previously located on the Aloha Settings tab.
Figure 37 Store Settings - System Group - Troubleshooting Tab
Page 64
Expanding Debugging Capabilities in Aloha Manager
RFC 60289, 60290 - Supporting Store-Wide FOH COM Debugging in Aloha Manager
Currently, if you want to debug FOH COM, you must create a Debug_COM system environment variable
on a specific terminal and assign the value to True. You can now perform a system-wide debug across all
terminals with the Debug FOH COM option in Maintenance > Store Settings > System group > Troubleshooting tab. This enhancement introduces the new DebugFOHCOM variable in Aloha.ini. We still support the system variable for situations when you want to debug a specific terminal, rather than the entire
store.
RFC 60553, 60554 - Supporting Store-Wide FOH PMS Debugging in Aloha Manager
Currently, if you want to debug FOH PMS, you must create a PMSDebug marker file in the Aloha directory on a specific terminal and assign the value to True. You can now perform a system-wide debug across
all terminals with the Debug FOH PMS option in Maintenance > Store Settings > System group > Troubleshooting tab. This enhancement introduces the new DebugFOHPMS variable in Aloha.ini. We still support
the PMSDebug marker file for situations when you want to debug a specific terminal, rather than the entire
store.
Page 65
Supporting FACTA Requirements for US Upgrades
Supporting FACTA Requirements for US
Upgrades
Version
RFC Number
POS v6.2.8 RFC 60819
POS v6.4.0
Products
Audience
The provisions of the U.S. Federal law known as FACTA (Fair and Accurate Credit Transactions Act) contain two requirements that impact the configuration of an Aloha site. One provision requires that a payment
card expiration date must not appear in print on receipts, vouchers, or other printed chits in the restaurant.
The other requirement specifies that no more than the last five digits of a payment card number may be
exposed in print.
Although we recommend suppressing the expiration date and masking all but the last four digits of the payment card, we felt it would be very helpful to the Aloha POS community to make these changes occur
automatically, whenever possible. Beginning with versions of Aloha that become available after November, 2007, the affected settings change automatically to the PCI-compliant state any time you upgrade the
Aloha database for a U.S. installation.
The affected settings are as follows:
•
•
•
In Maintenance > Payments > Tenders > Type tab > Options group box, clear the ‘Print Expiration’ check box.
In Maintenance > Store Settings > Credit Card group > Voucher Printing tab, select the ‘Suppress
Expiration Dates’ check box.
In the same location in Store Settings, immediately beneath the ‘Suppress Expiration Dates’
option, select ‘Only show last 4 digits’ from the ‘Credit Card Number Mask’ drop-down list.
If your installation is outside the U.S., we recommend you verify the legal requirements in your area with
regard to printing or suppressing the expiration date and the payment card number. If the regulations under
which you operate do not require printing this information, we recommend you configure Aloha to omit
printing the expiration date, and to mask all but the last four digits of the payment card number, as a best
practice to protect your customers, and your business. Check with your Radiant Systems representative, to
determine if a specific release includes this feature.
Page 66
Suppressing Pipe Characters on Customer Survey
Suppressing Pipe Characters on Customer
Survey
Version
RFC Number
POS v6.1.15 RFC 61041
POS v6.2.8
POS v6.4.0
Products
Audience
The Customer Survey feature provides restaurants the ability to prompt randomly selected guests for feedback about their dining experience. The prompts print on the guest check, along with a phone number for
the customer to call and take a customer survey, or poll, in exchange for a reward or discount. You can
define the times the survey is valid, the frequency the survey prints for a specific day part, the text to
appear in the survey, and can print up to a 16-digit code for reference information.
On the printed receipt, the survey code is framed by a beginning and ending pipe character. This is sometimes perceived as the number ‘one’ and reflects an incorrect survey code. In v6.1.15, v6.2.8, v6.4.0, and
all versions higher, you can now suppress the pipe characters from printing by adding the following variable to Aloha.ini:
NoSurveyPipe=True
Refer to the Customer Survey Feature Focus Guide for more information on configuring and
using the Customer Survey feature.
Rfasdfa
Page 67
Encrypting Sensitive Information in Debouts with Debug FOH COM
Encrypting Sensitive Information in Debouts with
Debug FOH COM
Version
RFC Number
Products
Audience
POS v6.4
RFC 61421
In an effort for the POS system to be in compliance with the requirements of the Payment Card Industry
Data Security Standard (PCI DSS), when you select Debug FOH COM in Maintenance > Store Settings >
System group > Troubleshooting tab, POS v6.4 now encrypts the sensitive information that is added to the
terminal debouts, such as card numbers, expiration dates, track information, and employee passwords. The
Debug FOH COM option is used for troubleshooting purposes when you enable a device via Aloha Connect.
Page 68
Adding the Time Items Appear on the Guest Check
Adding the Time Items Appear on the Guest
Check Window in GndItem.dbf
Version
RFC Number
POS v6.4
RFC 61555
Products
Audience
MenuLink
To generate correct information from the Aloha POS system for the Speed of Service (SOS) report in the
MenuLink product, you can now track the time an item is placed on the FOH guest check window. With
v6.4 and higher, GndItem.dbf now includes the following columns:
•
•
•
•
ETime_Hour
ETime_Min
ETime_Sec
TableID
Page 69
Supporting Radiant SRP-350 Series Printer
Supporting Radiant SRP-350 Series Printer
Version
RFC Number
Products
Audience
v6.2.11
v6.4.1
RFC 63288
Store Manager
In Aloha POS v6.5, you can now select the supported Radiant SRP-350 Series from the ‘Type’ and ‘Windows Printer Type’ drop-down lists in the Printers function. Previously, the printer was manufactured as
Bixolon by Samsung and you had to select ‘Epson TM-80’ to act as an emulation device. Since then, Radiant Systems has rebranded the printer as Radiant SRP-350 and the printer now appears as the first selection
in these drop-down lists to signify a preferred hardware solution.
Page 70
Printing Two Lines Per Item on Guest Check
Version
RFC Number
Products
Audience
v6.4.0
RFC 61730
In v6.4, you can now print a second line of text for an item on the guest check. You may want to print a second line for any of the following reasons:
•
In the International market, it is customary to print an item on the guest check in its native language and in English.
Tagessuppe
Soup of the Day
•
Some menu items have exceptionally long names or include patented signature items that need to
appear on the check, such as ‘Aloha Cafe®’s Triple-Decker Hamburger Deluxe.’
Aloha Cafe®’s Triple-Decker
Hamburger Deluxe
•
€3.99
4.99
Reserve the second line for the number of calories included in a menu item.
Nachos
Calories: 348
6.99
To print two lines for an item on the guest check:
1. Select Maintenance > Menus > Items > Item tab.
Figure 38 Items - Item Tab
2. Type the Long Name for the item.
Page 71
Long Name — Includes the formal, more descriptive name of the item. The ‘long name’ can be
up to 25 characters, prints on the guest check, and is used in conjunction with ‘Item Number’ to
create a unique ID for each item record in the system. Related Options: To print a second line of
text for the item, type a description in the ‘Long Name 2’ text box.
3. Type a second line of text to print for the item in Long Name 2.
Long Name 2 — Allows you to add a second line of text, in conjunction with the ‘long name’ text
box, to print on the guest check. You can use this for such things as displaying items in dual languages or for exceptionally long names. The additional line does not appear on the guest check
window, reports, or a video screen in use, nor does it contain a price.
4. Click Save.
5. Repeat this procedure for each item for which you want to print two lines of text on the guest
check.
6. Exit the Items function.
Page 72
Assigning an eFrequency Customer by Barcode Scan
Assigning an eFrequency Customer by Barcode
Scan
Version
RFC Number
Products
Audience
v6.4
RFC 63351
RFC 63397
For customers using eFrequency, you can now scan an eFrequency card that has an imprinted barcode from
the Order Entry screen, Tender screen, or Assign Member screen in the POS. This enables your employees
to scan the eFrequency card to retain speed of service. The POS enforces all eFrequency business rules,
such as only allowing you to scan the eFrequency card after items are ordered in the POS.
In Aloha TableService, you must enable ‘Scan eFrequency Members From Order Entry Screens’ to allow
scanning eFrequency cards from the Order Entry screen or Tender screen. Servers can still assign the eFrequency number to the check on the Assign Member screen. Refer to the eFrequency User Guide for more
information on eFrequency.
If you are using Aloha QuickService, you do not need to make any make any selections in the
POS; this feature is automatically enabled.
If you are using Aloha TableService, select Maintenance > Store Settings > System group > Interfaces tab
and select ‘Scan eFrequency Members From Order Entry Screens.’
Figure 39 TableService Assign an eFrequency Customer by Barcode Scan
Page 73
Assigning an eFrequency Customer by Barcode Scan
Your eFrequency cards must be encoded with a unique prefix of “ae” on the barcode followed by the 14
digit eFrequency number. This indicates to the Aloha POS that it is an eFrequency card and it connects
with the eFrequency database.
If this transaction is a first time transaction for the eFrequency number, you must swipe the card
via the magnetic card reader to activate the card.
Page 74
Alternating Chit Names on a Video Screen for Dual Lan-
Alternating Chit Names on a Video Screen for
Dual Languages
Version
RFC Number
Products
Audience
v6.4.2
RFC 63871
Restaurants often hire employees whose English is not their primary language, which presents a language
barrier between the kitchen and the wait staff. A misinterpreted word could lead to an item not prepared
correctly or a delay in service when the kitchen needs to receive further instructions.
When you configure an item in Item Maintenance, the chit name displays on the kitchen chit and on any
video display system in use; however, some kitchens do not use kitchen printers and rely primarily on
video screens to prepare orders. In v6.4.2, you can now type an alternate chit name, using the language of
your choice, and the operator can toggle the video screen to display the alternate name.
Configuring Alternating Chit Names on a Video Screen
To configure alternate chit names to appear on a video screen, you must first type the alternate chit name in
Item Maintenance, then enable the video device with the ability to switch to the alternate name when you
select the ‘Refresh Display’ button on the bump bar.
To configure an alternate chit name:
1. Select Maintenance > Menu > Items > Item tab.
Figure 40 Items - Item Tab
2. Select an item from the ‘Number’ drop-down list and press Enter.
3. Type an alternate name or a translation of the item name in the ‘Chit Name 2’ text box.
Page 75
Alternating Chit Names on a Video Screen for Dual Languages
Chit Name — Indicates the name of the item that prints on the kitchen chit and appears on a video
device. The chit acts as an order confirmation the kitchen receives after you send an order to the
kitchen. The chit can be up to 15 characters and contains menu items as well as modifiers, depending on how you enter the order in the system. You typically type the ‘Chit Name’ in ALL CAPs, to
make the name easier to recognize. This option is useful if your restaurant uses nicknames for
menu items. For example, if the kitchen staff of your restaurant refers to a lobster tale as ‘LOB,’
type LOB in the ‘Chit Name’ text box and ‘LOB’ appears on the kitchen chit and/or appears on the
video screen each time a server enters an order for a lobster tail. Related Options: 1) To provide an
alternate chit name to display on a video screen, such as for a translated item in a different language, type the alternate name in the ‘Chit Name 2’ text box. 2) To suppress the printing of the
item on all chits, select ‘Never Print On Chit’ in Maintenance > Menu > Items > Print tab. 3) For
other chit options, such as sort options, chit content, and more, select Maintenance > Store Settings
> Printing-Chits group.
Chit Name 2 — Indicates the alternate name of the item, such as the name of the item as it is written in a different language, to appear on a video device only. Required Option: To use this feature,
you must select ‘Toggle Chit Names on ‘Refresh Display’ in Maintenance > Hardware > Video
Devices.
4. Click Save.
5. Repeat this procedure for each item for which you want to use an alternate chit name.
To configure a video device with the ability to display an alternate chit name:
1. Select Maintenance > Hardware > Video Devices.
Figure 41 Video Devices Function
2. Select a video device from the ‘Number’ drop-down list and press Enter.
3. Select Toggle Chit Names on “Refresh Display.”
Page 76
Alternating Chit Names on a Video Screen for Dual Lan-
Toggle Chit Names on “Refresh Display” — Enables the video device to toggle between ‘Chit
Name’ and ‘Chit Name 2’ in Item Maintenance with the Refresh Display button on the bump bar.
Required Option: To use this feature, you must type an alternate name in Chit Name 2 in Maintenance > Menu > Items > Item tab. If you do not type a name in Chit Name 2, the system defaults to
the name in ‘Chit Name.’
4. Select Chit Name or Chit Name 2 from the ‘Default Chit Name’ drop-down list.
Default Chit Name — Specifies this video device reads all entries from either the ‘Chit Name’ or
Chit Name 2’ text box, upon start up.
5. Click Save.
6. Repeat this procedure for each video group to which you want to display the alternate chit name.
7. Exit the Video Devices function.
Using Alternating Chit Names on a Video Device
On the video screen, the chit name appears, as defined by the ‘Default Chit Name’ option for the video
device. If ‘Chit Name’ is selected, the system displays the text entered for the ‘Chit Name’ field. If ‘Chit
Name 2’ is selected, the system displays the text entered for the ‘Chit Name 2’ field. If nothing is entered
in ‘Chit Name 2,’ the system displays the ‘Chit Name’ field.
For example, items ‘Cheese’ and ‘Bacon’ are configured in Item Maintenance with a Spanish translation in
‘Chit Name 2.’ The guest orders a #1 with bacon and no cheese. The video cell displays the items from the
‘Chit Name’ field.
#1
NO Cheese
ADD Bacon
The employee in the kitchen presses ‘Refresh Display’ on the bump bar. The video screen switches and
displays the text from the ‘Chit Name 2’ field.
#1
NO Queso
ADD Tocino
The employee presses ‘Refresh Display’ on the bump bar again to toggle the system back to displaying the
text from the ‘Chit Name’ field.
Page 77
Displaying Totals on FOH Flash Report
Displaying Totals on FOH Flash Report
Version
RFC Number
POS v6.4.2 RFC 66310
Products
Audience
End User
The FOH Flash report for the Aloha QuickService and TableService products now has ending totals for
each column, where applicable.
Page 78
Supporting Radiant MSR Interface
Version
RFC Number
POS v6.4.9 RFC 68491
POS v6.5.2
Products
Audience
End User
Radiant terminals now provide a more secure way of communicating with the magnetic stripe reader
(MSR) through the Radiant MSR interface, instead of using the Keyboard Wedge service, which has the
potential risk of being accessed by malware. The Radiant MSR interface has the ability to detect unauthorized access of the magnetic stripe reader by another application, and if found, prevents the FOH from
operating. All future images of Radiant terminals will use the Radiant MSR Interface by default, and the
Keyboard Wedge service will be disabled.
The Radiant MSR interface is not supported on Radiant P1210 terminals and non-Radiant terminals.
Upon upgrading to v6.4.9, a new option, “Radiant,” appears in the MSR ‘Type’ drop-down list in Terminal
Maintenance. The preferred configuration is for you to change the MSR type for Radiant terminals from
Keyboard Wedge to Radiant. If you do not, messages and warnings appear in Verify.txt, Debout.txt, and in
the FOH, where appropriate.
Also upon upgrading, the system detects Radiant terminals configured with Keyboard Wedge as the MSR
type, unregisters the Keyboard Wedge Service for you, and automatically begins to use the Radiant MSR
interface driver set for communicating with the magnetic stripe reader. The messages, “Keyboard Wedge
Service Detected, Keyboard Wedge Service Stopped, and Keyboard Wedge Service Unregistered” are
written to the terminal debout.
Page 79
To configure a terminal to use Radiant as the MSR type:
1. Select Maintenance > Hardware > Terminals > Readers tab.
Figure 42 Terminals - Readers Tab
2. Select a terminal from the ‘Term ID’ drop-down list and press Enter.
3. Select Use Mag Stripe Reader.
4. Select Radiant from the ‘Type’ drop-down list. This disables the ‘OPOS’ and enables the ‘Track 2
Only’ options.
5. Click Save.
6. Exit the Terminals function.
When you select Keyboard Wedge as the MSR ‘Type,’ a warning message appears when you click Save.
Figure 43 Keyboard Wedge Warning Message
Click OK to use the keyboard wedge as the MSR type. The system writes a message to Verify.txt for each
terminal configured with a keyboard wedge, stating, “The keyboard wedge is selected as the Magnetic
Stripe Reader type. This can result in a security risk.” The system also writes a message to Debout.txt for
each terminal configured with a keyboard wedge, stating, “Keyboard wedge is saved as a magnetic stripe
reader. This can result in a security risk.”
Page 80
Using a Supported Radiant Terminal
Starting with v6.4.9, accessing the magnetic stripe reader using the Radiant MSR interface with a supported Radiant terminal is the preferred and more secure solution. When you launch the FOH, the system
detects a Radiant terminal is being used and writes the supported Radiant terminal model and serial numbers to the terminal debout.
Even if the MSR is configured as a Keyboard Wedge in Terminal Maintenance, the Radiant MSR interface
unregisters the Keyboard Wedge service, writes the action to the terminal debout, and begins to use the
Radiant MSR interface.
In the extreme case when the system detects unauthorized access to the MSR, a critical error message
appears on the FOH.
Figure 44 FOH Unauthorized Application Accessing MSR
When you touch OK, the FOH shuts down, and cannot launch until you resolve the problem. Contact your
Radiant representative for assistance in solving this problem. A message is also written to the FOH terminal debout stating, “The MSR is already being accessed by the Radiant API. This is a security risk. FOH
will not start until this is resolved.”
Using an Unsupported Terminal
For customers who are using an unsupported terminal, the system behaves properly; however, the system
is not secure and messages are written to Verify.txt and Debout.txt.
In the case of an improper configuration where you select ‘Radiant’ as the MSR type and you are using an
unsupported terminal, the system displays a FOH error message each time you log in, stating “The Magnetic Stripe Reader is not configured properly for this terminal.” The MSR will not function until you correct the configuration, but the FOH will continue to operate.
Figure 45 FOH Magnetic Stripe Reader is Not Configured Properly Message
Page 81
Interfacing with ETT Tavern Tracker Software
Version
RFC Number
POS v6.4.9 RFC 69767
Products
Audience
Store Manager
Aloha POS now interfaces with Tavern Tracker®, a player comp tracking software by ETT that services
casinos, convenience stores, and other venues. Communicating via an IP address, you can apply a comp in
the POS system and send the information, along with the number of the gaming machine, to ETT Tavern
Tracker and have the comp tracking software handle credits the guest earns.
SCENARIO: A bar in a casino environment has multiple gaming machines from which the guest can play
and earn credits for comps toward free drinks. When the guest is served a drink, the cocktail waitress
applies a comp on the POS and enters the number of the machine to associate with the free beverage. The
number of the machine is passed to the ETT Tavern Tracker software. If the comp is not associated with a
particular machine, the FOH PMS Inquiry screen appears for the server to enter the number of the
machine for which to apply the comp.
Configuring the POS to Interface with ETT Tavern Tracker
To configure the Aloha POS system to interface with the ETT Tavern Tracker software, you must do the
following:
•
•
•
Create a category of eligible items for which you can comp from the winnings earned from
Tavern Tracker.
Configure the ETT Tavern Tracker IP address and port number in Store Settings.
Configure either a generic ETT Tracker comp so the employee can enter the number of the
machine in the FOH, or associate a specific machine number for the corresponding comp.
To create a category to use from winnings earned from Tavern Tracker:
1.
2.
3.
4.
5.
6.
Select Maintenance > Menu > Categories.
Type an unused number, or select an existing category, and press Enter.
Type a descriptive name for the category, such as ‘Tavern Tracker’.
Select either Sales, Retail, or Non-Sales.
Select an item from the right list box and click Include. The item appears in the left list box.
Click Save and exit the Category function.
Page 82
To configure the Tavern Tracker IP address and port number:
1. Select Maintenance > Store Settings > System group > Interfaces tab.
Figure 46 Store Settings - System Group - Interfaces Tab
2. Type the IP address of the ETT Tavern Tracker PMS server.
IP — Specifies the IP address of the ETT Tavern Tracker PMS server. This option is specific to
the ETT Tavern Tracker software.
3. Type the port number of the ETT Tavern Tracker PMS server.
Port — Specifies the port number of the ETT Tavern Tracker PMS server. This option is specific
to the ETT Tavern Tracker software.
To configure a comp, or multiple comps, to interface with the ETT Tavern Tracker software:
1.
2.
3.
4.
5.
6.
Select Maintenance > Payments > Comps > Comp tab.
Type an unused number, or select an existing category, and press Enter.
Type a descriptive name for the comp, such as ‘Tavern Tracker’ or ‘Machine 1.’
Select the category.
Select Active.
Complete the remaining options of the Comp tab, as appropriate.
Page 83
7. Select the Back Office tab.
Figure 47 Payments - Comps - Back Office Tab
8. Select PMS Authorize.
9. Type the number of the gaming machine in the ‘PMS Account #’ text box if you are associating
the gaming machine to the comp or clear the option to prompt you to enter the number of the
machine in the FOH.
PMS Account # — Specifies a unique number of the ETT Tavern Tracker gaming machine, such
as ‘01,’ for which the Aloha POS interfaces. When you leave this option blank, you must enter the
number of the gaming machine each time you apply this comp in the FOH. This option is specific
to the ETT Tavern Tracker comp tracker software. Required Options: 1) To enable the interface to
the ETT Tavern Tracker PMS server, you must enter the IP address and port number in Maintenance > Store Setttings > System group > Interfaces tab. 2) You must select ‘PMS Authorize’ to
enable this option.
10. Click Save.
11. Repeat this procedure if you are configuring a comp for each gaming machine. Otherwise, proceed to Step 12.
12. Exit the Comps function.
Interfacing with ETT Tavern Tracker
When interfacing with the ETT Tavern Tracker software, you apply a comp in the POS system that is configured to send PMS information. The system sends the number of the machine to ETT Tavern Tracker to
reconcile all transactions. You can do this by using a single comp, per machine, or with a generic ETT Tavern Tracker comp where you must enter the number of the machine in the FOH when you close the check.
For both scenarios, the ETT Tavern Tracker software does not send a confirmation back to the POS.
Page 84
To interface with ETT Tavern Tracker using a comp per machine:
1. When you are ready to apply an ETT Tavern Tracker comp, perform one of the following based on
the product you have installed:
Aloha TableService: With the active check displayed in the guest check window, touch Close on
the Order Entry screen to display the Close screen, then touch Comps to display the Comp screen
(Figure 48).
Aloha QuickService: With the active check displayed in the guest check window, navigate to your
Comps panel.
2. Touch the comp button configured specifically for the number of the gaming machine. Based
on the comp rules, you may have to select the items to comp, enter an amount to comp, or require
manager approval. The POS system applies the comp and sends the number of the gaming
machine to the ETT Tavern Tracker software based on the number associated with the comp.
In this example, there is a
separate comp configured
per machine.
Figure 48 TableService Comp Screen With an ETT Tavern Tracker Comp Per Machine
3. If the check has a remaining balance, tender the check as normal, with the form of payment
received from the guest.
4. Close the check by performing one of the following based on the product you have installed:
Aloha TableService: Touch Close.
Aloha QuickService: Touch the button configured to close the check or the close function may
be inherent in Step 3.
To interface with ETT Tavern Tracker using a generic comp for all machines:
1. When you are ready to apply an ETT Tavern Tracker comp, perform one of the following based on
the product you have installed:
Aloha TableService: With the active check displayed in the guest check window, touch Close on
the Order Entry screen to display the Close screen, then touch Comps to display the Comp screen.
Aloha QuickService: With the active check displayed in the guest check window, navigate to the
panel containing your comps.
Page 85
2. Touch the comp button configured for all gaming machines. Based on the comp rules, you may
have to select the items to comp, enter an amount to comp, or require manager approval. The POS
system applies the comp.
In this example, there is a
generic comp for all ETT
Tavern Tracker machines.
Figure 49 TableService Close Screen With One ETT Tavern Tracker Comp
3. If the check has a remaining balance, tender the check as normal, with the form of payment
received from the guest.
4. Close the check by performing one of the following based on the product you have installed:
Aloha TableService: Touch Close.
Aloha QuickService: Touch the button configured to close the check or the close function may
be inherent in Step 3.
The FOH Enter Room Number screen appears.
Use the FOH Enter
Room Number screen
to enter the number of
the gaming machine.
Figure 50 FOH Enter Room Number Screen
5. Enter the number of the gaming machine, using the numeric keypad, and touch OK. The POS
sends the number of the gaming machine to the ETT Tavern Tracker software.
Page 86
Supporting Recipes in QuickService
Supporting Recipes in QuickService
Version
RFC Number
Products
Audience
POS v6.4
RFC 05184
Aloha QuickService
A recipe is a list of ingredients with directions for making or preparing an item. For the Aloha POS system,
recipes can be used for a wide range of purposes, from empowering employees with the ability to answer
ingredient questions for the guest, to providing the bartender instructions on how to prepare a drink. They
are not to be confused with recipes created in Inventory Control for inventory tracking.
Most of the time, you access recipes on demand, but you can configure the system to display or print a recipe each time, or for a defined number of times, you order the item. You can also optionally provide an
image of the item and an instructional movie for how to prepare the item.
Figure 51 FOH Recipe Information Screen
The Recipe feature has been available in the Aloha TableService product since v3.6. With v6.4 and above,
you can now configure and use recipes in the Aloha QuickService product.
Refer to the Recipes Feature Focus Guide for complete information on configuring and using
recipes.
Page 87
Supporting FOH Quick Lookup for Promotions
Version
RFC Number
Products
POS v6.4
RFC 28789
Aloha QuickService
Audience
Store Managers
End Users
For sites that use a large number of promotions, you must select a promotion from continuing pages from
the FOH Promo Lookup screen. In Aloha QuickService v6.4, you can now enable the Aloha ‘quick
lookup’ functionality that enables you to select a promotion from the FOH by entering search criteria until
you find the one you want.
Configuring FOH Quick Lookup for Promotions
To enable quick lookup functionality for the Promo Lookup button:
1. Select Maintenance > Menu > Panel Editor to access Panel Editor.
2. Select a desktop size and click OK.
3. From the Commands menu, select the panel to which you want to add the Promo Lookup button
function.
4. Double-click an available button. The Edit Buttons - QuickService dialog box appears.
Figure 52 Promo Lookup Button Function
5. Select Promo Lookup from the ‘Function’ drop-down list.
Promo Lookup — Displays the FOH Promo Lookup screen and allows you to select, or scan a
bar code for, a promotion to apply to the check. Required Options: You must select Maintenance >
Payments > Promotions and configure a promotion to appear in the list. Related Options: 1) If you
Page 88
select ‘Auto Apply’ for a promotion, it does not appear for selection. 2) If you clear ‘Active’ for a
promotion, it does not appear for selection. 3) If you select ‘Do Not Appear in Promo List’ for a
promotion, it does not appear for selection.
6. Select Use Quick Lookup Screen.
Use Quick Lookup Screen — Enables you to enter search criteria using an alphanumeric keyboard, to select an active promotion to apply to the guest check. If cleared, the list of promotions
appear on continuing pages.
7. Type a name, up to 15 characters, for the button. The text, ‘Promo Lookup’ is the default button
name.
8. Set the remaining button attributes the same as you would any other button.
9. Click OK to add the button to the panel.
Using FOH Quick Lookup for Promotions
When you look up promotions, using the Quick Lookup functionality, the system displays the FOH Promo
Lookup screen with a selection list of all active promotions. The list displays the promotions by name. If
the name of the promotion starts with a number, such as 1/2 Off Burgers, the promotion appears at the top.
You must touch the Add to Check button to apply the promotion.
To use the FOH Quick Lookup for promotions:
1. Start a new order and add items to the check that qualify for the promotion.
2. Touch the button configured for Promo Lookup. The FOH Promo Lookup screen appears.
Figure 53 FOH Promo Lookup Screen
3. Select the name of the promotion in the list, or filter the list of promotions by entering the first
few letters of the promotion, until you find a unique match.
4. Touch Add to Check to apply the promotion, if eligible, and return to the order entry screen.
Page 89
Printing Guest Count on Chits in QuickService
Version
RFC Number
Products
POS v6.4
RFC 40664
Aloha QuickService
Audience
Store Managers
You can now include the guest count on the chit in Aloha QuickService for assisting in delivery of nonfood related items, such as paper plates, cups, and napkins, with the meal. With this printed information,
bag handlers can easily include the proper amount of plasticware without having to physically count the
number of entrees, thereby, increasing the speed of service at the restaurant.
SCENARIO: A quick service restaurant includes a complimentary packet of plasticware for each order
based on the number of entrees in the order; however, the time it takes to count the entrees slows down the
speed of service of the restaurant. The restaurant configures the system to use the count of items found in
the ‘Entree’ category as the guest count and prints the number on the kitchen chit. The employee enters
one Aloha Combo meal, one Kid’s Meal, and a dessert. The system finds the first two items in the ‘Entree’
category, but not the dessert. The guest receives two packets of plasticware with the order.
To print the guest count on chits in Aloha QuickService:
1. Select Maintenance > Store Settings > Printing-Chits group > Chit Fields tab.
Figure 54 Store Settings > Printing-Chits Group > Chit Fields Tab
2. Select Print Guest Count.
Print Guest Count — Prints the guest count on the chit. The system uses the check count, including split checks, as the number of guests. Related Options: 1) If you select ‘Use Entrees for Guest
Counts’ in Maintenance > Store Settings > Order Entry group > Guest Count tab, the system uses
the count of items ordered from the specified category as the guest count. The entree count starts at
Page 90
zero for each new transaction. 2) If you select ‘Use Next Seat for Guest Counts’ in Maintenance >
Store Settings > Order Entry group > Guest Count tab, the system uses the count of seats for each
check as the guest count.
The following is a sample of a kitchen chit showing the guest count, using entrees to calculate the guest
count.
Figure 55 Sample Kitchen Chit with Guest Count
The guest count also appears in the following areas of the corresponding BOH and FOH reports:
Section
Guest Count by Day Part, Guest Count by Order
Mode, and Guest Count by Sales Type
Guest Count by Day Part, Guest Count by Order
Mode, and Guest Count by Sales Type
Count to Guest Count, if defined by the performance measure
Checkout Report, if defined by the performance
measure
Last Period and Entire Day Performance sections,
if defined by the performance measure
Report
BOH Sales Summary Report
BOH Sales Weekly Report
BOH Performance Measure Report
FOH Checkout Report or BOH reprint of Checkout
Report
FOH Flash Report
Page 91
Temporarily Capturing Card Data Using Automatic Detection
Temporarily Capturing Card Data Using
Automatic Detection
Version
RFC Number
POS v6.4.4 RFC 52370
Products
Audience
Aloha QuickService
In POS v6.2, we introduced in Aloha QuickService the ability to automatically detect the card type based
on the card prefix, which is similar to the Credit Card Lookup feature in Aloha TableService. This allowed
you to slide a card across the magnetic stripe reader without having to know which type of card is being
used and reduced the number of payment card buttons from which to select.
Refer to AKB 9783 Supporting Automatic Detection of Card Types in QuickService for the original implementation of the Automatic Detection feature.
In Aloha QuickService v6.4.4, we have enhanced this feature with the ability to temporarily capture card
payment data in the memory of the terminal and allow the guest to enter their payment card data, via a
magnetic stripe reader (MSR) or a proximity reader device (RFID), while the cashier is entering the order.
When the order is complete and ready for tendering, the system recalls the cardholder’s information, sends
it to the processor for an authorization, and then deletes the captured data from the terminal.
This enhancement does not effect the Orderpoint hardware (ICD or OCD), since Orderpoint has
its own method of capturing card information.
Configuring Automatic Detection to Temporarily Capture Card
Data
The Automatic Detection feature in Aloha QuickService now has four elements for you to consider in configuration:
•
•
•
•
The action to take on ordered items upon card detection (Ordered Items drop-down list).
The action to take on unordered items upon card detection (Unordered Items drop-down list).
Whether to display the respective tender screen upon card detection (Always Display Tender
Screen option).
The need to retrieve captured card data for payment (Get Stored CC button function).
Page 92
Temporarily Capturing Card Data Using Automatic De-
Not Using a Customer-Facing Payment Device
If you are not using a customer-facing payment device (MSR or RFID), the following table outlines the
recommend configuration of each consideration. This is existing functionality that was introduced in v6.2.
Feature
Configuration
‘Ordered Items’ dropdown list
Process Payment
‘Unordered Items’ dropdown list
‘Always Display Tender
Screen’ option
Since the cashier is initiating the payment, the system assumes the order is complete when the payment card information is received and can process.
Hold for Payment
Not recommended.
Order and Process Pay- Recommended you select this option with ‘Always
ment
Display Tender Screen.’
Prompt to Order and Pro- Recommended.
cess Payment
Hold for Payment
Selected.
Cleared
‘Get Stored CC’ button
function
Notes
Not configured.
Not recommended.
Recommended to allow you to enter split payments.
Recommended only to reduce an additional screen
touch when sending an authorization.
Since this scenario does not capture payment card
data prior to completing the order, adding this button function is not required.
Using a Customer-Facing Payment Device
If you are using a customer-facing payment device (MSR or RFID), the following table outlines the recommended configuration of each consideration:
Feature
Configuration
Notes
‘Ordered Items’ dropdown list
Process Payment
Hold for Payment
‘Unordered Items’ dropdown list
Not recommended.
Since the guest is initiating the payment, the system captures the payment card information until
the order is complete and ready to tender.
Not recommended.
Order and Process Payment
Prompt to Order and Pro- Not recommended.
cess Payment
Hold for Payment
Since the guest is initiating the payment, the system captures the payment card information until
the order is complete and ready to tender.
Selected.
Recommended to allow you to enter split payments.
Cleared
Recommended only to reduce an additional screen
touch when sending an authorization.
Configured.
Since this scenario does capture payment card
data prior to completing the order, you must add
this button function.
‘Always Display Tender
Screen’ option
‘Get Stored CC’ button
function
Page 93
Enabling Automatic Detection of Payment Cards
To use the ‘Automatic Detection’ feature you must enable the feature in Store Settings and select the
actions to take on ordered and unordered items.
Upgrade When you upgrade from a previous version, the ‘Automatically Detect Card Swipe’ option is
renamed to ‘Auto Detect Credit Card Swipe/Tap’ to better reflect the capabilities of the
Path
option. Additonally, the ‘Prompt for Unordered Items’ option is redesigned to allow more
flexibility of the actions you can configure on unordered and ordered items.
To configure storing credit card information for payment:
1. Select Maintenance > Store Settings > User Interface group > Order Screen 2 tab.
Figure 56 Store Settings - User Interface Group - Order Screen 2 Tab
2. Select Auto Detect Credit Card Swipe/Tap.
Auto Detect Credit Card Swipe/Tap — Configures the system to process gift and credit card
transactions and automatically detect the card type, based on the prefix digits of the card. The
check must be displayed in the guest check window to perform this action when the card is slid
across the magnetic stripe reader or a proximity reader. If you clear this option, the automatic
detection is disabled, and you must select the appropriate tender button in the FOH to apply the
transaction. Required Options: To enter prefixes for card types, select Maintenance > Payments >
Tenders > Identification tab and type the prefix numbers in the ‘Prefix’ text boxes for the appropriate tender. Related Options: To automatically display the tender screen for the corresponding card
type, for such things as split payments, select Maintenance > Payments > Tenders > Type tab and
select ‘Always Display Tender Screen’ for the appropriate tender.
3. Select one of the following from the ‘Ordered Items’ drop-down list.
Page 94
Process Payment — Immediately sends an authorization request to the processor for any ordered
item present on the check, regardless if the order is complete. Use the option if are not using a customer-facing proximity reader and the cashier always enters the credit card information. Required
Options: You must select ‘Auto Detect Credit Card Swipe/Tap’ located on the same tab to enable
this option.
Hold for Payment — Temporarily captures the guest’s card data in memory of the specific terminal for any ordered item present on the check so you can retrieve later for payment. Use this option
if you are using a customer-facing proximity reader and allow the guest to enter their card information at any time, regardless if the order is complete. Required Options 1) You must select ‘Auto
Detect Credit Card Swipe/Tap’ located on the same tab to enable this option. 2) To retrieve captured card data, access Panel Editor and add the ‘Get Stored CC’ button function to a panel.
4. Select one of the following from the ‘Unordered Items’ drop-down list.
Order and Process Payment — Immediately orders any unordered items present on the check,
using the default order mode, and sends an authorization request to the processor, regardless if the
order is complete. Use the option if are not using a customer-facing proximity reader and the cashier always enters the credit card information. Required Options: 1) You must select ‘Auto Detect
Credit Card Swipe/Tap’ located on the same tab to enable this option. 2) To prompt for unordered
items, you must configure a default order mode by selecting either Maintenance > System > Order
Entry Queue and an order mode from the ‘Default Order Mode’ drop-down list or selecting Maintenance > Hardware > Terminals and an order mode from the ‘Order Mode’ drop-down list. Otherwise, the action fails.
Prompt to Order and Process Payment — Prompts you to order any unordered items present on
the check. If you select ‘yes’ to the prompt, the system immediately orders any unordered items
present on the check, using the default order mode, and sends an authorization request to the processor, regardless if the order is complete. If you select ‘no’ to the prompt, the system does not
order the unordered items nor send an authorization request. Use this option if you are not using a
customer-facing proximity reader and the cashier always enters the credit card information.
Required Options: 1) You must select ‘Auto Detect Credit Card Swipe/Tap’ located on the same
tab to enable this option. 2) To prompt for unordered items, you must configure a default order
mode by selecting either Maintenance > System > Order Entry Queue and an order mode from the
‘Default Order Mode’ drop-down list or selecting Maintenance > Hardware > Terminals and an
order mode from the ‘Order Mode’ drop-down list. Otherwise, the action fails. Related Options:
To enable the system to automatically display the tender screen for the corresponding card type,
select Maintenance > Payments > Tenders > Type tab and select ‘Always Display Tender Screen’
for the appropriate tender.
Hold for Payment — Temporarily captures the guest’s card data on the specific terminal for any
unordered items present on the check so you can retrieve later for payment. Use this option if you
are using a customer-facing proximity reader and allow the guest to enter their card information at
any tim, regardless if the order. Required Options 1) You must select ‘Auto Detect Credit Card
Swipe/Tap’ located on the same tab to enable this option. 2) To retrieve captured card data, access
Panel Editor and add the ‘Get Stored CC’ button function to a panel.
Page 95
Adding the Get Stored CC Button Function to a Panel
If you allow the guest to slide or tap their payment card using a customer-facing device prior to completing
their order, you must provide the cashier the ability to retrieve the payment card information with the ‘Get
Stored CC’ button function. If the cashier always handles the entering of payment card information, you do
not need to add the button function.
To add the Get Stored CC button function to a panel:
1. Access Panel Editor.
2. Select Open Existing Panel > Button Functions from the ‘Commands’ menu and select a panel,
such as ‘Tenders’ or ‘Manager Functions,’ for editing.
3. Double-click an available button. The Edit Button dialog box appears.
4. Select Get Stored CC from the ‘Function’ drop-down list.
5. Complete the text, background, and bitmap options using the Preview window as a guide.
6. Click OK to return to the panel with the new button.
7. Select Save All Panels from the ‘Commands’ menu and exit the Panel Editor function.
Using Automatic Detection to Temporarily Capture Card Data
When you use automatic detection to temporarily capture card data, the guest can slide any configured
payment card across the mag strip reader or tap their RFID encoded card against a proximity reader while
the cashier enters their order. The system searches the prefixes of the credit card type, determines the credit
card type, and captures the card data for the check on the specific terminal to be used later for tendering.
You must have the active check displayed in the guest check window for the system to capture the information and the feature does not work if any other screen is displayed, such as the Modify screen, the floating
logo screen, or any report screens. The check appears with a green box in the order entry queue.
The system uses the last instance of the captured data. For example, if the guest taps their card twice, the
system retains the second instance and disregards the previous attempt, even if a different card was used.
When the check is tendered with the captured data, the cardholder’s card information is removed from the
system and not kept in the terminal’s memory. The captured card data is also removed when the order has
been cleared, and when the End-of-Day (EOD) occurs with the check open.
The following procedure describes how to use automatic detection to temporarily capture card data with
the recommended configuration explained in this document.
To use automatic detection to temporarily capture card data:
1. The cashier starts a check and begins entering items as normal.
2. With the check displayed in the guest check window on the cashier’s side, the guest slides the
payment card across the magnetic stripe reader or taps the payment card against a RFID
reader. The system determines the card type and captures the card data in memory on the respective terminal only.
3. If the order is not yet finished, the cashier continues entering items until the order is complete.
Page 96
4. The cashier locates and selects the Get Stored CC button. The system automatically orders any
unordered items using the default order mode.
The check containing
captured payment data
appears with a green box
in the order entry queue.
Figure 57 FOH Order Entry Queue with Captured Payment Data
5. If the system is configured to display the tender screen for the respective card type so you can
adjust the payment or perform a split payment, the tender screen appears with the check amount
and the payment information populated on the screen.
Figure 58 Tender Screen
6. Touch OK. The system sends the information to the processor for authorization.
If the check is split after the payment information is captured, the card data remains associated with the
original check. You can manually move the payment from one split check to another, per normal functionality, and the guest must have their card data captured again for each check.
Page 97
Troubleshooting Automatic Detection to Temporarily Capture
Card Data
The following are troubleshooting tips for problems you may encounter with using automatic detection to
temporarily capture card data.
RFID or MSR Device Did Not Accept Card Data
If the RFID or MSR device did not accept the card data, one of the following might be the problem:
•
•
•
The RFID or MSR device is not functioning or configured incorrectly.
The POS system is not configured to automatically detect card types. To correct this, select Maintenance > Store Settings > User Interface group > Order Screen 2 tab and select ‘Auto Detect
Credit Card Swipe/Tab.’
The guest or the cashier tried to slide or tap their card when the active guest check is not displayed
in the guest check window.
Payment Begins Processing Before I Am Ready
If the system begins connecting to the processor immediately upon sliding or tapping the payment card,
then the action you have configured for ordered and unordered items is not configured properly. To correct
this, select Maintenance > Store Settings > User Interface group > Order Screen 2 tab and select ‘Hold for
Payment’ from the ‘Ordered Items’ and ‘Unordered Items’ drop-down lists.
Another tip you can use is select ‘Always Display Tender Screen’ for each tender. This enables the tender
screen for the detected tender to display and require the cashier to approve the amount; thereby safeguarding against any transactions being processed too early and keep multiple transaction fees from occurring.
The Default Order Mode Did Not Apply to Unordered Items
If the system cannot determine the order mode to apply to unordered or ordered items when the guest uses
their card, then a default order mode is not configured properly. To correct this, you must select either
Maintenance > System > Order Entry Queue and an order mode from the ‘Order Mode’ drop down list or
select ‘Maintenance > Hardware > Terminals and an order mode from the ‘Order Mode’ drop down list.
The Card Data Was Captured With the Wrong Check
If the card data is captured for the wrong check, such as when the guest taps their card while the cashier is
working with another check, the guest can tap their card again for the correct check and the system will
delete the previous instance and use the new instance of the captured card data.
Page 98
Enhancing QS Quick Combo Functionality and Design
Enhancing QS Quick Combo Functionality and
Design
Version
RFC Number
Products
POS v6.4
RFC 52639
Aloha QuickService
Audience
Store Managers
End Users
In today’s fast food industry, restaurants increasingly use innovative marketing and pricing strategies to
compete in the marketplace; therefore, the POS must accommodate these ever-changing concepts. In
Aloha QuickService, we made multiple enhancements to quick combo promotions. These enhancements
include:
•
•
•
•
Redesigning the quick combo dialog box.
Increasing the number of items per quick combo component.
Configuring item surcharges for all quick combo levels.
Supporting mixed level quick combos.
Redesigning the Quick Combo Dialog Box
With the recent expansion of features available for quick combos, and the already limited space available
on the existing quick combo dialog box, we redesigned the dialog box to a tabular format, to simplify the
configuration of quick combos.
In the process, we renamed several existing options for clarification and exposed hidden options that were
visible on the interface only when you selected a required option. For example, prior to v6.4, you had to
choose ‘Upsell 2’ from the ‘Upsell’ drop-down list to change the names on the ‘Surcharge,’ ‘Upsell
Name,’ and ‘Upsell Price’ options to reflect a second upsell level. With the redesign of the quick combo
dialog box, these options are no longer hidden.
Additionally, the Items tab introduces a tree view design that you expand and collapse so you can visually
manage long lists of component items, and their associated prices, in a more organized fashion.
Refer to the QuickService Reference Guide for more information on the redesign of the Quick
Combo dialog box.
Increasing Number of Items Per Quick Combo Component
Many quick service restaurants allow a guest to complete a quick combo meal by choosing from an extensive list of items, typically for beverages. Beginning in v6.4, you can configure up to 45 items per component; a number that more than exceeds the choices of most quick combos in use today.
Page 99
Configuring Item Surcharges for All Quick Combo Levels
An item surcharge is an existing feature that allows you to specify an additional cost for an item that is not
considered a base item of a quick combo. For example, you can add a $0.30 item surcharge when a guest
orders a shake in lieu of the normal drink choice to complete a quick combo.
Prior to v6.4, an item surcharge applied to both the Normal and Upsell 1 quick combo levels and you could
apply a different item surcharge to Upsell level 2. With the redesign of the quick combo dialog box in v6.4,
you can now configure a different item surcharge for each upsell level.
Supporting Mixed Upsell Levels for Quick Combos
A quick combo level refers to a set of qualifying items, usually separated by the size or portion of the item,
that make up a quick combo promotion. In the Aloha POS system, you can configure a Normal, Upsell 1,
and Upsell 2 quick combo level, each with a name branded to your restaurant, such as ‘Biggie Size,’
‘Texas Size,’ or ‘King Size.’ When you advance from one level to another, you can add an extra charge for
upgrading the quick combo.
Corporations often require their direct and franchise stores to report their sales based on quick combo levels, to motivate and stimulate sales. In these organizations, the stores receive more benefits for quick combos sold at the higher level.
Prior to v6.4, quick combos allow a guest to order items from the same quick combo level only. If a guest
orders an item from a different level, the order is no longer considered a quick combo. For example, the
guest orders the normal quick combo level sandwich and fries, but asks for an extra-large drink. The system prices each item according to its individual price, rather than grouping the items under the discounted
promotion price. The sale is not reported as a quick combo.
Beginning with v6.4, you can configure a quick combo in which the guest can mix and match items from
the different quick combo levels. The system reports the quick combo using the lowest level assigned to
the items included in the quick combo, unless you specify to exclude an item from the level determination.
See “Determining the Reporting Level” on page 101 for more information.
Enabling the Use of Mixed Upsell Levels
You must configure each quick combo to support mixed upsell levels, otherwise, the quick combo ‘breaks’
and prices the items individually when you try to mix and match items from different levels.
To enable the use of mixed upsell levels:
1. Select Maintenance > Payments > Promotions > Promotion tab.
2. Select a promotion from the drop-down list and press Enter.
3. Select Quick Combo from the ‘Type’ drop-down list.
Page 100
4. Click Type Specifics. The Quick Combo dialog box appears.
Figure 59 Quick Combo Promotion - Setup Tab
5. Select Allow Components With Mixed Upsell Levels.
Allow Components With Mixed Upsell Levels — Enables you to order items from all levels
defined for the quick combo without breaking the promotion. Related Options: 1) To allow the
system to automatically calculate size surcharges based on the price difference between items,
select ‘Auto Calculate Size Surcharge.’ 2) To exclude a component from mixed upsell levels,
select ‘Exclude from Mixed Levels Determination’ on the Components tab. 3) To specify an additional amount to charge when a guest chooses a larger size, type an amount in the ‘Size Surcharge’
text box on the Edit Quick Combo Item dialog box.
6.
7.
8.
9.
Click OK to return to the Promotions function.
Click Save.
Repeat this procedure for each quick combo for which you want to allow mixed upsell levels.
Exit the Promotions function.
Determining the Reporting Level
The system examines the items in the mixed level quick combo and uses the lowest level of all components
for reporting. Using a quick combo with three components, refer to the following table to determine the
lowest quick combo level for each example:
Component 1
Component 2
Component 3
Recorded Level
Normal
Upsell 1
Normal
Normal
Normal
Normal
Upsell 2
Normal
Normal
Upsell 1
Upsell 2
Normal
Upsell 1
Upsell 2
Upsell 1
Upsell 1
Upsell 2
Upsell 2
Upsell 2
Upsell 2
Page 101
You can also exclude a component from the level determination for quick combos that contain a common
component, such as a burger, across all levels. Using the same examples, Component 1 is excluded from
the mixed level determination:
Component 1
Normal *
Normal *
Component 2
Upsell 1
Normal
Component 3
Normal
Upsell 2
Recorded Level Normal
Normal
* Excluded from mixed level determination.
Normal *
Upsell 1
Upsell 2
Upsell 1
Normal *
Upsell 2
Upsell 1
Upsell 1
Normal *
Upsell 2
Upsell 2
Upsell 2
To exclude a component from mixed level determination:
1.
2.
3.
4.
5.
Select Maintenance > Payments > Promotions > Promotion tab.
Select a promotion from the drop-down list and press Enter.
Select Quick Combo from the ‘Type’ drop-down list.
Click Type Specifics. The Quick Combo dialog box appears.
Select the Components tab.
Figure 60 Quick Combo Promotion - Components Tab
6. Select Exclude from Mixed Levels Determination for each component you wish to exclude
when determining the quick combo level.
Exclude from Mixed Levels Determination — Does not include the component when determining the quick combo level for reporting. You must have at least one component included in the
mixed levels determination. Required Options: 1) To enable the quick combo to use mixed levels,
select ‘Allow Components with Mixed Upsell Levels’ on the Setup tab. 2) To specify an additional
amount to charge when a guest chooses a larger size, type an amount in the ‘Size Surcharge’ text
box on the Edit Quick Combo Item tab.
7. Repeat this procedure for each quick combo for which you want to exclude a component when
determining the quick combo level.
8. Click OK to return to the Promotions function.
9. Click Save and exit the Promotions function.
Page 102
Configuring a Size Surcharge
A size surcharge enables you to specify an additional cost when the guest orders a larger sized item from a
different quick combo level, without upgrading or downgrading the quick combo level. For example, if
you are currently on a normal quick combo level that includes Medium Fries, and the guest orders Large
Fries, which are an item from Upsell level 1, you can configure a $0.30 size surcharge for the Large Fries,
and retain the normal quick combo level without the guest also incurring an upsell charge.
To configure a size surcharge:
1.
2.
3.
4.
5.
6.
Select Maintenance > Payments > Payments > Promotions > Promotion tab.
Select a promotion from the drop-down list and press Enter.
Select Quick Combo from the ‘Type’ drop-down list.
Click Type Specifics. The Quick Combo dialog box appears.
Select the Items tab.
Select a component from the drop-down list. The list box populates with the item groups configured for the selected component.
7. Click Expand to view items within each group in a tree-view appearance.
8. Click Add to add a new item group or click Edit to edit an existing item group.
Figure 61 Edit Quick Combo Item Dialog Box
9. Type the amount to charge when the guest orders the item without upgrading the quick combo
level, in the ‘Size Surcharge’ text box. You can type a negative value for the size surcharge, to subtract from the item price, without downgrading the quick combo level.
10. Repeat Steps 8 and 9 for each item group.
12. Click Save.
13. Repeat this procedure for each quick combo for which you want to charge the guest a size surcharge.
14. Exit the Promotions function.
Page 103
The system records the appropriate upsell level and prices the quick combo accordingly. The following are
examples of typical menus that support mixed upsell levels with QuickService quick combos:
Value Meal #1 $3.99
Normal
Item
Upsell 1
Upsell 1 Charge
Size
Item
Burger
Cheeseburger
Med Fries
Med Drink
Small
Shake
Large Fries
Large Drink
Med Shake
$0.45
$1.00
Size
$0.20
Upsell 2
Upsell 2 Charge
$0.20
$0.20
$0.35 $0.20
Item
Double-meat
Burger
XLarge Fries
XLarge Drink
Large Shake
$2.00
Size
$0.30
$0.30
$0.30
$0.25 $0.30
Figure 62 Mixed Levels Quick Combo
In Figure 62, a guest can order Value Meal #1 at the normal level and receive a burger, medium fries, and
medium drink for a discounted price of $3.99. The guest can upgrade to ‘Upsell 1,’ which includes a
cheeseburger, large fries, and large drink, and the guest can upgrade to ‘Upsell 2,’ which includes a doublemeat burger, extra large fries, and extra large drink. With each upsell level, an extra $1.00 is charged. The
guest can also substitute the drink for a shake for an extra charge; thereby, increasing the price of the quick
combo. When the guest orders the following combinations, the system calculates the total price and
records the appropriate level.
Item 1 (Burger) Item 2 (Side)
Item 3 (Drink)
1.
Burger
Med Fries
2.
Burger
Large Fries
($0.20)
Large Drink
($0.20)
Med Shake
($0.35 + $0.20)
3.
Cheeseburger
Large Fries
4.
Cheeseburger
XLarge Fries
($0.30)
5.
Double-meat
Burger
XLarge Fries
Page 104
XLarge Drink
($0.30)
Large Shake
($0.25 + $0.30)
Large Shake
($0.25)
Price
Calculation
$3.99 + $0.20 =
$4.19
$3.99 + $0.20 +
$0.35 + $0.20 =
$4.74
$3.99 + $1.00 +
$0.30 = $5.29
$3.99 + $1.00 +
$0.30 + $0.25 +
$0.30 = $5.84
$3.99 + $2.00 +
$0.25 = $6.24
Quick Combo
Level
Normal
Normal
Upsell 1
Upsell 1
Upsell 2
In Figure 63, the menu shows the burger as the same item in all three quick combo levels. Ordinarily, this
configuration reports the level as ‘normal,’ because the burger component is at the lowest level.
Value Meal #1 $3.99
Normal
Item
Burger
Med Fries
Med Drink
Small
Shake
Upsell 1
Upsell 1 Charge
Size
Item
Burger
Large Fries
Large Drink
Med Shake
$0.45
$1.00
Size
Upsell 2
Upsell 2 Charge
$0.20
$0.20
$0.35 $0.20
Item
Burger
XLarge Fries
XLarge Drink
Large Shake
$2.00
Size
$0.30
$0.30
$0.25 $0.30
Figure 63 Mixed Level Quick Combo, Component Excluded
By excluding the burger component from mixed level determination, you can achieve an accurate quick
combo level. When the guest orders the following combinations, the system calculates the total price and
records the appropriate level.
Item 3 (Drink)
1.
Burger *
Med Fries
2.
Burger *
Large Fries
3.
Burger *
Large Fries
4.
Burger *
Large Fries
Large Drink
($0.20)
Med Shake
($0.35)
XLarge Drink
($0.30)
Large Shake
($0.25 + $0.30)
5.
Burger *
XLarge Fries
Large Shake
($0.25)
Price
Calculation
$3.99 + $0.20 =
$4.19
$3.99 + $1.00 +
$0.35 = $5.34
$3.99 + $1.00 +
$0.30 = $5.29
$3.99 + $1.00 +
$0.25 + $0.30 =
$5.54
$3.99 + $2.00 +
$0.25 = $6.24
Quick Combo
Level
Normal
Upsell 1
Upsell 1
Upsell 1
Upsell 2
Configuring System-Generated Size Surcharges
A system-generated size surcharge allows the system to automatically calculate the size surcharge based
on the price difference between the two upsell items. In this case, the system does not use the size surcharge price you enter in the Edit Quick Combo Item dialog box.
To configure a system-generated size surcharge:
1. Select Maintenance > Payments > Promotions > Promotion tab.
2. Select a promotion from the drop-down list and press Enter.
3. Select Quick Combo from the ‘Type’ drop-down list.
Page 105
4. Click Type Specifics. The Quick Combo dialog box appears.
Figure 64 Quick Combo Promotion - Setup Tab
5. Select Allow Components With Mixed Upsell Levels.
6. Select Auto Calculate Size Surcharge.
Auto Calculate Size Surcharge — Automatically calculates all size surcharges for the quick
combo based on the price difference between component items found in separate mixed levels.
Required Options: You must select ‘Allow Components With Mixed Upsell Levels’ on the Setup
tab to enable this option. Related Options: This option overrides any value you enter in the Size
Surcharge text box on the Edit Quick Combo Item dialog box.
8. Click Save.
9. Repeat this procedure for each quick combo for which you want to allow components with mixed
upsell levels and have the system automatically calculate the size surcharge based on the difference in price between the two component items.
10. Exit the Promotions function.
The following table lists the prices of the items, as defined in Item Maintenance, and the differences
between them.
Sides
Medium Fries
Large Fries
XLarge Fries
Page 106
Item Level
Price
$1.49
$1.99
$2.29
Difference
Drinks
Medium Drink
+ $0.50 Large Drink
+ $0.30 XLarge Drink
Item Level
Price
$0.99
$1.49
$1.79
Difference
+ $0.50
+ $0.30
Using this method with Figure 63, the system does not use the user-defined amounts entered for the size
surcharge, but rather generates the size surcharge based on the item level price.
Value Meal #1 $3.99
Normal
Upsell 1
Upsell 1 Charge
Item
Burger
Med Fries
Med Drink
Small
Shake
Size
NA
NA
NA
$0.45
NA
Burger
Large Fries
Large Drink
Med Shake
$1.00
Item Size
NA
NA
NA
$0.35
NA
Upsell 2
Upsell 2 Charge
Burger
XLarge Fries
XLarge Drink
Large Shake
$2.00
Item Size
NA
NA
NA
$0.25
NA
When a guest orders the following combinations, the system calculates the total price and records the
appropriate level.
Item 3 (Drink)
1.
Burger *
Med Fries
2.
Burger *
Large Fries
3.
Burger *
Large Fries
4.
Burger *
Large Fries
5.
Burger *
XLarge Fries
Large Drink
($1.49 -$0.99 =
$0.50)
Med Shake
($0.35)
XLarge Drink
($1.79 - $1.49 =
$0.30)
Large Shake
($0.25)
Large Shake
($0.25)
Price
Calculation
Quick Combo
Level
$3.99 + $0.50 = Normal
$4.49
$3.99 + $1.00 + Upsell 1
$0.35 = $5.34
$3.99 + $1.00 + Upsell 1
$0.30 = $5.29
$3.99 + $1.00 + Upsell 1
$0.25 = $5.24
$3.99 + $2.00 + Upsell 2
$0.25 = $6.24
Page 107
Requiring Manager Approval for Cash Drops
Version
RFC Number
Products
Audience
POS v6.4
RFC 54586
Aloha QuickService
Store Managers
The ‘Prompt for Cash Drop’ feature in Aloha QuickService displays FOH prompts to make a cash drop
when the drawer has reached a defined threshold. You can define a threshold for the initial prompt, for
every following subsequent prompt, and for when you are required to make a cash drop. In v6.4 and
higher, you can now configure the system to require manager approval for performing a cash drop.
To require manager approval for cash drops:
1. Select Maintenance > Store Settings > Financials group > Banks tab.
Figure 65 Store Settings - Financials Group - Banks Tab
2. Select Require Manager approval for Cash Drops.
Require Manager approval for Cash Drops — Displays the manager approval screen when you
are prompted to perform a cash drop from the FOH. Required Options: 1) You must type a value
higher than 0.00 in the corresponding text boxes to enable the ‘Prompt for Cash Drop’ feature. 2)
To allow an employee to approve a cash drop, you must select ‘Cash Drop’ in Maintenance >
Labor > Access Levels > Financial tab and assign the employee to the access level.
Page 108
To provide the ability to approve a cash drop:
1. Select Maintenance > Labor > Access Levels > Financial tab.
Figure 66 Store Settings - Access Levels - Financial Tab
2. Select Cash Drops.
Cash Drops — Allows all employees using this access level to either do a cash drop without manager approval or to approve a cash drop. Required Options: You must select ‘Require Manager
approval for Cash Drops’ in Maintenance > Store Settings > Financials group > Banks tab to
enable this feature.
3. Click Save and exit the Access Levels function.
Page 109
To perform a cash drop with manager approval:
When the expected cash in the drawer reaches the amount defined for any threshold, either the ‘Would you
like to do a Cash Drop now?’ screen or the ‘You are required to make a Cash Drop’ screen appears.
1. Touch Yes or OK to continue. If you do not have sufficient access to perform a cash drop, the manager approval screen appears.
Figure 67 FOH Manager Approval Screen for Performing a Cash Drop
2. A manager, or employee with sufficient access, must enter their password to continue with the
cash drop.
3. Complete the cash drop, as normal.
Page 110
Reprinting a Credit Card Voucher
Version
RFC Number
Products
Audience
POS v6.4.4
RFC 57208
Aloha QuickService
In v6.4.4, you can reprint a credit card voucher on demand in Aloha QuickService the same way you can in
Aloha TableService. This is especially helpful in a delivery environment where an order could be paid with
a credit card and the voucher is attached to the bag for reference. By the time the driver is ready to deliver
the food, the voucher could be lost, damaged, or soiled, and is not presentable for the guest to sign.
Reprinting a credit card voucher requires you to configure the Reprint CC Voucher button function in
Panel Editor; however, this raises a security risk for the cardholder. The following procedure instructs you
how to configure the button function inside of a script that includes the JIT Mgr Approval function. If you
do not want to display the Manager Approval screen when you reprint a credit card voucher, you can configure the Reprint CC Voucher button function as a stand-alone function.
To configure the ability to reprint a credit card voucher:
2. Select Open Existing Panel > Button Functions from the ‘Commands’ menu and select a panel,
such as ‘Tenders’ or ‘Manager Functions,’ for editing.
4. Select Script from the ‘Function’ drop-down list.
5. Click Edit to display the Edit Script dialog box.
6. Click Add.
7. Select JIT Mgr Approval from the Functions list and click OK.
Figure 68 Script Function with JIT Mgr Approval
Page 111
8. Select at least one access level that can perform the next button function in the list without displaying the Manager Approval screen. In this example, we want only the Manager to bypass the Manager Approval screen.
9. Click Add.
10. Select Reprint CC Voucher from the Functions list and click OK.
Figure 69 Scripted Function with Reprint CC Voucher
11. Click OK to complete the script and return to the Edit Button dialog box.
Figure 70 Completed Script for the Reprint CC Voucher Button Function
Page 112
To reprint a credit card voucher:
1. Recall the check and select the credit card payment from the guest check window.
2. Touch Reprint CC Voucher. If you do not have access to perform this function, the manager
approval screen appears.
3. A manager, or an employee with sufficient access, enters their ID number and touches OK. The
credit card voucher prints.
Page 113
Including Modifier Counts with Quantity-Priced Items
Including Modifier Counts with Quantity-Priced
Items
Version
RFC Number
POS v6.2.8 RFC 61162
Products
Audience
Aloha QuickService
Some environments, such as a catering environment, use the quantity item function to enter items in multiples; however, any associated modifier does not inherit the quantity placed on the item, and the system
reports the modifier as a single item on the PMix report. Also, if the modifier has a price associated with it,
the system prices the item only once, instead of quantifying the price in accordance with the parent item.
Beginning with v6.2.8, you can apply the item quantity to any associated modifiers, when an item uses
quantity pricing.
SCENARIO: A catering service offers a sandwich meal at $5.00, with an order of chips, and the option to
include bacon at $0.50. When the guest orders five sandwich meals with bacon, the caterer enters the
sandwich meal using quantity pricing. The transaction appears as one transaction, priced accordingly,
and the system reports the modifier as five for a total additional charge of $2.50.
To include modifier counts with quantity priced items:
1. Select Maintenance > Menu > Special Pricing > Quantity Pricing. The Quantity Pricing function appears.
2. Click Add. The Quantity Item Price dialog box appears.
Figure 71 Quantity Item Price Dialog Box
3.
4.
5.
6.
7.
8.
Select the item from the drop-down list.
Type the price per unit.
Type a descriptive name for the unit of measure.
Type the number of decimal points to use when you enter the quantity.
Select Affects Inventory.
Select Apply Item Quantity to Modifiers.
Apply Item Quantity to Modifiers — Applies the item quantity to any associated modifiers,
when you enter the item using quantity pricing. This is useful in certain environments, such as
catering, when you want to order large numbers of items on a single check, and have the system
quantify an associated modifier, accordingly. For example, if you place an order for 50 hamburgers
and include cheese as a modifier, the system orders 50 slices of cheese, as well, as part of the sin-
Page 114
gle order entry transaction. If you attach a price to the modifier, the system applies the appropriate
price for the designated quantity. This option ensures that the modifier quantity reflects correctly
in the PMix report. Required Option: You must select ‘Affects inventory’ to enable this option.
Related Option: If you select ‘Combine price with parent item,’ on the Modifier tab, the price of
the modifier appears as part of the item price on the guest check.
9. Click Save to return to the Quantity Pricing function.
10. Repeat the procedure for each modifier for which you want to inherit the item count for the associated parent item.
11. Exit the Quantity Pricing function.
To use modifier counts with quantity-priced items:
1. Log in to the FOH.
2. Enter an item configured with quantity pricing. The FOH quantity pricing screen appears.
Figure 72 Quantity Pricing Screen
3. Enter the quantity, using the numeric keypad, and touch OK. The item appears consolidated in the
guest check window. If you add any modifiers to the item, the modifier inherits the quantity of the
item and the system prices the modifier accordingly.
In Figure 73, the example on the left depicts a quantity-priced transaction of five sandwiches sold at $5.00
without the Bacon modifier of $0.50 inheriting the quantity of the parent item. The guest check window
displays five counts of the sandwich and five counts of bacon; however, only one bacon is charged. The
PMix report includes only one count of bacon.
Page 115
The example on the right depicts a quantity-priced transaction of five sandwiches sold at $5.00 with the
Bacon modifier of $0.50 inheriting the quantity of the parent item. The guest check window displays five
counts of the sandwich and all five counts of bacon are charged accordingly. The PMix report includes all
five counts of bacon.
Figure 73 Quantity Pricing with the Modifier Not Inheriting the Quanitity (Left) and Inheriting the Quantity (Right)
Page 116
Recalling the Oldest Open Check in the Queue
Recalling the Oldest Open Check in the Queue
Version
RFC Number Products
POS v6.1.19 RFC 64053
POS v6.2.12
POS v6.4.2
Aloha QuickService
Audience
When you touch the Recall Next Open button function in Aloha QuickService, the system displays the
next open check in the queue, based on the current check you have displayed. You can now change the
behavior of the Recall Next Open button to recall the oldest open check in the queue.
SCENARIO: You have checks 0001 to 0005 open in the queue, with 0001 as the check opened first and
0005 as the check last. Select check 0003 from the queue to display in the guest check window. Normally,
when you touch the Recall Next Open button the system recalls check 0004 since it is the next open check
after check 0003. Configure the system with the ‘Recall Next Open should recall the oldest check’ option to
recall check 0001, which is the oldest open check in the queue.
To configure the Recall Next Open button to recall the oldest open check:
1. Select Maintenance > Store Settings > User Interface > POS tab.
Figure 74 Store Settings - User Interface Group - POS Tab
2. Select Recall Next Open should recall the oldest check.
Recall Next Open should recall the oldest check — Changes the Recall Next Open button function to recall the oldest open check in the queue regardless of the check you are on. If cleared, the
Recall Next Open button function recalls the next sequential open check of the check displayed.
Required Option: You must access Panel Editor and add the Recall Next Open button function to
a panel.
Page 117
Refunding a Check with One Touch
Version
RFC Number
Products
Audience
v6.4.6
RFC 66462
Aloha QuickService
Store Manager
To perform a refund, you must start a new check in the ‘refund’ mode and re-enter the exact same items for
which you want to refund. This process is especially cumbersome when locating the items and ensuring the
refund check is a duplicate of the original check. In v6.4.6, you can now add the ‘Quick Refund’ button
function to a panel and allow the system to copy the original check to a new check in the ‘refund’ mode, all
in one button touch.
SCENARIO: A customer is unsatisfied with their meal for which they have already paid and wants a
refund. Ordinarily, the manager must ascertain the items the customer ordered, start a new check in the
‘refund’ mode, and re-enter the same items. With the Quick Refund feature, the manager can recall the customer’s check, touch ‘Quick Refund,’ and the system creates a copy of the check in the ‘refund’ mode.
Configuring the Quick Refund Feature
To configure the Quick Refund feature, the system uses the existing access level and tender options available to you to determine who can perform a refund and which tenders can be refunded. Then you must add
the new ‘Quick Refund’ button function to a panel in use.
To provide the ability to perform a refund:
1.
2.
3.
4.
5.
6.
7.
8.
Select Maintenance > Labor > Access Levels > Financial tab.
Select an access level, such as Manager, from the ‘Level’ drop-down list and press Enter.
Select Cash Refunds if you want this access level to perform refunds on cash transactions.
Select Non-Cash Refunds if you want this access level to perform refunds on non-cash transactions, such as room charges, additional charges, gift certificates, and others.
Select C.C. Refunds if you want this access level to perform refunds on credit card transactions.
Click Save.
Repeat this procedure for each access level that can perform a refund.
Exit the Access Levels function.
To configure a tender with the ability to be refunded:
1.
2.
3.
4.
5.
6.
Select Maintenance > Payments > Tenders > Tender tab.
Select a tender from the ‘Number’ drop-down list and press Enter.
Select Can Refund to allow the tender to be refunded.
Click Save.
Repeat this procedure for each type of tender that can be refunded.
Exit the Tenders function.
Page 118
To configure a Quick Refund button function:
2. Select Open Existing Panel > Button Functions from the ‘Commands’ menu and select a panel
for editing.
4. Select Quick Refund from the ‘Function’ drop-down list.
Figure 75 Quick Refund Button Function
Quick Refund — Enables you to copy a closed check to a new check in the ‘refund mode,’ all in
one action, as opposed to using the ‘Refund’ button function. The entries and subtotals display in
negative amounts. A ‘Close Check’ button function has to be selected to close the check. Required
Options: 1) You must access Maintenance > Labor > Access Levels > Financial tab and select
‘Cash Refunds,’ ‘Non-Cash Refunds,’ or ‘C.C. Refunds’ and assign the access level to the appropriate employees. 2) You must access Maintenance > Payments > Tenders > Type tab and select
‘Can Refund’ for each tender type you will allow to be refunded.
Using the Quick Refund Feature
When you use the Quick Refund feature, the system performs all the steps you would normally perform for
a regular refund. You must select a reason for the refund and have a close check button available to close
the check and exit the ‘refund mode.’
You cannot perform a refund on an open check.
Page 119
To use the Quick Refund feature:
2. Locate and select any of the recall buttons to display the check to refund in the FOH guest check
window. Note: You cannot use the Recall Next Open button function since the function does not
recall a closed check.
3. Locate and select Quick Refund. The Refund Reasons screen appears.
4. Select a refund reason. The system creates a new sequentially-numbered check and copies the
items onto the check in negative amounts (refund mode).
Figure 76 Aloha QuickService in Refund Mode
5. If you want to change the check at this point, you can do any of the following; however, you must
still close the check:
• Select the item and press Delete for all items for which you are not providing a refund.
• Select Delete All to clear the check to a $0.00 balance in the case where you accidentally
pressed the Quick Refund button.
6. Locate and select the Close Check button.
7. Refund the monies to the customer. If it is a credit card purchase and the customer wants their
account credited, you must swipe their card again and the system sends a request to the processor.
Page 120
Supporting Deferred Modifiers
Version
RFC Number
Products
Audience
v6.4.9
v6.5.2
RFC 67389
Aloha QuickService
Store Manager
End User
In Aloha QuickService, the current order flow requires you to ask a guest specific questions about each
item as you add the item to the check. With deferred modifiers, a guest can tell you their order without you
interrupting the order flow, and you can address any choices they must make, such as the type of sauce they
would like or their preferred beverage flavor, at the end of the ordering process.
Configuring Deferred Modifiers
When configuring deferred modifiers, we suggest you utilize a system-generated modifier screen to display the modifier choices for a group instead of the classic modifier screen, so you are able to view the onscreen guest check window and the modifier screen simultaneously in the FOH. You must also designate
the modifier groups for which you want to defer the choices until the end of the order.
Creating a System-Generated Modifier Screen
Creating a system-generated modifier screen requires you to create at least one ‘modifier panel’ template
in Panel Editor; however, you can create multiple modifier panel templates to accommodate your specific
needs. You then designate the template to use for each modifier group you wish to defer to later in the
ordering process.
To create a modifier panel template:
1.
2.
3.
4.
5.
6.
7.
8.
Access Panel Editor.
Select Create New Panel > Button Functions. The Panel Properties dialog box appears.
Type a name for the panel, such as ‘System-Generated Panel.’
Complete the rest of the dialog box, such as text, background, and bitmap properties, as appropriate. The system-generated screens inherit these attributes.
Click OK to create the panel.
Right-click on the panel and select New Button.
Complete the text, background, and bitmap properties, as appropriate. The buttons on the system-generated screens inherit these attributes, excluding the button name for the template panel.
Select Save All Panels and exit Panel Editor.
Designating the Modifier Groups to Defer
After you create a modifier panel template, you access Modifier Group Maintenance and assign the template to the respective modifier group, making the modifiers display in the FOH on system-generated
screens. Additionally, you must select ‘Deferred Modifier’ for each modifier group you want to address at
a later time in the ordering process.
Page 121
To designate which modifier groups to defer and the modifier panel to use when displaying them:
1. Select Maintenance > Menus > Modifier Groups.
Figure 77 Modifier Groups
2. Select a modifier group from the ‘Modifier Group’ drop-down list and press Enter.
3. Select Deferred Modifier.
Deferred Modifier — Adds placeholders in the guest check window for any required modifier to
allow the employee to proceed working with the order without interrupting the guest. The
employee can address the deferred modifier at a later time once the guest has given their entire
order. This only applies to first-level modifiers, not nested modifiers. When cleared, you must
address each required modifier before you can enter the next menu item. Related Options: 1) This
option disables the ‘Screen Flow Required’ option. 2) This option is disabled when you select
‘Exempt Order Entry Queue from Modifier Flow’ and you are using an exempted order entry
queue. 3) This feature works best with system-generated modifier screens. To do this, you must
configure a template panel in Panel Editor and select that panel from the ‘Modifier Panel’ dropdown list on the same tab.
4. Select Use Modifier Panel to enable the ‘Modifier Panel’ drop-down list.
5. Select the template panel you created for system-generated modifier screens from the ‘Modifier
Panel’ drop-down list.
6. Click Save.
7. Repeat this procedure for each modifier group for which you want to use deferred modifiers.
8. Exit the Modifier Groups function.
You typically fulfill a deferred modifier with a modifier screen, whether it is with a classic modifier screen
or a system-generated modifier screen; however, you can also fulfill a deferred modifier by selecting a
modifier from a panel set up with modifier buttons, providing the modifier you touch on the panel is part of
the modifier group for the currently selected deferred modifier. For example, a choice of sides is config-
Page 122
ured as a deferred modifier. When you enter a menu item with a choice of sides, the placeholder appears in
the guest check window. If you select the side item from a panel, the system replaces the placeholder with
the side item and fulfills the deferred modifier for you.
Using Deferred Modifiers
Each time you select an item in the FOH that has a deferred modifier, the menu item and a placeholder for
each deferred modifier group appear in the guest check window. This does not apply to a “nested” modifier, where a modifier modifies another modifier. For example, if you have an entree modified by a salad,
and the salad is modified by Ranch dressing, Ranch dressing does not operate as a deferred modifier and
the functionality behaves as normal.
When interfacing with a video device, you can configure a video queue to display items on the video
screen as they appear on the guest check window, using the ‘Display Items As Entered’ option in Maintenance > Hardware > Video Queues > General tab. When you use deferred modifiers, the modifier does not
appear on the video screen until it is addressed.
To enter an item with deferred modifiers:
2. With an active order on the screen, touch an item configured with a deferred modifier group.
The menu item and a placeholder for the deferred modifier group appear in the FOH guest check
window. Only one placeholder per deferred modifier group appears, regardless if you must choose
more than one modifier from the respective modifier group. The placeholder contains the name of
the modifier group, enclosed by two question marks.
Deferred modifier entry
Figure 78 Order Entry Screen with a Deferred Modifier
Page 123
3. When needed, touch the deferred modifier entry on the FOH guest check window. The modifier
screen for the deferred modifier appears.
In this example, the system-generated modifier
screen appears when you
select the deferred modifier from the FOH guest
check window.
Figure 79 Order Entry Scren with System-Generated Panel
4. If applicable, touch a modifier code, such as No or Side, to indicate how to serve the modifier.
5. Select the modifier from the list. The placeholder is replaced with the selected modifier.
6. Repeat steps 4 through 5 if you are required or allowed to enter more modifiers. It may be necessary to touch OK to return to the order entry screen.
When the check has more than one deferred modifier group, repeat steps 3 through 6.
Figure 80 Order Entry Screen with Fulfilled Deferred Modifier
Page 124
When you send the order to the kitchen and you have not fulfilled a deferred modifier, the modifier screen automatically appears for each deferred modifier.
Changing Deferred Modifiers
If you enter a wrong modifier, or the guest changes their mind, you can change a modifier that was originally deferred. Select the modifier from the guest check window and touch Modify. The classic modifier
screen appears for you to make modifications. The system uses the classic modifier screen regardless if
you are using system-generated modifier panels.
Repeating and Quantifying Deferred Modifiers
You can copy, or enter in multiples, an item with deferred modifiers, using the Repeat or Quantity buttons;
however, when you perform the action on a deferred modifier only, the message, “Cannot Change Quantities on a Modifier” appears.
Figure 81 Cannot Change Quantities on a Modifier Message
Deleting Deferred Modifiers
If you need to delete a modifier, or the guest changes their mind, you can delete a modifier that was originally deferred. Select the modifier from the guest check window and touch Delete. If the deletion still
meets the requirements for the modifier group, the modifier is removed from the guest check window. If
the deletion does not meet the minimum requirements of the modifier group, the classic modifier screen
appears for you to select a replacement. The system uses the classic modifier screen regardless if you are
using system-generated modifier panels.
Page 125
Displaying Upsell Prices on System-Generated Panels
Displaying Upsell Prices on System-Generated
Panels
Version
RFC Number
Products
Audience
v6.5.2
v6.4.9
RFC 67407
Aloha QuickService
Store Manager
End User
When you configure an upsell price for a modifier, or you configure quick combos with size and item surcharges, the additional charge now appears on system-generated panels in the FOH. This includes systemgenerated panels used for displaying menu item modifiers, quick combo modifiers, and quick combo substitutions, which makes responding to customer questions regarding the cost of adding or switching items
much easier.
In v6.4.9, the system now displays the upsell price on the following FOH screens:
•
•
•
System-generated modifier panel (Figure 82).
Quick combo modifier panel.
Quick combo substitution panel (Figure 82).
Figure 82 Quick Combo Substitution Panel (left) and System-Generated Modifier Panel (right)
Page 126
Making Beep Settings Available in QuickService
Making Beep Settings Available in QuickService
Version
RFC Number
Products
Audience
v6.4.8
RFC 69289
Aloha QuickService
Store Manager
The touch screen beep settings in Maintenance > Store Settings > User Interface group > POS tab enables
you to set the frequency and duration of audible signals generated by the Aloha system. The options have
always been available; however, they were accessible only through Aloha.ini. In v6.4.8, you can now use
the Aloha Manager interface to enable the touch screen beep settings in the QuickService product.
Editing the frequency and time values changes the tone and its duration. Typically, you use the default beep
setting values, unless instructed differently; however, you can disable the beep sound by typing a 1 in both
the ‘Frequency’ and ‘Duration’ text boxes.
You must also have a sound card installed on the FOH terminal for which you want to have audible beeps when you press a button on the FOH.
Figure 83 Store Settings - User Interface Group - POS Tab
Page 127
Supporting Included Modifiers
Version
RFC Number
Products
Audience
v6.4.9
RFC 69392
RFC 69462
Aloha QuickService
Store Manager
To help the cashier easily identify the modifiers that are included with an item, you can configure a bitmap
to appear on the modifier button. This bitmap can appear on the classic and system-generated modifier
screens, as well as the pizza screen. This provides the cashier with a visual indication of the default items
that the guest can modify and also helps prevent the sending of confusing or incorrect orders to the kitchen.
Configuring Included Modifiers
To configure a bitmap to appear on modifier buttons that are included with an item, you must activate the
feature in Store Settings and build a list of modifiers on which you want to display a bitmap in Item Maintenance.
To activate included modifiers:
1. Select Maintenance > Store Settings > User Interface group > Order Screen 1 tab.
Figure 84 Store Settings - User Interface Group - Order Screen 1 Tab
2. Select Use Included Modifiers.
Use Included Modifiers — Activates the ‘Included Modifiers’ feature that allows you to place a
bitmap on the modifier button for modifiers that come with an item so the cashier can appear
knowledgeable and answer pertinent questions from the guest. Required Options: You must
access Maintenance > Menu > Items > Included Modifiers tab and specify the modifiers that are
included for each menu item for which you want to display the ‘included modifiers’ bitmap.
3. Select a bitmap from the drop-down list.
Page 128
Bitmap — Associates a bitmap to display on the FOH for all modifiers configured to be included
with a menu item. Required Options: You must select ‘Use Included Modifiers’ on the same tab to
enable this option.
To specify included modifiers for a menu item:
1. Select Maintenance > Menu > Items > Included Modifiers tab.
Figure 85 Items - Included Modifiers Tab
2. Select a menu item from the ‘Number’ drop-down list and press Enter.
3. Click Add to add a new included modifier or click Edit to edit an existing included modifier. The
Add or Edit Included Modifier dialog box appears.
Figure 86 Add or Edit Included Modifier Dialog Box
4.
5.
6.
7.
8.
Select the modifier group in which the included modifier resides from the drop-down list.
Select the modifier you want to specify as an included modifier.
Select Included to allow an ‘included bitmap’ to appear on the modifier button.
Click Done to return to the Items function.
Repeat steps 3 through 7 for each modifier you want to be an included modifier for this menu
item.
Page 129
9. Repeat this procedure for each item for which you want to configure included modifiers.
The Up and Down buttons on the Included Modifiers tab are reserved for a future enhancement.
To delete an included modifier from a menu item:
1.
2.
3.
4.
Select Maintenance > Menu > Items > Included Modifiers tab.
Select the menu item from the ‘Number’ drop-down list and press Enter.
Select the included modifier from the list and click Delete.
Click Save.
Using Included Modifiers
With the ‘Included Modifiers’ feature, a bitmap appears on the modifier button each time the modifier
appears for the corresponding item. For example, the menu item, ‘Cheeseburger’ has two modifier groups,
Condiments and Cheeses, and ‘Cheese’ is an included modifier for ‘Cheeseburger,’ then ‘Cheese’ appears
with the ‘included’ bitmap on the modifier screen for both modifier groups.
The ‘Included Modifier’ bitmap appears on the following screens:
•
•
•
Classic modifier screen (Figure 87).
System-generated modifier screen (Figure 88).
Pizza modifier screen (Figure 89).
In this example of the classic
modifier screen, a check mark
bitmap is used for included
modifiers.
Figure 87 Classic Modifier Screen with Included Modifiers
Page 130
In this example of a systemgenerated modifier screen, a
check mark bitmap is used
for included modifiers
Figure 88 System-Generated Modifier Screen with Included Modifiers
Figure 89 Pizza Modifier Screen with Included Modifiers
Page 131
Displaying Modifier Code Bitmaps on Modifier Buttons
Displaying Modifier Code Bitmaps on Modifier
Buttons
Version
RFC Number
Products
Audience
v6.4.9
v6.5.2
RFC 69459
Aloha QuickService
Store Manager
End User
Modifier codes allow you to communicate more information about a modifier to the kitchen staff, such as
the preparation method, omissions, substitutions, and additions. When needed, you first select a modifier
code, such as No, Side, or Extra, then the modifier relating to the code. The modifier code precedes the
modifier on the screen and appears on the guest check, chit, and video screen.
To quickly identify special requests from the customer regarding modifications to menu items, you can
now associate a bitmap to each modifier code. This bitmap will appear on the next modifier button you
touch after touching the modifier code. The bitmap displays on top of any other bitmap you have configured for the button.
Assigning a Bitmap to a Modifier Code
You assign a bitmap to a modifier code, such as No, Side, Extra, and Add, in Modifier Code Maintenance.
Aloha QuickService also has a modifier code of ‘With’ that the system uses when you select a modifier
without a modifier code. When you assign a bitmap to the ‘Add’ modifier code, the system automatically
uses the same bitmap for the ‘With’ modifier code.
To assign a bitmap to a modifier code:
1. Select Maintenance > Menu > Modifier Codes.
Figure 90 Modifier Codes
Page 132
2. Select a modifier code from the ‘Number’ drop-down list and press Enter.
3. Select a bitmap from the drop-down list.
Bitmap — Associates a bitmap with the modifier code. The bitmap appears on the next modifier
button you touch after touching the modifier code.
4. Click Save.
5. Repeat this procedure for each modifier code for which you want to assign a bitmap.
6. Exit the Modifier Codes function.
Using Modifier Code Bitmaps on Modifier Buttons
A bitmap appears on the modifier button depending on the modifier code you select before touching the
modifier or when you touch the modifier by itself. Common bitmaps include a (+) sign for the ‘Add’ code,
(++) for the ‘Extra’ code, (X) sign for the ‘No’ code, and others.
If you are also using the ‘Included Modifier’ feature, which commonly uses a check mark bitmap
to indicate the modifier comes with the item, the system replaces the check mark with the bitmap
assigned to the modifier code.
The bitmap appears on the following screens:
•
•
•
Classic modifier screen.
System-generated modifier screen.
Pizza modifier screen.
Modifier code bitmaps have identical behavior on the classic and system-generated modifier screens.
To use a modifier code bitmap on the classic and system-generated modifier screens:
1. With an active order on the screen, touch a menu item that displays either the classic or systemgenerated modifier screen. If the modifier screen does not appear automatically, touch the Modify
Page 133
button. See Figure 91 for the classic modifier screen. See Figure 92 for the system-generated modifier screen.
This example of the classic
modifier screen displays
several different examples
of bitmaps associated with
the ‘No,’ ‘Extra,’ ‘Side,’
‘Only,’ and ‘Add’ modifier
codes, and a bitmap associated with the ‘included
modifiers’ feature.
Figure 91 Classic Modifier Screen
This example of the system-generated
modifier screen displays several different
examples of bitmaps associated with the
‘No,’ ‘Extra,’ ‘Side,’ and ‘Add’ modifier
codes.
Figure 92 System-Generated Modifier Screen
Page 134
2. Perform any of the following actions:
Touch a modifier button. The bitmap associated with the ‘Add’ modifier code, such as (+),
appears on the modifier button.
Touch a modifier code, such as No, Add, or Only, and then touch a modifier button. The bitmap
associated with the selected modifier code appears on the modifier button.
If you can only add one modifier to the item, the modifier screen exits immediately upon making
the selection and modifier code bitmaps do not appear.
3. Touch OK, if necessary, to exit the classic or system-generated modifier screen.
There are three different topping options with the pizza modifier screen: whole pizza, left half side, and
right half side. The modifier code bitmaps update depending on the state of the pizza. Additionally, the
pizza modifier screen only uses the ‘Add’ and ‘No’ modifier codes.
To use modifier code bitmaps on the pizza modifier screen:
1. With an order active on the screen, touch a menu item that displays the pizza modifier screen. If
the modifier screen does not appear automatically, touch the Modify button.
Modifier codes
Add and No.
Figure 93 Pizza Modifier Screen
2. Select a pizza crust from the left side of the screen.
3. Select a pizza size from the left side of the screen.
4. Using the whole pizza, perform any of the following options:
Touch a pizza topping modifier. The bitmap associated with the ‘Add’ modifier code, such as (+),
appears on the modifier button.
Touch a pizza topping modifier code, such as plus or minus, and then touch a modifier button.
The bitmap associated with the selected modifier code appears on the modifier button.
Page 135
5. Touch a pizza half to modify the left or right half of the pizza and perform the options as described
in Step 4. The modifier code bitmaps appear only for the respective half of the pizza.
6. Touch the whole pizza option. Only the modifier code bitmaps for the whole pizza appear on the
modifier buttons and the modifier code bitmaps for a specific half do not appear.
7. Touch OK, if necessary, to exit the pizza modifier screen.
Page 136
Supporting Tipshare Distribution
Version
RFC Number
Products
POS v6.4
RFC 14404
Aloha TableService
Audience
Store Managers
End Users
Tipsharing is common in a table service environment where employees who do not directly receive tips
from the guests, referred to as the support staff, are compensated for their efforts by sharing in the tips the
guests give to the wait staff. The practice is often a company policy that is either mandatory or strongly
suggested. Restaurants use tipsharing as a hiring incentive for the support staff, which ordinarily are less
desirable positions and have a higher turnover rate. These positions are indirectly tipped on top of the
wages they already receive; thereby, providing a more satisfied and long-lasting employee for the restaurant.
When the employees who contribute to the tipshare pool checkout, they contribute a portion of their tips
into a tipshare pool, based on a percentage of their sales. The positions who receive money from the tipshare pool generally include bussers, dishwashers, food runners, and greeters. Although bartenders are normally a higher-level position, they are also considered part of the support team because they prepare
alcoholic beverages for the wait staff.
Figure 94 Tipshare Diagram
A server can also contribute more than the default tipshare percentage to reward the support team or specific employees for making their job easier and allowing them to spend more time serving their guests. For
example, if a server feels that a busser cleaned their station extra well, the server can tip out more than the
allotted amount to that busser.
Page 137
Once the contributions are put into the tipshare pool, a manager can distribute the default tipshare contributions to the appropriate recipients.
You can configure the distribution to occur either daily or weekly, but not both.
Refer to the Tipshare Distribution Feature Focus Guide for complete information on configuring
and using Tipshare Distribution.
Page 138
Applying a Payment to Amount Due Before Gratuity
Applying a Payment to Amount Due Before
Gratuity
Version
RFC Number
Products
Audience
POS v6.4
RFC 24925
Aloha TableService
Store Managers
When you apply a partial payment to a guest check with an automatic gratuity, the system applies the partial payment to the check total and the automatic gratuity proportionately, based on the gratuity percentage.
With v6.4, you can now configure the payment to completely deduct from the sales amount before deducting from the gratuity amount.
SCENARIO: A restaurant provides banquet service and requires a pre-payment for the event. The cost of
the banquet is $3000.00, and with a 20% gratuity of $600.00, the check increases to $3600.00. The guest
pre-pays $1000.00 and the employee authorizes the pre-payment via the BOH. On the day of the event, the
employee enters the $3000.00 amount of the banquet, adds the gratuity amount of $600.00, and applies the
pre-payment amount of $1000.00. The check reflects an amount with $2000 left and gratuity of $600.00,
instead of $2150 and gratuity of $450.00.
To enable the system to apply a payment to the amount due before the gratuity amount:
1. Select Maintenance > Store Settings > Financials group > Gratuity tab.
Figure 95 Store Settings > Financial Group > Gratuity Tab
2. Select Use Gratuity.
3. Select Apply Payments to Amount Due Before Gratuity.
Apply Payments to Amount Due Before Gratuity — Enables the system to apply a payment
first to the amount of the check, after taxes, then to the gratuity amount. For example, if you have
a check total of $3000.00 with a 20% gratuity of $600.00, and you apply a pre-payment of
Page 139
$1000.00, the guest check and credit card voucher reflect a balance of $2000.00 with the $600.00
gratuity still intact. If you clear this option, the check reflects a balance of $2150.00 with a $450.00
gratuity. Required Option: You must select ‘Use Gratuity’ to enable this option.
For ease of simplicity, the following examples describe how the feature affects the guest check and reporting for a $100.00 purchase with $10.23 of taxes, a 20% gratuity amount of $20.00, and a $50.00 pre-payment. Figure 96 the guest check on the left shows the purchase and a gratuity amount of $20.00 before a
payment. The guest check on the right shows the pre-payment amount of $50.00.
Figure 96 Guest Check Before and After a Pre-Payment
Page 140
Figure 97 shows how the sales and gratuity amount differs on the credit card voucher after a $50.00 payment is applied. The voucher on the left shows an adjusted gratuity amount of $12.42 when you clear
‘Apply Payments to Amount Due Before Gratuity.’ The voucher on the right shows the gratuity amount of
$20.00 still intact when you select ‘Apply Payments to Amount Due Before Gratuity.’
Figure 97 Voucher with ‘Apply Payments to Amount Due Before Gratuity’ Cleared (left) and Selected (right)
When you select ‘Apply Payments to Amount Due Before Gratuity,’ the full gratuity amount appears only
for the payment that absorbs the gratuity and reduces the balance due to zero on all reports that display
payment information, even when the guest uses a different tender type for the pre-payment.
If you divide the check equally, using the ‘Equal Payments’ button on the FOH Close screen, the
system divides the gratuity amount equally.
Page 141
In Figure 98, the BOH Sales report shows the full gratuity amount of $20.00 for ‘M/C’ only, and $0.00 for
the pre-payment tender, ‘AdvDepRedm.’
Figure 98 BOH Sales Report with Split Payments and Gratuity
Similarly, the distributed amounts display on the BOH Payment report and the employee checkout report.
Page 142
Rerouting Video Group by Revenue Center
Version
RFC Number
POS v6.4.8 RFC 48748
Products
Audience
Aloha TableService
Store Managers
When you define the tables in your restaurant, you specify the revenue center in which the table resides.
The current option for rerouting a video group by tables only allows you to specify a range of tables to
reroute. If the tables in each revenue center are not numbered consecutively, it becomes difficult to reroute
the tables in a revenue center to another video group. With Aloha POS v6.4.8, you can now use the Reroute
Video by Revenue Center event to send orders and items designated to display on the monitors in one
video group to display on the monitors in another video group, by revenue center.
SCENARIO: A restaurant has a floorplan layout
in which the even-numbered tables are in the
Landing revenue center and the odd-numbered
tables are in the Patio revenue center. Kitchen A
prepares food for the Landing revenue center and
Kitchen B prepares food for the Patio revenue
center. After a certain time, Kitchen B closes and
Kitchen A then prepares the orders for both revenue centers. To properly reroute orders, configure
a Reroute Video Group by Revenue Center event
to send orders from the odd-numbered tables in
the Patio revenue center to display on the video
screens in Kitchen A at the time Kitchen B closes.
To configure an event for rerouting a video group by revenue center:
1.
2.
3.
4.
5.
Select Maintenance > System > Events. The System Events function tab appears.
Click Add Event. The Event Time & Type dialog box appears.
Select Reroute Video Group by Revenue Center from the ‘Event Type’ drop-down list.
Select Daily, or a time frequency of your choice.
Type the time the event will begin. To keep the event activated all day, leave the value at 00:00.
Page 143
6. Click OK. The Reroute Video Group by Revenue Center dialog box appears.
Figure 99 Reroute Video Group by Revenue Center Dialog Box
7.
8.
9.
10.
Select the revenue center you want to reroute using the event.
Select the video group to reroute from and the target video group.
Click OK. The event is added as an event task.
Exit the System Events function.
Page 144
Enhancing Gratuity on Sales
Version
RFC Number
Products
Audience
POS v6.4
RFC 51197
Aloha TableService
Store Managers
The Aloha system calculates gratuity on straight sales (net sales + inclusive taxes), by default. You can
optionally select the ‘On Tax’ option in Store Settings to also apply gratuity to exclusive taxes. When you
upgrade to v6.4, the ‘On Tax’ option on the Automatic Gratuity tab is no longer available. Two new
options, ‘Include Inclusive Tax’ and ‘Include Exclusive Tax,’ are now available so you can configure gratuity to apply to taxes for any tax environment, such as the following:
•
•
•
•
Net sales only
Net sales + inclusive taxes (existing functionality)
Net sales + exclusive taxes
Net sales + inclusive taxes + exclusive taxes (existing functionality)
To configure the system to apply gratuity on taxes:
1. Select Maintenance > Store Settings > Financials group > Gratuity tab.
Figure 100 Store Settings > User Interface > QuickService Tab
2. Select Use Gratuity.
3. Select Include Exclusive Tax, if you want the system to include the exclusive taxes when calculating the gratuity amount.
Include Exclusive Tax — Includes exclusive taxes when calculating the gratuity to apply to the
check. Required Option: You must select ‘Use Gratuity’ to enable this option. Related Option: To
display additional exclusive tax information on the guest check, select ‘Print Exclusive Tax Breakout On Check’ in Maintenance > Store Settings > International group > Taxes tab.
Page 145
4. Select Include Inclusive Tax, if you want the system to include the inclusive taxes when calculating the gratuity amount.
Include Inclusive Tax — Includes inclusive taxes when calculating the gratuity to apply to the
check. Required Option: You must select ‘Use Gratuity’ to enable this option. Related Option: To
display additional inclusive tax information on the guest check, select ‘Print ‘Inclusive Tax Breakout On Check’ in Maintenance > Store Settings > International group > Taxes tab.
For the following scenarios, apply these conditions:
•
•
•
Nachos is priced at $5.00, with an exclusive tax rate of 8.25%.
Beer is priced at $2.31, with an inclusive tax rate of 8.25%. The item price appears as $2.50 with
inclusive tax.
The gratuity percentage is 20%.
GRATUITY ON NET SALES ONLY: When you clear ‘Include Exclusive Tax’ and ‘Include Inclusive Tax,’
the system applies gratuity on net sales only. The system uses the following calculation to apply gratuity:
(taxable amount - exclusive taxes - inclusive taxes) x gratuity rate. As a result, the system calculates (5.00
+ 2.31) x 0.20 = $1.46.
Page 146
NACHOS
BEER
5.00
2.50
Subtotal
Tax
7.50
0.41
Total
Gratuity 20.00%
Total
7.91
1.46
9.37
Balance Due
9.37
GRATUITY ON NET SALES WITH INCLUSIVE TAXES: When you clear ‘Include Exclusive Tax’ and
select ‘Include Inclusive Tax,’ the system applies gratuity on net sales with inclusive taxes. The system uses
the following calculation to apply gratuity: (taxable amount + inclusive tax rate amount) x gratuity rate
amount. As a result, the system calculates (5.00 + 2.31 + 0.19) x 0.20 = $1.50.
NACHOS
BEER
5.00
2.50
Subtotal
Tax
7.50
0.41
Total
Gratuity 20.00%
Total
7.91
1.50
9.41
Balance Due
9.41
GRATUITY ON NET SALES WITH EXCLUSIVE TAXES: When you select ‘Include Exclusive Tax’ and
clear ‘Include Inclusive Tax,’ the system applies gratuity on net sales with exclusive taxes. The system uses
the following calculation to apply gratuity: (taxable amount + exclusive tax rate amount) x gratuity rate
amount. As a result, the system calculates (5.00 + 2.31 + 0.41) x 0.20 = $1.54.
NACHOS
BEER
5.00
2.50
Subtotal
Tax
7.50
0.41
Total
Gratuity 20.00%
Total
7.91
1.54
9.45
Balance Due
9.45
Page 147
GRATUITY ON NET SALES WITH EXCLUSIVE AND INCLUSIVE TAXES: When you select ‘Include
Exclusive Tax’ and ‘Include Inclusive Tax,’ the system applies gratuity on net sales with exclusive and
inclusive taxes. The system uses the following calculation to apply gratuity: (taxable amount + exclusive
tax rate amount + inclusive tax rate amount) x gratuity rate amount. As a result, the system calculates
(5.00 + 2.31 + 0.41 + 0.19) x 0.20 = $1.58.
Page 148
NACHOS
BEER
5.00
2.50
Subtotal
Tax
7.50
0.41
Total
Gratuity 20.00%
Total
7.91
1.58
9.49
Balance Due
9.49
Requiring Guests to Pay Inclusive Taxes on Comps and
Requiring Guests to Pay Inclusive Taxes on
Comps and Promotions
Version
RFC Number
Products
Audience
POS v6.4
RFC 51212
Aloha TableService
Store Managers
In some countries, a guest still pays the tax on inclusively taxed items, even when the price of the item is
reduced because of a comp or a promotion. For example, when you comp a $2.00 bottle of beer, 0.15 of
which is an inclusive tax, the guest must still pay the $0.15 tax on the item.
COMP SCENARIO: A guest purchases a $2.00 bottle of beer, $0.15 of which is an inclusive tax. The manager applies a 100% discount to the beer item. If the comp is configured to apply taxes before you apply
the comp, the guest must pay $0.15. If the comp is configured to apply taxes after you apply the comp, there
is no tax for the guest to pay.
PROMOTION SCENARIO: A guest purchases a $2.00 bottle of beer, $0.15 of which is an inclusive tax.
The manager applies a $0.50 discount to the beer item. If the promotion is configured to apply taxes before
you apply the promotion, the guest must pay $0.15. If the promotion is configured to apply taxes after you
apply the promotion, the guest must pay $0.11 in inclusive taxes (2.00 - 0.15 - 0.50) x 8.25% = 0.11.
Configuring Comps and Promotions to Require Guests to Pay
Inclusive Taxes
For optimal use, perform the following procedures to configure comps and promotions to require guests to
pay the inclusive tax. You can also configure the text that displays for inclusive tax information on reports.
To require guests to pay inclusive taxes when you apply a comp:
1. Select Maintenance > Payments > Comps > Taxes tab.
Figure 101 Maintenance > Payments > Comps > Taxes Tab
Page 149
Requiring Guests to Pay Inclusive Taxes on Comps and Promotions
2. Select a comp for which you want the guest to pay the inclusive tax amount.
3. Select Guest Pays Tax.
Guest Pays Tax — Requires guests to pay exclusive taxes and inclusive taxes on items discounted
due to an applied comp. If this option is cleared, the restaurant absorbs the cost of the tax for the
discounted items. Related Option: To require guests to pay exclusive taxes only, select ‘Exclude
Inclusive Tax.’
Prior to v6.4, the ‘Guest Pays Tax’ option required the guest to pay the exclusive tax amount
only. Starting with v6.4, the option requires the guest to pay both exclusive and inclusive taxes.
4. Clear Exclude Inclusive Tax.
Exclude Inclusive Tax — Requires guests to only pay the exclusive tax on items discounted due
to an applied comp. If this option is cleared, the guest pays both exclusive and inclusive taxes for
the discounted item. Required Options: 1) You must select ‘Guest Pays Tax’ to enable this option.
2) You must also select ‘Tax Comp Amount,’ and a tax from the ‘Tax ID’ drop-down list to calculate taxes after you discount an item with an applied comp. Related Options: 1) To display inclusive tax information on the guest check, select both ‘Use Inclusive Tax Breakout’ and ‘Print
Inclusive Tax Breakout on Check.’ in Maintenance > Store Settings > International group > Taxes.
2) If you select ‘Include Inclusive Taxes’ in Maintenance > Store Settings > Financials group >
Gratuity tab, the system includes the inclusive tax collected from the guest when calculating the
gratuity. 3) If you select a tax from the ‘Tax ID’ drop-down list in Maintenance > System > Order
Modes, the order mode option overrides the tax ID you configure for the guest to pay.
5. Select Tax Comp Amount if you want to calculate taxes after you discount an item with an
applied comp.
6. If you select ‘Tax Comp Amount,’ select the tax to apply to the discounted amount from the ‘Tax
ID’ drop-down list.
We recommend using an inclusive tax dedicated to taxing the comp and promotion amount. If
this information is required by the government, you can easily send the monies collected from the
guest on inclusive taxes without extrapolating from other taxes.
7. Click Save and exit the Comps function.
Page 150
To require guests to pay inclusive taxes when you apply a promotion:
1. Select Maintenance > Payments > Promotions > Taxes tab.
Figure 102 Maintenance > Payments > Promotions > Taxes Tab
2. Select a promotion for which you want the guest to pay the inclusive tax amount.
3. Select Guest Pays Tax.
Guest Pays Tax — Requires guests to pay exclusive taxes and inclusive taxes on items discounted
due to an applied promotion. If this option is cleared, the restaurant absorbs the cost of the tax for
the discounted items. Related Option: To require guests to pay exclusive taxes only, select
‘Exclude Inclusive Tax.’
Prior to v6.4, the ‘Guest Pays Tax’ option required the guest to pay the exclusive tax amount
only. Starting with v6.4, the option requires the guest to pay both exclusive and inclusive taxes.
4. Clear Exclude Inclusive Tax.
Exclude Inclusive Tax — Requires guests to only pay the exclusive tax on items discounted due
to an applied promotion. If this option is cleared, the guest pays both exclusive and inclusive taxes
for the discounted item. Required Options: 1) You must select ‘Guest Pays Tax’ to enable this
option. 2) You must also select ‘Tax Applied Before Promotion,’ and a tax from the ‘Tax ID’ dropdown list to calculate taxes after you discount an item with an applied promotion. Related
Options: 1) To display inclusive tax information on the guest check, select both ‘Use Inclusive Tax
Breakout’ and ‘Print Inclusive Tax Breakout on Check.’ in Maintenance > Store Settings > International group > Taxes. 2) If you select ‘Include Inclusive Taxes’ in Maintenance > Store Settings
> Financials group > Gratuity tab, the system includes the inclusive tax collected from the guest
when calculating the gratuity. 3) If you select a tax from the ‘Tax ID’ drop-down list in Maintenance > System > Order Modes, the order mode option overrides the tax ID you configure for the
guest to pay.
Page 151
5. Select Tax Applied Before Promotion if you want to calculate taxes after you discount an item
with an applied comp.
6. If you select ‘Tax Applied Before Promotion,’ select the tax from the ‘Tax ID’ drop-down list to
apply to the discounted amount.
We recommend using an inclusive tax dedicated to taxing the comp and promotion amount. If
this information is required by the government, you can easily send the monies collected from the
guest on inclusive taxes without extrapolating from other taxes.
7. Click Save and exit the Promotions function.
To configure the text to use for inclusive taxes collected on discounted items:
1. Select Maintenance > Store Settings > Printing > Check Content 1 tab.
Figure 103 Store Settings > Printing Group > Check Content 1 Tab
2. Select “Discount Tax” Text.
“Discount Tax” Text — Replaces the default text used to indicate inclusive taxes collected from
the guest for items discounted due to an applied comp or promotion. The text appears on the guest
check, checkout reports, and sales report. If cleared, the system uses the text ‘Discount Tax.’
Required Options: 1) To use this option with comps, you must select ‘Guest Pays Tax’ and clear
‘Exclude Inclusive Tax’ in Maintenance > Payments > Comps > Taxes tab. 2) To use this option
with promotions, you must select ‘Guest Pays Tax’ and clear ‘Exclude Inclusive Tax’ in Maintenance > Payments > Promotions > Taxes tab.
Page 152
FOH Behavior When Guests Pay Inclusive Taxes on Comps
and Promotions
With the ‘Exclude Inclusive Tax’ option, you can configure whether or not the guest pays the inclusive tax
when you apply a comp or promotion. Figure 104 shows three examples when using inclusive taxes:
Figure 104 Inclusive Tax Examples when Guest Pays on Discounted Amount
Left guest check: Shows no comp or promotion applied to the check.
Middle guest check: Shows the item with a 100% comp. Because the comp is configured to apply the tax
before the discount with the ‘Tax Comp Amount’ option, the system requires the guest to pay the inclusive
tax based on the full price of the item. The inclusive tax the guest must pay (Discount Item Tax) is separated from the exclusive tax and appears in the FOH guest check window.
Right guest check: Shows a check with a BOGO promotion that reduces the second item to $0.50.
Because the promotion is configured to apply the tax before the discount with the ‘Tax Applied After Promotion’ option, the system requires the guest to pay the inclusive tax based on the full price of the item.
The inclusive tax the guest must pay (Discount Item Tax) is separated from the exclusive tax and appears
in the FOH guest check window.
Reporting the Inclusive Tax the Guest Pays on Comps and
Promotions
When you select ‘Guest Pays Tax’ and clear ‘Exclude Inclusive Tax,’ for either a comp or promotion, the
system adds a new line to the guest check, checkout report, and FOH Restaurant Sales report to show the
inclusive tax amount collected from the guest. The line is configured by the ‘“Discount Tax” Text’ text
box.
Page 153
Figure 105 shows the configurable line displayed on the checkout report
Figure 105 Checkout Report
Page 154
Customizing Submenus in TableService
Version
RFC Number
Products
Audience
POS v6.4
RFC 54070
RFC 58411
Aloha TableService
Store Managers
The Aloha TableService product uses hard-coded screens, known as ‘classic,’ to maintain familiarity and a
consistent screen flow for employees using the system. The FOH Order Entry screen is the main screen
employees use to enter orders and is divided into designed sections to hold function buttons and tools for
order entry, some of which you cannot customize. As of v5.231, you can customize the action item area
located on the bottom right row, and as of v6.4, you can now customize the submenu area with a Submenu
Panel.
Configuring a Submenu Panel in TableService
To configure a Submenu Panel in TableService, you must perform the following procedures:
•
•
•
Create a Submenu Panel.
Add buttons to a Submenu Panel.
Replace a classic submenu with a Submenu Panel.
Comparing Submenu Panels to Classic Submenus
There are many reasons to use a Submenu Panel over a hard-coded ‘classic’ submenu.
Smart Item and Smart Select Buttons — You can only use Smart Item and Smart Select buttons, commonly used for beverages that you sell in different sizes, with a Submenu Panel. Smart Item and Smart
Select buttons reduce the number of buttons needed on a screen. You cannot use Smart Item and Smart
Select buttons with ‘classic’ submenus.
Bitmaps — Unlike a ‘classic’ submenu, a Submenu Panel allows you to place a bitmap, such as the store’s
logo, on the submenu itself. Because you create a Submenu Panel using Panel Editor, you can place a bitmap on a submenu item button in a much easier fashion and you can place a bitmap on an unassigned button that is not associated with a menu item.
We recommend you balance the use of bitmaps depending on your processor
speed.
Colorization — Although you can employ installed FOH themes or use an enhanced graphical interface
(EGI) with a ‘classic’ submenu, a Submenus Panel allows you to add any background color you want. For
example, if your brand colors are pink and yellow, you can customize your submenus with alternating pink
and yellow backgrounds. A Submenu Panel also allows you to set the color on a submenu item button. For
Page 155
example, you can set all your salad items to green and all your hot items to orange. We recommend using
the colors red and blue sparingly, as the system uses these colors for indicators on the button with other
features, such as recipes and Item Availability.
We recommend you balance the use of colorization depending on your processor
speed. Setting the background color of a Submenu Panel to ‘transparent’ helps
eliminate slow screen redrawing.
Creating a Submenu Panel
You must create a Submenu Panel using Panel Editor.
We recommend you select ‘Transparent’ so the panel maintains the same colorization of the FOH
Order Entry screen. Otherwise, you may see a noticeable difference when passing between a
classic submenu and a Submenu Panel. Additionally, setting the Submenu Panel to transparent
reduces the chance of the FOH screen flickering during the redrawing of the panel on terminals
with lower processing speed.
To create a Submenu Panel in TableService:
1. Select Maintenance > System > Floor Plan > Panel Editor to access Panel Editor.
2. Select a desktop size and click OK.
3. From the Commands menu, select Create New Panel > Submenu Panel.
Figure 106 Create New Panel Drop-down List
Page 156
The Edit Panel - Submenu Panel dialog box appears.
Figure 107 Edit Panel - Submenu Panel Dialog Box
When using a Submenu Panel, the panel is in a fixed position on the screen and you cannot add a
border; therefore, the ‘Fixed Position’ and ‘No Border’ options on the Edit Panel - Submenu
Panel dialog box are disabled.
4. Type a name, up to 15 characters, for the panel. The text, ‘Unnamed Panel’ is the default panel
name.
5. Set the remaining panel attributes the same as you would any other panel.
6. Click OK. A Submenu panel appears on the right side of the Panel Editor workspace in a fixed
position.
Figure 108 Panel Editor Workspace With a Submenu Panel
Page 157
Refer to the TableService Panel Editor Essentials User Guide for more information on creating a
panel using Panel Editor.
Adding Buttons to a Submenu Panel
You can add up to 50 buttons to a Submenu Panel, either separately or as a group. To add a separate button,
select New Button from the Commands menu, or hold down the left mouse button and drag the cursor
across the panel in a box pattern. As the button forms, release the left mouse button. To add a group of buttons, select Buttons > Layout Panel Buttons. The Edit Button dialog box defines the function performed by
the button and its properties. The function determines the behavior of the button and how the FOH operates, regardless of any text, bitmap, and color selections. When you select a function, the button text
assumes the name of the function. Every new button has an Unassigned function as default. Select a function and click OK.
Although you can alter the number of columns and rows of buttons you can use on a ‘classic’ submenu, the
buttons lay on the ‘submenu area’ in a numbered order and all with the same size. With a Submenu Panel,
you can place buttons on the submenu with any size and in any order, and use any number of columns or
rows. For example, if you want to bring attention to a top selling item, or a row of Smart Select functions,
you can resize the buttons to double their size.
You can only add buttons to a Submenu Panel using these button functions:
•
•
•
•
•
•
•
•
•
•
•
Bitmap
Chain
Modifier Code
Order Item
Order Modifier
Order
PLU/SKU
Script
Smart Item
Smart Select
Unassigned
Refer to the TableService Panel Editor Essentials User Guide for more information on adding
buttons to a panel using Panel Editor.
Replacing a Classic Submenu with a Submenu Panel
After you create the Submenu Panel in Panel Editor, you must tell the system which panel to use for replacing the ‘classic’ submenu.
Page 158
Replacing a ‘classic’ submenu with a Submenu Panel:
1. Select Maintenance > Menu > Submenus.
Once you replace the
‘classic’ submenu with a
Submenu Panel, you cannot add a submenu button
to the classic submenu in
Submenu Maintenance.
Figure 109 Submenu Function
2. Type an unused number or select an existing number in the ‘Submenu ID’ drop-down box and
press Enter.
3. Type a descriptive short name for the submenu to appear on the FOH button.
4. Type a descriptive long name for the submenu.
5. Select a Submenu Panel from the ‘Submenu Panel’ drop-down list. If you did not create a Submenu Panel, click Panel Editor to access the Panel Editor function.
6. Click Save. A message appears, warning you that you are replacing the selected ‘classic’ submenu
with a Submenu Panel and any existing buttons configured on the submenu will be discarded.
Figure 110 Submenu Panel Replacement Warning
7. Click OK to replace the ‘classic’ submenu with a Submenu Panel, or click Cancel to cancel the
action.
Be aware when you replace an existing ‘classic’ submenu with a Submenu Panel,
you lose all buttons that reside on the selected ‘classic’ submenu, without the
ability to undo the action.
8. Exit the Submenu function when finished.
Page 159
FOH Behavior with a Submenu Panel
After you create a Submenu Panel in Panel Editor and assign the panel in Submenu Maintenance, the Submenu Panel replaces the ‘classic’ submenu on the FOH Order Entry screen. The height of the Submenu
Panel adjusts for employees with bartender functionality.
The height of the
submenu area
adjusts for employees with bartender
functionality.
Submenu Panel.
Figure 111 Order Entry Screen with a Submenu Panel
Submenu Panel Caveats
Submenu Panels do not support the following TableService features, commonly used with ‘classic’ submenus:
•
•
•
•
•
The ‘Suggested Selling Category’ feature groups items so they blink on a ‘classic’ submenu to
attract attention and encourage sales of these items. This feature is not supported with a Submenu
Panel.
In Access Levels Maintenance, you can allow an employee access to another menu via the ‘Assign
Menu’ option. When you assign another menu to the employee, the ‘Other Menu’ button appears
on each ‘classic’ submenu, for the respective check. The ‘Other Menu’ button does not appear on a
Submenu Panel.
In AutoMenu Maintenance, you can replace an entire ‘classic’ submenu. This does not apply to a
Submenu Panel.
In Events Maintenance, you can set up a ‘Set Submenu Item,’ ‘Set Auto Menu,’ and ‘Activate
Panel Button’ event to activate certain items, menus, or buttons on ‘classic’ submenus, at specific
times of the day. These events do not apply to a Submenu Panel.
Since Smart Items and Smart Select buttons are intended to reduce the number of buttons you
place on a panel, some buttons do not appear on the Submenu Panel, by design. For example, if
you sell a Kids Coke, Small Coke, Medium Coke, and a Large Coke, with Medium Coke as the
default selection, then Medium Coke appears on the submenu and the other three selections are not
visible. When you use the Recipe feature with Smart Items, the three red asterisks appear on the
Page 160
button only if the default selection has a recipe attached. When you use the Item Availability feature with Smart Items, the item and quantity on hand counters appear on the button designated as
the default selection only.
Page 161
Supporting Smart Item and Smart Select in TableService
Supporting Smart Item and Smart Select in
TableService
Version
RFC Number
Products
Audience
POS v6.4
RFC 54070
RFC 58411
Aloha TableService
Store Managers
The Smart Item and Smart Select button functions are a valuable menu building device in the QuickService
product. They work in conjunction with each other to support items sold by various sizes and portions,
without having to add each item to the panel. The Smart Select button function defines the assorted sizes in
the group. The Smart Item button function specifies the items associated with each button, and designates
the default size to order if the Smart Select button is not selected first. This enables you to create smaller,
less confusing panels, even if it does not reduce the number of items you must create in Item Maintenance.
In v6.4, you can now use the Smart Item and Smart Select button functions in the TableService product,
using a Submenu Panel to replace the hard-coded ‘classic’ submenus on the FOH Order Entry screen.
The following are examples of items you sell in quantities for which you can use the Smart Item and Smart
Select feature.
Small Shirt
Medium Shirt
Large Shirt
8 oz Ribeye
12 oz Ribeye
16 oz Ribeye
12 oz Coca Cola®
20 oz Coca Cola
2 Liter Coca Cola
Side Salad
Lunch Salad
Dinner Salad
Side Carrots
Large Carrots
Container Carrots
You must also consider how you are entering items in Item Maintenance and tracking them with an inventory program. You must create an item for each size or portion you are selling, which is required for most
inventory programs. This type of setup involves multiple submenus, and pages of submenus, and searching
for the correct item slows down the speed of service. If you configure the different sizes using modifiers,
you cannot use the Smart Item and Smart Select feature.
The Smart Item and Smart Select button functions greatly help in configuring items you sell in bar environments that sell draft beer in various quantities, such as 1/2 pint, pint, shots, double-shots, carafes, pitchers, and more. For example, a bar sells the following draft beers by the 1/2 pint, pint, and pitcher:
•
•
Guinness®
Shiner Bock®
•
•
Budweiser®
Michelob Ultra®
•
•
Fat Tire®
Blue Moon®
Without using the Smart Item and Smart Select button functions, you would have to add the following item
buttons to a ‘classic’ submenu:
Guinness 1/2 Pint
Shiner Bock 1/2 Pint
Budweiser 1/2 Pint
Michelob Ultra 1/2 Pint
Fat Tire 1/2 Pint
Blue Moon 1/2 Pint
Page 162
Guinness Pint
Shiner Bock Pint
Budweiser Pint
Michelob Ultra Pint
Fat Tire Pint
Blue Moon Pint
Guinness Pitcher
Shiner Bock Pitcher
Budweiser Pitcher
Michelob Ultra Pitcher
Fat Tire Pitcher
Blue Moon Pitcher
Supporting Smart Item and Smart Select in TableSer-
Using the Smart Item and Smart Select button functions with a Submenu Panel, you need only add the following buttons:
Smart Select buttons
1/2 Pint
Pint
Pitcher
Smart Item buttons
Guinness
Shiner Bock
Budweiser
Michelob Ultra
Fat Tire
Blue Moon
Rather than adding a button for each possible size (18), you can replace a ‘classic’ submenu with a Submenu Panel and consolidate the number of buttons to nine: six buttons for the types of draft beer, and three
buttons for the sizes. For each additional draft beer you sell, only one more button is required; therefore,
the larger the variety that is offered, the more beneficial this feature becomes.
Smart Item buttons
Configuring Smart Item and Smart Select Buttons in
TableService
You can only add the Smart Item and Smart Select button functions to a Submenu Panel. They must be set
up correctly in regards to the ‘Smart Group’ and ‘Smart Element’ options on the respective dialog boxes.
Use the ‘Smart Group’ number to collect the Smart Item and Smart Select button functions within the same
group. When you configure the Smart Item buttons, you must use a different group number for each type of
Page 163
item you sell in different sizes. For example, set up group one for the different sizes in which you sell beer,
group two for fries, group three for steaks, and group four for drinks. The ‘Smart Element’ number identifies the item used by the Smart Select button for that specific size.
Figure 113 Relationship Between Smart Item (bottom left) and Smart Select Buttons
Using Guinness as an example, Figure 113 shows the proper setup between a Smart Item and a Smart
Select button. Configure each Smart Item within the group in the same manner. Add a Smart Select button
for each size in which you offer the item, and specify the element to which it corresponds in the Smart Item
button function.
Page 164
To add a Smart Select button:
1. Using a Submenu Panel, select New Button from the Commands menu to display the Edit Buttons
- TableService dialog box.
2. Select Smart Select from the ‘Function. drop-down list. Additional options appear.
Figure 114 Smart Select Button Function
3. Type the smart group number associated with the size in the Smart Item button definition.
4. Type the smart element associated with the size in the Smart Item button definition. A smart element could refer to sizes, fluid levels, and more.
5. Enter a unique name as the Text, or accept the default description.
6. Complete the available button attributes on the left side of the Edit Button dialog box, such as
color, font, bitmap, and more.
7. Click OK to add the button to the Submenu Panel.
8. Repeat the procedure for each Smart Select button you need to create, such as 1/2 Pint, Pint,
Pitcher, and more.
To add a Smart Item button:
1. Using a Submenu Panel, typically the same one on which you added the Smart Select buttons,
select New Button from the Commands menu to display the Edit Buttons - TableService dialog
box.
Page 165
2. Select Smart Item from the ‘Functions’ drop-down list. Additional options appear.
Figure 115 Smart Item Button Function
3. Select the smart group associated with the Smart Select button function.
4. Select the smart element to designate the corresponding ‘Smart Element,’ as defined in the Smart
Select button function. For example, Item 016091 1/2 Pint Guinness corresponds to the Smart Element 1 (1/2 Pint).
5. Select the Smart Item to designate the item to associate with the ‘Smart Group’ and ‘Smart Element.’ You must create an item for each variation in Maintenance > Menu > Items and place the
item in its respective order in the drop-down lists. For example, the employee touches a FOH
Pitcher Smart Select button, then a Guinness Pitcher Smart Item button to ring up a Guinness
Pitcher.
6. Select the radio button next to each Smart Item and select one of the following pricing methods
for the selected item.
Price — Designates the button price should be used to price the item. Enter the button price in the
text box to the right.
Use Item Price — Designates the price of the item as entered in Item Maintenance is used to price
the item.
Price Level — Designates the price established in the assigned price level should be used to price
the item. Select the price level from the drop-down list to the right.
7. Select the Default Item to designate as the default Smart Item selection when a Smart Select button is not chosen first in the FOH. For example, if you select Guinness Pint as the default size, the
employee can touch the Guinness item button without a preceding Smart Select button to enter a
Guinness Pint.
8. Enter a unique name as the Text, or accept the default description.
Page 166
9. Complete the available button attributes on the left side of the Edit Button dialog box, such as
color, font, bitmap, and more.
10. Click OK to add the button to the Submenu Panel.
11. Repeat the procedure for each Smart Item button you need to create, such as Budweiser, Fat Tire,
and more.
12. Click OK.
Using Smart Item and Smart Select Buttons in TableService
After you add the Smart Item and Smart Select buttons to a Submenu Panel, and the submenu to a menu,
the submenu appears when you select the submenu button in the middle row of the FOH Order Entry
screen.
submenu button
Smart Item buttons
To enter an item using Smart Item and Smart Select buttons:
1. Touch the Smart Select button, such as ‘1/2 Pint,’ ‘Pint,’ or ‘Pitcher.’
2. Touch the Smart Item button, such as ‘Guinness.’ The item appears in the FOH guest check window for the appropriate size. If you do not touch a Smart Select button first, the size established as
the default is ordered.
Using Smart Item Buttons with Item Availability
When using the Item availability feature, you can only set the availability on the default item that appears
on the Submenu Panel. The system supports availability at the item level and not at the size level. We recommend using the Item Availability feature with pre-packaged items as opposed to items such as draft
beer.
For example: You sell pre-packaged sizes of Coke in an 8 oz. bottle, 16 oz. bottle, and 24 oz. bottle. You
have a quantity on hand of 30, 50, and 20, respectively. The 16 oz. bottle is the default item. You enter a
quantity on hand of 100 for the Smart Item. When you sell an 8 oz. bottle of Coke, a quantity on hand of 99
appears on the Coke button, but you have no way of knowing you now have only 29 8 oz. bottles of Coke.
Page 167
However, you can use the ‘unavailable symbol’ effectively for smart items that are not pre-packaged, such
as draft beer. For example: You sell Fat Tire on draft in 1/2 pint, pint, and pitcher. You might enter Fat Tire
with the correct size into the system, but once the item is depleted, you cannot sell Fat Tire at any size.
Therefore, when you set Fat Tire as unavailable, the ‘unavailable symbol’ indicates you are out of 1/2 pint,
pint, and pitcher of Fat Tire.
In the following example, Rib Eye shows as unavailable, and you cannot order the item whether you are
ordering a small, medium, or large portion.
Figure 117
Using Smart Item Buttons with Recipes
When you use Smart Items with the Recipe feature, the system displays the three red asterisks for the designated default item only. If a recipe is configured for any size other than the default item, then the asterisks do not appear because the button does not appear on the Submenu Panel, however; you can still access
a recipe.
Figure 118 Smart Item with the Recipe Feature
Page 168
Performing Petty Cash Transaction Using a Public
Performing Petty Cash Transaction Using a
Public Cash Drawer
Version
RFC Number
Products
Audience
POS v6.4
RFC 57381
Aloha TableService
Store Managers
Public cash drawers are common in the International market where several employees can access the same
drawer; however, you cannot perform petty cash transactions using a public drawer because petty cash
transactions are associated with a specific employee assigned to a drawer. In v6.4, you can now perform a
petty cash transaction using a public cash drawer.
To perform a petty cash transaction using a public cash drawer, you must meet the following pre-requisites:
•
•
•
•
Employees using a public cash drawer must have ‘Cash Drawer’ selected in Maintenance > Labor
> Job Codes > Functions tab for the job code under which they are clocking in.
The cash drawer must be designated as ‘public’ with the ‘Public Cash Drawer’ option in Maintenance > Hardware > Cash Drawers.
Petty cash accounts must be configured in Maintenance > System > Petty Accounts.
‘Disable Petty Cash Accts’ must be cleared in Maintenance > Store Settings > Security > Restrictions tab.
To perform a petty cash transaction using a public cash drawer:
1. From the Working with Tables/Tabs screen, touch Functions.
2. Touch Financial.
3. Touch Cash Drawers. The FOH cash drawer screen appears.
Button showing
the calculated
dollar amount in
the drawer.
Figure 119 FOH Cash Drawer Screen
Page 169
Performing Petty Cash Transaction Using a Public Cash Drawer
4. Touch the button labeled either Paid In/Outs or with the calculated dollar amount in the
drawer. The Paid In/Out screen appears.
The text on this button is dependent on how your system is set up. Refer to the TableService Reference Guide, Store Settings > Security Group > Cash Drawer tab for more information regarding the ‘Hide Cash Drawer Amount’ check box.
Figure 120 FOH Petty Cash Account Screen
5. Enter the amount of cash using the numeric keypad.
Page 170
Performing Petty Cash Transaction Using a Public
6. Select one of the following options to display the FOH Select Account screen.
To add cash to the drawer, touch $ In.
To remove cash from the drawer, touch $ Out.
Figure 121 FOH Select Account Screen
7. Select a petty cash account and touch OK. The Paid In/Out screen appears with the adjusted
amount reflected in the total for the drawer, if the system is set up to show the amount in the
drawer. The drawer opens. A receipt prints to the local printer.
Figure 122 FOH Cash Drawer Screen After Petty Cash Transaction
8. Touch Done.
Page 171
Performing Petty Cash Transaction Using a Public Cash Drawer
When you make a petty cash transaction, the system prints an audit slip with the name of the cash drawer,
employee, amount, and the petty cash account.
Figure 123 Petty Cash Audit Slip: Paid In (left) and Paid Out (right)
When you perform a drawer checkout on the drawer, the report lists all paid in and out transactions.
*** CASH TXNS ***
Kara Erley
02:10 PM
John Doe
02:11 PM
Joe Smith
02:23
TOTAL:
Opening 100.00(+)
Paid Out Misc
5.00(+)
Paid In Misc
10.00(+)
105.00
As normal, when the system is running in 24-hour mode, the system carries over all paid in and out transactions until you reset the drawer totals.
Page 172
Providing Access to Reroute Video Groups When Using
Providing Access to Reroute Video Groups When
Using QSR Video
Version
RFC Number
POS v6.4.9 RFC 69924
Products
Audience
Aloha TableService
Store Managers
Normally you enable the interface with QSR via COM in Maintenance > Store Settings > System group >
Interface tab. This setup does not require your security key to be authorized for Video+MX nor does it
require you to configure the Video group in Store Settings; however, if you do not configure the Video
group, you cannot use the manager functions for video on the FOH.
You can now interface with QSR video with the Aloha POS system, and with the existence of a Set Video
Group event, use the Reroute Video Group button on the FOH, thereby providing access to reroute video
groups manually.
Figure 124 FOH System Screen
Page 173
Providing Access to Reroute Video Groups When Using QSR Video
Page 174

Aloha POS Enhancement Release v6.4

Transcription

Similar documents

Joey Reznicek, Owner/Manager Salerno`s restaurant and pizzeria

OmegaLite USI supports Gilbarco`s PAM 1000 protocol, allowing

executive summary

Hispanic Heritage Month

Kordana® roses will bring the garden inside

Bali Hai Interval Owners Association Newsletter

Profile - DDB Lagos

OmegaZ US] supports Gilbarco`s PAM 1000

Archive-September 2012 - The Official Website for Songwriter Lance