POS Enhancement Release v6.7

(1)

Page 1

POS Enhancement

Release v6.7

Last Modified: October 26, 2011

The Purpose of This Document... 3

What You Need to Know Before Installing or Upgrading Aloha... 3

List of Enhancements by Product... 10

Accessing an Employee Schedule from FOH ... 12

Performing ‘Get Check’ with Named Tabs ... 20

Configuring Gross Sales in Sales by Revenue Center Report ... 21

Supporting New State Overtime Laws ... 23

Sorting and Consolidating Modifier Group Buttons ... 30

Supporting Rounding By Tender ... 33

Supporting Additional Pizza Modifier Groups ... 36

Adding Modify Item in Aloha Spy ... 38

Enhancing Order Entry for Delivery Operations ... 39

Enhancing the Aloha COM Interface for v6.7 ... 41

Replacing Default Tip Text Based on Gratuity ... 43

Configuring Gross Sales for Sales by Category Section on Sales Summary Report . 45 Configuring Video Display Method by Terminal ... 48

Printing Legal Disclaimer for Prepaid Visa and American Express Cards ... 50

Supporting Fiscal Requirements for Quebec ... 53

Preventing the Pizza Screen from Automatically Prompting Upon Ordering ... 64

Supporting Code Page 852/1250 for Native Printing ... 65

Supporting Configured Number of Modifier Rows and Columns on Pizza Screen ... 66

Supporting Validation Code for Private Label Cards ... 68

Prompting Twice for Manually Entered Payment Cards ... 72

Forcing Authorization for Gift Card Redemptions ... 74

Supporting Radiant SRP275 Impact Printer ... 77

Supporting Prompts for Cash Drops in Table Service and Public Cash Drawers ... 79

Automatic-Declaring of Charged Tips for Employees Who Do Not Clock-Out ... 83

Including Dates on BOH Void Report ... 86

Outputting Check Number Instead of Check ID for Aloha Spy ... 87

Supporting CAS PD2 Scale ... 89

Supporting Context Panels ... 90

Restricting the Ability to Cancel Cash Declaration ... 91

Supporting Dynamic Included Modifiers ... 93

Toggling Between Adding and Removing a Modifier ... 98

Supporting Dynamic Item Substitution for Quick Combos ... 101

Modifying Multiple Items Simultaneously ... 109

(2)

Copyright ©2011, 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 incorpo-rated in new editions of this publication. Any reference to gender in this document is not meant to be dis-criminatory. 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.

Substituting Included Modifiers With Context Panels ... 117

Enhancing Repeat Button to Quantify Items and Quick Combos ... 124

Automatically Printing an Included Modifier in the Kitchen ... 129

Supporting Fractional Toppings and Fractional Pizzas ... 133

Supporting ‘Topping Average’ Pizza Portion Pricing Method ... 170

Overriding Store-Level Pizza Portion Pricing Method by Item ... 174

Supporting Pizza Topping Inventory Depletion ... 176

Supporting Included Modifiers in Table Service ... 184

Limiting FOH Reports by Revenue Center ... 188

(3)

POS Enhancement Release v6.7 Page 3 The Purpose of This Document

The Purpose of This Document

This document contains instructions on how to set up and use the enhancements implemented in the POS v6.7 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 docu-ment 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 You Need to Know Before Installing or

Upgrading Aloha

Due to the general complexity of the working environment of the Aloha system, you must adapt the infor-mation in this document to address all aspects of your specific installation, taking differences into account. You must also address any third-party software in use in your installation, such as external applications exchanging financial or other information with the Aloha system.

Hardware Requirements

We strongly recommend you adhere to the following minimum system requirements to successfully oper-ate the Aloha POS software in your place of business.

What’s New at a Glance:

The following requirements changed between Aloha POS v6.5 and v6.7. The icon indicates places in the document where the text changed to reflect these new requirements.

Windows 2000 was removed from the list of supported operating systems.

Microsoft has announced it will discontinue support of Windows 2000 as of July, 2010. In response to this, beginning with Aloha POS v6.7, the Aloha POS software will no longer support the Windows 2000 operating system.

SuperSite was removed from the list of Aloha BOH File Server and FOH Termi-nal Hardware requirements.

Aloha SuperSite is no longer supported for Aloha v6.7 and later.

The needs of your business may require you to obtain more than the minimum system requirements. If you are uncertain, please contact your Radiant Systems representative to determine the specific requirements for your establishment.

(4)

What You Need to Know Before Installing or Upgrading Aloha

Aloha BOH File Server Hardware Requirements

The hardware for the Back-of-House (BOH) file server must meet or exceed the recommended require-ments of the operating system. Add additional memory and increase the processor speed to compensate for heavy use, third-party software, and usage unrelated to the Aloha application software.

Aloha FOH Terminal Hardware Requirements

The hardware for each FOH terminal must meet or exceed the following recommended requirements of the operating system. Add additional memory and increase the processor speed to compensate for heavy use, third-party software, and usage unrelated to the Aloha application software.

Operating System Requirements

All computers on the Aloha network must use a supported operating system. If the file server or any of the

FOH terminals use older operating systems, you must upgrade them. Also, if you are using Aloha Update to do the upgrade, or if you are performing a manual upgrade, you must apply all operating system updates to the computer before attempting the upgrade.

Resource Specification Comments

Database Software None (.dbf files)

Storage 20 GB The Aloha application software uses less than 100 MB, when initially installed, but requires approximately 3 MB per histori-cal day.

Memory (RAM) 1 GB

Network Interface Card

10/100/1000

Extended Ports Parallel or USB Required for HASP security key.

Video Adapter VGA-16 Bit Color

Resource Specification Comments

Processor 800MHz Celeron M Clock Speed is only one indication of processing potential. Use this recommendation as a guideline only.

Storage 1 GB The Aloha application software uses less than 50 MB.

RAM 512MB Processors or Storage medi without page file ability may ben-efit from more RAM.

Network Interface Card

10/100/1000 1 NIC of any of the rated speeds.

Video SVGA or 24bit full color

Ports USB, Serial Varies. Should be sufficient number and type to support nec-essary peripherals.

The FOH terminal hardware requirement list does not include peripherals, such as receipt printers, magnetic stripe readers, customer displays, and more.

(5)

POS Enhancement Release v6.7 Page 5 What You Need to Know Before Installing or Upgrading

Supported Operating Systems

The following operating systems, updated to the latest service pack available, are supported by this version of Aloha Table Service and Aloha Quick Service.

Additional Operating System Requirements

In addition to using a supported version of the operating system, the following table lists other operating system requirements. Some requirements, as indicated in the table, are met simply by being on a supported version of the operating system. Other prerequisites are installed for you, if not present, when you initiate the Aloha installation on the Back-of-House (BOH) file server using an Aloha installation CD. This is accomplished using files located on the first installation CD. If you are upgrading the POS version using Aloha Update or doing a manual upgrade, you must install these prerequisites prior to upgrading Aloha.

Operating System File Server FOH Terminal

Windows® XP Professional X X

Windows Server® 2003 X X

Windows Server 2008 X X

Windows 7 X X

Windows XP Embedded X

Windows Embedded Standard 2009 (updated XP Embedded) X

Windows Embedded POSReady 2009 X

Windows Vista X

As of POS v6.7, the Windows 2000 operating system is no longer supported.

The Windows XP Embedded operating system 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.

If you attempt to install Aloha v6.4 or later on a computer running an unsupported operating system, or if Windows Installer v3.1 is not installed, the Aloha installa-tion fails with no warning or error message. The installainstalla-tion process simply fails to start.

Although the program verifies the operating system of the BOH file server, it does not check the operating system on the Front-of-House terminals. All computers on the Aloha network must use

a supported operating system that meets the requirements. If any of the FOH terminals use older

(6)

Update Requirement

Must be

present on: Available From

Internet Explorer 7 or 8

BOH File Server FOH Terminals

Installed with supported operating system, if all service packs and security patches are up to date. Note: Internet Explorer 6 must be used in Aloha implementations prior to v6.4. Radi-ant strongly recommends that IE6 not be used for Internet browsing.If Internet browsing is a requirement, Radiant rec-ommends using a different browser, such as Firefox.

Distributed Com-ponent Object Model (DCOM) v1.3 or later

Installed with supported operating system, if all service packs and security patches are up to date.

Windows® Installer v3.1

Installed with supported operating system, if all service packs and security patches are up to date.The Microsoft Windows Installer v3.1 is a prerequisite for Microsoft .Net Framework 2.0 and later.

.NET Framework 2.0

Installed with supported operating system, if all service packs and security patches are up to date.You must install .Net Framework v2.0 on the FOH terminals, as the terminal instal-lation program will not do this for you.

Visual C++® 2005 Redistributable Package (x86)

BOH File Server FOH Terminals, only if fingerprint scanners are in use

Aloha POS versions 6.4 and later are compiled using Micro-soft Visual Studio® 2005. Microsoft issued a service pack for Visual Studio 2005 that also contained a fix for the redistrib-utable package used by Aloha. This fix (Vcredist_x86.exe) is installed for you on the BOH file server when using Aloha installation CDs; however, if you perform a manual upgrade, you must obtain and install this component separately before you begin. Refer to RKS ID 10994 for more information.

Microsoft Data Access Compo-nents (MDAC) v2.6

BOH File Server If Microsoft MDAC 2.6 does not exist on the FOH file server, it is installed for you when you install the Aloha POS using Aloha installation CDs.

Microsoft® Jet 4.0 SP 8

BOH File Server If Microsoft Jet 4.0 SP 8 does not exist on the BOH file server, it is installed for you when you install the Aloha POS using Aloha installation CDs.

RFSCtl80s.dll BOH File Server FOH Terminals

When upgrading from a 5.3 version of the Aloha POS to a version of the Aloha POS prior to v6.4.18, using either an installation CD or when doing a manual upgrade, the system does not recognize the RFSCtl80s.dll file due to the 8x3 file name and will not copy this file to the BOH file server; there-fore, you must manually copy this file to the Bin folder. As of 6.4.18 and later, this file is copied for you. The terminal upgrade that occurs after the first data refresh successfully copies this file to the FOH terminals for you.

6.06.1 and 6.2 dlls.zip

BOH File Server The installation CD copies the DLLs contained in this zip file for you; however, if you are performing a manual upgrade from a 5.3 version to a 6.x version, you must download the 6.06.1 and 6.2 dlls.zip file from the Radiant FTP site from the Downloads > Utilities folder and extract the DLLs contained within it to the Windows > System32 folder on the BOH file server.

(7)

Controlling Access to Aloha Manager and Aloha EDC

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 require-ments become ever more restrictive. Refer to RKS ID 9614 for more information.

Disabling Masking in Grind Files

Beginning with Aloha v6.4, we completely removed the ‘Disable Masking in Grind File’ option from the Aloha Manager interface, in Aloha Quick Service and Table Service, as part of making the Aloha system compliant with PCI DSS. This setting is located in Maintenance > Payments > Tenders > Type tab. You must examine each credit card and debit card tender, and clear this option, if currently enabled, prior to the

upgrade. If you are unable to make these changes prior to upgrading to v6.4 or later, you must obtain help

from your Radiant representative to edit the payment card tenders and clear the ‘Disable Masking in Grind File’ option.

Disabling Expiration Date Printing

Beginning with v6.4, an important security change occurs ‘behind the scenes.’ All settings relevant to printing the payment card expiration date automatically change to prevent printing this value in any loca-tion in the restaurant. This modificaloca-tion is in response to the requirements outlined in the Fair and Accurate Credit Transactions Act (FACTA). After you upgrade to Aloha v6.4, or later, we recommend you verify that Aloha does not print this information for all payment card types, when processed.

Supporting the Radiant MSR Interface

Beginning with v6.4.9, Radiant terminals now provide a more secure way of communicating with the mag-netic stripe reader (MSR) through the Radiant MSR interface, instead of using the Keyboard Wedge ser-vice, 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.

Upon upgrading, a new option, “Radiant,” appears in the MSR ‘Type’ drop-down list in Terminal Mainte-nance. The preferred configuration is for you to change the MSR type for Radiant terminals from Key-board 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 Key-board Wedge as the MSR type, unregisters the KeyKey-board Wedge Service for you, and automatically begins to use the Radiant MSR interface driver set for communicating with the magnetic stripe reader. The mes-sages, “Keyboard Wedge Service Detected, Keyboard Wedge Service Stopped, and Keyboard Wedge Ser-vice Unregistered” are written to the terminal debout. Refer to RKS ID 10990 for more information.

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.

(8)

Licensing Aloha Connect for Third Party Applications

Radiant Systems officially launched Aloha Connect beginning with version 6.2 of the Aloha POS soft-ware. Aloha Connect allows authorized third party companies to interface to the Aloha solution to meet customer needs and provide additional complementary technology functionality to meet business require-ments.

Examples of integrated solutions include: • Web ordering

• Call center applications

• Third party gift card and loyalty solutions • Beverage systems

• Non-POS terminal order taking and payment devices, such as kiosks and handhelds.

Beginning with Aloha POS v6.2, enforcement of interface terminals is restricted and licensing is verified at the site level. If your software keys are appropriately licensed, your third party/custom applications will work seamlessly with your POS. If your keys are not licensed, your additional applications will not be able to integrate to the POS. It is important for you to note that should you decide to pursue an integrated solu-tion in the future, your site software license will need to be upgraded to reflect the change.

Aloha Connect Now Requires License String

To ensure the Aloha solution maintains the highest standards in security for our customers, we are evaluat-ing different components of the Aloha Connect integration framework and identified an area that needed to be enhanced. The changes we made impact any client who partners with a third-party vendor to access the MSR or barcode reader through the Aloha Connect interface. Starting with our June maintenance releases (6.4.23, 6.5.17, 6.7.5) we require that all third-party vendors pass a serial string as part of our effort to ensure only valid authorized developers are accessing these devices. If you use a third-party solution that accesses either the MSR (Magnetic Swipe Reader) or the barcode scanner, please contact your vendor prior to upgrading to one of these versions to confirm that the necessary updates have been made to their integra-tion. If they have not made these changes, they can contact Radiant Systems at [email protected] to obtain the necessary license string.

Enabling Remote File Storage

After verifying your operating system meets all prerequisites, the installation program prompts you to enable Remote File Storage (RFS), a new, more secure method of communicating data between the Front-of-House and Back-Front-of-House. Using RFS is completely optional, unless you are using more than nine minals; however, we recommend you enable RFS upon initial installation regardless of the number of ter-minals in your network to facilitate more secure operations. If you do not enable it at this time, you can

(9)

enable RFS in Aloha Manager by selecting Maintenance > Store Settings > Security group > RFS tab. Set-upPOS.exe installs all files necessary for supporting RFS, including entries in the Windows Registry, on each computer in the Aloha network.

EDC and POS Version Compatibility

Beginning with Aloha EDC versions 6.4 and later, EDC adopted a policy of assured backwards compati-bility with Aloha POS versions 6.1.23 and later, 6.2.16 and later, and 6.4.7 and later. Generally speaking, you can upgrade to a newer version of EDC to take advantage of new features, and to comply with new processor requirements, without having to upgrade the POS. Although you must upgrade your Aloha HASP key to reflect the version of EDC you wish to run, the change in license status does not automati-cally make it a requirement to upgrade the POS to that same version; however, some new features require an upgrade to both the EDC and POS products.

Refer to the Remote File Storage (RFS) Feature Focus Guide for more information about install-ing and configurinstall-ing the Aloha system to use RFS.

Refer to RKS ID10265 “Aloha EDC and Aloha Point-of-Sale Version Compatibility and Depen-dencies” for clarity on POS and EDC version compatibility. Refer to the EDC Enhancement Release v6.4 document for detailed information on the EDC enhancements in v6.4.

(10)

List of Enhancements by Product

Version RFC Number Description

Quick Service and Table Service Enhancements POS v6.7 RFC 02634

RFC 76761 RFC 77457

“Accessing an Employee Schedule from FOH” on page 12

POS v6.7 RFC 05129 “Performing ‘Get Check’ with Named Tabs” on page 20

POS v6.7 RFC 06825 “Configuring Gross Sales in Sales by Revenue Center Report” on page 21 POS v6.7 RFC 08199 “Supporting New State Overtime Laws” on page 23

POS v6.7 RFC 09190 “Sorting and Consolidating Modifier Group Buttons” on page 30 POS v6.7 RFC 14956 “Supporting Rounding By Tender” on page 33

POS v6.7 RFC 18936 “Supporting Additional Pizza Modifier Groups” on page 36 POS v6.7 RFC 40695 “Adding Modify Item in Aloha Spy” on page 38

POS v6.7 RFC 67693 “Enhancing Order Entry for Delivery Operations” on page 39 POS v6.7 RFC 70097

RFC 73646

“Enhancing the Aloha COM Interface for v6.7” on page 41 POS v6.7 RFC 70845 “Replacing Default Tip Text Based on Gratuity” on page 43

POS v6.7 RFC 72019 “Configuring Gross Sales for Sales by Category Section on Sales Sum-mary Report” on page 45

POS v6.7 RFC 72197 “Configuring Video Display Method by Terminal” on page 48

POS v6.7 RFC 72965 “Printing Legal Disclaimer for Prepaid Visa and American Express Cards” on page 50

POS v6.7 RFC 73065 RFC 74435 RFC 74437 RFC 75044

“Supporting Fiscal Requirements for Quebec” on page 53

POS v6.7 RFC 73139 “Preventing the Pizza Screen from Automatically Prompting Upon Order-ing” on page 64

POS v6.7 RFC 73920 “Supporting Code Page 852/1250 for Native Printing” on page 65

POS v6.7 RFC 73954 “Supporting Configured Number of Modifier Rows and Columns on Pizza Screen” on page 66

POS v6.7 RFC 74323 RFC 76669

“Supporting Validation Code for Private Label Cards” on page 68 POS v6.7 RFC 74341 “Prompting Twice for Manually Entered Payment Cards” on page 72 POS v6.7 RFC 74342 “Forcing Authorization for Gift Card Redemptions” on page 74 POS v6.7 RFC 74535 “Supporting Radiant SRP275 Impact Printer” on page 77

POS v6.7 RFC 74566 “Supporting Prompts for Cash Drops in Table Service and Public Cash Drawers” on page 79

(11)

POS Enhancement Release v6.7 Page 11 List of Enhancements by Product

POS v6.7 RFC 75763 “Automatic-Declaring of Charged Tips for Employees Who Do Not Clock-Out” on page 83

POS v6.7 RFC 75659 “Including Dates on BOH Void Report” on page 86

POS v6.7 RFC 78088 “Outputting Check Number Instead of Check ID for Aloha Spy” on page 87 POS v6.7 RFC 82911 “Supporting CAS PD2 Scale” on page 89

Quick Service Only Enhancements POS v6.7 RFC 67405

RFC 69546 RFC 70441

“Supporting Context Panels” on page 90

POS v6.7 RFC 68013 “Restricting the Ability to Cancel Cash Declaration” on page 91 POS v6.7 RFC 68913 “Supporting Dynamic Included Modifiers” on page 93

POS v6.7 RFC 69460 RFC 69902

“Toggling Between Adding and Removing a Modifier” on page 98 POS v6.7 RFC 70440 “Supporting Dynamic Item Substitution for Quick Combos” on page 101 POS v6.7 RFC 71330

RFC 72160

“Modifying Multiple Items Simultaneously” on page 109 POS v6.7 RFC 71845 “Automatically Adding a Modifier to the Check” on page 114 POS v6.7 RFC 72155 “Substituting Included Modifiers With Context Panels” on page 117 POS v6.7 RFC 72161 “Enhancing Repeat Button to Quantify Items and Quick Combos” on

page 124

POS v6.7 RFC 76056 “Automatically Printing an Included Modifier in the Kitchen” on page 129 POS v6.7 RFC 76061 “Supporting Fractional Toppings and Fractional Pizzas” on page 133 POS v6.7 RFC 76062 “Supporting ‘Topping Average’ Pizza Portion Pricing Method” on page 170 POS v6.7 RFC 76063 “Overriding Store-Level Pizza Portion Pricing Method by Item” on

page 174

POS v6.7 * RFC 76064 “Supporting Pizza Topping Inventory Depletion” on page 176 Table Service Only Enhancements

POS v6.7 RFC 09779 “Supporting Included Modifiers in Table Service” on page 184 POS v6.7 RFC 70933 “Limiting FOH Reports by Revenue Center” on page 188

POS v6.7 RFC 74816 “Applying a BOGO Price to Items Based On Order Entry Time” on page 189

* Implemented only in Aloha Configuration Center or the new Aloha Manager. Version RFC Number Description

(12)

Accessing an Employee Schedule from FOH

Employee schedules are often posted in a central location of a restaurant and are sometimes overlooked by employees for a variety of reasons. The schedule may not be easily accessible to kitchen employees, not printed in copies for portability, or cannot be found at the moment. To increase the accessibility of employee schedules, in POS v6.7, once an employee is logged in, they can easily view or print any of their prepared work schedules from the FOH. You can also automatically print schedules for up to four work weeks on the clock-out chit when an employee clocks out to remind them when they work next.

Configure Access to Employee Schedules from FOH

To utilize this feature, you must have labor schedules created, using either the Basic Labor Scheduler, the Aloha Labor Scheduler, and MenuLink programs. For each work week, these scheduling systems create an .sch file, which the FOH uses to display scheduling information. You do not need to change the way you create schedules in these programs to access employee schedules from the FOH.

Configure the Date Format to Display on Schedules

You can configure the date format to display on schedules in the FOH in either mm/dd/yyyy format or using the name of the day, such as Monday.

Version RFC Number Products Audience

POS v6.7 RFC 02634 RFC 76761 RFC 77457 RFC 74767

Aloha Quick Service, Aloha Table Service Configuration Technician End User

Refer to the Aloha Quick Service or Aloha Table Service Manager Guide for help in creating labor schedules using Basic Labor Scheduler. Refer to the Aloha Labor Scheduler User Guide for more information on creating labor schedules using Aloha Labor Scheduler.

(13)

POS Enhancement Release v6.7 Page 13 Accessing an Employee Schedule from FOH

To configure the date format to display on schedules:

1. Select Maintenance > Store Settings > Labor group > Scheduling tab. The appearance of this

tab is the same in Quick Service and Table Service.

2. Select the format to use for printing the date on schedules from the ‘Printed Schedule Shows’

drop-down list.

Printed Schedule Shows — Determines the format to use for printing the date on the schedule

and the clock-out chit when you configure the system to print employee schedules from the FOH. • Date - Prints the date in mm/dd/yyyy format on the schedule and the clock-out chit.

Related Options: You can change the date to follow International formatting in Mainte-nance > Store Settings > International group.

• Day of the Week - Prints up to 10 characters of the full name of the day of the week, such

as Sunday, on the schedule and the clock-out chit.

3. Click Save and exit the Store Settings function.

Configure Employee Schedules to Print on Demand

When you enable employee schedules to print from the FOH in Aloha Table Service, a View Schedule but-ton appears on the FOH Employee screen, by default; however, you can also add the View Schedule butbut-ton to an available floor plan, if one is in use. When you enable employee schedules to print from the FOH in Aloha Quick Service, you must add the View Schedule button to an available panel, such as an Employee Functions panel, so employees can access and print their schedule.

To add a View Schedule button function to a panel: 1. Access Panel Editor.

(14)

2. From the Commands menu, select Edit Existing Panel > Button Functions Panel and select a panel for edit. The Edit Buttons dialog box appears.

3. Select View Schedule from the ‘Function’ drop-down box.

View Schedule — Enables a FOH employee to view prepared labor schedules from the FOH, on

demand. Related Options: To enable the system to automatically print employee schedules on the clock-out chit, select ‘Print Schedule on Clock-Out Chit’ in Maintenance > Store Settings > Labor group > Clock In/Out tab.

4. Complete the remaining options as you would for any other button. 5. Click OK to add the button to the panel.

6. Select Save All Panels and exit the Panel Editor function.

Configure Employee Schedules to Appear On-Screen

If you want employees to have the ability to view their schedules on-screen, with the option to print to the local printer, you must use the print intercepter functionality. To enable this, you must ensure PrtInter.dll resides in the Bin directory. You must also include the appropriate command lines in PrtIncptr.ini in the Data and Newdata directories. Then select Maintenance > Store Settings > System > Interfaces and select ‘Use FOH COM Interface?’

To enable FOH COM interface:

1. Select Maintenance > Store Settings > System group > Interfaces tab. 2. Select Use FOH COM Interface?

To provide an employee the ability to view their schedules on-screen:

1. Locate PrtIncptr.ini in the Newdata directory and double-click the file to open the file in

Note-pad.

2. Type the following line under the [DocumentTypes] heading:

FOHDOC_SCHEDULE=1

3. Select File > Save. 4. Exit Notepad.

5. In Aloha Manager, select Utilities > Refresh Data or manually copy PrtIncptr.ini into the Data

directory.

If you are creating a new PrtIncptr.ini file, you must at least add the [DocumentTypes] line to the file. Additionally, you must manually register the PrtInter.dll file by opening a command prompt on each terminal, navigate to the Bin directory, and type RegSvr32 PrtInter.dll. Then refresh the system and start the FOH. Refer to RKS ID 9552 for more information on using the Aloha Print Interceptor functionality.

(15)

Configure Employee Schedules to Automatically Print on Clock-Out

Chit

You can configure the system to automatically print an employee’s schedule on the bottom of their clock-out chit for all employees or a group of job codes. Use this feature if you want to ensure employees receive their schedule each time they work or if the schedule is updated regularly.

To configure employee schedules to automatically print on the clock-out chit:

1. Select Maintenance > Store Settings > Labor group > Clock In/Out tab. The appearance of this

tab is the same in Quick Service and Table Service.

2. Select Print Schedule on Clock-Out Chit.

Print Schedule on Clock-Out Chit — Enables the system to automatically print employee

schedules on the clock-out chit when the employee clocks out. Related Requirements: You must configure labor schedules in Basic Labor Scheduler, Aloha Labor Scheduler, or MenuLink to use this option.

3. Select Restrict to Labor Group.

Restrict to Labor Group — Limits the printing of employee schedules on the clock-out chit to a

labor group. Use this option if you want to enable automatic printing only for a group of job codes, such as employees who work only in the kitchen. If you need to create a labor group, click Labor Group to access the Labor Group function. Required Options: You must select ‘Print Schedule on Clock-Out Chit,’ located on this same tab, to enable this option.

You must leverage the use of your printer paper when you enable this feature.

(16)

4. Select Number of Weeks to Print.

Number of Weeks to Print — Specifies the number of scheduled weeks to automatically print on

the clock-out chit. Required Options: You must select ‘Print Schedule on Clock-Out Chit,’ located on this same tab, to enable this option.

Accessing Your Employee Schedule from the FOH

This section is intended to teach the FOH employee how to print and view their schedule on demand, or clock out and print the schedule.

View and Print Your Schedule on Demand

You can only view or print one schedule at a time.

To view or print your schedule from the FOH: 1. Locate and touch the View Schedule button.

• For Quick Service, locate and touch the View Schedule button.

• For Table Service, touch Special Functions on the Working With Tables/Tabs screen, then touch Employee > View Schedule to display the FOH Employee screen, or you can select the button from a floor plan screen in use.

The Select Schedule for Work Week Beginning screen appears.

The current or earliest work week appears in the upper left corner of the screen and all approaching work weeks list down in chronological order.

(17)

2. Select a work week. Your schedule either prints to the local printer or appears on-screen.

3. Touch Print to print the selected schedule to the local printer, if desired.

4. Touch Done to return to the FOH Select Schedule for Work Week Beginning screen and work with

another schedule.

When the schedule prints, all shifts for the week appear, regardless if the date is past. The dates you are not scheduled do not appear. Multiple shifts on the same day appear on separate lines.

Figure 4 Scheduled Information (On-Screen)

(18)

Clock Out and Automatically Print an Employee Schedule

When you clock out, one to four prepared work weeks automatically print in succession at the bottom of the clock-out chit.

To clock out and print your schedule:

1. When you are ready to clock out, locate and touch the Clock Out button. The Clock Out screen

appears.

2. Touch Clock Out.

The clock-out chit prints up to four employee schedules at the bottom of the receipt, in succession. All shifts for the week appear, regardless if the date is past. The dates you are not scheduled to work do not appear. Multiple shifts on the same day appear on separate lines.

(19)

Troubleshooting Accessing an Employee Schedule from FOH

Use the following troubleshooting tips when you experience problems accessing an employee schedule from the FOH:

Aloha Labor Scheduler Displays Multiple Work Weeks

The Aloha Labor Scheduler program has the unique ability to hold up to four work weeks inside of a single .sch file and work weeks are not restricted to a rigid start date for the week. If the .sch file contains more than one work week, all weeks display when you view or print an employee schedule from the FOH.

No Schedule is Found

If the system cannot find a corresponding .sch file for the selected work week, an error message appears, stating “Schedule not found.”

Only Three Schedules Appear When the System is in Redundancy

If only three approaching employee schedules appear when you print or view employee schedules from the FOH, the system may be in redundancy. The Aloha system ensures that scheduling information is available for the maximum redundancy length of 21 days by propagating up to three .sch files to the terminals. Pre-viously, the system read .sch files from the BOH server only.

Contact your Radiant Systems representative if you need help restoring the sys-tem from redundancy.

(20)

Performing ‘Get Check’ with Named Tabs

Currently, the ‘Get Check’ feature allows you to access an open order by its check number, table number, or associated card via manual card or a scanned bar code. In v6.7, you can look up a tab by its name. In Aloha Table Service, you can perform ‘Get Check’ using the following mechanisms:

• Select ‘Can Get Checks’ in Maintenance > Labor > Job Codes > Job Code tab and the system auto-matically displays the Get Check button on the Working with Tables/Tab screen.

• Add the Get Check button function to an order screen panel in Panel Editor and you have access to the button on the FOH order entry screen, providing you also select ‘Can Get Checks’ in Mainte-nance > Labor > Job Codes > Job Code tab.

In Aloha Quick Service, you can perform ‘Get Check’ when you add the Get check button to a panel in Panel Editor, providing you also select ‘Can Get Checks’ in Maintenance > Labor > Job Codes > Job Code tab.

POS v6.7 RFC 05129 Aloha Quick Service, Aloha Table Service Configuration Technician End User

(21)

POS Enhancement Release v6.7 Page 21 Configuring Gross Sales in Sales by Revenue Center

Configuring Gross Sales in Sales by Revenue

Center Report

In v6.7, you now have more flexibility in configuring the gross sales formula on the BOH Sales by Reve-nue Center report by optionally including inclusive taxes. This option appears in the following sections of the report:

• Sales by Category • Sales by Day Part

• Sales by Day Part and Category

To configure gross sales in the Sales by Revenue Center report: 1. Log in to the BOH.

2. Select Reports > Sales > Sales by Revenue Center. The Sales by Revenue Center Report dialog

box appears.

3. Click Settings. The Sales by Revenue Center Report Settings dialog box appears.

4. Select either Sales by Category, Sales by Day Part, or Sales by Day Part and Category from

the ‘Available’ list box and click > to move it to the ‘Included’ list box. Additional options appear in the right of the dialog box.

In v6.7, the BOH Sales by Revenue Center Report Settings dialog box now adheres to the current standard of a dual list view, for ease of use.

(22)

Configuring Gross Sales in Sales by Revenue Center Report

5. Select Include Inclusive Taxes.

Include Inclusive Taxes — Includes inclusive taxes in gross sales for each selected section. When

selected, the word ‘NET’ is removed from the default section header text. For example, the default header text for Sales by Day Part changes from ‘NET SALES BY DAY PART’ to ‘SALES BY DAY PART.’

(23)

POS Enhancement Release v6.7 Page 23 Supporting New State Overtime Laws

Supporting New State Overtime Laws

In POS v6.7, we have enhanced overtime to support new requirements implemented by certain state laws. These enhancements include the ability to:

1. Award daily overtime depending on the employee’s shift rate.

2. Configure overtime pay where the daily work starts at the employee’s clock in of the previous day,

within a 24-hour time frame, instead of using the Aloha date of business.

3. Allow employees to earn a one-time penalty pay when their daily worked hours exceed 10 hours. 4. Calculate overtime pay based on the store-level minimum wage, instead of using the blended rate. 5. Configure overtime calculation to include the daily overtime in weekly overtime hours.

In addition, we have redesigned the interface for configuring overtime and moved all options to a new tab called Overtime, in Maintenance > Store Settings > Labor group. Overtime computation has not changed.

1. Daily Overtime Awarded Based on Pay Rate

In accordance to the new laws of some states, such as Nevada, employees are entitled to daily overtime pay, depending on the rate of pay the employee earns for their given shift. If the employee’s pay is greater than the specified pay rate, the system does not award overtime to the employee. Use this feature for man-agers or employees whose job codes earn a high pay rate.

To configure overtime awarded based on pay rate:

1. Select Maintenance > Store Settings > Labor group > Overtime tab (Figure 8).

(24)

Supporting New State Overtime Laws

2. Select the first Daily check box and type the number of hours an employee an employee can work per day before going into overtime.

3. Select Do Not Apply Daily Overtime if Employee Rate Is Greater Than and type the pay rate

threshold.

Do Not Apply Daily Overtime If Employee Rate Is Greater Than ___ — Specifies that daily

overtime will not apply to any employee whose pay rate is more than the amount defined in the text box. Type the pay rate, from 00.00 to 99.99, for which you want to set the threshold. Required Options: You must select the first row of ‘After ___ Hours; Multiply ___’ to enable these options.

2. Daily Overtime Based on a 24-Hour Work Day

In accordance to the new laws of some states, such as Nevada, employees are entitled to daily overtime pay based on a 24-hour work day that starts with the employee’s previous clock in, and not by the system date of business. If the employee did not punch in during the previous 24-hours, the system uses the punch out for the day.

To configure overtime based on 24-hour work day and pay rate:

1. Select Maintenance > Store Settings > Labor group > Overtime tab (Figure 8).

2. For daily overtime, select the first Daily check box and type the number of hours an employee an employee can work per day before going into overtime.

Daily level one: After ___ Hours; Multiply ___ — Denotes the number of hours, from 0 to 99,

an employee can work per day before going into overtime. Then specify the multiplier rate used by the system when an employee’s hours exceed the hours per day limits. The default rate is 1.5 (time and a half).

3. Select 24 Hour Day Starts at Shift Start.

24 Hour Day Starts at Shift Start — Uses the employee’s last previous clock in time to begin a

24-hour work day, instead of using the system date-of-business, to calculate the daily overtime. For example, if the employee clocks in at 1:00 p.m. on Tuesday, the work day starts at 1:00 p.m. and continues until 12:59 p.m. on Wednesday, even if the employee clocks in again within that 24-hour time. Required Options: You must select the first row of ‘After ___ Hours; Multiply ___’ in the Daily group box and clear the first row of ‘After ___ Hours; Multiply ___’ in the 7th Day group box to enable this option.

Use the following example to illustrate how the 24-hour time frame operates. You may want to use other options on the Overtime tab to meet your needs, such as configuring weekly overtime, also. We recommend you consult the labor laws in your state and region.

(25)

In the above example, overtime is calculated both on a 40-hour work week (weekly) and on an 8-hour day (daily). Weekly overtime is configured as 40 hours and compensation awarded at 1.50 (time and a half). The daily overtime is based on a 24-hour time frame (24 Hour Day Starts at Shift Start). The payroll week starts on Wednesday.

Wednesday: Regardless of the job code under which the employee clocked in or how the hours were paid on the prior payroll period, the last clock in for the employee was at Tuesday 6:00 PM. Therefore, the 24-hour work day for the employee starts at 6:00 PM Tuesday and continues until 5:59 PM Wednesday. The four hours worked on Tuesday are attributed to the hours of the 24-hour time frame.

On Wednesday, the employee works an 8-hour shift from 10:00 AM to 12:00 PM; however, there are already four hours from the Tuesday in the calculation. Therefore, by 2:00 PM, the employee reaches daily overtime. Eight hours post to the total daily hours, with four of the hours as regular hours, and four of the hours as daily overtime.

Thursday: To determine the hours for Thursday, the employee’s previous clock in was at Wednesday 10:00 AM. The new 24-hour time frame for the employee starts at Wednesday 10:00 AM to Thursday 9:59 AM, thereby accumulating eight hours already for the 24-hour work day. On Thursday, the employee works a 10-hour shift from 9:00 AM to 7:00 PM. The first hour of the shift occurs before the 24-hour time frame lapses; therefore, it is daily overtime. 10 hours post to the total daily hours, with eight of the hours as regu-lar hours and two of the hours as daily overtime.

Friday: To determine the hours for Friday, the employee’s previous clock in was at Thursday 9:00 AM. The new 24-hour time frame for the employee starts at Thursday 9:00 AM to Friday 8:59 AM, thereby accumulating eight hours already for the 24-hour work day. On Friday, the employee works a 10-hour shift

(26)

from 8:00 AM to 6:00 PM. The first hour of the shift occurs before the 24-hour time frame lapses; there-fore, it is daily overtime. 10 hours post to the total daily hours, with eight of the hours as regular hours and two of the hours as daily overtime.

Saturday and Sunday: The employee did not work.

Monday: Since the employee did not work on Sunday, they do not have a previous clock in within a 24-hour frame. The 24-24-hour time frame then starts with the employee’s Monday’s clock in. The employee works a nine-hour shift from 1:00 PM to 10:00 PM. Nine hours post to the total daily hours, with one hour as daily overtime.

Tuesday: To determine the hours for Tuesday, the employee’s previous clock in was at Monday 1:00 PM. The new 24-hour time frame for the employee starts at Monday 1:00 PM to Tuesday 12:59 PM, thereby accumulating seven hours already for the 24-hour work day. On Tuesday, the employee works a 10-hour shift from 10 AM to 8 PM. The first three hours of the shift occurs before the 24-hour time frame lapses; therefore, it is daily overtime. 10 hours post to the total daily hours, with seven of the hours as regular hours and three of the hours as daily overtime.

Weekly Total: The total reported hours for the week are 35 regular and 12 overtime hours. If the regular hours exceeded 40, the hours would be converted to overtime. Overtime is only paid on actual hours worked; therefore, vacation and holiday time are not considered.

3. Overtime Laws Awarding Penalty Pay Based on Minimum Daily Spread of Hours

Work

In accordance to the new laws of some states, such as New York, employees are entitled to a one-time pen-alty pay for either weekly and daily overtime, if the total hours worked in a business day exceeds the mini-mum threshold set in the system. The spread of hours is the interval between the beginning and ending of an employee’s workday. The system adds a one-time penalty pay if the total hours from the first clock in to the last clock out of the day is greater than the user-defined hours, usually configured at 10 hours.

To configure overtime penalty pay based on a spread of work:

1. Select Maintenance > Store Settings > Labor group > Overtime tab (Figure 8). 2. Configure the system for either daily or weekly overtime.

3. Type the minimum daily spread of hours to qualify for penalty pay. Type 0.00 to not pay penalty

pay.

Workday Over ____ Hours: Add ___ Hours At Minimum Wage Rate — Specifies the

mini-mum working hours in a single business day to qualify for a one-time penalty pay at the minimini-mum wage defined in the system. Then type the number of hours to pay. The system records the pay as the other wage type ‘913 Spread of Hours Premium’ in the Other Wages function.

When the End-of-Day occurs and an employee receives penalty pay, the system logs the action in the Other Wages function, using ‘913 Spread of Hours Premium.’ Each system-generated record appears in the Other Wages section of the Edit Punches function and contains an asterisk in the ‘Review’ column. The asterisk remains until you review the other wage record. You may edit or delete the other wage record and the action is reflected in the Audit report.

(27)

To edit the time for penalty pay records: 1. Select Functions > Edit Punches.

2. Select the date for which you want to display the other wage records. 3. Select the record to edit from the Other Wages section.

4. Click Edit. The Edit Other Wage Data dialog box appears.

5. Type the edited time in the ‘Hours’ text boxes, if needed.

6. Click Save to exit the Edit Other Wage Data dialog box and return to the Edit Prior Days’ Time

and Attendance function. The record now shows ‘Reviewed’ instead of an asterisk.

To delete a penalty pay record:

1. Select Functions > Edit Punches (Figure 10).

2. Select the date for which to display the other wage records.

3. Select the record from the Other Wages section and click Delete. The record now shows

‘Reviewed’ instead of an asterisk.

Figure 10 Edit Prior Days’ Time and Attendance Function

(28)

4. Calculate Overtime Pay Using the Minimum Wage Rate

In accordance to the new laws of some states, such as Colorado, employees are paid overtime using the minimum wage rate, regardless of the rate under which they clock in. Prior to this enhancement, the Aloha system calculates overtime pay based on either the pay rate for the job code under which the employee clocks in, or use an average rate, which is the total pay divided by the total hours for the pay period, regard-less of the job code.

To calculate overtime pay based on minimum wage:

1. Select Maintenance > Store Settings > Labor group > Overtime tab (Figure 8). 2. Configure daily or weekly overtime, or both.

3. Select Calculate Overtime By Minimum Wage.

Calculate Overtime By Minimum Wage — Calculates overtime pay using the minimum wage

rate defined by the system.

5. Include Daily Overtime Hours in Weekly Overtime Hours

In accordance to the laws in some states, such as California, when configuring daily and overtime hours, daily hours are eligible to be included as overtime hours.

To include daily overtime hours in weekly overtime hours:

1. Select Maintenance > Store Settings > Labor group > Overtime tab (Figure 8). 2. Configure daily and weekly overtime.

3. Select Include Daily Overtime Hours in Weekly Overtime Hours.

Include Daily Overtime Hours in Weekly Overtime Hours — Includes the hours earned from

daily overtime in the weekly overtime calculation. Typically, daily overtime hours are counted only once as daily and are never included as weekly.

Upgrade Path

Upon upgrading from a version prior to v6.7, the overtime options are different and have been moved to the new tab, Overtime in Maintenance > Store Settings > Labor group. No configuration is necessary to retain your previous overtime configuration.

(29)

Weekly: After ___ Hours; Multiply ___ — Denotes the number of hours, from 0 to 999, an employee

can work, per week, before going into overtime. Then specify the multiplier rate used by the system when an employee’s hours exceed the hours per week limits. The default rate is 1.5 (time and a half).

Daily level one: After ___ Hours; Multiply ___ — Denotes the number of hours, from 0 to 99, an

employee can work, per day, before going into overtime. For example, type eight to specify hours worked after an eight-hour day, account toward overtime. Then specify the multiplier rate used by the system when an employee’s hours exceed the hours per day limits. The default rate is 1.5 (time and a half).

Daily level two: After ___ Hours; Multiple ___ — Denotes the number of hours, from 0 to 99, an

employee can work, per day, before going into overtime. For example, type 10 to specify hours worked after a 10-hour day, account toward overtime. The number must be greater than, or equal to, the number of hours in level one. Then specify the multiplier rate used by the system when an employee’s hours exceed the hours per day limits. The default rate is 1.5 (time and a half).

7th Day level one: After ___ Hours; Multiply ___ — Denotes the number of hours, from 0 to 99, an

employee can work on the 7th consecutive day worked before going into overtime, if applicable. Employ-ees receive overtime pay for the 7th consecutive day worked, regardless of the number of hours worked that same week. After a defined number of hours are worked on the 7th consecutive day, employees can receive additional overtime pay. Then specify the multiplier rate used by the system when an employee works on the 7th consecutive day worked before going into overtime. The default rate is 1.5 (time and a half).

7th Day level two: After ___ Hours; Multiply ___ — Denotes the number of hours, from 0 to 99, an

employee can work on the 7th consecutive day worked before going into overtime, if applicable. Employ-ees receive overtime pay for the 7th consecutive day worked, regardless of the number of hours worked that same week. After a defined number of hours are worked on the 7th consecutive day, employees can receive additional overtime pay. The number must be greater than, or equal to, the number of hours in level one. Then specify the multiplier rate used by the system when an employee works on the 7th consecutive day worked before going into overtime. The default rate is 1.5 (time and a half).

(30)

Sorting and Consolidating Modifier Group Buttons

Sorting and Consolidating Modifier Group

Buttons

Automatically sorting and consolidating buttons on the display grid in Submenu Maintenance with one button touch has long been a valuable database building tool in Aloha Table Service. In v6.7, you can now use sort and consolidate buttons in Modifier Maintenance for both Aloha Quick Service and Table Service, making this process much easier and less time-consuming.

To sort modifiers on the Modifier Group screen:

1. Select Maintenance > Menu > Modifier Groups.

2. Select a modifier group from the drop-down list and press Enter.

POS v6.7 RFC 09190 Aloha Quick Service, Aloha Table Service Store Managers End User

Figure 13 Modifier Groups Function

Click Sort ^, Sort >, and Consolidate to automatically arrange the buttons on the grid the way you want.

(31)

POS Enhancement Release v6.7 Page 31 Sorting and Consolidating Modifier Group Buttons

3. Click Sort ^ to display the modifiers vertically in alphabetical order on the screen.

Click Sort > to display the modifiers horizontally in alphabetical order on the screen.

Click Consolidate to fill the empty positions, starting from the top-left to the bottom-right, on the Figure 14 Sorting Modifiers Vertically (Before and After)

(32)

Sorting and Consolidating Modifier Group Buttons

screen.

4. Click Save to exit the Modifier Groups function.

(33)

POS Enhancement Release v6.7 Page 33 Supporting Rounding By Tender

Supporting Rounding By Tender

Other countries, such as The Czech Republic, New Zealand, and Thailand, require check rounding to occur at different levels based on the tender type, ranging anywhere from a low of 0.02 to a whole amount of 1.00. For example, the Czech Republic rounds the Czech crown to the nearest 0.50 for credit card transac-tions and to the nearest whole crown (1.00) for cash transactransac-tions. In New Zealand, the dollar is rounded to the nearest dime (0.10).

To accommodate the International market, you can now configure a rounding method for each tender type, and you have more flexibility when choosing the rounding level to use.

To configure rounding by tender:

1. Select Maintenance > Payments > Tenders > Rounding tab.

2. Select a tender for which you want to define rounding from the ‘Number’ drop-down list and

press Enter.

3. Select Round to___ to enable rounding for this tender and type the rounding amount.

Round to ____ — Rounds the check total to the defined amount when you apply this tender. Type

the rounding amount, from 0.02 to 1.00, to use for rounding the tender. Related Options: To change the decimal precision of the rounding, you must select ‘Special Currency’ in Maintenance > Store Settings > International group > Special Currency tab.

4. Select Display Adjustment.

(34)

Supporting Rounding By Tender

Display Adjustment — Displays the rounding benefit on the guest check when you apply this

tender. The rounding benefit describes the variance between the sales total and the payments total when using check rounding. The rounding benefit may also be viewed on various BOH reports. Required Options: You must select ‘Round to ___’ located on the same tab to enable this option.

5. Select Print Rounded Indicator, if this is a cash tender.

Print Rounded Indicator — Prints the text (Rounded) after the Change line on the check when

you apply this tender. Use this for cash tenders only. Required Options: 1) You must select ‘Round to ___’ located on the same tab to enable this option. 2) You must select ‘Cash’ on the Type tab to enable this option.

6. Select the rounding method to use for the tender.

Rounding Method — Specifies the rounding method to use when you apply this tender. Select Up

or Down if are rounding to the nearest nickel. For any other amount, select Nearest Up or Nearest Down. Required Options: You must select ‘Round to ___’ located on the same tab to enable this option.

7. Click Save.

8. Repeat this procedure for each tender for which you want to define rounding. 9. Exit the Tenders function.

Using the dollar currency as an example, when you apply a cash tender of $10.75, which rounds up to the nearest 1.00, for a check total of 10.76, the system tenders the check completely with a rounding benefit of 0.24.

When you use multiple payments, the system rounds the payment that reduces the check to zero only, regardless if previous payments are configured to round.

check total $10.76

apply $10.50 cash tender rounded up to the nearest 1.00

$10.50 $11.00 is tendered to the check -$11.00

rounding benefit = 0.24

check total $10.76

apply $5.00 cash tender rounded up to the nearest 1.00

$5.00 $5.00 is tendered to the check

with no rounding.

- $5.00 remaining balance due = $5.76 apply $5.76 Visa tender

rounded up to the nearest 0.05

$5.76 $5.80 is tendered to the check - $5.80

(35)

POS Enhancement Release v6.7 Page 35 Supporting Rounding By Tender

Upgrade Path

Upon upgrading from a version prior to v6.7, the rounding options in the International group in Store Settings are removed and relocated to Tender Maintenance. If you had your system configured for rounding, you must be aware of the changes the system made to your tender configuration.

Store Settings > International Group Tender Maintenance lf you previously

had ‘No Check Rounding’ selected...

...the system automatically clears all options on the Rounding tab for all tenders in Tender Maintenance. The system continues not to round.

If you previously had ‘All Tenders Round to 0.05’ selected...

...the system automatically selects ‘Round to ____’ and carries over the following options for all tenders in Ten-der Maintenance:

• The rounding to a nickel (0.05). • ‘Display Adjustment,’ if configured. • The rounding method.

If you do not want this configuration, you must access the tender and re-configure these options.

If you previously had ‘Cash Ten-ders Round to 0.05’ selected...

...the system automatically selects ‘Round to ____’ and carries over the following options only for all cash ten-ders in Tender Maintenance:

• The rounding to a nickel (0.05). • ‘Print Rounded Indicator, if configured. • The rounding method.

If you do not want this configuration, you must access the tender and re-configure these options.

(36)

Supporting Additional Pizza Modifier Groups

The existing pizza functionality in Aloha Table Service and Aloha Quick Service supports three modifier groups for each item within a given pizza category. Generally, the three modifier groups are used for 1) Size, 2) Crust, and 3) Toppings. Each modifier group is limited to 54 items; however, because of the lim-ited screen real estate, only the third modifier group can consist of more than a few items.

As of POS v6.7, the Pizza Modifier screen now supports two additional modifier groups, bringing the total number to five. This allows you to configure a more complex pizza environment to accommodate sauce choices, specialty pizzas per half, and more. For example, with five modifier groups, you could use them for 1) Size, 2) Crust, 3) Pizza Sauces 4) Pizza Toppings, and 5) Specialty Toppings.

When you take advantage of all five modifier groups, the first three appear on the screen when you initiate the Pizza Modifier screen. To display the fourth and fifth modifier groups, you must select the respective modifier group button located in the center of the screen. The system ignores any modifier groups config-ured for a pizza item beyond the five that you are allowed.

SCENARIO: A guest orders a large, pan pizza with marinara sauce, with half sausage and pepperoni and half Meat Lovers.

1. Select the pizza button to initiate the Pizza Modifier screen. The first three modifier groups

appear on the screen along with two new buttons labeled Pizza Toppings and Specialty Toppings appearing to the right of the third modifier group, ‘Pizza Sauces’ (Figure 18).

2. Select Large from the group of modifiers at the top-left of the screen (Size modifier group). 3. Select Pan from the group of modifiers at the bottom-left of the screen (Crust modifier group).

Refer to the Pizza Modifiers Feature Focus Guide for complete information on configuring the pizza functionality in the Aloha POS.

(37)

POS Enhancement Release v6.7 Page 37 Supporting Additional Pizza Modifier Groups

4. Select Marinara from the group of modifiers in the center of the screen (Sauce modifier group).

5. Touch Pizza Toppings to display the list of pizza toppings. 6. Touch the Left Half button.

7. Select Pepperoni and Sausage from the center of the screen (Pizza Toppings modifier group). 8. Touch Special Topping to display the list of specialty toppings.

9. Touch the Right Half button.

10. Select Meat Lovers from the center of the screen (Special Toppings modifier group).

11. Touch OK to exit the screen.

Figure 18 FOH Pizza Screen

Figure 19 FOH Pizza Screen - Half Order Modifier group 1: Pizza Size Modifier group 2: Pizza Crust Modifier groups 3 - 5: (Pizza Sauces selected) Modifiers for selected modifier group (3) appear here Modifier groups 3 - 5: (Special Topping selected) Modifiers for selected modifier group (5) appear here

(38)

Adding Modify Item in Aloha Spy

This RFC makes modifications to the TCP/IP data streams and COM port output, as generated by Aloha Spy, to add modifier transactions to the text overlay on the monitor screen, and to the basic information captured for possible later reference in Debout.spy. When a server adds a regular or open modifier to a menu item, the item and its modifier appear on the screen together, after exiting the modifier screen. If the server must cancel, void, or refund a modifier, this information also appears on the text overlay and in Debout.spy. This feature is immediately available upon upgrade to Aloha v6.7.0.1813, or later, and after restarting the Aloha Spy service, AlohaSpy.exe.

Refer to the Aloha Spy Feature Focus Guide for complete information on configuring and using the Aloha Spy feature.

(39)

POS Enhancement Release v6.7 Page 39 Enhancing Order Entry for Delivery Operations

Enhancing Order Entry for Delivery Operations

Changes made to the Delivery functions in Job Codes, impact the way Aloha responds to actions taken by delivery drivers. The changes do not affect the content of reports, but do provide more flexibility in both Aloha Quick Service and Table Service installations, of especially the former. In previous versions, the delivery driver and delivery order taker functions were mutually exclusive. An employee assigned to a job code with both of these options enabled was unable to perform order entry. This change removes the exclu-sivity of these functions, making it possible for a delivery driver to also enter orders, if they are not cur-rently signed out on a delivery. If the employee is signed out for a delivery, Aloha prevents order entry until they sign back in.

The ability to use the Delivery feature to recall a closed order and adjust or modify payments, in spite of access level restrictions normally denying Adjust Payments permissions, has been a great benefit in certain types of operations, but the potential for abuse has required a change. We have added a new option to the Delivery tab, in Job Codes, ‘Cannot adjust recalled closed checks.’ This new option, disabled by default, prevents order modification when the Delivery interface is enabled. Aloha displays the message, “The check is closed. This function is unavailable,” when an employee attempts to modify a check, if they are assigned to a job code in which the new option is enabled. If it becomes necessary to modify an order, a manager, or other employee with proper access-level permissions, must reopen the order and make the changes.

To restrict adjustments to recalled closed delivery checks: 1. Select Maintenance > Labor > Job Codes > Delivery tab.

2. Select a delivery job code from the ‘Number’ drop-down list and press Enter.

v6.7 RFC 67693

RFC 74654

Aloha Quick Service, Aloha Table Service Configuration Technician Store Manager

Figure 20 Job Codes - Delivery Tab

The ‘Delivery Driver’ and ‘Delivery Order Taker’ options are now exclusive.

(40)

Enhancing Order Entry for Delivery Operations

3. Select Cannot adjust recalled closed checks.

Cannot adjust recalled closed checks — Prevents an employee using this job code from

adjust-ing a recalled closed check from the FOH Delivery screen.