Odyssey/BackOffice Suite. Programming

Transcription

1 Odyssey/BackOffice Suite Programming Version Date: July 6, 2011

2 Odyssey BackOffice Suite The information supplied in this document is based on the latest information available as of the date of this document. The contents of this manual are subject to change without notice. Every effort has been made to insure the accuracy of this document, however, Comtrex can assume no responsibility whatsoever for any errors contained herein. Support for the Odyssey BackOffice Suite of software modules is provided under a contract agreement between the user and Comtrex Systems Corporation. Guarantees The software for the Odyssey BackOffice Suite is provided on a CD-ROM, and includes a security key. Comtrex guarantees that the original media and security key are free of defects when you receive them. Defective media and keys will be replaced. In no event will Comtrex Systems, Inc. be liable for consequential or incidental damage arising from use of this program. Disclaimer Comtrex Systems Corporation makes no representation or warranties with respect to the software and specifically disclaims any implied warranties of merchantability or fitness or any particular purpose. Further, Comtrex Systems Corporation reserves the right to revise this software from time to time. Copyright by Comtrex Systems Corporation. All rights reserved worldwide. This publication has been provided pursuant to an agreement containing restrictions on its use. The publication may not be reproduced without permission of Comtrex Systems Corporation, 1247 North Church Street, Suite 7, Moorestown, NJ Information contained in this document is proprietary and confidential and remains the intellectual property of Comtrex Systems Corporation. About the Company Comtrex Systems is a U.S. based software developer, systems integrator and manufacturer that specializes in information and control systems designed to solve the needs of the food service industry. Comtrex software development and systems engineering is accomplished at its headquarters building in Moorestown, NJ. Comtrex was founded in For more information on Comtrex, visit us at our Web site, on Release Information This version of this document has a release date of July 6, 2011.

3 Contents Introduction 11 Odyssey Programming Including POS/ Navigating Within Programming...12 Accessibility To Programming Options...13 Activator / Security Key...13 Windows Keyboard Usage...14 Task Tool Bars...15 Add Icon...15 Add New With Details Icon...15 Edit Icon...15 Undo Icon...15 Save Icon...15 Delete Icon...16 Search Icon...16 Copy Icon...16 Paste Icon...16 Print Icon...16 Odyssey Forms Filter Criteria Sorting...17 Staff Selections 18 Employee Configuration...18 Schedule Compliance...19 Theory of Operation...19 Schedule Compliance Definitions...20 Job Codes...20 Employees...21 Employees Employee Configuration Tab...21 Employees Rate/JC Definitions Tab...21 Employees Miscellaneous Tab...22 Operator Types...22 POS Operator Group Programming...22 Upgrade of Existing Installations...23 POS Operator Groups Operation Settings Tab...23 POS Operator Groups Manager Settings Tab...24 POS Operator Programming...24 POS Operators General Tab...25 Fingerprint Access Considerations...26 digitalpersona Fingerprint Software Installation...26 User Groups...27 Users...27 Sales Related Selections 28 Product Type...28 Sales Types...28 Transaction Types...28 Reason Codes...29 Auto Shifts...29 Odyssey/BackOffice Suite Programming Introduction 3

4 Price Levels Department Groups Departments Categories Categories General Tab Categories Applying POS Item Related Programming Changes Categories Pricing Tab Categories Display/Print Tab Categories Flags Tab Categories Itemizers Tab Menu Items Menu Items Selection Methods Menu Items Pricing and Price Levels Menu Items Deleting/Making Inactive Random Weight Barcode Items Sales Item (Menu Item) Pricing List Files List Files Auto Created List Files List File Programming Adding New List Files List File Programming General Tab List File Programming Adding List Details (POS Items) List File Programming Configuring POS Parameters of List Details List Files By Store Condiment Chains Condiment Chain Programming Automatic Condiment Entry (Macro) Suggestive Selling Definitions Suggestive Selling Not Menu Item Related Suggestive Selling Graphic Sizes Fixed Menu Type Items Fixed Menu Type Items List File Control Fixed Menu Type Items Condiment Chain Control Fixed Menu Type Items POS/2100 Control Fixed Menu Type Items Requisition Printing Fire Messages BackOffice Selections 56 Navigation Store Configuration Store Configuration Configuration Tab Store Configuration Miscellaneous Tab BackOffice Options Back Office Options Accounting Month Archive Defaults Control Account Types Control Accounts GL Account Types GL Sections GL Chart of Accounts GL Line Items Media GL Line Items Inventory Expense GL Line Items Labor Expense GL Line Items Net Sales (Franchise Fee) GL Line Item Introduction Odyssey/BackOffice Suite Programming

5 Stored Posting GL Line Item...63 Media Types...64 Medias...64 Media Programming Selection Methods...65 Media Programming General Tab...66 Media Programming Finalize Media...67 Interactive Charge Posting...70 Media Programming Foreign Finalize Media...70 Media Programming Transfer Currency In/Out Media...71 Media Programming POS Paid Out Media...73 Media Programming POS Paid In (ROA) Media...74 Media Programming Service Charge Media...75 egift Cards Voiding Sale or Voiding Add Value...76 Media Programming Gift Certificate Accountability...77 Media Programming Tip/Gratuity Media...79 Media Programming Tips Paid Media...80 Media Programming Void Item Media...80 Media Programming Line Item Discount Media...81 Media Programming Standard Coupons...82 Standard Coupon Evaluation Rules...82 Media Programming Combo Coupons...83 Media Programming Subtotal Item Discount Media...84 Media Programming Dollar Subtotal Discount Media...85 Media Programming Refund Transaction Media...85 Media Programming Waste Item Media...86 Media Programming Overring Transaction Media...86 Media Programming Tax / Add On Media...87 Media Programming VAT Media...87 Media Count Units...87 Scanned Coupon Definitions...88 Coupon Menu Groups...88 Media List Files...89 Media List Files General Tab...89 Media List Files List Details Tab...89 Itemizer Types...89 Itemizer Calculation Types...90 Itemizer Programming...91 Itemizer Programming General Tab...91 Itemizer Programming Tax Table...92 Itemizer Programming Tax Table Discontinuities...93 Miscellaneous Definition Programming...94 Track Item Type Programming...94 Report Definition Programming...94 Configure Selections 95 POS Terminal Options...95 POS System Options...95 Printer Configuration...95 POS/2100 Configuration 96 Defining Terminals In The POS Network...96 Navigating Within POS/2100 Configuration...96 Printer Configuration...98 Printer Operation Software Overview (Technical)...98 Odyssey/BackOffice Suite Programming Introduction 5

6 Printer Configuration Printer Types Printer Configuration Printer Definitions Printer Configuration Terminal Print Options Creating a Closed Check Log Printer Configuration System Print Options Printer Configuration Sale Types / Output Groups Printer Configuration Scoreboard Printer Configuration Surveys Order Video Setup Order Video Files Overview File Layout for RQV.INI Order Consolidation - Keyword CombineItems = Display New Items Only - Keyword CheckMode = Summary Screen - Keyword SummaryScreen = ScoreBoard Related File SLOGO.TXT POS System Options POS System Options POS2100 Programming POS System Options Revenue Centers POS System Options Back Office Software POS System Options Day Parts POS System Options Shift Definitions POS System Options Credit Card Options General Tab POS System Options Credit Card Options Credit Card Types Loyalty Network Options POS System Options Credit Card Options - Loyalty Voucher Options POS System Options Credit Card Options - Loyalty Rewards Options POS System Options Credit Card Options Nectar/Vouchers POS/2100 and DataCap Network Configuration POS System Options Ordering Systems POS System Options Desktop Options POS System Options Custom Colors POS System Options Miscellaneous POS System Options Scale Definitions POS System Options Scale Tare Lists POS System Options Scale Buttons POS Terminal Options POS Terminal Options Selection Methods POS Terminal Options Filter Criteria POS Terminal Options Copy / Paste Operation POS Terminal Options Posting Configuration POS Terminal Options Transaction Options Cafeteria Mode Operations OPOS Drivers Using with POS/ POS Terminal Options I/O Devices Security/Surveillance System Interface Berg/EasyBar Liquor Dispensing Interface LCD Customer Display POS Terminal Options Sale Types POS Terminal Options Message Prompts POS Terminal Options Desktop Options POS Terminal Options Auto Shifts POS Terminal Options Miscellaneous Inventory Selections 156 Inventory Options Introduction Odyssey/BackOffice Suite Programming

7 Stock Control Areas Deleting a Stock Control Area Stock Types Inventory Movement Types Inventory Count Frequencies Inventory Count Frequency Programming Exclusive Inventory Count Frequency Inventory Locations Inventory Delivery Codes Vendors Vendor Programming Configuration Tab Vendor Programming Miscellaneous Tab Vendor Programming Import/Export Tab Inventory Item Class Vendor Item List Vendor Item List Programming Vendor Item List A Generic Import Methodology Receive Reason Codes Inventory Items Inventory Item Units of Measure Inventory Item Programming General Tab Inventory Item Programming Options Tab Inventory Item Programming Vendor Items Tab Inventory Item Programming Location Tab Inventory Item Programming Substitution Tab Inventory Item Locations Batch Definition Recipes Recipes Programming Recipe Tab Recipe Programming POS Recipe Tab Recipe Programming Picture Tab Recipes Simplified Costing Accounts Selections 176 Internal Account Types AccountCharge Types Account Type Programming General Tab Account Type Programming Credit Limit Tab Account Type Programming Reset Tab Account Response Codes Customer Account Type Programming Customer Programming General Tab Customer Programming Home Tab Customer Programming Work Tab Customer Programming Delivery Tab Delivery Customers Added at the Point-of-Sale Delivery Related Entries Delivery Cities Delivery States Delivery Zip Codes Delivery Zones Delivery Statistics AccountCharge Member Programming AccountCharge Member Programming General Tab AccountCharge Sub-Accounts Odyssey/BackOffice Suite Programming Introduction 7

8 AccountCharge Member Programming Patronage Tab AccountCharge Member Programming Import/Export Tab AccountCharge Member Programming Picture Tab AccountCharge POS/2100 Considerations Delivery POS/2100 Considerations Sales Type and Operator Type Transferring Delivery Checks Retention of Orders On POS/ Tracking Totals/Delivery Statistics For Delivery Customers Using Caller ID with Delivery General Operation POS Operation With Multiple Incoming Calls CallerIDService.exe POS/2100 Application Programming 199 Overview Programs And Files Loaded On The POS Terminal Training Mode on the POS/ Changing Training Status of a POS Operator POS Operation in Training Mode Accessing POS/2100 Programming POS Operation During Programming Point-Of-Sale Desktop Types Point-Of-Sale Application Text Programming Tips Desktop Objects Button Window Sizing/Positioning A Button Window Button Window Object Properties Button Configuration In A Button Window Desktop Objects Status Window Desktop Objects Bitmap Window Desktop Objects Entry Window Desktop Objects Previous Order Window Desktop Objects Alarm Clock Log In Desktop Selection Options Desktop Selection Save Template Desktop Selection Load Template Deleting Desktops Log In Desktop Button Types Button Type Access Training Button Type ASCII Button Type Change Operator Secret Number Button Type Clear Button Type Closed Checks Button Type Driver Speed Pay Button Type Enter Button Type Execute Program Button Type Execute Program - MGR Button Type Exit Button Type Future Orders Button Type Limited Quantity Button Type List Checks Button Type Manager Button Type Message Board Button Type New Check Introduction Odyssey/BackOffice Suite Programming

9 Button Type No Sale Button Type Recipe Button Type Register Account Fingerprint Button Type Register Employee Fingerprint Button Type Reports Button Type Settlement Operator Button Type Shift Select Button Type Table Ready Button Type Time Clock Button Type Transfer Checks Button Type Transfer Delivery Checks MapPoint Interface Button Type Undefined Button Type Windows Manager View Desktop Table List Desktop Table List Desktop Screen View Table List Desktop Informational View Table List Desktop Programming Access Table Section Selection Options Table Section Table Objects Table Section Table Object Properties Table List Desktop Button Types Table List Desktop Refresh Future Orders Desktop Future Orders Desktop Screen View Future Orders Desktop Displayed Information Future Orders Desktop Button Types Sales Desktops Sales Desktops Programming Access Sales Desktops Restricted Access Sales Desktops Guest Check Object Sales Desktops Selection Options Sales Desktops Button Types Split Check Desktop Split Check Desktop Selection Options Split Check Desktop Moving Items Split Check Desktop Button Types Odyssey/BackOffice Suite Programming Introduction 9

10

11 Introduction Odyssey Programming Including POS/2100 This document has a release date of July 6, It covers the programming module which is an integral part of the Odyssey BackOffice Suite of software. It includes all documentation covering BackOffice parameter programming for the Windows point-of-sale module, the POS/2100. There is a companion document which covers Odyssey/BackOffice Suite Operations. The concepts of the BackOffice organization are fully covered in the Operations document. The purpose of this Programming manual is to: Provide a sequence for initially configuring a BackOffice database in conjunction with the Windows point-of-sale module, the POS/2100. Explain how the BackOffice database is used by the POS/2100 at the point-of-sale. Cover the various shortcuts implemented in the configuration module to speed the process of database creation. Explain, in reasonable detail, the options and parameters which are being configured and how they inter-relate with the operation of both the BackOffice and the point-of-sale. Provide a separate section which covers the programming included in the point-of-sale application. NOTE: This release of this document includes documentation covering the programming included in the point-of-sale application. Throughout this document, the words Configuration and Programming are used interchangeably, as are the words Menu Items and Sales Items. When referring to an item which is entered, or rung, on the point-of-sale terminal, the document consistently uses the wording POS Items. The words Finalizing Media, Payments and Payment Media are also used interchangeably. The main module of the Odyssey Suite is interchangeably referred to as Odyssey/MWS, Odyssey and Odyssey BackOffice. Odyssey/BackOffice Suite Programming Introduction 11

12 Navigating Within Programming The August of 2007 release brought an entirely new navigation method to all Odyssey BackOffice programs, with a look and feel similar to recent releases of Microsoft's Outlook and Small Business Accounting. A partial screen of the programming screen is shown below. The top left of the screen provides access to the primary software modules, the BackOffice, Reports, Programming and Inventory. The middle of the left always displays the functions (forms) applicable to the selected module. These are provided in a condensed tree structure. Merely click on the box with the + to expand a particular selection. To isolate one of the forms, use the wide buttons on the bottom left of the screen. For example, to only see the programming options applicable to Staff, click on the Staff button. Only the Staff forms will show in the middle left. To return to "All Forms", click the icon on the bottom right of the left portion of the screen. When a new selection is made, using the tree structure on the left, the open form is automatically closed and the new form is opened on the right portion of the screen. As shown above, another method of navigation is provided at the top of the screen. 12 Introduction Odyssey/BackOffice Suite Programming

13 Accessibility To Programming Options In order to access the Odyssey BackOffice Suite you must log on as a particular User using a unique password. The ability of a particular User to access certain areas of programming can be restricted. This restriction is established at the User Group Level. Every individual User must belong to a User Group. However, there is no restriction on the number of User Groups, so each individual User could theoretically have his/her own User Group if this is desired. The default database has a User Group Admin. There is a default User Admin, with a default password of Admin. The User Group Admin has access to all functionality of the Odyssey BackOffice Suite. For initial database programming you should log on as this User. Prior to installation, different Users and User Groups should be established to fit the particular installation. Resellers should always leave a User Group with unlimited access and a User belonging to that User Group for support purposes. Activator / Security Key The Odyssey Suite is supplied in two versions; the basic version which also includes all support for Odyssey AccountCharge and one which includes Odyssey Inventory. Both versions require that an activator, or security "key", be installed on the LPT1 port of the computer on which it is operating. The activator is supplied with all "live" copies the Odyssey Suite. If no activator is present, you will be unable to process more than five Sales Days. If the appropriate activator for Odyssey Inventory is not available, you will be limited to five Inventory Periods, or five Inventory processes, whichever occurs first. Both versions of the activator for the Odyssey Suite provide a license for a single POS/2100 user. Additional POS/2100 user licenses can be added either at initial delivery or after initial installation. The Odyssey Programming module is fully accessible WITHOUT any Activator/Security key present. Odyssey/BackOffice Suite Programming Introduction 13

14 Windows Keyboard Usage Any function, field or task throughout Odyssey Suite can be accessed via your mouse or other pointing device. Windows also provides the ability to use the keyboard to shortcut a function instead of using the point and click mouse interface. The following is a brief catalog of important keyboard shortcuts: <Shift> + <Home> Ctl + c Ctl + v Alt + n Alt F1 Alt + <Space Bar> Tab <Shift> + <Tab> Home End <Space Bar> Key Sequence Function Highlights the contents of the current field from the input cursor position through the beginning of the field for replacement with alternate typed in text. Copies the highlighted text to the clipboard. Pastes the clipboard contents to the cursor location. Activates a push button or Menu Item, where n is an underlined letter on that push button or Menu Item. Activates the menu bar for the current application. Activates the help function. Within both the Odyssey/MWS and Odyssey Programming modules, this is context-sensitive Help, in that the displayed section of the Help File will relate to the display area of the program itself. Activates the control box for the current window The control box allows you to move, minimize, or close the window. Moves the input cursor forwards through an input form. Moves the input cursor backwards through an input form. Moves the input cursor to the beginning of an input field. Moves the input cursor to the end of an input field. Toggles an option button or check box field on or off when the input cursor is on that field. 14 Introduction Odyssey/BackOffice Suite Programming

15 Task Tool Bars Different screens within the Odyssey Suite will present different versions of a Task Tool Bar. The following icons, however, are used throughout the Odyssey Suite. Add Icon A left click on this icon will to add a new data element. Add New With Details Icon This icon is only available in certain screens within the Programming module. A left click on this icon will create a new record copying the details of the selected record. Edit Icon A left click on this icon will bring you to the editing screen for a selected record or data element Undo Icon A left click on this icon will undo the previous action. The function is to cancel any entries and not save. Save Icon A left click on this icon will save the entered information, either a data element or selected line. Odyssey/BackOffice Suite Programming Introduction 15

16 Delete Icon A left click on this icon will delete the selected data element or line. Search Icon A left click on this icon in certain forms will change the grouping of items on the list. Copy Icon This icon is only available in certain screens within the Programming module. A left click on this icon will copy all information on the selected record (for instance a terminal s selected programming definitions) to the clipboard. Paste Icon This icon is only available in certain screens within the Programming module. A left click on this icon will paste the contents of the clipboard, previously copied from one selected record, into a selected record(s). Print Icon This icon is only available in certain screens within the Programming module. A left click on this icon will bring forward the Print Manager for printing a particular screen. 16 Introduction Odyssey/BackOffice Suite Programming

17 Odyssey Forms Filter Criteria Sorting Most of the programming forms displayed within the Odyssey Programming module show an Item Count at the top of the form. This can be a useful tool when comparing written lists with the information already entered into the Odyssey database. An example is shown below: The form illustrated is new with the March 2005 release of Odyssey. The form has already been sorted to only show Inventory Class "Bottle Beer" in Inventory Location "Walk In" and there are 55 count units for Bottled Beer in the Walk In. Notice, however, that there are three count units for each of the displayed inventory items. What if you only wanted to know how many count units of "Bottle" are located in the Walk In, in order to compare with the count units at a different Inventory Location such as the "Bar". You can filter any form using any of the banner titles at the top of the form. To only display count units of "Bottle", first left click on the banner title "Count Unit". The list will now sort alphabetically by count unit. Next, right click in any row. A filter selection window will display as shown below, where the letter "B" has been entered. Left click on the OK button to apply the filter criteria. The programming form above is shown again below after applying the filter criteria of "count units which begin with the letter 'B'". Note that the Item Count now indicates the number of count units beginning with the letter "B". This filter selection criteria is available on all Odyssey programming forms. Odyssey/BackOffice Suite Programming Introduction 17

18 Staff Selections Employee Configuration The entries programmed here define overall store level configuration relating to the labor analysis and control module of Odyssey/MWS. Day A Work Week Begins. Use the dropdown to select the first day of a Work Week. Generally, this will be the same day as you selected from the screen Back Office Options, under Day Account Week Begins. Time A Work Day Begins. Select the time of day that a Work Day Begins. The Hour, Minute and Second are separately programmable. Click into the appropriate area and either enter the number or use the up and down arrows to the left of the display window to select the time. Target Labor Cost Percent. Certain reports which analyze sales against labor cost will highlight in red when the labor cost represents a greater percentage of sales than the entered number. Overtime Rate. If an overtime rate will be applicable for any employees, enter the rate. As an example, if overtime is time and a half, enter 1.5. Daily Overtime Start Hour. If an overtime rate begins to accrue after a set number of hours worked in a single Work Day, enter that number. As an example, more than an 8 hour shift might start an overtime rate. If Daily Overtime does not apply, enter a number greater than 24. Weekly Overtime Start Hour. If an overtime rate begins to accrue after a set number of hours worked in a single Work Week, enter that number. As an example, more than 40 hours in a week might start an overtime rate. Use Highest Hourly Rate for OT. Employees clock in at a particular Job Code and can be paid different rates depending on the Job Code. When an employee s hours during a Work Week exceed the number in Weekly Overtime Start Hour, the employee may be working at a pay rate which is lower than most of the hours worked during the week. Enter a check in this box if the overtime rate should be applied to the Highest Hourly Rate for the employee during the Work Week. If the overtime rate should apply to the pay rate in effect when the hours worked exceed the Weekly Overtime Start Hour threshold, do not check this box. Server Tip Percent. When an employee clocks out on the point-of-sale terminal, and if the job code is Prompt For Tip Declaration for the employee, then the POS/2100 software will prompt for any non-declared cash tips. As an aid, the software will use the entered percentage here to compare the total amount of tips already entered to this percentage of sales. Server Distribution Percent. This percentage is used as an aid in assisting servers who distribute a portion of their collected tips to buss help or bartenders. The result of this calculation will print on the POS Operator report generated at the point-of-sale. Payroll Export Type. This pertains to the export of attendance information from the Summary Time Card Report when the Create Export File is selected. The two choices are Great Plains and ADP Pay expert. ADP Company Code. Only pertains when exporting payroll information to ADP. This three digit code should be supplied by ADP to the customer. Under the Scheduling Increment Section: Scheduling Increment. The selection here determines the grid on the scheduling screen. The typical scheduling increment is either 15 or 30 minutes. The width of the screen is a day, so scheduling increments of 15 minutes will require significant scrolling in the scheduling process. Allow Only 1 Break Per Shift. This MUST be set as checked. Under the Miscellaneous Section: Employee Paid For Breaks. Place a check mark in this box if employees are paid while on break. With no check, employees are not paid when on break. The Flash View Report, along with all other labor control and analysis reports, will reduce the number of employees On The Clock when an employee is on break and will also not accrue any labor costing for an employee who is on break. 18 Staff Selections Odyssey/BackOffice Suite Programming

19 Allow Clock With Open Checks. Generally you will NOT want to check this box. A check in this box allows an employee, who is designated as a POS Operator, to clock out while the POS Operator has checks open on the system. With no check in the box, the employee will be prompted when attempting to clock out that he/she has open checks which should be either transferred or finalized. Auto Z Server With Clock Out. The pertains to the POS Operator report taken at the point-of-sale terminal. With a check mark here, only totals from the current POS Operator's shift will show when a POS Operator works more than one shift per day. Confirm Clock In/Out Times. With a check in this box, the point-of-sale software will provide an additional screen display at both clock in and clock out to confirm the entry and the exact time. With no check, the action will be accepted by the point-of-sale software and a clock chit will be immediately generated. It is generally a good idea to check this box to prevent erroneous entries. Schedule Active. This function is not available. The ability to generate a schedule is included in Odyssey/MWS. However, the ability to preclude clocking in or clocking out if the punch does not conform to the schedule is NOT included as of the date of this documentation. Fingerprint ONLY Clock In/Out. Place a check mark here if the point-of-sale system is equipped with Digital Persona fingerprint readers and you wish to have employees ALWAYS use this sensor. Show Social Security # on Reports. Generally this will NOT be checked for employee privacy. Schedule Compliance The Schedule Compliance Monitor is a functionality added for U.S. locations which are using time and attendance for clocking in and out. The Monitor is a tool to assist in complying with the labor laws relating to minors. The active software module is an executable, automatically installed as a service on the server, either the BackOffice pc or the Workstation Server. The file is ScheduleComplianceMonitor.exe and it is located in the folder C:\Program Files\Comtrex Systems\ScheduleComplianceMonitor. Once installed, the service will automatically load each time the pc or terminal is booted. To totally disable this function, use Control Panel to access Administrative Tools then select Services. This service is listed as Comtrex Schedule Compliance Monitor. You may right click on the line, select Properties for the service and then under the General tab change the Startup Type from Automatic to Disabled. You can also use this access to determine if your release of software included this functionality. The functionality requires release Version or later to function. You may leave the service running but disable all of the functionality through unsetting a flag in this programming section. Theory of Operation The service, Comtrex Schedule Compliance Monitor, is activated by a setting defined below. If activated, the service will check the employee punch file in the database against the Schedule Compliance settings at a predefined interval, defined below as Alarm Interval Minutes. When a potential violation of a labor law relating to a minor is about to occur, the service will warn management. Since the manager will most likely not be monitoring the BackOffice computer, the POS terminals will be used to warn of a possible impending violation. Each and every POS terminal will show two prompts when a potential violation is about to occur. Regardless of the current state of the POS terminal, these two prompts must be dismissed by the POS Operator. The first warning is generic, that is, it is independent of the exact violation about to occur. The POS Operator must depress the OK button to dismiss the prompt. When this prompt is dismissed, a second prompt will appear. This will list all of the potential violations. Of course, if the prompt is ignored, then Odyssey/BackOffice Suite Programming Staff Selections 19

20 the prompts will not list potential violations but actual violations. If the violation is cured, e.g. a minor goes on break or clocks off for the day, then the warning will not reappear. If the violation is not cured after the expiration of the Alarm Interval Minutes, the cycle will repeat. Schedule Compliance Definitions Monitor Active. A check mark here is required to enable the Schedule Compliance functionality. Alarm Window Minutes. This defines the warning time provided in advance of a potential labor violation. It works in conjunction with the last entry, Alarm Interval Minutes. Age. Defines the maximum age for a minor. If an 18 year old is not subject to these provisions, then enter 17. The program will use the birthdates programmed in Employees for evaluating potential labor violations. Max Hours Per Day. This is a whole number entry. This defines the maximum number of hours a minor is allowed to work in a single day. Max Hours Per Week. This is a whole number entry. This defines the maximum number of hours a minor is allowed to work in a work week. Max Hours Before Break. This is a whole number entry. This defines the maximum number of hours a minor is allowed to work before a mandatory break must be taken. Minimum Break Minutes. This entry is similar to the entry programmed for each employee, Subject to Minimum Break. That flag applies whether the employee is a minor or not. You would generally NOT set the flag for minors and would use this entry instead. A minor will not be allowed to go off break prior until this minimum number of break minutes has been taken. Alarm Interval Minutes. This setting defines how often the Schedule Compliance Monitor checks for violations. In order to not totally disrupt POS operations, a reasonable setting is 4 minutes. This setting affects the operation of the setting Alarm Window Minutes. If the Alarm Window Minutes is set for 10 minutes, and the Alarm Interval Minutes is set for 4, it is possible that the actual window will only be slightly greater than 6 minutes if the Monitor has checked at 10 minutes plus 1 second prior to a violation occurring. To get an average warning of 10 minutes, you could set the Alarm Window Minutes to 12. That way you might get almost 12 minutes of warning or you might get just over 8 minutes of warning, depending on when the Monitor checked the punch information against the Compliance Definitions. Job Codes A punch record for an employee must include a Job Code designation. In addition, pay rates for employees are defined by Job Code. Odyssey/MWS supports up to 256 Job Codes. A variety of analytical reports are available on labor costing by Job Code. Job Code #. This merely a numeric identifier for the Job Code. The default database follows a convention of beginning Job Codes at 10 and incrementing by 10 when creating new Job Codes. Enter any number between 1 and 256. Job Code Description. Enter up to sixteen characters to describe the Job Code. Grace Minutes. Pertains to schedule enforcement with the POS2100. A manager will be required to Clock IN or OUT an employee if the punch time exceeds this window parameter, either before the punch time or after the punch time. Before and After. Pertains to schedule enforcement with the POS2100. A manager will be required to Clock IN or OUT an employee if the punch time exceeds this window parameter, either before the punch time or after the punch time. Prompt For Tip Declaration. Check this box if employees who are clocking out at this Job Code should be prompted to declare any additional tips. This flag is only evaluated if the Employee is also a POS Operator. (Only set this flag if you have set the system flag to automatically pay tips.) Overtime Allowed. Place a check in this box if this Job Code should accrue overtime, based on the settings under Staff Employee Configuration. With no check, no overtime calculation will ever be applied for punches using this Job Code. Daily Overtime. Place a check in this box if this Job Code should accrue overtime on a daily basis, based on the setting under Staff Employee Configuration Daily Overtime Start Hour. With no 20 Staff Selections Odyssey/BackOffice Suite Programming

21 check, regardless of this setting, no daily overtime calculation will be applied for punches using this Job Code. Job Code Color. Double click on the displayed field and select a color code for use during scheduling to designate this Job Code on the scheduling grid. Employees This is the section where the individual information is entered for employees, including pay rates at various Job Codes. This selection is now also available from within the core BackOffice module. This allows Managers, not authorized for any other programming, to use this section without having access to the full Programming module. Employees Employee Configuration Tab Social Security Number. This is an eighteen character text field. You should determine a convention for entering Social Security Numbers and follow that convention, i.e. enter or as a template for all employees. POS Clock #. Enter up to a four digit number. This number is printed on reports to identify the employee. (Formerly used as the employee clock in/out number. See POS Swipe # below.) POS Operator #. If this employee is also a POS Operator, enter the POS Operator # from the screen POS Operator Definition Programming General Tab. If this employee is NOT a POS Operator, enter a 0. Employees who are POS Operators, and working a tippable Job Code, will be prompted to declare tips when clocking out. In addition, an employee is who is also a POS Operator will not be allowed to clock out if logged on as an active operator of any point-of-sale terminal. POS Swipe #. Number used to clock employee in/out at the point-of-sale. Defaults to the same entry as POS Clock #, but may be changed. Allows for entry of up to sixteen digits so that the same magnetic card can be used both to enter the POS Operator Secret Number and to clock in/out employees, who are also POS Operators. Nick Name. Enter up to sixteen characters of descriptive text for the Operator. This field is used on various forms and reports to identify the employee where there is not room for a full last name and first name. It is a good idea to keep this field unique, since it appears on numerous dropdown lists. First Name. Enter up to twenty characters for the employee s First Name. MI. Enter up to three characters for the employee s Middle Initial. Last Name. Enter up to thirty characters for the employee s Last Name. Address. Enter up to twenty characters. Apt #. Enter up to ten characters. City. Enter up twenty characters. State. Enter up to five characters. ZIP. Enter up to twelve characters. Phone Number. Enter up to fifteen characters. Birth Date. Enter the birth date as a date field, depending on your Windows settings. Date Hired. Enter the hire date as a date field, depending on your Windows settings. Employees Rate/JC Definitions Tab This is the screen where employee pay rates are entered. Valid Job. Click in the Valid Job field and select from the dropdown lf all Job Codes. While the Job Code # is entered, the dropdown also shows the Job Code Descriptor. NOTE: The Job Code which is first on the list will be the Default Job Code. A Manager may be required in order to allow an Employee to clock in at a Job Code other than the first one on the list. Odyssey/BackOffice Suite Programming Staff Selections 21

22 Pay Rate. Click in the Pay Rate field and enter the pay rate for this employee at this Job Code. Note: Only enter one Pay Rate at a specific Job Code. Deductions. This is a memo field and is not utilized by any software. Married. This is a memo field and is not utilized by any software. Overtime Applicable. For an employee to accrue any overtime, regardless of the settings in Employee Configuration or Job Code configuration, you must place a check in this box. Minimum OT Base Rate. If there is no minimum overtime base rate, leave this field at the default value of $0.00. If the base rate for an employee (the rate to which the overtime multiplier is applied) is different than the normal pay rate, enter this Minimum Overtime Base Rate. Salary Employee. Place a check in this box if this employee will not clock in and out on the point-ofsale. Yearly Salary. Enter the amount of the yearly salary for this employee. Note: Employees who are salaried and who also have a link to a POS Operator # will be able to operate the POS/2100 without clocking in. (March, 2005) Employees Miscellaneous Tab Notes. This is a free entry memo field. Schedule Disabled. This field is not applicable as of the date of this documentation. Allow Override of Job Code Without Manager. If this employee may clock in at more than one Job Code, place a check mark here if a Manager is required (at the time of clocking in) in order for this Employee to clock in at any Job Code other than the Default Job Code. Terminated. Place a check box here when an employee is terminated. Terminated employees may not clock in nor have punch records added through Odyssey/MWS. Date Terminated. Enter the termination date as a date field, depending on your Windows settings. Operator Types There are only three Operator Types. This form is made available solely for translation purposes in foreign language countries. POS Operator Type 3 is used to parse the list of all POS Operators displayed with Button Type Transfer Delivery Checks at the point-of-sale and should be reserved for drivers. POS Operator Group Programming POS Operator Groups are new in July of Prior versions had various permissions for different POS Operators programmed on an individual basis. This new implementation copies the concept from the BackOffice of User Groups and Users. Like the BackOffice User Group configuration, you may establish as many POS Operator Groups as you desire. Typical use might be: Operator Shift Manager Store Manager Each of the above would have an increasing level of responsibility and capability. POS Operators are assigned to a POS Operator Group. Their level of authority is therefore established by the POS Operator Group rather than individually. 22 Staff Selections Odyssey/BackOffice Suite Programming

23 Upgrade of Existing Installations For upgrades of existing installations, two POS Operator Groups are created. The software finds the first POS Operator without Manager Mode Allowed and uses all of the settings to create POS Operator Group 1. Then the settings of the first POS Operator with Manager Mode Allowed is used to create POS Operator Group 2. Existing POS Operators are then assigned to one of these two groups based on their setting of Manager Mode Allowed. Immediately after upgrading, the installer needs to create as many new POS Operator Groups as will be required and set the authorization levels as required. Then the list of POS Operators must be evaluated and each POS Operator assigned to a POS Operator Group. POS Operator Groups Operation Settings Tab Auto Gratuity. A check mark here will cause any transaction for this POS Operator to have an automatic gratuity added. The media used to generate the automatic gratuity is defined under POS Terminal Options Miscellaneous Options. Master Server. In general, a check box here will allow this POS Operator to pick up any other POS Operator s guest checks, however, this flag interacts with the Auto Transfer flag and the Allow Sales flag. Auto Transfer. This flag is only applicable if there is a check in the box Master Server. With a check in both boxes, the guest check belongs to this POS Operator when it is picked up. With no check in the Auto Transfer box, this POS Operator is allowed to ring sales (see flag Allow Sales ) on any POS Operator s guest checks. Checks Available for All. This flag is very useful for bartenders. With a check in this box, the guest checks which belong to this operator may be picked up by any POS Operator, even if the POS Operator is NOT a Master Server. Normally on the Table Section Screen of the POS/2100, an operator is only shown his or her own guest checks in the middle column of the display. There is a touch point above this, with a label Refresh which will show not only the logged on POS Operator s guest checks, but those of all POS Operators with this flag. This functionality allows servers to retrieve a bartenders checks, and generally assume ownership of the guest check, without the server being a Master Server. Transfer At Finalize. This flag is not implemented in the software as of the date of this documentation. Allow Sales. An operator who does not have a check mark in this box will not be able to access any Sales Desktop. This flag is designed to work in a special manner, in conjunction with the flags Master Server and Auto Transfer for a Hostess. A Hostess would be set as a Master Server, without Auto Transfer and with Allow Sales as a No. The Hostess would be able to access the Table Section screen and transfer a guest check to a new table. The ownership of the check would remain with the bartender. The server would see a table in gray on his/her Table Section, then use the Refresh button to see the Check Number and Table Number. This provides a seamless transfer of a patron from the bar to a table while retaining control and avoiding any manager intervention. Allow Cash Bar. This flag is not implemented in the software as of the date of this documentation. Allow No Sales. Check this flag to allow this POS Operator to use the No Sale button. Note, however, that there is a flag under POS System Options Miscellaneous Options which provides overall control over the use of a No Sale button. An individual POS Operator can only perform a No Sale if this function is enabled for the system. Disable POS Operator Report. This flag pertains to the report set available at the POS/2100 pointof-sale terminal. A check mark here will disable the ability of this POS Operator to view his or her own POS Operator report. Allow AccountCharge Search. This flag pertains to the ability to use the Search Name and Search Number buttons on the entry screen when an Account Number must be entered. If you only wish certain operators to query the database to select an account to which charge, only check this flag for authorized operators. Odyssey/BackOffice Suite Programming Staff Selections 23

24 Allow Combine Checks. If this POS Operator is to be able to combine checks, place a check mark in this box. With no check mark, the Button "Enable Combine" on the Table Desktop will be disabled for this operator. Single Transaction Operator. This is for a special mode of operations in U.K. pubs. You would always have no check in the flag "Server Stay Down" under POS Terminal Options Transaction Options on the Start of Trans. tab. A POS Operator is logging on, therefore, for each round. With a check here, when a POS Operator has "sent" a guest check, to allow another POS Operator to use the terminal, the next time that POS Operator swipes his/her card, the "sent" transaction is automatically retrieved. Hence, a "single transaction" at a time POS Operator. POS Operator Groups Manager Settings Tab All of these Yes/No entries either allow or disallow certain operations for POS Operators assigned to this POS Operator Group at the point-of-sale terminal. Allow Refunds. This flag pertains to both an Overring Transaction and a Refund Transaction. The flag also pertains to access from the Closed Check screen. A Closed Check may be modified in three ways; it may be overrung, refunded or the payment method may be changed. Either this flag, or the flag Allow Media Transfers must be checked in order for the POS Operator to Select a Closed Check. Allow Void/Waste. This flag pertains to use of the Void Item Media (where the item has already been requisitioned) and the Waste Item Media. Allow Finalize. This flag pertains to all Finalizing Media. Allow Discounts. This flag pertains to all discounts. Allow Media Transfers. This flag pertains to the ability to modify the payment method on a Closed Check. Allow Function Keys. This must be set in order for any of the POS Price Level Button types to be used. Allow Shift Select. This flag pertains to the ability of this POS Operator to change the designated shift on a terminal using the Shift Select button on the Log In Desktop. Allow RA, PO, and Tips Paid. This flag pertains to both the POS Paid Out and the POS Paid In (ROA) medias. The Tips Paid media is not available as a button on the POS/2100. POS Reports Allowed. This flag pertains to the ability of the POS Operator to access the POS Reports button on the Log In desktop of the POS/2100. Allow Check Transfers. This flag must be set in order for the POS Operator to use either Button Type Transfer Checks or Button Type Transfer Delivery Checks. Manager Mode Allowed. This flag provides control to any function where a Manager is Required that is NOT covered by any other flag. POS Programming Allowed. This flag provides the ability to configure the POS/2100 database. As a general rule, POS programming should only be available to a single POS Operator and should always be performed on either the Back Office Server or a designated point-of-sale terminal. Allow Service Charges. This flag pertains to any Service Charge media. NOTE: Access to Sales Desktops on the POS/2100 whose names begin with the three characters Mgr (this is NOT case sensitive) is restricted to POS Operators with the Manager Mode Allowed flag set to Yes. This restriction only applies when the Button Type Desktop is depressed. If you wish to restrict access to certain Sales Desktops, DO NOT enter these desktops as the End of Sale Desktop in POS Terminal Options Desktop Options or as the Default Sales Desktop under POS Operators General Tab. POS Operator Programming This screen is used to define operators of the point-of-sale terminal. POS Operators who are also employees require a link, established under Staff Employees Employee Configuration Tab, so you will be required to re-access the Employee Configuration, after entering POS Operators, to associate employees with Operators. 24 Staff Selections Odyssey/BackOffice Suite Programming

25 This selection is now also available from within the core BackOffice module. This allows Managers, not authorized for any other programming, to use this section without having access to the full Programming module. POS Operators General Tab POS Operator #. This is a numeric designation for the POS Operator which is shown on various reports, including the Transaction Detail Log. It is NOT the number entered by the POS Operator to log on to the point-of-sale terminal. Enter a unique number for the Operator, from 1 to POS Name. Enter up to sixteen characters to uniquely identify this POS Operator. If this POS Operator is also an employee, often this is the same entry as the Nick Name entered under Staff Employees Employee Configuration. The POS Name is REQUIRED to be unique Secret Number. This is the unique number used by the POS Operator to log on to the point-of-sale terminal. It is also the number encoded onto a magnetic card reader. The form will accept a swipe of a magnetic card reader while the cursor is in this field if a keyboard wedge type card reader is attached to the PC running the program. This entry is hidden from view on the programming form. NOTE: The POS Operator s Secret Number should be encoded on Track 2 of magnet cards with a leading ; character (semi-colon) and the keyboard wedge card reader should be configured to supply a trailing CR/LF character. Operator Type. Use the dropdown to select one of the three Operator Types. One use of this field is in conjunction with Drawer Banking and the automatic transfer to a POS Operator of one of up to three pre-established banks. This is covered in the section under Transfer Currency In/Out Media Existing Default Medias. Additionally, Operator Type 3 is reserved for designating Drivers. It is used to sort the list of POS Operators presented with Button Type Transfer Delivery Checks. POS Operator Group. Use the dropdown to associate this POS Operator with one of the POS Operator Groups defined in the previous section. It is the POS Operator group which will control the functions allowed by this POS Operator. Temp POS Operator Group. Normally, this is identical to the POS Operator Group. Use the dropdown to temporarily associate this POS Operator with a different group for the current Sales Day. The Temp POS Operator Group will be automatically reset to the POS Operator Group at the End of Day. This functionality allows an Operator to assume certain managerial functions on a single day basis. Default Sales Desktop. This field acts in conjunction with the field programmed under POS Terminal Options Desktop Options. The Sales Desktop displayed on a particular terminal can either be set for the terminal or vary by POS Operator. For terminals set with Default Sales Desktop By POS Operator, select the Sales Desktop from the dropdown list. NOTE: Usually when POS Operators are being initially configured, the POS/2100 database is NOT defined. If you are configuring the Sales Desktop on a by-pos Operator basis, you will need to revisit this screen after you have completed all Desktop programming for the POS/2100. Default Table Section. This field defines the Table Section which will be displayed the first time this POS Operator logs on to the point-of-sale. If a POS Operator opens a check from a different Table Section, this setting is ignored and the POS Operator assumes a new default as the last Table Section from which a guest check was opened. (See NOTE above.) Active. A check mark is required here in order for the POS Operator to be able to log on to the pointof-sale terminal. Cash Drawers. If this operator is using a point-of-sale terminal with two cash drawers, check which drawer should open for the Operator. NOTE: With the February of 2007 release, cash drawer security can be obtained by forcing each drawer attached to a terminal to have a single, Manager assigned, Settlement Operator. The flag is Odyssey/BackOffice Suite Programming Staff Selections 25

26 programmed under POS Terminal Options I/O Devices on the Cash Drawer Tab. If the flag Settlement Operator Required is set true, then the above setting is only used when a Manager causes a drawer to be opened. Fingerprint Access Considerations The Odyssey BackOffice and POS/2100 software support the digitalpersona Fingerprint Reader since the September, 2005 software release. The reader can be used for: User Identification on the BackOffice (future release) Employee Identification for Clock In/Out for Time and Attendance POS Operator Identification This selection is now also available from within the core BackOffice module. This allows Managers, not authorized for any other programming, to use this section without having access to the full Programming module. A fingerprint is registered to an Employee using Button Type Register Fingerprint from the point-of-sale application. You may register multiple fingerprints for an individual employee. For employee identification, you can set the option on the Employee Configuration screen "Fingerprint ONLY Clock In/Out". If this option is NOT set, then employees have the option of either using the Fingerprint Reader or entering the Employee Clock Number. For security reasons, this number would typically NOT be given to employees, however, if a Fingerprint Reader were being used. The number would only be known or accessible to Management as a backup in the event of a failure of the Fingerprint Reader. NOTE: If a Fingerprint Reader is being used for Employee Identification, it is recommended that the option "Fingerprint ONLY Clock In/Out" be set. In the event of failure of ALL Fingerprint Readers, simply change the BackOffice option. For POS Operator Identification, there is no similar option to REQUIRE only a fingerprint. The POS Operator access can be with either a fingerprint or a magnetic card or manual entry of the POS Operator "secret" number. digitalpersona Fingerprint Software Installation The software to interact with the USB Fingerprint reader is installed on each terminal to which a reader will be attached. During the installation you are prompted as follows: "Please create a 16-character Security Key. This key is used to protect your digitalpersona database. You do not need to remember or write down this Key." This is not actually correct. You are given two choices, Create your own Security Key or use the Default Key. We recommend you always use the Default Key. The digitalpersona software used this Security Key when creating entries into the BackOffice database. If a different Security Key is used on different terminals, then the database can only be accessed from the terminal on which the fingerprint was registered. NOTE: Always use the Default Security Key when installing the digitalpersona software. 26 Staff Selections Odyssey/BackOffice Suite Programming

27 User Groups In order to access the Odyssey BackOffice Suite you must log on as a particular User (or Operator) using a unique password. The ability of a particular User to access certain areas of programming, the BackOffice itself, the Reports Module and the Inventory module can be restricted. This restriction is established at the User Group Level. Every individual User must belong to a User Group. However, there is no restriction on the number of User Groups, so each individual User could theoretically have his/her own User Group if this is desired. With the May of 2011 release, the User Group programming has been totally changed. There are now two sections to User Group Programming, both of which display a navigation tree structure. The top section is a selection of the modules: BackOffice (locked) Reports (locked) POS2100 Programming (locked) Inventory The check mark indicates the Group is allowed to access the executable module. No check mark indicates the Groups is blocked from the entire module. Note that no User Group can be entirely locked out of the BackOffice, Reports or Programming. The second section below the first is an exact duplicate of the Outlook Style Navigation tree structure for the selected executable. You can block the User Group from any individual selection by removing the check mark next to the selection. This scheme allows for absolute access control by User Group, and with an unlimited number of User Groups, by User. For an upgrade of existing installations, the User Group Names are retained. However, every single User Group has access to everything. Therefore, immediately after an upgrade, the installer must modify the programming for User Groups. Users This selection defines individual Users of the Odyssey BackOffice Suite. User ID. The Add icon will automatically assign the next sequential User ID. User Name. Enter up to a thirty character name to identify the User. Password. Enter up to a thirty character set of characters to be entered by the User when logging on to the BackOffice Suite. User Group ID. Use the down arrow to access the dropdown list to assign the User to the appropriate User Group. Language. An individual User can have all information displayed in a chosen language. Each and every screen from all of the modules of the Odyssey BackOffice Suite and each and every report can be displayed in a foreign language. A separate utility, the Language Editor, is provided to assist in the translation process. Use of this utility is covered in a separate chapter of this document. The Odyssey BackOffice Suite has been partially translated into Dutch, French and Polish as of the date of this document. In addition, there is a separate language database for English (UK). Odyssey/BackOffice Suite Programming Staff Selections 27

28 Sales Related Selections Product Type Product type is an extremely important concept to review before beginning the entry process of menu items within Odyssey Configuration. There are seven product types within the Odyssey Suite. Odyssey Suite only supports a product type of either a menu/sales item or a purchased item. That means that if you sell an item directly as purchased from a vendor, for example a bottle of wine, it must be entered twice, once as a purchased item and once as a sales item. It also means that if you utilize batch ingredients, which are neither purchased directly nor sold directly, the batch must be entered as a menu, or sales, item. The first product type shown on the Product Type programming form is applicable to all inventory items. The product type is a purchased item, at level 0. It is the level which is significant in conjunction with recipe implementation. The last six product types shown above are all menu/sales items, at levels 1 through 6. The difference is only significant in conjunction with Odyssey Inventory and recipe implementation. This form is made available solely for translation purposes in foreign language countries. Sales Types There are now six Sale Types where there were formerly three. The number of Sales Types is not programmable, is it fixed at six. Sale Type Number. Display only to indicate the selected Sales Type being programmed. Sale Type Name. Enter up to a thirty character name. It is recommended, however, that you use eight or fewer characters since the Sales Type appears at various places where space is at a premium. Active. In the POS2100, there is a button which is used to select a Sales Type from a List. By removing the check mark next to Active, the selected Sales Type will not appear in this list. Also, if a Sales Type Select button relating to the selected Sales Type is depressed, nothing will happen. Manual Desktop Select. This entry is used to automatically switch to a specified Sales Desktop when the Sales Type is selected. This can be extremely useful for applications like phone orders, since there may be more lead through programmed. List File. This is for use with Inventory only. A specified Menu Item can be automatically injected into Transaction Details on a by Sales Type basis. The purpose is to account for items such as bags, plastic dinnerware or disposable plates for the specific Sales Type. Automatic Menu Item. This works in conjunction with the above option and is only applicable for Inventory applications. The Sales Type also affects all calculations based on Itemizers, including tax, discounts and service charges, based on the programming under POS Terminal Options Sale Types. An example would be Eat In, Takeout and Delivery. NOTE: Sales Type 3 is reserved for designating delivery orders. It is used to parse the list of checks presented with Button Type Transfer Delivery Checks. The Sales Type which represents DELIVERY is NOT programmable, it is always Sales Type 3. Transaction Types There are twenty-two Transaction Types. This form is made available solely for translation purposes in foreign language countries. 28 Sales Related Selections Odyssey/BackOffice Suite Programming

29 Reason Codes A selection list of Reason Codes will be displayed on the point-of-sale terminal when a media is used which has the flag Reason Code Required set to a Yes in Media Programming General Tab. Reason Code Number. A unique number to identify the Reason Code text. When the list of Reason Codes is displayed on the point-of-sale, the list will be sorted numerically by this number, allowing the programmer to control the sequence of displayed choices. Reason Code Name. Enter up to sixteen characters, e.g. Wrong Item. Auto Shifts This form provides the ability to describe the six automatic shifts of the system. In actuality, each individual terminal can have six shifts, so depending on the application, there may be many more than six actual shifts. The name you use to describe the automatic shifts will depend on the application. The automatic shifting is programmed under the selection POS Terminal Options Auto Shifts. The names you enter here are the dropdown text when entering the actual configuration information for each individual terminal. Price Levels There are six price levels associated with every menu item. This descriptive text appears on various programming forms and also appears on the bottom of the guest check presentation on the point-of-sale terminal. If you are not implementing multiple price levels, a good choice for Price Level 1 is either Regular or Standard. A standard used throughout the demonstration database is to use Price Level 6 as a $0.00 price so that if a menu item is used as a modifier or condiment, where the price is included in a main item, there is always a no charge price for the item. Department Groups This is merely a name and a number. Department Groups are not used in any reporting from the Odyssey module. This tag is for use with Enterprise Reporting in the U.K. Each Menu Item must belong to a Department Group. Departments Departments, along with Categories, provide a way of grouping menu items together for reporting. Various analytical reports can print only Department totals, or sort menu items on a by-department basis. As noted in the previous section, Departments may be used as Main Groups, with Categories organized as subsets of Departments. This organization is not, however, required. The association of each and every menu item with a Department and a Category allows these two groupings of menu items to be totally independent. Odyssey/MWS allows for 9,999 Departments. The programming for a Department is an identifying number and a name. While the database will store a thirty character name, it is recommended that Department names be limited to approximately twenty-four characters so that the name will print properly on reports. The programming screen for Departments is as follows: Odyssey/BackOffice Suite Programming Sales Related Selections 29

30 Categories Categories are a grouping of menu items used for reporting purposes. Categories may be independent of Departments, or they may be grouped by Department. When grouped by Department, there is significant flexibility built-into the Odyssey Configuration module for making programming changes to all POS Items in all Categories with a particular Department as the main department. There is another reporting feature which is implemented within category, and that is target food cost. This is used in conjunction with Odyssey Inventory, and represents your target recipe cost for all menu items linked to a particular category. Items whose total food cost, including any finished goods waste, exceeds this target food cost will print on several reports within Odyssey Reports in red. The categories established within the Odyssey Suite may also be used to automatically establish List Files of POS Items. All of the programming associated with a POS Item is duplicated on a by-category basis for use in automatically creating POS Items. POS Items are automatically created on a by-category basis, using the defaults established by Category for condiment chains, itemizer status and other entries which distinguish a POS Item from the database element a menu item. The Category Name is used as the default name for the List File. Since these are displayed on the point-of-sale, it is recommended that you use no more than sixteen of the available thirty character descriptors when naming Categories. NOTE: If you are familiar with the PCS/5000 and are using auto created List Files, think of a one-toone correlation between the Categories you create and a PLU file, because this is exactly what the auto created List Files will be. Categories and Departments can be totally separate, or you can organize your database with Categories as a subset of Departments. As a general rule, Departments are for main groupings, such as Food, Beverage, Liquor/Beer/Wine and Miscellaneous. Categories can either be totally independent or organized under a Department. The default database contains the four listed departments. NOTE: If you are organizing Categories as subsets of Departments, you should skip ahead and first program your Departments before continuing with Categories. This kind of organization makes changing POS parameters such as tax and routing status extremely simple, since all POS Items which belong to a certain Category can be changed at once, and all Categories which belong to a certain Department can be selected. Refer to the section Media Programming Selection Methods, on adding a new Category or programming multiple Categories simultaneously. If Categories are organized as subsets of Departments, the dropdown at the top of the screen is a useful method for displaying only those Categories which are associated with the selected Main Department. This is particularly useful when you are using the Category programming screen to change the parameter programming for POS Items. Categories General Tab Category Number. Enter an identifying number for the Category between 1 and Category numbers are restricted to four digits because of the auto creation of List Files built into 30 Sales Related Selections Odyssey/BackOffice Suite Programming

31 Odyssey/MWS. Auto created List Files begin at 10000, and use the Category Number as the least significant four digits. Category Name. Enter up to thirty characters to describe the Category. As a general rule, in order to view the entire Category Name on various reports, Category Names should be restricted to around twenty-four characters. Since the Category Name also becomes the name for any auto created List Files, you may want to consider limiting Category Names to sixteen characters as a matter of practice. Main Department. If you wish to associate this Category with a Main Department, use the dropdown to select the appropriate Department. Highlighting the window and depressing Delete will leave the Category unassociated. Target Food Cost. Enter the appropriate percentage Target Food Cost for this Category. Certain reports will highlight the food cost percentage in red when the cost for either a recipe or all costs for a period exceed this entered percentage. Allow Repeat. This relates to POS Item programming and is more fully covered in the section on POS Item Programming. Condiment Chain Link. This relates to POS Item programming and is more fully covered in the sections Condiment Chain Programming and POS Item Programming. PLU / CMT Link. This relates to POS Item programming and is more fully covered in the section POS Item Programming. Suggestive Sell Group. Refer to the section under Sales Related Suggestive Selling Definitions for an in depth discussion of this functionality. Categories Applying POS Item Related Programming Changes If menu items are programmed to be auto created, then the settings established here will be used as the default for all items in the List File which corresponds to the Category itself. When menu items are set to auto create POS Items, there is a one to one correspondence between the List File and the Category. Even if POS Items are NOT auto created, changing these POS related parameters from the Category screen is often a faster method of changing the parameters on a by-list File basis. When a change is made to the POS Item related programming area under the Category programming screen, you will see the following window displayed: The three displayed choices are mutually exclusive. Only one line may be checked. Only New Auto Created Items. A check in this box indicates that the changes will not be applied to any existing POS Items which correspond to menu items associated with this Category. The changes will be used as the default for any new POS Items which are auto created. All Current Auto Created Items. A check in this box indicates that the changes will be applied to all existing POS Items which correspond to menu items associated with this Category which are in auto created List Files. All Items, All Lists. A check in this box indicates that the changes will be applied to all existing POS Items which correspond to menu items associated with this Category, whether they have been auto created or manually created. Odyssey/BackOffice Suite Programming Sales Related Selections 31

32 Categories Pricing Tab This tab, like all tabs on the Category programming screen except the General Tab, relates to POS Item programming. A complete discussion of this programming is included under the Pricing Tab for Sales List Files POS Item Programming. If menu items are programmed to be auto created, then the settings established here will be used as the default for all items in the List File which corresponds to the Category itself. When menu items are set to auto create POS Items, there is a one to one correspondence between the List File and the Category. Even if POS Items are NOT auto created, changing these POS related parameters from the Category screen is often a faster method of changing the parameters on a by-list File basis. Categories Display/Print Tab This tab, like all tabs on the Category programming screen except the General Tab, relates to POS Item programming. A complete discussion of this programming is included under the Display/Print Tab for Sales List Files POS Item Programming. If menu items are programmed to be auto created, then the settings established here will be used as the default for all items in the List File which corresponds to the Category itself. When menu items are set to auto create POS Items, there is a one to one correspondence between the List File and the Category. Even if POS Items are NOT auto created, changing these POS related parameters from the Category screen is often a faster method of changing the parameters on a by-list File basis. Categories Flags Tab This tab, like all tabs on the Category programming screen except the General Tab, relates to POS Item programming. A complete discussion of this programming is included under the Flags Tab for Sales List Files POS Item Programming. If menu items are programmed to be auto created, then the settings established here will be used as the default for all items in the List File which corresponds to the Category itself. When menu items are set to auto create POS Items, there is a one to one correspondence between the List File and the Category. Even if POS Items are NOT auto created, changing these POS related parameters from the Category screen is often a faster method of changing the parameters on a by-list File basis. Categories Itemizers Tab This tab, like all tabs on the Category programming screen except the General Tab, relates to POS Item programming. A complete discussion of this programming is included under the Itemizers Tab for Sales List Files POS Item Programming. If menu items are programmed to be auto created, then the settings established here will be used as the default for all items in the List File which corresponds to the Category itself. When menu items are set to auto create POS Items, there is a one to one correspondence between the List File and the Category. Even if POS Items are NOT auto created, changing these POS related parameters from the Category screen is often a faster method of changing the parameters on a by-list File basis. Menu Items A menu item is something with a recipe. It can also be used, depending upon its product type level, within the recipe of another menu item. A menu item does not necessarily correspond to something which is entered at the point-of-sale. For instance, chili batch would be entered as a menu item in order to include a portion of the batch in various recipes and through this connection, deplete the inventory items which comprise the menu item chili batch. 32 Sales Related Selections Odyssey/BackOffice Suite Programming

33 A menu item may also exist in several different forms within the point-of-sale module. Depending on the use at the point-of-sale, the same menu item may cause a different selection window to appear, may have a different set of itemizer association characteristics (for taxability or discountability) or may have a different standard price. For instance, a small coke which costs $1.00 when purchased separately may have no charge when selected as a part of a combo meal. Menu items appear at the point-of-sale as POS Items. A POS Item is an element of a List File, part of List File Details. Menu items must belong to an existing category, an existing department and be one of the existing six product types. In addition, there are six possible sales prices associated with each menu item. This is fixed within the Odyssey Suite. Menu Items Selection Methods Like the selection method applicable within POS Terminal Options, once you have created multiple menu items, you can change the programming on a selected group at one time. The dropdown at the top of the screen allows for filtering on a by-category basis and also allows for the display of either all programmed menu items or only those which are currently active. A screenshot of the Menu Item Programming screen is shown below. The view shown below is the Form view of the Menu Item Programming Screen. The icon which appears as the third from the right will change the form to a Table view, which is particularly useful when changing pricing on multiple menu items simultaneously. Once you have added a menu item to a particular Category, if you have the cursor on the left of the screen, under either Menu Item Number or Menu Item Name, the new menu item will inherit all of the properties of the existing menu item, except the Menu Item Number and Menu Item Name. Menu Item Number. This is actually an alphanumeric entry. Enter up to sixteen characters of text. The software will not allow the entry of a duplicate Menu Item Number. For scanned entries, see the flag Scannable below. For scannable menu items, place the cursor in the Menu Item Number entry field and scan the item. The Scannable flag will automatically set to true with a check in the box. Menu Items and Inventory Items are stored in the same table in the Odyssey database. Therefore you can NOT have a Menu Item Number which is the same as the Product Number of an Inventory Item. Since it is a text field, you can use any convention you desire, i.e. all Menu Items Numbers begin with M and all Product Numbers for all inventory items begin with an I. Menu Item Name. This is a thirty character text entry field. The text entered here, however, is used as the default entry for all POS Items. Generally, there will only be room for approximately sixteen to twenty characters on most buttons on the point-of-sale and on the guest check, both displayed and printed. Odyssey/BackOffice Suite Programming Sales Related Selections 33

34 Remember that you can use both inventory items and menu items in the recipe for a menu item. When you are entering the recipe, the easiest way to add a recipe line item will be to use a dropdown list of names. Both inventory items and available inventory items will appear on this dropdown, so try not to use the exact same name for a menu item as you will use for an inventory item. If you have followed the inventory item Product Number/menu item Menu Item Number convention above, even if you select the wrong one when entering a recipe, the Recipe Item Number will allow you to distinguish. Product Type. This selection relates to inventory and recipes. A sales item can only include in its recipe a product, either an inventory item or a sales item, which is at a lower level. Therefore, a level 1 sales item can only include inventory items in its recipe. A small coke or medium french fries are examples of typical level 1 sales items. A level 2 sales item can include both inventory items and any level 1 sales items in its recipe, and so on up to a level 6 sales item which can include any inventory item or sales item in its recipe other than another level 6 sales item. If you are planning on implementing Odyssey Inventory, you must have a reasonable handle on recipes prior to entering any menu items, even though you can create a menu item separately from entering the recipe. For instance, while a small coke is clearly a level 1 sales item, a hamburger is more likely a level 2 sales item. Its recipe would generally include a bun and a patty which are both inventory items, but for ease of recipe entry, its recipe might also include burger condiments. Burger condiments would be a list of the standard prep quantities of ketchup, mustard, onions, lettuce, etc. that are placed on all burger menu items. In this example, burger condiments would be entered as a sales item, in order to be included in a recipe, even though you might not have a direct entry on the point-of-sale terminal for this item. Therefore, if the recipe for a hamburger is to include the bun, the patty and burger condiments, the hamburger must be at least a level 2 product type or higher. If you are not implementing inventory, you should simply place every menu item at Level 2. Stock Type. The Stock Type is only used in multi-location inventory applications. The Stock Type associates the sales of the menu item with a particular Stock Control Area when generating a Period Cost of Sales report on a by-stock Control Area basis. This association is also on a by-revenue Center basis. Auto Create POS Item. A check mark here will cause the software to include this menu item in the automatically created List File which corresponds to the selected Category for the menu item. DO NOT PLACE A CHECK HERE FOR EITHER SCANNABLE OR RANDOM WEIGHT BARCODE ITEMS. Scannable. If the application will scan items at the point-of-sale, then generally the Menu Item Number will have been scanned and this box will have been checked. If you have manually entered the product number corresponding to the UPC code, you must manually check this box for scanned items. DO NOT check Auto Create POS Item for scannable items. They will automatically be created in a separate List File and really do not belong in an Auto Created List File by-category. NOTE: The Odyssey software interacts with a keyboard wedge type scanner. The leading character sent by the scanner should be programmed as a tilde ( ~ ) character and the trailing character should be programmed as a CR/LF. Most scanners program by scanning bar codes which are included in the documentation provided with the scanner. Random Weight Barcode Item. If this is an item which will be weighed, them marked with a scale equipped with a printer which generates a Random Weight Barcode, place a check here. Items will be automatically created DO NOT check Auto Create POS Item for Random Weight Barcode items. They will automatically be created in a separate List File and really do not belong in an Auto Created List File by-category. Program all prices as $0.00. Avg. Sold Per Day. This selection is for use with the Order Wizard for new items. It allows the Wizard to project use with no history. The entry can be changed from the Order Wizard screen. Date of Debut. Enter the first date this Menu Item should be Active. This selection is also for use with the Order Wizard for new items. Inventory purchases for items with a Date of Debut during the projection period will use the above quantity for projection of inventory usage. For a date after the 34 Sales Related Selections Odyssey/BackOffice Suite Programming

35 current Sales Day, the software will automatically unset the Menu Item Active flag when the form is closed and then set the Menu Item Active flag when the Sales Day equals the Date of Debut. Active. NO check mark here prevents this menu item from being purchased at the point-of-sale. Date Inactive. Enter the date when this item was made, or will be made, inactive. For a date after the current Sales Day, the software will automatically unset the Menu Item Active flag on this date. Category. Use the dropdown list to associate this menu item with a Category. Department. Use the dropdown list to associate this menu item with a Department. Sales Unit. The sales unit for all menu items should be Serving. Pricing. There is a check box at the right of Price Level 1 for the menu item. A check will cause any price entered as Price Level 1 to be automatically copied to the other five prices. The following section covers menu item pricing in greater detail. Included VAT. For U.S. installations, leave this entry at the default of 0.00%. This entry is used in the Recipe Costing reports where the recipe cost is reflected as a percentage of the selling price less normal VAT, rather than just the selling price. If VAT is applicable, enter the normal VAT which is applied to this menu item, when it is sold as a POS Item. Refer to the discussion in the section Store Configuration Miscellaneous Tab on the ISO Country Code for enabling the VAT reporting functionality of certain reports. Menu Items Pricing and Price Levels The names for the Price Levels which are displayed on the Menu Item Programming screen are those that are entered under the selection Sales Price Levels. Each menu item can have six different prices. This includes a price of $.00. The price charged for the menu item, as a POS Item at the point-of-sale, depends on the active Price Level at the point-of-sale. What you are entering here is every possible price that could be charged for this specific menu item, or recipe. Once a POS Item is associated with a menu item, there is another layer of programming which associates one of these six possible prices with a price to charge, at the point-of-sale, at a particular Price Level. There is a handy tool for quickly changing prices of multiple menu items simultaneously. The right most icons are provided for this purpose. The third icon from the right is Active when Menu Item programming is displayed in Form view. This icon can be used to change the display mode to Table view. Once in Table view, the second icon from the right becomes Active and is used to change the display mode back to Form view. The Table view of the Menu Item Programming screen is shown below in a screen shot, with all menu items belonging to the Appetizer Category highlighted. The Price Change icon is the right most icon on the screenshot below. Odyssey/BackOffice Suite Programming Sales Related Selections 35

36 The Price Change icon is accessible from either view, but is particularly useful in Table View because only the pricing is shown in this view. The screenshot below shows the tool which is displayed when you left click on the Price Change icon. As the banner display indicates, before clicking on the Price Change icon, you should select all items whose pricing you wish to affect. Use the small gray box at the top left of the menu item listing to select all (as shown in the previous screen shot) or left click on the gray box to the left of individual menu items to highlight the entire row in blue. This is the same selection methodology outlined in the section on POS Terminal Options Selection Methods. Change Price By. Enter a positive, or negative in the case of price reduction, figure by which you wish to change all selected menu items. Include Zero Priced Items. Generally at least one of the six prices for each menu item will be $.00, in case the menu item is ever in a Popup window of modifiers which are included with a previous selection. Click this box if you wish to leave all prices which are $.00 as they are, and not affect those by the price increase/decrease. Valid Prices. Place a check mark in each of the six price levels you wish to affect. Note that if the price at any of these price levels is $.00, and you do not have a check mark in the above box, these prices will not be affected. Click on OK. All selected prices, for all selected menu items will be updated. The following screen shot illustrates the after of clicking on OK for the selected menu items in the Appetizer Category. Note that all prices which were $.00 remain at $.00 and that all other prices have been increased by the selected amount of $.50. To revert back, use the same process but enter -.50 in the Change Price By entry. You will note that after you enter the -.50, the next time you click on the Price Change icon, the Change Price By entry window will show (.50) as the negative number. 36 Sales Related Selections Odyssey/BackOffice Suite Programming

37 Menu Items Deleting/Making Inactive The software will not allow you to delete a menu item once the item has been sold. If you highlight a row and click on the Delete icon, the software will prompt: If you no longer wish to sell this menu item, simply make it Inactive by placing a check mark in the Inactive box on the Menu Item Programming screen and enter the current Sales Day as the Date Inactive. Random Weight Barcode Items A menu item with a check mark as a Random Weight Barcode Item will have an entry automatically created in List File These items will have been weighed and marked with a barcode label which contains a Menu Item Number and a price based on the extension of the weight and the price per pound. Neither the price per pound nor the weight is included in the barcode, only the price to charge for the weighed item. These items must be entered as a six (6) digit, numeric only number beginning with a 2. (Actual barcode is a 12 digit number) Most random weight barcodes will only include a four digit (maximum $99.99) price. There is additional programming related to Random Weight Barcode Items under POS System Options Miscellaneous Options. Some barcode printers will encode a leading zero before the digit two (2). (Actual barcode is then a 13 digit number) In addition, some barcode printers (and scales) will utilize a five (5) digit price. Of course, all scales and associated printers in a particular location must produce identical barcodes. Sales Item (Menu Item) Pricing This selection allows for the entry of future pricing for the six prices of menu items. The prices are automatically entered during the end-of-day process where the date selected is equal to or greater than the date entered on this screen as the Start Date. While there is some value to this screen as an entry form, the primary use of the database tables which are fed from this form, and the future pricing functionality itself, is when the store is connected to a central site which is sending pricing information electronically. List Files This screen is where menu items are associated with POS Items. There are two types of List Files, designated as PLU and DCM files. The PLU type are main items at the point-of-sale. The DCM type are used to modify the PLU type items, either by being part of a Popup Window or configured as a Preset button on a Sales Desktop. A List File can be accessed as a Popup window on the Odyssey POS/2100. In addition, an item within a List File may be placed as a preset button on a Sales Desktop of the point-of-sale. NOTE: List Files are the methodology by which menu items are purchased at the point-of-sale. Even if you have created a menu item, it can not be entered at the point-of-sale unless it exists as a List Detail item (POS Item) within a List File. A menu item may exist in many different List Files. The programming performed under Menu Item Programming provided a Category and Department association, along with six possible prices. The programming under List Files provides information such as printer routing, which of the six prices to charge when the point-of-sale is at a particular price level and the status relating to taxability and discountability. Odyssey/BackOffice Suite Programming Sales Related Selections 37

38 List Files Auto Created List Files List Files may be automatically created based on the Category association of the menu item. For all menu items which a check in the box Auto Create POS Item, there will be a single instance of a POS Item in a PLU type List File. The auto List File numbers will begin at 10,001 and continue sequentially, skipping any existing List File Numbers. Usually, for consecutively numbered categories, Category 1 will have List File Number and so on. The POS Item parameters will have been initialized by the programming established under Categories. The Odyssey software WILL NOT automatically create any DCM type List Files. In many instances it is extremely helpful to allow the software to automatically create List Files, then pick and choose various menu items from these already created List Files during the process of configuring your Popup Windows the way you want them. The Add New With Details icon is extremely useful. Deleting Auto Created List Files and POS Items in Auto Created List Files The auto-creation process is initiated each time the Menu Item Programming form is closed and each time the List Files Programming form is closed. If the check mark under Menu Item Programming for a particular menu item remains checked, a deleted POS Item in an Auto Created List File will be automatically recreated as soon as you delete it. If you wish to remove an item from an Auto Created List File, or to delete/get rid of one or all Auto Created List Files, you must first remove the check mark on the menu item under Auto Create POS Item. Removing this check WILL NOT remove the item from the Auto Created List File. It will merely stop the POS Item from being automatically created when the form is closed. You can highlight ALL menu items from the Menu Item Programming form, or highlight all menu items in the Category whose corresponding Auto Created List File you wish to delete, uncheck the box Auto Create POS Item, then click on the Save icon. Next you would proceed to the List File Programming form and delete items or List Files as you choose. List File of Scannable Items When an item is designated as Scannable from the Menu Item Programming screen, it is automatically Auto Created. List File Number is reserved to contain all scannable items. The POS Item programming parameters which are used when the scannable POS Items are automatically created are the ones from the Category with which the menu item is associated. You can manually change any of these parameters for individual POS Items from the List Files Details screen, or you can change these parameters using the form under Category programming. List File can be placed as a Popup window on a Sales Desktop as a backup in the event of a scanner failure, however, depending on the number of scannable items, this will produce a rather lengthy list. The process of automatically creating this special List File is intended to automate the process of creating scannable items at the point-of-sale as much as possible. List File Programming Adding New List Files The screenshot below shows the presentation of the General Tab under List File Programming. When you click the Add icon, the entries on the General Tab for the new List File will be identical to the existing List File which was selected on the left of the screen. The filtering window provides a dropdown to display either All List Files or to select either PLU or DCM type List Files. The Add New With Details icon is the second from the left on the screen. As an example of its use, suppose you had an already Auto Created List File of small drinks, corresponding to a Category. Since this List File was automatically created, it will be a PLU type. We want these same menu items in another List File to use within a popup sequence when certain menu items are purchased at the point-of-sale. To create the DCM type List File, left click on the gray box to the left of the Small Drink PLU List File. Next left click on the Add New With Details icon. Enter an appropriate name on the General Tab and change the List File Type to DCM. All of the items from the existing PLU file now exist in a second List File. The only detail left is changing the pricing for the DCM file, probably to be at no charge. 38 Sales Related Selections Odyssey/BackOffice Suite Programming

39 Building a List File is a three step process. First you create the List File itself. This is done from the General Tab under List File Programming. Second you add menu items to the List File. This is done from the List Details Tab under List File Programming. Third, you configure the POS parameters of the POS Items (the List Details) for proper operation at the point-of-sale. This is done from a subset programming area of List Details. It is accessed by clicking on the blue text banner at the top of the List File Programming screen. It replaces the list of List Files on the left with a list of List Details (POS Items). List File Programming General Tab The icons at the top left of the screen are the Add icon, the Add New With Details icon, the Undo icon, the Save icon and the Delete icon. List Files may only be deleted one at a time. List File Number. Enter a number from 1 to List File Numbers greater than are reserved for auto created List Files. The software will automatically suggest a number as the next sequential number after the highest number already existing which is under This is merely an identifying number for the database and does not relate in any way to point-of-sale functionality. List File Name. This field will accommodate as many as thirty characters. However, it suggested that you keep this entry to less than sixteen characters because the field is displayed in the banner at the top of the Popup window at the point-of-sale when the list is displayed. List Files which are auto created may have this entry changed, and the software will not change the name during the autocreation process. List File Type. Select PLU type for main items, those which can be purchased by themselves. Select DCM type for lists which will hold menu items used as modifiers to main items. Sort Type. This entry defines the way items are displayed on the Popup Window. If you wish to define the order, select Numerical. The items will then display in the order you define when you assign a number to the POS Item under List Details programming. Select and Stay. This setting defines the operation of the Popup window at the point-of-sale. With a check mark in this box, once the Popup window is displayed, it remains displayed until dismissed by touching the banner at the top of the Popup. With no check mark, the box disappears after a single item is depressed. Of course, if the item depressed has following lead through windows, these are displayed. For DCM type List Files there is an alternative method of placing a Popup on a Sales Desktop on the point-of-sale. A later section defines Condiment Chain programming and this defines in further detail the operation of a Popup window when it is displayed. You can place either a Condiment Popup on a Sales Desktop or a Chain Popup. Number of Selections. This setting only pertains if Select and Stay is true. It allows you to limit the number of selections made. A setting of 0 allows unlimited. If this is a condiment file, and used in a condiment chain, this setting will be ignored. There is a layer within condiment chain programming to handle the number of selections on various popup windows. Odyssey/BackOffice Suite Programming Sales Related Selections 39

40 Use Global Clear Banner Text. The top button on a popup window acts as a Clear button to dismiss the popup. Normally the list file name is displayed in this button. With a check box here, the descriptor programmed as entry 894 in the POS Application will appear. The default is "Touch HERE To Clear". Use Global Clear All Banner Text. This entry is primarily for kiosk implementation and only pertains to condiment files. Touching an Error Correct button during the middle of a lead-through condiment chain sequence error corrects the original menu item and all entered condiments. Essentially it "starts over". By placing a check in this box, when the condiment window popup is displayed there will be two buttons at the top of the popup. The second, bottom, button will function identically to an Error Correct button. The text displayed will be the descriptor programmed as entry 895 in the POS Application. The default is "Start Item All Over". List File Unique By Store. This flag only pertains in multi-store situations. Normally, do NOT check this flag. When checked, the POS Item flag Display in Window is controlled on a store-by-store basis,, through the programming performed under the List Files By Store selection, immediately beneath the List Files selection on the dropdown list. When you are finished defining the List File, click on the Save icon. List File Programming Adding List Details (POS Items) List Details are the individual POS Items. Adding List Details is the second step in creating List Files. You can also delete a List Detail item (POS Item) by highlighting the row in blue then clicking on the Delete icon. List Details may only be deleted one at a time. For deleting POS Items in an auto created List File, refer to the previous section. Note that each time you access the List Detail Tab under List File Programming that all the numbers are even increments of 10. The software automatically renumbers each and every POS Item within each List File when the List Files Programming screen is closed. This is a significant programmer s aid if you are displaying the List File numerically, since it always leaves room for inserting new POS Items in their proper sequence between existing POS Items. To add POS Items as List Details to a List File, click on the Add icon. When you do, a new programming aid will appear, as shown in the screenshot below. A selection criteria is available at the top of this window which will display only menu items from a selected Category, or all menu items. The second selection criteria allows you to display only active menu items or active and inactive menu items. A menu item which is inactive may still be placed within a List File. It will not, however, be accessible on the point-of-sale terminal. It will simply not appear in the Popup window. You may add all displayed items by left clicking in the gray box to the left of the # sign on the top banner. To add selected items, left click on the gray box to the left of the menu item number to highlight the row(s) in blue. If you are putting together a List File which you want to sort numerically, the assigned numbers on the List Details Tab will correspond to the order in which you highlighted the menu items. The price which is displayed is for reference only and it the price programmed as the Level 1 price in menu item programming. Click on Ok when you have selected all menu items which you wish to appear as List Details in the selected List File. 40 Sales Related Selections Odyssey/BackOffice Suite Programming

41 When you return to the List Details Tab, all selected menu items will appear as List Details for the List File. Each will have been assigned a number automatically, in increments of 10. If you wish to display items from this List File in a predetermined order on the point-of-sale, you should modify this number to sort the items in the appropriate order. You can left click on the number at the top of the list on the List Details Tab to resort the display. List File Programming Configuring POS Parameters of List Details This is the screen where the POS parameters of items in the List File are configured. The tabs which are displayed in this section are identical to the tabs in the Category section. You will note that when you first enter this area of programming, that each and every POS Item already has settings which correspond to the default assignments determined in Category programming. To access the configuration screens for POS Items, click on the banner at the top of the List Files Programming screen, where the name of the List File appears in blue text. When you do, you will see a display identical to the screenshot below, but listing the existing POS Items already in the selected List File. Like many of the other screens within the programming module, POS Items may be programmed individually or in bulk. To change the programming for all POS Items in a List File, left click in the gray box to the left of the banner display Record # on the far left of the screen. All POS Items will be highlighted in blue. To select individual POS Items, left click in the gray box to the left of the line containing the POS Item to highlight the line in blue. Elements of programming which MAY NOT be programmed in bulk (like the POS Item name) will appear in light gray when multiple POS Items are highlighted. The name for a POS Item does not have to be the same as the Menu Item name, although when initially creating POS Items the names will be identical. The display at the far left of the POS Item Programming scre en will ALWAYS show the Menu Item name for reference. From th e POS Item Programming screen there are two ways to return to the List Files programming screen. Either click the name of the List File displayed in blue in the banner at the top (the same way you got to this screen in the first place) or click the X at the top right of the screen. Either will close the POS Item Programming screen and return to the List File Programming screen. POS Item Programming General Tab Active. Do not check or uncheck this box. This is a reference-only flag and is identical to the Active setting on the corresponding menu item. If the menu item is active, and you uncheck this box, the software will automatically re-check it when the List Files Programming screen is dismissed. Menu Item Name. This is for reference only and shows the name of the menu item to which this POS Item corresponds. POS Item Line 1. This is a 30 character field. When this item is displayed in a Popup window, there are three lines on each button. The first two lines display POS Item Line 1 and POS Item Line 2. The third line displays the price for the item corresponding to the selected Price Level on the point-of-sale terminal. You will note that the Odyssey software attempts to separate Menu Item Names into two distinct parts by placing part of the text on POS Item Line 1 and POS Item Line 2. On the guest Odyssey/BackOffice Suite Programming Sales Related Selections 41

42 check area of the point-of-sale terminal, these two lines are combined and as much text as can display will display. NOTE: The text in ALL displayed buttons on a Popup Window is determined by the longest text in ANY individual button. A SINGLE long line of text for an individual POS Item can cause the text to become too small to read for ALL buttons. You should try and keep each line to no more than approximately 12 characters. POS Item Line 2. This is a 30 character field. This is the text on the second line of a button on a Popup window which is displayed for this POS Item. You can separate the text in any way you desire and enter any text you desire. NOTE: When a POS Item is placed directly on a Sales Desktop as a Preset button, the text is part of the button itself and can be different than either the Menu Item Name or POS Item Line 1 or POS Item Line 2. Printer Line 1. This is a 30 character field. There are multiple uses for the two lines of print. Which lines actually print on the guest check and on requisition chits is determined by the programming entered under the selection Printer Configuration Printer Definitions. In the most simple of examples, only line 1 prints. However, since this is a 30 character text field and with bold print you can only fit 20 characters on a single line, there is another setting in under Printer Configuration Terminal Print Options under the Remote Tab pertaining to print on the requisition printer, Truncate Menu Item Print. This is somewhat of a misnomer, since it actually pertains to POS Items. With Truncate checked, only as much text as will fit on a single line is printed. With Truncate unchecked, the description will continue on a second line. One use of the two printer lines is for foreign language text. Printer Line 2 would contain a foreign language description of the item. Another use is simply for items which require a great deal of information, such as a bottle of wine which may need a bin #, a year, etc. Printer Line 2. This is a 30 character field. Note that by default, nothing is placed here by the Odyssey software. Even if you set the flag in Printer Configuration Printer Definitions to print two lines of text, if Printer Line 2 is empty you will NOT see an empty or blank line. So if you only have certain items which require clarifying text, you can enter information as appropriate only for those POS Items which require this clarifying text. By printing two lines, and leaving the Truncate flag unchecked, you can actually cause 60 characters of text to print on a requisition chit pertaining to a POS Item. Allow Repeat. This is a Yes/No field which pertains to the operation of the Repeat button on a Desktop of the point-of-sale terminal. If this box is NOT checked, the software will ignore a depression of the Repeat button when this item is selected. Often this is useful if your primary use of the Repeat button is for rounds of drinks. Only drink items would then have Allow Repeat set as true. However, the Repeat button is also extremely useful in duplicating complicated entry main items, those with several Popup windows of description. Category. This field is for reference and reflects the Category association of the menu item to which this POS Item corresponds. Department. This field is for reference and reflects the Category association of the menu item to which this POS Item corresponds. Condiment Chain. A condiment chain is a way of causing multiple Popup windows to appear after this POS Item is selected. However, in order to create a condiment chain you must first create multiple DCM type List Files, then you must group them together into a Condiment Chain. This entry will be changed later, once you have actually created condiment chains. Note, however, that if all the POS Items in a List File will use the same condiment chain this entry may be bulk programmed across several, or all, POS Items. 42 Sales Related Selections Odyssey/BackOffice Suite Programming

43 NOTE: This is a drop down selection, and there is no selection No Chain. If you have previously entered a Condiment Chain and want none, highlight the name in the Condiment Chain window and depress the Delete key on your keyboard. PLU/CMT Link. This entry provides a method for only allowing condiments to be associated with certain menu items. There is a similar entry to be programmed when entering Condiments. The programmer must determine, before beginning programming, if this is a desired feature. If this menu item should have restricted condiment access, enter the same number that you will enter when programming the Condiments which can modify this menu item. Examples of the use of this feature are small toppings only on small pizza, "on the rocks" only on bar items. Another option has to do with "fixed meals", where certain condiment files are only used in conjunction with a meal served at a fixed price. In this use, the entries programmed as "condiments" in these DCM type List Files, are actually menu items, and not prep instructions. The price entered for such a condiment is generally $.00, since the price of the fixed meal is entered with the entry of the menu item itself. You will want to restrict the use of such condiment files to prevent operators from requisitioning normally priced items at no charge. The default entry for all POS Items is 0 for this field. NOTE: If you enter a 99 for a POS Item in a PLU file, it will be able to be modified by any POS Item in a DCM file, regardless of the entry in the PLU/CMT Link for the condiment. Likewise, if you enter a 99 for a POS Item in a DCM file, it will be able to modify any POS Item in a PLU file, regardless of the entry in the PLU/CMT Link for the main item. Suggestive Sell Group. Generally this will be programmed on a Category basis, however, it can be set on an individual POS Item basis. Refer to the section under Sales Related Suggestive Selling Definitions for an in depth discussion of this functionality. POS Item Programming Pricing Tab This tab is used to determine which of the six prices associated with a menu item are actually charged when this POS Item is used. The price is a function of which of the six price levels is active on the point-of-sale terminal. You will notice that just because the point-of-sale terminal is on Price Level 2, that does not mean that the second price level for the menu item is charged for this instance of the menu item as a POS Item. The following screen shot displays a DCM List File which is always used as part of a Popup window lead through in a condiment chain sequence. Odyssey/BackOffice Suite Programming Sales Related Selections 43

44 The six lines labeled POS Price 1 through POS Price 6 refer to the six price levels which may be active on any given point-of-sale terminal. Note that regardless of the active price level of the terminal, when Carrot Cake as a POS Item in THIS List File is entered, Price 6 from Menu Item Programming will always be charged. The names which display on the bottom half of the screen are the ones entered under Sales Price Levels. Price Levels. Leave this entry at its default value of 6. Prompt For Price. This entry allows you to create an Open Entry amount button on the point-of- for sale. Such a POS Item would be associated with a menu item called Open Food, with no recipe. The flag is ONLY evaluated if the POS Price is associated with a menu item price which is $0.00. POS Price Levels. This is where you determine which of the six menu item prices will be charged this POS Item at the six POS Price Levels. Distribute Pricing. This option pertains only to a priced PLU item with modifying condiments. The idea is for the BackOffice to get proper revenue associated with items rung up at the POS as "free" like coke, fries, etc. If this flag is set, 1 - there must be at least one condiment. 2 - the sum of all Price Level 5 prices for the main item and all condiments must be >= what is being charged the customer. If so, then 1 - set the denominator of distribution as the sum of all P5 prices. For each item, take the item P5 divided by the denominator times the price being charged. For things like "Upsize" which have a price in P1, make the P5 price.00. For things like Hamburger Combo, with the same recipe as Hamburger but a higher price in P1, set the P5 prices the same for both. Example: Take a $5.00 hamburger combo, selected as Upsize for an extra $0.75 with a large coke and large fries (with both the large coke and large fries at $0.00 in P6 used at all price levels). The price charged the customer is therefore $5.75. If distribute pricing were not set, the main item of "hamburger combo" would get revenue of $5.00, the fictitious menu item Upsize would get revenue of $0.75 and both large fries and large coke would get revenue of $0.00. Not really very fair to the fry cook. Assume a P5 for hamburger combo of $4.00 which is also the P1 price for a hamburger. With inventory enabled, the recipe for the menu item hamburger would be the same as the recipe for the menu item hamburger combo, given the way the combo is being rung up at the POS. Assume P1 and P5 for large coke and for large fries is $1.50. It is the P6 price of $0.00 which is being used in the hamburger combo. So if a hamburger and two large condiments were bought separately, the customer price would be $ $ $1.50 or $7.00. A good deal on the "hamburger combo" then. Since P5 for Upsize is $0.00, the sum of all P5 prices is 7 and therefore 7 is the denominator of distribution. We send to the BackOffice for the hamburger combo (4/7) * $ 5.75 = $3.29. Note this is a little less than a normal hamburger at $4.00. For both the large condiments, we send (1.5/7) * $5.75 = $1.23. Note this is also a little less than a normal large fries or large coke. We send to the BackOffice for Upsize (0/7) * 5.75 = $0.00. This is as it should be, since Upsize is not really a menu item but a vehicle for pricing. The total sen t to the BackOffice matches what is charged the customer, $5.75. What the Distribute Pricing flag has done is to allocate, for analytical purposes, the revenue received from the customer among all of the real menu items. Menu Item Prices. This section is for a programmer s reference and merely displays the values entered for each of the six prices for the menu item to which this POS Item corresponds. Note that the name for Price 6 for ALL menu items is 6-Included, and by convention, the demonstration database has a price of $0.00 entered for every menu item on the sixth price. POS Item Programming Display/Print Tab Remote Printer Groups. Enter the Output Printer Group number(s) corresponding to a list of remote printer(s) and/or Order Video(s) where this item is to print when the guest check is serviced. These assignments will have been defined in POS Terminal Options Sales Types/Output Groups. Entering more than one group is generally only used for an "expediter" printer. There are two ways of implementing an "expediter" printer. One is to define one of your eight groups as the "expediter" group, enter the printer designation of the printer when programming printer assignments into Output Groups, and program each and every item which should print on the expediter printer with two groups, the "normal" requisition group and the "expediter" group. The second, and probably easier way, is to enter the expediter printer designation as the second line in each and every group. The 44 Sales Related Selections Odyssey/BackOffice Suite Programming

45 difference is that if you designate a group as the "expediter" group, you will print one "chit" for the entire transaction on the printer. If you enter the printer as the second line in every group, you will duplicate the chit from each group, creating multiple chits per transaction, on the expediter printer. Video Color ( 0 to 15 ). This entry is only applicable if you have Order Video screens in your installation. The default entry here is a 0. With a 0 setting here for the POS Item, the setting in the RQV.INI file determines the color for PLU type and DCM type POS Items. If you wish to have different PLU type and/or DCM type POS Items print in different colors, enter the color number here. The colors are illustrated in the section RQV.INI Color Selections. Print Sequence. This setting gives the programmer total control over the order in which both PLU type POS Items and DCM type POS Items will print on the requisition printers and display on the Order Video screens. The valid sequences are 0 through 12. The sorting is first by PLU type POS Item, with sequence numbers 0 first, then 1, then 2, etc. Underneath the PLU type POS Item, DCM type POS Items (condiments) are also sorted in the same order. If items all have the same print sequence number, the print and display is in the order entered on the point of sale. Print In Red. A check mark here will cause the software to output the text to the selected printer using the character codes defined under Printer Configuration on the Printer Types Roll Printer Tab. This may correspond to red print, or may be inverse print on thermal printers. NO TE : For POS Items in type DCM List Files, this flag may not be operational on an individual POS Item basis, depending on the programming of the flag Use Cmts Print In Red Flag set under Printer Configuration Terminal Print Options on the Remote Tab. Suppress Check Print. If you set this parameter to a Y, then the selected menu item will not print on the guest check or on a receipt. As a general rule, this should not be checked for ANY item that does not have a price of $0.00, and even these items have a separate method for eliminating their printing. Suppress In Window. This is a method of making the POS Item Inactive, even though the menu item itself is active. It does not pertain to an instance of this POS Item as a Preset, only to the Popup window display. With a check mark here, this POS Item will not list on the Popup window corresponding to this List File. Hide In Combine Mode. This flag is automatically implemented for POS Items which are DCM type and are $0.00 priced on the point-of-sale. Inverse On Video. A check mark here will cause items to display in inverse on an Order Video screen. Undo Bold. This relate to printing on a remote chit. Normally, all items on the remote chit are printed bold/double wide. To set a particular item to print single wide, put a check mark here. Image File Location. This setting is used to place a bitmap icon on the Popup Window which displays this POS Item. Use the Browse button below to select an appropriate bitmap (bmp file). POS Item Remote Printing Considerations The entry programmed in Remote Printer Groups determines on which printers or Order Video screens the items will appear. Normally, you will want condiments to follow the main item. To accomplish this, enter the appropriate Remote Printer Group for the main item and leave the selection Remote Printer Groups as a blank field for the PO S Items which are condiments. They will then follow the main item. You can also cause the condiments to print an additional separate chit. Under the main item, enter the appropriate Remote Printer Group where you wish both the main item to print, along with the condiment item whic h will follow. Enter a different Remote Printer Group under the POS Item which is a condiment. Note that th e same printer could be listed in each, so that the requisition would first include the main item along with the condiment, then a separate chit would print on the same printer, including only the condiment itself. You can also cause ONLY the condiments to print, with the main item not appearing. This is often useful with Fixed Menu Items. Under the main item, enter a 0 as the Remote Printer Group. Enter a valid Remote Printer Group under the POS Item which is a condiment. Only the condiments themselves will print. Odyssey/BackOffice Suite Programming Sales Related Selections 45

46 POS Item Programming Flags Tab Increment Cover Count. This flag interacts with the system-wide option programmed under POS System Options Miscellaneous Options, the Add to Covers by Item Only flag. With the systemwide flag set as true, a check here will cause the purchase of this POS Item to increment the guest or cover count. Modify Condiments After Send. This flag will generally be set, for control purposes, to a no. With no check mark here, after a PLU type POS Item has been serviced, the POS Operator will not be able to add a condiment or modify an existing condiment. The only way to change what has been sent to the kitchen is to void the entire PLU item and re-ring the item and all of its condiments. You should ALWAYS set this flag to a yes if the following flag Fixed Menu Type is set. You might also set this flag for condiments which modify an All You Can Eat POS Item, but you would also implement control by associating the PLU and the condiments using the PLU/CMT link described in under the section POS Item Programming General Tab. Fixed Menu Type. This setting is for a menu type which includes only certain items, for instance a $20 Fixed Meal might include your choice of one of several appetizers, one of several main courses and one of several deserts. The required programming to set up a Fixed Menu is the subject of a subsequent section. Scale Required. This setting indicates that the POS Item can ONLY be used in conjunction with a weight entry, either from an interfaced scale or a manual weight. Image File Location. This setting allows you to place either a BMP file or an ICON file on the button displayed when this POS Item appears in a Popup window. ICON files are a fixed size and are NOT recommended for this purpose. Use the Browse button to start at c:\icom\pos2100\graphics to select a BMP file. Note that all graphics used by the point-of-system must be resident on the hard disk of the terminal on which the application is running, in the same folder you select here. POS Item Programming Itemizers Tab This tab contains a list of the sixteen itemizers, with the name you have previously entered under the General Tab of Itemizer Programming and a check box for each itemizer. If this POS Item should add to the itemizer, for tax or discount calculation purposes, place a check next to the itemizer. Note that itemizer calculations can be excluded through Sales Type programming, so if you have an item which is taxable if the Sales Type is Here but not taxable if the Sales Type is To Go, you should always place a check mark next to the itemizer which is accumulating the tax. POS Item Programming Bonus Points Tab Individual POS Items may be programmed to accumulate points in up to eight categories. This accumulation is only on a transactional basis, and only for printing on the bottom of a guest check/receipt. The descriptors which show on this tab are programmed under Printer Configuration System Print Options. If the descriptors shown on this tab are blank, then no points will ever display. The first criteria for printing Bonus Descriptors and the accumulated points for each is a non-blank descriptor. Even if the Bonus Descriptor is non-blank, no line will print if there are no accumulated points in a particular category or if the flag Print Bonus Descriptors, under Printer Configuration Terminal Print Options on the Check 1 Tab is left unchecked. Bonus Descriptors print at the bottom of the guest check/receipt, when the descriptor is non-blank, points have been accumulated and the flag Print Bonus Descriptors is checked. List Files By Store This programming selection is only applicable in multi-store situations, where Odyssey Enterprise Manager is being used to create in-store databases for multiple locations. The setting List File Unique By Store, set on the General Tab under List File Programming, selects List Files which contain all items available in all stores, where certain stores will only have certain items available for 46 Sales Related Selections Odyssey/BackOffice Suite Programming

47 sale. When List Files By Store is selected, only those List Files with this flag checked will show on the selection. You can initially set ALL POS Items with the same setting by left clicking in the small gray box in the List Details Tab, immediately to the left of the # column. This selects all POS Items in the selected List File at the selected store. This programming selection allows a multi-store group to maintain fewer databases, although there may be many locations, when only a few items are different from store-to-store. When programming changes are updated in the store, the setting Display In Window, for the selected List Files, will be determined by which store is receiving the programming update. Note that this requires that items which are sold at only certain stores be accessed on the POS2100 via a Popup Items button and not a Preset button on the Sales Desktop. Condiment Chains A Condiment Chain is a sequential presentation of Popup windows which are DCM type List Files. A chain is used display windows of condiments which prompt the operator in a pre-determined manner. Up to five different DCM type List Files may be chained in a sequence. Each of these five different screens can allow multiple entry or be repeated in a sequence. The order in which the List File names are entered within the sequence is the order that an operator will be led through the ordering process. NOTE: Only List Files which are the DCM type may be listed in a Condiment Chain. You can always use the Add New With Details to create a DCM type List File from a PLU type List File, if required. Obviously you must first create all of the List Files which you will want to use in a particular Condiment Chain. Since a Condiment Chain has certain properties which are not associated with a DCM type List File, you may very well create several Condiment Chains which have only a single DCM type List File within the chain. A Condiment Chain may be placed, like a DCM type List File, as a separate button on a Sales Desktop of the point-of-sale terminal. There is also a Popup presentation, as there is with all DCM type List Files, of all Condiment Chains. Condiment Chain Programming There is no bulk programming associated with Condiment Chains. Each must be programmed separately. The process of completely programming a point-of-sale database will be an iterative one, as relates to Condiment Chains. As you determine POS Items where you would like to lead the operator through a sequence, you will first create List Files containing the various items to prompt. Then you will group these List Files into a Condiment Chain. Often the POS Items within the DCM type List File will require their own separate Condiment Chain, e.g. a potato selection is prompted with an entrée, but you want the potato toppings to be prompted when the potato is selected. Once you have your Condiment Chains programmed, you will go back to the List Files area, select POS Item Programming and associate your Condiment Chains with ind ividual POS Items from the screen POS Item Programming General Tab. The entries made on the Condiment Chain Programming screen are as follows. Condiment Chain Number. This is merely an identifying number for the chain. There is no reason not to simply start with 1 and continue sequentially as you create new Condiment Chains. Condiment Chain Name. Enter up to sixteen characters to describe the chain. Remember, this name will appear on the dropdown list when you are programming POS Items and it may appear in a Popup window on the point-of-sale if you place a Condiment Chain lookup button on a Sales Desktop. When you are developing an application with lots of lead-through, keeping track of all the Condiment Chain Names is often difficult. Condiment File 1 to 5. You can include up to five List Files in a Condiment chain. However, any POS Item in a List File which is part of the chain can also call its own Condiment chain, therefore there is virtually no limit on the lead through process which is provided. Odyssey/BackOffice Suite Programming Sales Related Selections 47

48 Alternate Banner Text 1 to 5. This entry pertains to the text displayed at the top of the popup display window showing the condiments. Leave the entry blank if you wish the default text to appear. The default text is generally the name of the menu item being modified. If you wish alternate text to appear for this specific condiment file, enter it here. An example might be Touch Any/All Touch Here as a lead through on multiple entry and highlight type condiment popups. # to Select. This entry is only examined if the following, Multiple Entry is true. The entry Number of Selections in List File Programming for Condiment Files is not valid when the file is used in a chain. It is replaced by this entry. This will limit the number of multiple entries allowed from the presented popup window of the List File. No quantity entry will be accepted, as is documented below under compulsory. If you purchase 3 PLU items, and then are presented with a multiple entry popup, limited to four choices, you will only need to (be able to) select four. You will not be able to say 2 this way, then 1 this way and then proceed on the balance of the next three available in the multiple entry window. Multiple Entry. This is a selection available for each individual List File in the chain. A check here indicates that there is no association between the quantity of a PLU type POS Item and the number of entries allowed when this List File is presented as a Popup. As an example, a listing of all of many different Hamburger toppings would certainly be a Multiple Entry as a Yes. A window which displayed Meat Temperatures would certainly be a Multiple Entry as a No, because you can only cook the meat one way. With Multiple Entry as a Yes, you have the choice on whether or not to make the Popup window for the List File a Highlight window or not. You CAN NOT make a Popup Highlight which is not a multiple entry window. If you do not check this box, you will only be allowed to select as many items from the displayed Popups as you entered for the main PLU Item. The pointof-sale software automatically assumes, if you merely touch a button, that the quantity is the same as the entered PLU Item. For instance, if you touch 3 then Hamburger and the Popup you display has two selections, With Cheese and Without Cheese, if all the Hamburgers are With Cheese, you merely touch With Cheese. If 2 are with and 1 is Without, when the Popup displays, touch 2 then With Cheese. You have the choice next, since there is only one item left un-described of either simply touching Without Cheese or touching 1 then Without Cheese. With Multiple entry not checked, your ability to NOT make a selection from a Popup List File window is determined by the flag Compulsory. If Compulsory is not checked, then you can touch the banner at the top of the Popup at any time to say I want none of these. If Compulsory is checked, then you must choose one of the selections for each of the main PLU items you purchased. The window will not go away until you have chosen. An example of Compulsory might be for meat temperatures. Highlight. This is a very useful feedback mechanism for many kinds of multiple entry Popup List Files. With Multiple Entry as a Yes and Highlight as a Yes, when the POS Operator touches a button on the displayed window a circle of a different color appears on the button as it is touched. The color of the circle is generally white, which means you want your text on the Popup to be black or some other dark color. These color used to draw the circle is the Condiment Highlight color, set on the General Tab under POS System Options Desktop Options. When the item is touched, it highlights and is placed on the guest check display. To remove the item, touch it again. The highlight goes away and the item is removed from the guest check. Compulsory. This selection is mutually exclusive with the Multiple Entry selection. You can make a Popup either Multiple entry or Compulsory, but not both. With Multiple entry not checked, your ability to NOT make a selection from a Popup List File window is determined by the flag Compulsory. If Compulsory is not checked, then you can touch the banner at the top of the Popup at any time to say I want none of these. If Compulsory is checked, then you must choose one of the selections for each of the main PLU items you purchased. The window will not go away until you have chosen. An example of Compulsory might be for meat temperatures. Automatic Condiment Entry (Macro) You have the ability to automatically enter a condiment when a menu item is entered by setting up a List File with a single item, then configuring the DCM type List File as compulsory in a Condiment Chain. A typical use of this feature would be if regular french fries were always included with a combo meal. In order to requisition the fries on the Kitchen DisplayStation, the condiment must be entered. (Some operations want 48 Sales Related Selections Odyssey/BackOffice Suite Programming

49 the fires to display, some do not. This provides an easy way to accomplish the display on the Order Video with no Operator action.) Since the fries are always included, it should not be necessary for the operator to make the entry. To enable this automatic entry, you need to program a Condiment File with only one entry, the regular fries. Place this condiment file as the first entry in the Condiment Chain, and check the Compulsory Entry When the POS Item is purchased which has this Condiment Chain is entered, the regular fries will be automatically entered, just as if the operator had selected from a window with only one entry. There may be multiple automatic entries, however, each one will require a separate only one entry. Condiment File with There may be a second Condiment File in the Condiment Chain as well. For example, the regular fries are auto matic, but the customer is offered the choice of beverage. After the single item in the first Condiment File is automatically entered, the selection window of the Condiment File containing the beverages will appear. Suggestive Selling Definitions Suggestive selling is intended to work in conjunction with an LCD Customer Display. For the configuration and a view of the 12.1 LCD Customer display, refer to the section I/O Devices - LCD Customer Display. Suggestive selling will display a picture, a jpg, bmp or gif, to the customer based on what has already been entered and what has not been entered. Menu items belong to a suggestive selling group. Generally this will be programmed by Category, but it can be programmed by a single menu item. As an example, suppose we wish to suggest purchases to the customer as follows: 1. Salads 2. Drinks 3. Wraps 4. Panninis 5. Soups 6. All Others 7. Final Display You would first program the Salad category for all items to belong to Suggestive Selling Group 1 (or perhaps 10 if you were leaving room for another suggesting selling group). Then program the Drinks Category for Suggestive Selling Group 2 (or 20), etc. All other Categories would belong to Suggestive Selling Group 6 in the above example. Refer to the programming screen below. At the beginning of a transaction, the Image File from Suggestive Sell # 1 (or the smallest number programmed) will display. It will continue to display until an item from that group is selected. As soon as the item is rung, the software will look to the next highest group and continue until it encounters a group from Odyssey/BackOffice Suite Programming Sales Related Selections 49

50 which no item has been rung. From the display above, no items are programmed to belong to Suggestive Sell Group 99, so the Image associated with that will display once an item from each and every group has been entered. Between transactions, the display may either display a single image, a single video (avi or wmv) or a series of either or both. The software will look to the folder G:\POS2100\Graphics\SuggestiveSellIntermission and display in alphabetical order. For images, the display will show for five (5) seconds. For video, the entire video will present. Note the P4 Glaive does not have internal speakers. Suggestive Selling Not Menu Item Related An alternative to utilizing the suggestive selling portion of the 12.1 LCD customer display is to merely sequence through a list of graphics files or a movie contained in the folder G:\POS2100\Graphics\SuggestiveSellIntermission. This will occur if you define NO Suggestive Sell Definitions. The sequence of graphics or the movie can also be defined by Day Part. This allows for a different grouping of suggeste d Me nu Items by the time of day. The so ftware will search for sub-folders under the folder with a DP extension, e.g. G:\POS2100\Graphics\SuggestiveSellIntermission\ DP1 through./dp10. There are currently only a maximum of ten day parts. When the time changes to begin a new day part, the files in the appropriate folder will be displayed. If there is not a specific folder /DPX, then the files in the main folder will be displayed. Suggestive Selling Graphic Sizes The ideal size for a displayed graphic will depen d on the native resolution of the LCD customer display. The pictur e takes up roughly 2/3 of the displayed screen. Below is a chart for common native resolutions. Most likely you will not be able to create graphics files of the exact size shown. It is good to try and maintain the ratio shown on the right and make the picture j ust a little smaller, rather than a little bigger. Native Screen Resolution Ideal Picture Size Horizontal Vertical Horizontal Vertical 640 x x x x x x x x x x x x x x x x Sales Related Selections Odyssey/BackOffice Suite Programming

51 Fixed Menu Type Items This section outlines the methodology for creating the requisite control over Set Selection type meals. The control involves: Prompting with only those items which may be chosen for the particular Fixed Menu Selection. Preventing POS Items intended for use with Fixed Menu Selections from being used with other POS Items. Prompting the POS Operator, prior to printing a guest check, that not all items included with the Fixed Meal have been entered. This example will use the List File Fixed Menu from the demonstration database. The List File contains two menu items, $20 Dinner and $30 Dinner. The choices for appetizers, main course and dessert are, of course, different between the two. Each of these two items has a check mark next to Fixed Menu Type and Modify Condiments After Send on the POS Item Programming Flags Tab. NOTE: This control mechanism has been improved with the May 2008 release and no longer works the same as in prior versions. The improvement allows for significantly easier entry when a patron has changed the selection during the course of serving to either a more or less expensive fixed menu selection. Fixed Menu Type Items List File Control If the various selections for Fixed Menu items, e.g. choice of appetizers, mains, desserts, etc. is the same for all Fixed Menu Items, and the variation is in the number of choices offered, then all Fixed Menu Items should be placed in the same List File. If different groups of choices are offered for different Fixed Menu Items, then the Fixed Menu Items which choose from the same groups may be placed in the same List File, creating multiple List Files. Doing so, however, requires that a selection button for the various groups for EACH type of Fixed Menu Item be placed on the Sales Desktop. If the Fixed Menu Items are all in the same List File, you can still prevent certain items from a group from being used with certain Fixed Menu Items, e.g. there are certain appetizers for the $20 Dinner and others reserved for the $30 Dinner. To ease any possible POS Operator confusion, it is recommended that the use of the selections be encoded into the name of the item. Fixed Menu Type Items Condiment Chain Control We will want a separate Condiment Chain for each of the two Fixed Meals we are entering. The less expensive Fixed Menu Item will have fewer selections. It is important that the List Files included in the Condiment Chain be in the same order for the different Fixed Menu Items. In addition, we will want to prevent any POS Items which are included in the DCM type List Files which will be included in the Condiment Chains from being used to modify the Fixed Meals. Remember, the price is controlled by the price in the PLU type List File. In general, all of the choices in the following windows will be at a price of $0.00, although nothing prevents one of the POS Items in an included List File from having an up charge. To establish control, we will be creating one Condiment Chain called $20 Meal Choices and another called $30 Meal Choices. We will arbitrarily select a PLU/CMT number of 78 for each of these meals. If we wanted different items for each meal, we would still have the same list of files in our Condiment Chain, but the PLU/CMT number for the $20 Meal, and all POS Items in all item in the List Files in the Condiment Chain reserved for $20 Meals would also use a PLU/CMT number of 78 and the same would hold true for our $30 Meal, and all POS Items reserved for use with it. That means if the same Menu Item is included in both, we must create another instance of the Menu Item in the same List File, only for use with the appropriate PLU item. Obviously the use of the item would need to be encoded in the PLU Item Name to assist the POS Operator, e.g. Scallops $20 FM and Scallops $30FM. Odyssey/BackOffice Suite Programming Sales Related Selections 51

52 To continue with our example, a $20 Meal includes a choice of a Starter, choice of Entrée and choice of Desert. Our $30 Meal includes the above, but also includes a choice of a wine. We will create four List Files and two Condiment Chains. The Condiment Chain for the $20 item we will call $20 Meal Choices. The List Files will be Fixed Meal Starters, $Fixed Meal Entrees and Fixed Meal Deserts. The second Condiment Chain will have the identical List Files as the first three choices and the fourth will be Fixed Meal Wines. Each of the POS Items in the three DCM type list files for the $20 Meal has a price of $0.00 at all levels. The following screenshot shows the Condiment Chain $30 Meal Choices. The Condiment Chain $20 Meal Choices is identical, except it only includes the first three Condiment Files. Each of the four included list of items is in the Condiment Chain. Part of the control we are looking for with Fixed Meals is to prompt the POS Operator, prior to the guest check being printed, if not all of the included choices have been entered. If you want that level of control, you MUST list each grouping on the Condiment Chain with which the PLU type POS Item. That means that the first time the Meal choice is entered, the POS Operator will be prompted with each of the displayed four choices. That is also the reason the Condiment Files are NOT compulsory, allowing the POS Operator to postpone the desert selection or the entrée selection until the guest is ready to make that choice. Fixed Menu Type Items POS/2100 Control In order to allow for selection of an Entrée or Desert or Wine after initially entering the Fixed Menu, the Sales Desktop on the POS/2100 has a button corresponding to each of the selections, for Starters, Entrees, Desserts and Wines. In the demonstration database, the buttons are Condiment Chains. If the POS Operator highlights a line on the guest check which says 3 $30 Meals, he/she will be able to depress the Button on the Sales Desktop $30 Entrees and select only one, if at least one of the $30 Meals has NOT made an Entrée choice. However, if all of the three meals have already made an Entrée choice, even though the Modify After Send flag is set as a Yes on the main item, the POS Operator will NOT be able to add an illegal entrée. For ease of entry, the patron may change his/her mind to either a less expensive or more expensive Fixed Menu Item, depending on what has already been entered. To accomplish this, the POS Operator touched the Fixed Menu item on the displayed receipt and touched Button Type Modify Fixed Menu Item. A list of allowable changes is displayed. In all cases this means displaying all items in the same List File which have List Files in their Condiment Chain which have already been entered. The corrected Fixed Menu Item moves to the bottom of the displayed receipt, much as a Void Item. However, since there is no change in any requisition, there is not remote printer chit generated nor can this item be re-inserted onto the Guest Check. For additional POS functionality relating to Fixed Meals, the POS/2100 software checks the items on a guest check when a Print button is selected. If there are any Fixed Meal type POS Items on the check, the software uses the Condiment Chain to which the Fixed Meal item is linked and confirms that a choice has been made 52 Sales Related Selections Odyssey/BackOffice Suite Programming

53 from every list on the above screen for each item. If there are missing included items, a display prompts the Operator and allows the Operator to exit the Print and use a Send instead and go interact with the guest who is missing an included item. An example of an incomplete Fixed Meal prompt is shown below: The ability of the POS Operator to print a guest check in this situation Options Transaction Options on the End of Transactions Tab. Fixed Menu Type Items Requisition Printing is controlled under POS Terminal In general, the text $20 Fixed Meal will convey no information on the requisition chit. The items selected from the List Files presented through the Condiment Chain represent the actual items to be prepared, so there is generally no reason to want the main item, $20 Fixed Meal to print on the requisition chit. Since this item also has the flag Modify After Send set, under POS Item Programming Flags Tab, the normal requisition printing format would not only re-print the main item on subsequent service rounds when additional courses are selected, but would also print the prior courses selected along with the new courses with a + sign next to them. In order to not print the main item, yet print the courses, set the entry Remote Printer Groups, under POS Item Programming Display/Print Tab, for the $20 Fixed Meal to either a 9 or a 0. If you set the group for the $20 Fixed Meal to a 9, then all of the individual condiments (selections under fixed meal) will group together, based on their Print Sequence as defined in POS Item Programming Display/Print Tab. If you set the group to 0, the only way to group like items, i.e. group the appetizers together, followed by the entrees, is to use separate Printer Groups with the same printer listed in the group. This will print a separate chit for each group of like items on the single printer. To get a grouping on a single chit of all of the like items on a Fixed Meal on one printer: If you are using the Print Sequence of the individual condiments associated with a Fixed Meal to provide the grouping of like items together, set the Printer Group for the Fixed Meal to a 9. Then, as an example, say all items will print on RequisitionA. Use Printer Group 6, and list RequisitionA as the only printer in this group. Program each of the condiments to go to Printer Group 6. Program the Print Sequence for appetizers to a 2. Program the Print Sequence for entrees as a 4. Program the Print Sequence for the desserts as a 6. The like items will group together, but all print on a single chit. The only reason this example did not use Print Sequences 1, 2 and 3 was to leave room in case an additional kind of item was ever associated with the Fixed Meal. To get separate chits for each of the like items on a Fixed Meal on one printer: If you are using Printer Groups to provide the grouping of like items together, set the Printer Group for the Fixed Meal to a 0. Then, as an example, say all items will print on printer RequisitionA, and there are three courses which will print in the kitchen. Allocate Printer Groups 6, 7 and 8 for this function. List RequisitionA on the first line of each group. When both the appetizers and entrees are ordered on the same service round, with multiple Fixed Menu items being ordered, a separate chit listing only the appetizers will first print on printer RequisitionA, followed by a second chit listing only the entrees. In this example, it is the Printer Group designation which is grouping the like items together. Odyssey/BackOffice Suite Programming Sales Related Selections 53

54 Fire Messages Fire messages provide additional information on requisition chits printed in the kitchen. In addition, a fire message may be programmed to hold the printing of a requisition chit for certain items, in situations where the POS Operator is controlling the movement of food from the preparation area. NO TE: Fire Messages do not display on the Order Video displays. Fire Message Number. This is an identifying number for the Fire Message. In addition, it controls the listing order of Fire Messages on the Popup Window which displays all Fire Messages. It is a good idea to start with number 10 and increment message numbers by 10 in order to provide room for any additional Fire Messages which you wish to sort in a particular order on the Popup window. Fire Message Name. Enter up to thirty characters of descriptive text. The Fire Message will print in bold on all requisition chits, with a leading and trailing * character to distinguish the message from an actual menu item. If you enter more than sixteen characters, the Fire Message will cause two lines of print, both in bold, so if you are going to enter more than sixteen characters, think about the separation as you are entering the text. Remote Printer Group. Entering any number other than a 0 here will cause this Fire Message to stand-alone and not be associated with a particular menu item. It may also print on the guest check if both the flags Retain With Check and Print On Check are set. The Printer Groups here are the ones with which printers are associated under POS Terminal Options Output Groups. The valid Group Numbers are 1 through 8. With no highlighted item, the Fire Message will appear on the top of the guest check presentation. It will appear after any highlighted item. Entering a 0 here indicates that the Fire Message modifies the highlighted item on the guest check. If no item is highlighted, the point-of-sale will prompt that no item is highlighted. A special kind of Fire Message is one with a Remote Printer Group of 0 and the flag Remote Fire also set. Active. Place a check mark here for the Fire Message to appear in the Popup window on the point- of-sale. Modify Message. A check mark here means the POS Operator will have the ability to modify the text through a Popup keyboard presentation on the point-of-sale. Print In Red. A check mark here will cause the Print In Red characters to be sent to any printer along with this Fire Message. Retain With Check. A check mark here will cause the Fire Message to continue to display on the guest check presentation on the point-of-sale. Print On Check. A check mark here requires that the Fire Message also be set to Retain With Check. Remote Fire. This is a special kind of Fire Message, which works in conjunction with a Remote Printer Group setting of 0. A Fire Message with this flag set, along with a Remote Printer Group of 0, is used to group highlighted items together on any printers where they will print. A separate requisition chit is printed, with the Fire Message at the top of the separate chit. An example of use would be HOLD 15. Operationally, the POS Operator highlights the items to group, then depresses the Fire Message Popup and selects this kind of Fire Message. Another use of a Fire Message with this flag set, along with a Remote Printer Group of 0, is to store the printed information for a predetermined period of time, an actual hold before printing time, then print the requisition chit. Carry Type Remote Fire. This flag may only be set if the "Remote Fire" flag is set. This is a different entry method for messages. Instead of touching the item to which the Fire Message will attach, this kind of Fire Message will attach to all subsequent items. It allows the POS Operator to enter items which will have no message (and print at the top of the requisition chit), then touch a "Carry Type" Remote Fire Message for subsequent items, separating the groups on the chit with a header of the Fire Message. It allows the fastest entry method for grouping items on a remote requisition chit. NO TE: See the section under Printer Configuration Printer Definitions for an alternative method of organizing items on a "by-type" basis (e.g. appetizers, then mains, then desserts) on a single chit of a remote printer. 54 Sales Related Selections Odyssey/BackOffice Suite Programming

55 Hold Print. This flag may only be set if the Remote Fire flag is set. This flag causes the printed information to be delayed for a programmed number of minutes before printing. Minutes Delay. For Fire Messages with Hold Print set, this determines the number of minutes the software (WRemote operating on the Server) will hold the highlighted items before sending the information to the printers. Odyssey/BackOffice Suite Programming Sales Related Selections 55

56 BackOffice Selections Navigation We will proceed through the BackOffice Selections as they are displayed below. Note that there are two ways of accessing the programming, using the navigation pane at the left of the screen or the drop down at the top of the screen. Store Configuration In most instances, there will only be either one or two entries under Store Configuration. One is for this store. The others are used only in the Inventory Module for transferring inventory from one store to another. The default database is configured with two entries, This Store and All Transfers. Store Configuration Configuration Tab Entries here are for information retrieval only. Enter the appropriate information on the right side of the screen, under the tab itself, for each store. Use the Enter or Tab key to move to the next field. It is not necessary to click on the Save icon. Moving to the next store or to the Miscellaneous tab will save the information under the Configure Tab. If you have not clicked on the Save icon, you may use the Undo icon to restore the original information. Store Configuration Miscellaneous Tab The ISO Currency Code entry under this tab is for future use. The ISO Country Code, for the store defined as this store, is used in the Reports Module to determine if VAT extraction is applicable with various sales reports. If you are in the United States, this setting should be either US or USA. Any other settings here will change all related sales reports to report extracted VAT. If some of the pricing at the point-of-sale is such that tax is included within the price, and you need to extract this included tax, set the entry at something other than US or USA. 56 BackOffice Selections Odyssey/BackOffice Suite Programming

57 The check mark next to the text This Store determines at which store in the list the software is installed. Notice that you can not uncheck this setting. You can only set the box in a store which is currently not defined as This Store. In general, you should merely change the name and add any desired information under the Configure Tab for the record already defined as This Store. The check box next to the text No Decimal On POS is only applicable with the PCS/5000. It causes every currency field brought in from the PCS/5000 posting files to be multiplied by 100. It should only be checked in countries where the currency valuation is such that no decimal point is ever printed on the point-of-sale, and only set in conjunction with the matching entry on the PCS/5000 configuration module. Unless you are installing a new Odyssey BackOffice Suite in conjunction with a PCS/5000 system with the matching entry set, DO NOT place a check mark in this box. The Hourly Staff Chart selection is for a future release. Leave the entry at "Staff Chart Inactive. The Notes section merely allows the operator to enter free form text information. BackOffice Options The entries programmed here affect various displays and procedures on the BackOffice. They should, generally, be programmed once, then remain fixed. Disable Log In Screens. Generally this box is left unchecked. A check in this box affects whether the User Name and Password is prompted before or after the actual application is launched. With a check, the application will launch then the User Name and Password will be prompted. Legacy Sort Items. Previous releases of the BackOffice have sorted all lists in a non-standard manner for text fields. If you are installing in a new location, do not check this box. Desktop Main Toolbars Visible. A check in this box will show the left hand side of the screens for an Outlook style selection. CoolNet Export Enabled. This box is exclusively for use with Rita s installations. The selections under the Flash View selection allow either recipe costing or labor costing or both to be excluded from the Flash View Report selection in cases where Inventory or Time & Attendance are not implemented at a particular site. Disable Recipe Costing. A check in this box will exclude the section of the Flash View report pertaining to Inventory Recipe Costing. Disable Labor Costing. A check in this box will exclude the section of the Flash View report pertaining to hours worked, personnel currently on-the-clock and labor costing for the current day. The Accounting Period Ends selection pertains both to the AccountCharge module within Odyssey BackOffice Suite and the To-Date reports within Odyssey Reports. Statements are prepared on a Monthly basis, and this selection defines the monthly period for AccountCharge. The To-Date reports provide current day, current week and current month information. The next section provides additional information on changing the Accounting Period. Last Day of Calendar Month. A check box here indicates that the AccountCharge monthly period is a calendar month. For the To-Date reports, the first day of a week will be different for each calendar month, and will be defined by the day of the week on which the first day of the month occurs. Last Account Week In Month. A check box here indicates that the AccountCharge monthly period is set to coincide with an Accounting Month. This facilitates comparative reporting, since the first day of each week and month is the same day of the week. This selection works in conjunction with the next selection, the Day Account Week Begins. This selection will cause all months to consist of either a four or five week period, i.e. either exactly 28 or 35 days. The Day the Account Week Begins defines the first day of a new period. The month will end on the prior day. Months always will end during the calendar month. For example, if the last day of your week is a Sunday, the Reset Day will be a Monday. For the month of September, 2002, the last day of the accounting month September would be Sunday, September 29, Monday, September 30, 2002 was the first day of the accounting month of October, Odyssey/BackOffice Suite Programming BackOffice Selections 57

58 Day Account Week Begins. Use the drop down list to select the first day of your week. Generally this will be the same day you will place under programming for Staff Employee Configuration, the selection Day A Work Week Begins. On the right of this screen there are several miscellaneous selections as follows: Tax 1 Local Purchase. This flag is for use in conjunction with the Inventory Module, which allows for the local purchase of inventory. A local purchase will add to inventory on hand, deduct the funds paid from the store funds, as well as allocate any tax amounts associated with the local purchase. The entry screen provides for the entry of up to two separate tax amounts. If you are using Inventory AND are providing for the entry of local purchases of inventory, use the dropdown list to select the primary tax. Tax 2 Local Purchase. Same as the above entry for a possible second local tax which might be charged on local inventory purchases. Petty Cash Bank Amount. If you are using the Deposit functionality of the Odyssey BackOffice Suite, the software will prompt the operator with a suggested deposit from the Transfer Screen for cash. This defines the amount which is prompted, and is to allow for a small amount of cash to be retained. If you are using this functionality, enter the amount of cash normally retained at store level. If no cash is either being retained at store level, or if Odyssey BackOffice is not being used to track these funds, enter Display Detail Safe. This box pertains to the count screens presented for BackOffice Control Accounts. A check box here will always fill the theoretical amount into the counted amount. This provides for an extremely quick counting process, as all the User must do is enter any counted amounts which different from the theoretical. A left click on Accept indicates all amounts are correct. Display Detail Operator. This box pertains to the count screens presented for POS Operators. A check box here will always fill the theoretical amount into the counted amount. If you are not counting POS Operator amounts in the BackOffice, e.g. for banked servers whose bank is counted on the floor and then merely pooled in the BackOffice with all other funds, place a check in the box below. Auto Count Operators. A check in this box will eliminate the requirement to balance each individual POS Operator during the End Of Day procedure. All operators will be assumed to perfectly balance the theoretical amount with the actual amount collected from the POS Operator. This process occurs during the Process POS Transaction Log function within Odyssey BackOffice Suite. Auto Deposit After Operator Count. This flag is mutually exclusive with the Auto Count Operators flag. It is applicable after counting operators. With a check here, if there is an active Drop Box Control Account and active Transfers from Petty Cash to the Drop Box for media such as Cash and Bank Checks, the software will automatically move the entire amount first to Petty Cash, then to the Drop Box. The POS Operator Name will be included in the Comment field, along with the Envelope Number for the deposited media. Enable Auto Link. This only pertains to PCS/5000 installations and the selection is disabled if the POS Type is POS/2100. Under the selection Default Account Types: Delivery Account Type. This selection is used by the point-of-sale software when a delivery customer is added during a transaction. Since Account Type is a required field when adding a new Account Member, a default is required. Import/Export Account Type. This selection is used when importing or exporting into the AccountCharge database. Since Account Type is a required field when adding a new Account Member, a default is required. Back Office Options Accounting Month The accounting period structure is designed to be as simple as possible to maintain. It is not intended to cover each and every situation which a particular establishment may utilize. There are only two options. The accounting month is a calendar month. The accounting month ends on a particular day of the week, and a particular month ends on the last time this day occurs in a calendar month. If the calendar month has 31 days, and the last day of your accounting month is a Sunday, and in this particular month Sunday is the 25 th day of the month, that 58 BackOffice Selections Odyssey/BackOffice Suite Programming

59 means Monday the 26 th of this calendar month through Saturday the 31 st of this calendar month will be in the next accounting month. You CAN change the accounting period in the middle of a month. For new installations, if you are using the AccountCharge functionality and are preparing statements, or if you are using the To-Date reporting you should enter the correct accounting period on the first day of use. If you change the accounting period on Sales Day 2 (the first day of use), the current accounting period will be correct. However, if the Sales Day is not Sales Day 2, the current accounting period s beginning date CAN NOT BE CHANGED. The current accounting month will end based on your new settings, and subsequent accounting months will reflect your changes. Archive This selection determines the number of days certain information will be retained in the database. With the March, 2004 release of Odyssey BackOffice Suite, the "Purge/Recover" functionality has been eliminated. Once information is removed from the database, it is not recoverable. In order to retain information beyond the scope of the in-store Access database, an SQL Server based reporting mechanism is available with Enterprise Manager. The following screen illustrates the default periods for the archiving of information: The database will not accept an entry for "Days To Retain" which is less than thirty six for any Archive type. If you are upgrading an existing installation and you wish to retain information within your active database (prior to the new "purge" functionality removing it permanently from the database) you should recover information from the Archive database prior to upgrading. The response of all activity through Odyssey will deteriorate as the size of the database grows. As a general rule, it is best if the size of the database is kept below 500 MB. The largest single contributor to the size of the database is the POS Transaction Details. The defaults illustrated above allow for the current month s data to always be available, and information on all activity for the last year, in the form of the roll-up tables. It is highly recommended that you NOT set POS Transaction Details to be retained for any more than 36 days. This will always allow for storing a full five week accounting period, if applicable. Defaults There is no entry required or allowed from this screen. It is merely for informational purposes and lists certain required default entries in the database. Many of the entries allow for the names of the database elements to be changed, so the screen is very helpful from a support standpoint. Odyssey/BackOffice Suite Programming BackOffice Selections 59

60 Control Account Types Control accounts are the structure around which Odyssey MWS provides an accounting for the movement of funds within your store. A control account is the basic structure used in the Odyssey Suite for moving funds. A control account is like a cash drawer, in that it is a depository for funds. A control account is either an internal account, the money is still in your store, or an external account, the money is no longer under control of the store. While only Control Account Types 1 through 4 are fixed (can not be changed nor deleted) it is HIGHLY RECOMMENDED that NONE of the default Control Account Types be changed or deleted. Deleting a Control Account Type will also delete all Control Accounts of that type. Control Type Number. This is merely a reference number. You will note that the first four types are numbers 1 through 4, listing Front-Office (POS), Back-Office, Over/Short and Bank. The only entry which may be changed for these is the Control Type Name. Unless your installation is in a foreign country and you are entering a foreign language descriptive name, it is highly recommended that, for support purposes, you not change the names on these required, default Control Account Types. Control Type Name. This is the name for the Control Account Type which will appear throughout Odyssey screens and reports. Internal Account. A check in this box indicates that any funds associated with the Control Account Type are within the store itself. The funds associated with the POS network and the Back-Office are Internal Account types. No check in the box indicates that any funds associated with the Control Account Type are outside of the store itself. The Bank is an external Control Account Type. Allow External Transfer. A check in this box allows funds to be moved from an internal Control Account Type to an external one. Note that the Back-Office has a check box but the Front-Office (POS) Control Account Type does not. Control Accounts There is a lengthy discussion in the Odyssey Operations document covering Control Accounts. If you are not familiar with the concept of Control Accounts, do not enter anything on this screen until you read the appropriate documentation. Control Accounts 10000, 20000, 20100, 30000, and are fixed. Control Account Number. This is merely an identifying number for the Control Account. The convention used in the default database uses the Control Account Type Number as the first digit(s), followed by four digits from 0000 to You can not change the number if historical data exists. Control Account Name. This is the descriptive text displayed for the Control Account throughout all application programs and reports. Control Account Type. Select from the dropdown list of all Control Account Types to associate this Control Account with the appropriate type. Require POS Operator ID. Do not set this flag for any new Control Accounts without consulting with Comtrex Support. It is set in the default database for Control Account 10000, All POS Operators. It causes the software on the Transfer Screens to always require the selection of the appropriate POS Operator when amounts are transferred to or from the primary Control Account of All POS Operators. Require Envelope. Do not set this flag for any new Control Accounts without consulting with Comtrex Support. It is set in the default database for Control Account 20100, the Deposit Lock Box. It generates a unique number for a deposit envelope when amounts are transferred to this account from the Transfer Screen. Require Employee ID. This flag causes the software to require the selection of an Employee from a drop down list when amounts are transferred to or from the Control Account. If is set in the default database for Control Account 60300, Employee Advances. Affects Balance.. Do not set this flag for any new Control Accounts without consulting with Comtrex Support. It is set in the default database for Control Account 20000, Petty Cash. 60 BackOffice Selections Odyssey/BackOffice Suite Programming

61 GL Account Types There are only four GL Account Types. You can not add any, and the numbers for the GL Account Types are fixed as 1 through 4. You are able to change the name, for descriptive purposes generally in foreign language countries, and you can cause the name to print on the associated report. Account Types 1 and 2 are Revenues and Expenses, respectively, and correspond to the sections of the Income Statement. Account Types 3 and 4 are Assets and Liabilities and Shareholders Equity, respectively, and correspond to the sections of the Balance Sheet. The Odyssey Suite is NOT intended to be a general purpose accounting system. However, it will assemble sufficient information to export all media, inventory movements and time and attendance information in order to be imported into a general purpose accounting system. In addition, for smaller operators who are seeking a simple, general overview of their financial status, it can report a Changes In Income Statement report and a Changes In Balance Sheet Report, which can include recurring charges, such as rent, utilities, etc. GL Sections GL Sections are first associated with one of the four GL Account Types. These correspond to reporting sections on the built-in reports with Odyssey Suite. There are a number of required Accounts, which in turn are associated with GL Sections. You will not be able to delete a GL Section to which an account is linked. For the default database, every GL Section is required, and can not be deleted. All of the programming entries on this form pertain to the printout of the built-in Changes In Income Statement and Changes In Balance Sheet reports and are not documented herein. It is recommended that programmers, and users, work with the default presentations which are a part of the default database. GL Chart of Accounts This is where the general ledger chart of accounts is defined. There a number of accounts which are required. There is a separate check mark on the programming form, which can not be changed, which indicates whether or not the particular account is required. If a particular account is required, you will not be able to change the GL Section into which the account accumulates. You can always change the descriptive text for an account and you can always change the account number. COA Number. This is a sixteen character text field indicating the account number, on the general ledger chart of accounts. This text number can be changed to correspond to an existing chart of accounts, principally for export, then subsequent import into a general purpose accounting system. COA Name. This is a fifty character text field used to describe the general ledger account. It can be changed to any desired description. GL Section. This is an association with a section of the General Ledger, which in turn is an association with a GL Account Type, i.e. revenue account, expense account, asset account or liability account. For required accounts, this can not be changed. Export. This is a Yes/No field which indicates whether or not the net of all debits and/or credits to this account will be included in the export file for the GL Export function. Required. This is a reference Yes/No field. It can not be changed. Reference Text. This is a thirty character text field, only for use with the export file created with the GL Export function. Odyssey/BackOffice Suite Programming BackOffice Selections 61

62 GL Line Items GL Line Items are the mechanism by which accumulated totals are posted to the general ledger. There are five types of GL Line Items. GL Line Item Number. This is merely an identifying number for the GL Line Item. GL Line Item Name. This is a thirty character text field used to identify the GL Line Item. For automatically created GL Line Items, it will be the Media Name, the Inventory Movement Type Name, the Job Code, the words Salaried Labor Cost or the words Net Sales when automatically created. This name can be changed, however, it is highly recommended that you NOT change this name. GL Line Item Type. There are five types of GL Line Items, four of which are automatically created. The types are covered in subsequent sections. You can NOT change the GL Line Item type once a GL Line Item has been created. Debit COA Number. Use the dropdown to select from the Chart of Accounts which account to debit with accumulated amounts, on a daily basis. This can be changed to any existing account in the general ledger chart of accounts. Changing this account obviously requires a thorough knowledge of general accounting practices and the customer s chart of accounts. This link will NOT be changed or updated automatically. The default Debit COA Number is only created when a GL Line Item does not exist for an existing Media, Inventory Movement Type, Job Code or Net Sales. Credit COA Number. Use the dropdown to select from the Chart of Accounts which account to credit with accumulated amounts, on a daily basis. Changing this account obviously requires a thorough knowledge of general accounting practices and the customer s chart of accounts. This link will NOT be changed or updated automatically. The default Debit COA Number is only created when a GL Line Item does not exist for an existing Media, Inventory Movement Type, Job Code or Net Sales. Percentage Allocation. The default on every GL Line Item is either 100% or, in the case of Inventory Movements out of inventory, -100%. (This is because of an idiosyncrasy of the Odyssey database. Normally all numbers are stored as positive values, with the Media Type indicating the affect on balancing. Inventory numbers are the only ones where negative numbers are used to record movement out, and need to be reversed since they are posting to a GL Account.) The primary use of this field is to create additional GL Line Items, based on the automatically created ones. For instance, if you wish to automatically impact the pro forma Income Statement with an allocation for employee benefits of 20%, you could create additional GL Line Items for each Job Code, and another for Salaried Labor Cost and make this percentage 20.00%. Then the P&L impact of labor would include your estimated cost of benefits. This is also used on GL Line Item type Net Sales (Franchise Fee). Media GL Line Items The Odyssey software will AUTOMATICALLY create a GL Line Item for each and every media key within the Odyssey Suite s database. The account to debit and the account to credit will be fixed, using the required Chart of Account entries and the associated GL Sections, which in turn link to the GL Account Type. Unless the programmer is reasonably familiar with accounting systems, it is highly recommended that you not change any of the entries for Media GL Line Items. All of the GL Line Items can be deleted, with the exception of the Cash GL Line Item. If a Media GL Line Item is deleted, it will be automatically recreated at the next end of day or the next time any of the GL reports is accessed. All amounts for the media for the past 36 days will be automatically reposted. Inventory Expense GL Line Items The Odyssey software will AUTOMATICALLY create two GL Line Items for each and every Inventory Movement Type. One will be for Food type inventory movements and the other for Non-Food inventory movements. Like the Media GL Line Items, while the Inventory Expense GL Line Item can be deleted, it will be automatically recreated at the next end of day or the next time any of the GL Reports is accessed. All inventory movements for the past 36 days will be automatically reposted. 62 BackOffice Selections Odyssey/BackOffice Suite Programming

63 Labor Expense GL Line Items The Odyssey software will AUTOMATICALLY create one GL Line Item for every Job Code, and a single GL Line Item for all salaried employees, as defined under Employees Rate J/C Definition. The punch information entered at the point-of-sale is used with the GL Line Items for Job Codes. Salaried employees affect the general ledger on a daily basis, 365 days a year, with their yearly salary being divided by 365. Like Media GL Line Items, while the Labor Expense GL Line Item can be deleted, it will be automatically recreated at the end of the day or the next time any of the GL Reports is accessed. All labor information for the past 36 days will be automatically reposted. Net Sales (Franchise Fee) GL Line Item This is a single GL Line Item which uses the Miscellaneous Net Sales figure, as collected at the point-of-sale. The default percentage to apply is 0.00%. Like the Media GL Line Items, while this GL Line Item can be deleted, it will be automatically recreated at the end of the day or the next time any of the GL Reports is accessed. Stored Posting GL Line Item This type of GL Line item is used to impact the Changes In Income Statement and Changes In Balance Sheet reports with figures which are NOT collected by Odyssey. As an example, an operator may wish to generate a pro forma P&L where monthly rent and utilities are reflected. Again, the Odyssey Suite is NOT intended to be a general purpose account system. The Stored Posting GL Line Item is merely intended to assist in presenting a pro forma operating statement. When the Add New icon is clicked, the GL Line Item Number will be automatically generated. The Operator can enter any text desired under GL Line Item Name, e.g. Rent. Use the dropdowns to select the Debit COA Number and the Credit COA Number. The Percentage Allocation will almost invariably be 100%. As an example, using Rent and the default Chart of Accounts, the Debit COA Number would be the expense account Building and Utilities. The Credit COA Number would be the liability account Accounts Payable. There are four additional fields to be programmed with a Stored Posting GL Line Item. Stored Posting Type. This selection is used to indicate the kind of amount being posted. The selection will determine which dates are available under Start Date and End Date. The types are Non-recurring - Each Day (you will need to select both a Start Date and an End Date), Recurring Each Day (you will need to select a Start Date and the End Date will default to 12/31/2099) and Monthly (you will need to select a Start Date and the End Date will default to 12/31/2099). Posting Amount. This is a currency field. For the two daily types, enter the amount to post per day. If you have selected Monthly, enter the monthly amount. The amount posted each day will be the entered amount times 12, divided by 365. Start Date. Use the drop down to select the starting date for this Stored Posting GL Line Item. Items are automatically reposted for up to the last 36 days when entered, if the Start Date is before the current Sales Day. End Date. For the Non-recurring Stored Posting Type, use the drop down to select the End Date for the daily amount to be posted. For a single, one-time expense, this will be the same as the Start Date. You can enter an End Date, even if you have selected Recurring. In actuality, all GL Line Items use the Start Date and End Date. The programming module merely defaults the End Date to 12/31/2099 for Recurring types. You can delete a Stored Posting GL Line Item, and the reports will no longer reflect the amount. If you change the amount, the new amount will be automatically reposted for each of the previous 36 days. Odyssey/BackOffice Suite Programming BackOffice Selections 63

64 Media Types The types of media correspond to how the media is used to balance the calculation of net sales on a balancing or financial report. There are twelve media types within the Odyssey Suite. There is no programming on this screen except for changing the names of the different Media Types. Unless you are changing the names due to a foreign language installation, it is highly recommended that you change nothing on this programming screen. Medias All configuration for medias for both the BackOffice and the point-of-sale is accomplished within this programming section. The options and parameter programming are different for each media type, although there are common attributes for each media. Those common characteristics are programmed on the General Tab, which is covered first. Not all selections under this tab are applicable to all media types. After covering the General Tab, there is a selection covering each separate media type for the applicable programming. The following screen shot shows the top section of media programming. To select a particular media type, use the down arrow to the right of the window displaying All in the screen shot which follows. By default, only medias with the Active flag set to true are displayed in the selection list on the left of the screen. To view all programmed media, uncheck the Active Only flag. Once you have made these two selections, only the medias of the selected type and status will appear in the list on the left. 64 BackOffice Selections Odyssey/BackOffice Suite Programming

65 To select a particular media, merely left click on the Media Number or Media Name within the list. To create a new media: Select the appropriate Media Type for the new media from the dropdown box at the top. From the list of medias on the left, click on the Media Name for a similarly programmed, existing media. Click on the Add icon. All programming, except for the Media Number and Media Name, will be inherited from the selected existing media. You can, of course, change any entries you wish. A Media Number will be assigned as the next highest number. You can use any number you wish, but the Media Number must be unique. Medias with numbers below 100 can not be deleted. You can change the name, and you can change certain parameters and you can make them inactive. To delete a media: Select the appropriate Media Type from the dropdown box at top or simply scroll the list on the left. From the list of medias on the left, click on the Media Name for the media. Click on the Delete Icon. NOTE: You can delete an existing media, with a Media Number greater than 100, only if there is no information related to that media in the active database. If the media is no longer active, then merely uncheck the Active flag for the selected media. Media Programming Selection Methods Like the selection method applicable within POS Terminal Options, once you have created multiple medias, you can change the programming on a selected group at one time. In order to select more than one media at a time for program changes, you must have selected a particular Media Type. The following screenshot illustrates multiple Finalize Media Selected. To select all medias of a particular Media Type, left click on the small gray box immediately to the left of the title Media Number. All medias will be highlighted in blue. With multiple medias selected you MUST left click on the Save Icon for your changes to affect ALL medias. If you merely click on another media in the list after making changes, the only media affected will be the last one selected. In the above screen shot, only the Visa media would be affected. Odyssey/BackOffice Suite Programming BackOffice Selections 65

66 Like the selection method applicable under POS Terminal Options, once you have created multiple medias, you can use the Copy/Paste method to copy the programming from a selected media to multiple other medias. The Copy/Past is only applicable once you have selected a particular Media Type. All programming is copied, except for the Media Number and Media Name. Media Programming General Tab The General Tab is the same for all medias Media Number. A unique number used by the database to identify the media itself. The Media Number for an existing media can only be changed if there is no historical data associated with the media. You CAN NOT change a Media Number which is less than 100. These are fixed. Media Name. This is descriptive text used throughout the BackOffice, on all reports and on the pointof-sale to identify the media. There are thirty characters available. For media which are associated with the point-of-sale, such as payment methods, you may want to limit yourself to ten to sixteen characters, however, if you are using the media in any Popup window. Media Type ID. You can not change the Media Type ID on an existing media. The best way to create a new media is to first select the Media Type you are creating using the pulldown menu at the top of the screen. Next, select an existing media from the list on the left of the screen which is most similar to the media you are creating. When you select the Add icon, the media type is already filled in. Active. A media must be active to appear on various lists, both within the BackOffice and at the point-of-sale. You should use this flag instead of deleting medias which are no longer applicable. This flag is applicable to all media. Certain medias are required and should never be set Inactive. These include 1-Cash, 2-Equivalent Cash, 3-Euro and 215-Service Balance. Others are required in certain configurations, such as 4-Cash Tips. It is a good idea not to make any of the first 100 medias Inactive, but instead use other options to hide them from displaying or prevent them from being used at the point-of-sale. POS Type. This flag allows certain media to still be active, for BackOffice use, but inactive for the point-of-sale software. It is particularly useful for Media Finalize. First, a Media Type must be applicable at the point-of-sale, e.g. Currency Transfer is not a point-of-sale Media Type. In order for the media to display on various lists at the point-of-sale, place a check in this box. Retain Detail. This flag works in conjunction with the Show On Count Screen flag and is only applicable for counted media. A check in this box causes the detailed count entry to be retained. Generally you will NOT want to retain detail, because the details must be moved from one Control Account to another as a set. Bank checks are an example of a possible use for retaining detail. Force Count Time. This flag works in conjunction with the Show On Count Screen flag and is only applicable for counted media. A check in this box causes the software to default to a.00 count. With no check in this box, the software pre-fills the count entry for the media with the theoretical amount. The screen shot which follows shows a count screen where Cash has no check in this box and Bank Checks does have a check. The theoretical amount of Cash has been pre-filled into the Declared, or counted, column to match the Reported, or theoretical, amount. The Declared amount for Bank Checks is left at.00. Affects Over Short. This flag works in conjunction with the Show On Count Screen flag and is only applicable for counted media. All media finalize should have a check in this box. If you are counting coupons programmed as subtotal discounts, you should NOT have a check in this box. 66 BackOffice Selections Odyssey/BackOffice Suite Programming

67 In general, ALL Media Finalize should have a check for Affects Over Short and no other Media Types should have a check. Show On Count Screens. This flag determines whether or not this media will be counted. All Media Finalize should be counted. This flag allows for the counting of media such as discounts or service charges, where there are chits or documents to keep track of. Employee Required. This flag works in conjunction with the Show On Count Screen flag and is only applicable for counted media. A check in this box will provide an additional drop down window on count screens listing all employees and requiring that an employee be selected. It is only applicable if the Retain Detail flag is also set. Open Entry Required. This flag is for future implementation. Do not place a check in the box. Quantity Entry Required. This flag is for future implementation. Do not place a check in the box Print Check At EOS. This flag is evaluated within the POS/2100 software in conjunction with the flag Print Check At EOS programmed under Printer Configuration Terminal Print Options. In many quick service situations, you will program the flag under Terminal Print Options to NOT print a check at the end of sale, however, if a certain media key is used then you WILL want to print a check. This flag is for that purpose and acts as an override on the programming of the Terminal Print Options flag. Examples are for discount media or certain finalize/payment media. ISO Currency Code. This entry is for future implementation. Manager Required. This entry is for use in conjunction with the point-of-sale software. A check in this box causes the POS/2100 to check the table programmed under Staff POS Operators under the Manager Settings tab. If the current POS Operator does not have the permission to use the media, the software will require the entry of an access number for an operator who does have the permission set. The screen shot below illustrates which medias are affected by this flag. Reason Code Required. This entry is for use in conjunction with the point-of-sale software. A check in this box causes the POS/2100 to force the selection of a Reason Code when a particular media is used at the point of sale. Generally this flag might be set for Voids or Refunds. This flag operates independently of the Manager Required flag. Media Programming Finalize Media Finalize media represent payment methods such as cash, credit card, bank check or house charge. There are two programming tabs for finalize media in addition to the General Tab. All entries programmed on these two tabs pertain to operation at the point-of-sale. Media 1 is fixed in all Odyssey software as the local currency. There are various points in the software where such a default assumption is required. Media 2 is fixed in all Odyssey software as Equivalent Cash. The Odyssey software uses this default finalize media when balancing foreign currency. It is used to hold the equivalent in local currency for the foreign payment amount. The default database contains a finalize media for every credit card type, so it is unlikely you will need to create any new credit card media. Uncheck the Active Only box to view all existing finalize media prior to creating a new one. Odyssey/BackOffice Suite Programming BackOffice Selections 67

68 Finalize Media Options Tab Tip Media ID. Every finalize media must have a linked Tip Media ID. This works in conjunction with the flag on this same tab Change To Tips and defines which Tip/Gratuity media collects such automatic tips. The drop down will only show Tip/Gratuity media. The default database contains two Tip/Gratuity media, Media 4 and Media 72. Change Media. Every finalize media must have a linked finalize media from which change is subtracted if this is the last payment media in a transaction, and there is change due the customer. Generally the Change Media will always be Media 1, local currency Cash. The drop down will only show local currency finalize media. Minimum Entry. This is evaluated by the POS/2100 software and is for use in preventing inadvertent erroneous entries. For example, an entry of.01 will force at least some entry. Maximum Entry. This flag is evaluated by the POS/2100 software and is for use in preventing inadvertent erroneous entries. For example, an entry of will disallow any single entry greater than 1, Drawer # If Override. This flag overrides the default cash drawer assignment for the POS Operator, depending on the payment media and is useful in certain applications where a second cash drawer is being used to handle a very commonly accepted foreign currency. Functional as of May Conversion to $. Always leave this entry at a 1. This entry is exclusively for use with Foreign Finalize Media. # of Check Reprints. A 0 is the default. Use of this finalize media may cause multiple receipts to print whenever the check is printed. Set as 1 to print 2 receipts, 2 to print 3 receipts, etc. Walkout Type. This flag is not yet implemented in the point of sale software as of this date. It is intended to finalize transactions where the patron has walked out without paying and automatically forgive any tax calculations on sales. There is a tax exempt button which may be utilized for this purpose on the POS/2100 and should be placed on the Payment Desktop. RA/PO Allowed. This flag works in conjunction with Media Types POS Received On Account and POS Paid Out. Generally, the box is only checked for cash, however, if amounts are being picked up periodically from the cash drawer for finalize media other than cash, this box must be checked. Only finalize media with this box checked will be displayed on the Popup Window (for RA and PO which are not automatically associated with a finalize media) when the RA or PO button is depressed on the POS terminal. Over Tender Allowed. This flag determines whether or not an amount in excess of the current amount due on a transaction may be entered for the finalize media. It is always checked for cash. As an example, if store policy was to not accept Bank Checks in excess of the transaction, this flag would be checked for Bank Checks. For credit card type finalize media, if the environment included tips, you might check this box and also check the flag Change To Tips. Amount Tender Required. This flag determines what happens when the POS Operator simply depresses the finalize media button on the POS Terminal. If you want the software to consider this action as an exact amount tender for the remaining balance due, do not check this box. If you want the software to prompt for an entry of an amount, check this box. With this box checked, the next flag checked by the software will be the Suppress Suggest Tender flag. Open Drawer. This flag determines whether or not the cash drawer should be opened, when the transaction balance is.00 or change is due, if this finalize media was used within the transaction. If this finalize media is being stored in the cash drawer, always check this flag. Change To Tips. The functionality of this flag requires that Over Tender Allowed be checked. If this box is checked, any amounts entered in excess of the amount due will always be considered as a tip. The tip will be associated with the Tip Media ID entered elsewhere on this tab. The tip may also be automatically be considered as paid, using the Tips Paid media programmed on the screen Configure POS System Options Misc. DO NOT SET THIS FLAG IF ENABLE OUTLET POSTING IS SET. If the auto pay tips flag is not set, only these charge tips will appear on the Tip column of employee reports, since these will need to be deducted from payroll. In this mode, with auto tips paid NOT SET, you should also never have any Job Codes set with Prompt For Tip Declaration as true, since the declared tips would also (incorrectly) appear on the employee reports. 68 BackOffice Selections Odyssey/BackOffice Suite Programming

69 Suppress Suggest Tender. This flag requires that the Amount Tender Required flag be checked. If you want the amount entry window on the point-of-sale to pre-fill the exact amount of the remaining balance of the transaction, do not check this box. The operator will then be prompted, but can merely depress the Enter button to confirm an exact tender. With a check in this box, the POS Operator must manually enter the amount being tendered. The POS/2100 software also supports preset amounts and preset finalize media amounts. You can program a button as the entry of for instance. You could next depress any finalize media button on the point-of-sale. You can also program a button as the entry of Cash, or any other finalize media, to quickly enter payments. Display Split. There are two possible entry windows presented when an amount must be entered for a finalize media at the point-of-sale. One merely shows a numeric keypad. The other contains an addition area on the left of the window which shows 1/2, 1/3, 1/4, 1/5 and 1/6 of the total transaction as a preset. This is to aid in split payments. If you want to display the split payment assistance screen with this finalize media, place a check in this box. MPayType. Developed for an international distributor. Applies to payment by cell phone. Finalize Media Authorization Tab Merchant Number. The entry here is only meaningful if you are implementing interactive Internet credit card authorization. If you are implementing a dial up connection for credit card authorization, enter a 1. With Mercury Payment, and interactive Internet credit card authorization, this field is the assigned Merchant Number for the establishment and must be entered for every payment method with a check in the following box, again, only if you are implementing interactive Internet credit card authorization. This field is also required for electronic Gift Cards. NOTE: If Credit Card Authorization is active, the software REQUIRES that some number be entered in this field. For a dial up connection, with a check in the following box, enter a 1. Credit Card Authorization Active. If you are implementing credit card authorization, place a check in this box for every credit card. This flag is ignored if there is no check in the box Credit Card Network Active, programmed under POS System Options Credit Card Options. Prompt for Card. This flag is only evaluated if the previous box is checked. You should place a check in this box if you have one in the previous box. Prompt for Authorization Number. No longer implemented. Do not place a check in this box. Verify Expiration Date. This flag is only evaluated when Credit Card Authorization is Active. You should place a check in this box if it is. Gift Card Type. Set this flag for an electronic Gift Card. A Merchant Number is required. Posting Printer Group. If you want a "posting chit", enter the printer group for the printer. You MUST also have Yes to Account Number Required, probably also with Yes to Override Account# Validation. The chit can be used to manually post the charge to a property management system. Enable Charge Posting. This flag causes the software to attempt to interact with the module WinPost for outlet charge posting. Refer to the immediately following section Interactive Charge Posting. DO NOT SET CHANGE TO TIPS FOR AN OUTLET POSTING MEDIA. Net Charge Posting Total. This flag is only pertinent if the flag Enable Charge Posting is set, and an overtender has been entered, presumably Cash. The net amount, i.e. amount entered less change, is sent to the property management system, not the entered amount. Account Number Required. This field works in conjunction with the following flag. Generally, it is used to enable the built-in AccountCharge capability of Odyssey and the POS/2100. However, if there is no check in the following box, it will merely force the entry of a sixteen character reference field when the finalizing media is utilized. (Must be Yes to enable Posting Printer Group.) Override Account# Validation. This field works in conjunction with the previous flag. For interactive AccountCharge media, check the previous box and DO NOT place a check in this box. To merely require the entry of a reference number, check the previous box and this one. Odyssey/BackOffice Suite Programming BackOffice Selections 69

70 Print Voucher. Always set this flag if you have checked the box Credit Card Authorization Active. Apply Partial Credit. This field is applicable if you have checked Account Number Required and have NOT checked Override Account# Validation or if you have checked Gift Card Type. It is for use both with the built-in AccountCharge features and egiftcards. If there is available credit on an account or an egiftcard, but the amount being posted is in excess of this amount, a check in the box will take all you can from the account or card without further prompt to the operator, bringing the available credit to $.00. You should check this box for AccountCharge and egiftcard finalizing media. Interactive Charge Posting The Odyssey POS/2100 can interact with property management systems through the software module WinPost. A separate Help File is available from the Help selection above the tool bar on Odyssey MWS. WinPost is designed to operate, constantly, on the BackOffice Server. It processes request files from the POS terminals, and transmits posting and inquiry requests over an RS-232C The Posting Path for the POS/2100 is fixed as G:\POST. Each and every POS Item in the database must be linked to one, and only one, of four Type 4 Itemizers. Typically, these itemizers are Itemizer 1 through 4. An individual POS Item can only be linked to one Type 4 Itemizer, however, the programming module will not REQUIRE that a particular POS Item be linked to any. Certain Property Management Systems, particularly Fidelio, require that the posted amount balance to the sum of transmitted itemizers, plus tax, plus service charges, plus gratuities minus discounts. In order for a Finalize Media to interact properly with WinPost, the following settings are recommended: It is good practice to program a "backup" Media in the event the posting interface is down. This backup Media can be set with a Posting Printer Group. This would designate a printer placed at the Front Desk/Reception area which would print a chit for manual posting to the guest folio. In addition to a Room Charge Payment Finalize Media, another button may be placed on any Sales Desktop of the POS/2100, Button Type Outlet Inquiry. This button allows the POS Operator to confirm the status of a room or a guest, depending on the Property Management System. Media Programming Foreign Finalize Media The same as a finalize media, but with an exchange rate to the local currency. For balancing purposes, the Odyssey Suite maintains a separate figure for each media, the cash equivalent amount. For payments in the local currency, the two amounts are equal. For foreign finalizing medias, the cash equivalent is the amount in the local currency which was subtracted from the transaction when the foreign amount was entered. Foreign Finalize Media Options Tab Change Media.. Always select local currency Cash. Conversion To $. Enter the conversion from the foreign media to the local currency. For example, the approximate exchange rate from Canadian $ to US$ is 1.65 Canadian $ to 1 US$. You would enter 1.65 in this field. 70 BackOffice Selections Odyssey/BackOffice Suite Programming

71 Foreign Finalize Media Authorization Tab None of the selections on this tab are applicable to foreign finalize media. Media Programming Transfer Currency In/Out Media This is the most complicated media type within the Odyssey Suite. These medias are only used by the Back Office module, Odyssey MWS, and can not be used at the point-of-sale. First, the transfer may be set to apply only to a particular finalize media. Next, the transfer must be from one control account to another. For example, a drawer pickup operation is the transfer of cash from the POS Operator to the Back Office. Most of the transfer medias in the standard configuration are set to be of one particular media from one particular control account to another. The most common general use of Transfer Currency media will be to automatically move media finalize amounts from the Petty Cash Control Account (at the end of the day) to either the Bank, or to a Processed Control Account, so that Petty Cash starts at $.00 (or your default amount) for the next day. There are a large number of pre-programmed Transfer Currency In/Out media in the default database. Very few of these should require any modification and great care should be taken prior to any editing of these existing media. Transfer Currency In/Out Existing Default Medias Media Media 18 Media 19 Media 21 Media 23 Media 24 Media 26 Media 27 Description Account Payment Check. Do not edit this media, except for changing the name for translation purposes. Account Payment Other. Do not edit this media, except for changing the name for translation purposes Bank Deposit. Do not edit this media, except for either changing the name for translation purposes or making the media Inactive. Bank Funds Received. Do not edit this media, except for either changing the name for translation purposes or making the media Inactive. Drawer Bank. Do not edit this media, except for either changing the name for translation, making the media inactive or changing the amount. This Transfer Media defines the Drawer Bank for POS Operators of Type 1. To disable the automatic prompting at POS Operator Count time (for Operators of Type 1), set the transfer amount to $0.00. Local Purchase Non-Inventory. Do not edit this media, except for either changing the name for translation purposes or making the media Inactive. Local Purchase Inventory. Do not edit this media, except for either changing the name for translation purposes or making the media Inactive. Note that Media 27 is fixed as the Local Purchase Inventory Transfer In/Out Media in the Defaults section of Odyssey MWS. Use of this Transfer media will automatically prompt the operator to select the inventory items being purchased locally in order to properly increment the on-hand inventory. Media 28 Media 49 Media Description Cash To Lock Box. Do not edit this media, except for either changing the name for translation purposes or making the media Inactive. Drawer Pull. Do not edit this media, except for either changing the name for translation. (You can uncheck Single Media Transfer to record ANY Media Finalize, rather than only Cash.) Odyssey/BackOffice Suite Programming BackOffice Selections 71

72 Note that Media 49 is used in conjunction with the flag Auto Count Operators programmed in Back Office Options. When funds are automatically moved from a POS Operator to the Petty Cash Account, it is this Transfer In/Out Media which accounts for the funds movement. Leave the single media of cash set as is. When the Transfer Currency Media is used to auto transfer funds, the software ignores this setting and moves each and every different finalizing media using this Transfer. The media can still be selected, with a default of Cash, to record a drawer pickup of Cash. You can also uncheck the flag under Single Media to prompt the operator for the finalizing media being moved from a POS Operator to Petty Cash. Media Media 60 Media 63 Media 64 Media 70 Media 71 Description Checks To Lock Box. Do not edit this media, except for either changing the name for translation purposes or making the media Inactive. Drawer Bank Type 2. Do not edit this media, except for either changing the name for translation, making the media inactive or changing the amount. This Transfer Media defines the Drawer Bank for POS Operators of type 2. To disable the automatic prompting at POS Operator Count time (for Operators of Type 2), set the transfer amount to $0.00. Drawer Bank Type 3. Do not edit this media, except for either changing the name for translation, making the media inactive or changing the amount. This Transfer Media defines the Drawer Bank for POS Operators of type 3. To disable the automatic prompting at POS Operator Count time (for Operators of Type 3), set the transfer amount to $0.00. Post House Account Debits. Do not edit this media, except for either changing the name for translation purposes or making the media Inactive. House Charge EOD. Do not edit this media, except for either changing the name for translation purposes or making the media Inactive. Transfer Currency In/Out Options Tab Auto From Control Account ID. Place a check mark in this box if the source of the funds being moved is always the same Control Account. There are many default Transfer Currency In/Out medias which move funds out of Petty Cash at the end of day. All of these have a check in this box. The drop down list immediately below the check box allows a selection of the fixed source. With no check, the Transfer Screen in Odyssey MWS will allow you to select a source of funds. Auto To Control Account ID. Place a check mark in this box if the destination of the funds being moved is always the same Control Account. As an example, there are many default Currency In/Out medias which move funds from Petty Cash to a generic Processed Control Account. All of these have a check in this box. The drop down list immediately below the check box allows a selection of the fixed destination. With no check, the Transfer Screen in Odyssey MWS will allow you to select a destination for the funds. List From Control Account Type. This box provides a way of screening the source Control Accounts and is only functional if there is NO CHECK in the Auto From Control Account ID. An example is Media 70 (Post House Account Debits), where the only listed Control Accounts will be Control Accounts of type House Account Debits. Note there are three default Control Accounts for use with the Transfer In/Out media Post House Account Debits. List To Control Account Type. This box provides a way of screening the destination Control Accounts and is only functional if there is NO CHECK in the Auto To Control Account ID. An example is Media 26 (Local Purchase Non-Inventory), where the only listed Control Accounts will be Control Accounts of type Categorized Expense. Note there are three default Control Accounts for use with the Transfer In/Out media Local Purchase Non-Inventory. Single Media Transfer. Place a check mark in this box if the media being transferred is always the same. To automatically move funds at the end of day, you will need a separate Transfer In/Out Media for each and every finalizing media. The transfer will always be an automatic from Petty Cash to a designated account and there will be a check mark in this box. The dropdown list 72 BackOffice Selections Odyssey/BackOffice Suite Programming

73 immediately below the check box allows a selection of finalize media. With no check, the Transfer Screen in Odyssey MWS will allow you to select from a list of all finalizing media. An example of the use with NO CHECK is Media 19 (Account Payment Other), where the operator is selecting from a list of all media. Note that Control Account is fixed as the House Account Control Account. When using a Transfer In/Out media which has Control Account as either the Auto To or Auto From Control Account, the other side of the transfer will always present a list of all internal House Accounts from which to choose. Fixed Amount. This entry allows the amount of the transfer to be fixed. An example are the three default Transfer In/Out Medias 24, 63 and 64. These medias are used for the automatic drawer bank for a POS Operator. Note: To eliminate the prompting at POS Operator Count time relating to the automatic drawer bank, set the Fixed Amount for medias 24, 63 and 64 to $0.00 Minimum Entry. This field is not used. Leave the field at the default of $0.00. Maximum Entry. This field is not used. Leave the field at the default of $0.00. Amount Required. A check in this box will require the entry of an amount to be transferred from the Transfer Screen of Odyssey MWS. With no check in this box, the entire amount of the finalizing media will be entered in the amount entry field. Note that this amount can be changed by the User. An exception is the default Media 28, Cash To Lock Box. This media interacts with the field programmed in Back Office Options Petty Cash Bank. With no check in the box, the amount automatically entered in the transfer field will be the total amount in Petty Cash, less the Petty Cash Bank. To automatically prompt essentially all Cash, you must place an entry of $0.01 in the Petty Cash Bank field of Back Office Options. List In Drop Down. A check in this box causes the Transfer In/Out media to list in the dropdown of transfers in the Transfer Screen of Odyssey MWS. Without a check, the transfer will not list. This is a useful function in screening out Transfer In/Out medias which are automatically performed. Local Inventory Purchase. This flag is only checked on a single default Transfer In/Out media, Media 27. A check in this box causes Odyssey MWS to provide an additional screen after the transfer is entered and forces the Operator to select the inventory items being purchased locally in order to properly increment the on-hand count of inventory items. Tax Entry Local Purchase. This flag causes Odyssey MWS to provide two additional entries in conjunction with the transfer to allow for the entry of any tax amount included in local purchases. The amount charged to inventory is net of the tax amounts. Show On Deposit Screen. This flag is set on three default Transfer In/Out medias, 24, 28 and 29 and is for use exclusively with the separate creation of drop numbers to track deposits. Print Always. A check in this box causes the Odyssey MWS software to always print a Transfer Sheet when this Transfer In/Out media is utilized. Auto Transfer Allowed. This flag is set for Transfer In/Out medias which are automatically generated during the end of day process. This flag is ignored unless the Transfer In/Out Media has an automatic To Control Account, an automatic From Control Account and also has a Single Media setting. The Transfer In/Out media may or may not be shown on the drop down list depending on the flag List In Drop Down. However, typically you would NOT show these media, since they are intended for automatic use at the end of day. Print Paid Out Counter. This field is not used. Media Programming POS Paid Out Media This is actually a subset of the Transfer Currency media type only for use at the point-of-sale. Unlike the Back Office Transfers, there is no accountability for the destination of the funds. At the point-of-sale, a Paid Out is a separate transaction. A Paid Out may NOT be recorded during a sales transaction. Odyssey/BackOffice Suite Programming BackOffice Selections 73

74 NOTE: When a Paid Out operation is performed, the Cover Count (Guest Check Count) is automatically set to zero, regardless of any Covers entry which has been made. POS Paid Out General Tab POS Type. You MUST place a check in this box in order to utilize this media at the point of sale. POS Paid Out Options Tab None of the selections under Auto Transfer of Control Account are meaningful for this type of media. An amount entered as a Paid Out at the point-of-sale is simply no longer in the cash drawer for counting purposes. Odyssey MWS does not account for the use of these funds. A drawer pickup SHOULD be performed in the Back Office in order to not lose control over the funds, because the result of a POS Paid Out is that the finalizing media is no longer in the store. If you are using a POS Paid Out at the point-of-sale to pick up funds, you should establish a method of re-entering the funds in the Back Office, either at the time you are counting POS Operators or when you are counting Petty Cash. This would be a Transfer In/Out media where the source of funds is an external Control Account, and the destination is either the POS Operator or Petty Cash. Depending on what kinds of media finalizing you are recording drawer pickups for using a POS Paid Out media, you can either use a Single Media (for Cash) or select the media. This transfer will bring the funds back into the store for accountability. Note that in order for a finalizing media to be eligible to be Paid Out, you must have a check mark in the box under Finalize Media Options, RA/PO Allowed. Single Media Transfer. A check in this box causes the POS/2100 to always record the selected finalize media as the media being transferred, generally Cash. With no check, the POS/2100 will provide a list of all eligible finalize media during the paid out operation. Fixed Amount. This can be set for a fixed amount for a standard amount paid out. Amount Required. While you should place a check in this box, the POS/2100 will always require an amount to be entered for a Paid Out operation if the amount is not fixed. Print Paid Out Counter. Place a check in this box to cause a separate Paid Out receipt to be printed at the point-of-sale. None of the other selections under POS Paid Out Options are applicable for this media type. Media Programming POS Paid In (ROA) Media This is actually a subset of the Transfer Currency media type only for use at the point-of-sale. The media is used to record finalize media placed in the cash drawer for reasons other than the sale of menu items. Another way of recording this kind of transaction at the point-of-sale is to use a Service media. A service media may be used in the middle of a sales transaction to record funds in the cash drawer that do not relate to the sale of menu items. Unlike the Back Office Transfers, there is no accountability for the source of the funds, other than using multiple medias. NOTE: When a Paid In (ROA) operation is performed, the Cover Count (Guest Check Count) is automatically set to zero, regardless of any Covers entry which has been made. POS Paid In (ROA) General Tab POS Type. You MUST place a check in this box in order to utilize this media at the point of sale. POS Paid In (ROA) Options Tab The applicable selections are identical to the media POS Paid Out. 74 BackOffice Selections Odyssey/BackOffice Suite Programming

75 Media Programming Service Charge Media This media is used to record an amount which will be collected from the customer at the point-of-sale representing something other than a menu item. At the point-of-sale, there may be a separate collection of service items, which are linked for balancing purposes to a service charge media. Typical uses for service items might include newspapers, cigarettes or a delivery fee. A service charge can only be removed in the service round in which it is added, and then, only with a current items only type item void media. Service Charge General Tab POS Type. You MUST place a check in this box in order to utilize this media at the point of sale. Service Charge Options Tab Amount / Percent. For a dollar amount service charge, enter the amount. For a percentage service charge, enter the percentage. This entry works in conjunction with the following entry, Manual Override. Dollar Amount Entry. If this is a dollar amount service charge, place a check in this box. Leave the box unchecked for percentage service charges. Manual Override. Place a check in this box to allow the POS Operator to enter an open dollar amount or to enter the percentage manually. With no check, the amount or the percentage will be fixed as the amount entered above under Amount / Percent. Amount Required. This field is not used. A service charge will always require than an amount, either dollar or percentage, be entered. Account Credit Type. A check in this box indicates that this service charge is used to place a credit on a House Account using the AccountCharge module. With a check in this box, after the entry of the amount, the POS Operator is prompted to select the account receiving the credit. Operationally, the service charge establishes an amount to be collected from the customer. The amount entered for the service charge is posted as a credit to the entered account only after payment is made in full at the point-of-sale. Refer to the later section Accepting AccountCharge Payments at the POS. Gift Card Type. This flag is mutually exclusive with the flag Account Credit Type. Check this box if this service charge is being used either to issue a new egift Card or to add value to an existing egift Card. Gift Card Issue. You must have a separate service charge media for the function of issuing a new egift Card and for adding value to an existing egift Card. Check this box for the service charge media which will be used to issue new egift Cards. Leave the box unchecked for the service charge media which will be used to add value. Print Voucher. Set this flag to issue a custom voucher receipt for the acceptance of payment against an egift Card. (This flag is not implemented as of the initial release of egift Card in October of 2004.) Merchant Number. This is the same field which is required for Internet credit card authorization. It will generally be the same value as that entered for credit card finalizing media. Itemizer Calculation Type. A previous section described in full detail Itemizer Calculation types. Itemizer calculation types are most frequently used in conjunction with discount functions. In general, you will select Itemizer Calculation Type Distribute Each Pro Rata, unless the Service Charge is tabxable. For taxable service charges, set the Itemizer Calculation Type to Net All, Entire Amount. Apply on Discount Amount. This flag only applies to percentage service charges. Check this flag if a percentage service charge should be applied after discounts have been taken. With no check, the percentage service charge will be calculated on the gross amount. Include Tax Amount. This flag only applies to percentage service charges. Check this flag if tax amounts should be included in the amount to which a percentage service charge is applied. Odyssey/BackOffice Suite Programming BackOffice Selections 75

76 Service Charge Itemizers Tab A percentage service charge is NOT applied to the entire transaction, but rather to the amount collected within an itemizer. If all menu items are to be applicable to a service charge, establish a single Itemizer as Service Charge and link all items to this Itemizer. There are two lists on the Itemizer Tab. The first is Use Itemizer and the second is the Affect Itemizer. For most service charges, the only affected itemizer will the same single itemizer used to calculate the itemizer. To make a service charge taxable, set both the Use and Affect Itemizer for the tax itemizer. Do not set the Affect Itemizer for non-taxable service charges. For taxable service charges, set the Itemizer Calculation Type to Net All, Entire Amount. egift Cards Voiding Sale or Voiding Add Value Selling egift Card (issuing an egift Card) or adding value to an egift Card is handled by a Service Charge type media. The software within the POS/2100 specifically prevents a Closed Check which contains such a Service Charge from being selected for modification. The software within the POS/2100 also specifically prevents such a Service Charge button from being used within either a Void Transaction or a Refund Transaction. Within the active transaction, either type of Service Charge may be corrected. However, once the transaction is closed, neither the sale of nor the adding value to an egift Card can be reversed using the "normal" operations of the POS/2100 Once an egift Card has been initially sold/issued, there is no way the software can be assured that the card has not been used. If the egift Card has been used, it will not be possible to reverse the sale or add value operation. Since the Void Transaction and Refund Transaction operations are "single touch" transactions, they MUST complete once begun. This is why retrieving the transaction from the Closed Check screen is specifically prevented. A void or refund transaction with an egift Card requires the initial transaction number and the initial authorization code. It is unlikely this information will be available to the Operator, or if it is, the entry process of this specific information would be confusing. In any case, neither operation is allowed on a "next business day" basis from any egift Card processing network. This section is included to provide a secure method of voiding either the initial sale or an add value operation using the POS/2100; one which assures balancing and one which assures that the merchant retrieves the funds which are being returned to the customer in the form of cash or other payment media. NOTE: In almost every situation, it will be the general policy of establishments to NOT return funds to a customer once an amount has been added to an egift Card and the transaction has been finalized. The funds behind the egift Card will generally not be in the bank account of the merchant being asked to refund monies. They will either be in a corporate holding account or in another location's account. Reversing either the sale of an egift Card or an add value operation is a two step process. The process requires the use of either an open entry menu item, or a dollar entry service charge media. If both steps are performed properly, there will never be a balance in the open menu item or the service charge button used in this process. The first step removes the value from the card. Begin a transaction. Touch either the open entry menu item or the dollar entry service charge button. When prompted, enter the amount to be removed from the egift Card. Finalize the transaction using the egift Card finalizing media. The amount has been removed from the card and the funds will be transferred into the merchant's account. The second step refunds payment to the customer. Begin a Void Transaction. Touch either the open entry menu item of the dollar entry service charge button. When prompted, enter the amount to be returned to the customer. Finalize the transaction using either the Cash finalizing media or other payment method being returned to the customer. The amount in cash has now been removed from the cash in drawer total and can be tendered to the customer. If refund is by credit card, then the amount will be a debit to the merchant's account and placed as a credit on the customer's statement. 76 BackOffice Selections Odyssey/BackOffice Suite Programming

77 The net effect of the two operations is a zero balance in either the open menu item or dollar entry service charge, a deposit to the merchant's account from the holding account behind the egift Card and a reduction in cash in the drawer or a debit on the merchant's account to cover the credit card refund. Media Programming Gift Certificate Accountability This section documents a custom programming configuration to maintain accountability for Gift Certificates which are dispensed from a corporate location and secured at the restaurant in a Gift Certificate box prior to sale to the customer. The configuration utilizes a Control Account for the Gift Certificate Box, a Control Account for Corporate, a Transfer Currency media to move the Gift Certificates from Corporate to the Gift Certificate Box, a Transfer Currency media to move the Gift Certificates from the POS Operator directly to the Gift Certificate Box and a Service Charge Media to record the sale of the Gift Certificates at the point-of-sale. The normal use for a Transfer Currency media is to maintain accountability for Finalize media, e.g. Cash, Bank Checks, credit cards or Gift Certificates accepted as payment. The Transfer Currency media provides a means of maintaining accountability as funds are moved from the cash drawer to Petty Cash and then to the bank. The offset to funds coming into the location is the movement of inventory out of the location through recording the sale of a Menu Item. A Gift Certificate sale, however, is the movement of a media, the Gift Certificates, out of the location, offset by the movement of Finalize media into the store. When a Gift Certificate is sold, the accountability requires that Gift Certificates on hand be decremented rather incremented, so the transfer requires a sign reversal on the count and the amount. The Service Charge media to record Gift Certificate Sales should be programmed exactly as shown below: Using a Service Charge media allows Gift Certificate Sales to be recorded during a transaction. The amount due from the customer will include both menu items sold and the amount charged for the Gift Certificate. The transaction can be finalized using any Finalize Media, just like any transaction. Although Affects Over/Short is set as Yes, the Service Charge does not really affect Over/Short. Although Show On Count Screens is set as Yes, the Service Charge WILL NOT show on the POS Operator Count Screen. It is this unique setting of these two flags, along with the No for Force Count Time that causes the special handling of this media (a sign reversal) in conjunction with a Transfer Currency media which has this Service charge as the Single Media Transfer. The Gift Certificate Box should be established as a Control Account of Type 2 (Back Office) with a Yes on the flag Affects Balance under Control Account programming. Corporate should be established as a Control Account of Type 6, with a Yes on the flag Allow External Transfer and a No on the flag Internal Control Account in Control Account Type programming. Odyssey/BackOffice Suite Programming BackOffice Selections 77

78 The Transfer Currency media Receive GC To Sell used to record incoming Gift Certificates for sale should be identical to Media 23, Bank Funds Received, except programmed as shown below: The Transfer Currency media which will cause the on-hand quantity of Gift Certificate Sales to decrement should be programmed exactly as shown below: Although the Auto From Control Account ID is shown as the Transfer Account (Control Account 20000, also generally named Petty Cash), the transfer of Gift Certificate Sales is directly from the POS Operator to the Gift Certificate Box. The special handling is invoked because the Single Media Transfer is a Service Charge, programmed identically to the screen shot previously shown. In operation, when Gift Certificates are received at the location, they are recorded using the Transfer Media Receive GC To Sell. This causes a positive amount to be placed in the Gift Certificate Box. When the sale of a Gift Certificate is recorded at the point-of-sale, the amount will not show on the POS Operator Count screen. When the POS Operator s count is accepted, prior to the Finalize Media being moved to the Transfer Account (Petty Cash), the amount recorded through the Service Charge Media Gift Certificate Sales will be automatically SUBTRACTED from the amount in the Gift Certificate Box, not transferred. This functionality to maintain Gift Certificate accountability is also operable if the flag Auto Count Operators is set under Back Office Options programming. The finalize media for all POS Operators are automatically moved from the operator to the Transfer Account, and the special handling Service Charge amounts for Gift Certificate Sales are automatically SUBTRACTED from the amount in the Gift Certificate Box. 78 BackOffice Selections Odyssey/BackOffice Suite Programming

79 Media Programming Tip/Gratuity Media This media is very similar to a service charge in that it records amounts collected from the customer at the point-of-sale for something other than a menu item, however in this special case, the collected funds will typically be immediately given to the POS Operator, the server. Tip/Gratuity General Tab POS Type. You MUST place a check in this box in order to utilize this media at the point of sale. Tip/Gratuity Options Tab Amount / Percent. For a dollar amount tip/gratuity, enter the amount. For a percentage tip/gratuity, enter the percentage. This entry works in conjunction with the following entry, Manual Override. Extraction Percentage. This entry only works if you have the flag in POS System Options Miscellaneous Options Media Options for Automatically Pay Tips checked. It is for use with credit card tips, where the establishment is paying a credit card fee, normally around 2%. The establishment will NOT be reimbursed for all credit card tips, but only for 98% of the tips. If you wish to pay POS Operators only the amount you are being reimbursed, enter the credit card fee being paid. Note that while this is legal in most states, it is a requirement that the establishment notify Servers (POS Operators) in advance of this practice. Dollar Amount Entry. If this is a dollar amount tip/gratuity, place a check in this box. Leave the box unchecked for percentage tip/gratuity types. Manual Override. Place a check in this box to allow the POS Operator to enter an open dollar amount or to enter the percentage manually. With no check, the amount or the percentage will be fixed as the amount entered above under Amount / Percent. Amount Required. This field is not used. A tip/gratuity will always require than an amount, either dollar or percentage, be entered. Itemizer Calculation Type. A previous section described in full detail Itemizer Calculation types. Itemizer calculation types are most frequently used in conjunction with discount functions. In general, you will always select an Itemizer Calculation Type of Distribute Each Pro Rata. Apply Tip on Discount Amount. Check this flag if a percentage tip should be applied after discounts have been taken. With no check, the percentage tip will be calculated on the gross amount. Include Tax Amount. Check this flag if tax amounts should be included in the amount to which a percentage tip is applied. Tip/Gratuity Itemizers Tab A percentage tip/gratuity is NOT applied to the entire transaction, but rather to the amount collected within an itemizer. If all menu items are to be applicable to a percentage tip/gratuity, establish a single Itemizer as Tip Applicable and link all items to this Itemizer. There are two lists on the Itemizer Tab. The first is Use Itemizer. This defines the itemizer(s) to which a percentage tip/gratuity is applied. The second is the Affect Itemizer. This defines which itemizers have the calculated tip/gratuity added to. For most tip/gratuity types, the only affected itemizer will the same single itemizer used to calculate the itemizer. Odyssey/BackOffice Suite Programming BackOffice Selections 79

80 Media Programming Tips Paid Media This media is similar to a Transfer Currency media type. It is used to record the movement of funds, initially received as a tip or gratuity, from the cash drawer to the POS Operator or the server. It balances funds collected from the customer against funds which will be transferred to petty cash as an offset, since these funds were given to the POS Operator, the server. The most common implementation is to set the flag Automatically Pay Tips to a Yes in POS System Options Miscellaneous Options Media Options. This eliminates the requirement for a Manager to enter the amount of the tips actually paid to a Server. If the establishment is implementing some form of tip sharing, then the process of actually allocating tip amounts to the various Servers (POS Operators) must be performed manually. This would be a Back Office task. The amount of the tip for each Employee can be entered, via the Punch Edit screen in Odyssey MWS. The funds should be moved separately, as one amount, using a Back Office Transfer Currency In/Out, from Petty Cash to any external Control Account. Note: You can not place a Tips Paid Media button on a Sales Desktop of the Odyssey POS/2100. Media Programming Void Item Media This media is used to account for the removal of an item from the receipt or the guest check. It is a control total, since the menu item was never actually given to the customer and the ingredients of its recipe are not consumed from inventory on-hand. There are two kinds of Void Item Medias, those that apply to an item before it has been requisitioned and those that apply an item after it is requisitioned. In most sit-down dining situations, a void after an item has been sent to the kitchen is actually a Waste. The difference is that the ingredients have been consumed in a Waste operation, whereas with a Void the item was never prepared. There is a similar by-transaction operation, where a Void Item corresponds to an Overring Transaction and a Waste Item corresponds to a Refund Transaction. Void Item General Tab POS Type. You MUST place a check in this box in order to utilize this media at the point of sale. Current Items Only. Place a check mark here for an Error Correct type of button at the point-ofsale. The correcting function may only be applied to items which have not been sent to the kitchen. With no check mark here, items which have already been sent may be corrected. A requisition chit will be generated, hopefully to notify the kitchen to NOT prepare the item. Reference Number Required. Place a check mark here if you wish to enter up to a sixteen character alphanumeric reference to further identify the type of void being performed. Void Media Existing Default Media A void item with a check in Current Items Only is programmed in the default database as Media 13. A void item with no check in Current Items Only is programmed in the default database as Media 14. The check can not be changed in either of these media, as both are required media. Media 13 Media 14 Media Description Error Correct. Can only be used for current items. Void. Can be used with either current or prior items. However, when used on prior items, the actual media number contained in Transaction Details will be Media 13. A void on prior items represents an amount already included in the Grand Control Total, while an amount in the Error Correct media represents an amount NOT included in the Grand Control Total. 80 BackOffice Selections Odyssey/BackOffice Suite Programming

81 Media Programming Line Item Discount Media This media is used to record a reduction in price of a single menu item. The Odyssey BackOffice suite reports this amount on a by item basis. Operationally at the point-of-sale, the POS Operator selects one or more items, then applies either a fixed amount or percentage discount to the particular items on a one time basis. An item may only have a single Line Item Discount applied at the point-of-sale. Line Item Discounts are also used as coupons and there is significant programmability in this section relating to coupons. Line Item Discount General Tab POS Type. You MUST place a check in this box in order to utilize this media at the point of sale. Line Item Discount Options Tab Amount / Percent. Enter either the fixed dollar amount of the line item discount (e.g. $1.00 off) or the percentage of the line item discount. Dollar Amount Entry. Place a check mark here if the discount is a fixed dollar amount. Leave no check mark for percentage discounts. Manual Override. Place a check mark here if the POS Operator has the ability to enter an amount which is different from the entry in Amount / Percent. Reference Number Required. Place a check here to require the entry of a sixteen character reference number/text when this discount is used at the point-of-sale. Apply To Lowest Price. This flag only pertains to coupons. If multiple items fit the coupon criteria, check this flag to discount the lowest priced item. With no check, the highest priced item will be used. In a Combo Type coupon, if this flag is set, the grouping of items resulting in the lowest pre coupon price will be collected together and used in the combo group. With no check, the grouping of items resulting in the highest pre coupon price will be used. Coupon Type. A check mark here indicates this line item discount is a coupon. It is mutually exclusive with Combo Type. Combo Type. This is a specific type of coupon, one where a collection of items represents a combo which will be discounted so that the combination of items is charged to the customer at a specific price. It is mutually exclusive with Coupon Type. Coupon Application Attempts. Number of times to repetitively attempt to apply this line item discount. Only applies to Coupons, so either ComboType or Coupon Type = Y. Sort of an "automatic re-touch" of the line item discount (which is a coupon type discount) button. Campaign Coupon/Voucher. This section of programming pertains to a custom development and is documented in a user-specific white paper. The section pertains to both combo and coupon types. Line Item Discount Coupon Setup Tab See the separate section Media Programming Standard Coupons. Line Item Discount Combo Type See the separate section Media Programming Combo Type Coupons. Line Item Discount Itemizers Tab This provides a screening mechanism for Line Item Discounts. Only items which belong to itemizers which have a check mark on this tab may have a line item discount applied to them. For instance, if an item belonged to the taxable AND the food AND the service charge itemizers, these three itemizers would have to be selected for the line item discount. When programming coupons, it is easiest to check all itemizers. Since your main criteria is established on the Coupon tab, there is no need for itemizer screening also. Odyssey/BackOffice Suite Programming BackOffice Selections 81

82 Media Programming Standard Coupons Standard coupons are implemented as a type of line item discount. The third tab under Media Programming Line Item Discount Media provides a mechanism for configuring a line item discount as a standard coupon. Programming on this tab is only valid if there is a check mark next to Coupon Type on the Options tab. Fixed Amount Coupon. Only valid (programmable) if there is also a check mark next to Dollar Amount Entry for the line item discount. A check mark here indicates that the Amount / Percent field represents a dollar amount to charge for the item, rather than a discount amount to apply to the item. Price Level. This is used to allow coupons to apply only to a specific POS Price level. A 0 indicates that the coupon is valid at all price levels, while a number 1 to 6 specifies the only price level for which the coupon is valid. The section of the tab under Evaluation Criteria indicates the required item or category of items which must be present on the guest check in order for the coupon to be valid. Evaluation Criteria Category. If the evaluation is based on Category, use the dropdown list to select the Category in which the item(s) which must be present are located. Evaluation Coupon Group. As an alternative to menu items in a specific Category, you can use Coupon Menu Item Groups to collect menu items from any number of categories. For example, you may have multiple entrée categories, but collect all entrees in a single group. Use the dropdown list to select the Coupon Group. NOTE: Coupon Groups must be programmed first. Evaluation Criteria Menu Item. Use the dropdown list to select a specific Product Number (Menu Item) which must be present. Leave the field blank for any item in the selected Category or Coupon Group. Evaluation Criteria Minimum Item Count. This specifies the minimum number of the criteria item(s) which must be present. As an example, Buy 2 Sandwiches, Get a Free Drink would have a Minimum Count of 2. The section of the tab under Apply Coupon To indicates to which item the coupon will be applied if the criteria above are met. Apply Coupon To Category. If you are applying the coupon to a Category, use the dropdown list to select the Category in which the item(s) to which the coupon applies are located. Apply Coupon Group. If you are applying the coupon to a Coupon Group, use the dropdown list to select the Coupon Group in which the item(s) to which the coupon applies are located. Apply To Menu Item. Use the dropdown list to select a specific Product Number (Menu Item) to which the coupon applies. Leave a blank field for the Menu Item to apply the coupon to any item in the selected Category or Coupon Group. How Many To Discount. If the criteria menu item count is greater than 1, it is possible that the number of menu items you wish to discount will also be greater than 1. For example, a coupon Two Entrees for $20 would use a fixed amount coupon to charge $ It would require two menu items from either a Category containing all entrees or a Coupon Menu Group which collected all entrée. The number to discount would be 2, resulting in each being $10.00 and satisfying the coupon criteria. NOTE: There is a setting under the Options tab for Coupon Application Attempts. This setting defines the number of times to repetitively attempt to apply a coupon. Sort of an "automatic re-touch" of the discount button. Standard Coupon Evaluation Rules Determining which menu items to use in a coupon is complicated. First, we will illustrate the complications. Then we will list the rules used in evaluating coupons and consuming menu items as having been used in a coupon. 82 BackOffice Selections Odyssey/BackOffice Suite Programming

83 The first rule is that a menu item can only be used once. It gets complicated if the menu items in the apply group are a subset of the menu items in the criteria group. Say you have a coupon for buy any two pizzas get a free standard pizza. You set the coupon to apply to the lowest priced pizza, since you want to give away the least amount of revenue. When you do that, the menu items in the criteria are checked off as used starting with the most expensive first. But this still leaves open the possibility for three menu items to be used in the coupon. For example, lets use four menu items with prices as follows: Item Item Item Item Say all these items are in the criteria group. Say Item1 and Item2 are in the apply group. For our coupon above, it is easy to see that Item1 should be free. If we normally use items in the criteria group as most expensive first, we would flag Item3 and Item4 as used. When we were done, we would have flagged three items as used in a coupon and we could not use a second coupon. So, once we have determined which menu items to which we will apply the coupon, if they are in the criteria group, we use them first, regardless of price. This would mean that we would flag first Item1 as used, since it received the discount and then Item4, since it was the most expensive. This leaves Item2 and Item3 as not used and the coupon could then be used a second time. Unfortunately, this does not always work. Say it is Item1 and Item4 in the apply group. Item2 and Item3 are in the criteria group but not in the apply group. Again, Item1 will get the discount since it is the least expensive. Again it will be flagged first as used. Then we will flag Item4 as used, since it is the most expensive. Unfortunately we can not use the coupon again because, alas, we have used both items in our apply group. So, we must use a different criteria for flagging the items which are in the criteria group. In the above example, of course Item1 gets the discount and it is flagged first. But instead of looking first to the most expensive, we sort the items twice. First we look at items in the criteria group which are not in the apply group and we sort them by price. Then we look at items which are in the apply group and we sort them by price. So the highest price item which is not in the apply group is Item3. When we are done now, it is Item1 flagged since it was discounted and Item3 flagged as the first item in the list now sorted twice. The coupon can be used again because both Item2 and Item4 remain as unused. The effect of this double sort is to preserve menu items in the apply category, regardless of their price, for multiple coupons. The coupon evaluation rules are therefore: Sort the apply items top to bottom depending on whether the highest priced or lowest priced item is discounted first. Make sure you have sufficient number of apply items to satisfy the coupon. Sort the criteria items first into two groups, with the items which are not in the apply group first. Sort each group of criteria items in the reverse order of the apply items, i.e. if you discount the lowest priced item first, sort the criteria items with highest priced at the top. Make sure you have sufficient number of criteria items to satisfy the coupon. Apply the coupon to the item(s) in the apply group. Flag any items in the criteria group which you just discounted. Flag the number of items necessary in the criteria group to satisfy the coupon. Media Programming Combo Coupons Combo type coupons are implemented as a type of line item discount. The fourth tab under Media Programming Line Item Discount Media provides a mechanism for configuring a line item discount as a standard coupon. Programming on this tab is only valid for the following programming on the Options tab. Odyssey/BackOffice Suite Programming BackOffice Selections 83

84 Dollar Amount Entry True A non-zero amount in the Amount field Combo Type True. There can be up to five Coupon Groups associated with a Combo Coupon. An example of its use would be Get an appetizer, an Entrée and a dessert for $ You would place all the applicable appetizers in one Coupon Group, all the applicable entrées in another and the same for the desserts. When the coupon button is depressed, the software will search out the combination. If it finds each item, it will discount each item on a pro rata basis (based on the sum of the charged prices) so that the sum of the items equals the programmed amount to charge. The flag Apply To Lowest price on the Options tab dictates which items will be used if multiple items fit the combo coupon criteria. The entry Coupon Application Attempts can be used to cause the software to continue to search for qualifying combinations and create more combos up to either the limit of items on the check or the number of application attempts. Media Programming Subtotal Item Discount Media For balancing purposes, this media is exactly the same as a line item discount. The only difference in the media types is the access methodology on the point-of-sale terminal. Subtotal item discounts are initiated by the POS Operator to apply to a group of items rather than a single item. In addition, a Subtotal Item Discount is a continuing discount, from service round to service round to the next. Once applied, all subsequent items, which qualify for the discount through their itemizer association, are discounted. If you desire to be able to report pure net sales by either Category or Department, you should always implement subtotal discounts as Subtotal Item Discounts, and not Dollar Amount Subtotal Discounts (calculated as a percentage) because the discount percentage is applied to each line item individually rather than to the amount in the itemizer. In VAT situations, you should also always implement Subtotal Item Discounts in order to properly show Sales less VAT on the Financial Report. In rare instances, this can result in a somewhat strange presentation. For example, a 10% discount on an item costing $0.15 is $.02 because the discount is rounded up. On a transaction with ten such items, the total 10% discount will be $.20 and not $.15, because the discount percentage is applied separately to each and every line item which belongs to the itemizer against which the discount is applied. Subtotal Item Discount Item General Tab POS Type. You MUST place a check in this box in order to utilize this media at the point of sale. Subtotal Item Discount Options Tab Amount / Percent. The only type of Subtotal Item Discount is a percentage discount. Enter percentage of the subtotal item discount. As noted below, there is a special type of subtotal item discount when the percentage is 100%. Manual Override. Place a check mark here if the POS Operator has the ability to enter a percentage amount which is different from the entry in Amount / Percent. Max Percent. For percentage entry, with manual override allowed, this is the max percentage which can be entered. For example, if you wish to allow POS Operators to grant any percentage from 1% to 50%, but no higher, enter 50% Max Amount. This is used to enter the maximum dollar amount of the percentage discount. For instance, you want a 50% discount, but in no case more than $5.00, enter Another use of this is for dollar amounts off, where the discount amount is accurately allocated on an item basis. For example, use this for a $2.00 off coupon. Enter the percentage as 100%, and the maximum amount as For amounts less than $2.00 the coupon results in no amount due and for amounts greater than $2,00 it acts as a dollar amount off. Another special case is a 100% discount with a max amount 84 BackOffice Selections Odyssey/BackOffice Suite Programming

85 of $0.00. In this case, the POS software will prompt for a dollar amount off. The resulting amount will be properly allocated to each item, so the VAT on the Financial Report will be correct. Reference Number Required. Place a check here to require the entry of a sixteen character reference number/text when this discount is used at the point-of-sale. Use a 100% discount for dollar amounts off. Set the max amount to the dollar off amount. For a special case, where the POS Operator will enter the dollar amount off, set the percentage to 100% and set the max amount to $0.00. The POS software will prompt for the dollar amount off. Subtotal Item Discount Itemizers Tab This provides a screening mechanism for Subtotal Item Discounts. Only items which belong to itemizers which have a check mark on this tab will have the subtotal line item discount applied to them. Media Programming Dollar Subtotal Discount Media This media is used to record a discount which is not applied on a menu item by menu item basis. As such, there is no record within detailed menu item reporting of dollar amount subtotal discounts taken. Dollar Subtotal Discount General Tab POS Type. You MUST place a check in this box in order to utilize this media at the point of sale. Dollar Subtotal Discount Options Tab Amount / Percent. For a dollar amount discount, enter the amount. For a percentage discount, enter the percentage. This entry works in conjunction with the following entry, Manual Override. Dollar Amount Entry. If this is a dollar amount discount, place a check in this box. Leave the box unchecked for percentage discounts. Manual Override. Place a check in this box to allow the POS Operator to enter an open dollar amount or to enter the percentage manually. With no check, the amount or the percentage will be fixed as the amount entered above under Amount / Percent. Upper Limit Type. This field pertains to Dollar Amount Entry type discounts. A check in this box will cause the POS/2100 software to apply the Dollar Amount Discount up to the amount of the transaction. For example, if the transaction total was $8.95, and a $10.00 Dollar Amount Subtotal Discount was entered, the transaction balance would be zero. With no check in this box, the discount would not be applied, because the fixed dollar amount exceeds the transaction total. Itemizer Calculation Type. A previous section described in full detail Itemizer Calculation types. Itemizer calculation types are most frequently used in conjunction with discount functions. In general, you will always select an Itemizer Calculation Type of Distribute Each Pro Rata. Reference Number Required. Place a check here to require the entry of a sixteen character reference number/text when this discount is used at the point-of-sale. Dollar Subtotal Discount Itemizers Tab This tab is identical to the one displayed for Service Charges. In general, with a Distribute Each Pro Rata Itemizer Calculation Type, the Use Itemizers collect items which are discountable. The Net itemizers include all that also have the Use box checked and, in addition, affect those itemizers which are collecting taxable and non-taxable amounts. Media Programming Refund Transaction Media This media is used to provide a control total against menu items and payments when giving a customer money back. Menu items entered during a refund transaction do not reduce the number of menu items sold, and do not replenish inventory items which are a part of the recipe for the menu item. The menu item was presumably already counted as sold in a previous transaction, and the inventory items would have been Odyssey/BackOffice Suite Programming BackOffice Selections 85

86 depleted in that previous transaction. Odyssey will report net sales quantities as sold minus refund, however for inventory depletion, it will use the gross quantity sold. The button Refund Transaction which is placed on a Sales Desktop of a POS/2100 can be used in two ways. If a transaction is first selected from the Closed Check display, then a single depression of the Refund Transaction button will reverse the entire transaction. The software will create a new check number for this transaction. This is extremely useful if the transaction being refunded occurred during the same Sales Day. If the transaction occurred during a previous Sales Day, the transaction will not be displayed on the Closed Check Screen. A transaction may be begun with a single depression of the Refund Transaction button. In such a transaction, all quantities and dollar amounts are a reverse sign. Media Programming Waste Item Media This media is used as a control total when removing an item from the receipt or guest check whose ingredients, for inventory purposes, will be counted as consumed. An example in a table service situation would be removing an item from the guest check which was already prepared, but for which the customer will not be charged, because it was mis-prepared or was the wrong item and can not be served to another customer. The Waste Item Media operates identically at the point-of-sale to a Void Item Media. The only difference is the impact on inventory items consumed. Presumably the item being wasted was previously entered, and previously decremented inventory. An item which is wasted therefore has no affect on inventory. A Void Item essentially adds the ingredients back into inventory. Note: Using a Waste Item Media on items which have not been requisitioned has the effect of operating as a Finished Goods Waste operation at the point-of-sale. The POS Operator enters all the items to be wasted, selects all and then depresses Waste which brings the amount to be collected from the customer to $0.00. Operationally, this transaction will require the entry of 0 as the Cash collected by the POS Operator. Waste Item Existing Default Medias The following medias are part of the default database and are used by Odyssey Inventory. They should not be edited at all, other than for possible translation purposes. Media Media 45 Media 46 Media 47 Media 47 Description Prep Waste. Do not edit this media, except for changing the name for translation purposes. Back Office Wastes. Do not edit this media, except for changing the name for translation purposes. Back Office Prep Waste. Do not edit this media, except for changing the name for translation purposes. Inventory Recipe Consumption. Do not edit this media, except for changing the name for translation purposes. Media Programming Overring Transaction Media This media is used to provide a control total against menu items and payments which were simply misentered originally. Menu items entered within an overring transaction net the count on the number sold. The inventory item depletion, based on the recipe, is reversed. An overring transaction has the same effect on balancing as if you performed a void operation on each and every menu item while the transaction was still being entered at the point-of-sale. Odyssey will report net sales quantities as sold minus the overrings and will use this net amount for inventory depletion. 86 BackOffice Selections Odyssey/BackOffice Suite Programming

87 The button Overring Transaction which is placed on a Sales Desktop of a POS/2100 can be used in two ways. If a transaction is first selected from the Closed Check display, then a single depression of the Overring Transaction button will reverse the entire transaction. The software will create a new check number for this transaction. This is extremely useful if the transaction being refunded occurred during the same Sales Day. If the transaction occurred during a previous Sales Day, the transaction will not be displayed on the Closed Check Screen. A transaction may be begun with a single depression of the Overring Transaction button. In such a transaction, all quantities and dollar amounts are a reverse sign. Note: Given that the operation of an Overring Transaction is essentially the sale never happened, IT IS HIGHLY UNLIKELY that the function should be performed after a Sales Day is closed. Media Programming Tax / Add On Media This media is used to record taxes calculated as an additional amount to the menu item price, the typical tax situation in the U.S. Amounts collected from the customer will be the sum of menu item amounts and taxes added on. Note: In order for the Tax / Add On to actually collect the taxable amount and the amount of the tax, the media must be properly linked to an Itemizer programmed as Itemizer Type 1 or 2. Media Programming VAT Media This media is used to record taxes which are already included in the menu item price, the typical tax situation in the U.K. and Europe. Amounts collected from the customer will only be the sum of menu item amounts, which already include the value added tax. This type of media is also used to collect reporting information onto the Financial, POS Operator and other balancing reports in conjunction with Itemizer Types 4 and 5. Note: In order for the VAT to actually collect the amount including tax and the amount of the tax, the media must be properly linked to an Itemizer programmed as Itemizer Type 3. To collect reporting information, the VAT media must be linked to an Itemizer programmed as Itemizer Type 4 or 5. Media Count Units Media Count Units are used for two purposes within the Odyssey Suite. The first is to provide an alternative method of counting cash. An example would be a roll of quarters. This Media Count Unit is linked to the finalize media cash and has an equivalent amount of $ This kind of Media Count Unit does not cause a detail to be retained, and should always be linked to the Petty Cash control account. This is merely a counting aid. Once the roll of quarters has been counted, it is indistinguishable from a reporting standpoint from ten one-dollar bills or two five-dollar bills. A second use of a Media Count Unit is to retain a full detail of a particular media. An example would be bank checks. This Media Count Unit is linked to the finalize media bank checks and has no equivalent amount. The amount is entered on the count screen. The Media Count Unit is linked to a special Control Account, Bank Checks B/O. A similar use of Media Count Units would be to retain detail tracking of travel vouchers which are tendered in specific, defined amounts. The Control Account to which the Media Count Unit should be linked is the destination Control Account, from a Transfer Currency In/Out Media, for the media from Petty Cash. Media Count Number. This merely an identifying number for the Media Count Unit. The convention followed in the default database is to use the media number followed by a three digit number beginning at 001. Media Count Descriptor. This is the name which will appear on the count screen, such as Quarters, Roll. Odyssey/BackOffice Suite Programming BackOffice Selections 87

88 Media Number. This is the finalize media with which the Media Count Unit is associated. Use the dropdown to select the finalize media by name. Media Amount. If this is a non-detail Media Count Unit, enter the equivalent amount of the unit. For example, for Quarters, Roll enter 10, since there are 40 quarters in a roll, representing $ Control Account Number. As a convention, select the Petty Cash Account (Control Account 20000) for entries which have a Media Amount. For a Media Amount of $0.00, select the destination Control Account, from a Transfer Currency In/Out Media, for the media when is moves from Petty Cash. Show On Safe Count. Place a check mark if you wish this Media Count Unit to appear when counting the Safe. As an example, you might wish Quarters, Roll to appear when counting the safe but not when counting POS Operators. Show On POS Count. Place a check mark if you wish this Media Count Unit to appear when counting POS Operators. Unless you are storing the full detail of a particular media, DO NOT create a Count Unit with an amount of zero. This will prevent the full amount of the media from displaying on the Transfer Screen, regardless of the setting of the flag Amount Required on the Options Tab of the Media Type Transfer Currency In/Out. Scanned Coupon Definitions This feature is new with the May of 2009 release. It provides the ability to scan a UPC-A barcode and process a coupon. Since there is a link to an existing Media, there will also be a counter behind the scanned coupon and it will appear on the Financial Report and all POS Operator Reports. By scanning a barcode, the merchant assures that a valid discount is being given. Of course, coupons must be counted and tracked if this control is desired. Coupon Number. This is the bar coded number on the coupon. You can use a scanner to make this entry. The leading ~ character (if implemented on the scanner) will not be entered into this field. This number may also be entered on the standard numeric pad of the POS2100. For manual entry, a Button Type Enter is required to follow the entry of the UPC number. Media Name. This is a dropdown selection of all valid media which can be scanned, which is any discount media, including Dollar Subtotal Discounts, Line Item Discounts and Subtotal Item Discounts. Coupon Start Date. This is the first date when the discount media can be scanned. The coupon will be valid on this date. (NOTE: If you place this discount media on a Sales Desktop, this Start Date will not be enforced. Enforcement on the date range is only applicable when the discount media is scanned.) Coupon End Date. This is the last date when the discount media can be scanned. The coupon will be valid on this date. (NOTE: If you place this discount media on a Sales Desktop, this Start Date will not be enforced. Enforcement on the date range is only applicable when the discount media is scanned.) Coupon Menu Groups Coupon Menu Groups are used in creating Line Item Discounts which are programmed as coupons. Prior to the April, 2010 release, if you wanted a coupon to apply to a group if menu items, your only selection was a Category. If you had used separate categories for hot sandwiches and cold sandwiches, as an example, you could not create a coupon which applied to all sandwiches. Coupon Menu Groups are simply groupings of menu items which are either requisite criteria in order for a coupon to be applied or the group of menu items to which the coupon is applied. 88 BackOffice Selections Odyssey/BackOffice Suite Programming

89 Media List Files Media List Files provides a way of grouping medias so that they may be presented in a single Popup window at the point-of-sale terminal. The POS/2100 programming allows for all media of a single type to be presented as a Popup Window, however, it is often desirable to only display certain of the same type of media on a Popup. As an example, you might want to display only the Credit Card Finalizing Medias, not any others, or to show Foreign Finalize Media on the same Popup window as local currency Finalize Media. Media List Files General Tab Media List File Number. This merely an identifying number for the List File itself. Media List File Name. This name is only used at the point-of-sale to select from the list of all available Media List Files when programming a button on a point-of-sale Desktop. Media List Files List Details Tab Use the Add icon to display a list of available media. The displayed window may be sorted to show all medias or only medias of a particular type. To add multiple medias at one time, left click on the gray square at the far left of the displayed window to highlight each row being added in blue. From this screen, click the OK button to add the details. Medias are listed in the sequence number of the record number entered here. To sort the media within the Popup window, create sequential numbers in the order in which you want the medias to display at the pointof-sale. Itemizer Types This discussion is included in advance of Media Programming as a requisite background in order to program discount, service charge and tip/gratuity medias. However, all Itemizer Types except Type 0 require a link to a media, so you will have to go back and forth between Media Programming and Itemizer Programming. The medias which Itemizer Types require are either an Add-On Tax or a VAT Tax. POSItems are configured to either add-to any of sixteen itemizer totals or not. The results of a discount, tip or service charge operation is also configured to both use the amount in a particular itemizer and then add or subtract the result of the calculation or entry to the itemizer during the transaction. Taxes are calculated on a single itemizer, whatever has been accumulated after all sales and discounts during a particular transaction. There six types of itemizers and they are listed in the table below. Itemizer types 0 and 4 are for use in calculating service charges and discounts. You should, as a general rule, NEVER use any other type of itemizer when calculating service charges and discounts in order to avoid adding too great a service charge or providing too great a discount. Itemizer types 1 and 2 are basically the same, except type 2 uses a table for U.S. taxes rather than a flat percentage. Itemizer type 3 is for use in situations where the tax amount is included in the price charged for items, typically in Value Added Tax situations. Itemizer type 4 is a special kind of calculating and reporting itemizer. An item can only belong to one, and only one, type 4 itemizer. This is useful where you want to separate all items into categories such as Food, Beverage, Liquor and Miscellaneous. Itemizer type 5 is basically the same as Itemizer type 4, except that this kind of itemizer can not be used in a calculation for a service charge or a discount. Itemizer Type Itemizer Type Name Description 0 Calculate Only Use this type of itemizer for most service charge and discounts being calculated. 1 Add On Tax % Use this type of itemizer to calculate U.S. add-on taxes as a percentage. Odyssey/BackOffice Suite Programming BackOffice Selections 89

90 Itemizer Type Itemizer Type Name Description 2 Add On Tax Table Use this type of itemizer to calculate U.S. add-on taxes through an entered tax table. 3 VAT - Tax Use this type of itemizer in situations where the tax is included as part of the item price. 4 Calculate and Report Use this type of itemizer to segregate items into distinct, separate groups. These groups are mutually exclusive, i.e. an item can belong to one and only one type 4 itemizer. This kind of itemizer can also be used to calculate service charge and discount amounts. 5 Reporting Only This type of itemizer is used to segregate items into distinct groups but not for any service charge or discount calculations. Itemizer Calculation Types This discussion is included in advance of Media Programming as a requisite background in order to program discount, service charge and tip/gratuity medias. The principal use of Itemizer Calculation Types is to properly distribute the results of calculations to handle all the various tax scenarios in the United States. There is a selection under Back Office for Itemizer Calculation Types, but this selection merely allows the User to change the names of the types for translation purposes. The number of Itemizer Calculation types is fixed and there are five types. Calculation Type Calculation Type Name Description 1 Distribute Both Pro Rata Take the amount of the service charge or discount and distribute it on a pro rata basis amongst all itemizers with a Y for Affect. 2 Distribute Each Pro Rata Take the amount of the service charge or discount and distribute it on a pro rata basis amongst all itemizers with a Y for Use and a Y in Affect. Then take the amount of the service charge or discount and distribute it on a Pro rata basis amongst all itemizers with a N for Use and a Y in Affect. 3 Net All, Entire Amount Add/subtract the entire amount of the service charge or discount to/from each itemizer with a Y in Affect 4 Distribute Use, Net Affect Take the amount of the service charge or discount and distribute it on a pro rata basis amongst all itemizers with a Y for Use and a Y for affect. Then add/subtract the entire amount of the service charge or discount to/from each itemizer with a N for Use and a Y for affect. 5 Net Use, Distribute Affect Add/subtract the entire amount of the service charge or discount to/from each itemizer with a Y for Use and a Y for Affect. Then take the amount of the service charge or discount and distribute it on a pro rata basis amongst all itemizers with a N for Use and a Y for Affect. The general default would be Type 1. This assumes that the itemizers being affected are mutually exclusive or are on a one-to-one basis with the itemizers being used in the calculation. 90 BackOffice Selections Odyssey/BackOffice Suite Programming

91 Type 2 is used where some items are taxable and others are non-taxable. If all items were either discountable, or service chargeable, you would set up a single itemizer to track all items and use this itemizer as the Use itemizer. You would have three itemizers listed as Net, the itemizer used for the calculation and the two separate taxable and non-taxable itemizers. The single Use itemizer is netted by the discount. As a second pass, the amount of the discount is then netted from the two separate taxable and non-taxable itemizers, on a pro rata basis. Itemizer Programming This discussion is included in advance of Media Programming as a requisite background in order to program discount, service charge and tip/gratuity medias. You must program itemizers prior to using them for purposes of calculating discounts or service charges. However, all Itemizer Types except Type 0 require a link to a media, so you will have to go back and forth between Media Programming and Itemizer Programming. The medias which Itemizer Types require are either an Add-On Tax or a VAT Tax. Itemizer Programming General Tab Itemizer ID. There are sixteen itemizers. The number of itemizers is not programmable and this field is merely a reference designation for each itemizer. Itemizer Name. Use this field to provide an appropriate descriptor for your use of this specific itemizer. Examples of Type 0 might be Service Charge Applies or Discountable. Examples of Type 1 or Type 2 Itemizers might be State Tax or NJ State Tax. Examples of Type 4 itemizers might be Food, Beverage, etc. Itemizer Type. Use the dropdown provided to select one of the six types of itemizers applicable to your use of this itemizer. Media Number. All Itemizer Types except Type 0 must be associated with a Media. The Media with which the Itemizers are associated are either an Add-On Tax Media (for Types 1 and 2) or a VAT Media (for Types 3, 4 and 5). For Types 1, 2 and 3, both the amount of the collected (or extracted) tax and the amounts to which the tax rate was applied (taxable) will be collected and reported on the Financial Report and all other balancing reports. For types 4 and 5, the total amount collected in the itemizer will be reported. Percent. For all itemizer types other than Type 0, a percentage amount is required. For all taxes (Types 1, 2 and 3), enter the tax rate percentage amount. For Types 4 and 5, the percentage is set by the programming software to be 100%. Suppress Print. This option is only applicable to Itemizer Types 3 and 4. A check here will suppress the printing of the Itemizer Name and the collected amount at the bottom of the receipt/guest check. Odyssey/BackOffice Suite Programming BackOffice Selections 91

92 Itemizer Programming Tax Table This table is used exclusively with Itemizer Type 2, U.S. Add-On Taxes calculated through a tax table. Many states and localities use tables to calculate tax, not a straight percentage. All of these tax rate tables have a "repeat" cycle. Unfortunately, the "repeat cycle" is not always readily apparent, and must be determined by the programmer prior to entering the table into Odyssey programming. The "repeat" cycle will always sum to an even multiple of $1.00, since the table is merely determining the "breaks" at which the tax charged will occur. The following table illustrates a 7% tax rate table, and the method of determining the repeat cycle. Purchase Amount Tax Increment to Program Increment #.00 to N/A N/A.11 to ($.11 - $.00) 1.22 to ($.22 - $.11) 2.36 to ($.36 - $.22) 3.51 to ($.51 - $.36) 4 Start Cycle.65 to ($.65 - $.51) 5.79 to ($.79 - $.65) 6.93 to ($.93 - $.79) to ($ $.93) to ($ $1.08) to ($ $1.22) 10 End Cycle 1.51 to ($ $1.36) Start 2 nd Cycle 1.65 to ($ $1.51) 1.79 to ($ $1.64) 1.93 to ($ $1.79) 2.08 to ($ $1.93) 2.22 to ($ $2.08) 2.36 to ($ $2.22) End 2 nd Cycle The first two columns and the from-to dollar amounts in column three are a partial reproduction of a 7% tax table. It merely shows what tax to charge based on the transaction amount. The bold number in column 3 is a calculation we have made and illustrated. It shows the incremental amount of a transaction when an extra penny tax is charged. It is this incremental amount that is entered into the itemizer programming, and which produces a "repeat" cycle. The fourth column is merely a sequential numbering of the increments which we will use when programming the tax table into the terminal. In the previous table, the "repeat" cycle begins at increment 4, when there is a $.15 increment in a transaction for an extra $.01 tax. The cycle is seven entries in length, and the entries are Note that these seven increment add to $1.00. Note that the seven increments following increment 10 (which are not programmed into the terminal since it would be "repetitious") are identical. The following screen shot illustrates the previous tax table correctly entered onto the Itemizer Programming Tax Table Tab. 92 BackOffice Selections Odyssey/BackOffice Suite Programming

93 If the point-of-sale does not charge tax properly, revisit the programming of your Itemizer and confirm that you have selected Add On Tax Table and not Add On Tax %, that the first entry is not a.00 and that your Start Cycle and End Cycle entries are correct. Itemizer Programming Tax Table Discontinuities A discontinuity in a tax table is an instance where the amount of tax charged changes by more than $.01. As an example, look at the following chart illustrating a 6.50 % tax table. Purchase Amount Tax Increment to Program Increment #.00 to N/A N/A.16 to ($.16 - $.00) to ($.31 - $.16) 3 Start Cycle.47 to ($.47 - $.31) 4.62 to ($.62 - $.47) 5.77 to ($.77 - $.62) 6.93 to ($.93 - $.77) to ($ $.93) to ($ $1.08) to ($ $1.24) to ($ $1.39) to ($ $1.54) to ($ $1.70) to ($ $1.85) to ($ $2.01) 15 End Cycle 2.31 to ($ $2.16) Start 2 nd Cycle 2.47 to ($ $2.31) 2.62 to ($ $2.47) Odyssey/BackOffice Suite Programming BackOffice Selections 93

94 The discontinuity is in the first break. Instead of starting out at $.01 of tax charged, the table starts with $.02 of tax. Note how this is handled in the tax table programming. The first increment of.16 tells the software to start charging tax at $.16 by adding a penny of tax. The next increment of.00 says add another penny of tax immediately, causing the tax charged to start at $.02. A discontinuity elsewhere in a tax table would be programmed the same way. Note that in the table above the sum of the repeat cycle is $2.00 with a Cycle Start Entry of 3 and a Cycle End Entry of 15. Miscellaneous Definition Programming This screen is strictly for use in translation. The Miscellaneous set of totals and counters includes information such as Grand Control Total, Checks Opened and Checks Closed. Unless you are creating a database for a foreign language country, there is no reason to access this programming screen. Track Item Type Programming This screen is strictly for use in translation. The text here is used on the Track Item programming screens within the Reports module. Unless you are creating a database for a foreign language country, there is no reason to access this programming screen. Report Definition Programming This screen is strictly for use in translation. The text here is used on the Batch Report programming screen within the Reports module. Unless you are creating a database for a foreign language country, there is no reason to access this programming screen. 94 BackOffice Selections Odyssey/BackOffice Suite Programming

95 Configure Selections POS Terminal Options The Configure Selection is only available at the top of the screen. It provides an alternative access mechanism. Refer to the section POS Terminal Options for a complete discussion. POS System Options The Configure Selection is only available at the top of the screen. It provides an alternative access mechanism. Refer to the section POS System Options for a complete discussion. Printer Configuration The Configure Selection is only available at the top of the screen. It provides an alternative access mechanism. Refer to the section Printer Configuration for a complete discussion. Odyssey/BackOffice Suite Programming Configure Selections 95

96 POS/2100 Configuration Defining Terminals In The POS Network For a new installation, the first step in configuring the POS network should be to access the selection under POS Terminal Options Posting Configuration. Terminals in the point-of-sale network are assigned a Terminal Descriptor, a Terminal Name and associated with a Revenue Center under the selection POS Terminal Options Posting Configuration. They are also assigned an Active status through this selection. Navigating Within POS/2100 Configuration The configuration of the POS/2100 is accessed from the toolbar command Configure, then selecting POS Configuration. This is also the default window presented when you directly click on the icon corresponding to the Configure command. The following is a screen shot of the primary POS/2100 configuration screen. The screen shot excludes the toolbar and the icons at the top of the main programming screen. The POS/2100 configuration is divided into three principal areas: Printer Configuration. POS System Options. POS Terminal Options. Within each of these three areas are a number of additional selection choices. These additional choices are made by left clicking on an icon, such as the interconnected terminals above the text Posting Configuration, shown at the top on the left of the screen above. 96 POS/2100 Configuration Odyssey/BackOffice Suite Programming

97 The default selection is under POS Terminal Options, and is the selection Transaction Options. It is easy to always tell where you are from the screen presentation. First, the programming window on the right of the above screen shot shows the title bar POS Terminal Options Transaction Options. This corresponds to the display on the left of the screen. The selection bar POS Terminal Options is the one immediately on top of the vertically listed icons. From the previous screen, if you clicked on the bar POS System Options, the bar POS Terminal Options would move underneath the icons, and a new set of icons would appear. The screen shot below shows the result of clicking on the bar POS System Options. Unseen in the screen shot as displayed above is the bar POS Terminal Options. It has moved to the very bottom of the left portion of the screen. Note the title bar on the top of the programming window on the right. The window corresponds to the second icon from the top on the left, for POS System Options Back Office Software. From within any of the three primary areas, to move to your particular selection, merely left click on the icon above the descriptive text. The appropriate programming window for your selection will be displayed on the right of the screen. Odyssey/BackOffice Suite Programming POS/2100 Configuration 97

98 Printer Configuration This selection pertains to traditional, forty-column, point-of-sale printers. The POS/2100 does not support slip printers. Forty-column roll printers can be attached to any active terminal in the point-of-sale network. All receipts and point-of-sale printouts will use these printers in text mode. All print formatting is in forty columns. The report selection available at the point-of-sale requires that the attached printer have the appropriate windows driver installed. Even with the windows driver installed, the receipts and other point-of-sale printouts will utilize the printers in text mode. This significantly increases the speed of print. Printer Operation Software Overview (Technical) Printers can be attached to any terminal in the network. An attached printer must be configured as a Windows printer. The name assigned to each printer in the network must be unique. The driver used for the printer may be the generic text driver, however, a printer which uses the generic text driver can not be used to generate point-of-sale reports. It can be used for printing guest checks and as a remote requisition printer. An Order Video screen requires a separate PC. This separate PC is running under MS-DOS. Every terminal in a POS/2100 network MUST be running WRemote.exe in the background. On satellites, the Comtrex Print Client portion will execute. The Comtrex Print Client provides three functionalities: Interacts with Windows Print Manager to cause print on an attached printer. Interacts with Comtrex Print Server to establish the time on the Server as the time on the PC on which it is executing. Interacts with Comtrex Print Server to notify the local POS Operator that print is being redirected as a result of printer failure relating to a print request generated by the terminal. The printer failure may have occurred on a local printer, or on any printer in the network to which this terminal sent a print job. The Server MUST also be running WRemote.exe in the background. On the Server, the Comtrex Print Server body of software will execute. The Comtrex Print Server provides five functionalities: Manage the G:\ drive and handle the BackUp functionality. Refer to the Odyssey Operations Manual. Interacts with the POS/2100 software to create a print job for any printer in the network. This results in a file being created for Comtrex Print Client. Interacts with the POS/2100 software to create display jobs for any Order Video screens in the network. Interacts with Comtrex Print Client to notify POS Operators, at the terminal from which a print job was requested, that a printer is not operational and that print is being redirected. Interacts with Comtrex Print Client to establish the time on the Server as the time on all POS terminals. Any time the point-of-sale software wants to access a printer, or an Order Video screen, the point-of-sale software either creates a file, if it does not already exist, or appends information to a file in a folder on the Server. The POS/2100 software does NOT directly send information to any printer. The folder where these files are written is the c:\icom\pos2100\remote folder on the Server. Since the c:\icom folder on the Server is always defined as a mapped network drive, the G:\ drive, on each terminal, this is always the G:\POS2100\Remote folder for each terminal. On the Server, the c:\icom folder is always a substituted drive, also the G:\ drive. This is the print spooling folder. The POS/2100 application, when executing on the Server, also writes print requests to the print spooling folder. A request to print a guest check from Terminal 3 will appear as the file CHECK.3 where the terminal number is the file extension. A request to print a remote requisition chit from Terminal 2 will appear as the file ORDER.2. The Comtrex Print Server is constantly monitoring the print spooling folder for print/display requests. When it finds one, it uses the file name to determine if the request is for guest check printing or remote requisitioning, either for a printer or an Order Video. The Comtrex Print Server uses the extension to determine which terminal has requested a print job, then uses the appropriate by-terminal programming information from the database to format a separate file for each printer which will print display information. Requests for display create a file on a by-terminal basis. 98 POS/2100 Configuration Odyssey/BackOffice Suite Programming

99 Information which is to be printed will always be contained in a file in the print spooling folder with the printer name as the file name and txt as the extension. For a printer in the network with the name ReceiptB, all information, both requisition and guest check, to be printed will be contained in the file ReceiptB.txt. Information to be displayed is placed in a different folder on the Server, c:\icom\pos2100\rqv, or G:\POS2100\RQV. This is the video spooling folder. The files containing information to be displayed are created on a by-terminal basis, not a by-order Video screen basis. Information sent from Terminal 2 to be displayed will be contained in the file ORDER.B in the video spooling folder. The extensions will be letters of the alphabet corresponding to numeric terminal numbers, i.e. Terminal 3 is ORDER.C, Terminal 4 is ORDER.D. The monitoring function for information to be displayed is part of the software RQV.EXE, the DOS application which is running on each PC to which an Order Video screen is attached. The Comtrex Print Client is constantly monitoring the print spooling folder looking for files with an extension of.txt and a file name identical to any Windows printers defined in Windows Print Manager for the terminal on which it is executing. Therefore if you have named an attached printer ReceiptB, the Comtrex Print Client software on that terminal is looking for the file ReceiptB.txt. The Comtrex Print Client sends the print job to Windows Print Manager on the local terminal and is also notified by Print Manager if any failure occurs during the print job. Unfortunately, a printer failure CAN NOT be detected for the print job on which it occurs. The notification is an after the fact notification. When the Comtrex Print Client is notified by Windows Print Manger of a failure, it creates a file in the print spooling folder to notify the Comtrex Print Server that a printer is down. The Comtrex Print Server then uses the printer backup information contained in the database to redirect future print jobs. In addition, the Comtrex Print Server will create a separate file in the print spooling folder to notify the terminal from which the print request was generated that a printer failure has occurred. Comtrex Print Server also synchronizes the time for all terminals in the network to be the same as the time on the Server. Once an hour, on the half-hour, a file is created in the print spooling folder as Timeset.1, Timeset.2, Timeset.3, etc. through a file extension of the last active terminal number. This file is read by each Comtrex Print Client, which in turns sets the Windows time on the point-of-sale terminal. Printer Configuration Printer Types You can think of a printer type as a manufacturer and model number for a printer. The printer type TM-T88 IIP is part of the default database. The Windows driver, supplied by Epson, is also included in the installation for the POS/2100. Other manufacturers often support emulation modes for Epson printers. For example, the Star TSP700 has dipswitch settings to emulate the Epson TM-T88 IIP. Not only are the text mode printer codes compatible, but the Windows driver is also compatible. The default database includes Printer Type 2 as VIDEO. You will need a Printer Type if you are using Order Video screens. You should establish the Printer Type with only a Printer Type Number and a Name. While the software will not look at any other settings, you should leave all other settings on both tabs blank. Order Video Screens MUST be named as Video1, Video2 through Video9. This is established under Printer Configuration Printer Definitions. Printer Types General Tab Printer Type Number. Printer types should be listed sequentially. This is merely an indexing number by which the software references the printer type. Name. This should be descriptive of the printer make and model number. Leading Line Feeds. The number of line feeds issued by the point-of-sale software prior to actual printing. This setting will be determined by a combination of user preference and positioning of the print head and the cut or tear bar. Trailing Line Feeds. The number of line feeds issued by the point-of-sale software after printing the trailing logo lines and prior to generating the cut command, if applicable. Open String. The series of HEX characters required to open any cash drawer attached to a printer of this printer type. Odyssey/BackOffice Suite Programming POS/2100 Configuration 99

100 Printer Types Roll Printer Tab Printer Startup. The series of HEX characters used to initialize a printer of this printer type. Print Bitmap. The series of HEX characters used to initiate a printout of a stored bitmap by a printer of this printer type. Loading the bitmap into the printer is a function documented by the printer manufacturer. Red Active. Check the box if printers of this type support red color printing. The following boxes are the series of HEX characters used to cause the next line of text to be printed in red for printers of this printer type. NOTE: Generally, this option is only applicable to impact printers. While some thermal printers do support red printing, this functionality is a function of the heat of the print head and requires special (usually relatively expensive) thermal paper. With thermal printers, you can also substitute inverse printing for red printing to highlight items. Red Disable. The series of HEX characters used to revert to standard print color for printers of this printer type. Cut Active. Check the box if printers of this type support an cutter mechanism. The following boxes are the series of HEX characters used to cause a cut. For printers which support both a full and partial cut, it is recommended to enter the codes applicable to a partial cut. Large Character Codes. The series of HEX characters used to cause the next line of print to be double wide for printers of this printer type. Some printers support not only double wide but double high characters as well. Normal Character Codes. The series of HEX characters used to revert to standard character width and height for printers of this printer type. Printer Types Slip Printer The POS/2100 does not currently support slip printers. Consequently this tab is not available. Printer Configuration Printer Definitions After you define the various types of printers which will be used in your installation, you need to designate names and set certain parameters for the actual printers themselves. In order for a printers to be used in the POS/2100 system, you must define a Windows printer driver for the printer itself. If you will not be taking reports from the point-of-sale software on this printer, you can use the Windows generic text printer driver. When the Add New Printer Windows dialog leads you to the printer name area, you should select a name which relates to the terminal to which the printer will be attached, e.g. Term1Ptr1 or Bar1. The POS/2100 software directs information either to a printer or an Order Video through programming established under POS Terminal Options Sale Types under the Output Groups tab. The name selected for each printer MUST be unique. The printer at the point-of-sale terminal DOES NOT need to be a network printer. It can (and usually SHOULD) be defined as a local printer. Since each printer is a local printer, Windows will allow you to have a printer named Receipt at every point-of-sale terminal in your network, but you MUST make them unique. Refer to the previous section under Printer Configuration - Printer Operation for detailed information. Printer Name. Enter a unique name for each printer in your installation. If you are implementing Order Video Screens, each Order Video screen must be established as a Printer within this programming. There are reserved names for the Order Video screens; Video1, Video2, through Video9. There is not a space between the o and the number. Associate these printers with Printer Type VIDEO established under Printer Configuration Printer Types. Printer Type. Select the appropriate printer manufacturer and model from the drop down list of previously programmed printer types. 100 POS/2100 Configuration Odyssey/BackOffice Suite Programming

101 Network Printer. Put a check mark here if the printer is an EtherNet network printer. Drivers should be loaded on both the primary Server and the BackUp Server. Only the terminal serving as the system server will direct print to this printer. Backup Printer. Generally you should leave this selection blank. This selection pertains to a very specific user configuration where, during peak periods, print is directed to two separate printers. During lull periods, one printer is turned off and all print is automatically redirected to the Backup Printer without operator notification. The drop down list will show a list of all printers already programmed through this selection. If you select one of these printers, when the printer you are defining herein is turned off, all print will be automatically redirected to the Backup Printer without operator notification. Guest Check Printing Use Printer Line 1. Generally you will select this box. There are actually two separate thirty character descriptors, defined on a POS Item basis, used for printing. Checking this box causes the first of the two descriptors to print on guest checks. The formatting on the Guest Check will include as much of the descriptor as will fit in the overall forty-column guest check format. Generally, however, this will be limited to sixteen characters. This is covered in detail in the section POS Item Programming General Tab. Guest Check Printing Use Printer Line 2. Checking this box causes the second of the two POS Item descriptors to print on guest checks. Guest Check Printing Use Both. Checking this box causes two lines to print on the guest check. If the second line in the POS Item is blank, or a null character, then the second line will not print. This functionality is useful in multi-lingual countries. It may also be applicable where a second line of text would provide the patron with more specific information, such as the year for a bottle of wine. Remote Printing Use Printer Line 1. Generally you will select this box. Checking this box causes the first of the two descriptors for a POS Item to print on requisition printers. The format for requisition printing allows for either single wide or double wide printing. For legibility, double wide printing is generally selected. This effectively turns the forty-column printer into a twenty-column printer. With count and indenting, there will generally only be space for between twelve and sixteen characters. However, unsetting the option Truncate Menu Item Print, programmed under Terminal Print Options Remote Tab, allows for a second line of printing to automatically occur if the line of text does not fit on a single line. Remote Printing Use Printer Line 2. Select this box if you have programmed your POS Item database with different descriptors in the second line. Typically this implementation is to assist kitchen personnel who principally speak a language other than the patron s primary language. Remote Printing Use Both. Checking this box causes two lines to print on requisition chits. Depending on the selection of the Truncate Menu Item Print, programmed under Terminal Print Options Remote Tab, a single item might generate as many as four lines of double wide print on a remote requisition chit. Cash Drawer 1 Active. Only set this option if there is a cash drawer attached to this printer. Cash Drawer 2 Active. Only set this option if there are two cash drawers attached to this printer. Combine Output to Single Chit. This option pertains to Remote Printing and the organization of items on a single printed chit. Kitchen personnel are often accustomed to seeing items grouped on a single chit, often with a line of " * " characters used as a separator, by appetizer, main item, dessert, etc. When Fixed Menu Items are included in the order, a Carry Type Fire Message will not suffice to accomplish this organization. The actual structure can be accomplished by directing items to different printer groups, by their type, and then listing the same printer as the only printer in the group itself. However, the "normal" operation in this instance will cause a separate chit to print for each "type" of item. With this flag set as true, when items are sent to this particular printer from different groups, the items will print on a single chit (no auto-cut or trailer lines). This option was specifically requested by U.K. customers. Ticket Printer. This option designates this printer as one where a separate chit will print for each menu item. This functionality is only enabled when the printer is placed in Output Group 8, allowing the printer to be used for standard requisitions when placed in other Output Groups. Odyssey/BackOffice Suite Programming POS/2100 Configuration 101

102 Printer Configuration Terminal Print Options Prior to entering information on this screen, you must first have established the list of active terminals. Terminals in the point-of-sale network are assigned a Terminal Descriptor, a Terminal Name and associated with a Revenue Center under the selection POS Terminal Options Posting Configuration. If you have not already entered this information, you will need to do so before proceeding. Terminal Print Options Overview The logo lines for the receipt, when a guest check prints, the level of detail on the guest check, whether or not requisition video is active, and how information is printed on a remote requisition chit are determined on a byterminal basis. It is probable in most installations that most of these settings will be identical for every terminal. Examples of exceptions would be on which printer point-of-sale reports taken on a particular terminal will print, or printing a check for each service round on a bar terminal but not on a pre-check terminal. Print options are included under the selection bar Printer Configuration for consistency. The selection options, for all terminals or for copying one terminal s settings to one or a group of terminals, is identical in this area of programming to all programming performed under the selection bar POS Terminal Options. These selection options are covered in a separate section, POS Terminal Options Selection Methods. If you are accessing this Help Document for assistance on this area of programming, refer to that section of this manual. Terminal Print Options Check 1 Tab Print On Split Check. When the Create Check button is depressed, from the Split Check Desktop, on the POS/2100, one or more new checks are created by moving items from an existing guest check. Selecting this check box will cause a guest check to be printed for all of the checks, both the original and the newly created ones. Print Full Detail On Send. This flag is used at two points within the POS/2100 software. The POS/2100 has separate button selections for printing and sending a guest check. With this box checked, the Send button functions identically to the Print button. In addition, with this box checked, a receipt is printed when the Store button is depressed, as in a drive through window application. Print Check At EOS. Checking this box will cause a receipt to be printed when paid in full. With no check, a guest check will (generally) not print. See Media Programming General Tab for override. Full Detail Receipt. Normally there is a check in this box. With no check, menu items will not print. Cash Bar Receipt. Place a check here to print a receipt for a "cash bar" operation. With no check in this box, if a guest check has no table and is paid with only cash, no receipt will print at the end of sale, even if the flag "Print Check At EOS" is set. By Seat Print At EOS. A check in this flag will cause the receipt generated at the end of sale (assuming the flag Print Check At EOS is also set) to include a subtotal for each Seat (Tray). Combine Mode. There are two selections available, Exact and Top. This selection pertains to the printed guest check, NOT the presentation of the guest check on the display of the POS/2100. For a discussion of the differences between Exact and Top, see the section POS System Options Desktop Options - POS Displayed Guest Check Combine Modes. Print Name At Top. This pertains only to an entered guest name, as in the TABS mode of the POS/2100. If the box is not checked, the guest name will print at the bottom of the guest check or receipt. The Account Member Name always prints at the bottom of the guest check or receipt. Print Sales Type On Check. A check in this box will cause the Sales Type, e.g. Eat In, Take Out, to print at the top of each guest check or receipt. Suppress Operator Name. A check in this box will prevent the POS Operator s name from printing on the guest check or receipt. Suppress Date Print. A check in this box will prevent the date from printing on the guest check or receipt. Suppress Time Print. A check in this box will prevent the time from printing on the guest check or receipt. Suppress Check Number Print. A check in this box will prevent the check number from printing on the guest check or receipt 102 POS/2100 Configuration Odyssey/BackOffice Suite Programming

103 Suppress Reprint Line. A check in this box will prevent a header line from printing on the guest check indicating that the guest check has been previously printed. Note that if this box is checked, the second print of the guest check/receipt will indicate Reprint Check #2 indicating that this is the second printing of the guest check (the FIRST reprint ), Print Bitmap. A check in this box causes the POS/2100 software to output the characters to print a bitmap at the top of the guest check/receipt. Print Bonus Descriptors. This option only pertains if there are Bonus Descriptors entered which are not blank text. For Bonus Descriptors which are not blank or null text, a check mark here will cause a line to print on the receipt if points have been accumulated. With no check, even if Bonus Descriptors have been entered and points have been accumulated, no line will print. Bonus Descriptors are entered under Printer Configuration System Print Options. Individual POS Items are assigned a number of points to accumulate under List Files - POS Item Programming on the Bonus Points Tab. Print Delivery Info. This option is only checked by the POS2100 software is there is an Account associated with the order and the Sales Type is 3 (reserved for Delivery). If both of these conditions are satisfied, then the Account address, phone number and entered delivery instructions will print at the bottom of the receipt when Button Type - Print and Send is touched on the POS. Print Check Barcode. With a check here, a bar code of the check number will print at the bottom of the receipt or guest check when it is printed. The bar code may be scanned from the Table Desktop to retrieve the check, assuring cashier retrieval of the correct order. Mgr Rqd Reprint Open Check. This pertains to table service applications. With a check mark here, once a check has been printed, the POS Operator must have the Manager flag set in order to print a second copy of the open guest check. Mgr Rqd Reprint Closed Check. This pertains to both table and quick service applications. With a check mark here, the POS Operator must have the Manager flag set in order to access the Closed Check Desktop. Terminal Print Options Check 2 Tab Print Sorted By Dept. A check in this box will sort the items on the guest check or receipt sequentially by the Department Number to which the menu item belongs. Print Qty At Price Line. A check in this box will cause a price to print on the left of the guest check or receipt when multiple identical items have been purchased. Without a check, the quantity appears along with the extension, but the unit price does not print on the guest check or receipt. Print Zero Price Cmts. A check in this box will print all modifying condiments on the guest check, even those with no price. With no check, only modifying condiments with a price will print. A related option under Printer Configuration System Print Options pertains to priced modifiers. The related option causes the price to either print separately or roll up into the price of the main item. Priced modifiers will always print, unless the individual item is set to NEVER print under POS Item Programming Display/Print Tab. Suppress Sign Line. Pertains only to Button Type Tip Lines Print. A check in this box will prevent a signature line from printing. Without a check box, a signature line will print. (A signature line will ALWAYS print immediately under the Account Name and Number, either for the entire transaction or immediately under an individual payment line.) Print Duplicate Voucher. This flag pertains to interactive credit card authorization. A check in this box will cause two copies of the voucher to print, one for the establishment and the other for the patron. NOTE: Normally on a credit card voucher, after a pre-authorization operation, the voucher contains a "Tip" entry line. This "Tip" entry line WILL NOT print unless there is a non-zero value in either "Tip Verification Percentage" or "Pre Authorization Percent" under POS System Options Credit Card Options, on the General Tab. Print Tip Suggestions. A check in this box will cause a two line print on the bottom of a guest check printed for presentation (not a finalized guest check) showing "For Your Convenience" and three Odyssey/BackOffice Suite Programming POS/2100 Configuration 103

104 calculated tip amounts; 15%, 17.5% and 20%. The percentage is applied to the subtotal, before tax and exclusive of any service charges. Print Subtotal. A check in this box will cause a separate subtotal line of all items purchased, exclusive of tax, service charge and prior to discount, to print on the guest check or receipt. A total of the entire transaction amount due will ALWAYS print on the guest check or receipt. One Line Service Charge. This flag is not implemented as of this date. The POS/2100 will always print a single line service charge. Print Combined Tax Line. A check in this box will cause only one line combining all taxes to print on the guest check or receipt. Without a check, if there are multiple tax rates, the tax at each rate will print separately. Print Finalize. This flag is not implemented as of this date. A single line for each entered payment method will always print on the guest check or receipt. Print Change If Zero. A check in this box will cause a separate line indicating an amount of 0.00 as change. Without a check, no line will print if the entered payment is exactly the amount due. Print Foreign Line Active. Place a check mark in this box to print an "alternative payment amount" at the bottom of a guest check when it is printed for presentation. This amount will be the amount due in the designated foreign currency, as selected below. Foreign Media To Print. With a check mark in "Print Foreign Line Active", use the arrow to select from the dropdown list of all foreign finalize medias. Immediately under the bold "TOTAL" line on a guest check printed for presentation an "alternative payment amount" will show which is the amount due in the designated foreign currency. Terminal Print Options Header Tab And Trailer Tab These two sections provide control over the text header and trailer, or logo, lines on a guest check. Both the header and trailer are grouped into five lines, although with bold, or double wide, printing, you can actually print ten lines of header text and ten lines of trailer text. The display presentation for the Header Tab is identical to the presentation for the Trailer Tab. The Check Header programming window is shown in the screen shot below. Placing a check in the Bold box will cause two lines to print, each twenty wide. If you leave the second line blank, only one line will print. Both Line 1 and Line 3 above will print a single line of twenty bold characters. Placing a the slash character ( / ), as shown in the presentation for Line 4 above, will cause a blank line to print. Placing a check in the Red box will cause the selected line to print in red, if the guest check printer supports two color printing. All header and trailer lines are automatically centered by the point-of-sale software. Terminal Print Options Remote Tab This section controls the formatting of information printed on remote requisition printers and displayed on requisition video stations. 104 POS/2100 Configuration Odyssey/BackOffice Suite Programming

105 All printout on requisition printers will be in double wide, bold format, unless the flag Price On Remotes is set. Under the Remote Printers selection: Print Non Default Sales Type. A check in this box will cause the sales type to print when it has been selected by the point-of-sale operator as different from the defined default Sales Type for the terminal. The default Sales Type is established under POS Terminal Options Transaction Options. Print Default Sales Type. A check in this box will cause the default Sales Type to print. To always print the Sales Type, check this box and the above. Print Account On Remote. A check in this box will cause an entered account number to print on the requisition chit. Print Account Description. A check in this box will cause the Customer Name, as entered in the TABS mode at the point-of-sale, to print at the bottom of the remote requisition chit. Price On Remotes. A check in this box will cause print to be the standard size, and the prices of items will also print on requisition chits generated by this terminal. Combine Exact On Remotes. A check in this box will cause main items to consolidate in Exact mode. See the discussion in the section "Desktop Options POS Displayed Guest Check Combine Modes" for a description of Exact vs. Top. With no check, whether or not items are combined, and how, will be determined by the next two flags below. Combine Items On Remotes. A check in this box will cause main items to consolidate on the requisition chits. Combine Cmts On Remotes. A check in this box will cause identical modifiers to also consolidate on the requisition chits. For example, with the above flag set and this flag unset, 2 Burgers both Medium would print as 2 Burgers, 1 Medium, 1 Medium. With this flag set, the print would be 2 Burgers with only Medium underneath, the quantity 2 being implied. Separate Ticket Per Item. This flag is not implemented as of this date. Truncate Menu Item Print. The descriptor field for a POS Item is actually thirty characters long. If you do not place a check here, then requisition chits will print a second, indented, line if the entire descriptor will not fit on the single, double-wide line. A check in this box will print a single line per item, with as much of the text as will fit. Use Cmts Print In Red Flag. If you want all condiments (items in a DCM type List File) to always print in red, do not check this option. If you want to selectively print condiments in red, based on the programming within POS Item Programming Display/Print Tab, check this flag. Weight On Remote. This flag only pertains to items requiring a weight entry, either manual weight entry or from an attached scale. A check causes the net weight to be printed on the remote. Under the Video selection: Order Video Active. A check in this box enables the body of software within the POS/2100 point-ofsale software which provides information to Order Video stations. If your installation does not include any Order Video stations, do not check this box. Order Video On Fly. With Order Video Active, this flag determines if the individual items are sent in a group at the end of the transactions, or are bumped over by the next item entered. A check in this box causes items to be displayed as the next item is entered at the point-of-sale. For example, enter a Hamburger and nothing displays. Enter the second item, then the Hamburger displays. This last item over assures that all modifiers have been added to the item prior to its display on the Order Video station. Some establishments implement a separate menu item with a descriptor of Send to cause the last entered item to sent to the video screen. NOTE: Some installations prefer to create a separate menu item to push the last entered item over. This is very useful at the end of a transaction, just prior to paying. It might also be useful in extremely high volume applications where the POS Operator knows the last entered item is fully described. This dummy item can be programmed to not appear on the OrderVideo or the requisition printer or the receipt through List File programming. To prevent this item from appearing on the Scoreboard, create this dummy menu item as number POS005, or create the item with a name of Send To Video. The name is NOT case sensitive. Odyssey/BackOffice Suite Programming POS/2100 Configuration 105

106 Bottom Video Display. This flag only pertains to output to video stations which are set as Over/Under and divided into two separate sections. Order Video screens are configured through the setting OMode in the file RQV.INI documented in a later section. A check in this box will cause all items sent to such a video screen, from this terminal, to display on the bottom or Under section. No check causes the items to display on the top, or Over, section. Scoreboard Active. This flag pertains to installations with a customer display screen at the drive through point of order. A check in this box causes the POS/2100 terminal to create a separate output file which will be directed to the customer display. Scoreboard#. This flag is not implemented as of this date. It is intended to be implemented if there are multiple customer display screens at a particular establishment. Under the Active Lines of Output Groups selection: The Active Output Group Lines selection pertains to routing of orders to both printers and Order Videos in a quick service restaurant. Each and every POS Item belongs to one or more Output Groups for requisition purposes. The Output Groups to which a POS Item belong are established under POS Item Programming Display/Print Tab. Orders are routed to printers, or Order Videos, through the programming of listed printers or videos in the section POS Terminal Options Sale Types. There are eight Output Groups and each consists of a list of up to four printers or Order Videos. In order to allow orders to be routed to different printers and/or Order Videos, with the same Sale Type, depending of volume, these lines can be masked so that during one period only printers and Order Videos listed on either line 1 or line 2 of the Output Group will display orders from a particular terminal. By selecting a different printer/order Video routing scheme at the point-of-sale terminal, these same items can be sent to a different set of printers and/or Order Videos listed on either line 3 or 4 of each Output Group. The selections below define the default Routing Scheme for each terminal. The default can be toggled between Routing Scheme 1 and Scheme 2 using Popup Order Video Route button on the point-of-sale terminal. If the above discussion is not applicable to an installation, select Routing Scheme 3. Lines 1 and 2 Active. Routing Scheme 1 (Standard). Items will only be printed or displayed on printers and/or Order Videos listed on either line 1 or line 2 of an Output Group to which an item belongs. Any printers or Order Videos listed on lines 3 and 4 will be ignored. Lines 3 and 4 Active. Routing Scheme 2 (Alternate). Items will only be printed or displayed on printers and/or Order Videos listed on either line 3 or line 4 of an Output Group to which an item belongs. Any printers or Order Videos listed on lines 1 and 2 will be ignored. All Lines Active. Routing Scheme 3. Items will be printed or displayed on all printers and Order Video listed on any of the four lines of the Output Group to which an item belongs. Terminal Print Options Output This section pertains to the printer, or requisition, groups established on a by-terminal basis in the section under POS Terminal Options Sale Types. There are eight groups, each of which may contain four printer names or Order Video names. POS items are programmed to be sent to one or more of these Output Groups through the programming in POS Item Programming Display/Print. Guest Check Print Group. This is not programmable and is for display only. Group 1 MUST contain the name of the guest check and receipt printer. EOS Guest Check Group. This is programmable. It to which printer group the guest check will be directed at the end of sale. (Used in conjunction with a fiscal printer to prevent duplicate checks.) Voucher Printer Group. This flag pertains to interactive credit card authorization and defines the printer group where the credit card voucher will print. Clock/Void/Disc Print Group. If printout related to employees clocking in and out is to be printed on a printer other than the guest check and receipt printer, enter the Output Group number containing the name of the printer on which these chits should print. Normally this is Group 1. In Delivery applications, the Transfer chit and the Speed Pay chit will be directed to this Output Group. POS Reports Printer. Enter the name of the printer where reports taken on this terminal should print. This printer name is the Windows printer name, which is the same name entered under Printer Definitions. This printer, however, must not be a generic text printer since the reports are NOT formatted in forty-columns. POS reports have been tested and configured using a TM-T88 IIP printer. 106 POS/2100 Configuration Odyssey/BackOffice Suite Programming

107 Ticket Remote Groups. This entry is not implemented as of this date. Seat Tray Remote Groups. This entry is not implemented as of this date. Bar Code Remote Groups. This entry is not implemented as of this date. Print/Video Output Path. DO NOT CHANGE THIS ENTRY. The entry should ALWAYS be the default of G:\POS2100\Remote. This is a path to a subdirectory/folder on the Server where all information to be printed or displayed is spooled. This is discussed in detail in the section Printer Operation Software Overview (Technical). Russian Fiscal Printer. DO NOT CHECK THIS BOX. Only for Russia. Creating a Closed Check Log With the February of 2007 release, a Check Viewer is included in the Reports module accessed from the BackOffice. The closed check log must be "enabled" as follows: 1. Access Printer Configuration Printer Definitions and create a printer with the name ClosedCheck. The name must be exactly as shown, no spaces. The case does not matter. The printer can be any existing printer type. 2. Do not create a Windows printer ClosedCheck. We are only using this printer name to create a file in folder G:\POS2100\Remote. 3. Access Printer Configuration Terminal Print Options on the Output Tab. The second selection is EOS Guest Check group. Normally this is Output Group 1, since that is where the receipt will default to printing. Change this from Group 1 to an unused Output Group, for example Access POS Terminal Options Sales Types. For each of the Sales Types, put two printers into the formerly unused Output Group, the actual printer and your new printer, ClosedCheck. When the Sales Day is closed, the BackOffice will look for the file ClosedCheck.txt which will have been created for each transaction. The software will move this file to the folder G:\ClosedCheck, rename the file using a convention and then delete the file ClosedCheck.txt. As an illustration of the convention, the file CC_1_2_ TXT is the renamed ClosedCheck.txt from Store Number 1 for Sales Day 2 which was February 14, Since the file is a text file, there is no limit on the number of days for retention of these Closed Checks. To view the closed checks for a particular sales day, open the Reports Module and select as shown below. When the Check Viewer presents, click on the folder in the top left of the screen. This will show the contents of the folder G:\ClosedCheck. Select the date by clicking on the text file and then clicking Open. The list will show on the left of the screen and a view of the check will show on the right. The checks can be sorted by clicking on the column header. The selected check can be printed by selecting the POS printer using the pull down window at the top then clicking on the print icon. Odyssey/BackOffice Suite Programming POS/2100 Configuration 107

108 Printer Configuration System Print Options Entries on this programming window pertain to all terminals in the point-of-sale network. Under the Guest Check section: Suppress Zero Price Items. A check in this box will prevent modifiers with a price of $.00 from printing on the guest check. Rollup Condiment Price On Check. A check in this box will cause the price of modifiers to print along with the price of the main menu item. For example, without a check in this box, an up charge for On The Rocks would print on the same line as the descriptor. With a check in this box, the up charge would be included in the price for the drink itself. Suggest Tip Percent 1 through 3. These three percentages work in conjunction with the "by terminal" flag programmed under Printer Configuration - Terminal Print Options, on the Check 2 tab in the Sign and Tip Lines section as "Print Tip Suggestions". 2 Digit Check Number. A check in this box will cause only the last 2 digits of the check/order number to print on the receipt/guest check and on any requisition chits. There are two purposes behind this option; a smaller number is easier to "call out" for customer pickup in counter applications and it is more difficult for competitors to use a receipt to determine order count at a location. Suppress Account Number Print. A check in this box will remove the Account number from printing anywhere on any receipt. MPayPrint. Pertains to a development with an international distributor for payment via cell phone. Print Void Chit. With this flag set, an additional chit will print whenever an item is voided at the pointof-sale. This chit will print even if the item is not programmed to print on a remote printer. The chit will also contain a signature line. The chit will print on the printer group defined under Printer Configuration Terminal Print Options on the Output Tab as the Clock/Void/Disc Print Group. Print Discount Chit. With this flag set, an addition chit will print whenever a discount is taken at the point-of-sale. The chit will print on the printer group defined under Printer Configuration Terminal Print Options on the Output Tab as the Clock/Void/Disc Print Group. Enable Stub VAT Receipt. With this flag set, an additional button will appear at the bottom of the Closed Check display screen as VAT Receipt. The following two options only apply with this box checked. This is a custom development for France. Prompt for Information with Stub VAT. With this flag set, the terminal will prompt for a name, city, zip code and number of meals. This is a custom development for France. Print Tax ID on Stub VAT. There is a field in Store Configuration Store Tax ID. With a check here, the Store Tax ID will print on the Stub VAT. This is a custom development for France. 108 POS/2100 Configuration Odyssey/BackOffice Suite Programming

109 Under the Remote Printer section: Display Printer Failed Message. In live installations, you should always have a check in this box. With no check, there will be no displayed notification when a remote printer requisition has failed. Use Printer Reroute Table. This flag enables the functionality programmed in the selection Reroute Printer Groups. Print Limited Quantity Items. With this flag set, an additional line (showing the remaining quantity in the POS Limited Quantity "count down" table) prints on the remote printer whenever a menu item is requisitioned which has been established within the POS as a limited quantity item. Under the Bonus Points section: There are eight Bonus Descriptors, of sixteen characters of text each. Individual POS Items can be assigned a number of points to accumulate for each of the eight Bonus Descriptors. One use is to indicate caloric and other nutritional information on a guest check/receipt. If you are not implementing Bonus Descriptors, you should blank out any existing Bonus Descriptors by highlighting the line and pressing the Delete button. Even if you program descriptors, they will not show, if no POS Items are set to accumulate Bonus Points or if you leave the flag Print Bonus Descriptors unchecked under Printer Configuration Terminal Print Options under the Check 1 Tab. Printer Configuration Sale Types / Output Groups This is the exact same programming selection available under POS Terminal Options Sales Types. Refer to that section for documentation of this selection. Printer Configuration Scoreboard This section pertains to a Texas Digital customer display at the point of order in a drive through application. The software supports two models, the AccuView LCD display and the WenView LED display. The default database has a single Scoreboard programmed as number 1. Since the POS/2100 only supports a single Scoreboard at this time, you should merely edit this selection if you are implementing an installation with a Texas Digital customer display at the point of order for a drive through. Scoreboard Number. Leave this at the default of 1. Display Heading. This text entry is the header display, on the POS/2100, when the Scoreboard button is displayed on the point-of-sale terminal. Logo Timer. Enter the number of seconds to delay, after a transaction is either stored or paid, before refreshing the logo on the Scoreboard. Scoreboard Type. Check the appropriate box for either an LED display, an AccuView display or an AccuView with the TDS protocol. Color Selection. This selection allow for programming of the POS/2100 desktop which is displayed when the Scoreboard button is depressed. You can establish the Background Windows color, the Background color of the Scoreboard emulation window and the color of the font which is displayed within the Scoreboard emulation window. Odyssey/BackOffice Suite Programming POS/2100 Configuration 109

110 Printer Configuration Surveys This section is included at the request of several multi-location customers. It allows for a printout to occur on the receipt at a programmable interval and is generally used to solicit marketing feedback. Alternatively, if the frequency of print is set at 1 (for every transaction) it allows for essentially unlimited text to print on each guest receipt. The survey form above will print every tenth transaction. The lines will print after the Sub-Total. Other choices are before the Date/Time and after the Check Trailer. Often the survey form will indicate that the caller to an 800 number should have the store number and check number available. NOTE: For Atlanta Bread Company, a line may be included exactly as ~TC1. This will cause, at the indicated sequence, a line to print in the format MMDDY HHSSS STTTT, per their specifications. For Saladworks, include a line as ~TC2 to create the format MMDDY HHSSSS STTTT. For Gondola/Zizzi, include a line as ~TC3 to create their unique format. To generate a blank line, program a single character as a decimal point. Order Video Setup This section documents the files related to configuration of the Order Video screens themselves. Currently, the two files related to Order Video configuration are NOT programmed from within the Odyssey software. The operation of the Order Video screens is identical to the Order Video configuration used with the PCS/5000 software, however, the Item Video mode of operation is not implemented within the POS/2100. Order Video Files Overview There are two files related to the operation of the Order Video, or Kitchen Display System, which are not programmable through Odyssey. Both files should be edited using the Windows utility NOTEPAD.EXE. The two files, RQV.INI and SLOGO.TXT are "read" by a DisplayStation when the unit is initialized. Therefore, changes to either file will not immediately impact the operation of a DisplayStation. You can use the MODE button on the Bump Bar to re-initialize the DisplayStation. These two files are located on the Server as: C:\icom\POS2100\pcs\RQV.INI C:\icom\POS2100\Remote\SLOGO.TXT File Layout for RQV.INI There is a significant amount of programmed information contained in the file RQV.INI. There is no programming screen in either the POS/2100 application software or Odyssey BackOffice to enter all of the 110 POS/2100 Configuration Odyssey/BackOffice Suite Programming

111 features which are implemented in the file. For an understanding of the full functionality of the KitchenDisplay System, you should carefully read the annotated file listing below. The number of boxes in each screen for the Item Video, as well as various colors used on the screen, is defined in the file C:\icom\POS2100\pcs\RQV.INI. This file can not be programmed through the application software. In addition to information concerning the item requisition display type screens, this file contains information on the order type display and the ScoreBoard. If you must change this file, use the Windows utility NOTEPAD.EXE to modify the file. Use extreme care when modifying the file RQV.INI. A commented listing of the file follows. RQV.INI Default Section ; The DEFAULT section describes settings for ALL Kitchen DisplayStations. Any entry in the DEFAULT section may be changed by placing the same keyword in the separate section appropriate for the particular video (KitchenDisplay screen). [DEFAULT] Background=0 BoxBorder=8 MainText=15 CondText=14 VoidText=12 AddBack=8 VoidBack=8 Key Word Function ;Main screen background color display screens. (0 is black) ;Color used to draw the lines which form the "boxes" display screens.(8 is a darker gray) ;Default color for menu items on screen (only used if color not programmed or set to a 0 in the individual menu item programming). Used for various miscellaneous text on an item type display. (15 is white) ;Default color for condiment items on screen. (14 is a yellow) ;Color for an item which has been voided on screen. (12 is a bright red, almost orange) ;Background color for the "added items" section on screen. (8 is a dark gray) ;Background color for the "voided items" section on screen. (8 is a dark gray) BumpBar=0 ;Set to a 1. (A formerly used bump bar required a setting of 0.) CheckMode=0 TargetTime=xyz SortCond=1 ;Set as a 0 to display the entire order when items are added at a later time. Set as a 1 to only display the new items when items are added at a later time. CheckMode must be set to a 0 to enable on the fly (programmed under Terminal Print Options Remote Tab) display. Set as a 1 when guest checks are being used in the restaurant. If an order is on the screen when a new service round is entered, then new or voided items are appropriately placed in a separate section, and tagged. If the order remains on the screen for a third service round, another section of >>ADD or >>DELETE is appended to the displayed order. If an order is off the screen while multiple service rounds are added, then when the order is finally moved onto the actively displayed portion, only the net items entered will be displayed, as if they had all been entered on a single round, and is if voided items had never in fact been ordered. ;This activates the target time software, whereby the banner at the top of a box changes color when the order has been held in the KitchenDisplay system for longer than xyz seconds. 999 seconds is the maximum target time. To disable this feature, either do not put this keyword in the RQV.INI file, or set TargetTime=0. There is a statistical report available on any KitchenDisplay screen. To view the report, place the KitchenDisplay into the MODE screen, and select option 6. ;When set to a 1, the Display Station will sort condiments, based first on the setting in condiment programming, then alphabetically, if two condiments have Odyssey/BackOffice Suite Programming POS/2100 Configuration 111

112 CombineItems=1 SuppressErrorItems=1 DisplayTotal=1 SummaryScreen=1 FileDelay=6 OrderSorting=0 HeaderColor1=10 HeaderColor2=14 HeaderColor3=13 MaxOrderTime=600 the same video sequence number. Set to a 0 to disable condiment sorting. There is no corresponding keyword to sort menu items. ;When set to a 1, items will be combined on the KitchenDisplay screen, even if they are not on the terminal. ;Error corrected items will not appear on the KitchenDisplay screen with a zero (0) quantity. ;When set to a 1, the transaction total will display in the Previous Order Window. ;First, you must have keyword Omode=1 for this function to be operable. Setting SummaryScreen=1 enables the tracking feature on an order video. The lower right square will constantly display a summary of items on the remaining seven boxes. Exactly what is displayed is controlled by the setting of SummaryMode, the next field. ;This parameter is normally not used. The value 6 is the default. The parameter represents the number of 55 msec time ticks the KDS software waits before accessing the hard drive on the Server. In extremely busy locations, with more than two KDS units, or with a slow Server, this parameter can be used to reduce the load on the Server and the network from the KDS units. :This setting is normally not used. Its purpose is for multiple KDS operations, where stations are being used to prepare orders and it is important that orders be kept in the same order on each and every KDS. With a setting of 0, orders are displayed on a KDS as-received. With multiple terminals and multiple KDS units in a busy environment, it is likely that orders may not be displayed in the same sequence on two KDS units. With a setting of 1, orders are always displayed in order # sequence. The order # is assigned by system, not by terminal. Unless you need to synchronize two or more KDS units, do not set this parameter to a 1, since it might result in orders moving on a particular screen. An order begun on one terminal first, then finished after an order which was begun later on a second terminal would normally be displayed as finished. With this setting as a 1, the order begun second, but finished first, would be displayed in a square, and perhaps being prepped. When the KDS receives the order begun first, but finished second, it will move the order to maintain order # sequence. ;These settings allow the background color of the order header to be set according to the Sales Type. This is helpful to kitchen staff in quickly recognizing, by color rather than text, the type of order being displayed. HeaderColor1 sets the order header background color for Sales Type 1. The colors shown are 10 is lime, 14 is yellow and 13 is fuchsia. ;This setting works in conjunction with the order average calculations. These calculated numbers are available, as of March, 2005, as a BackOffice report as well as on the screen of a Display Station. The default is 600 seconds or 10 minutes. When an order has been displayed for a length of time in excess of this setting, it will be excluded from the calculations for order averages. This prevents orders which are left on the screen at the end of a serving period or overnight from impacting the calculations. 112 POS/2100 Configuration Odyssey/BackOffice Suite Programming

113 RQV.INI Video Section ; The VIDEO section(s) describe settings unique to each of the up to nine units. [VIDEO1] OMode=1 ScoreBoard=1 Beep=0 ForceToTop=C ForceToBottom=C RamDrive=C Key Word MasterBump=0 (Inactive) MasterBump=1 (Active) SlaveBump=0 (Inactive) SlaveBump=1 (Active) Function ;Operating mode for all screens. ;Do not set as a 0. (For item type with PCS/5000, and not implemented in POS/2100.) ;Set as a 1 for order type with 8 orders, shown 4 over 4. ;Set as a 2 for the "over/under" mode, where some terminals direct to the top, others to the bottom. ;Set as a 3 for 4 orders in 4 columns. ;Set as 4 to enable the Park Order operating mode. The main order window is organized as 8 orders, shown 4 over 4. Only parked orders will ever appear on the bottom. To park an order, depress the Park button on the BumpBar. Select which of the four orders on the top of the screen will be parked by touching a number 1 through 4. The selected order moves to the bottom of the screen, with a parked designation. To bump a parked order, use numbers 5 through 8. ;Set to a 1 for the single DisplayStation which will be connected, via an RS232 connection, to the ScoreBoard. ;Set to 0 to disable the buzzer on the screen. Set to a 1 to sound the buzzer each time an order is received. DO NOT SET TO A 1 ON AN ITEM SCREEN IF ONFLY IS SET BY TERMINAL. ;The entry after = is a terminal Node designation. If the entry is required for multiple terminals, add one line for each terminal. The entry overrides the programming in Terminal Print Options under the Remote tab. The entry provides for positioning on a particular screen of requisition information from a particular terminal, e.g. normally Terminal 3 (entered here as the C terminal) displays on the bottom, but when re-directed to this screen, it will display on the Top. (With the POS/2100, for Terminal 1, use the letter A, for Terminal 2, use the letter B, etc. ;Same as previous entry, except force Terminal 3 (entered here as the C terminal) to display on the bottom for this screen. ;Must be set as RamDrive=D on itp units used as KDS units. The default designation for the RamDrive, with a DigiCom PC is C, since there is normally not a hard drive. If there is a hard drive in a KDS, then this parameter must be used to change the default designation, normally to a D. The disk-on-chip for the itp is the C drive, therefore this parameter must be set to D to prevent the KDS from filling up the disk-on-chip itself with orders. If all KDS units are itp units, then this setting should be placed in the [DEFAULT] Section. ;As of March, 2005, bumping an order from one Display Station can also bump the order from other Display Stations. A setting of 1 for the MasterBump parameter identifies the Display Station as a Master. You can identify more than one Display Station as a Master. ;This setting works in conjunction with the above MasterBump setting. A Display Station with this setting as a 1 will have its orders bumped off the screen when the order is bumped by any Display Station which is identified as a Master. A Display Station can be identified as both a Master and a Slave. All slave Display Stations follow ANY Master Display Station. Odyssey/BackOffice Suite Programming POS/2100 Configuration 113

114 RQV.INI Color Selections The colors referenced in the file RQV.INI are from a palette of sixteen. If you are viewing this through Help, then the colors are as shown below. The color 0 is black, the color 15 is white. Order Consolidation - Keyword CombineItems = 1 The following example illustrates how an order would look on a terminal screen, and on a KitchenDisplay screen if the keyword CombineItems were set to a 1. Terminal Screen 1 Hamburger Cheeseburger 1 Hamburger Hamburger Lettuce 1 Lettuce 1 Hamburger Tomato Tomato 1 Cheeseburger 1.99 Video Screen 114 POS/2100 Configuration Odyssey/BackOffice Suite Programming

115 Display New Items Only - Keyword CheckMode = 1 The following example illustrates how the same order would look on a KitchenDisplay screen after the second round was entered, when the keyword CheckMode is set to different values. Sample Order Round 1 1 Single 1 Double 1 Triple Round 2 1 Big Bacon VOID 1 Double This is a guest check transaction, where three items have been ordered, then the check serviced. The check is then retrieved. An item is added, and a previously entered item is voided. At the time the second round is serviced, the KitchenDisplay may been in one of three situations. In case 1 below, the first round of the order was actually still actively in a box on the order screen. In case 2 below, the first round of the order was still held in the KitchenDisplay system, had not yet been displayed, and of course, had not been bumped off. In case 3 below, the order had already been bumped off. The following three show what will display on the KitchenDisplay screen after Round 2 above has been entered. CheckMode=0 Case 1 CheckMode=1 Order On-Screen Case 2 CheckMode=1 Order Off-Screen Case 3 CheckMode=1 Rnd1 Bumped 1 Single 1 Single 1 Single 1 Big Bacon 0 Double 1 Double 1 Triple >>> DELETE 1 Triple 1 Triple 1 Big Bacon 1 Double 1 Big Bacon >>> ADD ---- ADDED -- 1 Big Bacon 1 Big Bacon >>> DELETE -- VOIDED - 1 Double 1 Double NOTE: You do NOT need to set CheckMode = 1 when you are operating in Cafeteria Mode to obtain a separate display of each portion of an order when the Seat (Tray) button is depressed. Odyssey/BackOffice Suite Programming POS/2100 Configuration 115

116 Summary Screen - Keyword SummaryScreen = 1 In order for keyword SummaryScreen=1 to function, the keyword Omode=1 must also be set. This keyword causes the lower right hand box to display the quantity of on order for each of up to twenty (20) menu items. The box can only display ten menu items. When the banner at the top reads as below Item Summary 1, use the number 8 button on the bump bar to see the next ten menu items. The counts are the total number of menu items, either actively displayed in the remaining seven (7) boxes or still held in the DisplayStation, waiting for an order to be bumped so that there is room to display the order. Note that in the above example, the orders in boxes 1 through 6 have a red banner at the top. The keyword TargetTime=60 has been set in this example, and these orders all have been in the DisplayStation for in excess of sixty seconds. ScoreBoard Related File SLOGO.TXT This is a text file containing the logo message which will display on the ScoreBoard between transactions. The length of time, after a transaction is complete and before the logo displays, is set in the section under Printer Configuration Scoreboard. The file may only contain twelve lines of text, with up to twenty-four characters per line. This file may be modified using the utility NOTEPAD.EXE from Windows. A sample SLOGO.TXT file follows: Note that the output routine, from the DisplayStation to the ScoreBoard, does not have any "self-centering" software. The text will be displayed on the ScoreBoard exactly as is entered into the file SLOGO.TXT. 116 POS/2100 Configuration Odyssey/BackOffice Suite Programming

117 POS System Options The entries here relate both to the BackOffice operation and to various functions at the point-of-sale for all terminals in the network. POS System Options POS2100 Programming This selection will launch the POS2100 application in programming mode. All Desktops and Table layouts must be programmed from within the POS2100 application itself. POS System Options Revenue Centers Various reports can be organized on a by Revenue Center basis. A POS terminal MUST belong to one, and only one, Revenue Center. You should number your Revenue Centers consecutively, beginning at 1. There is a thirty character name for a Revenue Center, but on most reports the entire thirty character field will not fit. There is no additional programming related to a Revenue Center with the POS/2100 point-of-sale. The BackOffice merely uses the Revenue Center to which a terminal is assigned as a grouping filter. All programming related to operation and definition is either on a store-wide basis or on a by-terminal basis. You MUST check the box next to the text Active if you wish to have point-of-sale terminals associated with the Revenue Center. You must also check the box next to POS Revenue Center. The five drop down windows next to Stock Control Area relate to multi-location inventory functionality. This is where the Stock Control Area from which inventory items will be depleted is established by Stock Type. For a complete discussion of multi-location inventory functionality, refer to the Odyssey Operations document. NOTE: If multi-location inventory is not being implemented, there will be only a single default Stock Control Area and all five selections of Stock Types will be linked to that default Stock Control Area. For initi al programming of a new installation, the next selection after defining the Revenue Centers should be definin g the terminals in the point-of-sale network. Terminals in the point-of-sale network are made active, assigned a Terminal Descriptor, a Terminal Name and associated with a Revenue Center through POS Configuration, under the selection POS Terminal Options Posting Configuration. POS System Options Back Office Software End of Day Options Section Allow EOD With Open Checks. Generally there should NOT be a check in this box. An Open Check is not necessarily one which an Operator is currently entering items upon. An Open Check is one which has not been paid in full. Open checks cause an imbalance between sales and funds collected. (This option is IGNORED when performing an Automatic End of Day, which WILL occur.) Allow EOD With Employees Clocked In. A check in this box will allow the BackOffice procedure to continue even if hourly employees have not yet clocked out. The BackOffice User is still notified during the procedure and prompted whether to continue or not. With no check in the box, the end of day procedure can not be performed unless all employees are clocked out of the system. (This option is IGNORED when performing an Automatic End of Day, which WILL occur.) Retain Limited Quantity Items. A check in this box will retain entries in the Limited Quantity Items section of the point-of-sale software. With no check, the entries are removed at the End Of Day. Collect Weight of Scale Items. This flag only pertains to POS Items with the Scale Required flag set to a Yes. With Collect Weight set as Yes, the weight (times 1000) will be collected instead of the item count. The weight is collected in thousandths of a pound, or in grams. This flag is generally only set when inventory is being implemented, in order to correctly deplete weighed items. Odyssey/BackOffice Suite Programming POS/2100 Configuration 117

118 Reset All Secret Numbers. A check in this box will "un-assign" all Secret Numbers of all POS Operators who do not have the "Manager Mode Allowed" flag set under POS Operators Manager Settings Tab. The POS Operators will not be able to access the point-of-sale until a new Secret Number is assigned either through the BackOffice or through Button Type Change Operator Secret Number on the point-of-sale. This flag is useful if POS Operators are being assigned new magnetic cards each day from a common "pool" of cards. Charge Posting Options Confirm Account Number Entry. This flag pertains to operation of AccountCharge on all POS/2100 terminals. With this box unchecked, after an account number is selected, if the charge is accepted there is no prompting window. With this box checked, the same window as is displayed when an account inquiry is made displays, allowing the operator to confirm by name the account number prior to accepting the payment. Fingerprint Only AccountCharge. This flag pertains to operation of AccountCharge on all POS/2100 terminals. With this box unchecked, the Account Number may be manually entered or swiped. With this box checked, the only access to charging against the internal AccountCharge is for the patron to use his/her fingerprint. Ordering System Processing Terminal. This flag pertains to integration with third party ordering systems. The Processing Terminal is the terminal which is evaluates the trigger date/times of the orders in the Future Orders File every sixty seconds. When the Trigger Date/Time is reached, the order is activated. The processing functionality is built into the POS2100 software application. Unless the Server is a WorkStation Server, do not designate the Server as the Processing Terminal since the software must be constantly evaluating the Trigger Date/Time in order to place the order into the system at the designated Date/Time. Open Table Options Interface Active. Only place a check mark here if the POS2100 system of terminals is interactive and integrated with the in-store Open Table system. IP Port. This is the port of the Open Table computer with which the POS2100 will interact. This will be provided by the Open Table installer. IP Address. This is the IP Address of the Open Table computer with which the POS2100 will interact. It will be a fixed IP address, i.e. a numerical grouping. This will be provided by the Open Table installer. App Category. This has to do with the dynamic table display on the Open Table system. One of the status colors is appetizers served and the POS2100 will inform the Open Table system when any item from this Category is placed on the guest check for a table. Main Category. This has to do with the dynamic table display on the Open Table system. One of the status colors is main course served and the POS2100 will inform the Open Table system when any item from this Category is placed on the guest check for a table. Dessert Category. This has to do with the dynamic table display on the Open Table system. One of the status colors is dessert served and the POS2100 will inform the Open Table system when any item from this Category is placed on the guest check for a table. POS System Options Day Parts Day Parts are a grouping of the hourly information. Since the smallest increment of the hourly information is a fifteen minute increment, Day Parts begin and end on a fifteen minute increment. Day Parts are not required and are used only in reporting. The screenshot below should be used as a template when creating Day Parts. 118 POS/2100 Configuration Odyssey/BackOffice Suite Programming

119 Note the check marks under the column First and Last Sales Day Part. Note that there are no gaps in the programming of Day Parts and that a Day Part can extend over the midnight barrier. PO S System Options Shift Definitions Generally, all media balancing is by POS Operator. Unless the establishment is a guest check environment utilizing a cashier, as opposed to banked servers, there is no need to program any shifts. Under POS Terminal Options Transaction Options - Start Of Transaction Tab, you would NOT check the box Shift Logon Required. Select the shift 1, pre-configured in the database as Default Shift. There are separate Shift Reports both on the point-of-sale and from within the Odyssey Reports module. These are applicable in guest check environments utilizing a cashier. All counting within Odyssey MWS is by POS Operator and NOT by Shift. In order to retain tip accountability for the POS Operators who are servers, the finalizing media MUST stay with the set of totals pertaining to the POS Operator. That means the POS Operator who is acting as the Cashier must be set as a Master Server without Auto Transfer. This is more fully covered in the section of this document covering Staff POS Operators Operation Settings Tab. This means that there are no balancing media totals associated with the POS Operator acting as the cashier, and therefore no way to account for the payment media in the cash drawer. By requiring a Shift Logon for the POS terminal for the cashier, a separate set of totals is available for this purpose. Unless the cashier is also selling items, such as takeout items, there will be no sales associated with the shift. The report will show amounts transferred in, and show all payments under the Shift Report. Shift Number. This is merely a numerical designation for each shift. Shift 0 is, by program, set as no shift established on a particular POS terminal. Shift 1 should be used as the default shift for all terminals used as pre-check terminals. Shift Name. Leave the names for shift number 0 as No Active Shift. Shift 1 can be left as Default Shift or changed to All Servers. Examples of others are AM Shift, Lunch Shift, etc. Active. This box is only used by the POS Terminal to list, or not list, shifts when the Shift Selection button is depressed on the Log In Desktop at the point-of-sale. Generally you will want to set Shift 0 as active, and NOT set Shift 1, the default shift, as active. The lack of a check in this box DOES NOT mean that totals will not accumulate for Shift 1, only that it can not be selected on a terminal. You can not operate the POS terminal with Shift Number 0 as the selected Shift Number. POS System Options Credit Card Options General Tab The interactive credit card implementation, and electronic Gift Cards, with the POS/2100 uses DataCap. This require s implementation of the TCP/IP protocol within the point-of-sale network. It also requires that Internet Explorer Version 6 or later be installed on each of the point-of-sale terminals. The re are three variations on the DataCap implementation. For dial-up implementation, a body of DataCap software (DIALePay ML) resides on the Server. This software handles communication with the DataCap modem (DataTran ML) and with the application program of the POS/2100. For on-line Internet authorization with Mercury Payment, there is no requirement for any DataCap software running on the Server. (Other providers may be authorized by DataCap for this implementation in the future.) For other IP authorization Odyssey/BackOffice Suite Programming POS/2100 Configuration 119

120 networks, NETePay will reside on the Server. While a DSL connection is not required (only an open Internet connection is required), typically Internet authorization will be done over a DSL or cable modem connection. The only authorized direct provider of network services with the Comtrex POS/2100 over the Internet is Mercury Payment. Other network services require the DataCap software NETePay on the Server. Credit Card Options Tip Verification Percentage. Typically this entry will be 8.00%. The POS/2100 software uses this amount when a POS Operator, who is an employee, clocks out and provides a reference of the actual amount of tips paid (typically these are set as automatically paid under the setting POS System Options Miscellaneous Options) and this percentage of the Operator s net sales. NOTE: Unless there is a non-zero value in the above field, no "Tip" entry line will appear on the credit card voucher. Authorization Timeout. The default for this is an entry of 60 seconds. For a DSL implementation, it could be set to 20 seconds. You DO NOT want to set this entry too low however. Hold Card Authorize Amount. Pertains to use of Button Type Credit Card Hold, used to swipe a customer's card and hold the credit card number and expiration date until payment. Comtrex recommends a value of $0.00, since different processors handle this transaction differently. With a value of $0.00, the software will not interact with the credit card processing software and the merchant will not be charged for a transaction. This allows the card to be checked for validity but does not in any way affect the customer s available credit. Any entered amount (to confirm credit worthiness) will result in the POS software performing an Auth Only transaction. This transaction should not affect the customer s available credit, but there will be a charge to the merchant. Authorization Path. This is the IP Address used by the POS software for authorization; either the in-store Server's IP address or one for Mercury Payment. A separate section covering POS/2100 and DataCap Network Configuration is included following this section. Your entry here will be fixed as (DO NOT enter the quotation marks) with either DIALePay or NETePay. For Internet authorization with Mercury Payment, the entry is fixed as x1.mercurypay.com;x2.mercurypay.com (DO NOT enter the quotation marks). If you are running the software on a single terminal or PC and using the demonstration version of the DataCap software, enter in this field. Card Interface Processor. If you are not using either credit authorization or egift Cards, select Inactive. In the U.S., select Datacap. Comedia is for U.K. use only. Wynid is for French use only. Require Mgr for Manual Card Entry. Normally you will place a check mark here. It forces a manager to manually enter a card number since the fee is normally greater for manually entered credit card numbers. Automatically Close Pre-Authorization. A check in this field activates an additional feature on the point of sale terminal. A normal pre-authorization is used in a table service environment, where a tip will be added later. After interaction with the credit card processing network, a voucher is automatically printed in the background with a tip line to present to the customer. The advantage of a pre-authorization is that the terminal is immediately available for use for another transaction. If no tip will be added, normally you would simply finalize to a credit card payment method and await the accept or decline. The printed voucher would not have a separate tip and total line. However, in a counter service situation with a dial-up line, the delay in response may be up to thirty seconds. When the Table List Desktop is accessed by a POS Operator with a check under Manager Mode Allowed, as set in POS Operators Manager Settings Tab, an additional button will display on the Table List Desktop. Selecting this button will automatically sequence through each and every successfully preauthorized order and complete the authorization process, without a tip. This flag is only useful in counter service situations, where an InterNet Credit Card authorization is not possible because of the unavailability of DSL, to quickly free up the terminal for the next transaction. Keep Check Open on Pre-Auth. For counter service applications where a tip line is desired, so pre-auth is used rather than charge. Significantly speeds up operation by eliminating pick-up of check. 120 POS/2100 Configuration Odyssey/BackOffice Suite Programming

121 Gift Card Options Gift Card Options Authorization Path. Generally this will be the same as the Authorization Path. This field is used by Button Type Gift Card Balance on the POS/2100. Gift Card Options Merchant Number. Generally this will be the same as the Merchant Number for all credit cards. This field is used by Button Type Gift Card Balance on the POS/2100. POS System Options Credit Card Options Credit Card Types You can not add a credit card type. The following are fixed as the types of credit cards for the POS/2100. Included in the set of Finalizing medias in the default database are medias which correspond with each of these types. You can, therefore, only have one interactive Visa payment, one interactive American Express payment, etc. The above screen is only used to associate a Finalizing media with the credit card type. Note: The merchant number is REQUIRED to be entered in the programming of the associated Finalizing Media, i.e. Amex, Visa, etc. and for each Service Charge media associated with egift Cards. A merchant number IS NOT required for dial-up networks. Loyalty Network Options The February, 2007 release included the initial implementation of customer loyalty with Mercury Payment. The "ba sic" loyalty package is made available by Mercury at no charge to merchants who use Mercury to process credit cards. The February, 2009 release included the initial implementation of customer loyalty through a Comtrex web site. This loyalty package includes the ability of the merchant to customize a web site where customers may register their loyalty cards and provide information such as address and addresses. Various reports can be exp orted which allow the merchant to contract with third party vendors to initiate targeted customer marketing campaigns based on customers site and purchase preferences. For both Mercury and Comtrex, the central site is essentially only a points recorder during the transaction, with th e POS system having the ability to add, subtract or check the balance on an account. At any time during the transaction, the customer provides the card to the POS Operator and points are accumulated based on the purchase, as programmed in the following section. Service charges, tip amounts and tax amounts do not accumulate points. Programming at each store, under POS System Options in the Loyalty Options section defines the number of points (total dollar amount spent) before the customer is eligible for a rew ard. The voucher option results in a reward is in the form of a fixed dollar amount discount which is automatically taken on the next transaction. This discount can be declined by the customer so that points can continu e to accrue. The loyalty rewards option provides the customer the ability to select a free item based on the number of points already accrued. POS System Options Credit Card Options - Loyalty Voucher Options Loyalty Authorization Path. Generally this will be the same as the Authorization Path. This field is used by Button Type Loyalty Balance and Button Type Loyalty Add on the POS/2100. Loyalty Merchant Number. Generally will be the same as the Merchant Number for all credit cards. This field is used by Button Type Loyalty Balance and Button Type Loyalty Add on the POS/2100. Odyssey/BackOffice Suite Programming POS/2100 Configuration 121

122 Points at which Voucher Prints. This value defines the number of points at which a reward discount will be automatically applied to the transaction. (If you are implementing Loyalty Rewards, program ten nines ( ) here.) Dollar Amount of Voucher. Defines the amount of the discount automatically applied when the defined points level is reached. The dollar subtotal discount media used is fixed and is media number 94. (If you are implementing Loyalty Rewards, program 0.00 here.) Card Add Amount. This is the dollar amount at which you accrue one point. Typically this will be set to $1.00 for one point for every dollar of purchase. ($0.03 would accrue 33 points for $1.00 spent and 67 points for $2.00 spent.) If the Loyalty should not accrue any points (used only in conjunction with certain customers using in-house loyalty) you can set this to a 0. This applies identically to both Loyalty Voucher generation and the Loyalty Rewards program. Card Interface Processor. For Mercury Payment Loyalty, select Datacap. The Comtrex option is for in-house use for selected customers. Select No Loyalty if functionality is to be disabled. Points Accrue On. Select either Net Sales of a single itemizer. This selection allows Loyalty to exclude certain items, such as alcoholic beverages. Authorization Timeout. The default for this is an entry of 60 seconds. For a DSL implementation, it could be set to 20 seconds. You DO NOT want to set this entry too low however. Award CONFIRMED Customers Only. Only pertains to Comtrex Loyalty. Customers must register on the Loyalty Site in order to actually receive the loyalty reward, although points will accumulate. Use Loyalty Rewards - Not Voucher. This programming tab pertains to Loyalty Voucher Options, wherein a discount will be provided on a subsequent transaction. The following tab pertains to Loyalty Rewards, there the customer can use accumulated Loyalty Points to redeem a reward from a programmed list. You must choose your loyalty program to either generate a voucher for a future discount on a transaction or to provide a list of authorized rewards once a predetermined threshold of points has been achieved. You can not have both types of reward systems. Day of Week Loyalty Multiplier. There is a selection for a loyalty multiplier for each day of the week, with a start time and a stop time. This allows the establishment to change the number of loyalty points at a given sales level at certain times to incentivize customers. The multiplier can be less than one and therefore have digits after the decimal point. Loyalty Multiplier By Sales Type. There is a selection for each of the six sales types. This allows the establishment to change the number of loyalty points for different sales types to incentivize customers. The multiplier can be less than one and therefore have digits after the decimal point. If there is a double situation, i.e. a multiplier for a sales type and a day/time different than one (1), then both will be applied. POS System Options Credit Card Options - Loyalty Rewards Options Loyalty Rewards provides a list of items to offer the patron at no charge when a predetermined level of points is reached. You can program as many rewards as you desire. Each reward will carry the level of points required to select the reward. Reward Number. An automatically generated number for tracking purposes. Reward Name. Enter any name descriptive of the reward, such as Free Drink. List File. The rewards displayed must be a programmed List File. Of course, this List File does not need to appear on any Sales Desktop and can be created solely for use as a list of Loyalty Rewards at a certain points level. POS Item. Select a specific item from the List file if there is only a single menu item for this particular reward. Leave blank if all of the items in the above List File are eligible for the reward. Points Redeem. Enter the number of accumulated points in order to be eligible for the reward. 122 POS/2100 Configuration Odyssey/BackOffice Suite Programming

123 POS System Options Credit Card Options Nectar/Vouchers This programming section is unique to clients in the United Kingdom and relates to custom programming for electronic payment options. POS/2100 and DataCap Network Configuration Unless the point-of-sale implementation is within an existing private network, you should follow these steps when configuring the TCP/IP protocol on all of the terminals within the network. The network administrator should be consulted in a situation where the point-of-sale network is within an existing private network. In this situation, the only information required is the IP Address assigned to the POS/2100 Server. POS/2100 Network Configuration Server IP Address The TCP/IP protocol must be implemented on the Server and on all client POS workstations. The IP Address of the Server must be fixed with either DIALePay or NETePay. The Network Configuration outlined herein is based on an industry accepted standard for private network addressing. This is the same standard used by most routers. Examples of inexpensive, reliable routers which also act as 10/100 BaseT hubs are the LynkSYS BEFSR41, a router and four port hub, and the LynkSYS BEFSR81, a router and eight port hub. Even if you are using a combination router and hub, the IP Address of the Server must be fixed if either DIALePay or NETePay resides on the in-store Server. Since Internet Explorer uses the TCP/IP protocol, this protocol should always already be established on the Server. The following documentation leads you through setting the IP Address of a Server running Windows Right click on My Network Places, then left click on Properties at the bottom of the displayed list. The display will show as follows: Right click on Local Area Connection, then left click on Properties at the bottom of the displayed list. The display will show as follows: Left click on the bottom selection Internet Protocol (TCP/IP) to highlight it in blue then left click on the Properties button next to the Uninstall button. The display will probably show as follows: Odyssey/BackOffice Suite Programming POS/2100 Configuration 123

124 With Mercury Payment (or any service provider authorized in the future by DataCap to simulate NETePay on an external Server), the in-store Server can be set to Obtain an IP address automatically. With either DIALePay or NETePay running on the Server, left click on the box next to Use the following IP address and enter the following information. Do not make any entry into the Default gateway box or to either of the boxes at the bottom of the screen. Do not access the Advanced button, unless you are sure you know what you are doing. Click on the OK button to save the setting. POS/2100 Network Configuration Client POS Terminal IP Addresses If you are using a combination router and hub, you should allow the router to set the IP Addresses of the client POS terminals. This means that client POS terminals should have the TCP/IP protocol properties at the setti ng to Obtain an IP address automatically on the above window. If you are NOT using a combination router and hub, you may set the IP Addresses of the client POS terminals manually. However, the cost of a combination router and hub is very close to the cost of a hub and will eliminate possible headaches after the fact in configuring the TCP/IP protocol for your network. Aga in, if you are NOT using a combination router and hub, set each client POS terminal with a different IP Address the same way you set the Server. Use as the IP Address of your first terminal, IP Address for the second terminal, etc. Enter as the Subnet Mask for both. POS/ 2100 Network Configuration Single Demonstration Terminal If you have a single terminal or PC and are using the demonstration version of the DataCap software, enter for the IP Address in the field Authorization Path under POS System Options Credit Card Options under the General tab. 124 POS/2100 Configuration Odyssey/BackOffice Suite Programming

125 POS System Options Ordering Systems Programming for Third Party Ordering begins with Programming POS System Options Ordering System. Note that all three of the currently supported third party ordering systems are shown below. It is possible that a store might receive orders from more than one third party ordering system, i.e. both a kiosk system and an InterNET ordering system. This screen is used to configure all ACTIVE ordering systems. A separate White Paper is available on the web (which may be more up-to-date than this document) at ering/. The three vendors currently supported are: 1) Patron Path 2) White Knight Digital 3) Usable Health LLC Ordering System Name This is a dropdown selection of the available third party ordering systems. Default Table Allows incoming orders to be assigned to a particular table number. Generally, leave this at a 0. Default Operator An incoming order must be assigned to a particular POS Operator. The requirements for the default POS Operator are included in this section. Default Sales Type Generally this will be Take Out. An order received with active Delivery Instructions is automatically assigned to Sales Type 3, the designated Sales Type for Delivery. Default Terminal An incoming order is assigned as having been entered on this default terminal and, if the order arrives as paid, as having been closed on the default terminal. The Default Terminal can be different for each active ordering system. A separate programming screen defines which terminal is evaluating the Trigger Date/Time or orders and placing them in either the Open or Closed Orders table depending on their paid status and programming. It is on a separate screen since there can only be one Processing Terminal. Default Price Level When the menu sync feature is activated, only one price per POS Item is sent. The price level sent as the Online Ordering price is defined with this entry. Printer Group Pertains to printing a receipt/guest check upon initial receipt of an incoming order. (Not Trigger Date/Time when items are requisitioned). Select a printer group, usually Receipt Group, to print or select Inactive to print no receipt/guest check upon receipt of incoming order. Print Check Place a check here to print a receipt/guest check at Trigger Date/Time. Receipt, and POS Items assigned to be requisitioned, are sent as programmed in normal programming. Automatically Close Order Received as Paid Put a check here if an incoming order received as paid should be immediately placed in the Closed Order File or be available on the Table Desktop. If available on the Table Desktop, the order/check can only be closed, i.e. moved to the Closed Order File. A reason for retaining the check on the order screen might be to assure that the correct order is being picked up and create a process by which orders are finalized when given to the customer. IP Address Not currently used. Leave as is. IP Port Not currently used. Leave as it. POS System Options Desktop Options The selections under Desktop Options pertain to various display options within the POS/2100 software. With very few possible exceptions, it is recommended that you utilize the default parameters in the database for the entries programmed within this selection. Desktop Options Color Selections Various entries within this area allow colors displayed on the point-of-sale terminal to be changed. For entries which a color selection, double click in the colored window. The color palette will display. To retain the option of reverting back to the previous color, either write down the three numbers displayed in the left column or click on Add to Custom Colors. Odyssey/BackOffice Suite Programming POS/2100 Configuration 125

126 This pal ette is the standard windows color selection palette. Use the cursor to change the color in the display window immediately above the text Color Solid., then click on OK. Desktop Options General Tab Under the Table Selections area: Open Table Color. This is the color displayed on the Table Desktop of all point-of-sale terminals for tables which have no guest check associated with them. The default color is a shade of green. Current Table Color. This is the color displayed on the Table Desktop of all point-of-sale terminals for tables which have a guest check, where the guest check was last serviced by the Operator who is logged on and the guest check was last serviced within the Over Due Minutes time period established herein. The default color is a shade of yellow. Over Due Table Color. This is the color displayed on the Table Desktop of all point-of-sale terminals for tables which have a guest check, where the guest check was last serviced by the Operator who is logged on and the guest check was last serviced outside the Over Due Minutes time period established herein. The default color is a shade of red. Over Due Minutes. Enter the number of minutes where an Operator s open tables should turn from the Current Table Color to the Over Due Table Color. A typical setting is 20 minutes. Other Operator s Tables. This is the color displayed on the Table Desktop of all point-of-sale terminals for tables which have a guest check and the guest check was last serviced by an Operator other than the one currently logged on. Check Printed Color. This is the color displayed on the Table Desktop of all point-of-sale terminals for tables which have a guest check and where the guest check was printed by the Operator who is logged on within the Over Due Minutes time period established herein. If the check is not closed within the Over Due Minutes period, it will change to the Over Due Table Color. The default color is white. An Over Due Minutes setting of 20 provides ample time to settle a guest check after it has been printed. POS Operators are defined with certain privileges and characteristics in the selection under Staff POS Operators and the tab Operation Settings. If a POS Operator is defined as a Master Server but not defined to Auto Tr ansfer (as for a Cashier or a Hostess), then the Other Operator s Tables color will never display. For a Hostess, you would in addition disallow Sales. Then the Hostess can see all tables which are open, occupied and determine how long since the last service round. There is a Refresh button on the tables display desktop to update these colors. Under the Check Display area: Show Item Price With Quantities > 1. This pertains to the displayed guest check and not any printed guest checks. A check in this box displays the unit price of items in addition to the quantity entered and the total price for the items. The unit price will display immediately to the left of the extended price. Depending on the width of the guest check display, this may cause a portion of the item descriptor to not display. Combine Mode. This selection pertains to the displayed guest check. The displayed guest check can display main menu items either combined or separately. Touching the lower left of the displayed guest check toggles the display mode from None to either the Top or the Exact combine mode. Use the dropdown to pick which Combine Mode you desire to use for the displayed guest check. A separate section, immediately following this section, illustrates the differences. Under the Buttons and Windows area: Condiment Highlight. This is the color displayed on a Highlight type Condiment Window Popup. This definition is made under Sales Condiment Chains on an individual List File basis. The selected condiment displays a colored circle when an item is selected. An additional touch dedefined by the number of pixels in the left and right direction. The default is selects the item. The default color is white. Snap To Grid X. This selections pertains to programming of Button Windows on Sales Desktops within the POS/2100 software. When an entire Button Window is moved, it will snap to a preset grid POS/2100 Configuration Odyssey/BackOffice Suite Programming

127 Snap To Grid Y. This selection is identical to the one above but pertaining to movement up and down of Button Windows. Bevel Width. This selection pertains to displayed Button Windows on Sales Desktops within the POS/2100 software and defined the width, in pixels, of the surrounding bevel of the window. Border Width. This selection pertains to displayed Button Windows on Sales Desktops within the POS/2100 software and defined the width, in pixels, of the surrounding border of the window. Bitmap Expand. A check in this box causes bitmaps placed on buttons to expand to fill the entire button if they are smaller than button itself. Without a check mark, bitmaps smaller than the button will be placed in the center of the button. Under the Miscellaneous area: Display Currency Symbol. This flag is not implemented as of this date. The currency symbol will always display on the guest check displayed by the POS/2100. If you wish to disable this, use Control Panel to access first Regional Settings, then the Currency tab. In the area for the Currency symbol, enter a <Space> character. The operating system will not allow a null in this field. Desktop Options POS Displayed Guest Check Combine Modes The method of combining main menu items on the guest check displayed on the point-of-sale was selected in the previous section from a dropdown list of either Exact or Top. The Exact combine mode will only combine main menu items if every modifier, including modifiers which modify modifiers, are identical for the menu items. The Top combine mode will always combine main menu items. If the modifiers for one or more of the main menu items are different, the count of the different main menu items will appear below the total quantity of main menu items and the modifiers will display. The None mode of guest check display always displays each main menu item separately. In addition, for an order which has already been sent and subsequently retrieved, either by a Recall on a drive through application or by selecting the check from the Table Desktop in a table service application, the None mode will always display all modifiers. The following three screenshots illustrate the POS guest check display with an order containing two exactly identical main menu items, including condiments, during the entry process and a third with different modifiers. Odyssey/BackOffice Suite Programming POS/2100 Configuration 127

128 NOTE: Referring to the point-of-sale guest check displays which follow, the POS Operator can change the display mode from None to the selected Combine Mode, either Exact or Top, by touching in the check area at the bottom left. When an order is sent or paid, the check display mode is remembered for the next transaction on the terminal. Touching the lower left acts as a toggle between None and the selected Combine Mode. All three screenshots represent the order display during the initial entry process. Initial Entry None Display Mode Initial Entry Top Combine Mode Initial Entry Exact Combine Mode 128 POS/2100 Configuration Odyssey/BackOffice Suite Programming

129 All of the modifiers in the above application are set to be Hide In Combine Mode, through POS Item Programming Display/Print. This is the default for all modifiers with a $0.00 price. All modifiers are always retained to properly handle inventory in the event of a Void operation. The guest check display presentation when this order is recalled will be identical in the None presentation format. The following two screenshots show the same order after it has been Sent (or Stored) and subsequently recalle d. Recalled Order Exact Combine Mode Recalled Order Top Combine Mode Desktop Options Popup Windows Tab There are four types of Popup Windows within the POS/2100 software and four types for the POS/2100 HandHeld software. The default programming of each is shown below: Popup Type Name Rows Columns Button Color Font Color PLU Popup 5 2 Light Blue Black Condiment Popup 5 2 Light Red Black Media Popup 7 2 Dark Green White Generic Popup 7 2 Light Purple White PLU Popup HH 3 2 Light Blue Black Condiment Popup HH 3 2 Light Red Black Media Popup HH 3 2 Dark Green White Generic Popup HH 3 2 Light Purple White Rows. This defines the number of rows which the Popup will display before an up and down scroll bar is displayed on the right of the screen. All of the default programming above defines two columns, therefore a Popup with 5 rows will display a maximum of ten buttons before the scroll bar appears. Both the PLU and Condiment Popup Windows display up to three lines of text. The text on the buttons is automatically sized assuming that three lines of text will display. On a 12.1 screen, the Odyssey/BackOffice Suite Programming POS/2100 Configuration 129

130 text becomes rather small if you allow more than five rows. For installations using larger screens, it is practical to increase the defaults above. Columns. This defines the number of columns which the Popup will display when the number of items exceeds the number of rows. Popup windows with fewer items than rows will always display in a single column. More columns means narrower columns. The narrower space results in smaller text in order to fit the number of characters set under the Popup Line Length on the POS System Options Desktop Options General Tab. If the text becomes illegible, you must either edit the descriptor to be shorter, or reduce the number of characters displayed per line using the Popup Line Length entry. Button Color. This defines the background color of all buttons on the Popup window. As a programming aid, the button color window will display the character A in the font color programmed next. Font Color. This defines the text font color for all buttons on the Popup window. Notice in the window that the letter A is placed in the Button Color area, in the Font Color defined here to provide an image of how the button will look on the point-of-sale screen itself. The areas on the display screen which the Popup Windows occupy is set within the programming of the POS/2100 software itself. Generally, the Popup Window will be set to NOT block the guest check area of the screen or the numeric keypad. The guest check screen itself is also sized within the software of the POS/2100 and can be less wide than the default Desktops in the demonstration database. If the actual guest check size is less wide than the demonstration database, it is quite practical to use 4 or even 5 columns for the PLU and Condiment Popup windows. Popup Text Line Length. This selection pertains to each of the four Popup Window types of PLU, Condiment, Media and Generic. It defines the number of characters which will display on each button. The point-of-sale software will automatically size the font displayed on the Popup windows to fit. Long descriptive fields can cause the text to become illegible since the font is too small to read. The default entry is 16, however if you are using three or four columns on your Popup windows, you will want this entry to be closer to 10 to 12. NOTE: If your Popup windows are displaying text which is too small to read, either find the longest text entry which is displaying on the Popup window and make it shorter, OR, change this entry to a smaller number. The text entries which are too long will display nine characters followed by a -, e.g. Doubl e Cheeseburger Combo, would display Double Ch- with this entry as a 10. In such an example, you would want to edit the descriptor so that it is meaningful, e.g. Dbl Ch CMB. POS System Options Custom Colors The programming window here allows the User to create custom templates of sixteen colors each. The programming is to support a capability within the POS/2100 which is not implemented as of this date. The template assumes that when Button Windows are being created within the programming of the POS/2100 itself, that sixteen colors will be sufficient and that by using a fixed set of sixteen colors, the various Desktops used at the point-of-sale will be consistent. Any color can be created currently with the POS/2100 programming software. But once a color is created that the programmer likes on one desktop, it is somewhat cumbersome to copy the color to the color palette then paste it in to various buttons. POS System Options Miscellaneous Under the Transaction Options area: Allow Store / Recall. If you are placing a Store and Recall pair of buttons on any Sales Desktops at the point-of-sale, place a check in this box. Add To Covers By Item Only. A check in this box will disable the ability of the POS Operator to manually enter the number of guests. The covers entry will be determined solely based on a flag, 130 POS/2100 Configuration Odyssey/BackOffice Suite Programming

131 established in programming under Sales List Files then POS Item Programming Flags Tab. From this window, various POS Items can be set to increment the cover count when an item is purchased. NOTE: The above flag overrides the setting of "Allow Zero Covers" entry, programmed in POS Terminal Options Transaction Options on the Start of Transaction Tab. DO NOT set this flag in Cafeteria Mode. Allow No Sales. A check in this box is required in order to enable any No Sale operations on any POS terminal. Even with a check, a No Sale Button must be placed on a Sales Desktop, then the POS Operator must be authorized under the Operation Settings Tab to perform a No Sale operation. Manager Entry Per Task. Various operations at the point-of-sale require that the POS Operator have permission to perform the operation. When the logged on POS Operator does not have permission, the POS software prompts for the access number of a POS Operator who does have permission, typically a Manager. If this box is checked, and there are two or more times within the same transaction that a Manager is required, the access number must be entered each time. With no check, once an authorized access number is entered, any further tasks requiring permission within that specific transaction will be considered to have been authorized by the Manager whose access number was first entered. Manager To Access. This flag should only be set if all terminals are set with Server Stay Down and the # of Seconds to Stay Down = 0, under POS Terminal Options Transaction Options. With a check in this box, when a POS Operator attempts to access either a Sales Desktop or the Table Desktop, the POS/2100 software will check the flag Manager Mode Allowed for the POS Operator. Generally POS Operators will NOT have this flag set. In this case, a Manager number must be entered to enable the POS Operator to access the Sales Desktop. This is useful in quick service environments to allow managers to control the access by POS Operators to terminals at shift changes. Prompt on Sales Date not equal to Actual Date. A check for this flag causes the POS/2100 software to check the date/time on the POS terminal at each POS Operator log in operation and compare this with the Sales Date of Odyssey MWS. The start time for the Sales Day is the one defined under Employee Configuration Time a Work Day begins. If the date on the POS Terminal is later than the Sales Day and the time is after the Time a Work Day begins, the software will advise the POS Operator. A Continue Yes or No? prompt allows the Operator to continue operating despite the discrepancy. Collect Gross Sales Hourly. A check for this flag will cause Gross Sales (sales before discounts) to be collected and reported for Hourly and Day Parts. NOTE: This flag is evaluated when information is placed into the database. It should be set once because is it not a "retroactive" flag. Allow Sale of Items Out of Stock. A check here will allow the POS Operator to purchase a menu item even if it is set for limited quantity and the quantity on-hand is less than or equal to zero. The POS will prompt the POS Operator with the theoretical on-hand quantity along with "Sell Anyway?". This flag is for use principally in Cafeteria Mode where the limited quantity is an approximate figure. Assume no decimal for POS numeric entry. A check here will cause a currency entry at the POS to be interpreted without an automatic decimal point, e.g. with no check an entry of 123 is $1.23 and with a check here an entry of 123 is $ Isolate Checks By Revenue Center. Pertains to checks displayed on the Table Desktop of a POS terminal. With a check mark, only checks last serviced in the terminal's Revenue Center will display. Use Touch Delivery Keyboard. A check mark here will cause the display of the on-screen QWERTY keyboard during entry of a new Delivery Customer. With no check mark, an attached keyboard is required. Display Total Column Check Lists. With a check mark here, a column showing the total will appear for closed checks and open checks where the two table desktop is selected. This is optional because in order to display this column, the items for each check must be used to calculate the total and with many closed checks or large quantities on closed checks a substantial delay may result. Five Digit Barcode Price. This option pertains to barcodes generated by a scale printing Random Weight Barcodes for scanning. Most scales will generate a four digit price. All scales in a particular location must generate identical barcodes. Odyssey/BackOffice Suite Programming POS/2100 Configuration 131

132 Leading Zero RW Barcode. This option pertains to barcodes generated by a scale printing Random Weight Barcodes for scanning. Most scales will generate a barcode which begins with the digit two (2), however, some will generate a leading zero. All scales in a particular location must generate identical barcodes. Maximum Quantity Entry. Enter a number between 1 and 999. This entry determines the maximum number which the POS Operator may enter on a point-of-sale terminal for the quantity of single item. The recommended default values are either 99 or 199, since this will handle over 99% the real amounts while preventing inadvertent erroneous entry. Minutes Before Auto End. Enter the number of minutes of total inactivity (touching the screen is activity) before the software will perform an automatic "Send" function. This automatic "Send" will NOT be enabled if the POS Operator has left the popup "Enter Amount" displayed or has left the terminal in the Split Check Desktop. The maximum entry is 60 minutes. An entry of 0 is not allowed. Void All Prior To Auto End. Set to a yes if items on the display should be voided prior to the Auto End. If No, the items will be requisitioned. If the result is a zero balance check, the check will be closed, not sent. Under the Media Options area: Automatically Pay Tips. With this box checked, any entered tip is assumed by the software to have been automatically paid to the POS Operator in cash. The reports will reflect the actual amount of the tips as a memo, but the cash due from the POS Operator at the end of the shift, which is printed on the Operator report, will already be net of the tips. In addition, a Charge Tip can be established to pay the POS Operator only a percentage of the actual tip amount entered. This is to reimburse the establishment for credit card processing fees. This amount is programmed under Back Office Medias and then selecting a media type of Tip/Gratuity. The Options tab under this programming allows the entry of an extraction percentage. As an example, if the extraction percentage was 2%, and a POS Operator received $100 in tips from patrons entered through this Tip/Gratuity media, then the amount of cash from the Operator would only be net $98.00, not $ The extracted $2.00 will automatically show as owed to the establishment by a banked POS Operator. This Tips Paid amount appears on the employee payroll reports in the Tips column, along with any tips declared by employees with a Job Cod with Prompt For Tip at Declaration as true. If the Automatically Pay Tips flag is not set, only the charge tips will appear on the Tip column of employee reports, since these will need to be deducted from payroll. In this mode, with the above flag NOT SE T, you should also never have any Job Codes set with Prompt For Tip Declaration as true, since the declared tips would also (incorrectly) appear on the employee reports. Prevent Multiple SBTL PC Disc. This flag is used to prevent multiple subtotal percentage discounts on the same guest check. With no check in this box, a 50% police discount, followed by a 10% senior discount on a $100 sale would yield $45 ( *100 = *50 = 45). Tips Paid Media. This entry works in conjunction with the above option, for automatically paying tips. You should leave the default media entry as is. Reason Code For Modify Payment. This flag pertains to Button Type Modify Payment (Transfer Media). Place a check mark here if a Reason Code should be selected when the button is touched. Reference Text For Modify Payment. This flag pertains to Button Type Modify Payment (Transfer Media). Place a check mark here if Reference Text should be entered with the button is touched. Evaluate Coupon at Entry Only. With this flag set, the criteria for a coupon are evaluated one time, at entry. A subsequent purchase can not change the items to which a coupon applies. With no check mark, the coupon criteria are re-evaluated each time an item is entered. It is recommended that you NOT place a check here, to assure proper utilization of the coupon criteria. Mgr Rqd for all Discounts after Print. This flag allows POS Operators to operate discount media as long as the guest check has not been printed. With the flag set, a Manager is required to apply a discount after printing. This is to prevent the POS Operator from falsely entering a coupon and pocketing the payment. One Coupon Per Transaction. With this flag set, only one coupon may be used during a particular transaction. a of 132 POS/2100 Configuration Odyssey/BackOffice Suite Programming

133 Round to Nearest Nickel. This flag is to prevent the use of pennies. Amounts of.01,.02,.06 and.07 will be rounded down to either.00 or.05. Amounts of.03,.04,.08 and.09 will be rounded up to.05 or.00. The amount is accumulated in a balancing total, Media 95, which prints on all financial reports in the same section as a add-on tax. Contro l options: Enable Change Operator # at POS. This flag pertains to Button Type Change Operator Secret Number which may be placed on the Log In Desktop. In the U.S., you should generally not set this flag as true unless you are not using interactive credit card authorization or if you are, you have forced fingerprint identification at the POS by Managers. Otherwise, enabling this button may be a PCI compliance violation. POS Operator # by Fingerprint Only. With this flag set, any form of POS Operator declaration at the POS, including all Manager authorization, can be by fingerprint only. This will exclude any magnetic card swipe and the entry pad will not be presented for manual Secret Number identification. If this flag is set, each and every POS Operator must be associated with an Employee, even if time and attendance is not being used, because the fingerprint association is on a unique individual basis and is programmed by relating the fingerprint to an employee. POS System Options Scale Definitions This section is only utilized if there will be a scales in the point-of-sale network. The POS/2100 supports an interface to the NCI, Weigh-Tronix Models 6702, 6710, 6712 and 6720 using the "NCI" Serial Communications protocol. If items will be weighed and have their weight manually entered, you must still complete this section on Scale Definitions in order to enter the scale resolution. This is a Weights and Measures requirement, to prevent erroneous container weight ( Tare ) and item weight entries. For more information on these scales, refer to the web site In general, if there is are scales in the point-of-sale network, they will all be the same brand and model, so there will only be one entry. However, if different point-of-salwould require an entry in this section for each scale within the terminals are interfaced to different scales, you network. Items which will have a weight entry must have the Scale Required flag set under the Flags Tab under List Files POS Item Programming. Scale ID. This is merely an identifying number assigned by the software. There is no reason not to start with 1 and continue in progression if you have more than one scale in your network. Scale Name. Enter an identifying name for the scale, typically a manufacturer and model number, e.g. NCI For terminals where a scale will be interfaced, and on terminals where the display of a scale will be used to manually enter a weight, it is this name which is selected from the dropdown list on the Scale Tab under POS Terminal Options I/O Devices. Weight Symbol. Enter the unit of measure used for the scale, either lb or kg. Note that Weights and Measures REQUIRES the use of lower case characters when identifying units of weight. Scale Resolution. Enter the resolution of the identified scale using the documentation provided by the manufacturer. Typical entries are.002,.005,.01 and.02. For both a Tare entry and manual weight, the point-of-sale software will screen the entries and disallow any entry which is not an even multiple of the entered Scale Resolution. Number Scale Digits. This entry is for future support of scales other than NCI, Weigh-Tronix. For NCI, enter a 16 Decimal Point In Response. This entry is for future support of scales other than NCI, Weigh-Tronix. For NCI, place a check mark in the box. PO S System Options Scale Tare Lists In most applications, there will be a single Scale Tare List. A tare is the weight of the container for the sales item being weighed. Providing a list allows the POS Operator to select the container, by name, being used to hold th e sales item. The facility for multiple Scale Tare Lists allows the programmer to place multiple Scale Buttons on the Sales Desktop for use with different kinds of sales items, e.g. Salads or Meats, to shorten the list from which the POS Operator will pick. Odyssey/BackOffice Suite Programming POS/2100 Configuration 133

134 Sca le Tare Lists General Tab Scale Tare List Number. This is merely an identifying number for the list. All programming will use the name in a dropdown window. There is no reason not to simply use 1 and continue with 2, 3 etc. if you are implementing multiple Scale Tare Lists. Scale Tare List Name. This is a sixteen character text field used in a dropdown window when assigning a Scale Tare List to a Scale Button. Scale ID. Use the dropdown list to choose the scale for which this list will be used. In most installations, there will be only one Scale ID. Scale Tare Lists List Details This tab is used to enter a name for the container being used to hold a weighed item and the weight of the container. To add a new container: Left click the Add icon. Enter a unique Record Number for this container, within this list. Scale Tare Names will be listed at the point-of-sale terminal by this number. Enter up to sixteen characters to describe the container corresponding this tare value. Enter the weight of the container in the field Scale Tare Value. NOTE: The software will indicate a warning prompt of Invalid Entry if the entered Scale Tare Value is not an even multiple of the Scale Resolution of the Scale ID selected on the General Tab, i.e. you can not enter a Scale Tare Value of.001 if the Scale Resolution of your scale is.005. You can delete a Scale Tare using the Delete icon on this tab. You can also use the Undo icon to start the entry process over again. POS System Options Scale Buttons In most installations there will be two, at most, Scale Buttons on the Sales Desktop of any point-of-sale terminal. One will interact with the attached scale to read the weight. The other would be a manual backup in case the interface is down. Of course, the manual backup assumes you have a display attached to the scale and the scale itself is actually operational. The entries here are used as a selection mechanism when configuring a Scale Button on a Sales Desktop of the POS/2100. To add a new Scale Button, left click on the Add icon and complete the information pertinent to the Scale Button listed below. You can use the Delete icon to remove an erroneous entry. Scale Button ID. This is merely an identifying number for the Scale Button. It is automatically filled in by the software. Scale Button Name. This entry is used in the dropdown list when configuring a Scale Button on a Sales Desktop of the POS/2100, e.g. Manual Entry or Read Scale. Another use of multiple Scale Buttons might be to weigh different types of items, e.g. Salads or Meats, and then use different Scale Tare Lists to only identify the appropriate containers from which the POS Operator will choose. Scale ID. Use the dropdown list of Scale Names to identify the Scale with which this Scale Button is associated. Manual Entry Only. A check mark here indicates that this Scale Button will ONLY accept a manually entered weight and WILL NOT interact with an attached scale. A Scale Button with Manual Entry Only checked will, however, require that any manually entered Tare be in an even multiple of the Scale Resolution for the selected Scale ID. Confirm Tare Entry. A check mark here will cause the programmed amount of the selected tare to display in an entry window. The tare amount may be changed or merely depress the Enter button to accept. Scale Tare List Number. If Manual Entry Only is not checked, this is a required entry. With a blank selection under Scale Tare Name, a list of all tares in the Scale Tare List Number will be presented to the POS Operator for selection. 134 POS/2100 Configuration Odyssey/BackOffice Suite Programming

135 Scale Tare Name. This is an optional entry if Manual Entry Only is not checked. If a Scale Tare Name is selected here, then the amount of the tare is automatic for this Scale Button. If Confirm Tare Entry is checked, then the amount of the tare will be displayed and the POS Operator will be provided the opportunity to override the entry, or enter an amount if the selected Scale Tare Name corresponds to a tare value of POS Terminal Options All of the selections herein use the same presentation format which provide the same options to program a single terminal, a group of terminals or all terminals. In addition, you have the ability to program a single terminal then copy the changes to either a single terminal or a group of terminals. This is referred to as bulk programming in later sections. The selection methodology and how the copy and paste operate is covered in the following section. POS Terminal Options Selection Methods A typical programming screen under POS Terminal Options is shown in the screen shot below. The section on the left, in the above screenshot, determines which terminal(s) are being programmed by the entries being made on the right. The display above shows that only the terminal BackOfficeServer is being programmed. The text displayed is the text entered under POS Terminal Options Posting Configuration as the Terminal Descriptor. You may program more than one terminal at a time by left clicking on the small gray box to the left of the Terminal #. When you do so, the terminals which will be affected by your entries are all highlighted in blue, as shown below. In the above example, both Terminal 2 and Terminal 3 will be affected by any entered changes. If you have highlighted an incorrect terminal, merely left click again in the small gray box to the left of the incorrectly selected terminal and the blue highlight will disappear. Odyssey/BackOffice Suite Programming POS/2100 Configuration 135

136 You may select all terminals by left clicking in the small gray box to the left of the symbol # on the above displayed screen. When you do so, all terminals will be highlighted in blue. Some entries must be unique for each terminal. The se entries will gray out with multiple terminals selected. POS Terminal Options Filter Criteria As an additional programming aid, you may filter the terminals which are listed on the screen at the left of the disp lay. Next to the toolbar display at the top of the window are the two primary filter criteria. The first filter criteria will cause only those terminals in the selected Revenue Center to display. Use the drop down to select the terminals to be programmed. This is useful as a prelude to selecting all terminals. The second filter criteria enables the programming of terminals currently not set as Active. This is useful when p rogramming a database prior to receipt of the Security Activator/Key. Two of the selections under POS Terminal Options have additional required filter criteria. The Sales Type selection requires that the information being programmed by terminal also be programmed separately by sales type. This is covered in detail in the section POS Terminal Options Sales Types. The Auto Shifts selection requires that the information being programmed by terminal be programmed separately for each auto shift which will apply to the particular terminal. This is covered in detail in the section POS Terminal Options Auto Shifts. POS Terminal Options Copy / Paste Operation The Copy/Paste Operation is provided as a programming aid to duplicate programming from one terminal to either a single terminal or a group of terminals. First, hig hlight a single terminal by left clicking in the small gray box to the left of the Terminal #, then left click on the Copy Icon. Notice that when you click on the Copy Icon, the highlight will change from dark blue to light blue. Next, with the copied terminal highlighted in light blue, left click on the small gray box to the left of the Terminal #(s) you wish to make identical. Notice that as you highlight a terminal into which you will paste programming details, the elements to be programmed on the right of the screen turn a dull gray. While you are in the middle of a Copy/Paste operation, you can not program individual entries. When all the terminals into which you wish to paste are highlighted in dark blue, click on the Paste Icon. Certain information must be unique to each and every terminal. For example, the Terminal Name and Terminal Descriptor must be unique. The Copy/Paste operation is smart enough to know this. The information which CAN be pasted, WILL be pasted. You can see this by simply highlighting multiple terminals in the selection. The entries which must be unique, those which can not be programmed on multiple terminals at the same time nor pasted from one terminal to another, will gray out with multiple terminals selecte d. The screen shot below illustrates this using the POS Terminal Options Posting Configuration selection. Note that the entries next to Terminal Descriptor and Terminal Name are a very light gray, while the text Active and the text Revenue Center remain a darker gray. 136 POS/2100 Configuration Odyssey/BackOffice Suite Programming

137 PO S Terminal Options Posting Configuration In this selection, terminals in the point-of-sale network are assigned a Terminal Descriptor, a Terminal Name and associated with a Revenue Center under the selection POS Terminal Options Posting Configuration. They are also assigned an Active status through this selection. Terminal Descriptor. This must be unique for each terminal in the point-of-sale network, including the Back Office Server. This name is used throughout the programming module to identify terminals being programmed. It is also the name printed on all reports identifying information as having originated at a particular terminal. While the database supports a thirty character descriptor, a sixteen character descriptor is generally all that will fit in many reports and on many screens. Terminal Name. This must be unique for each terminal in the point-of-sale network. This MUST be the same as the computer name. The computer name is established under Network Identification in the Windows 2000 operating system. It is strongly recommended that the computer names listed in the default database, SERVER for the Back Office and WS2 through WS26 be used as computer names for support purposes. A POS/ 2100 terminal seeking to start up will look in the database to determine if its computer name matches an entry established here as the Terminal Name. If there is no entry, the POS/2100 terminal software will not initiate. A common problem in attempting to put a new terminal into service in an existing point-of-sale network is either an incorrect or a duplicate computer name. Active. Place a check mark in the box next to Active to allow the POS/2100 terminal to operate. The number of active terminals allowed depends on your Security Key/Activator. The license mechanism in the BackOffice software will not allow ANY terminals to be placed as Active unless a Security Key/Activator is installed on the computer. In addition, the license mechanism REQUIRES that the active terminals start at 1 and ascend sequentially. For instance, if you have a Security Key/Activator for five licenses, it is not possible to have Terminal # 6 as Active. Of course, you can make Terminal #5 inactive if you are only operating four licenses and have allowed room for growth. Active terminals must start at terminal 1 and end at the number of licensed copies of the POS/2100 software. Revenue Center. Use the drop down list to assign a terminal to a particular Revenue Center. POS Terminal Options Transaction Options Entries programmed under this selection define certain operating characteristics of the terminal during a transaction. Transaction Options Start Of Transaction Tab Compulsory Table Entry. A check in this box will require the selection of a Table Number in order to access a Sales Desktop from the Table List Desktop. In order to REQUIRE a Table Number for each guest check, there should be NO New Check button on the Log In Desktop and the End of Sale Desktop MUST ALWAYS be the Table List Desktop. Refer to the section POS Terminal Options Desktop Options for a discussion on determining the End Of Sale Desktop. Compulsory Cover Entry. A check in this box will cause a Popup Window to appear at the beginning of each sales transaction requiring the entry of the number of guests. With no check, the software will usually assume the number of guests is one, unless there is a check under the option Add to Covers by Item Only under the POS System Options Miscellaneous selection window. If the number of guests is being determined by the items purchased, DO NOT check this box. Odyssey/BackOffice Suite Programming POS/2100 Configuration 137

138 Allow Zero Cover Entry. A check in this box will allow the POS Operator to enter a zero either from the compulsory covers entry Popup or directly using a Covers button on a Sales Desktop. Place a check here if the following flag for Cafeteria Mode is also checked. Default to Zero Covers. Without a check here, no covers entry defaults to a cover count of one (1). Cafeteria Mode with Seat Button. A check in this box establishes a different mode of operation when Button Type Seat Number is touched. This is documented in a subsequent section, Cafeteria Mode Operations. Prompt if Open Checks. This flag pertains to a very particular use of the terminal, one where POS Operators are being used as Shifts. With this flag set as a Yes, when a POS Operator is entered from the Log In screen of the POS/2100, the software will prompt Do You Want To Continue? if any other POS Operators have open checks. Generally, DO NOT check this flag. There is a related flag under the End Of Transaction Tab. Server Stay Down. This flag is intended for use when the POS Operator will log in for each and every transaction. In most applications you should place a check in this box and place an entry in the following selection. With no check in this box, when the POS Operator number is entered, the POS/2100 software will immediately present the End Of Sale Desktop, either the default Sales Desktop, defined either by Operator or Terminal under POS Terminal Options Desktop Options, or the Table Selection. When a single service round or transaction is complete, the next screen presented will be the Log In screen. With a check in this box, the POS Operator will stay logged on as the active Operator for the number of seconds defined in the following entry. # Of Seconds To Stay Down. Enter the number of seconds that the terminal should retain the logged on status of the POS Operator both after log-on and at the end of a transaction. The maximum entry is 3600 seconds (60 minutes). Any entry of greater than 3600 seconds will be interpreted as 60 minutes, or 3600 seconds. A Serve r CAN NOT stay on indefinitely. An entry of 0 for the # Of Seconds to Stay Down for the POS Operator will translate to 3600 seconds, or 60 minutes. Shift Logon Required. Generally this box will not be selected. Any terminal with a check in this box MUST have a Shift Select button on the Log In desktop. The shift must be selected prior to any POS Operator logging in. The selected shift is retained until either another shift is selected or the Odyssey End Of Day procedure is performed. Refer to POS System Options Shift Definitions. Default Shift. For terminals where the Shift Logon Required box is not checked, this defines where the shift totals will accumulate and you should leave this as shift 1. For terminals where the Shift Logon Required box is set, you should select No Active Shift, Shift 0, from the dropdown. NOTE: Two options have been moved from this section with the June of 2005 release. The options "Compulsory Account # Entry" and "Validate Account" are now programmed both by terminal and by Sales Type. Refer to the section under POS Terminal Options Sales Types under Compulsory Reference/Account Entry. Display Name in Table/Check List. This flag pertains to the POS 2100 Table List Desktop. With a check in this box, an entered name will display in the list in the middle of the desktop, even if there is an assigned table number. With no check mark, the table number and check number will display. Compulsory Sales Type Entry. A check in this box will cause a Popup Window to appear at the beginning of each sales transaction requiring the selection of a Sales Type. The POS software supports three Sales Types. If there are only two valid Sales Types, you should set the following entry to a 2. If the Sales Type Entry is not compulsory, the Default Sales Type will be used for the transaction. The Sales T ype may be changed by the POS Operator at any time prior to completion of all payment on a sales transaction. Default Sales Type. Use the drop down to select the default Sales Type for this terminal. 138 POS/2100 Configuration Odyssey/BackOffice Suite Programming

139 Default To Forgive Tax. With a check mark here, a new transaction (or service round) is begun just as if the Forgive Tax button had been depressed. A depression of the Forgive Tax button enables tax. Transaction Options End Of Transaction Tab Display Current Order With Send. At the end of a service round, a guest check may be dismissed either using a Send Button or a Print Button. With a check in this box, a separate Popup Window will appear when the Send Button is depressed, presenting only those items entered on this service round. The POS Operator will then select either the Send Button or the Cancel Button to dismiss the Popup. Display Current Order With Print. At the end of a service round, a guest check may be dismissed either using a Send Button or a Print Button. With a check in this box, a separate Popup Window will appear when the Print Button is depressed presenting only those items entered on this service round. The POS Operator will then select either the Print Button or the Cancel Button to dismiss the Popup. Leave Screen A lways. This flag pertains to the completion of payment on a Sales Transaction. With a check in this box, regardless of whether or not change is due the customer, the guest check will continue to be displayed on the POS screen until the POS Operator depresses a button to move on to the next transaction. Leave Screen If Change. This flag pertains to the completion of payment on a Sales Transaction. With a check in this box, the guest check will continue to be displayed on the POS screen if change is due the customer until the POS Operator depresses a button to move on to the next transaction. Confirm Sales Type at End Of Sale. A check in this box will cause the Select Sales Type Popup to display the first time a payment is added to a transaction. See Compulsory Sales Type under the Start of Transaction tab in the previous section. Confirm Sales Type on Save. A check in this box will cause the Select Sales Type Popup to display when any of the button types FIFO Store, "Send" or "Print and Send" are touched. Disallow Print Partial Fixed Menu. If this box is checked, the point-of-sale software will not allow a guest check to be printed if the check includes Fixed Menu Items which have not completed all selections which are included with the meal. Fixed Menu Items are discussed in a separate section of this document. Prompt If Open Checks. This flag pertains to a very particular use of the terminal, one where POS Operators are being used as Shifts. With this flag set as a Yes, when the Cancel button is touched on the Table Desktop, the software will prompt Do You Want To Continue? if any other POS Operators have open checks. Generally, DO NOT check this flag. There is a related flag under the Start Of Transaction Tab. Spotter Screen Timeout. Pertains to the display of a large popup display window immediately after an order is paid, displaying the amount and number of items for use by a spotter. Enter 0 to disable this functionality or the number of seconds the window will display to enable. Cafeteria Mode Operations This is a new functionality with the March, 2005 release of the Odyssey Suite. It is intended for use not only in cafeteria operations but also in counter service operations where multiple patrons are placing orders which will be paid together, after the last patron's portion of the order is entered. This mode is established, in conjunction with the use of Button Type Add Seat, when the flag "Cafeteria Mode with Seat Button" is checked in POS Terminal Options Transaction Options, on the Start of Transaction Tab. The mode provides for: An accurate and automatic customer, or tray, count. A clear display to the POS Operator of the current portion of the order, with the easy ability to view the entire order as well. Immediate requisition, both to printers and OrderVideo Display stations, after each portion of the overall order when the Seat/Tray button is touched. All items may be sent to the receipt printer at this Odyssey/BackOffice Suite Programming POS/2100 Configuration 139

140 time to act as a pickup "chit" for the current customer. A "stub receipt" may also be generated which includes a tray subtotal, approximate tax and total. Print options to automatically provide a "by-tray" receipt at payment time. Customer (Tray) Count The POS/2100 software will automatically increment the customer (cover or tray) count when in Cafeteria Mode. In the section POS Terminal Options Transaction Options, Start of Transaction Tab, in addition to setting the flag "Cafeteria Mode with Seat Button", the flag "Allow Zero Cover Entry" should be checked. In the section POS System Options Miscellaneous, the flag "Add to Covers by Item Only" should NOT be checked. The POS Operator has the option of beginning the transaction by depressing the Seat (Tray) button or merely beginning the order entry process. Either way, the customer count will be a one after the first item for the seat (tray) is entered. When the Seat/Tray button is touched again, the customer count will automatically increment for the next seat (tray). Tray Count Seconds In either a cafeteria operation or in a counter service operation there will generally NOT be a Button Type Covers Entry on any Sales Desktop. The customer count will be determined automatically as outlined in the previous section. In many cafeteria operations, however, a patron may come back for "seconds". This should not increment the customer (tray) count. To accomplish this, place the Covers Entry button on a sales desktop and enter Auxiliary Text of "0". This will accomplish the same function as if the POS Operator had touched "0" then the cover button. Of course, the button text should be "SECONDS" and not "COVERS". On Screen Guest Check Display in Cafeteria Mode There is a separate entry in the Language database for display on-screen in conjunction with Button Type Seat Number when in Cafeteria Mode. The default entry in the Language database is "TRAY" rather than the "standard" display of "SEAT". (The Button Type, however, is the same "ADD SEAT".) As soon as the Seat/Tray button is touched a second time, the operation is exactly the same as if the POS Operator had performed the following manual touch operations: Touched the Send Button. This cause the requisition of the current portion of the order on both printers and OrderVideo displays. Recalled the order. The next Seat/Tray would already be displayed. Touched 2, then Button Type Covers entry. (Of course, the numeric entry is dependent on the number of times the Seat Number button has already been used.) Touched the top of the guest check display, to only display the current portion of the order. The top portion of the on-screen guest check display, after the third time the Seat Number button has been depressed, is shown below. The POS Operator is shown that the current entry is for the third tray and the current customer count is POS/2100 Configuration Odyssey/BackOffice Suite Programming

141 The bottom portion of the on-screen guest check display, after the third time the Seat Number button has been depressed, is shown below. The order total of $10.91 reflects the total of trays 1 and 2. The item count is for the current tray and is zero, since no items have yet been entered for Tray 3. To view the entire order, the POS Operator merely touches the header portion of the on-screen display, where the time, POS Operator, check number and number of customers is shown. The on-screen guest check display is shown below, after the POS Operator has touched the very top portion of the guest check display, to show all seats (trays) on the current order. The amount due remains the same, $10.91 for the entire order. The item count now reflects all items on the current order. To return to a view of only the current portion of the order (the current tray) the POS Operator merely again touches the header portion of the on-screen display, where the time, POS Operator, check number and number of customers is shown. NO TE: There is a separate entry in the Language database for display on-screen in conjunction with Button Type Seat Number when in Cafeteria Mode. The default entry in the Language database is "TRAY" rather than the "standard" display of "SEAT". This entry controls both the on-screen display sho wn above and the subtotal line printed if the receipt is "by-seat". With n o items entered for the current tray, touching the Seat (Tray) button again does not perform any operation. The software will not allow for an "empty" tray. Touching a number, followed by touching the Seat (Tray) button, is just as if only the Seat (Tray) button had been touched. The numeric entry is ignored in Cafeteria Mode. You can not "skip" a tray in Cafeteria Mode. If Button Type Transaction Cancel is touched, only the current portion (the current) tray will be removed since all previous tray totals have already been requisitioned. The customer count will NOT include the last, empty, tray. Odyssey/BackOffice Suite Programming POS/2100 Configuration 141

142 Requisition Functionality in Cafeteria Mode The requisition process is accomplished when the Seat (Tray) button is depressed. For OrderVideo requisition, the "on the fly" functionality can also be implemented, so that the individual items of each portion of the overall order are displayed on the OrderVideo screen as the "next item after" is entered on the POS termina l. Referring to the section which outlines the file RQV.INI, which determines how the OrderVideo displays operate, you will also have established CheckMode = 0 in Cafeteria Mode Operation. New items, for the separate trays on the order, will be the only items which display. When the particular "tray" portion of the overall order is displayed, it will occupy a separate "box" on the OrderVideo dis play. The Order Number displayed will have a dash, followed by the tray number. There are two forms of a receipt or chit which can be pr ovided to each individual patron on an order placed in Cafeteria mode. You can print a requisition "chit" after each tray to hand to the customer to act as a "claim" chit if this functionality is required. Simply program each a nd every item to associate with a Sale Type/Output Group which includes the receipt printer. If you want to provide each patron with a form of an actual receipt, set the flag "Print Full Detail on Send" programmed in Printer Configuration Terminal Print Options on the Check 1 Tab. With Cafeteria Mode enabled, this will print only the items on the most recent Seat (Tray) and not all items on the entire order, i.e. items from previous trays. The receipt will include a "TRAY Subtotal", a tax amount and a "TOTAL" line. Receipt Printing at Payment in Cafeteria Mode When the overall order is actually paid, you have the option of generating a "normal" receipt, with items consolidated, or a "by-tray" receipt. To enable the "by-tray" receipt, set the flag "By Seat Print at EOS" on the programming screen Printer Configuration Terminal Print Options, Check 1 Tab. This flag will cause a memo total amount to print for each Seat (Tray) when the receipt is generated at the end of sale if the flag "Print Check At EOS" is also set. NOTE: There is a separate entry in the Language database which controls the line printed on the receip t if it is "by-seat". The default entry in the Language database is "TRAY" rather than the "standard" display of "SEAT". This entry also controls the on-screen display shown in the previous section. OPOS Drivers Using with POS/2100 The POS/2100 software supports the use of OPOS drivers for the following peripherals: Customer Display (2 X 20) Magnetic Card Reader Cash Drawer 1 Cash Drawer 2 If the POS/2100 software is operating on an Odyssey terminal, there is no need to use OPOS drivers. The point-of-sale application software has built-in direct support for these peripherals. However, the appropriate OPO S drivers are installed when the installation program installs the POS program. For har dware other than the Odyssey terminal, it is recommended that you use the OPOS drivers provided by the terminal manufacturer. Manufacturers often change the internal configuration of their hardware and such changes are often not compatible with prior versions of the hardware. The changes are, however, incorporated into the compatible OPOS drivers which should be available from the manufacturer. To use the OPOS drivers with the POS/2100 software: 142 POS/2100 Configuration Odyssey/BackOffice Suite Programming

143 Follow the manufacturers instructions for installation of the OPOS drivers appropriate for the terminal. The POS/2100 software requires a fixed Logical Device Name for each supported peripheral. The OPOS driver installation software will allow you to establish this name during the installation process. Enabling the use of the OPOS drivers from within the Odyssey programming application only requires a check mark in the box labeled "Use OPOS Drivers" for each peripheral. The Logical Device Names for each of the supported peripherals is shown in the following table. Supported Peripheral Customer Display Magnetic Card Reader Cash Drawer 1 Cash Drawer 2 Display1 MSR1 Drawer1 Drawer2 Logical Device Name PO S Terminal Options I/O Devices The entries here pertain to any attached cash drawer or customer display on the selected terminal. Two tabs, one for an attached scale and another for miscellaneous, are grayed out and are not implemented as of the date of this documentation. I/O Devices Cash Drawer Tab There are two primary sections on this tab, one for a single cash drawer and another for instances where there are two cash drawers. The selection is from a drop down list. No Cash Drawer. Select this if no cash drawer is attached to the selected terminal. Flytech. Select this for the Flytech POS Terminal. ITP. The POS/2100 supports the separate cash drawer port for older generation itp terminals. Odyssey. The POS/2100 supports the separate cash drawer port on both the Odyssey 450 and Pentium III. Select the correct terminal if there is a cash drawer attached to an Odyssey. Printer. Check this box if there is a cash drawer attached to a printer which is attached directly to this terminal. OPOS. Check this box if you have installed the OPOS Drivers for the hardware and established the Logical Device Names of Drawer1 and Drawer2. Note that the choices above are mutually exclusive and the software will only allow one of the choices to be selected. Check For Open Drawer. This selection only applies if there is a check next to Odyssey in the previous selection area. With a check in this box the software will prompt the POS Operator to close the attached cash drawer if it is open. The prompt can only be dismissed when the drawer is closed or through the entry of an authorized POS Operator s number. Only Open Drawer At Zero Balance. Place a check here to delay drawer opening until the balance due is less than or equal to $.00. Otherwise the drawer fires on the first payment media set with the flag Open Drawer as true. Settlement Operator Required. New with February of 2007 release. A check here will force the assignment of a particular POS Operator to any cash drawer attached to the terminal. The drawer programming of the POS Operator is overridden if this flag is set. A Manager must assign a POS Operator to a cash drawer before the cash drawer can be opened. Other POS Operators may use the terminal to enter sales, but only the Settlement Operator can use any button that opens the cash drawer. If the actual Settlement Operator has forgotten to ask the Manager to assign the drawer or if the current Settlement Operator assigned is wrong, a prompting message appears when the button is touched, providing an opportunity for the Manager to correctly assign the Settlement Operator. Odyssey/BackOffice Suite Programming POS/2100 Configuration 143

144 I/O Devices Display Tab The entries apply to the RS-232 customer display. Currently, the POS/2100 software only supports the customer display shipped with the Odyssey series of hardware. The display is available either directly attached to the Odyssey terminal or as a separate pole mount. Remote Display Port. Enter the COM port to which the customer display is attached. For Odyssey terminals, enter a 4. (This entry will be changed if you select OPOS Display Active in the next entry.) OPOS Display Active. Place a check box here if you have installed the appropriate OPOS drivers and have established a Logical Device Name of Display1. You must still place a check in each of the following two boxes, however, to inform the software that there is, in fact, an attached display, even if the actual connection to the customer display is USB, parallel or any other connection methodology. Firich Display Active. If you have a customer display attached, place a check in this box. RS-232 Display Active. If you have a customer display attached, place a check in this box. RS-232 Display Amount. Two lines are displayed on the customer display. The top line can include the price of the item entered along with as much of the descriptor as will fit in the remaining twenty characters of the line. Place a check in this box to display both the descriptor and the price. With no check, only the descriptor will appear on the first line. The second line is a running subtotal of the transaction, including any tax amounts. RS-232 Message Delay. This entry is not implemented as of this date. Rotating Message. Between transactions, the POS/2100 will scroll through the 100 characters which are entered here. I/O Devices Scale Tab The entries here only apply to an attached RS-232 scale. Scales must be identified under POS System Options Scale Definitions to be associated with a terminal. You can use a manual Scale Button on the point-of-sale terminal with no entries herein. Scale ID. If an RS-232 scale is attached to this terminal, select the Scale Name using the dropdown window. If no scale is attached, depress the Del button while any text in this window is highlighted. Scale Port. If you have a scale attached, enter the COM port to which the scale is attached. The port settings of the selected COM port must match the programming of the NCI scale. You will need the NCI manual to confirm the port settings of the scale itself. The scale should be set as type "NCI" and NOT as type "ECR". The default for these scales is usually 9600, 7, E, 1. To place the NCI scale into Menu Mode, you will need access to the dipswitch settings. Usually, dipswitch 4 is used. There are two buttons on the front of the scale which are used to navigate through this programming process. To download the User's Manual for the NCI 6700 Series of scales, access the web site com/ncipos/nciprod.htm, or the Comtrex ftp site for documentation at ftp:/ /comtrex.com/pos2100/documentation/pdf%20files/. I/O Devices Bar Disp Tab The entries here apply only to an attached Liquor dispenser and the associated interface software. Bar Dispenser Enabled. Place a check mark in this box if there is a Berg or EasyBar Liquor dispenser connected to this terminal. Bar Dispenser ID. The POS System supports three different versions of the Berg Liquor dispenser system software, however, it is recommended that you select "Berg Generic". This will cause the selected COM port to be automatically configured by the POS software as 2400 BAUD, no parity, 8 databits, 1 stop bit and use a STX character at the beginning of transmission and an LRC followed by an ETX character at the end. For EasyBar, select EasyBar 9600 for 9600, 8, N, 1, 144 POS/2100 Configuration Odyssey/BackOffice Suite Programming

145 Bar Dispenser Port. Enter the COM Port number to which the interface is connected. Bar Dispenser List File ID. Use the drop down listing to select the List File of items dispensed by the Berg system. Menu Item If No Match. One of the menu items in the list file MUST BE an "open" department. This is the item which will be rung if the dispenser interface sends over a menu item number which does not have a match in the List File. Make sure this is a prompt for price, $0.00 amount POSItem. Price No Match. For non-matched items, you have two choices. Enter a.00 here and the POS Operator will be prompted to enter the correct price for the drink just dispensed. Otherwise, enter the "default" (absolute minimum price for any dispensed drink) price to be charged. Entering a default price helps to prevent theft while still speeding service to the customer. I/O Devices Misc Devices The only current entry here pertains to an optional RS-232C, Telequip Transact 2 Coin Dispenser. This is the only supported coin changer. Coin Changer Active. Only place a check mark here if you have a coin changer attached to the POS terminal. Coin Changer Port. If you have a coin changer attached, enter the COM port to which the coin changer is attached. Caller ID Path. If you are implementing CallerID with this system, enter the path G:\icom\POS2100. If you are not implementing CallerID, blank out this field. For a detailed explanation of how CallerID works with the POS/2100, refer to the section Using CallerID With Delivery. Magnetic Card Reader. This dropdown provides three choices. The standard is Wedge. The Codexxa uses COM2, 9600, O, 7, 1. OPOS requires installation of the appropriate OPOS drivers and establishment of a Logical Device Name of MSR1 for the magnetic card reader. Security Output Type. Typically "None". The dropdown allows a selection of "XML-ezUniverse", or Electronic Journal. For the Electronic Journal option, the file will be stored as JRNL_001_ TXT, where "001" is the store number and the date of the current Sales Day as shown is March 27, There will, therefore, always be one file for each Sales Day in which there was POS activity. Security Output Path. Typically left blank. Only meaningful if a Security Output Type is selected above. For an ezuniverse implementation, this is where the URL of the ftp site would be entered. XML Fiscal Printer. Typically left unchecked. A check mark creates an XML file when a guest check is closed for use in integrating with fiscal printers, currently only in Poland. This file (FiscalPrinter.xml) is written to a fixed folder, G:\FiscalPrinter. In the Polish use, this file is deleted by the software which is extracting the information to be directed to the fiscal printer. Another use of this file is to interact with various BackOffice software modules, currently in France. When the EOD is performed, if the file G:\FiscalPrinter\FiscalPrinter.xml exists, it will be automatically renamed as 1_37_ XML, where "1" is the store number, "37" is the Sales Day and the date of the Sales Day as shown is March 27, FTP Protocol Active. Typically left unchecked. Used in conjunction with ezuniverse in-store controller. Only place a check here if you are installing an ezconnect surveillance system. FTP User Name. Used in conjunction with FTP Protocol Active as a Yes. Contact Comtrex support for information. FTP Password. Used in conjunction with FTP Protocol Active as a Yes. Contact Comtrex support for information. NOTE: The five selections for Security Output and FTP pertain to an integration with ezconnect. Security/Surveillance System Interface The POS/2100 provides a means to supply transaction information to a security/surveillance system in order to overlay this information on a video display which shows the POS Operator and customer during the transaction along with the surroundings of the POS terminal. This transaction information differs from a mere Odyssey/BackOffice Suite Programming POS/2100 Configuration 145

146 receipt because the error corrected items are required in order to detect fraud on the part of the POS Operator. The initial implementation of this interface is with the ezconnect system from ezuniverse. This system requires a high speed Internet connection. The minimum in-store solution includes a central piece of hardwar e with storage and then some cameras, typically one for each POS terminal and two or three focused on other customer or back office locations. The cameras are wireless, IP based and route to the on-site HDD where the video is stored. Real-time video is also available over the Internet. A file, or group of packet, are created by the POS, which include "keystroke equivalent" information, i.e. all of the error corrects that normally do not show up on a receipt. The packets are moved over the Internet to a remote Server (an ftp site at the ezuniverse location) which catalogs them by terminal, date/time and also analyzes the information based on predetermined "triggers". An example of a trigger might be a transaction where the final amount paid was less than the total of the error corrects on the transaction. An owner, manager or other "enabled" individual has a bo dy of software on their PC which can connect over the Internet to the database maintain ed at the central Server, to the store and/or to both simultaneously. What can be displayed on the screen is a display of all the trigger events at each of the stores or a single store, either from yesterday, over a selected past time period or for today only. By clicking on a trigger event, you can then view the video related to that trigger event. For a POS transaction, you see the transaction detail as entered by the operator alongside the video of the POS O perator, the customer and anyone else in view. The idea is that no one has the time to view stored raw data. You want to view "suspicious" transactions or events. The triggers are a way of defining suspicious. Of course you can create trigger events after the fact because the raw transaction data is stored on a Server. There are two types of information packets created, a com ma separated file and an XML format file. In each case, a separate file is created for each transaction. Creating a separate file for each transaction eliminates any possibility of a "sharing" collision where the security/surveillance software is attempting to read then delete a file while the POS/ 2100 software is writing to the same file. Security Output File Naming Convention The file names created for the ezun iverse Security Output follow a naming convention as follows: EzUxx-yyyy.xml Where "xx" represents the two digit terminal number for the transaction. Where "yyyy" represents a four digit sequential number for the transaction on the designated terminal. (NOTE: This transaction number is not related to the transaction number stored in TransactionHeader and TransactionDetails and reported by the BackOffice Reporting software.) Security Output File csv Format Each line in the csv file begins with the terminal number and is followed immediately by a tag which defines the line. The only lines not related to items on the guest check are the two lines with a "HDR" and a "TRL" tag. These are the HEADER and TR AILER lines that bracket the transaction itself. 146 POS/2100 Configuration Odyssey/BackOffice Suite Programming

147 Security Output File Tag Formats Each line in the csv file is identified with a tag. The same tag is used in the xml file in a different format. Tag Description Actual Tag Comment Header HDR Only used in csv model. Trailer TRL Only used in csv model. Menu Item (PLU) PLU Sale Item Modifier/Descriptor (Condiment) DCM Also a Sale Item Finalize or Payment Media FIN Media or Sales Item Offset Foreign Finalize or Payment Media FFI Media or Sales Item Offset Paid Out at POS PDO Media or Sales Item Offset VOID VOD Media or Sales Item Offset Error Correct ECT Media or Sales Item Offset Line Item Coupon CPN Media or Sales Item Offset Line Item Discount LID Media or Sales Item Offset Item Discount (Group or Subtotal) ITD Media or Sales Item Offset Dollar Amount Discount DOD Media or Sales Item Offset Service Charge SVC Media or Sales Item Offset TIP TIP Media or Sales Item Offset Tips Paid To Server Amount TPD Media or Sales Item Offset Refund Item REF Media or Sales Item Offset Waste Item WST Media or Sales Item Offset Overring Item OVR Media or Sales Item Offset Tax (Add-on US Type) TAX Media or Sales Item Offset Value Added Tax VAT Media or Sales Item Offset Open Guest Check OPN Transaction Type Middle Round of Guest Check MRD Transaction Type Close Guest Check (Pay Off) CLO Transaction Type Single Round (Cash Bar Transaction) SRD Transaction Type Paid Out Operation PDO Transaction Type Receive On Account Operation ROA Transaction Type Refund Operation REF Transaction Type Overring Operation OVR Transaction Type Modify Payment Operation MPA Transaction Type Sales Type Number XML Only Identifier Sales Type Name XML Only Identifier Unique ID XML Only Identifier within transaction Parent Unique ID XML Only For DCM items, reference to parent's Unique ID Top Parent Unique ID XML Only For DCM items, reference to Menu Item Odyssey/BackOffice Suite Programming POS/2100 Configuration 147

148 Security Output File Sample Transaction The following is a Transaction Detail rendering of the sample transaction documented in the following two sections. Security Output File Sample XML File The following is the XML file created as a result of the prior transaction. <?xml version="1.0"?> <Stream> <Transaction Type="SRD"> <TerminalNumber>1</TerminalNumber> <CheckNumber>28</CheckNumber> <OperatorID>2</OperatorID> <OperatorName>Bobby B.</OperatorName> <DateOpened>10/12/2005</DateOpened> <TimeOpened>9:15:23 AM</TimeOpened> <OpeningBalance>$0.00</OpeningBalance> <Items> <Item Type="PLU"> <Count>1</Count> <Description>Glass Chablis</Description> <Amount>$4.50</Amount> </Item> <Item Type="PLU"> <Count>0</Count> <Description>Glass Chardonnay</Description> <Amount>$0.00</Amount> </Item> </Items> <Offsets> <Offset Type="ECT"> <Count>1</Count> <Description>EC: Glass Chardonnay</Description> <Amount>$4.75</Amount> </Offset> <Offset Type="FIN"> <Count>1</Count> <Description> Cash</Description> 148 POS/2100 Configuration Odyssey/BackOffice Suite Programming

149 <Amount>$4. 81</Amount> </Offset> </Offsets> <Taxes> <Tax Type="TAX"> <Description>NJ State Tax (No Disc)</Description> <Amount>$0.31</Amount> </Tax> </Taxes> <DateClosed>10/12/2005</DateClosed> <TimeClosed>9:15:36 AM</TimeClosed> <ClosingBalance>$0.00</ClosingBalance> </Transaction> </Stream> Security Output File Sample csv File The following is the csv file created as a result of the prior transaction. 1,HDR,SRD,28,2,Bobby B.,10/12/2005,9:15:23 AM,$0.00 1,PLU,1,Glass Chablis,$4.50 1,PLU,0,Glass Chardonnay,$0.00 1,ECT,1,EC: Glass Chardonnay,$4.75 1,FIN,1, Cash,$4.81 1,TAX,NJ State Tax (No Disc),$0.31 1,TRL,28,2,10/12/2005,9:15:36 AM,$0.00 The only supported interface with ezuniverse is the XML implementation. This information is sent to a local folder and processed by a program authored by ezuniverse. This allows for the information to be buffered locally and then sent to the ezuniverse ftp site when the site is available. Berg/EasyBar Liquor Dispensing Interface With the February of 2007 release, the POS/2100 software supports both the Berg Generic and Basic POS Interface specification. With the October of 2009 release, EasyBar support has been added. The pour is initiated using the liquor system. Each drink is assigned a number in the liquor system and this number is transmitted over an RS-232C interface to a connected POS terminal. Each item in the liquor system must be programmed first as a Menu Item, then a POS Item. To eliminate the dual programming on the BackOffice, you should create a separate category for liquor items and have them Auto Create POS Items. It is the Menu Item number which must match the number from the liquor system. EasyBar requires the entry of five digits, e.g. PLU 1 in EasyBar must be Menu Item The POS system will accept a pour indication from the liquor system any time an item could be touched on a Sales Desktop. If the number sent from the liquor system does not match a Menu Item number within the programmed Berg List File, the POS system will either prompt the POS Operator for a price, or ring a predetermined price for mis-matched items. A daily "mis-matched" file will be created for every instance of an item poured by the Berg system for which there is no match in the POS. At the end of day, a list of liquor items sent to the POS, for which there was no match, will automatically on the receipt printer of every POS terminal which has the flag "Bar Dispenser Enabled" set. print Odyssey/BackOffice Suite Programming POS/2100 Configuration 149

150 LCD Customer Display There is no specific programming associated with enabling the LCD Customer Display as an I/O device. The device is an optional peripheral on the P4 Glaive terminal. After installation, go to the Desktop and right click, then select Properties, then the Settings tab. Select Multiple Monitors, then left click on the displayed second monitor then check the box next to Extend my Windows desktop onto this monitor. The display during a transaction will be divided into a left and right side. The left side will show the last item purchased and the price charged, a guest check and the total amount due. The right side is used for suggestive selling prompts. A sample LCD Customer Display is shown below. 150 POS/2100 Configuration Odyssey/BackOffice Suite Programming

151 POS Terminal Options Sale Types Note: This is the same programming selection that is available under Printer Configuration Sales Types/Output Groups The POS/2100 software uses the Sale Type of the transaction to determine what calculations are performed at the end of the transaction and how to route remote requisition printing and Order Video information. In addition to the filter criteria presented on the other programming windows under POS Terminal Options, this programming window requires that each of the three Sales Types be programmed separately. By selecting one or more terminals, you can program the selected Sales Type for more than one terminal. If you use the Copy/Paste functionality available within POS Terminal Options, only the selected single Sales Type will be first copied then pasted. Sale Types Sales Computations Tab Itemizers Calculations such as discounts, service charges, add-on taxes and value added taxes are performed on Itemizers. Every individual POS Item is configured to associate, or not, with each of the up-to sixteen itemizers through the programming under List Files, then POS Programming Itemizers. Names for the sixteen itemizers are established under the selection BackOffice Itemizers selection. The names displayed on this tab are the names established there. A complete discussion of itemizers is available under the above selection. The check marks on this tab either enable or disable any computations for a particular itemizer. For example, if st ate tax is charged on Take Out items but not on Eat In items, then the calculation of tax on the itemizer being used to collect the amount of all taxable items would be disabled in Sales Type Eat In. First, se lect the Sale Type being programmed. Next, place a check mark next to each itemizer where you desire the calculation to be performed on the named itemizer. Sale Types Sales Computations Tab Compulsory Reference/Account Entry With t he June of 2005 release, two options have been moved from POS Terminal Options Transaction Options to the Sales Computations Tab under POS Terminal Options Sales Types. The primary purpose is to allow for mandatory entry of a phone number for a Delivery Sales Type, while not mandating the entry for other sales types. Compulsory Account # Entry. This flag works in conjunction with the following entry, Validate Account. With Validate Account unchecked, a check in this box enables the TABS mode of the terminal. When a new check is started without a Table Number, the POS Operator is prompted to enter up to sixteen characters of the Guest s Name. This name is displayed on the Table Desktop to assist in identifying patrons at the bar. The software WILL NOT prompt for a Guest s Name if the check has been started with a Table Number. You can still enter a Guest Name from a POS2100 Sales Desktop using Button Type Enter Name. Whether the table number and check number or the entered name displays on the Table List Desktop depends on the setting below Display Name in Table/Check List. Validate Account. This flag works in conjunction with the previous entry. With a check in both boxes, the POS software will assume that the compulsory entry is prompting for a valid AccountCharge member in the AccountCharge file. The entry will be checked against the database and if the entry does not match, a sales transaction will not be able to be initiated. With a check in both boxes, the compulsory entry will be prompted for all transactions, including those where a check has been started with a Table Number. Refer to AccountCharge POS/2100 Considerations. Odyssey/BackOffice Suite Programming POS/2100 Configuration 151

152 Sale Types Output Groups 1-4 and 5-8 Tabs Items are routed at the end of a service round or transaction based on the Sale Type. Every individual POS Item is configured to belong to up to 8 Output Groups. An Output Group is a list of up to four printers or Order Video screens. There is a separate listing of the printers and Order Videos in each Output Group for each of the three Sale Types. This way, an Eat In Transaction can cause a requisition chit to print on one printer while a Take Out order can cause a requisition chit to print on a different printer. Prior to making any programming entries here, all printers and Order Videos must have already been program med under Printer Configuration Printer Definitions, because the only selections available are those displayed on a drop down selection list. There is a special configuration pertaining to Order Videos, which allows for changing of the way items are rout ed to Order Videos during the Sales Day. By treating lines 1 and 2 as one set and lines 3 and 4 as another set, you can establish two Order Video Routing Schemes for each of the three Sale Types. This configuration is established on a by-terminal basis and is useful in quick service restaurants. If this is applicable, then lines 1 and 2 of an Output Group can be used with one routing scheme and lines 3 and 4 with an alternate routing scheme. This configuration is discussed in the section under Printer Configuration Terminal Print Options under the Remote Tab section. For each Output Group, use the dropdown list to select the remote printer name or Order Video name to which items associated with the Output Group should be directed. POS Terminal Options Message Prompts This is an area where certain messages and prompts displayed on the point-of-sale terminal may be customized. Most of the selections are for future use, and only the lines listed below are currently being implemented within the POS/2100 software. The programming window shows forty lines of sixteen characters each. Prompts 4 and 5. These thirty-two characters are shown in the banner display at the top of the Log In screen. The default entry is Enter Operator Number Prompts 11 and 12. These thirty two characters are shown in the banner display at the top of all Sales Desktop screens prior to an item being purchased. POS Terminal Options Desktop Options The programming here acts as steering logic for operation of the point-of-sale software. This programming is interactive with the programming performed through the POS/2100 application program and should be postponed until the actual point-of-sale Desktops are configured. NO TE : Usually when POS Terminal Options are being initially configured, the POS/2100 database is NOT defined. If you are configuring the Sales Desktop on a by-pos Operator basis, you will need to revisit this screen after you have completed all Desktop programming for the POS/2100. Default Sales Desktop. This entry defines the default Sales Desktop for the Terminal. The default Sales Desktop is the one presented to the operator when a transaction is begun and when a guest check is retrieved for an additional service round. As defined by the selection below, the Default Sales Desktop can be configured either on a by-terminal basis or a by-operator basis. Default Log In Desktop. This entry defines the default screen presented when the point-of-sale software requires the entry of a POS Operator s identifying number. Closed Check Desktop. This entry defines the Sales Desktop presented to the POS Operator when a guest check is selected from the Closed Check Screen. A closed check may be selected to change payment methods or for voiding/refunding the entire guest check. Generally this will be the Payment Desktop or it could be a custom Desktop only accessible from the Closed Check Screen. Display Message Board At Log In. The Message Board functionality of the POS/2100 software provides the ability to list specials for the day as well as to communicate private messages to individual POS Operators. It also provides an access point to list any items which are either in limited 152 POS/2100 Configuration Odyssey/BackOffice Suite Programming

153 supply or are already unavailable. With a check in this box, the Message Board will be automatically displayed, after a ten second waiting period, whenever the Log In screen is presented. Manager Required For Table Section. Pertains to changing the table layout on the Table Desktop. If checked, only a Manager can change the table layout for a POS Operator. Two Screen Table Desktop. A check mark here enables two separate Table Desktops. The POS Operator can switch between the two by touching his/her name at the top left of the screen. One Table Desktop is a large table section, taking the entire screen. The other is a check listing which displays key information from the check header including # guests, check amount and the number of times the check has been printed. Checks may be sorted on this display by touching header text. Display FIFO On Table Desktop. This option is for a drive through terminal where the POS screen will be used as a requisition screen. It works in conjunction with the above setting for a two screen table desktop and also would require the End Of Sale Desktop to be Table Selections. With all of these set, the last four entries in the FIFO buffer will display on the Table Selection. Touching any displayed Guest Check will immediately move to the Default Sales Desktop on the terminal, which would generally be a Payment Desktop to allow two touch payment of cash. By Operator or By Terminal. Select one of these two options to determine if the default Sales Desktop will be determined on a by-operator or by-terminal basis. If on a by-operator basis, the default Sales Desktop is configured under the selection Staff POS Operators with the General Tab. If the default Sales Desktop is set to be by-operator, the automatic shifting of the Sales Desktop is disabled. If you are implementing the Auto Shift feature, set the default Sales Desktop to be byterminal. End Of Sale Desktop. There are two choices for the Desktop presented at the point-of-sale either when the Enter Button is depressed from the Log In screen (or the POS Operator swipes his or her card) or when a guest check has been sent or paid in full. Check the box next to Default Sales Desktop for quick service. For pre-check situations, and for bar operation with TABS mode, check the box next to Table Selections. Even if you have a check mark next to Default Sales Desktop, the Table Selections Desktop can be accessed from any Sales Desktop if the appropriate button is on the Sales Desktop and the terminal is not in the middle of a sales transaction. Table Desktop. There are two optional buttons which may be configured to appear on the Table Desktop. Generally, only one of these buttons will be configured to appear on the Table Desktop of a particular terminal. These two are Button Type Transfer Checks and Button Type Transfer Delivery Checks. On the programming screen, these two buttons are identified as "Server Transfer Button" and "Delivery Transfer Button". These two Button Types may also be placed on the Log In Desktop through POS/2100 programming. Particularly for Delivery applications, it may make for a more fluid operation to place the Button Type Transfer Delivery Checks on the Table Desktop. POS Terminal Options Auto Shifts This programming window provides the ability for terminals to automatically shift from the default Sales Desktop, Price Level or Sales Type both by time and by day-of-week. Each terminal can be configured with up to fourteen (14) automatic shifts, with each shift including a start time, stop time and a list of the days-ofthe week for which the Auto Shift is valid. If the default Sales Desktop is set to be by-operator, automatic shifting of the Sales Desktop is disabled. If you are implementing Auto Shifts, set the default Sales Desktop to be by-terminal. Auto Shift Selection. Use the dropdown list to select from Auto Shift 1 through Auto Shift 14. Time Of Day Start. Use the dropdown list to select the starting time of day for this shift, or enter the time in military format. The starting time is limited to fifteen minute increments. Time Of Day End. Use the dropdown list to select the ending time of day for this shift, or enter the time in military format. The ending time is limited to fifteen minute increments. When the shift is Odyssey/BackOffice Suite Programming POS/2100 Configuration 153

154 complete, if there is no other Auto Shift scheduled to begin at the same time, all entries set below will revert to the default values for the terminal. Sales Desktop. Choose a Sales Desktop from the dropdown list. The listed Sales Desktops will be those which have already been programmed using the POS/2100 application programming. If you do not wish to switch Sales Desktops during this Auto Shift, select any Sales Desktop, highlight the entry line, then touch delete, leaving the entry window blank. This Auto Shift will then only affect either POS Price Level or Sales Type. The default Sales Desktop for a terminal is either on a by-terminal or by-pos Operator basis. Having an Auto Shift affect the Sales Desktop only makes sense if the default Sales Desktop is by-terminal. The default Sales Desktop, and the by-terminal or by-pos Operator selection for the Sales Desktop, for each terminal is established under POS Terminal Options Desktop Options. Price Level. Choose the POS Price Level to be activated, from Price Level 1 through Price Level 6. If you do not wish to switch POS Price Level during this Auto Shift, select any POS Price Level, highlight the entry line, then touch delete, leaving the entry window blank. This Auto Shift will then only affect either the Sales Desktop or Sales Type. The default POS Price Level for each terminal is established under POS Terminal Options Miscellaneous, in the section Price Level and Menu Level Options. Sales Type. Choose the Sales Type from the list of the three available Sales Types. If you do not wish to switch the Sales Type during this Auto Shift, select any Sales Type, highlight the entry line, then touch delete, leaving the entry window blank. This Auto Shift will then only affect either the Sales Desktop or the POS Price Level. The default Sales Type for each terminal is established under POS Terminal Options Transaction Options on the Start of Transaction Tab. Auto Discount Media. As an alternative to switching price levels during an Auto Shift, this selection can be used to automatically apply a discount to each transaction during the selected Auto Shift. The discount selected should be a subtotal percentage discount, taken either on a by-item basis or on an itemizer. Days Valid. Place a check mark next to each day-of-the week where the selected Auto Shift should be implemented. PO S Terminal Options Miscellaneous Under the Media Options selection: Apply Auto Tip Or Service. Check this box if you wish to automatically charge either a Tip/Gratuity or a Service Charge based on the number of guests or covers. Auto Is Tip Type. Check this box if the automatically applied amount is a Tip/Gratuity. Leave the box unchecked if the automatically applied amount is a Service Charge. Auto Tip Media Number. If the automatically applied amount is a Tip/Gratuity, select the media to be applied from the dropdown list of all Tip/Gratuity medias. The media selected must be programmed as a preset percentage. With a check mark in the Auto Is Tip Type box, the software does not even evaluate the entry under Auto Service Media Number. Auto Discount Media Number. This entry will cause a discount to be added to each and every transaction on the terminal. The discount selected should be a subtotal percentage discount, taken either on a by-item basis or on an itemizer. Typically there will be no entry here and this entry is for use by a Manager in extraordinary circumstances. A more common use of an Auto Discount Media Number is on an Auto Shift basis, as explained in the previous section. Auto Service Media Number. If the automatically applied amount is a Service Charge, select the media to be applied from the dropdown list of all Service Charge medias. The media must be programmed as a preset percentage. With no check mark in the Auto Is Tip Type box, the software does not evaluate the entry under Auto Tip Media Number. Auto Cover Charge Media. Use to add a fixed amount per person to the guest check. Select a fixed amount service charge for this media. If a fixed amount service charge is entered here, an amount equal to the extension of the number of guests and the fixed amount is added to the check. The amount is updated if the number of guests is changed. The entry can be removed at payment time, however, if the amount is removed and the guest check is serviced, it will be automatically added 154 POS/2100 Configuration Odyssey/BackOffice Suite Programming

155 again the next time the check is retrieved. This amount is separate from the Auto Gratuity/Service Charge, i.e. both amounts may be added to the guest check. Covers Required For Auto Gratuity. Enter the number of guests where you want the automatic gratuity to be automatically added, e.g. more than five guests will initiate a 15% Service Charge should have an entry of 6. Under the Price Level and Menu Level Options selection: Auto Level Shift Active. This flag is not implemented. Auto Price Level For Cmts. This flag is not implemented. Menu Price Level For Cmts. This flag is not implemented. Default Price Level. Select the default Price Level for the terminal from the dropdown of Price Level 1 through 6. Under the Misc. Options selection: Recall By Terminal Only. This check box pertains to the operation of the Store and Recall function buttons on this terminal. If you wish the Store a nd Recall to be limited only to those orders entered on this terminal, place a check in the box. If the orders stored can be later recalled from any terminal in the point-of-sale network, leave the box unch ecked. Store and Recall must be active in the system. Odyssey/BackOffice Suite Programming POS/2100 Configuration 155

156 Inventory Selections Inventory Options This is a main configuration relating to inventory functions. Under the Miscellaneous section: FIFO. This is the recommended implementation of Inventory, costing on a first-in, first-out basis. With no check mark here, the Inventory module will use a standard costing pricing model on inventory. However, even with FIFO checked, the inventory cost reports will always provide two inventory costs, a true FIFO cost and a Last Purchased cost. This Last Purchased is what most quick service establishments that operate under a standard cost model actually use, since the standard cost is updated immediately upon receipt of inventory at a new price. Process PO Receipts Immedia tely. This flag is not implemented. Receipts against a Purchase Order must be processed from the Process screen within Odyssey/MWS. Process Local Purchases Immediately. This flag is not implemented. Receipts entered through the Transfer Process of Odyssey/MWS where local purchases of inventory are entered must be processed from the Process screen within Odyssey/MWS. Process R aw Waste Immediately. Place a check mark here is you wish to affect the on-hand inventory quantities immediately after entering raw waste amounts. With no check, these inventory movements must be processed from the Process screen within Odyssey/MWS. Process Finished Goods Waste Immediately. Place a check mark here is you wish to affect the on-hand inventory quantities immediately after entering finished goods waste amounts. With no check, these inventory movements must be processed from the Process screen within Odyssey/MWS. Finished goods waste entered at the point-of-sale is not processed until the entire batch of sales for the day is processed during the End of Day process within Odyssey/MWS. Process Store Transfer In Immediately. This flag is not implemented. Receipts from another store must be processed from the Process screen within Odyssey/MWS. Process Store Transfer Out Immediately. This flag is not implemented. Transfer of inventory to another store must be processed from the Process screen within Odyssey/MWS. Set Negative Quantities To Zero At Count. Normally, you will NOT check this flag. With this flag checked, the software will set the quantity of any inventory item which has been driven negative to zero at the e nd of a count entry, resulting in a favorable count variance and an actual food cost less than the theoretical food cost. If recipes are wrong, a check here will r esult in a correct daily food cost. If receipts have not been entered, a check here w ill shift the actual cost into the next inventory period where the receipts have been entered and a correct physical count has been entered. Purchased Item Price History D ays. Set this to 90 days. This does NOT impact the FIFO costing. Costs associated with inventory items still in stock are retained in the FIFO buffer indefinitely. Under the Order Wizard section: Default Days To Order For. This sets the default number of days to order for with the Order Wizard. The number can always be changed from the Order Wizard screen. Exclude. There are four types of inventory movements, each with a separate flag; Raw Waste, Finished Goods Waste, Quantity Adjustments and Count Variances. A check next to Exclude text means that inventory consumption from this type of inventory movement will be ignored when the Order Wizard is projecting inventory usage for purchasing. 156 Inventory Selections Odyssey/BackOffice Suite Programming

157 Stock Control Areas A Stock Control Area is either a single inventory location, or a group of inventory locations. Odyssey maintains a complete on-hand balance of all inventory items by Stock Control Area. All inventory movements, including receiving inventory, wasting inventory items, transferring inventory items and depleting inventory items through the sales process must be associated with a particular Stock Control Area. Inventory depletion through the sales process is established on a revenue center basis and uses the Stock Type of the inventory item. For example, a large restaurant operates with two separate kitchens, each with their own food stocking areas. Alcoholic beverages are sold from a single bar area with its own stock. A main liquor closet is maintained along with a wine cellar. Each of the two kitchens, the bar, the wine cellar and the main liquor closet are Stock Control Areas. The relationship between the Stock Control Areas and the Inventory Location is shown below. Kitchen 1 Stock Control Area Freezer Walk In 1 Dry Goods 1 Kitche n 2 Walk In 2 Dry Goods 2 Main Liquor Closet Bar Wine Cellar Main Liquor Closet Bar Wine Cellar Inventory Location Odyssey will report the on-hand inventory for each of the five Stock Control Areas. Counting will be accomplished for each of the eight inventory locations. All inventory movements must be associated with one of the five Stock Control Areas. In the example above, there will be no sales depletion from the Main Liquor Closet. That will be handled with Internal Transfers from the Liquor Closet to the Bar. We will show an example in the following section of how to program Odyssey to deplete properly from the remaining four Stock Control Areas. Deleting a Stock Control Area There is a selection available for deleting a Stock Control Area. This selection is provided more as a programmer's convenience than for use in a live installation. All on-hand inventory in a multi-location restaurant is maintained by Stock Control Area. To accomplish this, all inventory movements are also tracked by Stock Control Area. When you delete a Stock Control Area you totally lose the information retained for the Stock Control Area. Because of the database impact of deleting a Stock Control Area, the actual deletion is a process which occurs when the Stock Control Area form is closed, not immediately after the delete selection is checked. To delete a Stock Control Area, check the box next to delete. You are prompted after selecting a Stock Control Area to delete and a confirmation is required. When the form is closed, the deletion process occurs: All Inventory Locations within the deleted Stock Control Area are assigned to the default Stock Control Area. All inventory on-hand within the deleted Stock Control Area is added to the default Stock Control Area. All inventory movements are changed to associate with the default Stock Control Area. Odyssey/BackOffice Suite Programming Inventory Selections 157

158 Stock Types Odyssey supports five Stock Types. Based on the Stock Type of an inventory item, and the revenue center where the menu item whose recipe contains the inventory item was sold, Odyssey Inventory will deplete inventory from a particular Stock Control Area. For inventory items, the Stock Type is therefore more of a "where does it come from" concept than a "what kind of inventory item is this", although the two concepts may be related. Stock Type 5 is a "special" Stock Type. Inventory items with a Stock Type of 5 will deplete from a particular Stock Control Area based on the menu item in whose recipe the inventory item is contained. Based on the example of Stock Control Areas from the previous section, a possible use of Stock Types for the restaurant in the example follows. Stock Type Number 1 Kitchen Item 2 Bar Item 3 Bottle Wine 4 Not Used 5 Special Stock Type Name Food and non-alcoholic beverage inventory items from revenue centers associated with the first kitchen would deplete inventory from that stock control area, as would similar sold from the revenue centers associated with the second kitchen. Liquor inventory items from all revenue centers would be depleted from the single bar stock control area as. Liquor would be stocked to the bar using an internal transfer procedure. Wine will have to be treated specially so all wine bottles will be Stock Type 5. In Revenue Center programming, each Stock Type is associated with a particular Stock Control Area for depletion. To continue with our example, assume there are three Revenue Centers in the restaurant; a Bar Lounge, Upstairs Restaurant and Downstairs Restaurant. All food for the bar comes from the Downstairs Restaurant. The programming for sales depletion by Revenue Center is shown below. Revenue Center Stock Control Area Stock "Kitchen Item" Stock Control Area Stock "Bar Item" Stock Control Area Stock "Bottle Wine" Stock Control Area Stock Type 4 Bar Lounge Kitchen 1 Bar Wine Cellar Not Used Bar Upstairs Restaurant Kitchen 2 Bar Wine Cellar Not Used Downstairs Kitchen 1 Bar Restaurant Stock Control Area Stock "Special" Kitchen 2 Wine Cellar Not Used Kitchen 1 To illustrate the use of Stock Type 5 for Inventory Items, we will "configure" our restaurant to deplete bottles of wine sold at the point of sale directly from the Wine Cellar. Wine sold by the glass will be depleted from the Bar. In this "special" case, the inventory item itself does not define the Stock Control Area for depletion; the menu item does. Therefore, all menu items which are bottles of wine would be assigned as Stock Type 5. Inventory Movement Types There are seventeen types of inventory movement tracked by the Odyssey Inventory Module. Each of these may be selected separately on various Inventory Reports. There is no programming on this screen except for changing the names of the different Inventory Movement Types. Unless you are changing the names due to a foreign language installation, it is highly recommended that you change nothing on this programming screen for support reasons. 158 Inventory Selections Odyssey/BackOffice Suite Programming

159 Inventory Count Frequencies The physical count of inventory ends the Inventory Period. When the count entry screen is accessed in Odyssey Inventory, the operator selects which count frequency to access. The inventory items which will appear on printed count sheets and on the inventory count entry screen depend on which count frequency is selected. Each inventory item is associated with a primary count frequency. The database allows for a second count frequency, the local count frequency, which must be on a more frequent basis than the primary count frequency. This feature is designed to work in conjunction with future corporate database generation functionality, where the headquarters determines the primary count frequency, but the local manager may determine to count certain inventory items on a more frequent basis. Count frequencies are generally also established with a priority level on an ascending basis. For example, a count frequency with a priority level of 2 would include all inventory items with a count frequency of 1 on the count screen and on physical count sheets. Inventory Count Frequency Programming Count Frequency Number. This is merely an identifying number for the count frequency. Use any convention you desire in assigning a Count Frequency. Count Frequency Name. This is a thirty character field. Enter descriptive text for the count frequency, e.g. Daily or Weekly. Priority Level. Enter the appropriate Priority Level for the Count Frequency, according to the functionality defined in the previous section. Exclusive. This is a check mark entry, with Yes as checked. This functionality interacts with Priority Level and is discussed in the following section. Exclusive Inventory Count Frequency Setting the count frequency to be an exclusive count is an override on the functionality which causes all lower priority level count frequencies to be included with a higher level count frequency. Items which are associated with an exclusive count frequency will not appear on the count sheets when a count frequency with the same or a higher priority level is selected. There are two kinds of exclusive count frequencies; those which also have a numeric priority level and those which have a blank, or null, priority level. As one example, there may be several specific items which you wish to count at infrequent or random intervals, in addition to including all the other items scheduled for a periodic count. You would associate these items with a count frequency which was exclusive and also had a numeric priority level. When you select this count frequency, all items associated with count frequencies equal to or less than this count frequency will appear on the count sheets. For instance, if you establish a count frequency of Special Weekly as exclusive with a priority level of 2 and only special items are associated with this count frequency. You have another count frequency of Weekly, which is not exclusive. Select Special Weekly to count your normal weekly items and the special items. Because Special Weekly is exclusive, these items would not appear on the Monthly count sheets. As a second example, there may be a group of items which you wish to only count at certain times, and not be counted with any other count frequencies. If you establish a count frequency as exclusive, then Odyssey Configuration will also allow you to establish the priority level as blank, or null. Inventory items associated with this count frequency can only be counted when the particular count frequency is selected. A use for this kind of count frequency might be the periodic counting of non-food inventory items. Odyssey/BackOffice Suite Programming Inventory Selections 159

160 Inventory Locations Odyssey Inventory uses inventory locations to assist in the physical count of inventory items. The reporting available from the Odyssey Suite in the initial implementation maintains all on-hand, received, sold, wasted and other information pertaining to inventory items on a store basis, not on an inventory location basis. Inventory items are associated with a primary inventory location, however, inventory items may set to be counte d in multiple inventory locations. Location Number. This is merely an identifying number for the Inventory Location. Use any convention you desire in assigning an Inventory Location Number. Location Name. This is a thirty character field. Enter descriptive text for the Inventory Location, e.g. Walk-In Cooler or Dry Goods. Stock Control Area. Select the Stock Control Area with which this location is associated. If you are not using multi-location inventory, leave the entry on the programming form at its default. Inventory Delivery Codes Each inventory item is associated with a delivery code. If the functionality outlined in this section is not applicable, the default database includes a single default delivery code and there is no reason to enter any programming information on this form. The delivery code interacts with the purchasing functionality within Odyssey Inventory. When a purchase order is generated, the required selections include not only a vendor and a delivery date, but also a delivery code. The only items which can be ordered on the purchase order entry screen are those which can be provided by that vendor and which have the selected delivery code. When the Order Wizard within Odyssey Inventory automatically creates purchase orders, it creates those orders using both the primary vendor and the delivery code of inventory items. For items with different delivery codes from the same primary vendor, the Order Wizard will automatically create multiple purchase orders, one for each delivery code, to the same primary vendor. The purpose of delivery codes is to accommodate vendors who deliver different products on different days or with different delivery methods. For example, frozen foods require a different truck than refrigerated foods or dry goods. If your vendors have different delivery dates or delivery methods for different products, the delivery codes can be the key to getting full benefit from the Order Wizard through providing your vendor with separate purchase orders automatically. Delivery Code Number. This is merely an identifying number for the Inventory Delivery Code. Use any convention you desire in assigning an Inventory Delivery Code Number. Delivery Code Name. This is a thirty character text field. Enter descriptive text for the Inventory Delivery Code, e.g. Frozen or Dry Goods. 160 Inventory Selections Odyssey/BackOffice Suite Programming

161 Vendors This is t he programming form on which information pertaining to the suppliers from whom you purchase inventory is entered. Vendor Number 00 is a database default entry and should not be changed or used as a real Vendor. Vendor Programming Configuration Tab Vendor Number. This is a sixteen character text field. Enter a number the store will use to designate a particular vendor. Vendor Name. This is a thirty character text field. Enter the name of the Vendor as you desire it to print on Purchase Orders generated to this Vendor. Customer Number. This is a thirty character text field. Enter a number supplied to you by the Vendor which the Vendor uses to identify the store as a customer. This will print on all Purchase Orders sent to this Vendor. Address. Two thirty character text fields are provided to enter the street address for the Vendor. City. This is a thirty character text field. State. This is a thirty character text field. Postal Code. This is a ten character text field. Phone Number. This is a sixteen character text field for the Vendor s phone number FAX. This is a sixteen character text field for a FAX number for this Vendor. Address. This field related to electronic interaction with this Vendor over the InterNET using a separate body of Comtrex software, FTP Messenger. Do not enter anything in this field without consulting with Comtrex Support. FTP Profile. This field related to electronic interaction with this Vendor over the InterNET using a separate body of Comtrex software, FTP Messenger. Do not enter anything in this field without consulting with Comtrex Support. Vendor Programming Miscellaneous Tab The only active element to be programmed on this tab is the Active check box. You may make a Vendor inactive by removing the check from this box. You will not be able to generate Purchase Orders to a Vendor whom you have made inactive. Vendor Programming Import/Export Tab All entries on this tab relate to electronic interaction with this Vendor over the InterNET using a separate body of Comtrex software, FTP Messenger. Do not enter anything in any of these fields without consulting with Comtrex Support. If there is an entry in either the field Import Vendor Price List or Export Purchase Order, use the cursor to highlight the entire entry and press the Delete key. Inventory Item Class Much like categories and departments for menu items, an inventory item class is a grouping of inventory items used for reporting purposes. Basically, an inventory item class is nothing more than a number and a name, and each inventory item must be linked to an existing inventory item class. An inventory item class has a default delivery code and a default count frequency which is established when you create the inventory item class. When you create a new inventory item which belongs to this inventory item class, these values are inherited from the class. This is designed to speed the process of creating inventory items. Both the delivery code and the count frequency can be changed from the screen which creates new inventory items. Odyssey/BackOffice Suite Programming Inventory Selections 161

162 Item Class Number. This is a sixteen character text field. Enter a number the store will use to designate a particular Item Class. Item Class Name. This is a thirty character text field. Enter the name of the Inventory Item Class. Count Frequency. Use the dropdown to select the default Count Frequency for new inventory items which are associated with this Inventory Item Class. This can be changed from the screen which creates new inventory items. Delivery Code. Use the dropdown to select the default Delivery Code for new inventory items which are associated with this Inventory Item Class. This can be chang ed from the screen which creates new inventory items. No other fields are relevant on this programming form. Vendor Item List The vendor item list is essentially the catalog of all available items from each of your vendors. It describes the product they provide as a vendor part number with a vendor item name, it provides text information on the packaging size and it provides a price for the product provided by the vendor. Until an item in the vendor item list is associated with one of your inventory items, however, it is not a functional part of your Odyssey database. The price established here will be the current price of an inventory item if the Vendor is established as the Primary Vendor in inventory item configuration AND the start date of the price is BEFORE the current Sales Day for Odyssey. A vendor item, i.e. a unique vendor part number from a particular vendor, can be associated with one and only one of your inventory items. An individual inventory item of yours may be associated with different vendor items from the same vendor, or with different vendor items from different vendors. This association is established from the Inventory Item Programming Vendor Items screen. Functionality is included within the Odyssey Suite to import the vendor item list. This includes new items and pricing updates on existing items. This functionality has been implemented with Sygma, using the FTP Messenger component of the Odyssey Suite. With an InterNET connection, the software can automatically retrieve your custom item list from the secure Sygma FTP site on a scheduled basis. New vendor items which have been imported must still be associated with your inventory items in order for the new vendor item to appear on purchase orders to Sygma. Vendor Item List Programming The screenshot below illustrates the programming form for the Vendor Item List. All active Vendors will show in the Vendor List area in the upper left of the screen. The information on the upper right of the screen only applies to Vendors with an electronic integration for importing a price list. To add a new product from the list of products supplied to the store by a particular vendor: 162 Inventory Selections Odyssey/BackOffice Suite Programming

163 Click on the appropriate Vendor from within the Vendor List in the upper left of the screen. When you do so, all products supplied by this vendor which have been previously entered will display in the lower area of the screen, the Vendor Item List area. Either left click on the Add icon below the Vendor List (and immediately above the Vendor Item List) or left click in the bottom row. Enter the information described below. NOTE: There is no entry on this form for either Product # or Product Name. These two fields are provided for reference once an inventory item has been associated with a product from a particular vendor. This association is entered under Inventory Item Programming Vendor Items. Note on the screenshot above that all of the displayed Vendor s products have been associated with an inventory item for this store except for the bottom product, Ground Turkey. Vendor Product Number. This is a sixteen character text field. Enter the number supplied to the store by the Vendor for the Vendor s product. This will be used when generating Purchase Orders to the Vendor. Vendor Product Name. This is a thirty character text field. Enter the name supplied to the store by the Vendor to describe the Vendor s product. This will be used when generating Purchase Orders to the Vendor. Unit of Measure. This is a sixteen character text field. Enter the packaging unit supplied to the store by the Vendor to describe the packaging or unit of measure to be used on Purchase Orders for the Vendor s product. Price. Enter the price charged by this Vendor for this Product when it is ordered in the unit of measure on a Purchase Order. Start Date. The programming provides a default of the current date. You may enter an earlier date. If you enter a later date than the current date, the item can not be ordered on a Purchase Order until the date you enter. When you have entered the last item being added for a particular Vendor, hit the Enter key from the Start Date window, then click on the Undo icon. Vendor Item List A Generic Import Methodology There are two formats currently supported for import into the Vendor Item List table; one from Sygma and another from US Foodservice. As an aid to dealers, the US Foodservice file format is explained in detail here and can be used as a generic import of any vendor's price list. The file name must be OrderGuide.csv. The file must be stored in the folder G:\USFood\In, which is the same as c:\icom\usfood\in. The format of the file is comma separated, with a CR LF at the end of each line. Each line has four fields. A sample file is shown below, as opened in Wordpad.exe. Sample OrderGuide.csv Odyssey/BackOffice Suite Programming Inventory Selections 163

164 The file shown above is not only comma separated, but the fields are fixed width. The fields are as follow: Field Name Field Type Maximum Field Size Vendor Product Number Text 16 characters Vendor Product Name Text 30 characters Unit Invoice Price Currency Unit Invoice Text 16 characters You can use Excel or any other tool to create such a file from the sources available from the Vendor. It is the responsibility of the individual creating the file to assure that the above maximum field sizes are not exceeded. The import will fail should the field sizes be exceeded and any information in the Vendor Item List could be lost. Establish the vendor in Vendor Programming under the Import/Export Tab as shown below: Once you have created the file in the appropriate format and then placed the file in the folder G:\USFood\In, you can use the Vendor Item List programming form to import the price list by clicking the Import button at the top of the screen, as shown below: Receive Reason Codes The text entered here can be accessed through a dropdown list from the Receive Inventory Form within Odyssey/MWS. Typically the text is used to describe a reason an ordered product was not shipped. Reason Code Number. Enter an identifying number for the text. The list of Reason Code Names will be displayed in the sequence defined by this number. Reason Code Name. This is a twenty character text field. Enter the text to display on the Receiver. Inventory Items The terms Inventory Items and Inventory Products are used interchangeably throughout this document. An inventory item is something you purchase from a vendor and use in recipes for menu items. The Odyssey Suite maintains a perpetual inventory, on a store basis, for inventory items. In addition, the Odyssey Suite maintains an Inventory Movement Log which tracks each and every movement of each and every inventory item by the type of movement, including the quantity and the amount. Amounts for all depletion types are maintained on a first-in, first-out (FIFO) basis. 164 Inventory Selections Odyssey/BackOffice Suite Programming

165 Inventory Item Units of Measure There are four standard units of measure which Odyssey Inventory maintains for each inventory item. In addition, you may create as many additional counting units as you desire. All units of measure for an inventory unit and vendor item are related back to on the Recipe_Unit through a conversion factor. The simple formula for the conversion factor for all units of measure within Odyssey Inventory is: How many Recipe_Units are there in this unit of measure?. The balance of this section will explain in detail the units of measure for an example inventory item. The inventory item is Beef, 4 oz. Patty. Recipe_Unit The most basic unit of measure for an inventory item is the Recipe_Unit. Within the database, all tracking of inventory items is stored by this unit of measure. While Odyssey Configuration will allow you to change the Recipe_Unit, this should only be done prior to actual implementation of the system. There is no recovery for any prior period information if you have created an inventory item with an incorrect Recipe_Unit. The Recipe_Unit for our example inventory item of Beef, 4 oz. Patty is the ounce. Since the Recipe_Unit is the most basic unit of measure, the conversion factor for the Recipe_Unit is always a 1. The Recipe_Unit is established in the configuration screen for an inventory item, under the Options tab. As you might have guessed, when you create recipes which use an inventory item, the quantity entered is the number of Recipe_Units of the inventory item which are in the recipe for the menu item. Inventory_Unit The Inventory_Unit is the unit of measure which appears on most reports within Odyssey Reports. It is generally the unit of measure which is counted. When an inventory item is assigned to a primary inventory location, the Inventory_Unit is created within the inventory location as the default Count_Unit. In our e xample, the Inventory_Unit for our example inventory item Beef 4 oz. Patty is the patty (or possibly each ). The conversion factor for the Inventory_Unit in our example is 4. There are four Recipe_Units in our Inventory_Unit. Remember that it is the Recipe_Unit quantity which is entered during the creation of recipes. If we are creating a menu item for a double burger, which uses two of our example inventory item Beef, 4 oz. Patty, then th e quantity entered will be 8 ounces. The Inventory_Unit and its conversion factor are established in the configuration screen for an inventory item, under the Options tab. Invoice_Unit The Invoice_Unit is the unit of measure which appears on the invoice from your vendor. It is also the unit of measure which you, generally, order from your vendor. You will generally be required to use your calculator to determine the conversion factor for Invoice_Units. In our example, assume that we order and receive our inventory item Beef 4 oz. Patty by the case. The case will be our Invoice_Unit. In each case there are four ten-pound packages. Each case therefore contains forty pounds. With 16 ounces in a pound, there are 640 ounces in a case. The conversion factor for the Invoice_Unit in our example is 640. There are six hundred and forty Recipe_Units in our Invoice_Unit. The Invoice_Unit is established in the configuration screen for a Vendor Item. The conversion factor for the Invoice_Unit is established when the vendor item is associated with an inventory item in the configuration screen for an inventory item, under Vendor Items tab. Odyssey/BackOffice Suite Programming Inventory Selections 165

166 Delivery_Unit The Delivery_Unit is a kind of extra standard unit of measure. The most common use is to describe the packaging within an Invoice_Unit. It is also, therefore, commonly used as a counting unit of measure. In our example, we order and receive our inventory item Beef 4 oz. Patty by the case. In each case there are four ten-pound packages. The Package - 10 lb will be our Delivery_Unit. With 16 ounces in a pound, there are 160 ounces in a ten-pound package. The conversion factor for the Delivery_Unit in our example is 160. There are one hundred and sixty Recipe_Units in our Delivery_Unit. Within both the purchase order and the receive functions of Odyssey Inventory, the Search icon allows the operator to view the quantity being ordered or received in either the Invoice_Unit or the Delivery_Unit. This is mer ely as an aid in counting or understanding the order itself. The De livery_unit and its conversion factor are established in the configuration screen for an inventory item, under the Vendor Items tab. Coun t_units Count u nits are a way of saving time for personnel conducting the physical inventory. You must enter a count on t he count sheet. The count is the number of units of measure you are counting. In our example, the default Count_Unit for our inventory item Beef 4 oz. Patty is the patty. If an inventory item exists within your store in several different forms, then you might want to establish Count_Units which are not any of the four standard units of measure. Following our example, the only conceivable additional unit of measure which might possible be established for Beef 4 oz. Patty is the pallet. Our vendor delivers case s to us on pallets, with each pallet holding four cases. The conversion factor for our Count_Unit of the pallet would be 2,560. Count_Units and their conversion factors are established in the configuration screen for an inventory item, under the Location tab. Inventory Item Programming General Tab All existing inventory items are displayed in list box on the left of this screen. The items may be screened by Inventory Item Class using the dropdown at the top of the screen. There is a default inventory item number 00. Do not change this default item. There is no bulk programming available for inventory items, they must be programmed one-at-a-time. There will always be an inventory item highlighted in the list of items on the left of the screen. The displayed information in the five tabs on the right of the programming form corresponds to the highlighted inventory item. As a pro grammer s aid, when you click on the Add icon, all information contained in the General and Options tab for the highlighted inventory item is inherited by the new inventory item. This excludes only the Product Number and Product Name. Creating a new inventory item is a two step process. Select an existing inventory item and click on the Add icon. When you do, only the General Tab, the Options Tab and the Substitution Tab will be available. Enter all information on both the General Tab and the Options Tab, then click on the Save icon. Once you have entered all information on the General Tab and the Options Tab, you will be able to access the Vendor Items and Location Tabs. NOTE: The Substitution Tab was created for a specific customer. It is used to temporarily substitute one of the store s inventory items for an out-of-stock inventory item and is seldom used. 166 Inventory Selections Odyssey/BackOffice Suite Programming

167 Product Number. This is a sixteen character text field. Enter the number used by the store to designate the store s inventory item. This may, or may not, be the same as any particular Vendors Product Number. Of course, while this number may duplicate a Vendor s Product Number, it must be unique within the store. Menu Items and Inventory Items are stored in the same table in the Odyssey database. Therefore you can NOT have an Inventory Item with the same Product Number as a Menu Item Number. Since it is a text field, you can use any convention you desire, i.e. all Menu Items Numbers begin with M and all Product Numbers for all inventory items begin with an I. Product Name. This is a thirty character text field. Enter the name used by the store to describe this inventory item. Remember that you can use both inventory items and menu items in the recipe for a menu item. When you are entering the recipe, the easiest way to add a recipe line item will be to use a dropdown list of names. Both inventory items and available menu items will appear on this dropdown, so try not to use the exact same name for an inventory item as you used for a menu item. If you have followed the Product Number/Menu Item Number convention above, even if you select the wrong one when entering a recipe, the Recipe Item Number will allow you to distinguish. Product Type. This is merely a reference window. All inventory items will be Product Type Inventory Item/Article. Active. If you remove the check from this box, the following field will default to the current date and this item will show in red on all recipe cost presentations of any menu items which include the inventory item in their recipe. The inventory item WILL remain in the recipe. The cost of the item will show on the Flash Report. The item will be depleted from inventory if is included in the recipe of any sales. The inventory item will not appear on any Order Wizard presentations, nor can it be ordered on any Purchase Order. If the inventory item is being replaced, change all recipes to the new inventory item. If the inventory item is simply being removed from all recipes, manually remove the item from all recipes. NOTE: make sure if you are doing central programming that the inactive date is earlier than the real date to prevent the item from being ordered. Date Inactive. If you remove the check from the Active box, this field will default to the current date. It may also be changed, however, the Active box controls the inclusion of the inventory item on any Purchase Orders, even if the Date Inactive is in the future. Item Class. Use the dropdown to associate this inventory item with an Inventory Item Class. Note the entry which will display for new inventory items will have been inherited from the inventory item which was highlighted when the Add icon was clicked. Count Frequency. Use the dropdown to associate this inventory item with a Count Frequency. Note the entry which will display for new inventory items will have been inherited from the inventory item which was highlighted when the Add icon was clicked. Local Count Frequency. Use the dropdown to select the same selection as Count Frequency. Note the entry which will display for new inventory items will have been inherited from the inventory item which was highlighted when the Add icon was clicked. Delivery Code. Use the dropdown to associate this inventory item with a Delivery Code. Note the entry which will display for new inventory items will have been inherited from the inventory item which was highlighted when the Add icon was clicked. Location. Use the dropdown to select a "default" Inventory Location for this inventory item. Note that separate "instances" of the inventory item, in the form of a "count unit" may be placed in alternative Inventory Locations. This is default location and also defines the Stock Control Area into which inventory items are received when a Purchase Order is received. NOTE: In multi-location inventory situations, the default Inventory Location defines the Stock Control Area into which the inventory item will be received when receiving against a Purchase Order. Odyssey/BackOffice Suite Programming Inventory Selections 167

168 No other entries are relevant on this programming form NOTE: You should not click the Save icon until you review/change all entries on the Options Tab. All of the information on the Options Tab will have been inherited from the inventory item which was highlighted when the Add icon was clicked. Inventory Item Programming Options Tab All information contained on this tab for new inventory items will have been inherited from the inventory item which was highlighted when the Add icon was clicked. Inventory Unit Conversion. The Inventory Unit for this inventory item will be displayed in the third window on this screen. If the Inventory Unit is wrong, change it first. The entry here is how many recipe units are in an inventory unit. For example, if the inventory unit is the 4 Oz. Patty, and the recipe unit is the Oz., the entry here is 4. Recipe Unit. Use the dropdown to select from any of the existing recipe units, or enter up to sixteen characters of text to describe the recipe unit. If you are uncertain of what a recipe unit is, refer to the section Recipe_Unit. Inventory Unit. Use the dropdown to select from any of the existing inventory units, or enter up to sixteen characters of text to describe the inventory unit. If you are uncertain of what an inventory unit is, refer to the section Inventory_Unit. Food Cost Type. The functionality for which this dropdown is intended is not implemented within Odyssey Inventory as of the date of this documentation. Leave the selection at its default value. Stock Type. The Stock Type defines from which Stock Control Area this inventory item will be depleted when sold. This is further defined on a by-revenue Center basis. Refer to the discussion under Stock Types in the previous section. If you are not using multi-location inventory, leave the selection at its default value. Yield Percentage. The yield percentage should be entered here if it pertains to the inventory item itself. A yield percentage is also be entered when an inventory item is included in a recipe. The yield entered here acts as a default for the yield of this inventory item when it is used in a recipe. You may change this default yield for the inventory item in a particular recipe. The ONLY yield used is the one entered in the recipe itself. This entry is ONLY A DEFAULT when creating recipes using this inventory item. Yield pertains only to items which may need to be trimmed or which are partially usable, such as a head of lettuce (generally around a 55% yield). In general, leave the default yield of 100%. Food Cost Item. You must place a check in this box if you are going to use this inventory item in any recipes. Inventory items are listed separately on various reports depending on the setting of this check box. An example of an inventory item without a check in this box would be a broom or some other cleaning utensil. The item in included in inventory so that it may be ordered on a Purchase Order, but it should not be included in the regular inventory for costing. Include On Count Sheets. Remove the check from this box if you NEVER want to include this inventory item on ANY printed count sheet. Reorder To Par. Place a check in this box if this inventory item will be ordered from the Par Order Wizard using a Par, or minimum on-hand amount. Par Quantity. Enter the number of inventory units (refer to the section Inventory_Unit) established as the minimum on-hand for use with the Par Order Wizard. For reference, the Inventory_Unit is shown above the field where the Par Quantity is entered. Minimum Order Quantity. Enter the number of invoice units (refer to the section Invoice_Unit) which the standard vendor for this product has established as a minimum quantity to purchase. In general, the Minimum Order Quantity will be one (1) Invoice_Unit. For reference, the Invoice_Unit is shown above the field where the Minimum Order Quantity is entered. NOTE: After you have reviewed all entries on both the General and Options tab, click on the Save icon. The two other relevant tabs, the Vendor Item and Location, will now be accessible for the inventory item. 168 Inventory Selections Odyssey/BackOffice Suite Programming

169 Inventory Item Programming Vendor Items Tab When you create an inventory item, you associate it with a vendor item from the vendor item list. An individual inventory item of yours may be associated with different vendor items from the same vendor, or with different vendor items from different vendors. This is the screen where you associate your inventory items with the items you purchase from your Vendors. There must be one and only one Primary Source for each of your inventory items. The recipe-costing module does not use the FIFO cost of your inventory items. The recipe-costing module uses the most up-to-date cost fo r each inventory item from the Primary Source. This cost is the standard cost for each inventory item. When you access the Vendor Items tab for the first time on a new inventory item it will be empty. A screen shot of the Vendor Items tab is shown below. NOTE: There is a check mark box shown on the screen with the label Standard Vendor. This somewhat of a misnomer. The designation actually pertains to a particular Product supplied by a Vendor and not the Vendor itself. It is possible to associate one of your inventory items with two different products supplied by the same Vendor. This might be due to packaging. However, only one of those can be the Primary Source for your inventory item. This check mark will be automatically made for the first product you associate with an inventory item. It can be changed once you have more than one source. It can not be unchecked. Rather, you select a product from the list at the left of the screen, and check the box for this Vendor Product. The software will automatically remove the check mark from the previous Primary Source. To associate one of your Vendors products with one of your inventory items, follow these steps. Left click on the Add icon at the upper left of the Vendor Items tab. When you do, a line will be added to the list on the left and the cursor will move to the window immediately beneath the Vendor. Use the down arrow at the right of the Vendor window to select the Vendor from the list of all Vendors by clicking on the appropriate name. Move the cursor to the window under V. Product Name. Use the down arrow at the right of the Vendor Product Name window to display a list of products supplied to you by this Vendor which are NOT already associated with one of your inventory items. Remember, you can associate your inventory with multiple sourced, even from the same vendor, but a Vendor s product can only be associated with one and only one of your inventory items. Once you have selected an available product from this Vendor, the field V. Product # will be filled in for reference. This is your Vendor s number for his own product, which may or may not be the same as the store s inventory item product number. The field Order Rank is used by the software as the first sorting criteria on both Purchase Orders and Receivers. After "Order Rank", items are sorted alphabetically. Odyssey/BackOffice Suite Programming Inventory Selections 169

170 Click into the field Inv. Conv. This is where you associate the recipe unit you use for your inventory item with the Invoice Unit which your Vendor ships to you. The Invoice Unit will be the one entered on the Vendor Item List programming form. In the example screen shot, the Meat Supplier wants orders for, and ships and invoices for, forty pound cases of Ground Beef. Our recipe unit is the ounce. With 16 ounces in the pound, the number of recipe units included in the Vendors Invoice Unit is 640. If you are uncertain of your entry, refer to the section Invoice_Units. Use the down arrow to the right of the Delivery Unit to select a Delivery Unit from the existing list, or key in up to a sixteen character text field. For more information on Delivery Units, refer to the section Delivery_Unit. Click into the field Del. Conv.. Enter the number of recipe units in the Delivery Unit. Click on the Save icon within the Vendor Item Tab to save this association. If you have multiple sources for this inventory item, repeat the process. NOTE: It is good practice to click on the Save icon at the top left of the entire Inventory Item Programming form to save these entries prior to accessing the Location Tab. Once you have associated a Vendor Item from a particular Vendor with your store s inventory item, the reference text Product Number and Product Name will display on the Vendor Item List screen documented in a previous section. Inventory Item Programming Location Tab This is the form used to place your inventory items in a particular location, for counting purposes, and to establish count units for the inventory item. Odyssey Inventory uses inventory locations to assist in the physical count of inventory items. The reporting available from the Odyssey Suite maintains all on-hand, received, sold, wasted and other information pertaining to inventory items on a Stock Control Area basis. Inventory items are associated with a primary inventory location, however, inventory items may set to be counted in multiple inventory locations. Inventory items have a primary counting unit which is the Inventory_Unit, however, inventory items may have an unlimited number of counting units established on an inventory location basis. This eliminates the need for personnel to perform manual calculations when entering the physical count, since a particular item might be counted by the case of 374 slices, the package of 187 slices or the individual slice. Each count unit in an inventory location also has an optional shelf location. The shelf location is merely an to assist personnel in locating inventory within the inventory location when performing the physical count. When you access the Location Tab for the first time you will find that an entry already exists. The entry is for the Inventory Unit you entered on the Options Tab. The location is already established as the location you defined when you set the default Inventory Location for the Inventory Item Class with which this inventory item is associated. A screenshot of the Location Tab is shown below. aid NOTE: See also the following section Inventory Item Locations for a faster method of assigning inventory items to multiple locations, particularly in a multi-location inventory environment. 170 Inventory Selections Odyssey/BackOffice Suite Programming

171 If you wish to delete a count unit in a location, highlight the location in the list on the left and click the Delete icon. Note that it certainly possible to have the same location listed twice on the list at the left. For example, you want to count both Patties and Cases, but both are kept in the Walk In Cooler. To add a count unit for a particular inventory item in a particular Inventory Location, follow the steps below. Left click on the Add icon on the Location tab. An identical count unit in the same location will display as the next line on the list. Use the down arrow at the right of the Location window to select the Inventory Location where this inventory item will be counted. Use the down arrow at the right of the Count Unit to display a list of all the existing units of measure for this inventory item. The dropdown will show the Recipe Unit, the Inventory Unit, the Delivery Unit and the Invoice Unit. When you select the unit of measure, the entry in the Conversion window will automatically change, since the conversion for all of these existing units of measure (for this inventory item) has already been established. If you are creating a new unit of measure, say the package, enter up to sixteen characters of text. The Conversion field is automatically filled in if you are establishing an existing unit of measure as a count unit in a particular Inventory Location. If you are establishing a new count unit, enter the number of recipe units in the count unit. The shelf code is an optional entry. If you have already entered shelf codes for other menu items, the existing shelf codes may be selected using the down arrow at the right of the Shelf Code window and clicking on an existing Shelf Code. If this is a new shelf code, enter up to four characters of text. Click on the Save icon at the top left of the Location Tab to complete the entry. Inventory Item Programming Substitution Tab The Substitution Tab is used to temporarily substitute one of the store s inventory items for an out-of-stock inventory item. The Sub Product will be depleted from inventory, rather than the actual inventory item included in any recipes. The substitution is NOT one Vendor Product Number for another Vendor Product Number, because if you had two sources for YOUR inventory item, the recipe depletion is by inventory item not by Vendor Product Number anyway. As an example, assume dozens of recipes call for a portion of Ground Chuck. Your Meat Supplier is temporarily unable to supply you with Ground Chuck, however, he is able to supply you with Ground Beef, and you already have existing inventory items for both. Your inventory item Ground Chuck is included in dozens of recipes. You do not want to edit your recipe list because it is a lot of work and this is temporary. You can not stop selling items which include Ground Chuck. You make the decision to temporarily substitute Ground Beef in all recipes which normally use Ground Chuck. However, you want to accurately maintain your on-hand inventory for Ground Beef, since it is also used. Also, this shortage is going to last several weeks. You want to correctly order Ground Beef, since that is all you can get anyway. In order to substitute one inventory item for another, the Recipe_Units of the two item MUST BE identical. Select the inventory item WHICH IS UNAVAILABLE from the list of all inventory items on the left of the screen and access the Substitution Tab. In Substitution. You must place a check in this box to actually cause the substitution to take affect. Regardless of the dates you enter on the rest of this screen, if there is no check mark here, the substitution will not be in effect. Sub Product. Use the down arrow to display a dropdown list of all inventory items and select the inventory product you DO HAVE and which you will use in place of the temporarily out of stock inventory item. Sub Date Start. Enter the date on which the substitution is to take affect in the appropriate date format for your Windows settings. It can be the current date, but the substitution can not affect your on-hand inventory in arrears. Sub Date End. Enter the date on which the substitution will end. If no date is entered, the substitution will continue indefinitely. In Substitution will automatically uncheck on this date. Sub Unit Conversion. This entry is always a one. You can not substitute 2 Oz. for 1 Oz. Recipe Unit. The is for reference only. Note that the two Recipe_Units MUST be identical. Odyssey/BackOffice Suite Programming Inventory Selections 171

172 Inventory Item Locations A separate section on assigning inventory items to various Inventory Locations is included with the March, 2005 release of Odyssey. This form allows the User to establish count units in Inventory Locations for inventory items. This is the same information as is programmed on the Location Tab under inventory item programming, but the selection criteria is on this form is first Item Class and then Inventory Location, rather than individual inventory item. The form provides a means of "bulk programming" count units into various Inventory Locations by copying from another Inventory Location. This is particularly useful in multi-location inventory environments. You can also use this form to establish new count units for any Inventory Location, or to delete count units in a particular location. NOTE: There is a default Inventory Location for each inventory item. This location is used during receiving to place items into a particular Stock Control Area, since each Inventory Location must belong to one and only one Stock Control Area. While the graphical interface will allow the User to delete an inventory item from a particular location, the software will automatically create at least one count unit for an inventory item in its default Inventory Location. The count unit is automatically established as the Unit_Inventory. This default is created only if no count units exist at all within the default Inventory Location for an inventory item. Batch Definition With the October of 2008 release of Odyssey, the Inventory Module supports Batch Preparation and the Programming module has been modified to create the association bet ween an Inventory Item and a Menu Item. There was always the ability to define a batch as a Menu Item for use in recipes. However, there was not a method for taking a physical inventory of batch items. Now the preparation of a batch can be recorded, moving individual inventory items from their raw state into the transformed batch inventory item. The Batch Definition programming screen creates an association between a Menu Item and an Inventory Item. The Menu Item holds the batch recipe. Do not use the Menu Item in any recipes if you are recording Batch Preparation. Use the linked Inventory Item itself in order to properly deplete inventory. Obvious ly, the Menu Item used for the batch recipe is not something which is sold. It is only to create the reci pe for the batch itself. The Inventory Item created does not have to be associated with any Vendor Items. This item will not ever be received. It is this Batch Prep process that places the batch into inventory as a transformed inventory item to be used in recipes and counted along with actual received inventory items. So, prior to accessing this Batch Definition screen, each batch should already have an Inventory Item for counting, use in recipes and Inventory control and a Menu Item, to hold the recipe. It is recommended that a Category be created for all batch recipes and an Inventory Class be created for all Prepared Batch Items. When the Batch Definition program module is accessed, you should first select the pre-defined Category and Item Class in order to narrow the selections, as shown below. The zbatch Recipes, Dressing selection is the Menu Item Category. The Prepared Batches is the Inventory Class. In order to create a new association, click the Add New Icon, select the Menu Item from the list, sele ct the Inventory Item from the List, the click the Save Icon. Only the batches which have been defined using this screen can be recorded in the Inventory Module. 172 Inventory Selections Odyssey/BackOffice Suite Programming

173 Recipes A good rule in entering recipes is Start with the simpler recipes first. That will make the whole concept of Product Types for menu items much, much easier. The simplest recipes are the ones which only include inventory items. Of course, every recipe ULTIMATELY includes only inventory items, but once you have gone t o all the trouble of entering the exact recipe for a hamburger, it s a whole lot easier to enter the recipe for a cheeseburger as one hamburger plus one slice of cheese. You just need to give your menu item cheeseburger a Product Type equal to the Product Type of the hamburger + 1. It s really that easy Start with the simpler recipes first. As the recipes get more complex, just go back into menu item programming and bump up the level of the Product Type of the menu items with the more complex recipes. A menu item can only include in its recipe a product, either an inventory item or a menu item, which has a Product Type of a lower level. Therefore, a menu item with a Product Type of Level 1 can only include inventory items in its recipe. A small coke or medium french fries are examples of menu items with a Product Type of Level 1. A menu item with a Product Type of Level 2 can include both inventory items and also any menu items with a Product Type of Level 1, and so on up to a menu item with a Product Type of Level 6, which can include any inventory item or any menu item with any Product Type other than Level 6. If you are planning on implementing Odyssey Inventory, hopefully you had a reasonable handle on recipes prior to entering any menu items, even though you can create a menu item separately from entering the recipe. If you encounter difficulty during the entry of recipes, i.e. you want to use a menu item in a recipe but the Product Type of the menu item you want to include in a recipe is the same or above that of the menu item whose recipe you are entering, you can go back and INCREASE the level of the Product Type for the menu item whose recipe you are entering. It is not a good idea to decrease the level of the Product Type for a menu item, particularly one whose recipe you have already entered. NOTE: If you decrease the level of the Product Type for the menu item you wanted to use in the new recipe, you would more than likely change the recipe for the menu item you want to use. The software will automatically delete any menu items in the recipe which are at or above the newly lowered level. For instance, while a small coke is clearly an example of a menu item with a Product Type of Level 1, a hamburger is more likely a menu item with a Product Type of Level 2. Its recipe would generally include a bun and a patty which are both inventory items, but for ease of recipe entry, its recipe might also include burger condiments. Burger condiments would be a list of the standard prep quantities of ketchup, mustard, onions, lettuce, etc. that are placed on all burger menu items. In this example, burger condiments would be entered as a menu item (even though you won t sell this as a POS Item at the point-of-sale), in order to be included in a recipe. Therefore, if the recipe for a hamburger is to include the bun, the patty and burger condiments, the hamburger must be have a Product Type of a Level 2 or higher. That means we want our cheeseburger to be a Product Type of Level 3. Our combo would move up to a Product Type of Level 4. That still leaves us two extra Product Types, Levels 5 and 6. Recipes Programming Recipe Tab Entering a recipe is extremely simple. Just Start with the simpler recipes first. There is no Add New functionality to the programming screen itself, because only menu items can have recipes and we enter those through Menu Item Programming. There is no bulk programming available from the Recipe Programming screen. The recipe for each menu item must be entered separately. The screenshot below shows an entered recipe for a menu item of Product Type 1. Odyssey/BackOffice Suite Programming Inventory Selections 173

174 The list on the left of the screen shows all menu items. It can be sorted by category using the dropdown at the top of the screen. To add a recipe line item to the recipe for a menu item follow these steps. Left click on the menu item whose recipe you want to define. Click on the Add icon on the Recipe Tab displayed. A blank line will appear. The Sequence Number will be automatically generated as ten plus the maximum existing Sequence Number. Left click into the window to the right of the text Sequence Number and enter different number if required. The Sequence is only used when listing recipe line items on the recipe report in a particular order. It is perfectly acceptable for each and every recipe line item to have the same Sequence Number, however, if you are going to all the trouble of implementing inventory, it s just not right. So enter a number corresponding to how you want to see the recipe line items listed. Use the down arrow at the right of the window underneath the text Recipe Item Name to select a recipe line item to add. What is displayed will depend on the Product Type of the menu item whose recipe you are programming. If the Product Type of the menu item you are programming is a Level 1, only inventory items will display. If the Product Type of the menu item you are programming is a Level 2, in addition to all inventory items, you can choose from all menu items with a Product Type at Level 1. If you know you have programmed a recipe for a menu item that you want to use as a part of the recipe for this menu item but it does not display, go check the Product Types of both the menu item whose recipe you are programming and the menu item you want to use in the recipe. When you select a Recipe Item Name, the Recipe Item Number will also display in the dropdown. Once you have selected the Recipe Item Name from the dropdown list, the Recipe Unit will automatically display. For menu items, it will invariably be Serving, since that s what the manual said to enter as the unit of measure for menu items. For "Batch Recipes", entered as menu items, it will most likely be the amount prepared, e.g. "2 GAL". NOTE: If you are using the Batch Definition and Batch Preparation features, DO NOT use the Menu Item which holds the recipe for the batch in the Sales Item s recipe. Use the Inventory Item instead, in order to properly deplete the inventory of the counted batch inventory item. Left click into the window to the right of the text Quantity Used and enter the quantity of recipe units included in the recipe. Remember, if you are entering the recipe for a hamburger, with a 4 Oz. Patty, the recipe unit is probably ounce, so enter 4, not Inventory Selections Odyssey/BackOffice Suite Programming

175 If there is any trim associated with the recipe line item, left click into the window to the right of the text Yield Percentage and enter the percentage of the recipe line item available after trimming. For Inventory Items used in recipes, this field defaults to the entry made on the Options Tab under Inventory Item Programming. Click on the Save icon. Either continue to add recipe line items to the selected menu item, or select another menu item whose recipe you are prepared to program. The Comment field is not printed on any reports and is only able to be viewed in this screen. Recipe Programming POS Recipe Tab This tab is for use both with the Recipe Book Report and in conjunction with Button Type Recipe at the point-of-sale. The report prints a single page, including a picture, with the entered recipe for the item, along with the text entry which is made on this tab. The entry on this tab is more for instructional lead-through in the process of making the menu item. At the point-of-sale, the POS Operator can view the entered text and the optional picture, selected next. The entry is a "memo" entry. The character "tab" is not allowed. Recipe Programming Picture Tab This tab is for use both with the Recipe Book Report and in conjunction with Button Type Recipe at the point-of-sale. The picture is printed on the report and displayed, along with the text, at the point-of-sale. Recipes Simplified Costing There is a default inventory item in the default database of All Other Inventory Items. In the default database, it is sourced from the default Vendor, All Other Vendors, with a unit of measure of Dollars and a unit price of $1.00. The costing, provided on the Flash View Report and in the analytical reports under the POS section of Odyssey Reports, all use the Standard Costing model. Normally the standard cost is the last purchased price from the Primary Source of the inventory items in the recipe. If you are NOT implementing inventory, or even if you are only implementing inventory for main ingredients, and you have a reasonable handle on the various costs of your menu items, nothing prevents you from creating a recipe for each of your menu items using the default inventory item. If you have a significant variation in the recipe costs across the spectrum of your entire menu, this methodology will at least provide some information on the impact of the product mix you have sold on your margins. You DO NOT need an Activator for the full Inventory module to implement this extremely basic costing methodology for your product mix. Odyssey/BackOffice Suite Programming Inventory Selections 175

176 Accounts Selections Internal Account Types As explained in the following section, an Account Type provides default settings for credit limits and defines the actual credit limits which are evaluated, total, daily or period counts and amounts. Internal Account Types merely define where certain detailed information is stored. The Internal Account Type is a selection provided when you are entering Account Members. For all Internal Account Types except House Charge/Gift Cards, you will be selecting the actual Account Member from a previously defined person or entity, i.e. existing employees, affiliated stores, vendors and most commonly, customers. There are five Account Types as shown in the screen shot below. The programming screen above is provided primarily for translation purposes. The numbers are fixed. Odyssey allows you to use the existing information in the database for Employees, affiliated stores and vendors should you desire to provide AccountCharge privileges. Customers. The Customer type includes the ability to monthly statements automatically. The monthly period can either be a calendar month, or an accounting month. The only accounting month supported by Odyssey Suite is the last day of accounting month. The software requires a last day of the accounting month, e.g. Sunday, and the accounting month will end on the last Sunday in a calendar month. The next accounting month will start on the following Monday, more than likely still in the same calendar month. The accounting month is established under Back Office Back Office Options. There are separate tabs for entering a variety of information pertinent to customers. Customers are also the only Internal Account Type supported by the Delivery functionality at the point-of-sale. Employees. The Employee type uses the information entered under Staff Employees to establish the AccountCharge number. The number used by the Employee to Clock In is the employee s Account Number. Vendors. The Vendors type uses the information entered under Inventory Vendors to establish the AccountCharge information. The ability to generate monthly statements is also provided for Vendors. Affiliated Stores. The Affiliated Stores type uses the information entered under Configure Store Configuration to establish the AccountCharge information. All stores, except the one configured with This Store as true are possible AccountCharge members. The ability to generate monthly statements is also provided for Vendors. House Charge/Gift Card. This selection is used both for Gift Cards and for customers who are provided charge privileges, or whose purchase activity you wish to track, who will NOT be receiving a monthly statement. This type is also commonly used in institutional feeding situations, such as a hospital or school. There is a separate import and export facility, for integrating an institution s existing list of members who can charge and the charges incurred at the point-of-sale. 176 Accounts Selections Odyssey/BackOffice Suite Programming

177 AccountCharge Types You should enter pertinent information first onto the Account Type programming form. Odyssey Suite allows you to group your account members into as many Account Types as required. The type of house account is used to establish what kind of credit checking will be performed when the pointof-sale seeks to post a debit or credit amount related to a transaction. The kinds of credit checking supported include an overall dollar amount credit limit, a daily count limit, a daily amount limit, a period count limit and a period amount limit. Any, or all, of these checks will be performed before the amount is accepted by the point-of-sale as payment on a transaction. AccountCharge types also include default credit limits for each of the above, as well as establishing when the daily and period limits will be reset. NOTE: If you are using the statement generating capabilities of the AccountCharge module, or the To-Date reporting capabilities of Odyssey Reports, you should set the Accounting Period in Back Office Back Office Options on the first day of use of Odyssey. For additional information, refer to the previous section covering the Accounting Month. The default entries can be changed by individual AccountCharge member. Account Type Programming General Tab Account Type. This is merely an identifying number. It also is used when sorting various lists of Account Members. You can add as many account types as are needed, depending on the need to establish either different response codes or credit check types. Account Type Name. This is a thirty character text field to identify the account type. Response Code Accept. The text which appears on the screen of the point-of-sale can be customized through entries under Account Selections Account Responses. The text which you desire to appear when a charge is accepted is selected here. One of the options you can set for a response is to print either the current balance owed by the AccountCharge member or the available credit. This is especially useful in debit situations, where the Total Credit Limit is $0.00. For a prepaid amount of $100.00, and a member who has already charged $37.00, it is much more desirable to display Available Credit $63.00 than Account Balance $ This is discussed in a following section Account Response Codes. (The default text includes two entries identical to the text used in the example herein for this purpose. If the text is changed, the functionality remains.) Media Number. For additional control at the point-of-sale, each Account Type may be associated with its own unique finalizing media or a single media may be selected for all Account Types. The result is that only a single finalizing media may be used for any individual Account Type, i.e. you can not make the Cash finalizing media interact with the AccountCharge module. The selected media MUST have a check mark in the box Account Number Required and NO CHECK in the box Override Account# Validation, as set Finalize Media Authorization Tab. The proper selections are shown below. Odyssey/BackOffice Suite Programming Accounts Selections 177

178 Control Account Number. This is a fixed entry, shown here only for reference. Track Patronage. This is a default for newly created accounts of this Account Type. Auto Discount Media. This is a default for newly created accounts of this Account Type. Auto Service/Tip Media. This is a default for newly created accounts of this Account Type. Account Type Programming Credit Limit Tab There are two sections to this programming form. The first column is a list of check mark boxes. These define whether or not a particular credit limit type is applicable for all AccountCharge members of this type. This selection CAN NOT be changed on an individual member basis. The second column is the actual credit limit. This selection CAN be changed on an individual member basis. The entries programmed here are used as the default credit limit when new AccountCharge members are added and associated with the applicable Account Type. For reference, the programming form is shown in a screenshot below. The check mark boxes are cumulative. In other words, you may select all of the boxes and each credit limit will be checked sequentially. The software checks the credit limits in the order shown. NOTE: It is possible, therefore, that a charge will be denied for an AccountCharge member who is und er their total credit limit, but has already exceeded their Daily Credit limit. The denial text presented at the point-of-sale will reflect the first credit limit checked which has been exceeded. Use Total Credit Limit. A check mark here causes the software to check the dollar amount defined for the individual AccountCharge member as their Total Credit Limit. The dollar amount entered here is used as a default for new AccountCharge members and can be changed on an individual basis. If you enter $0.00 for the Total Credit Limit, only members with a credit balance will be authorized to place charges. Use Daily Credit Limit. A check mark here causes the software to check the dollar amount defined for the individual AccountCharge member as their Daily Credit Limit. The dollar amount entered here is used as a default for new AccountCharge members and can be changed on an individual basis. The Daily Period can either be the Sales Day, or a number of hours. The number of hours selection allows for either multiple shifts during a day, or can be used for meal periods, provided the number of hours between meal periods is greater than the meal period itself. The Daily Period used here is established on an individual Account Type basis, under the Account Type Programming Reset Tab. Use Daily Count Limit. A check mark here causes the software to check the number of charge transactions counter defined for the individual AccountCharge member as their Daily Count Limit. The counter for the number of charges entered here is used as a default for new AccountCharge members and can be changed on an individual basis. The Daily Period can either be the Sales Day, or a number of hours. The number of hours selection allows for either multiple shifts during a day, or can be used for meal periods, provided the number of hours between meal periods is greater than the meal period itself. The Daily Period used here is established on an individual Account Type basis, under the Account Type Programming Reset Tab. 178 Accounts Selections Odyssey/BackOffice Suite Programming

179 Use Period Credit Limit. A check mark here causes the software to check the dollar amount defined for the individual AccountCharge member as their Period Credit Limit. The dollar amount entered here is used as a default for new AccountCharge members and can be changed on an individual basis. The Period used here can either be a weekly period or a monthly period. If it is a weekly period, the Weekly Period is defined on an individual Account Type basis, under the Account Type Programming Reset Tab. If it is a monthly period, it is the Accounting Month, defined under Back Office Back Office Options. Use Period Count Limit. A check mark here causes the software to check the number of charge transactions counter defined for the individual AccountCharge member as their Period Count Limit. The counter for the number of charges entered here is used as a default for new AccountCharge members and can be changed on an individual basis. The Period used here can either be a weekly period or a monthly period. If it is a weekly period, the Weekly Period is defined on an individual Account Type basis, under the Account Type Programming Reset Tab. If it is a monthly period, it is the Accounting Month, defined under Back Office Back Office Options. Account Type Programming Reset Tab This tab is used to establish when the Daily Periods and Period credit limits are reset. A screenshot of the programming form is included below for reference. Under the Reset Daily section, the two check boxes are mutually exclusive. Check the appropriate box. This section is only applicable if the account type is actually using the daily credit limits on counts or amounts. With End Of Day. The Daily Credit Limit and Daily Count Limit are reset when the End Of Sales Day procedure is performed using Odyssey/MWS. By Time. The Daily Credit Limit and Daily Count Limit are reset prior to processing an individual transaction, based on the number of hours since the previous charge. This will work both for split shifts and for meal periods, provided there is some pattern to when meals are charged. If the breakfast meal period is three hours, and there are two hours between the breakfast meal period and the lunch period, then this functionality WILL NOT operate as desired. If you set the period to 2 hours, allowing for very late breakfast and the first lunch period, you have left an opening for two breakfast amounts. If the breakfast period is shorter than the break in between periods, e.g. a two hour breakfast period and a three hour break before lunch, then enter a 3 and you have complete control over one meal per meal period. Under the Reset Period section, the two check boxes are mutually exclusive. Check the appropriate box for either a weekly period or a monthly period. This section is only applicable if the account type is actually using the period credit limits on counts or amounts. By Day Of Week. The Period Credit Limit and Period Count Limit will be reset on a weekly basis. If your week begins on a Sunday, select Sunday from the dropdown. The limits are reset when the End Of Sales Day procedure is performed using Odyssey/MWS and the New Sales Day selected is greater than the day you have selected here, e.g. if you are actually closed on Sunday, the Period Limits WILL BE reset when you select the following Monday as the new Sales Day. By Last Day Of Month. The last day of the month used is either the last day of the calendar month or the Accounting month as established under Back Office Back Office Options. Odyssey/BackOffice Suite Programming Accounts Selections 179

180 Account Response Codes This form is used to customize what is displayed and printed when a finalizing media is interacting with the AccountCharge module. While the Add icon is active on this programming form, there is no reason to add a new Response Code, you should merely change the text on an existing Response Code. The context of the utilization of the Response text is pretty much self-explanatory. There are a few Response Codes which require further explanation, however. Response Number 10 Media Not Valid For Account. This Response text indicates that the Account Number entered was valid, however the finalizing media used was not the one entered under Account Type for the selected AccountCharge member. Response Number 11 Account Balance. This Response text is available for an accepted charge amount. Following the example in the previous section, a member with a $ credit limit with total charges to date of $37.00 would show Account Balance $37.00 with this Response Number as the selected as the Response Code Accept on the Account Type Programming General Tab. Response Number 12 Available Credit. This Response text is available for an accepted charge amount. Following the example in the previous section, a member with a $ credit limit with total charges to date of $37.00 would show Available Credit $63.00 with this Response Number as the selected as the Response Code Accept on the Account Type Programming General Tab. Response Number 13 Account Verification Name. You SHOULD NOT change the text on this Response Text because this is not the text which is used for the response. For situations where a credit limit is NOT applicable, using this as the Response Code Accept on the Account Type Programming General Tab causes only the account verification name to show, rather than either Available Credit or Account Balance. Response Number 14 Account Not Active. This is the prompt shown at the point of sale window for AccountCharge members with no check in the active box when either an Account Inquiry function is performed, or you have the option check box set to Confirm Account Number Entry, under POS System Options Back Office Software. The Active flag is set under AccountCharge Member Programming General Tab. The Inactive flag is evaluated BEFORE any Credit Limits are checked. It is quite possible that the Credit settings for an AccountCharge member would allow for the posting of a charge, but the charge would be denied if the Account is not Active. Response Number 15 Credit Limit. This text defines what is shown on the point-of-sale window when either an Account Inquiry function is performed, or you have the option check box set to Confirm Account Number Entry, under POS System Options Back Office Software on the line which subtracts the Account Balance from the Total Credit Limit. (If the Account Type is set for Daily Credit Limit, the line shown will subtract the Daily Charges from the Daily Credit Limit.) NOTE: A window displays at the point-of-sale in response to a Charge Inquiry, the AccountCharge Inquiry Confirmation Screen. This window displays the text for Response Number 11 and the text for Response Number 12. In some situations, institutional food service for example, these amounts are not relevant. To suppress these amounts from displaying, set the text for Response Numbers 11 and 12 to a blank by highlighting the text in blue, then depressing the Del key. 180 Accounts Selections Odyssey/BackOffice Suite Programming

181 Customer Account Type Programming For all Account Types OTHER THAN Customers, the primary entry form for AccountCharge members is the programming form Account Members. Odyssey/MWS retains a great deal of additional information for the Customer Account Type, related both to the mailing of monthly statements and delivery activity. Customer Programming General Tab This form is used to add a new Customer to the AccountCharge member list. To add a new Customer as an AccountCharge member, follow these steps. Click the Add icon. You will note that a number of fields appear at the bottom of the entry form which to not show for existing customers and that all entry windows are blank EXCEPT the Account Number field. The entry shown in this window is a default, merely counting the number of existing Account Numbers. The entry shown in this window, however, is the Account Number used to post charges for a particular customer. It can be changed from this programming form, or from the Account Members programming form after the fact. You will also note a window which only appears on this programming form immediately after the Add icon is depressed a Balance window. Click into the Title field. This is a fifteen character text field, but is generally Mr. or Ms. Click into the Last Name field. This is a thirty character text field. Note that the Account Verification Name (which also must be a unique field) will default to an entry based on both the entered Last Name and entered First Name. A duplication may be changed by amending the Account Verification Name entry, which is normally set by default. Click into the First Name field. This is a twenty character text field. Note that the Account Verification Name (which also must be a unique field) will default to an entry based on both the entered Last Name and entered First Name. A duplication may be changed by amending the Account Verification Name entry, which is normally set by default. NOTE: For simplicity, the AccountCharge module programming defaults the Account Verification Name field to the Last Name followed by a comma and a space and then as many characters of the First Name as will fit. The result is placed in the field Account Verification Text. This field MUST be a unique entry and generally there will be no problem with this. However, the notification that there is a problem will not appear until you attempt to save the entry. Click into the Middle Name field. This is a fifteen character text field, but is generally a single capitalized character and a decimal point. Click into the Birth Date field. Enter a date field, appropriate for your Windows settings. The entered Birth Date appears on the point-of-sale window when either an Account Inquiry function is performed, or you have the option check box set to Confirm Account Number Entry, under POS System Options Back Office Software. There is also a Happy Birthday greeting printed on the customer statement for the month immediately preceding the entered month for this Customer. Click as appropriate the Use Work Address For Billing Statement. This defines the address used on the monthly statement as either the entered Home Address or the entered Work Address. The Account Verification Name field will have been pre-filled with the entered Last Name followed by a comma and a space and then as many characters of the First Name which will fit. In rare instances, you will need to change this entry. NOTE: When adding a new Customer, the Account Verification Name can be entered from this screen. If you are changing the Account Verification Name for an existing customer, who is already an AccountCharge Member, this field can only be changed from the AccountCharge Member Programming General Tab. Click into the Account Number field. This is the number which will be used by the Customer when placing charges at the point-of-sale. The default entry is merely a count on the total number of Account members ever programmed into the Odyssey database. This is a sixteen character text field Odyssey/BackOffice Suite Programming Accounts Selections 181

182 and should be set as appropriate for the number assigning system of the establishment. This field is initially entered on this programming form and can be changed on the Account Member programming form. Click into the Balance field. This field is for use in entering any existing account balance for this customer prior to the installation of Odyssey. For a truly new Customer, do not make an entry here. If there is a deposit associated with the Customer in conjunction with membership, you should make that entry using Odyssey/MWS from the main screen using the Postings selection under Accounts. When you have entered all the information on the General Tab, click on the Save icon. In rare instances, you might see the following prompt. The displayed error message indicates that the default entry which the Programming module has made for the Account Verification Name has resulted in a duplicate database entry. The field Account Verification Name MUST BE UNIQUE. You can manually change the Account Verification Name so that the sixteen character text for THIS Customer does not conflict with the Account Verification Name of any other AccountCharge member. Deleting a Customer As a general rule, it is not good practice to delete a Customer. Odyssey has maintained historical records for the Customer as an AccountCharge member and if you delete the Customer, all historical records will be deleted, including any current records. If the Customer is being deleted as a result of some kind of programming error, when you attempt to delete the customer from the Customer Programming General Tab, you may see a prompt as follows: This Customer can still be deleted, if you really want to. You must first, however, access the Account Members selection and delete the associated Account Number. This will leave a dangling customer with no Account Number association. You can then re-access the Customer Programming General Tab and actually delete the Customer information. Customer Programming Home Tab The information entered on this tab is used in the mailing address for the monthly statements generated for Customers and may also print on the bottom of a receipt for Delivery customers. To send statements to the Home Address, the check box under Customer Programming General Tab must not have a check next to the text Use Work Address For Billing Statements. 182 Accounts Selections Odyssey/BackOffice Suite Programming

183 Customer Programming Work Tab The information entered on this tab is used in the mailing address for the monthly statements generated for Customers and may also print on the bottom of a receipt for Delivery customers. To send statements to the Work Address, the check box under Customer Programming General Tab must have a check mark next to the text Use Work Address For Billing Statements. Customer Programming Delivery Tab There are two sets of entries this tab, for delivery to the Home Address of the Work Address. Home Delivery Instructions. This is a memo field entry. The information entered here will display at the point-of-sale when the customer has been identified through the entry of the Home Phone Number, the Cell Phone or the Home Address and will also print on any receipts which are generated for an order with Sales Type equal to 3. The printing is established by the option set under Printer Configuration Terminal Print Options as Print Delivery Info. Home Delivery Zone. This is a ten character text field. It can be used to identify Delivery Zones for a customer to assist in transferring delivery checks to a driver. It is displayed on the POS screen when Button Type Transfer Delivery Checks is depressed. Work Delivery Instructions. This is also a memo field entry. The information entered here will display at the point-of-sale when the customer has been identified through the entry of the Work Phone Number or the Work address and will also print on any receipts which are generated for an order with Sales Type equal to 3. The printing is established by the option set under Printer Configuration Terminal Print Options as Print Delivery Info. Work Delivery Zone. This is a ten character text field. It can be used to identify Delivery Zones for a customer to assist in transferring delivery checks to a driver. It is displayed on the POS screen when Button Type Transfer Delivery Checks is depressed. NOTE: When the point-of-sale is searching for a Delivery Customer with an entered phone number, the software will search three fields; the "Phone Number" and "Cell Phone" fields entered under the Home Tab and the "Phone Number" entered under the Work Tab for a matching customer. If the same number is associated with multiple customers, the POS Operator will be prompted to select from the list of all customers associated with the entered phone number. When an address is used to search the Customer database, the software will search two fields: "Home Address Line 1" and "Work Address Line 1". Delivery Customers Added at the Point-of-Sale When a customer calls in for the first time and has no phone number in the Odyssey database, the only required fields are a last name and a phone number. Both a customer and AccountCharge member will be automatically added to the database. The form presented to the POS Operator allows for significantly more information to be entered and if this information is entered, it will be placed appropriately in the database. The software uses a default for the Account Type, entered under Back Office Options Delivery Account Type. Generally this Account Type will have a credit limit of $0.00 since delivery establishments are more than likely not extending credit but rather using the database to track patronage, re-order from the prior order database maintained at the point-of-sale and maintain the delivery address and instructions. Odyssey/BackOffice Suite Programming Accounts Selections 183

184 Delivery Related Entries There are five selections immediately under the selection "Customers" on the pull down menu under Accounts. These relate to the operation of Button Type Customer Lookup on the POS/2100. Delivery Cities The entries here are used to provide for quicker entry of new customers on the POS/2100. There are two entries. City. This is a thirty character text entry. It will be displayed in a drop down list at the point-of-sale when entering the city field for new customers, or modifying the field for existing customers. This entry may be added at the point-of-sale if a customer is identified within a city which does not already exist in the BackOffice database, however, this should be highly unlikely if the database has been properly prepared initially. List Order. This numeric entry defines the order in which cities will be displayed in the drop down list. The primary city should have the lowest list order number, since that is the default for new customers. Delivery States The entries here are used to provide for quicker entries of new customers on the POS/2100. There are two entries. State. While this is a thirty character text entry, you should limit your entry to the proper two character state identification for operation within the United States. Unless the restaurant is on a state border, generally there will be only one entry in this table. This entry can not be added at the point-ofsale. List Order. This numeric entry defines the order in which states will be displayed in the drop down list. The primary state should have the lowest list order number, since that is the default for new customers. Delivery Zip Codes The entries here are used to provide for quicker entries of new customers on the POS/2100. There are two entries. Zip Code. While this is a twelve character text entry, you should limit your entry to the proper five nine for full zip code) zip code for operation within the United States. This entry may be added at the point-of-sale if a customer is identified as having a zip code which does not already exist in the BackOffice database, however, this should be highly unlikely if the database has been properly prepared initially. List Order. This numeric entry defines the order in which zip codes will be displayed in the drop down list. The primary zip code should have the lowest list order number, since that is the default for new customers. NOTE: There is no built-in correlation between the City selection and the Zip Code selection for new customers added at the point-of-sale. Each entry, state and zip code, must be selected separately. Delivery Zones The entries here are used to provide for quicker entries of new customers on the POS/2100. There are two entries. Zone. This is a ten character text entry and can be used to separate the overall delivery area into "zones" to assist in driver transfer. The zone appears on the check list when Button Type Transfer Delivery Checks is touched. List Order. This numeric entry defines the order in which zones will be displayed in the drop down list. Auto Service/Tip Media. An entry here will override the default entry for new delivery customers added at the point-of-sale, which is set under Account Type Programming on the General Tab. (or 184 Accounts Selections Odyssey/BackOffice Suite Programming

185 Delivery Statistics From the Delivery Customer information screen, displayed after confirming the customer with Button Type Customer Lookup, there is an "Activity" button. The "standard" information displayed for the selected customer includes the number of days of "history" available at the point-of-sale, the number of orders retained at the point-of-sale and the net sales to the customer represented by the retained orders. In addition to this "standard" information, up to three additional historical pieces of information may be made available to the POS Operator at the point-of-sale. The purpose of this is to assist in placing a coupon on the order, based on the prior purchasing habits of this particular customer. The three elements of information can be: Any Menu Item Any Department Any Category The point-of-sale will display both the count and amount, in the retained history, for the selection. AccountCharge Member Programming This is the main form used to establish all AccountCharge members EXCEPT Customers. AccountCharge members of Account Type Customers should be initially established under the Customer Programming General Tab. There is a screening filter at the top of this screen, allowing you to display only those AccountCharge members of a particular Account Type. Since AccountCharge members can be set as Inactive, there is also a filte r to display only the Active AccountCharge members or all programmed AccountCharge members. You do have the ability to set the parameters simultaneously for either all displayed AccountCharge members or o nly selected AccountCharge members. The parameters which can NOT be bulk programmed will display in a light shade of gray. For more information on the selection methodology, refer to the section Menu Items Selection Methods. As an alternative to highlighting all AccountCharge members and entering new amounts, you can select a single AccountCharge member and click the Copy icon. Next, select all AccountCharge members you wish to mak e identical to the previously selected AccountCharge member. Lastly, click on the Paste icon. All parameters associated with the selected AccountCharge members that CAN be bulk programmed will have been. Odyssey/BackOffice Suite Programming Accounts Selections 185

186 AccountCharge Member Programming General Tab When adding a new AccountCharge member with the screening filter at the top of the screen at All, you select the Account Type. If you have filtered the listing on the left of the form to only show a particular Account Type, the Account Type will be fixed. A screenshot of the General Tab is shown below for reference. NOTE: This screen is available from the main Odyssey/MWS window, for viewing only, under Accounts Status. The information entered on this form is as follows: Account Number. This is a sixteen character text field. It is the number entered at the point-of-sale to identify the AccountCharge member. For Customers, the entry will have been made when the Customer was initially established under Customer Programming General Tab. This is a unique field in the database and the software WILL NOT allow duplicate Account Numbers. The software will accept either a scanned or swiped entry into this field, as long as the leading character on the keyboard wedge scanner or magnetic card reader is a ; character (semi-colon) and there is a trailing CR/LF character. The internal number used by the Odyssey software to track all charges related to an AccountCharge member is NOT the Account Number. This means you CAN change the Account Number for an AccountCharge member after postings have been made, either in Odyssey/MWS or at the point-ofsale and you WILL retain all the information. The number used at the point-of-sale for future postings will be the new number and the new number will print on all statements. This is particularly useful when a swiped card is used, and the AccountCharge member loses his/her card and for security reasons a new card must be issued. All the previous charges are associated with the same internal Account Number. Account Type. Use the down arrow at the right of the window to display a dropdown list of Account Types. Internal Account Type. This field may only be changed when adding a new AccountCharge Member. It determines which grouping, employees or vendors or affiliated stores, will be displayed. Customers are established as AccountCharge members when initially added as a customer. You would only be adding a customer as an AccountCharge member if you deleted the AccountCharge member, leaving the customer "dangling" and then re-established an AccountCharge membership for the customer. 186 Accounts Selections Odyssey/BackOffice Suite Programming

187 Customer/Employee/Vendor/Store Number. For four of the Internal Account Types, another window will display. Use the down arrow at the right of the window to select the Employee, Vendor or Affiliated Store to whom you wish to grant charge privileges an AccountCharge member. Again, customers are added as AccountCharge members when initially added as a customer. This window does not display for Internal Account Type 5, "House Charge/Gift Cards", since there is no related database of information for this kind of Internal Account Type. Account Verification Name. This is a sixteen character text field. It must be a unique field in the database for ALL AccountCharge members. For Customers, this was completed under the Customer Programming General Tab. For Employees, the default used when granting charge privileges is the Nick Name Field. For both Vendors and Affiliated Stores, it is the first sixteen characters of the Name field in the database for the Vendor or the Affiliated Store. NOTE: This field MUST BE unique and should therefore be allowed to default to the same entry as the Account Number. In addition, Gift Cards are generally sold at the point-of-sale, after having the card swiped in the BackOffice to establish a zero balance account. There is no text entry at the point-ofsale to associate the Gift Card with a "holder". Secondary Number. This is a sixteen character text field. It DOES NOT need to be a unique entry. In an institutional feeding environment, this can be used as the Social Security Number field, even though the SSN# will, in fact, be unique. The Account Verification Name is shown at the point-of-sale and should be a textual reference for the individual. The Secondary Number is not shown, however, it is provided in the Export file and provides a method of relating the charges to a known field in the data processing system against unknown fields such as an Odyssey Account Number or an Odyssey Account Verification Name. This field is also printed on certain reports related to account activity. It is a good field for the name of the Gift Card holder, however, because the Gift Card is generally established in the database as a $0.00 Total Credit Limit account and is only available for use once it has been purchased at the point-of-sale, where there is no text input at purchase time, the entry into the AccountCharge member database would need to be made after the purchase itself. Print Operator Instructions On Guest Check. Pertains to the memo field programmed on the Patronage Tab. Will print as formatted, in 40 character lines. (Used in a particular account for extremely lengthy and formal names/titles. Sub-Account of Master Account. This field identifies this AccountCharge member as a subaccount of a different AccountCharge member. A separate section follows immediately which explains greater detail relating to sub-accounts. Master Account. The down arrow displays a drop down listing of all AccountCharge members who are not also sub-accounts if the "Sub-Account of Master Account" selection has been checked. For existing AccountCharge members who are not sub-accounts, it displays their own Account Verification Name. A separate section follows immediately which explains greater detail relating to sub-accounts. Active. You MUST place a check in this box in order to allow for a debit to the account to be posted at the point-of-sale, regardless of any of the Credit Limit settings. An account which DOES NOT have a check mark in this box will result in a charge denial at the point of sale, with Response Text 14. Credit Limit Used Flags. The check marks in the boxes to the left of the five lines for Total Credit Limit, Daily Credit Limit, Daily Count Limit, Period Credit Limit and Period Count Limits are determined by the settings in Account Type Programming Credit Limit Tab. Credit Limits. The second column at the bottom of the screen will initially be filled based on the setting for the default amounts for the various limits. Each of the amounts and counts can be changed on this screen to be unique to the individual AccountCharge member. They may be changed at any time to affect subsequent charge postings at the point-of-sale. Balance. The third column at the bottom of the screen reflects the current amount or count balance for the individual AccountCharge member AT THIS MOMENT. Last Visit. This is a date/time stamp and reflects the last date and time an amount, either a debit or a credit, was posted to this account either through the Back Office under Accounts Postings or at the point-of-sale terminal, or the last time this AccountCharge member was associated with a check for Patron/Loyalty purposes. Odyssey/BackOffice Suite Programming Accounts Selections 187

188 AccountCharge Sub-Accounts Sub-accounts are useful for two purposes; when extending credit to a company or other entity where multiple individuals are allowed to charge but there is one statement and payments come from one source, or when you desire to track Patron/Loyalty both individually and for a company or other entity. No statement is generated for a sub-account. There is a single statement generated for the Master Account, however, the individual sub-account charges are sub-totaled on the statement. Sub-accounts are also excluded from the All Accounts Summary report. The Detailed Postings report, like the statement, subtotals the individual sub-accounts under the Master Account. When you are c reating a new account, you can always make the new account a sub-account at the time of creation. For accounts already established, the current balance of the account must be identically zero in order to change the AccountCharge member from its "own" Master Account to a sub-account. There is no facility wit hin Odyssey to automatically transfer outs tanding balances, either debits or credits, from the existing account to a new Master Account. You can, however, merely post a credit or debit to the account using the "Postings" selection on the main Odyssey/MWS menu, then turn the account into a sub-account and then post an identical but opposite debit or cred it to the Master Acc ount. At the point-of-sale, the Account Verification Name and Account Number for the sub- account should be used. The BackOffice will take care of the rest of the accounting. Accoun tcharge Member Programming Patronage Tab Odyssey a llows you to track the activity of custome rs even if you are not extendi ng credit. You can also associate an automatic discount and/or service charge with identified customers. The customer is identified at the point-of-sale using the Button Type Account Number Entry. The entry screen for the Patronage Ta b is shown below. Track Patronage. Place a check here if you wish to track all purchases from this AccountCharge m ember. This box is automatically checked for customers added at the point-of-sale as a new delivery customer. Aut o Discount. Place a check here to automatically provide a discount to the customer, once identified. Auto Discount Media. Use the down arrow to select the appropriate discount from the list displayed. Normally, customers are identified at the beginning of a sale. This means the only appropriate discounts are percentage discounts, either on the subtotal or individual items. If a dollar amount discount is selected, the discount will not be applied if the customer is identified at the beginning or a transaction because there will be no sales to offset the discount. 188 Accounts Selections Odyssey/BackOffice Suite Programming

189 Auto Service. Place a check here to automatically add a service charge to the customer, once identified. A use for this is when providing an automatic discount to a customer along with a small "cover fee" for each visit in order to encourage a larger check average. Operator Instructions. This is a memo field, displayed at the point-of-sale once the customer is identified. It is useful for providing information to the POS Operator about the customer regarding preferences for seating or menu selection. AccountCharge Member Programming Import/Export Tab This tab is intended to provide interaction with institutional feeders, such as Hospitals or Schools, who have an independent database on individuals who are authorized for charge posting privileges on the Odyssey POS/2100. The import facility allows for the entry of such individuals as Internal Account Type 5 AccountCharge members. There are two export facilities. Both the export facilities pertain to ALL AccountCharge members, not only the Internal Account Type 5 members. This tab is only of benefit when interacting with an independent database of individuals and will require a level of development by the institution maintaining the independent database. The format for importing and exporting is fixed within the Odyssey AccountCharge module, however, the file format can be handled by virtually any software module which has an import/export facility. AccountCharge Import/Export File Conventions The import facility assumes that the independent third party software is TOTALLY in charge of all Internal Account Type 5 accounts. The design concept was to minimize the level of effort required to create an import file and also minimize possible sources of human intervention error. The folder used for importing is c:\icom\accounts\in. There is no facility for actually getting the file into this folder. It is assumed that the independent third party software will have the folder c:\icom\accounts as a shared drive and simply copy the account list into this folder. The folder used for exporting is c:\icom\accounts\out. It is assumed that the independent third party software will have the folder c:\icom\accounts as a shared drive and will simply copy information from this folder to the appropriate location. The imported listing of accounts should be contained in the file c:\icom\accounts\in\accountlist.txt. An exported listing of accounts will be created as the file c:\icom\accounts\out\accountlist.txt. An export of account transactions will be created as the file c:\icom\accounts\out\accounttransactions.txt. The file format uses a fixed length convention. Each field must contain the exact number of characters as specified in the documentation. All text fields are left justified with trailing ASCII space characters to fill in the required field length. All fields which are NOT REQUIRED, and for which the independent third party software HAS NO CORRESONDING INFORMATION, should be filled with ASCII space characters. All numeric fields which are NOT amount fields are right justified. All numeric fields which contain dollar amounts are right justified. The first character before either a number or a decimal point should be either an ASCII space character or an ASCII + character (plus sign) for positive amounts, or an ASCII - character (minus sign) for negative amounts. Most amount fields are ten characters in length, some are 12 characters in length. The decimal point MUST BE included, if appropriate. An entry read as six space characters, followed by the digits 1200 as the last four characters will be interpreted as $1, To send $12.00, there would be five leading space characters, then the characters as the last five characters in the field. Exported fields WILL NOT contain the decimal point followed by two ASCII 0 characters if they are exact dollar amounts, e.g. the number $12.00 will be exported as eight ASCII space characters followed by 12. All records should be de-limited with an ASCII CR/LF character. AccountCharge Record Format AccountList.txt To import an Account List, access the AccountCharge Member Programming Import/Export Tab and left click on the Account List button. There is no facility to automate this import procedure. Odyssey/BackOffice Suite Programming Accounts Selections 189

190 To export an Account List, access the AccountCharge Member Programming Import/Export Tab and left click on the Accou nt List button in the E xport area of the screen. The follo wing section shows a screenshot of the entire Export area of this tab. The followi ng is the record format for the file AccountList.txt, both imported and exported. Field Number Field Name Start Position Length of Field Data Type Required Index User Field Name 1 Account Verification Name 1 16 Text Yes Yes (No Duplicates) Employee Number 2 Account Number Te xt Yes Yes (No Duplicates) Badge Number 3 Secondary Number Te xt No Yes (Duplicates OK) Employee Name 4 Customer Number Numeric No Yes (Duplicates OK) 5 SSN Number Te xt No Yes (Duplicates OK) 6 Vendor Number Te xt No Yes (Duplicates OK) 7 Store Number Numeric No Yes (Duplicates OK) 8 Active Numeric No -1 Defaults -1 = True 0 = False 9 Total Credit Limit Numeric No Daily Credit Limit Numeric No Daily Count Limit Numeric No Period Credit Limit Numeric No Period Count Limit Numeric No 1000 Note that fields 1 and 2 are both required and it is required that the fields be unique. If the import software encounters a second record with an identical Account Verification Name or an identical Account Number, the second entry will over write the initial entry. The export of the Account list can be used to highlight any offending entries. 190 Accounts Selections Odyssey/BackOffice Suite Programming

191 All fields which have been imported will be exported within each and every export record. The field names above relate to the Odyssey database, however the independent third party software provides may pre-fill these fields with any value in order that they be included in the export of transaction information. Note that fields 8 through 13 are not required. Field 8 should be used to cancel charge privileges for an AccountCharge member. An import of an AccountList.txt file with only a single record appropriate to the employee with a 0 in this field will cancel charge privileges. The default values which are listed for fields 9 to 13 are database defaults, and DO NOT relate to the credit limits established by the programming under Account Type Programming Credit Limit Tab. In general, credit limits are not imposed in the type of AccountCharge scenario anticipated by the import/export methodology. If credit limits are applicable, then the independent third party software MUST fill the appropriate amounts and counts into these fields. Whether or not these fields are evaluated IS a function of the programming under Account Type 5 programming, however, under the Account Type Programming Credit Limit Tab. AccountCharge Record Format AccountTransactions.txt To export transaction information on AccountCharge member postings, access the AccountCharge Member Programming Import/Export tab as shown below. There is no facility to automate this export procedure. There are two options available for an export of AccountCharge transactions, Detail and Summary. Both selections require that a date range be selected. The file format for both selections is identical. NOTE: If there is an existing AccountList.txt or AccountTransactions.txt file in the OUT folder, a new export will simply overwrite the existing file. For a Detail selection, a record will exist for each and every charge posting for each and every AccountCharge member. If you refer to the record format shown below, in a Detail selection, the Start Date and End Date fields (Fields 8 and 9) in each individual record will be identical values and reflect the date the individual charge was posted. The Transaction Count field (Field 10) will always be a 1. For a Summary selection, one record will exist for each Revenue Center for each AccountCharge member. If an AccountCharge member had no charges in a particular Revenue Center, an empty record is not created. The Start Date field and the End Date field will be identical in each and every record, and will reflect the values selected on the above screen for Sales Beginning and Sales Ending. The Transaction Count field will indicate the number of postings. Odyssey/BackOffice Suite Programming Accounts Selections 191

192 The following is the record format for the exported transactions file, c:\icom\accounts\out\accounttransactions.txt. Field Number Field Name Start Position Length of Field Data Type Format 1 Account Verification Name 1 16 Text 2 Account Number Text 3 Secondary Number Text 4 Customer Number Numeric 5 SSN Number Text 6 Vendor Number Text 7 Store Number Numeric 8 Start Date Date mmddyyyy 9 End Date Date mmddyyyy 10 Transaction Count Numeric 11 Amount Numeric 12 Revenue Center Number Numeric The information contained in fields 1 through 7 will be simply a regurgitation of the fields provided on the Account list import. The information contained in Fields 8, 9 and 10 will depend on the User s selection of Detail or Summary export. NOTE: The format of fields 8 and 9 is FIXED and DOES NOT depend on any Windows settings. In situations where the standard date format is ddmmyyy, the independent third party software vendor must accommodate the FIXED date format of mmddyyyy as illustrated. AccountCharge Member Programming Picture Tab Use th is tab to select a picture of the customer to be displayed at the point-of-sale when the customer is identifie d. The only type of file which may be displayed are "bmp" files. 192 Accounts Selections Odyssey/BackOffice Suite Programming

193 AccountCharge POS/2100 Considerations This section is included to cover some options pertaining to AccountCharge on the POS/2100 in a single section. In addition to covering options previously covered in this document, it covers some of the buttons available on the various point-of-sale Desktops which relate to Account Charge. Compulsory Account Number Entry The software can require that an AccountCharge Account Number be entered prior to starting a new check at a table. This option is both by terminal and further by sale type. Set the boxes under POS Terminal Options Sale Types as illustrated below. Note that if there is no check next to Validate Account, you are operating in the Tabs mode and the entry which is prompted is not checked against the AccountCharge member database. This can be used to enter a Guest Name at a bar or any other appropriate reference text. The entry window displayed at the point-of-sale is different when the AccountCharge member database is being checked. The screenshot below illustrates the entry window when the AccountCharge database will be checked. When the point-of-sale is NOT checking against the AccountCharge database, the text at the top of the screen is Enter Reference Number and the Search Name and Search Number buttons are not displayed. The Search Name button may be used to retrieve active AccountCharge members by Account Verification Name. The Search Number button may be used to retrieve active AccountCharge members by Account Number. NOTE: The Account Number is actually a sixteen character text field. A Finalizing Media may also be configured to require the entry of an AccountCharge member s Account Number. The programming is by finalizing media and is illustrated below. The selection is accessible from Back Office Medias Finalize Media Authorization Tab. Note that there should be no check next to the box Override Account# Validation. If you have already entered an AccountCharge Account Number, either because it was compulsory or through the use of an Odyssey/BackOffice Suite Programming Accounts Selections 193

194 ACCOUNT NUMBER ENTRY button on a Sales Desktop, the number will be automatically pre-entered when you use the Finalize Media. If the check is to be paid by a different member, you can enter a different AccountCharge Account Number, or merely depress the Enter key to accept the number previously entered. A Service Charge is used at the point-of-sale to record amounts paid by AccountCharge members against their account balance. This is covered in the following section. Accepting AccountCharge Payments at the Point-of-Sale A Service Charge is used at the point-of-sale to record an amount paid by an AccountCharge member against an account balance. This is also the method used to record the purchase of a Gift Card. Setting up Gift Cards is covered in the following section. The programming is by service charge media and is illustrated below. The selection is accessible from Back Office Medias Service Charge Media Options Tab. The above Service Charge is used at the point-of-sale to record a fixed amount purchase of a $25.00 Gift Certificate, since the Manual Override check box is not checked. It is the check mark next to the text Account Credit Type which establishes the interaction with the AccountCharge database. Using AccountCharge for Gift Certificates/Cards Gift certificates/cards would be established as Internal Account Type 5 accounts. Procedurally, a batch of pre-numbered cards would be received at the location. These cards must be swiped on the BackOffice Server, to establish the encoded Gift Card Number as a valid AccountCharge Account Number. This procedure is quite fast, since the Account Type 5 would be set up to use the Total Credit Limit and no other Account Type Credit Limits and the default Total Credit Limit would always be $0.00. The following screenshot illustrates the programming of Account Type 5 under Account Type Programming Credit Limit Tab. Note the Account Type Name has been changed to Gift Cards. Note that the only credit limit being checked is the Total Credit Limit and the default Credit Limit for new Accounts (Gift Cards) is $0.00. Each Gift Card from the batch of pre-numbered cards is swiped from the screen AccountCharge Member Programming General Tab. Of course, this requires a keyboard wedge type magnetic card reader be attached to the BackOffice Server. The card should have the Account Number on Track 2. The magnetic card reader can be configured to provide a leading ; character and a trailing CR/LF character, or the leading ; can be encoded on Track 2. The latter is the method used most commonly. The screenshot of this tab, with the default programming for Account Type 5 Credit Limits as outlined above, is shown below. 194 Accounts Selections Odyssey/BackOffice Suite Programming

195 The procedure is: Left Click the Add icon. The screenshot shown above appears. The cursor is in Account Number. Swipe the Gift Card through the attached keyboard wedge magnetic card reader. The Account Verification Name will be pre-filled with the same entry as is encoded on the Gift Card. Left click the Save icon. Repeat step 1. This procedure provides a high degree of security, in that the Gift Card must be handled by a User with access to the BackOffice Server before being placed in the front-of-the-house for sale. At the point-of-sale, a Service Charge media button is used to record the sale of a Gift Card. The advantage of using a Service Charge button over a Received On Account type media is that the POS Operator can record the sale of a Gift Card during a sales transaction. There is no need for a separate Gift Card Sale transaction, although there could be one. The payment for the sale of the Gift Card is recorded identically to the payment of a sale of POS Items, using Cash, a Credit Card or any other finalizing media. The actual credit balance is not applied to the swiped card until the transaction in which the Gift Card was sold, through the Service Charge media, is paid in full. AccountCharge Buttons on the POS/2100 Desktop Using an AccountCharge payment has been covered. This is a Finalize Media programmed to require an Account Number, with no check in Override Account# validation. Recording the sale of a Gift Card, or accepting payment from any AccountCharge member at the point of sale has been covered. This is a Service Charge media programmed as an Account Credit Type. You may Inquire on the status of an AccountCharge member at the point-of-sale. The Button Type on a Sales Desktop is an INQUIRE ACCOUNT CHARGE button. You may associate an AccountCharge Account Number with a check using another button on a Sales Desktop. The Button Type on a Sales Desktop is an ACCOUNT NUMBER ENTRY button. AccountCharge Inquiry/Confirmation Screen A screen displays with all information related to an AccountCharge member which you select an INQUIRE ACCOUNT CHARGE button on the point-of-sale. This is the same information which will display if you select the Confirm Account Number Entry check box on the POS System Options Back Office Software programming form. The actual information displayed is slightly different depending on the Account Type of the AccountCharge member. The most detailed information is available for the Customer Account Type. A screenshot below illustrate the result of an INQUIRE ACCOUNT CHARGE selection for a valid AccountCharge member. The first line above is the Account Number. Note that it is actually an alphanumeric entry in this case. The second line is the Account Verification Name. The third line indicates that the last charge posting from Alan Schwartz, or the last time he was associated with a check for Patron/Loyalty, was on April 26, 2004 at 1:30 Odyssey/BackOffice Suite Programming Accounts Selections 195

196 pm. The fourth line indicates that the current account balance, in this case an amount due since it is a positive number, is $ We can discern that Alan has a $1, Total Credit Limit since the Available Credit shown on the fifth line is $ If Alan was configured to use the Daily Credit Limit, the amounts shown would relate to the Daily Balances. The sixth line indicates Alan s birthday so that a POS Operator can provide special handling for AccountCharge members. The text area at the bottom of the screen provides information to the POS Operator to improve the dining experience of Alan and is entered in the Patronage Tab of AccountCharge Member Programming. NOTE: The lines shown above, Account Balance and Available Credit may be suppressed if the amounts are not appropriate. To suppress these lines, set the text under Account Response Codes to a blank. Neither the text nor the currency amount will display on the above Inquiry Confirmation screen. Delivery POS/2100 Considerations The utilization of the POS/2100 and Odyssey BackOffice for Delivery applications is relatively simple. There are several programming considerations which should be addressed from the beginning, however. Sales Type and Operator Type Operator Type 3 and Sales Type 3 are "reserved" when using the POS/2100 for Delivery. On the button used to Transfer Delivery Checks, the only POS Operators listed in the far left column will be only those of Operator Type 3, the drivers. In the second column, the only orders listed will be those of Sales Type 3, those for delivery, by drivers. The printing of Delivery Instructions requires; first, that the flag "Print Delivery Info" be set under Printer Configuration Terminal Print Options, and second, that the order be Sales Type 3, those for delivery, by drivers. Transferring Delivery Checks The Button Type Transfer Delivery Checks is used to present a screen to easily transfer accountability to drivers. While this button can be placed on the Log In Desktop, for terminals which are used in delivery applications it is recommended that the flag "Delivery Transfer Button" be checked on the programming screen POS Terminal Options Desktop Options, under the "Table Desktop" programming area. For POS Operators who are entering Delivery orders, and also transferring delivery orders to drivers, you must set the option "Allow Check Transfers" on the programming tab Manager Settings under POS Operator Definition Programming. It is recommended that you also set the flag "Master Server" on the programming tab Operation Settings under POS Operator Definition Programming. Each Sales Desktop on any terminal being used for Delivery should generally have at least two buttons, Button Type Customer Lookup and Button Type List Checks. The reason for the Delivery Lookup is obvious, that is how a customer is associated an order. The List Checks provides quick access to the Table Desktop from a Sales Desktop. This provides the vehicle for transferring the checks and reviewing the status. The reason it is recommended that POS Operators transferring orders to drivers be Master Servers is to show all checks entered by any "operator" taking phone orders for Delivery. A Master Server will be presented with all outstanding orders on the Table Desktop. In addition, the guest check presentation on the Table Desktop has been modified to include two new elements of information at the bottom of the check to allow the POS operator to quickly respond to a follow up call from the customer on the status of an order. "Since Open 00:58" The length of time in minutes the check has been open. "Since Last 00:12" The length of time in minutes since the check was last opened or was transferred. 196 Accounts Selections Odyssey/BackOffice Suite Programming

197 Retention of Orders On POS/2100 When a delivery customer is identified at the point-of-sale, the POS Operator is provided the ability to duplicate a recent order. The number of days of orders retained for this purpose is programmable. The selection is made under Configure Archive Functions under "Delivery Checks For Recall". Regardless of the number of days set here, the last order will always be retained for recall. Tracking Totals/Delivery Statistics For Delivery Customers When a delivery customer is identified at the point-of-sale, the POS Operator is presented with a screen which not only allows for the duplication of a recent order, but also provides a summary of the information retained on the point-of-sale. NOTE: The summary information presented at the point-of-sale IS NOT a summary of the information stored in the BackOffice and available through Odyssey Reports. It is ONLY a summary of the "Delivery Checks For Recall" which are retained at the point-of-sale terminal. The "standard" information presented includes the number of days since the oldest check retained at the point-of-sale, the number of checks retained (generally the number of visits) and the net sales. In addition, three separate counters and totals may be summarized. These separate "tracking" totals are programmed under Accounts Delivery Statistics and may represent any menu item, any category or any department. This information is often useful when placing coupons along with the order for either delivery or pickup Using Caller ID with Delivery The POS/2100 supports all Caller ID controllers from CallerID.com via an RS-232C connection. The initial release of the POS/2100 in October of 2004 only supported the direct connection of the controller to a single terminal. Current versions support a connection of the controller to the server, allowing for multiple incoming lines and for connection to a selected incoming telephone line at any terminal. General Operation A minimized application, CallerIDService.exe, is constantly executing on the server. It is monitoring the RS232C port to which the CallerID controller is attached, generally the COM1 port. As a call comes in, the information from the controller is buffered by the application and placed in a folder on the server. Client POS terminals have access to this folder. When a single call is incoming, the POS Operator will answer the phone and then depress the Customer Lookup button on the Sales Desktop of the POS/2100. Since there is only one call coming in, the information will be directly transferred to the Customer Information screen. If the incoming phone number matches an existing customer, that information will be instantly displayed. If two or more calls come in prior to any POS Operator depressing the Customer Lookup button, a list of incoming calls will be displayed when the Customer Lookup button is touched. The list will show each incoming line number, the incoming telephone number and the customer last and first name. The POS Operator merely touches the correct incoming line, the one matching the line he or she has just picked up, and that information is immediately transferred to the Customer Information screen. Odyssey/BackOffice Suite Programming Accounts Selections 197

198 POS Operation With Multiple Incoming Calls When the Customer Lookup (Delivery Lookup) button is touched and there are multiple incoming calls, a screen will display showing each line number, the incoming telephone number and the caller's name. The POS Operator touches the correct line number and the information is transferred to Customer (Delivery) Information screen. CallerIDService.exe A separate application program must be running on the server to support the CallerID controller. This program, CallerIDService.exe, will be located in the folder c:\icom\pos2100 and a shortcut to this program should be included in the startup folder, along with the shortcut which establishes the G: drive on the Server and invokes WRemoteS.exe. The CallerID controller is attached via an RS232C connection. The default connection is to the COM1 port. This is established in an ini file located in the folder c:\icom\pos2100, CallerIDService.ini. This is a text file and should be edited if for some reason the connection is to a port other than COM1. A listing of the default for this ini file is as follows: [Main] CallerIDDirectory=C:\ICOM\POS2100\CallerID CallerIDPort=1 Simply change the 1 in the ini file to the correct COM port designation. The connection to the CallerID controller is always set as 9600, N, 8, 1. The path above should generally not be changed. Note that this is the pa th used by the program CallerIDService.exe which is executing on the server itself. The path to this folder for the client POS terminals is set under POS Terminal Options IO Devices on the Misc Devices Tab with th e selection ControllerIDPath. This path for the client POS terminals is G:\POS Accounts Selections Odyssey/BackOffice Suite Programming

199 POS/2100 Application Programming Overview The primary programming functionality which is built into the point-of-sale application software is the configuration of the graphical user interface (GUI). Most of the programming related to how things operate is configured with the Odyssey Programming module. The POS/2100 will operate at any screen resolution, however it is recommended that a minimum resolution of 800 x 600 be utilized at the point-of-sale. It is a very good idea to actually configure the GUI on a PC which is set to the same resolution as the point-of-sale terminals. For example, if your terminals will be configured with an 800 x 600 resolution and you initially configure your GUI on a Back Office Server with a 1024 x 768 resolution, you will find that the text does not always fit on the point-of-sale buttons. Terminals with an LCD screen have a fixed resolution based on the number of pixels. While you can often obtain a kind of crippled display at a lower resolution, it is the number of pixels in the LCD panel itself which determines the actual display resolution. The 12.1 Odyssey terminals have a resolution of 800 x 600. A CRT screen can generally be set to either 800 x 600 or 1024 x 768. The 15 LCD monitor used in the Vision LE series has a resolution of 1024 x 768. Most 15 LCD monitors available with touch screens, as of the date of this documentation, use a 1024 x 768 screen resolution. All of the point-of-sale terminals will utilize the same database for determining the GUI, the database POS2100.mdb. It is therefore a good idea to use the same display resolution on all point-of-sale terminals, although this is not required. If you have different resolution displays in a single network, you should configure your screens at the LOWEST resolution to assure that all of the text can be viewed on these terminals. This will often result in buttons which look exceptionally large, with text that appears somewhat small, on the point-of-sale terminals operating at the higher screen resolution. Programs And Files Loaded On The POS Terminal When the Odyssey POS/2100 software is loaded onto a terminal, an operating environment is created on the terminal. As of the date of this documentation, only Windows/98 is supported as a client point-of-sale terminal. The executable programs which are loaded onto the point-of-sale terminal include: POS2100.exe. Located in folder c:\icom\pos2100, this is the actual executable point-of-sale program. It is written in Visual C++. WRemote.exe. Located in folder c:\icom\pos2100, this is the Print Client. It is written in Visual Basic 6.0. The functionality of this module is outlined in the section Printer Operation Software Overview (Technical). PrintCheck.dll. Located in folder c:\icom\pos2100, this body of software interacts with the point-ofsale application to format files which are forwarded to the Print Server. It is written in Visual C++. POSReports.exe. Located in folder c:\icom\pos2100, this is the body of software which generated the reports which can be displayed and printed from point-of-sale application program. It is written in Visual Basic 6.0. Update.bat. Located in the folder c:\icom\pos2100, this is a batch file which will update the hard disk of a client point-of-sale terminal with all new programs and graphics from the Back Office Server. A shortcut is automatically created on the Desktop of point-of-sale terminals. NOTE: If you are upgrading an installation with the latest release of programs and database configuration, you MUST use the Update.bat file on each and every terminal in the network to assure that the executables are copied to each terminal along with any new graphics files required by the application program. Odyssey/BackOffice Suite Programming POS/2100 Application Programming 199

200 A numb er of files are utilized, and created, by the point-of-sale application and are stored on the hard disk drive of the point-of-sale terminal. POS2100.ini. Located in folder c:\icom\pos2100, this contains initialization information for the pointof-sale program. NOTE: Aside from the single value relating to Training Mode (explained in the next section, do not attempt to edit the file POS2100.ini. All of the settings in this file should always remain at their default values. ErrorWRC.log. Located in folder c:\icom\pos2100, this contains information which might be requested by Comtrex support relating to error conditions encountered by the application program WRemoteC.exe. It is an ASCII text file. C:\icom\POS2100\LogFiles\. This folder contains up to thirty-one day-encoded log files which might be requested by Comtrex support. Each file is an ASCII text file and contains detailed information on every button depression on the point-of-sale network. An example is POS-06.TXT. This file would contain, in an ASCII text format, all log information for the last day which was the sixth day of the month. C:\icom\POS2100\Graphics\. This folder contains a number of additional sub-folders, all of which contain BMP and ICON files for use in the point-of-sale application. Training Mode on the POS/2100 Odyssey includes a Training Mode for the POS/2100. A POS Operator may be placed in Training Mode using a Button Type Access Training if it is placed on the Log In Desktop. When the button is touched, a Manager code will be required. This may require a fingerprint if that option is set. There is a list or related options which can be set in the file POS2100.ini, located in the folder c:\icom\pos2100 on the Server. A listing of the applicable setting follows: [Main] TMColorWM = Training TMColorRQ = False TMColorPC = False TMColorRD = False A banner displays on the guest check displayed on the POS Terminal when a POS Operator who is in Training Mode is using the terminal. For purposes of translation, this banner is defined using the definition "TMColorWM" and the default is "Training". When a POS Operator who is in Training Mode is using the terminal, the entry sequence is identical to normal operation, except as follows: The watermark "Training" (or as otherwise defined) appears on the Guest Check displayed on the POS Terminal. There requisition system is not operational. (RQ = False) There is no printed guest check. (PC = False) The customer display is not operational. (RD = False) There is no training total, since no check is printed and no requisition chits are generated and the customer display does not display at all. NO TE: Do not change any parameter definitions in the file POS2100.ini other than the two parameters "TMColor" and "TMColorWM". 200 POS/2100 Application Programming Odyssey/BackOffice Suite Programming

201 Changing Training Status of a POS Operator To change the Training Status of a POS Operator: The POS Operator must be logged on, i.e. able to use the POS terminal, to be placed in Training Mode. Touch the button Access Training and validly enter a Manager number of fingerprint identification. POS Operators in Training Mode will be highlighted in blue. To place a POS Operator in Training Mode, touch the POS Operator Name. To remove a single POS Operator from Training Mode, touch the name. The blue highlight will be removed. To remove all POS Operators from Training Mode, touch Un-Select All. Touch the Cancel button to exit the screen. NOTE: The end of day process on the BackOffice Server will remove ALL POS Operators from Training Mode automatically. POS Operation in Training Mode Training Mode checks do not print, they do not requisition, the customer display does not function and there is a watermark on guest check shown on the POS Terminal's display. There is no training total. No totals in the BackOffice are affected during Training Mode. Normal guest checks begin at 0001 at the beginning of a Sales Day. They "wrap" at 8999 back to A different sequence is used for Training Mode. Training Mode checks will display beginning at the number 9001 and "wrap" at 9999 back to Both sequences are reset at the end of day Accessing POS/2100 Programming As indicated in the previous section, all information which is configured through the POS/2100 programming is contained in a single database, POS2100.mdb, stored in the folder c:\icom\pos2100\ on the Back Office Server. NO TE : It is highly recommended that point-of-sale application programming be performed on the Back O ffice Server. This programming section is NOT configured to allow multi-user or simultaneous programming on two separate terminals. To access the Programming software of the POS/2100 application from BackOffice Programming, click on the POS/2100 icon at the top of the screen, as shown below. You will already be in Programming mode of the POS/2100. You WILL, however, need the POS Operator Number for an authorized Operator to exit. While it is not recommended, you can perform point-of-sale programming changes while the system is operatio nal. However, the changes WILL NOT be implemented on the individual point-of-sale terminals until the application program itself is terminated, then re-started. In order to access POS/2100 Programming, a POS Operator number is required. The POS Operator must have the POS Programming Allowed flag set to a Yes, under POS Operator Programming Manager Settings Tab. Launch the point-of-sale application program. In order to launch, the Network Name of the computer on which you are launching the application must be included as a Terminal Name in the list programmed under the selection POS Terminal Options Posting Configuration. Odyssey/BackOffice Suite Programming POS/2100 Application Programming 201

202 When the Log In Desktop is presented, use the displayed numeric buttons (on the default Log In Desktop) to enter the Secret Number programmed under POS Operators General Tab. Do not depress the Enter button. Do not use a swipe of a magnetic card. Each entered number will display as a * character in the Entry Window. With the * characters in the Entry Window, right click on a black area, which is the Windows (or Desktop) Background. When the small drop down appears, left click on the bottom selection Turn Programming On. NO TE: You MUST have a numeric keypad (or a magnetic card reader) on the Log In Desktop in order to access (or exit) the programming mode of the point-of-sale application. POS Operation During Programming The default Log In screen contains a Status Window at the very top. When the point-of-salselected application is in the programming mode, this window will generally contain positional information on either itself, or a object. In order to configure the GUI for the point-of-sale application, it is necessary to move around from desktop to desktop. It is also necessary to be able to enter items to view the presentation on the guest check and on various Popup windows. These are not real sales. The ability to enter items and pay, from within the programming portion of the application, is necessary to configure the GUI. No information entered during programming will display or print anywhere, nor will it accumulate in any totals. The access to programming, and the exit from programming, is recorded in the Manager Log report available in Odyssey Reports. Point-Of-Sale Desktop Types There are four principal Desktop Types within the point-of-sale application which may be configured and a fifth which is not configurable. Depending on the desktop, different buttons or objects may be placed on the desktop itself. The organization following this section is a lead-through presentation of the various buttons and objects which may be placed on each of these desktop types. Log In Desktop. This is the desktop presented immediately after the point-of-sale application is launched. There is no POS Operator defined when this Desktop is being displayed. This MUST be the Desktop being displayed on all point-of-sale terminals when the End Of Day process is performed on the Back Office Server. There can be multiple Log In Desktops defined within the database, each of which presents different buttons as options, based on the terminal itself. This is programmed from the POS Terminal Options Desktop Options as the Default Log In Desktop. Of course, you must first create more than one Log In Desktop in order to be able to select one appropriate for a different terminal. As an example, in a cashier environment where POS Operators are not banked, the cashier terminal will require a Shift Select Button on the Log In Desktop. It would be inappropriate for this button to be on the Log In Desktop of the pre-check terminals, since the active shift on the pre-check terminals will be a default shift. Manager_View Desktop. This is an "optional" Desktop. It can only be accessed from the Log In Desktop through Button Type Manager. It can be used to reduce the number of buttons displayed on the Log In Desktop by removing all "Manager Required" buttons to this Desktop. Table List Desktop. This is the desktop typically shown to a POS Operator functioning as a Server immediately after the Log In Desktop. There is ONLY ONE Table List Desktop, however, the area at the far right of this screen can show multiple table sections. The table sections are configured through programming of the Table List Desktop. Once you have configured multiple table sections, you can use their names to assign a Default Table Section on the POS Operator Programming General Tab. Sales Desktop. This is the most common desktop displayed by the point-of-sale application. Sales and payments are recorded from a Sales Desktop. 202 POS/2100 Application Programming Odyssey/BackOffice Suite Programming

203 Split Check Desktop. This is a desktop used to move items to a new check when a check is being split. There is very little configuration required, and even applicable, to this desktop. Closed Check Desktop. There is no configuration applicable to this desktop. It is listed herein for the sake of completeness. In addition to desktops, there are a variety of Popup presentations which may be accessed from the point-of- and their functionality will be covered when sale application. The GUI for these Popups is not configurable the buttons which are used to present the Popups are covered. Point-Of-Sale Application Text The point-of-sale application, like all modules of the total Odyssey Suite, is totally translatable. The translation is performed using the software module LanguageEditor.exe. This module is accessed from Odyssey MWS by a left click on Edit, then a left click on Language Database. When the Language Editor is invoked, use the dropdown list under Application List to select POS Application. The language database selection used by ALL point-of-sale applications must be the same. It is not possible for one terminal in a network to use English and another Dutch. The language selection for the point-of-sale applications is set from Odyssey MWS. Left click on Edit, then left click on Back Office Configuration. When the list of tabs is displayed, select the Language tab. Use the dropdown next to the text POS Application Language and select from the drop down list of languages. Programming Tips The general methodology for programming the GUI for the point of sale is quite structured. Access the programming mode of the point-of-sale application software. Select the Desktop you wish to program. The vast majority of your actual programming effort will be devoted to the various Sales Desktops. Add an object to the Desktop. The vast majority of the objects you will be adding will be button windows. Position your object. The best way to assure correct positioning of objects is to drag the left or right side, then the top or the bottom. The exact coordinates of the left edge, right edge, top edge, bottom edge, total width and total height are displayed in the Status Window at the top of the Desktop. For button windows, select the number of rows and columns, then choose a standard font and button color. For each button on your button window, complete the programming by selecting a Button Type, creating a custom color and font if desired, place a graphic on the button if desired and enter up to three lines of text. There are a number of hints which, if you follow them from the beginning, will make the Desktops you create easier to manipulate after creation and speed the process of either modifying existing desktops or creating new desktops. Always create your Desktops under the same display resolution as the point-of-sale terminals. If you MUST use different display resolutions on different point-of-sale terminals, use the lowest resolution when creating Desktops. Start with a single Sales Desktop template. Get everything right on this template before creating multiple new Sales Desktops. This includes the format of the guest check, the position of the Entry Window, the position of the Banner Display and any fixed button windows you want on ALL Sales Desktops. Each object on each desktop is a SEPARATE object. It is quite easy to save this template under a new name, then add button windows for lists of preset items or Popup window select buttons. But if you decide later that you want your guest check smaller, or a different color, or with lines rather than no lines, you must edit the Guest Check object on each and every Sales Desktop. Always leave an area of Windows background accessible on EVERY desktop. You MUST right click in the Windows background area to save the desktop. Odyssey/BackOffice Suite Programming POS/2100 Application Programming 203

204 When programming button windows, it is a good idea to leave the spacing selection at a minimum of 2. The software will not accept a spacing entry of 0, although it will accept a spacing of 1. In order to affect the entire button window, you must right click in a Windows background area of the button window itself. Always program using a mouse, not a touch pad. It is quite difficult sometimes to select a Windows background area, either on an entire desktop or within a button window. In addition, when you are dragging the sides or top/bottom of a button window, it is much easier to hold the left button on the mouse down and drag than it is to perform this function with a touch pad. Always save your desktop before proceeding to another desktop. Each and every time you attempt to move to another desktop, the software will prompt Changes have not been saved! Continue to new desktop? This prompt will appear EVEN IF you have just saved the desktop. When saving desktops exercise care not to overwrite an existing desktop. The best methodology is to create your template, save it, then save the template under the name you are going to assign to the new template. If you begin editing your template, under its template name, often you will (in a hurry) save your newly created Sales Desktop under the name of your template. Desktop Objects Button Window This is by far the most common object placed on any Desktop. When you select Add Object, then select Button Window, a small object similar to a 2 x 2 keyboard will appear on your desktop. Sizing/Positioning A Button Window It is probably better to position the button window on the desktop before changing the number of buttons on the button window. There are two ways to size, or position, a button window. The first way to position a button window is to move the cursor to the background area of the button window, left click and hold the button down on the mouse, then move the entire button window. The screenshot below shows the initial presentation when a button window is added. The white area surrounding the four gray buttons above is the Windows background area. With the cursor pointing within this background area, you can left click, hold and then move the entire button window. The second way to position a button window is to move the cursor immediately above an edge; left, right, top or bottom. When you do so, the cursor will show as a line with arrows on either end. Hold the left button down and move the left, right, top or bottom edge of the button window to the desired location. The Status Window will show the exact coordinates of the positioned button window. This will allow you to line up button windows. The screenshot below illustrates the Status Window. The actual numbers displayed will depend on the screen resolution of the display on which you are performing the programming. For all resolutions, the minimum Position Left and Top will be 0. For screen resolutions of 1024 x 768 screen, the maximum Right will be 1020 and the maximum Bottom will be 764. The Width and Height are provided to assist in lining up button windows. 204 POS/2100 Application Programming Odyssey/BackOffice Suite Programming

205 If you have initially configured your Desktops on one screen resolution, then access the programming mode on another screen resolution, the displayed numbers will be different. They will automatically re-size to the proper relative numbers. The maximum Right with a resolution of 800 x 600 will be 796. The maximum Bottom with a resolution of 800 x 600 will be 596. Button Window Object Properties Certain properties of the entire button window object can be set to apply either to the object itself, or to each and every button within the object. To access this programming, place the cursor within the Windows background area of the button window and right click. You will see a selection dropdown as illustrated in the following screenshot. Button Window Button Font (All) Selection Left click on this selection to program the size and color of the text information on ALL buttons in this button window. The displayed window is illustrated in the screenshot below. For most buttons on a point-of-sale terminal with an 800 x 600 resolution, a size of 8, 10, 11 or 12 is appropriate. Of course the choice of Font is up to the programmer, but the default database generally uses the Arial Font and always used a Font Style of Bold. An interesting choice which seems to take less space than Arial is Comic Sans MS. You can start with all buttons of the same font, then individually tailor buttons as you choose. NOTE: If you have already tailored several buttons with different fonts and font colors and button colors, do not use this selection. It will change ALL buttons to be identical, thereby losing all of your hard work in individually tailoring the buttons. Odyssey/BackOffice Suite Programming POS/2100 Application Programming 205

206 Button Window Button Color (All) Selection Left click on this selection to program the button color of all buttons in this button window. The displayed window is illustrated in the screenshot below. This is the standard Windows color palette selection. Note a handy tool is the Add to Custom Colors button at the bottom right, which has been clicked in the screenshot above. Not so much for this selection, but when you are individually programming colors on buttons, it is very helpful to right click on a button you have alread y programmed, with a color you have worked hard to get just right, and then use this button to add it to your Custom Colors so that you may make another button the same EXACT color. Button Window Button Square (All) And Button Round (All) Selections Left click on this selection to program the shape of all buttons in this button window. The selection Square will actu ally result in a rectangular shape depending on the number of rows and columns and the shape of the overall button window. Likewise, the selection Button Round will actually result in an oval, as illustrated in the screen shot below. (The font illustrated below is Comic Sans MS.) Note that with Round buttons, it is often difficult to right click into the background area of the button window, because this background area is ACTUALLY defined as if the buttons themselves were Square. Button Window Cut Selection Left click on this selection to delete the button window from this Desktop and place it on the clipboard. The butt on w indow may be pasted onto another Desktop. It is much more common to use the Copy selection when moving a button window from one Desktop to another, however. Button Window Spacing Selection Left clic k on this selection to indicate the spacing between buttons on the button window. The selection is in the number of pixels. The default selection for newly added button windows is 4. The software will not allow a spacin g of 0, and it is recommended that you use 2 as a minimum due to the difficulty in positioning the cursor into the button window background with a single pixel as the spacing. Generally, the smaller the buttons, the smaller you will want the spacing and the larger the buttons, the larger you will want the spacing. 206 POS/2100 Application Programming Odyssey/BackOffice Suite Programming

207 Butto n Window Rows/Columns Left click on this selection to set the number of buttons in this button window. Note that each button in a button w indow must be the same size, since the only selection is the number of rows and the number of columns. If you wish to have a large button on what appears to be a single button window, you must break the buttons down into button windows of a fixed number of rows and columns. The screen shot below illustrates three separate button windows which appear as one when the point-of-sale application is running. The above screenshot shows three button windows, a 1 row by 1 column, a 1 row by 2 columns and the bottom is a 1 row by 4 columns. The background color of the button window itself is the same as the background color of the desktop and there is no border on any of the three button windows. Button Window Window Color Left click on this selection to program the background color of the button window. A common color should be selected for both the button window s Window Color and the Background Color of the Desktop if you wish to make buttons appear to Float. You would also set no Border. Then the background of the Desktop blends into the Window Color of the button window. Button Window Window Border Left click on this selection to create a border around your button window. The screenshot below illustrates the appearance of a button window with a border. The gray box around the 4 row by 3 column button window is the border itself. The Window Color of the button window and the Background Color of the Desktop are both black. Button Window Delete Object Left click on this selection to delete the button window. There is NO un-delete selection, so be sure you are ready to throw this button window away prior to deleting the object. Button Configuration In A Button Window The kinds of buttons which can be placed on the various desktops are slightly different. For instance, you can not place a preset item on a Log In Desktop. However, the methodology of programming an individual button in a button window is the same on all desktops. To configure a particular button in a button window, right click on the button itself. A dropdown selection will appear as illustrated in the screenshot below. Odyssey/BackOffice Suite Programming POS/2100 Application Programming 207

208 Button Configuration Properties After right clicking on an individual button in a button window, left click on the bottom selection Properties. This is the basic button configuration selection. The screenshot below illustrates the primary configuration window. It is best to follow the order listed below when programming buttons. Button Type. The Button Type defines what kind of button this will be. The available buttons are different on the Log In Desktop than the Sales Desktop. Use the down arrow at the right of the displayed window to select the appropriate button Type. Lookup. Depending on the Button Type this button is used to display a selection list, e.g. a Button Type of Popup Items will display a list of all List Files. Square or Round. This selection is identical to the selection provided for all buttons on a button window, but on an individual button basis. Face Color. This selection is identical to the selection provided for all buttons on a button window, but on an individual button basis. Font. This selection is identical to the selection provided for all buttons on a button window, but on an individual button basis. Image. This selection allows for a graphics image to be placed on the button. The two accepted graphics types are a BMP file or an ICON file. Icon images will be placed on the left of the button. A BMP file may either remain at its fixed size or enlarge to fill the button, depending on the setting under POS System Options Desktop Options under Bitmap Expand. Note that when you select a graphics image, the line Mid Text is overwritten with the name of the graphics file. Use the Find button to browse through the graphics folder. Use the Clear button to remove the graphics file. Transparent. This check box only pertains to certain kinds of BMP graphics files. If there are transparent areas in the graphics, then the button color will show through with a check in this box. NOTE: As explained earlier, graphics images are contained on the hard disk of the terminal executing the point-of-sale software. If a message is displayed on the point-of-sale that a bitmap can not be found, you should execute the batch file Update.bat on each point-of-sale terminal. Top Text. This entry pertains to the top line of up to three which may be displayed for this button. In general, if you are using a BMP graphics file, you should leave all three of these lines blank. For an ICON file, you may want to place several leading space characters in any text lines. Mid Text. This entry pertains to the middle line of up to three which may be displayed for this button. 208 POS/2100 Application Programming Odyssey/BackOffice Suite Programming

209 Bottom Text. This entry pertains to the bottom line of up to three which may be displayed for this button. ASCII. The small box to the right of the line Mid Text will display a heading of ASCII if the Button Type selected is ASCII. An example is the numeric keypad, where the displayed Mid Text line is a 7 and the entry in this box would also be a 7. Auxiliary Text. This entry places preceding ASCII text in front of certain Button Types. For example, a $10.00 fixed amount Cash Entry button is a Button Type of Media and the Auxiliary Text is 10. Or This entry also works in conjunction with the Repeat Button Type, with either no Auxiliary Text (repeats the highlighted quantity) or an Auxiliary Text Entry of 1 to repeat only one. Next Highest Dollar. This check box only pertains to a Button Type of media and is the way of setting up a payment of next even dollar preset button, e.g. $5.31 is owed, a Media Preset with this box checked would function as $6.00. Button Configuration Reset This is a seldom used selection. A left click on this selection will remove any graphics, set the Button Type to Undefined and set the button text as an indicator of the button position in the button window. After you left click on the Reset selection, the button will not appear to have changed. However, as soon as you select Properties, then Cancel, you will see that indeed, you have removed any and all programming associated with the button. Button Configuration Cut This is a seldom used selection. A left click on this selection will act upon the selected button EXACTLY the same as the selection Reset. However, all the properties of the button will be copied to the clipboard. The generally used selection is Copy, so as to not lose the configuration on the source button. Button Configuration Copy A left click on this selection will copy all of the button properties to the clipboard. This includes the graphics. It is often used when placing multiple Preset buttons on a desktop, since it not only copies the button color and font settings but also copies the name of the List File itself, and allows use of the Lookup button to select another Preset button. Buttons may be copied from one button window to another. Buttons MAY not be copied (i.e. placed on the clipboard) and then pasted onto a button window on a different Desktop. The only way to move a button from one Desktop to another is to copy the entire button window, then paste the entire button window onto another Desktop. However, even if you are only looking to copy two or three buttons, it is often easiest to copy an entire button window to a Desktop, knowing you will delete it, just to be able to copy then paste individual buttons onto a button window on the other Desktop. Button Configuration Paste A left click on this selection will paste a previously copied button onto the selected button. Desktop Objects Status Window Generally, there will be a Status Window on every Log In Desktop and every Sales Desktop. In programming, it is the Status Window which displays the coordinates of a highlighted object. During sales operation, the Status Window displays the descriptor and amount for items purchased and payments made. Once you have added a Status Window, you can size it just as a button window was sized, and set parameters relating to the colors and font. When you right click within a Status Window, the following screenshot illustrates the choices. Odyssey/BackOffice Suite Programming POS/2100 Application Programming 209

210 Text Font. This selection defines the Font displayed within the Status Window and the screen presented when you left click on Text Font is identical to the selection provided for all buttons on a button window. Window Color. This selection defines the background color within the Status Window. Of course, you will want a contrast between the Text Font color and the Window Color. A left click on Window Color presents the identical selection to the one provided for all buttons on a button window. Window Border. This selection determines whether or not there is a border around the Status Window, the same way as the selection under button windows. Delete Object. This selection deletes the Status Window object from the Desktop. There is no Undelete selection; you must simply add another Status Window. Desktop Objects Bitmap Window A Bitmap Window is one of two ways to get a graphics image on a Desktop. The other is to place a 1 column Button Window, define the button as Undefined and then place a graphics image on the 1 row by button. Immediately after selecting Bitmap Window as an object to add to a Desktop, you are presented with a browser to select a BMP file. You can not add an ICON file as a Bitmap Window. Once you have selected a BMP image, you can size the object the same way as a button window is sized. After the object is on the Desktop, a right click on the Bitmap Window will present the following selection window. These selections are virtually identical to the selections under Status Window. NOTE: The Log In Desktop is the Desktop which most frequently might have a Bitmap Window. However, the recommended method for placing a graphics image on the Log In Desktop is to create a 1 row by 1 column Button Window, make the Button Type Undefined then place the graphic on the button. Desktop Objects Entry Window The Entry Window object is generally placed on Sales Desktops. It is the area in which entered numbers are displayed. On the Log In Desktop, all entered numbers are displayed as * characters to protect the security of the POS Operators Secret Numbers. After adding the Entry Window object, you can size the object the same way a button window is sized. A right click o n the Entry Window will present the following selection window. 210 POS/2100 Application Programming Odyssey/BackOffice Suite Programming

211 These selections are virtually identical to the selections under Status Window. Desktop Objects Previous Order Window The Previous Order Window object may be placed on either the Log In Desktop or any Sales Desktop. The Previous Order Window is used primarily in counter service/quick service situations where the screen of the point-of-sale is used as a kind of mini-requisition screen. The amount of space allocated to the Previous Order Window on any desktop is a function of the sizing of the object itself, however the number of lines which will display is fixed at thirty-three. A Previous Order Window which is too small will result in illegible text. A screenshot of a very small Previous Order Window, as it appears in programming mode follows. Previous Order Window Object After adding the Previous Order Window you can size the object the same way a button window is sized. A right click on the Previous Order Window will present the following selection window. Odyssey/BackOffice Suite Programming POS/2100 Application Programming 211

212 These selections are virtually identical to the selections under Status Window. Desktop Objects Alarm Clock The Alarm Clock Window object may be placed on either the Log In Desktop or any Sales Desktop. In counter service applications, it should be placed on every Sales Desktop, if implemented at all. The background color, font size and color are programmable as is the format, 24 hour or am/pm. There are two different programmable alarm times. When the object is touched, the display shown below will appear. It allows the POS Operator to select up to two alarm times, whether the alarm is a flashing clock, a beeping noise or both. There is a text message associated with each alarm as well. The alarm can be made to occur Daily, so the message might be "Happy Hour Starts in 2 Minutes". You turn the alarm off by touching the clock. There is one "set" of alarm times for the terminal, not for each clock object, so if you put the Alarm Clock object on the Log In Desktop and each Sales Desktop, the POS Operator will see the alarm only once, on the Desktop being displayed at "alarm time". Log In Desktop Selection Options Once you have accessed the programming mode of the point-of-sale application, you are now able to configure desktops. To affect the desktop, right click again in a black area which is the Windows Background. From the Log In Desktop you will be presented with the following selection window. Turn Programming Off. A left click on this selection will exit the programming mode. Note, however, that the Status Window will continue to display position information. NOTE: When exiting the programming mode, you should ALWAYS exit the point-of-sale application then restart. Also, changes made to the GUI using the programming mode ARE NOT EFFECTIVE at point-of-sale terminals until the application is exited, then restarted. Screen Size. Do not click on this selection. Button Window Color (All). This selection is similar to the Button Color (All) selection under button windows. It allows you to change the color of all buttons on all button windows on the Log In Desktop. It is a seldom used selection. 212 POS/2100 Application Programming Odyssey/BackOffice Suite Programming

213 Button Window Border (All). This selection is similar to the Window Border selection under button windows. It allows you to add a Window Border to each and every object on the Log In Desktop or to remove any Window Borders on each and every object on the Log In Desktop. It is a seldom used selection. Desktop Color. This selection allows you to set the color of the Windows Background on the Log In Desktop. Desktop Pattern. This selection is not functional. You can only set a color for the Log In Desktop. The selected Desktop Pattern WILL NOT be retained, although it will appear to take in the programming mode. Add Object. The following list will appear when the cursor is moved over the Add Object selection. All selections have been described in previous sections. Save Template and Load Template. These selections are covered in the following two sections. Desktop Selection Save Template You MUST explicitly use the Save Template selection to save any changes you have made to any Desktop. From any Sales Desktop, when you attempt to move to another Desktop the following Popup will display. This Popup will display on the Sales Desktop even if you have JUST saved the template. It is to prevent losing, accidentally, all of your work in configuring a Sales Desktop. The prompt DOES NOT appear when you have made changes to the Log In Desktop. NOTE: Do not forget to explicitly use the Save Template selection after you have made any changes to the Log In Desktop. When you left click on the Desktop Selection Save Template, you are presented with a list of all existing templates, by Template Name, of the same type of Desktop. The screenshot which follows illustrates the display when Save Template is clicked from the Log In Desktop where two Log In Desktops exist. Odyssey/BackOffice Suite Programming POS/2100 Application Programming 213

214 Note that the Template Name of the Desktop which you have just finished modifying defaults to the selection window at the top of the screen. Note that this Template Name is also displayed below in the list of ALL existing Log In Desktops, by Template Name. To save your work on the Desktop and use the same Template Name, merely click on the OK button. To save your work on the Desktop under a different Template Name, type in the new Template Name, then click on the OK button. This is the method for creating new Desktops. You can save your work on the Desktop using an existing Template Name by left clicking on the other name, then clicking OK. Note, however, that this is a highly unlikely scenario. If you wanted to edit an existing Log In Desktop, you would most likely have used the Load Template selection first. Desktop Selection Load Template You should only select Load Template if you have either not made any changes to the Desktop which is being displayed or if you have just used the Save Template selection to save any changes. The Desktop Selector display when you left click Load Template is identical to that which is displayed when you left click on Save Template. The Template Name which is displayed in the window at the top of the Desktop Selector is the name of the currently displayed Desktop. To load another existing Desktop, left click on the Template Name in the list at the bottom, then left click on the OK button. NOTE: If you select Load Template after having made changes to a Desktop that were NOT saved, then you have lost all the changes you have made. Deleting Desktops You can delete a Desktop either by starting with the Save Template selection or the Load Template selection. When the Desktop Selector window is displayed, as shown in the Save Template section, as soon as you left click on a Template Name in the list at the bottom, the Delete button becomes visible. It DOES NOT become visible if you left click on the current Desktop. To delete a Desktop, left click on the Template Name in the list, then left click on the Delete button. There is no Un-delete functionality when you delete a Desktop. You can not recover the Desktop. It is gone. There is no Recycle Bin from which to recover the Desktop. Be sure you really want to delete the Desktop before clicking on the Delete button. 214 POS/2100 Application Programming Odyssey/BackOffice Suite Programming

215 NOTE: You MUST have at least one Log In Desktop. Since you can not delete the currently displayed Log In Desktop, it is not possible to NOT have at least one Log In Desktop. This holds true for the Sales Desktops as well. Log In Desktop Button Types Many Button Types may be placed on either the Log In Desktop, a Sales Desktop or the Split Check Desktop, while certain are restricted as to the Desktop on which they may be placed. All of those which are listed herein may be placed on the Log In Desktop. Button Type Access Training Used to assign POS Operators to a training status. A Manager must enter an ID or use the fingerprint reader. This Button Type may only be placed on the Log In Desktop or the Manager desktop. Button Type ASCII Used to enter a single digit/character of keyboard type information. The numeric keys on the default Log In Desktop are examples of ASCII Button Types. The ASCII character is entered in the small box immediately to the right of the Mid Text line on the Properties Form for Button programming. This Button Type may be plac ed on any Desktop. There are four special types of ASCII Button Types which are particularly useful on Sales Desktops used for payments. Button Type ASCII Calculate Type If y ou select Button Type ASCII, and select the * character as the ASCII character, you will have created the ability to multiply from within the Entry Window. The request was to be able to accept multiple fixed amount payments, specifically travel vouchers, where the denominations were not fixed, i.e. the patron hands over four $2.75 travel vouchers. The denominations could be in any amount, so multiple fixed amount payment media buttons were not appropriate. The entry method would be to touch 4, then touch the ASCII Calculate button with a * as the ASCII character, then touch 2, then.,then 7, then 5 then touch the Finalize Media button. It would be just as if the POS Operator had entered $11.00, or four times The Button Type may also be used with an open entry preset, i.e. an open department. The other ASCII Calculate Types are +, - and /. Button Type Change Operator Secret Number Used to change the POS Operator Secret Number (assign a new Magnetic Card) to a POS Operator. The POS Operator must have a check in Manager Mode Allowed under the POS Operator Programming Manager Access Tab. Also, the flag programmed under POS System Options System Options must be set to allow this button top operate on the POS. Changing this number at the POS without Fingerprint identification of Managers may be a PCI compliance violation. The software presents a list of all active POS Operators who do not have the flag "Manager Mode Allowed" flag set. The exception is that the current POS Operator's name is shown to allow someone to re-assign their own Secret Number. However, one Manager can not change the Secret Number of another Manager. This must be done using the BackOffice Programming module. The screen presented is shown below. Odyssey/BackOffice Suite Programming POS/2100 Application Programming 215

216 Touch the Operator's name and then touch either "Assign" or "Unassign". The "Unassign" button will set the Operator's Secret Number to his/her sequential number, followed by "-XXXX". This will effectively prevent the POS Operator from using the point-of-sale system. To change the Secret Number of a POS Operator, touch the "Assign" button. A window prompts for the new Secret Number. Enter the number then touch "Enter" or swipe the new Magnet Card assigned to the Operator. Since the POS Operator Secret Number must be unique, the software will not allow a single number (Magnetic Card) to be assigned to two different POS Operators. If a conflict occurs, the screen will prompt as shown below: The number, or magnetic card, is already assigned. Touch the "Ok" button, then use the "Unassign" function to remove the assignment from POS Operator Kathryn K. and then assign the number or magnetic card to the selected POS Operator. Button Type Clear Used to clear an entry in the Entry Window. Aside from the text to display on the button, there is no additional programming associated with this Button Type. This Button Type may be placed on any Desktop. Button Type Closed Checks Used to access the Closed Checks Desktop. This Button Type may be placed on either the Log In Desktop or the Sales Desktop. When placed on a Sales Desktop, it will no longer function once a transaction has begun. On a Sales Desktop, a similar Button Type is available, the View Prior button. The View Prior button presents a list identical to the Closed Checks list, however, only checks closed on the terminal will be displayed and Print is the only option available. The Closed Check Desktop provides four functions. Either manually enter the POS Operator s Secret Number, then touch the button, or first touch the button and then swipe a magnetic card when the Manager ID entry Popup appears. Always use the POS Operator ID whose closed check you are modifying. 216 POS/2100 Application Programming Odyssey/BackOffice Suite Programming

217 By displaying all guest checks/receipts which have been closed during the current Sales Day, it allows a quick method of viewing transactions already rung. Allows for re-printing a receipt for a transaction which has already been rung. The receipt will always print with a header of Reprint Closed Check. Provide a method of opening the closed check and presenting the Sales Desktop defined under POS Terminal Options Desktop Options as the Closed Check Desktop for purposes of changing the payment method or a tip amount. Provide a method of opening the closed check and presenting the Sales Desktop defined under POS Terminal Options Desktop Options as the Closed Check Desktop for purposes of performing a transaction refund or transaction overring. NOTE: In order to open the closed check, the POS Operator must have Manager Access to either Allow Refunds or Allow Media Transfers established under POS Operator Programming Manager Tab OR the flag "Mgr Rqd Reprint Closed Check" is not set true. Closed Check Desktop When the Closed Checks button is touched, the display presentation will be a separate listing of all guest checks/ receipts closed during the current Sales Day. A screenshot follows which illustrates the Closed Check Desktop. There is NO configuration applicable to the Closed Check Desktop. The functionality is controlled by t he point-of-sale application itself. While the screenshot above only shows two checks, typically the presentation will contain hundreds of checks. The closed checks can be sorted by Check Number, Table Number, Terminal, POS Operator, Time or Sales Type by merely touching the appropriate title at the top of the screen. To view a particular check, merely touch the line on the check listing. In the screenshot above, Check 2 has been touched. To print a particular check, first touch the line on the check listing, then touch the Print Check button at the bottom of the Desktop. If the check has already been refunded of voided, then the Select button at the bottom right will be grayed out. To perform either operation, touch Select to present the Sales Desktop defined in POS Terminal Options Desktop Options. The POS Operator will only be allowed to perform the operation(s) for which access is allowed. If the POS Operator has gained access to the Closed Check screen because printing is allowed for non-managers, then when the Operator attempts to Void or Refund a transaction, an additional prompt will appear for the Manager to authorize the action. Odyssey/BackOffice Suite Programming POS/2100 Application Programming 217

218 When the Select Button is touched on the Closed Check Desktop, the software will provide the following warning Popup, in an attempt to prevent authorized Managers from incorrectly using the wrong button when the only desired function is to Print a closed check. If the POS Operator incorrectly selects Yes, and then accesses the check, a Button Type Media, which is an Error Correct (Media 13 is fixed for this function) will exit back to the Log In Desktop. Button Type Driver Speed Pay Used to provide a list of all orders which are currently assigned to POS Operators of Operator Type 3 (driver s) and which are Sales Type 3 (delivery orders). The button provides an extremely quick method of closing out all orders of a driver, or a group of selected drivers, to an exact payment in cash. If any orders belonging to a driver have had a coupon presented, or if any ordered items were refused or could not be delivered, these orders should be selected prior to using this button and the appropriate entries made using the standard point-of-sale functionality. The Driver Speed Pay button presents the following screen. To close out all orders of a particular driver, to an exact payment in cash, touch the driver's name on the right. This will highlight all orders of the driver. Then touch Cash. The screen will prompt with the amount owed as shown below. Touch the Ok button to complete the operation. A chit will print on the receipt printer listing each order number, the total of that order and the total amount of cash. If a Tip/Gratuity is included on any order, then the confirmation screen presented after the Ok button will include a line with the descriptor "To Driver" indicating how much of the amount entered is due the driver. This line will also print on the chit. The chit is designed to serve as a "receipt" for the driver. 218 POS/2100 Application Programming Odyssey/BackOffice Suite Programming

219 Button Type Enter Do not use this Button Type. Use Button Type ASCII with the character "?". Used to manually enter the POS Operator s Secret Number. When the button is depressed, and a valid Secret Number has been entered, the point-of-sale terminal will present the Desktop defined as the End Of Sale Desktop in POS Terminal Options Desktop Options. This Desktop can either be defined on a by-terminal basis or a by- presented is also a function of programming under POS Terminal Operator basis. In addition, the Desktop Options Auto Shifts if the Desktop to be presented is the Sales Desktop rather than the Table List Desktop. Button Type Execute Program Used to launch a Windows program from the Log In Desktop. Great care should be taken that the program be a well-behaved application and terminate both promptly and properly, so as to not disrupt the point-of-sale application. This Button Type may also be placed on a Sales Desktop. Button Type Execute Program - MGR Same as Button Type Execute Program but a Manager is required. Button Type Exit On the Log In Desktop, used to terminate the point-of-sale application. The POS Operator must have check in Manager Mode Allowed under the POS Operator Programming Manager Access Tab. Either manually enter the POS Operator s Secret Number, then touch the button, or first touch the button and then swipe a magnetic card when the Manager ID entry Popup appears. Button Type Future Orders Used to access the Future Orders Desktop. This Button Type may be placed on either the Log In Desktop or the Sales Desktop. When placed on a Sales Desktop, it will no longer function once a transaction has begun. When placed on the Log In Desktop, it will require the entry of a valid POS Operator before functioning. While there is only one button type, there are two modes of operation for the button. The mode of operation is defined by the entry in the field Auxiliary Text. If the entry in Auxiliary Text is not a number between 1 and 99, then depressing the button will display all future orders, regardless of the Trigger Date/Time. If the entry in Auxiliary Text is a number between 1 and 99, then the button becomes a combination notification and access button. Depressing the button will show all future orders with a Trigger Date/Time within the next 1 to 99 minutes, depending on the entry in Auxiliary Text. The number of orders which will be displ ayed will show in place of Line 3 of the button text. Therefore, always program the text on line 1 and program no text on line 2. Button Type Limited Quantity Used to access the Limited Quantity items functionality of the POS/2100. This Button Type may only be placed on the Log In Desktop. The POS Operator must have check in Manager Mode Allowed under the POS Operator Programming Manager Access Tab. Either manually enter the POS Operator s Secret Number, then touch the button, or first touch the button and then swipe a magnetic card when the Manager ID entry Popup appears. The Limited Quantity functionality provides three functions: Flag a particular menu item as being out of stock immediately. Enter a quantity available number for a particular menu item. Unset the flag for a particular menu item as being out of stock. Odyssey/BackOffice Suite Programming POS/2100 Application Programming 219

220 When an item is out of stock, either by setting the quantity available to zero or when the count down has reached zero, an automatic message will be generated on the Message Board. This message is also automatically removed when the menu item is either deleted from the limited quantity screen or if a new quantity is entered. When a POS Item which is associated with the limited quantity menu item appears in a Popup window, the remaining quantity will display on the button of the Popup. When the quantity remaining is zero, a large red X will appear on the button of a Popup window for a POS Item associated with the menu item. There is no graphical designation relating to limited quantity items for a Preset button on a Sales Desktop. The menu items which are listed in the Limited Quantity screen can either be automatically reset during the End Of Day process of Odyssey MWS or they may remain from one Sales Day to the next. This automatic resetting, or clearing, is established under POS System Options Back Office Software through the flag Retain Limited Quantity Items. Limited Quantity Functionality When the Limited Quantity functionality is accessed, a Popup window will appear listing all current menu items which have been assigned a limited quantity. A view of the screen is shown in the following screenshot with two menu items having been assigned a limited quantity. Note that the second line is highlighted. It has been touched in this view. Note also that the two middle buttons at the bottom, Delete and Quantity are available. With no item touched, these two buttons will be grayed out. To change the available quantity on an existing item: Touch the line containing the menu item descriptor. If the menu item is now available in essentially unlimited quantity, touch Delete. This will remove the item from the Limited Quantity list. If the available quantity has changed, touch Quantity. A Popup screen will be presented which will allow the POS Operator to enter a new quantity available. To add a new menu item to the Limited Quantity List: Touch the Add button on the bottom right of the popup. When the Add button is touched, a popup window will appear showing two columns of names. On the left will be a listing of all Categories. These will be listed alphabetically and the first will be highlighted. On the right will be a listing of all menu items belonging to the selected Category. First touch the Category, then touch the menu item you wish to add to the Limited Quantity List. Once you have touched a menu item, the Add button at the bottom of this popup will become available. Touch the Add button and a popup screen will be presented which will allow the POS Operator to enter a quantity available. Obviously for items which are now Out Of Stock, the quantity entered will be zero. 220 POS/2100 Application Programming Odyssey/BackOffice Suite Programming

221 Button Type List Checks Used to access the Table List Desktop when a POS Operator s Secret Number is manually entered. This Button Type may also be placed on a Sales Desktop. When placed on a Sales Desktop, the button will not be accessible once a transaction has begun. Either manually enter the POS Operator s Secret Number, then touch the button, or first touch the button and then swipe a magnetic card when the Manager ID entry Popup appears. The Desktop which is presented, either when a magnet card is swiped or the Enter button is depressed, is defined through programming. This button allows for an override if the normal Desktop is a Sales Desktop. It is generally a good idea to place a List Checks button on all Log In Desktops. Button Type Manager Used to access the Manager_View Desktop. The POS Operator must have a check in Manager Mode Allowed under the POS Operator Programming Manager Access Tab. This button can be used to reduce the buttons on the Log In Desktop. Button Type Message Board This button will cause the Message Board to popup and display. This Button Type may also be placed on a Sales Desktop. Messages are placed on the Message Board through Odyssey MWS and can be either visible to all POS Operators or they may be private. In addition, an automatic message is placed on the Message Board when a limited quantity item has reached a count of zero. No POS Operator Secret Number entry is required to display the Message Board. The entire Message Board may be printed to a forty column printer as a convenient method of carrying a list of daily specials. Once a private message has been selected by the POS Operator to whom it is addressed, the private message may also be printed. Button Type New Check Used to access the default Sales Desktop when a POS Operator s Secret Number is manually entered. This is a required button on a Log In Desktop if any programming will be performed on Sales Desktops if the default Desktop presented when a mag card is swiped is the Table List Desktop. When the Table List Desktop is presented, and the point-of-sale terminal is in programming mode, you may not proceed to a Sales Desktop from the Table List Desktop. Either manually enter the POS Operator s Secret Number, then touch the button, or first touch the button and then swipe a magnetic card when the Manager ID entry Popup appears. Button Type No Sale Used to merely open the cash drawer. Entry of an authorized POS Operator is required. Button Type Recipe This button may also be placed on a Sales Desktop. The button is used to display a list of menu items for which a recipe has been entered for the menu item under Recipe Programming POS Recipe Tab. On the Log In Desktop, the Operator selects from a list of menu items and the recipe for that item will be displayed. Button Type Register Account Fingerprint This button is identical in operation to Button Type Register Employee Fingerprint except that the list from which the POS Operator chooses are all AccountCharge customers rather than Employees. See the following discussion. Odyssey/BackOffice Suite Programming POS/2100 Application Programming 221

222 Button Type Register Employee Fingerprint Used to associate a fingerprint, or multiple fingerprints, with an Employee or to verify a fingerprint association at the point of sale terminal. This Button Type may only be placed on the Log In Desktop. The POS Operator must have check in Manager Mode Allowed under the POS Operator Programming Manager Access Tab. Once the button has been touched, there are two modes of operation, fingerprint registration and fingerprint verification. The default is the verification mode. To merely verify a fingerprint, merely touch Digital Persona sensor. A verified fingerprint is shown below. To register a fingerprint to an Employee: Touch the description "Registration" under the text Select Mode. When you do so, the text in the bottom portion of the screen will illuminate and the Prompt will indicate "Please select employee and finger". Touch the button "Employee" A list box will appear displaying all Employees for the store. Touch the Employee Name and then touch the OK button. Touch the black down arrow to the right of the window "Finger" and select which finger is being registered. Touch the button "Register" and wait until the screen appears as shown below: Have the Employee place his right index finger on the Digital Persona sensor. The process requires four consecutive images. NOTE: Associating fingerprints with an Employee is only done once. It is recommended that this procedure be performed on the BackOffice PC. 222 POS/2100 Application Programming Odyssey/BackOffice Suite Programming

223 Button Type Reports Used to provide access to the point-of-sale reports selection menu. This Button Type may only be placed on the Log In Desktop. The POS Operator must have check in Allow X Report under the POS Operator Programming Manager Access Tab. Manually enter the POS Operator s Secret Number, then touch the button, or first touch the button and then swipe a magnetic card when the Manager ID entry Popup appears. This button also provides access to the same Flash View display which may be displayed from Odyssey MWS, as the first choice on the reports selection menu. The available reports are illustrated in the screenshot which follows. Once the report selection display presentation is presented, a sixty second timeout is initiated. If no report is selected within sixty seconds, the software performs an automatic Exit. With the exception of the Flash View, touching any button will present another window of choices, either to select a particular employee or type of report and also to either View or Print the report. If View is selected, there is always another chance to actually print the report. Printing reports at the point-of-sale requires that a printer with a Windows driver be attached to the point-ofsale terminal from which the report is being taken. This CAN NOT be a printer with the Generic Text driver. The point-of-sale reports use various fonts and are all written using the Crystal Reports engine. The name of the Windows printer whose driver will be used in generating the reports is programmed under Printer Configuration Terminal Print Options on the Output Tab under POS Reports Printer. This printer DOES NOT have to be the default Windows printer on the computer from which the reports are being generated, although for client point-of-sale terminals, this generally will be the default Windows printer. If you are running the point-of-sale application on the Back Office Server, then the default Windows printer will definitely NOT be this printer, since all of the reports generated by Odyssey Reports require a full screen presentation. All of the View presentations have a sixty second timeout as well. If a report or selection screen is left on the display for a period longer than sixty seconds, the software will automatically exit back to the Log In Desktop. Odyssey/BackOffice Suite Programming POS/2100 Application Programming 223

224 Button Type Settlement Operator Used to assign a single POS Operator, aside from Managers, as being able to use any Finalize Media or other button which might open one of the possible two cash drawers. In order to use the button, the POS Operator must have a check in Manager Mode Allowed under the POS Operator Programming Manager Access Tab. A Settlement Operator may be required under POS Terminal Options I/O Devices on the Cash Drawer tab. When the button is touched, a list of all POS Operators currently able to operate the terminal will appear. To assign a Settlement Operator to a drawer, Use the <> button to select which drawer then touch the name and touch Assign. To Unassign the current Settlement Operator, touch Unassign. Button Type Shift Select Used only on point-of-sale terminals with the option Shift Log On Required checked under POS Terminal Options Transaction Options on the Start of Transaction Tab. This button may only be placed on the Log In Desktop. A discussion on the use of shifts is included in the section POS System Options Shift Definitions. At the End Of Sales Day process through Odyssey MWS, the active shift on any point-of-sale terminal with Shift Log On Required set as true will automatically be set to No Active Shift. The software will prompt the selection of a shift prior to accessing either the Table List Desktop or any Sales Desktop. NOTE: This button should NOT be placed on a pre-check terminal where a shift log on is not required. The default shift will be used on these terminals. Therefore, this functionality is the primary reason for establishing two separate Log In Desktop with appropriate defaults on a by-terminal basis. To change shifts, either manually enter the POS Operator s Secret Number, then touch the button, or first touch the button and then swipe a magnetic card when the Manager ID entry Popup appears. The POS Operator must have a check in Allow Shift Select under POS Operator Programming Manager Settings Tab to access the shift select display. An illustration of the shift selection window is shown in the following screenshot. 224 POS/2100 Application Programming Odyssey/BackOffice Suite Programming

225 Note that the shift Default Shift does not display, since it will be used exclusively at those terminals where a shift selection is NOT required. Note also that the No Active Shift selection is available. Selecting No Active Shift will effectively disable the terminal for any operation until a POS Operator with the authority set to Allow Shift Select presents this window again and selects a new shift. Button Type Table Ready Used only in conjunction with an interface to Open Table. The POS Operator enters a Table Number and touches this button. If there are checks open at the table, the POS Operator is informed that the operation is not allowed. If there are not tables open, the POS Operator is prompted to confirm that the table is ready for seating. If the POS Operator confirms, a message is sent to Open Table so indicating. Button Type Time Clock Used by employees to clock-in, clock-out, go onto break and come off of break. This Button Type may also be placed on a Sales Desktop. No POS Operator Secret Number entry is required to display the Time Clock window. The number entered to identify the employee is the POS Clock Number entered in Employees under the Employee Configuration Tab. If an employee is qualified at more than one job code, a Manager may be required at clock-in in order for an individual employee to select a job code other than the default job code. An employee may only take a single break between clocking-in and clocking-out. Employees who have an assigned POS Operator Number, and who are clocking out from a job code which is tippable, will be prompted with a tip declaration screen when clocking out. NOTE: A POS Operator whose POS Operator Number has been assigned to an Employee may not operate the point-of-sale software until the POS Operator has clocked-in as an Employee, UNLESS THE EMPLOYEE IS CHECKED AS A SALARIED EMPLOYEE. Button Type Transfer Checks Used to transfer a group of guest checks to a selected POS Operator. This Button Type may also be placed on the Table Desktop through POS Terminal Desktop programming. The POS Operator must have check in Allow Check Transfers under the POS Operator Programming Manager Access Tab. The screen provides a three column display. The first column displays all POS Operators who are currently "signed on" and able to utilize the terminal. The Operator/Manager touches the POS Operator to whom the checks will be transferred. The second column then lists all open guest checks and the currently assigned POS Operator. Excluded are guest checks which currently belong to the selected "Transfer To" operator. The third column displays all POS Operators who currently have open checks. Excluded is the "Transfer To" operator. Touching a check in the middle column selects/deselects a single check. Touching a POS Operator in the third column selects/deselects all checks displaying in the middle column which belong to that POS Operator. Odyssey/BackOffice Suite Programming POS/2100 Application Programming 225

226 The screen above shows that Robert B. will be receiving all currently open checks from Clifford C., as soon as the Operator/Manager touches the "Transfer" button at the bottom right of the screen. The screen is designed to allow multiple POS Operators to "receive" multiple checks from various other Operators, such as at a shift change. Once all transfers have been accomplished, touching the "Exit" button will cause the screen to revert to the Log In Desktop. Button Type Transfer Delivery Checks Used to transfer a group of guest checks to a selected POS Operator. The POS Operators displayed on the far left of this screen must be POS Operator Type 3, which is reserved for Delivery Drivers. In addition, only open orders of Sales Type 3 are displayed. This Button Type may also be placed on the Table Desktop through POS Terminal Desktop programming. The POS Operator must have check in Allow Check Transfers under the POS Operator Programming Manager Access Tab. Only POS Operators of Type 3 (drivers) will display in the left column. Only orders of Sales Type 3 will display in the right column. The currently open orders can be sorted by the "length of time since check was initially opened" or by the Delivery Zone. Also displayed for reference are the street address and the Customer Name, to assist in transferring the correct order. The POS Operators listed on the left are the only two currently active POS Operators of Operator Type 3, the drivers. The second column defaults to a sort criteria which lists the orders which have been "in-house" the longest first. As shown above, the first orders was initiated over one hour and forty nine minutes ago, and the most recent order at the bottom was initiated eight minutes ago. If the Transfer button were depressed with the three orders highlighted as shown, all three orders would be transferred to Driver "Tommy T". A chit will print on the receipt printer listing each order number, the total of that order and the total amount of all transferred orders. The chit is designed to be used at driver settlement time, at the end of each delivery or a series of deliveries. NOTE: Also listed in the right column will be Delivery Checks which HAVE already been assigned to drivers. This is to allow for re-assignment in the event a driver's delivery route has changed. Delivery checks ALREADY assigned to drivers will list at the bottom. Instead of the Delivery Zone, three * symbols will display. Instead of the time "in-house", three * symbols will display. Instead of the Customer Name, the currently assigned driver's name will display. Delivery checks already assigned to t he driver selected in the left column WILL NOT display in the right column. 226 POS/2100 Application Programming Odyssey/BackOffice Suite Programming

227 MapPoint Interface On the Transfer Delivery Check screen, there is a new button with the October 2008 release, Print Map. This button uses MapPoint to print either a map, directions or both. You can highlight multiple checks and then tou ch Print Map. When the button is touched, you are provided a choice as shown below. The interface supports the latest version of MapPoint, as of October of Button Type Undefined This is the default Button Type for all newly added buttons on a button window. You can also use this Button Type for a button window which is only being used to display graphics images. Button Type Windows Used to minimize the point-of-sale application program and present the Windows desktop. This Button Type may only be placed on a Log In Desktop. The POS Operator must have check in Manager Mode Allowed under the POS Operator Programming Manager Access Tab. Either manually enter the POS Operator s Secret Number, then touch the button, or first touch the button and then swipe a magnetic card when the Manager ID entry Popup appears. Aside from the Back Office Server, it is generally not a good idea to place this button on a Log In Desktop. Manager View Desktop The Manager View Desktop can only be accessed from the Log In Desktop, using Button Type Manager. There must be a Button Type Exit on the Manager View Desktop. You can not access either the Table List Desktop or any Sales Desktop from the Manager View Desktop. Any button which can be placed on the Manager View Desktop can also be placed on the Log In Desktop. The Manager View Desktop allows for less "clutter" on the Log In Desktop. Once the Manager View Desktop has been accessed, the software "remembers" the POS Operator who accessed the Desktop, so performing multiple Manager operations is somewhat easier if this Desktop is implemented. Table List Desktop The Table List Desktop provides both a convenient graphical method and a list selection method for handling guest checks. The operations available from the Table Desktop are: Open a new guest checks at an empty table. Open a second guest check at a table. Combine two guest checks, whether they are associated with the same table or not. Open a guest check that is NOT associated with a table. Move a guest check from one table to another. View all entries on any guest check belonging to the current POS Operator. Odyssey/BackOffice Suite Programming POS/2100 Application Programming 227

228 Transfer a guest check from a Tabs mode (no table assigned) to a table. Provide a visual image of tables which are empty, have a guest check which has been selected with the last twenty minutes (this is a programmable time), have a guest check which has not been selected within the last twenty minutes and finally, have a guest check which has been printed within the last twenty minutes. The only programming, from within the point-of-sale application program, associated with the Table List Desktop is the creation of Table Sections. The buttons which appear on the Desktop are fixed functions, however the operation is controlled through programming within Odyssey Programming. Tabl e List Desktop Screen View The following screenshot illustrates the functionality of the Table List Desktop. The screen is divided into five primary areas; a banner of POS Operator Name, Refresh and Table Section Nam e, the guest check display, the table/check list, the Table Section itself and five buttons. (If the logged on POS Op erator has Manager Mode Allowed, a sixth button Unlock Check will also be visible.) The colors of the table images in the above screenshot give a quick visual image of the situation with Robert B., the current POS Op erator. All tables in green have no guest check associated with them. The three tables in gray have gue st checks, but do not belong to Robert B. Robert B. has five tables with guest checks. These are listed in the middle of the screen and have three colors associated with the tables in the Table Section view on the right of the display. The three yellow tables have guest checks which have been selected within the last twenty minutes. The red table has a guest check which has not been selected within the last twenty minutes. The white table has a guest check which has been printed, and presumably presented to the customer for payment. The selected check, outlined in blue in the middle, is check number 6 at table 104 and the items entered on the guest check are shown on the far left of the screen. 228 POS/2100 Application Programming Odyssey/BackOffice Suite Programming

229 Table List Desktop Informational View An alternative view of the Table List Desktop does not show the table layout, but instead displays information on the open checks themselves. This mode of presentation is enabled under POS Terminal Options Desktop Options when you set the flag Two Screen Table Desktop. You can switch back and forth between views by touching the POS Operator Name displayed in the upper left portion of the screen. Note the fourth column, Total listed above. This column is controlled by a flag in POS System Options Miscellaneous Options, as Display Total Column Check Lists. This flag pertains to both the above screen and the Closed Check Desktop. Prior to the October of 2008 release, it was recommended that this flag NOT be set when a large (greater than ten or so) checks would be displayed at any time. This was because it was necessary to add the detail information for each check in order to display this total and it took greater than ten seconds to actually present the desktop. With the October of 2008 release, this total information is included in the header record and there is no speed degradation associated with displaying the total. The total column simply provides an additional method for the POS Operator to quickly identify the correct guest check for retrieval. Table List Desktop Programming Access There is only one Table List Desktop. However, there can be as many Table Sections as are required. A Table Section is a graphical presentation of a particular area of the restaurant. Referring to the screenshot in the previous section, the selected Table Section has been named Main Dining by the programmer. To create or modify Table Sections: Access POS/2100 programming as described in the previous section. Odyssey/BackOffice Suite Programming POS/2100 Application Programming 229

230 With the POS Operator s Secret Number still in the Entry Window (displayed as * characters) touch a Button Type List Checks if one is on the Log In Desktop, or touch the Enter button if the terminal is programmed to display the Table List Desktop at the End Of Sale. Right click on the Background Color of the Table Section on the right. Use the Load Template selection to select an existing Table Section to modify. As an alternative to right clicking in the Background Color area, you can also touch the displayed name of the Table Section at the top of the Table Section area. A Popup will appear showing all existing Table Sections. Touch the Table Section you wish to modify. Table Section Selection Options When you right click on the Background Color of a Table Section, you will be presented with the Popup selection window shown in the following screenshot. Paste. This selection is active whenever all of the properties of a table object have either been Cut or Copied onto the clipboard. It is the most convenient method for adding multiple table objects to the Table Section. Window Color. This selection defines the background color within the selected Table Section. Of course, you will want a contrast between the colors selected to display the status of guest checks at any table objects you will place on this Table Section. A left click on Window Color presents the identical selection to the one provided for all buttons on a button window. If you are going to place a graphic image on the Table Section, use black for the Window Color. Window Pattern. This selection allows you to place a graphics BMP image on the entire Table Section. The BMP image will be enlarged to fill the entire Table Section. You can still place table objects onto the Table Section if you place a graphics image, however, the display becomes quite cluttered. The most common use of a graphics image would be a Table Section used at a bar, where there were no tables, and all guest checks will be opened without a table assignment. As an option, you can require that a name be assigned such a guest check. This is the Tabs mode of the POS/2100. In POS Terminal Options Transaction Options, under the Start of Transaction Tab, you would check Compulsory Account # Entry and NOT check Validate Account. When the New Check button on the Table List Desktop is touched, a Popup will display allowing the entry of up to sixteen characters of Reference Text. Add Object. There are essentially five objects to add, a small, medium or large table and a round ended or flat ended line. Adding objects is covered in the next section. Delete Object. This selection is not functional. Deleting table objects is covered in the next section. Save Table Section. Once you have finished with a Table Section, use this selection to save the Table Section. The process is identical to the Save Template process, covered in the Log In Desktop section. Note that the name assigned to the Table Section will appear in the banner area of the Table List Desktop when it is selected, and will also appear in a Popup window when the name of the current Table Section is touched. It is a good idea to limit the names of Table Sections to sixteen characters. Always choose Save Table Section immediately after making your changes to avoid the possibility of losing all of your work. 230 POS/2100 Application Programming Odyssey/BackOffice Suite Programming

231 Load Table Section. Once you have saved a Table Section, you can load another Table Section using this selection. NOTE: If you do NOT save your Table Section, but instead choose Load Table Section, you will LOSE ALL OF YOUR WORK in creating the Table Section. If you exit the Table List Desktop without choosing the Save Table Section option, you will LOSE ALL OF YOUR WORK. Deleting a Table Section is identical to the process explained in the previous section covering Deleting Desktops. Like a Desktop, a deleted Table Section can not be recovered. There is no Un-delete and there is no Recycle Bin from which to retrieve a deleted Table Section. Table Section Table Objects When you choose Add Object, there are only three choices; a small, medium or large table. These will default to a red color, with no text. The following screenshot illustrates three new objects added to a Table Section named test as small, medium and large. You can position any table object by left clicking on the object and simply dragging it to the desired location. When you right click on a Table Object, you are presented with the following selection dropdown. Cut. This selection will delete the table object and copy all properties to the clipboard. This is seldom used. Copy is much more valuable when placing table objects on a Table Section. Copy. This selection will copy all properties of the table object to the clipboard. Once a table object has been copied to the clipboard, a subsequent right click in the Background area of the Table Section will show the Paste selection. For table objects with the same graphics, the only edit after a Paste operation will be the Text and Table #. Delete Object. This selection deletes the table object from the Table Section. Properties. This is the configuration selection for the table object and is covered in the following section. NOTE: If the Table Section is not saved, none of the changes made to the Table Section are stored. While this is bad news if you have done work and forgotten to save the Table Section, it is good news if you have inadvertently deleted too many table objects or simply moved them incorrectly. Table Section Table Object Properties Wh en y ou right click on a table object you are presented with a Properties programming window as shown in the following screenshot. Odyssey/BackOffice Suite Programming POS/2100 Application Programming 231

232 Button Type. This is a reference only window. All objects on the Table Section are table objects. Style. Under Style you can click on either Square or Round. Typically, you will be placing a graphics BMP image on top of the table object and you will want a contrast between the table object itself and the graphics. Text. This is the text that will display on the table object. While you can enter alphanumeric characters, the table number itself is a number in the point-of-sale database, and the table number must be unique. Table #. This is the numeric reference to the table number. It is the same number that a POS Operator would enter upon depressing the Table button at the bottom of the Table List Desktop, as shown in a previous section. Font. This is to format the presentation of the Text on the table object. It presents the same screen as is presented when you left click on Text Font under the selection provided for all buttons on a button window. A typical font size is 12 and typically the font color is black, with bold characters. Transparent. This pertains to any selected graphics, BMP, file you will place on the table object. You will generally want to make any graphics transparent, so the color of the table object to designate its status will show through the graphic. Image Only. This also pertains to any selected graphics, BMP file you place on the table object. If the graphics includes a table number designation, you can check Image Only. This presumes, of course, that the image is small enough to allow at least a portion of the table object to show through in order to take advantage of the status. Path. Use the Find button to select a graphics image. The standard table images are located in the folder c:\icom\pos2100\graphics\tables & chairs\ in the standard installation. Table List Desktop Button Types There are no programmable buttons on the Table List Desktop. The only objects which may be added are Table Objects, which are added to Table Sections. There are six fixed function buttons which may be displayed on the bottom of the Table Desktop. The function of these buttons is documented herein purely for operational reference. Button Type Cancel Use this button to return to the Log In Desktop. Depending on the settings under Transaction Options Start Of Transaction Tab, for both Server Stay Down and # Seconds To Stay Down, the software may perform an automatic return to the Log In Desktop after a pre-determined number of seconds, or stay at the Table Desktop until the Cancel button is touched or a transaction is begun. Button Type New Check Use this button to begin a new transaction without a table assignment. This button will be grayed out if there is a check next to Compulsory Table Entry under Transaction Options Start Of Transaction Tab for the particular terminal. 232 POS/2100 Application Programming Odyssey/BackOffice Suite Programming

233 A touch on this button may also prompt the POS Operator to either enter a reference name or enter/select a valid AccountCharge Customer, depending on the settings under Compulsory Account # Entry and Validate Account on the same programming tab. Button Type Table Use this button to open a new check at a table, either because the table number itself does not have a Table Object on any Table Section, or to open a second guest check at a table which does have a Table Object. When the button is touched, the POS Operator will be shown an entry window prompting Enter Table Number. Table numbers can range from 1 to 999. NOTE: In order to prevent erroneous entry, the POS/2100 limits the table number to three digits. In order to prevent accidentally opening a second guest check at a particular table, the software will prompt the POS Operator to confirm the entered table number if a guest check ALREADY exists at the entered table number. To open a second (or third or fourth) guest check at the entered table, the POS Operator should touch Yes. If the table number has accidentally been entered incorrectly, the POS Operator should touch No. Button Type Transfer Checks This button will only be visible on the Table Desktop if the flag "Delivery Transfer Button" is checked in BackOffice programming under POS Terminal Options Desktop Options. This button may also be placed on the Log In Desktop. For information on its operation, see the section under Log In Desktop. Button Type Transfer Delivery Checks This button will only be visible on the Table Desktop if the flag "Server Transfer Button" is checked in BackOffice programming under POS Terminal Options Desktop Options. This button may also be placed on the Log In Desktop. For information on its operation, see the section under Log In Desktop. Button Type Unlock Check This sixth button on the Table List Desktop is only visible if the logged on POS Operator has Manager Mode Allowed checked under POS Operators Manager Settings Tab. In general, the button will be grayed out. The middle area of the Table List Desktop shows either a check number and table number or an entered name, if the check has an assigned name and IS NOT assigned a table number. A check which is open on the system will appear with a * character at the far right on this list. A check which is open on the system can not be retrieved by a POS Operator, since presumably it is already in the middle of a transaction. In the extremely rare instance that the point-of-sale software has been abnormally terminated in the middle of entering items, the check will REMAIN flagged as open on the system. This button allows a POS Operator, with the Manager Mode authority, to unset the open on the system flag and allow normal access. This process should only be implemented when the point-of-sale software has been abnormally terminated in the middle of entering items. A POS Operator with Manager Mode Allowed should touch the guest check with the * character in the middle of the Table List Desktop. Odyssey/BackOffice Suite Programming POS/2100 Application Programming 233

234 When the check is touched, the Unlock button will no longer be grayed out, and should be touched. The point-of-sale software will provide a prompting window indicating the name of the POS Operator currently responsible for the open guest check and the name of the terminal on which it is flagged as being open, as shown in the following screenshot. The only choice is to touch the Ok button. When the button is touched, an additional prompting window will display, warning the POS Operator of the danger in unlocking a guest check which is, in fact, actually open on this terminal and being used by the described POS Operator, as shown in the following screenshot. If the POS Operator with Manager Allowed access is uncertain of the actual status of the guest check, touch the Cancel button. If the Manager has confirmed that the check is incorrectly flagged as open on the system, touch the Ok button. When the Ok button is touched, an additional entry window will appear prompting the Manager to actually enter the guest check number to be unlocked. This second pass at identifying the guest check is to prevent any possibility of accidentally unflagging an open check as being open on the system. The Manager should enter the Check number to be unlocked then touch the Enter button on the entry window. When the Enter button is touched, the point-of-sale software will confirm the unlock operation. 234 POS/2100 Application Programming Odyssey/BackOffice Suite Programming

235 Button Type Enable Combine This button is used to begin the operation of combining two different guest checks to a single guest check, either at a particular table or retain the unassigned to table status of the guest check. The middle area of the Table List Desktop shows either a check number and table number or an entered name, if the check has an assigned name and IS NOT assigned a table number. Normally, when a check number/table number is touched, the point-of-sale terminal merely displays the selected transaction in the guest check image on the left of the Table List Desktop. When a second check number/table number is touched, the first is dismissed and only items from the newly selected check number/table number are displayed. When the Enable Combine button is touched, the middle area of the Table List Desktop acts differently. In add ition, the text on the button changes from Enable Combine to Disable Combine, indicating that another touch on the button will return the operation to the normal Table List Desktop operation. When in the Combine mode, the POS Operator should FIRST touch the check which will REMAIN. Next, the POS Operator should touch any other check(s) listed in the middle whose items will be added to the check touched FIRST. Lastly, the POS Operator should either touch the Select button on the far right at the bottom of the screen, or touch the Table Object in the Table Section corresponding to the table with which the combined checks will be associated. The point-of-sale software provides various prompting windows to prevent erroneous entries. Button Type Select Used to bring forward a Sales Desktop, along with the items already purchased, for a check number/table number which has been touched in the middle area of the Table List Desktop. POS Operators who have the authority Master Server under POS Operators Operation Settings Tab have the ability to enter items on guest checks belonging to other POS Operators. Depending on the setting Auto Transfer, after being opened by the Master Server the check can either remain the responsibility of the original POS Operator or be automatically transferred to the Master Server. The touch check number/table number then touch Select process is used to open these guest checks. In addition, if a check belongs to a POS Operator who has the setting Checks Available For All, under the same programming tab, any POS Operator may open the check. The transfer of responsibility is automatic for such operations. Such checks do not normally appear in the middle area of the screen when a POS Operator is presented the Table List Desktop. These checks are listed in the middle, in order to be opened using the Select button, when the POS Operator touches the Refresh text in the middle of the top of the screen. Table List Desktop Refresh The area of the Table List Desktop immediately above the middle of the screen where check numbers/table numbers are listed appears with a heading Refresh. Touching the displayed text causes two separate functions to occur. The colors of the Table Objects displayed in the Table Section are refreshed to reflect their current status as relates to the selection Over Due Minutes programmed in POS System Options Desktop Options on the General Tab. Any guest checks belonging to POS Operators with a check under Checks Available For All under POS Operators Operation Settings Tab are displayed in the middle area of the Table List Desktop, in order that they may be opened using the Select button. Future Orders Desktop The Future Orders Desktop provides several views and information pertaining to future orders. Future orders are ones for which the sales and possible payments have not yet been processed. These orders will be activated at a time established by the Trigger Date/Time. When the Trigger Date/Time is reached (or when Odyssey/BackOffice Suite Programming POS/2100 Application Programming 235

236 the future order is selected and activated by a POS Operator), the items will be requisitioned, a receipt/guest check may be printed and the order will either be moved to the Open Orders list (and accessible on the Table Desktop) or the Closed Orders list (and accessible on the Closed Orders Desktop). If the Button Type Future Orders which cause the display had an entry between 1 and 99 in Auxiliary Text, then only future orders in that time frame of minutes will display. With any other entry in Auxiliary Text, all ord ers will display, even orders days in the future. The operations available from the Table Desktop are: Immediately activate a future order, regardless of the Trigger Date/Time. Change the Trigger Date/Time. Change the Name associated with the future order. Change/define the date range of displayed orders. Display a summary of all items ordered on all displayed checks. The only programming, from within the point-of-sale application program, associated with the Table List Desktop is the creation of Table Sections. The buttons which appear on the Desktop are fixed functions, however the operation is controlled through programming within Odyssey Programming. Future Orders Desktop Screen View The following screenshot illustrates the functionality of the Future Orders Desktop. Future Orders Desktop Displayed Information Guest Check Screen Area The time will be the time the order was received as an incoming order. The POS Operator identification will be the default POS Operator as programmed under POS System Options Ordering System. The guest check number will be a sequential number for all future orders. When the order is activated, it will be assigned a sequential guest check number for the Sales Day in which it is activated. As on all check display desktops, the entered name is shown at the bottom 236 POS/2100 Application Programming Odyssey/BackOffice Suite Programming

237 Future Orders List Area Touching the header row for any column will sort the displayed list by that column. The Trigger column shows the Date/Time when the order will be activated. The Name column shows the entered name. If an order number was provided by the third party ordering system, it will be shown at the end of the name as an additional reference when the customer arrives to collect the order. The Paid column will have a check mark if the order was paid online. No check mark indicates the order will be paid upon pickup or delivery. The Total column shows the total amount of the order, including tax as calculated by the POS terminal. The Delivery columns will have a check mark if the order is to be delivered. The order will be processed as Sales Type 3 once activated. An order with no check mark is most likely pickup but will be processed as the default Sales Type as programmed under POS System Options Ordering System. The Originated column shows the Date/Time when the order was placed. The time will be the same as the time displayed in the Guest Check Area of the screen. This is useful for orders whose Trigger Date/Time was received days in advance. Future Orders Desktop Button Types There are no programmable buttons on the Future Orders Desktop. The re are six fixed function buttons which are displayed on the bottom of the Future Orders Desktop. The function of these buttons is documented herein purely for operational reference. Butto n Type Exit Use this button to return to either the Log In Desktop or the Sales Desktop from which the Future Orders butt on was depressed. Button Type Range Use th is button to parse the displayed list of Future Orders by Trigger Date. The screen below shows the selection methodology. Touch a start date as From and an ending date as To and touch OK. The selected range is forgotten as soon as the Future Orders Button is depressed. This button type is very useful when using either the Summary or the Activate button when finding orders. Odyssey/BackOffice Suite Programming POS/2100 Application Programming 237

238 Butto n Type Summary This button is for use as a planning tool in ordering. The button will display a consolidation of all menu items yet to be requisitioned (contained in Future Orders) for the displayed range of dates. Management can quickly scan this list to see if additional inventory might need to be ordered, or batch preparations made, in order to fill the orders. A sample is shown below. Button Type Activate This button will be grayed out if there not an order selected. When there is an order selected, and highlighted, this button is used to override the customer s Trigger Date/Time and immediately bring the Future Order into the system, causing requisition print. In order to prevent the inadvertent activation of an order, this button has an Are You Sure? prompt which alerts the POS Operator that the order is about to be activated and therefore requisitioned. Button Type Trigger This button will be grayed out if there not an order selected. When there is an order selected, and highlighted, this button is used to override the customer s Trigger Date/Time and change it to a Date/Time selected by the POS Operator as shown below. The current Trigger Date/Time shown is May 14, 2011 at 11:28 AM. To change the date, merely click another date To change the time, click on the hour, minute or AM/PM and use the up and down arrows on the right. If you have made a mistake and want to start over, touch Cancel To confirm the entry and change the Trigger Date/Time, touch OK 238 POS/2100 Application Programming Odyssey/BackOffice Suite Programming

239 Button Type Name This button will be grayed out if there not an order selected. When there is an order selected, and highlighted, this button is used to change the Name associated with the highlighted Future Order. Enter a new name and touch Enter If you want to start over, regardless of what is displayed, touch Clear Twice Sales Desktops Sales Desktops are the most commonly programmed desktops in the point-of-sale database. You can utilize as ma ny Sales Desktops as are required in a point-of-sale application. Moving from one Sales Desktop to another is done by touching a Button Type of Desktop, covered in a later section. Every Sales Desktop will require a Guest Check object. If for some reason you need a Sales Desktop without a Gue st Check display, you can first size the Guest Check object smaller, then hide the Guest Check object behind a button window. Every Sales Desktop should also have a Status Window, an Entry Window and a numeric keypad, although none of these objects are required. Sales Desktops Programming Access To create or modify Sales Desktops: Access POS/2100 programming as described in the previous section. With the POS Operator s Secret Number still in the Entry Window (displayed as * characters) touch a Button Type New Check if one is on the Log In Desktop, or touch the Enter button if the terminal is programmed to display the default Sales Desktop at the End Of Sale. Right click on any area of Background Color of the Sales Desktop. Use the Load Template selection to select an existing Sales Desktop to modify. The other selections on this list are covered in a subsequent section. NOTE: As noted in a previous section, every time you attempt to load a new Sales Desktop while you are in programming mode, you are prompted to save the current desktop. Sales Desktops Restricted Access Access to Sales Desktops on the POS/2100 whose names begin with the three characters Mgr (this is NOT case sensitive) is restricted to POS Operators with the Manager Mode Allowed flag set to Yes under the POS Operators Manager Settings Tab. This restriction only applies when the Button Type Desktop is depressed. If you wish to restrict access to certain Sales Desktops, DO NOT enter these desktops as the End of Sale Desktop in POS Terminal Options Desktop Options or as the Default Sales Desktop under POS Operators General Tab. Odyssey/BackOffice Suite Programming POS/2100 Application Programming 239

240 Sale s Desktops Guest Check Object A Guest Check object is required on every Sales Desktop. The best way to create Sales Desktops is to start with a template Sales Desktop, then save it as a Template, then save it again with your first Desktop name. Size and position the Guest Check object. Create all the properties associated with the Guest Check object. Determine if you will have a numeric pad on your template Sales Desktop and size and place it. Size and place your Status Window and your Entry Window. Position you Popup Windows so they do not cover the guest check or numeric keypad. An optional object on the Sales Desktop is the Previous Order Window. This will occupy quite a bit of space on your Sales Desktops, so size and position this. The following screenshot illustrates the Guest Check object used in the default demonstration database. The guest check was first opened at 16:03, at table 100, it is guest check 0011, with 2 covers, it has been 10 minutes and 51 seconds since it was opened, the price level is 1 with a name of Regular, the Sales Type is Eat In, the amount due with tax is $ and 5 items have been entered on the check. Guest Check Object Item Display Area Selections When you right click on any of the line item display area of a Guest Check object (shown in blue on the previous screenshot), you are presented with the following selection window. Item Font. This is to format the presentation of the Text on the Guest Check object. It presents the same screen as is presented when you left click on Text Font under the selection provided for all buttons on a button window. Note that the text color selection is not made through this selection. Each type of entry line which appears on the Guest Check object may have its color set by the type of entry displayed. Depending on the width of the Guest Check object and the display resolution, good choices are either 12 or 14. The Item Font on the previous screenshot is Arial, bold. You will ALWAYS want to select bold. 240 POS/2100 Application Programming Odyssey/BackOffice Suite Programming

241 NOTE: The space (vertical separation) between displayed lines on the Guest Check object is determined by the Item Font selected. The larger the Item Font, the more space between lines. The more space between lines, the easier for the POS Operator to properly select a displayed line. The selection of Item Font should be a trade-off between the width of the Guest Check object and the number of characters of text information which will display on the Guest Check object. Vertical Lines. A left click on this selection will either set or unset the display of vertical lines on the Guest Check object. The displayed vertical lines will automatically move if the amount to be displayed on any single line does not fit in the spacing. The area where the item description is displayed will simple get smaller. Horizontal Lines. A left click on this selection will either set or unset the display of horizontal lines on the Guest Check object. Horizontal Line Fill. This only applies if Horizontal Lines is checked. A check here will fill horizontal lines on the entire Item Display Area. With no check, lines will only be under lines which contain information. Generally, if you want Horizontal Lines, you will want to fill the entire Item Display Area. Item Color. Before selecting any of the colors for the various types of lines on the Guest Check Object, you should determine the Background Color you are going to choose for your Guest Check. Obviously you will not want any item color to wash out against the selected Background Color. Use the displayed Windows color palette to select the color for menu item lines on the Guest Check object. The default demonstration database uses black. Condiment Color. Use the displayed Windows color palette to select the color for condiment (items entered from DCM type List Files) lines on the Guest Check object. The default demonstration database uses white. Payments Media Color. Use the displayed Windows color palette to select the color for finalizing media lines to display on the Guest Check object. The default demonstration database uses a shade of green. Charges Color. Use the displayed Windows color palette to select the color for service charge and tip media lines on the Guest Check object. The default demonstration database uses a shade of yellow. Other Media Color. Use the displayed Windows color palette to select the color for any media type lines other than a finalizing media or a service charge/tip on the Guest Check object. Generally this applies to discounts. The default demonstration database uses a shade of red. Other Line Color. Use the displayed Windows color palette to select the color for any line not covered above on the Guest Check object. Examples would include Fire Messages or an entered Customer Name. The default demonstration database uses black. Background Color. Use the displayed Windows color palette to select the Background Color for the Guest Check Object. Guest Check Object Header Area Selections There is only one additional parameter associated with the Guest Check object, the ability to tailor the header area at the top. When you right click on either the white area on top of the item display area or the white area at the bottom of the item display area you are presented with the following selection window. Odyssey/BackOffice Suite Programming POS/2100 Application Programming 241

242 Set Header Bitmap. A left click here will allow you to browse and select a BMP graphic image to show in the expanded height of the header area at the top of the Guest Check object. Remove Header Bitmap. A left click here will remove any BMP graphic image you have placed in the header area at the top of the Guest Check object. Delete Object. This selection is not valid and is grayed out. Every Sales Desktop must have a Guest Check object. Guest Check Object Individual On Each Sales Desktop This section is included as a reminder to follow the procedure to first create a template Sales Desktop, then begin to create your actual Sales Desktops. The Guest Check object is separate and distinct on each and every Sales Desktop. If you decide later to make the Guest Check object smaller or larger or change some of its properties, you will be required to program each and every Guest Check object on each and every Sales Desktop. Guest Check Object Sizing and Positioning The Guest Check object can be moved and sized in the identical fashion to a Button Window, as described in a previous section. As an example of the programmability of the Guest Check object, the same check as was shown in the previous screenshot is illustrated below with the width smaller, the font changed, both horizontal and vertical lines added, the Background Color changed and a Header Bitmap added. To illustrate the various colors on the Guest Check object, the line item Bay Scallops was wasted from the prior presentation, reducing the amount due to $ and the item count to 4. Note also that it has now been 1 hour, 18 minutes and 27 seconds since this guest check was first opened. 242 POS/2100 Application Programming Odyssey/BackOffice Suite Programming

243 Sales Desktops Selection Options Once you have accessed the programming mode for Sales Desktops, you are now able to configure them. To affect the desktop, right click again in a black area which is the Windows Background. From any Sales Desktop you will be presented with the following selection window. Screen Size. Do not click on this selection. Button Window Color (All). This selection is similar to the Button Color (All) selection under button windows. It allows you to change the color of all buttons on all button windows on the Sales Desktop. It is a seldom used selection. Button Window Border (All). This selection is similar to the Window Border selection under button windows. It allows you to add a Window Border to each and every object on the Sales Desktop or to remove any Window Borders on each and every object on the Sales Desktop. It is a seldom used selection. PLU Popup Parameters. There are four selections under Popup Parameters. They all accomplish the same purpose, and any selection can be used to perform the task. The selection allows you to place the Popup in a fixed location on the Sales Desktop. All you are doing is establishing the top left and bottom right coordinates of all four Popup Parameters, using ANY of the four selections. The four selections herein are a carryover of programming from an earlier version. The four different Popup windows may have a different number of rows, columns, the button color and button text color may be different on each of the four Popup windows. This programming, however, is accomplished in Odyssey Programming, under POS System Options Desktop Options, under the Popup Windows Tab. The font used in each Popup window is automatically sized to fit the number of characters for ALL four Popup windows. This is the Popup Line Length Text selection, also under POS System Options Desktop Options, but on the General Tab. There is also a discussion at the end of this section in this document concerning the legibility of text on Popup windows, with characters becoming small due to overly lengthy descriptors. NOTE: The Popup Parameters, i.e. the location of the Popup windows, should be done when you are creating your template Sales Desktop. While the position of each of the four different Popup windows is the same on any given Sales Desktop, it may be different on each and every Sales Desktop, like the Guest Check object. This allows you to have one, or more, Sales Desktops with a totally different look. CONDIMENT Popup Parameters. This selection performs the IDENTICAL function as if the PLU Popup Parameters selection was utilized. MEDIA Popup Parameters. This selection performs the IDENTICAL function as if the PLU Popup Parameters selection was utilized. GENERIC Popup Parameters. This selection performs the IDENTICAL function as if the PLU Popup Parameters selection was utilized. Desktop Color. This selection allows you to set the color of the Windows Background on the Sales Desktop. Odyssey/BackOffice Suite Programming POS/2100 Application Programming 243

244 Desktop Pattern. This selection is not functional. You can only set a color for the Sales Desktop. The selected Desktop Pattern WILL NOT be retained, although it will appear to take in the programming mode. Add Object. The following list will appear when the cursor is moved over the Add Object selection. All selections have been described in previous sections. Save Template. Refer to the sections Desktop Selection Save Template and Deleting Desktops. Load Template. Refer to the sections Desktop Selection Load Template and Deleting Desktops. Sales Desktops Button Types The most common Desktop Object on the Sales Desktops are Button Windows. Refer to the section Desktop Objects Button Windows for a complete discussion of creating, sizing and selecting the properties for button windows and individual buttons on button windows. Many Button Types may be placed on either the Log In Desktop, a Sales Desktop or the Split Check Desktop, while certain are restricted as to the Desktop on which they may be placed. All of those which are listed herein may be placed on any Sales Desktop. Button Types may be placed on either a Sales Desktop or the Log In Desktop have already been discussed in the section Log In Desktop Button Types. Button Type Account Number Entry Used to associate an AccountCharge Member with the guest check. When depressed, the display will prompt with an alphanumeric keyboard, as well as allow for a search by name or account number. For more information, refer to the sections AccountCharge POS/2100 Considerations and AccountCharge Buttons on the POS/2100 Desktop. NOTE: In order to be able to use the Search Name and Search Number buttons, the POS Operator must have the authorization to do so set under the Operations Settings Tab of POS Operator Programming. Button Type Add Seat Used in conjunction with entering items on a by seat basis. This is generally used to assist bus staff in presenting ordered items to the appropriate customer. It is also useful when printing checks, either a single check ordered by seat with separate totals, including tax, for each seat, or for printing separate checks for each seat. When the first item is ordered on a new guest check, it is automatically assigned to Seat 1. If the Add Seat button is never touched, then there is no designation present on the guest check object on the Sales Desktop relating to seat positions. NOTE: Refer to the section "Cafeteria Mode Operations" for a discussion of the alternative use of this button. The first touch on the Add Seat button will cause a banner showing SEAT [1] to appear above all previously entered items. Another banner showing SEAT [2] will show under these items. The banner SEAT [2] will be highlighted. Entered items are always associated with the highlighted seat number banner. To go back to seat 1, simply touch the banner SEAT [1] and enter items associated with that seat. To skip a seat number, e.g. only the patrons at seats 1 and 4 are choosing an appetizer on the first round, first touch 4 then touch Add Seat. Previously entered items are associated with seat number 1 and newly entered items are associated with seat 4. When you touch Add Seat with NO number entered, the seat added is the maximum current seat number plus 1. The organization of items on the Split Check Desktop is the same as the seat numbers. Ordering an item under seat number 2 is the same moving the item from the main order (seat number 1) to check 2 of 3 on the Split Check Desktop. If items have been associated with the wrong seat number when ordered on the Sales Desktop, the POS Operator can select the Split Check Desktop to move them around in order to properly group items for either the requisition process or the check printing process. 244 POS/2100 Application Programming Odyssey/BackOffice Suite Programming

245 Button Type Back Used very much like the Back button on your browser. If you have moved from one Sales Desktop to another, merely touching the Button Type Back will move to the previous Sales Desktop. This button will acts from a buffer of prior Sales Desktops and can be depressed multiple times sequentially. Button Type Cancel Transaction Used to Error Correct all items entered for the transaction, or during the current service round in the case of a retrieved guest check. The action is just as if all items were highlighted and the Error Correct button was depressed twice. A transaction is closed out as a zero balance guest check. A guest check is Sent. Button Type Chip & Pin As of October, 2004, this functionality is not available. Used only in the U.K. for sending the details of the transaction to Comedia software on the server for finalization using either a fixed station or wireless payment terminal, typically a Verifone Omni Button Type Condiment Chain Used to present a list of all Condiment Chains. The menu item must first be selected, i.e. the POS Operator must have touched the menu item line on the Guest Check object. The button is similar to the DCM List File List Button Type, except the list presented is all Condiment Chains rather than all List Files of type DCM. When a single Condiment Chain is selected from the list, it is just as if a Button Type of Popup Condiment Chain had been selected. Button Type Covers Used to enter the number of guests associated with a transaction. The button operates two ways. The POS Operator can enter the count, then touch the Covers button, or first touch the Covers button, then enter the number of Covers when prompted through a separate Popup entry window. The actual number of covers associated with a transaction will be set, therefore if you have previously entered a cover count of 5, then re- enter a cover count of 4, you are effectively reducing the number of covers by 1. When the Transaction Detail Report is generated through Odyssey Reports, the particular transaction will report a cover count of negative one. You can also enter a number in the "Auxiliary Text" field to pre-define the number of covers. This is principally for use as a "Seconds" button (enter a "0") when operating in Cafeteria Mode. Button Type Credit Card Hold This button is only functional if you are implementing interactive credit card authorization. The flag Credit Card Network Active on the General Tab under POS System Options Credit Card Options must be checked. When the Credit Card Hold button is touched, the point-of-sale software will present the Credit Card Number Entry window, as illustrated in the following screenshot. Odyssey/BackOffice Suite Programming POS/2100 Application Programming 245

246 While a manual entry is allowed from this popup window, the functionality of the Credit Card Hold button is to accomplish the four functions listed below. The button presents restaurant operators, particularly in bar situations, with an alternative to asking the patron to provide the credit card and actually holding the credit card itself behind the bar. NOTE: The point-of-sale software automatically identifies the type of credit card using the number. The link between the types of credit cards and the Media Finalize in the Odyssey database is established under POS System Options Credit Card Options on the Credit Card Types Tab. The functionality provided by this button is as follows: Read the First then Last Name of the card holder on Track 1 and store it with the Guest Check just as if it had been entered using the Customer Name Entry Button Type. NOTE: Changed to store first the first name then the last name for a more friendly environment. Verify the expiration date and determine the type of card being used. Retain the card number and type for eventual use in pre-authorizing (prior to the entry of a tip) or in paying the transaction. Perform an Auth Only transaction with the credit card network to confirm that the card is valid for use and has current credit availability. See POS System Options Credit Card Options for this optional interaction. If a value of $0.00 is entered, the software will not interact with the credit card network. Any interaction will result in the merchant being charged a fee.) When a Credit Card Sale or Pre-Authorization or Media Credit Card Button Type is touched later in the transaction, the credit card itself does not need to be swiped again, because the stored information is prethis fed into window. If the na me on the card is not useful in identifying the customer, e.g. it is a company name, the POS Operator can override the name functionality by using an Enter Customer Name Button Type. The credit card number and type will STILL be retained. It is recommended that the card be swiped again at finalization in order that the merchant be charged for a swiped transaction rather than a manually entered transaction. The POS2100 software does not retain full track data for transmission to the credit card processor for PCI compliance reasons. Button Type Credit Card Sale Used to initiate an actual credit card posting of an entered amount. This button is only functional if you are implementing interactive credit card authorization. The flag Credit Card Network Active on the General Tab under POS System Options Credit Card Options must be checked. When the Credit Card Sale button it touched, the first popup displayed is the Credit Card Number Entry window. The previous section provides a screen shot of this popup window. After the credit card is swiped, and assuming the card number is correct and the expiration date is correct, another window will appear to prompt the POS Operator to enter an amount. The type of window is determined in programming under Finalize Media Options Tab. The following screenshot illustrates the window provided through the default demonstration database. 246 POS/2100 Application Programming Odyssey/BackOffice Suite Programming

247 In the above window, the transaction total is $ As a convenience, it has been pre-entered into the Enter Amount window. The area on the left is intended to facilitate split payments, situations where the customer has provided two or more credit cards. With a Credit Card Sale button, the credit card authorization process is initiated immediately upon touching the Enter button. Depending on whether or not a balance due remains, the transaction may require further payment or be finalized. In either case, with a successful authorization, a credit card voucher will print. If the Media corresponding to the credit card has the flag Change To Tips checked under Media Programming Finalize Media Options Tab, then an amount entered in excess of the transaction total will automatically be added to the Tip Media, which is also set on this Options Tab. If an amount less than the transaction total has been entered, the transaction may either be finalized with another Media Finalize, or items may continue to be added. NOTE: You can not add a tip to the credit card used with the Credit Card Sale button after the credit card has been processed. You MUST either overtender by the amount of the tip or enter the tip using a Button Type Media Tip prior to using the Credit Card Sale button. For sit-down dining, when the voucher will be presented to the customer so that a tip may be added, the Button Type Pre-Authorization should be used to initiate the credit card authorization process. Button Type Customer Lookup Used to present a selection window to select the specific customer for delivery. The screen allows for the entry of a phone number, a last name or an address. If a "partial entry" is made in any field, the screen will provide the Operator with a selection window of all possible customers. As shown above, only the first three digits of the Phone have been entered, then the "Go" button next to the Phone entry area was touched. (You can also use the Enter key on the keyboard.) All existing customers with a Home Phone, Cell Phone or Work Phone are displayed below. To select the customer, touch the appropriate line and touch the "Ok" button at the bottom. If none of the displayed customers are, in fact, the delivery customer, touch the "New" button at the bottom of the screen. The "New" button will allow the POS Operator to enter, at a minimum, the correct phone number, a single line of address and the last name of the customer. The "Ok" button will display a window of all currently available information on the customer, including a selection of any order placed in the last thirty six days (see the Archive selection under Configure). Information may also be edited from this screen, as shown below. Odyssey/BackOffice Suite Programming POS/2100 Application Programming 247

248 From the Delivery Customer screen, the "Ok" button confirms the selected customer. The "Duplicate" button re-orders the displayed previous order (with current pricing). The "Activity" button displays selected days of history within the POS, number of visits, net sales and the three "Delivery Statistics" entered in the BackOffice, which may be any menu item, any department or any category. Button Type Customer Name Entry Used to associate a name with the guest check. Typically, this entry will be made from the Table List Desktop, when the New Check Button Type is used to open a guest check where there is not a table association. The software will present a keyboard entry popup which allows for the entry of up to sixteen characters to identify the customer. The popup is identical to the screenshot illustrated in the section Compulsory Account Number Entry, with a heading of Enter Reference Text and no buttons for Search Name or Search Number. The entered name will display on the guest check presentation on the Table List Desktop, at the bottom of the item area of the check. The entered name will display on the Guest Check object of the Sales Desktop both in the Header Area and at the bottom of the Item Area. Button Type DCM List File List This button is a single button method of accessing every single POS Item in the entire database which is a modifying item and contained in a List File of type DCM. The menu item must first be selected, i.e. the POS Operator must have touched the menu item line on the Guest Check object. The Button Type is similar to the Condiment Chain Button type, except the list presented is all List Files, not Condiment Chains. When a single DCM List File is selected from the list, it is just as if a Button Type Popup Items had been selected, where the List File to popup was a DCM type. Button Type Desktop Used to move from one Sales Desktop to another. When Button Type Desktop is selected, the Desktop Selector window automatically appears. This window is illustrated in the section Desktop Selection Save Template. Only existing Sales Desktops will appear, therefore, you will need to first create your Sales Desktops, then program the various Desktop Button types on each to navigate through them. Immediately after selecting the Desktop which should present to the POS Operator when the button is depressed, the Template Name of the selected Desktop will automatically fill into the Mid Text Line of the button. Generally you will want to change this text to be more operator-friendly than the names you have chosen for your Sales Desktop Template Names. 248 POS/2100 Application Programming Odyssey/BackOffice Suite Programming

249 Button Type Exit On the Sales Desktop, used to move to the Log In Desktop. This button is not active in the middle of a transaction. Button Type FIFO Recall Used to bring forward an order from the first-in, first-out buffer. This button is not active in the middle of a transaction. If there is NO order in the FIFO buffer, no action will occur. Orders are placed in the FIFO buffer using Button Type FIFO Store. The FIFO buffer can either be set on a by-terminal basis or be global for the entire store. This setting is established under the Misc. Options Selection area of POS Terminal Options Miscellaneous in Odyssey Programming. It is therefore possible that one group of terminals share a common FIFO buffer, but one or more individual terminals utilize their own FIFO buffer. Button Type FIFO Store Used to place an order into the first-in, first out buffer. This button is only active in the middle of a transaction. While the principal use is in the drive through application for quick service restaurants, it can also be useful in counter service and bar situations for a quick method of storing the current transaction to handle another customer. Orders are recalled from the FIFO buffer using Button Type FIFO Recall. The FIFO buffer can either be set on a by-terminal basis or be global for the entire store. This setting is established under the Misc. Options Selection area of POS Terminal Options Miscellaneous in Odyssey Programming. It is therefore possible that one group of terminals share a common FIFO buffer, but one or more individual terminals utilize their own FIFO buffer. Button Type Fire Message Used to place a single Fire Message on a Sales Desktop. There is a related Button Type Popup Fire Messages. Button Type Gift Card Balance Used to inquire on the current balance on an electronic Gift Card. This button requires entries under POS System Options Credit Card (egift Card) Options. Button Type Hold With Requisition This button is very similar to Button Type Send and is principally for use in U.K. pubs. Use of this, and the following button type, is an alternative to configuring POS Operators as "Single Transaction Operators". The transaction is dismissed, and all items entered during the most recent service round are requisitioned. However, the next time the POS Operator moves to any Sales Desktop, the "held" transaction is immediately retrieved. This button is used to allow another POS Operator access to the terminal while the current Operator is engaged with a particular customer for a protracted period of time. Button Type Hold Without Requisition Like Button Type Hold With Requisition, the is principally for use in U.K. pubs. It works identically, except that items entered during the most recent service round are NOT requisitioned, nor are they sent to the transaction detail log. Essentially, it is as if they had not yet been entered. They are requisitioned the next time the check is brought forward and then dismissed with a Send, Hold With Requisition or payment. Button Type Hold/Send Requisition This button type provides a manual alternative to timed fire message that delays selected items by a predetermined number of minutes. Selected items can be held from being requisitioned until the server decides to send them. Odyssey/BackOffice Suite Programming POS/2100 Application Programming 249

250 Select items entered during the current service round by highlighting them then touch the Hold/Send Requisition. When the transaction is sent, the items will not be requisitioned on either the printer system of the video system. Items which are being "held" will show on the displayed guest check as italicized. To send the items, select the ones you wish to now requisition and touch the Hold/Requisition. If any items are being held from requisition, the guest check can not be printed. If you have either Display Current Order with Send or Display Current Order with Print set under POS Terminal Options Transaction Options, the held items will always display, italicized, along with the items ordered in the most recent service round. Items being held from requisition do not combine on the guest check image displayed on the POS screen. Button Type Inquire AccountCharge Used to confirm that a customer exists in the AccountCharge database and provide certain information relating to the customer. This Button Type does NOT retain any information pertinent to the customer, nor associate the customer with the guest check. Use the Account Number Entry Button Type for that functionality. The information displayed upon a successful retrieval of customer information is shown in a screenshot in the section AccountCharge Inquiry/Confirmation Screen. Button Type Itemizer Shift This Button Type is not implemented as of the date of this documentation. It is intended for future functionality. To forgive tax on a particular transaction, use Button Type Tax Shift. Button Type Level Change This Button Type is one of six that determine the point-of-sale Price Level for sales items. The others are Level Select, Level Shift, Popup Level Change, Popup Level Select and Popup Level Shift. All of these Button Types are documented herein. Use of each of these buttons is restricted by the flag "Allow Function Keys" set on the Manager Tab, under POS Operator Definition programming. Changing the Price Level at the point-of-sale causes the price charged for individual POS Items to be that which is set on the form POS Item Programming Pricing Tab for the selected POS Price Level. This is accessed through Odyssey Programming by left clicking on Sales, then selecting List Files from the dropdown menu. A POS Item IS in actuality a Menu Item. The difference is that the POS Item has additional properties to determine where it should print, whether tax should be charged and which of the six FIXED prices associated with a Menu Item should be charged at a particular POS Price Level. Refer to the discussion under List Files. The Level Change, Level Select and Level Shift Button Types are single buttons which are associated with a single POS Price Level. The three corresponding Popups present a list of ALL POS Price Levels, allowing the POS Operator to select from this list. Whether a particular Sales Desktop, or overall installation, uses the single button approach or the Popup list approach will depend on how many of the POS Price Levels are actually being used. The default POS Price Level for each terminal is established under POS Terminal Options Miscellaneous, in the section Price Level and Menu Level Options. The current POS Price Level is always displayed on the Guest Check object, in the white area under the item display area, in the middle. The differences between Change, Select and Shift are: Price Level Change will set the selected POS Price Level, on the terminal on which the Price Level Change was touched, until it is changed. The exception is if an Auto Shift is active for the terminal, and the Price Level is being affected by the Auto Shift. If an Auto Shift IS in effect for the terminal and POS Price Level is being affected, then a Price Level Change will act the same as a Price Level Select. 250 POS/2100 Application Programming Odyssey/BackOffice Suite Programming

251 Price Level Select will set the selected POS Price Level, on the terminal on which the Price Level Select was touched, during the balance of this service round. Price Level Shift will set the selected POS Price Level only for the next main item (PLU type item) entered. A Price Level Shift DOES NOT affect the POS Price Level for any associated condiments, whether they are part of a pre-programmed popup chain or not. The Price Level Shift IS remembered if the next Button Type touched is a Desktop Button Type, but again, only for the next main item. Button Type Level Select Refer to the section Button Type Level Change for a complete discussion regarding various options to set the POS Price Level on the POS terminal. Button Type Level Shift Refer to the section Button Type Level Change for a complete discussion regarding various options to set the POS Price Level on the POS terminal. Button Type Loyalty Add This Button Type is used in conjunction with the Loyalty functionality of Mercury Payment. To associate a Loyalty customer with a particular transaction, touch this button then swipe the magnetic card when prompted. Button Type Loyalty Balance This Button Type is used in conjunction with the Loyalty functionality of Mercury Payment. To print a chit for the Loyalty customer which will show the number of accumulated points (dollars spent) touch the button then swipe the magnetic card when prompted. A chit will print which will also indicate if the patron is eligible for the programmed automatic discount on the next transaction. Button Type Loyalty Rewards This Button Type is used in conjunction with the Loyalty function if the setting under POS System Options Credit Card Options Loyalty tab has a check mark for Use Loyalty Rewards Not Voucher. It allows the POS Operator to re-display the list of rewards for which the customer is currently eligible. Button Type Media Used to place any Media as a single button on a Sales Desktop. Two related Button Types are the Popup Media List and Popup Media Type buttons. There are various programming options as to how a touch of a Button Type Media will act. These include prompting for an entry or automatically accepting a default, etc. All of these programming parameters are set in Odyssey Programming on a by-media basis. The two options for Manager Required and Reason Code Required are set on the Media Programming General Tab. The options which are specific to the Media Type for the selected media are programmed individually, generally on an Options Tab or the Authorization Tab, in the case of Media Finalize. When you select Media as the Button Type, a popup window will display. On the left will be a list of all Media Types. By touching the Media Type Name, the right portion of this popup will show the medias which are active and are of this Media Type. To select a specific Media to associate with this button, first select the Media Type, then select the individual Media. After selecting the specific Media from the right, touch OK to program the button. The popup list of Media Types and active Media is shown in the following screenshot. Odyssey/BackOffice Suite Programming POS/2100 Application Programming 251

252 The Auxiliary Text section of the Button Properties window is particularly useful when programming Media Button Types and is covered in the following section. There are two Media Button Types that operate in two different ways, the Refund Transaction Media and the Overring Transaction Media. These buttons may either be used as the very first button to begin a transaction or used immediately after the Select button is touched from the Closed Check screen. When used as the very first button, all items entered are negative, and payment must be made which reverses the prior receipt of payment. Given the ease of using the Select button from a Closed Check screen, the Overring Transaction Media will generally not be used in this way. If the transaction never happened, i.e. all items were simply entered incorrectly and were immediately re-entered by the POS Operator, it is much easier to perform the operation from the Closed Check screen. However, if the operation is a real refund, it is possible that the original transaction did not occur in the same Sales Day. When either of these two buttons is touched after bringing forward a Closed Check, the operation is complete and the entire transaction selected is reversed through the creation of a new check number, with identical items and payment methods, with all signs reversed. Button Type Media (Button Property Auxiliary Text) The Auxiliary Text area of Button Type Media is used to establish preset payment amounts for Finalize Media. It can also be used to create fixed amount discounts instead of creating multiple discount Medias through Odyssey Programming. The difference is that with multiple discount Medias, all amounts will be reported separately. However, if the separate reporting is not a requirement, then a single open discount Media could be created and the button itse lf can provide the amount of the discount. This works as well for any other type of media where an amount or percentage is entered. The text entered in as Auxiliary Text is placed in the Entry Window before processing the Media button itself, just as if it had been entered by the POS Operator. The following screenshot shows the Button Properties window for a $10.00 fixed payment Cash Media button. In the particular screenshot above, there is also an Image associated with the button. The check mark next to the wording Next Highest Dollar is only applicable to Media Finalize. 252 POS/2100 Application Programming Odyssey/BackOffice Suite Programming

253 There is an exception to the just as if it had been entered by the POS Operator rule on Auxiliary Text for preset amounts. Suppose a patron provided two Fifty Dollar bills for a particularly large transaction. There is no Fixed Amount Preset on the payment Sales Desktop for $100.00, but there is a Fixed Amount Preset for $ If the POS Operator entered 2 then touched the preset, we DO NOT want to take it as $250.00, but rather to multiply the 2 times the preset amount. With Fixed Amount Presets, you can enter a quantity then touch the Fixed Amount Preset and the result will be the quantity times the Fixed Amount. Button Type Media (Credit Card Authorization Discussion) When the flag Credit Card Authorization Active is set under Finalize Media Authorization Tab, AND the flag Credit Card Network Active is set under POS System Options Credit Card Options on the General Tab, the Credit Card Number Entry window will automatically appear then the credit card finalizing media is touched. This window is illustrated in a screenshot in the Button Type Credit Card Hold section. Generally with credit card authorization active, you would use Button Type Credit Card Sale instead of directly touching the Media button. This Button Type automatically identifies the credit card type. For preauthorization, prior to presenting the voucher on which the customer would add a tip, you would use Button Type Pre-Authorization. If you do touch a credit card Media directly, the Credit Card Number Entry window is only looking for the credit card type linked to the Finalize Media you have selected. If you touch an American Express Finalize Media, then swipe a M/C, you would be presented with an error message, as is illustrated below. Again, with Button Type Credit Card Sale or Button Type Pre-Authorization, the Credit Card Entry window automatically identifies the type of credit card. Button Type Modify Fixed Menu Item This Button Type is used to change a Fixed Menu Item to either a lesser value or higher value item. The procedure is to first touch the Fixed Menu Item on the screen, then this button. If there are any other Menu Items in the same List File which have condiments from the same Condiment Files, the POS Operator is presented with a list of allowable modifications. There is no requisition chit printed on remote printers, since only the condiments represent actual prepared items. Refer to the section on Fixed Menu Items. Button Type Modify Payment This Button Type has two separate modes of operation. The first is to modify a payment on a check which has been re trieved from the Closed Check Desktop. The second is to transfer an amount from one Finalize Media to another Finalize Media as an individual, separate transaction. The first mode of operation obviously require s access through the Closed Check Desktop. The second mode of operation is only valid on a newly ope ned transaction, with no items whatsoever. This mode of operation is similar to a Paid Out or Received On Account operation. NOTE: It is HIGHLY recommended that the programmer place THREE Modify Payment buttons on the Desktop. One with text of "Begin Modify Payment", a second with the text of "End Modify Payment" (in order to avoid ANY Operator confusion as to how to end a Modify Payment transaction) and a third with th e text "Media Transfer" to distinguish the different methods of operation. Odyssey/BackOffice Suite Programming POS/2100 Application Programming 253

254 Modify Payment On A Closed Check A guest check is selected from the Closed Check Desktop. This button should be placed on the Sales Desktop programmed under POS Terminal Options Desktop Options as the Closed Check Desktop if the establishment is going to change incorrectly entered payment methods. It is also a required button as a prelude to modifying a tip which was incorrectly entered during a Pre-Authorization process and where the guest check was closed with the incorrect tip remaining. The POS Operator must have a check under Allow Media Transfers on the POS Operators Manager Settings Tab in order to use the Modify Payment button. There are only three buttons which are valid once the Select button is depressed from the Closed Check screen. Both the Refund Transaction Media and the Overring Transaction Media are Button Type Media buttons, which act immediately and cause a reversal of the entire check, including all payments. The third button is the Modify Payment button. Once the Modify Payment button is selected, the Status Window will immediately display Modify Payment-. The settings under POS System Options Miscellaneous, in the Media section do not apply to this use of the "Modify Payment" button. The software will then allow the POS Operator to touch a payment method, a service charge or a tip, and then Void the highlighted media. For voided service charges or tips, the transaction balance due will actually show a negative amount due. The Modify Payment operation CAN NOT be completed until the Balance Due is identically $0.00. If the Modify Payment button was touched accidentally, and no amounts were reversed, the POS Operator need merely touch the Modify Payment butt on again. Since any media may be reversed during a Modify Payment transaction, the software needs a way to be told This transaction is over. Quit already. To complete a Modify Payment transaction, touch the Modify Payment butt on again. As long as the Balance Due is identically $0.00, the point-of-sale terminal will automatically revert to the Log In Desktop. If it appears change is due because of a reversal of a tip or service charge, or an amount is still due because of a reversal of a payment, the software will prompt with the amount due. Transfer Finalize Media To Another Using Modify Payment At the point-of-sale, a Transfer Finalize Media operation, using Button Type Modify Payment, is a separate transaction. A Transfer Finalize Media operation may NOT be recorded during a sales transaction. In order to perform this Transfer Finalize Media operation, the POS Operator must have either the "Manager Mode Allowed" flag or the "Allow Media Transfers" flag set under POS Operators on the Manager Settings Tab. NOTE: When a Transfer Finalize Media operation is performed, the Cover Count (Guest Check Count) is automatically set to zero, regardless of any Covers entry which has been made. When Button Type Modify Payment is the first button touched in a new transaction, the POS Operator may be prompted for either a Reason Code or Reference Text, or both, depending on the settings under POS System Options Miscellaneous, in the Media section. After any required entries, a popup window will appear to enter the amount to be transferred. Next, a popup window appears to select the Finalize Media which will be reduced in amount, followed by a popup window to select the Finalize Media which will be increased in an identical amount. There is a final confirmation entry required to complete the process. Excluded from the displayed Finalize Medias presented are those which are set to interact as a credit card, a gift card or with the AccountCharge module. The amounts in these Finalize Media may only be "transferred" through the Closed Check Desktop and then using Button Type Modify Payment to first remove the Finalize Media from the Guest Check then "add back" the correct Finalize Media. Button Type Nectar Attach Do not place this on any Sales Desktop. This pertains to a custom development for a U.K. customer. 254 POS/2100 Application Programming Odyssey/BackOffice Suite Programming

255 Button Type Nectar Balance Do not place this on any Sales Desktop. This pertains to a custom development for a U.K. customer. Button Type No Sale Used to open an attached cash drawer without a sales transaction. Even if this button is placed on a Sales Desktop, there must be a check on the flag Allow No Sales under POS System Options Miscellaneous. In addition, the POS Operator must have the authority set as Allow No Sales under POS Operators Operation Settings Tab. Button Type Outlet Inquiry Used in conjunction with an interactive Property Management System interface for outlet charge posting, in conjunction with the software module WinPost. Used to confirm that a customer exists in the Property Management System database and provide certain information relating to the customer. This Button Type does NOT retain any information pertinent to the customer, nor associate the customer with the guest check. When the keyboard presentation is displayed, the entry will be sixteen characters of text. The actual information entered is dependent on the Property Management System, but is typically a Room Number or the first few characters of the guest s last name, followed by a room number. Button Type Pizza Pricing Do not place this on any Sales Desktop. This pertains to a custom development effort for a French customer. For a discussion on this functionality, refer to the text file POS2100-Version.txt under Version Button Type PLU List File List This button is a single button method of accessing every single POS Item in the entire database which is a main item and contained in a List File of type PLU. When depressed, a Popup window will display showing all the List File Names for List Files of type PLU. When the POS Operator touched a displayed name, then the list of all POS Items in the selected List File will appear in a Popup window. When the POS Item is touched, it is just as if a Button Type Preset had been touched, or just as if a Button Type Popup Items had been touched, then the POS Item selected from that presentation. Button Type Popup Condiment Chain Used to present a Popup window, or a sequence of Popup windows, in order to modify a menu item. The menu item must first be selected, i.e. the POS Operator must have touched the menu item line on the Guest Check object. This Button Type is similar to Button Type Popup Items, where the List File selected to popup is a DCM type list file. The difference is that there are attributes which may be assigned to an individual List File when it is part of a Condiment Chain. Condiment Chains are created in Odyssey Programming. The most frequent use of this button is to present a Popup window that is NOT compulsory, but allows the Highlight functionality of a List File which is part of a Condiment Chain. This functionality is discussed at length in the section Condiment Chain Programming, under the Multiple Entry and Highlight selections. Button Type Popup Current Items Used to cause a Popup display of only those items which have been entered during the current service round. The Popup will use the PLU Popup Parameters to determine where it will appear on the Sales Desktop. The following screenshot illustrates the Popup window. Odyssey/BackOffice Suite Programming POS/2100 Application Programming 255

256 To dismiss the Popup, the POS Operator merely touches the banner at the top where Current Items is displayed. An alternative method to use in displaying the Current Items is a function of the Guest Check object itself. Referring to the screenshot in the Sales Desktops Guest Check Object section, if the POS Operator touches anywhere in the white area at the top of the Guest Check object, where the time, table number, check number and number of covers is displayed, then the items displayed in the Item Display area of the Guest Check object will only be those that were entered on the current service round. In addition, the Item count, shown in the white area below the Item Display area of the Guest Check object, will only reflect items entered during the current service round. To revert to displaying all items on the guest check, the POS Operator merely touches the white area at the top again. Two flags set through Odyssey Programming, Display Current Order With Send and Display Current Order With Print are set through POS Terminal Options Transaction Options, on the End of Transaction Tab. If either of these flags is checked for a particular terminal, the POS Operator will be presented with a Popup similar to the preceding one when a Button Type Send Check or Button Type Print And Send is touched to finish a service round. The screenshot included in the section Fixed Menu Type Items POS/2100 Control illustrates a form of this Popup presentation. Button Type Popup Fire Messages Used to display a Popup window of all Fire Messages. There is a separate Button Type Fire Message which places a single Fire Message on the Sales Desktop. Button Type Popup Items Used to display a Popup window of POS Items, either main menu items or modifying items. When Popup Items is selected as the Button Type, a selection window will automatically appear as illustrated in the following screenshot. The two check boxes on the right of the above screen shot determine whether the List File Names presented in the selection box on the left are PLU or DCM type List Files. To create a Popup of modifying items, first click the check area next to DCM. To select which List File of POS Items will appear, first select the List File Name from the left side of the screen. For reference, all POS Items in the selected List File show grayed out on the right. To finalize the selection process, click on the OK button on the right. The location of the Popup window is set under PLU Popup Parameters under Sales Desktops Selection Options. 256 POS/2100 Application Programming Odyssey/BackOffice Suite Programming

257 Button Type Popup Level Change Refer to the section Button Type Level Change for a complete discussion regarding various options to set the POS Price Level on the POS terminal. Button Type Popup Level Select Refer to the section Button Type Level Change for a complete discussion regarding various options to set the POS Price Level on the POS terminal. Button Type Popup Level Shift Refer to the section Button Type Level Change for a complete discussion regarding various options to set the POS Price Level on the POS terminal. Button Type Popup Media List Used to display a popup selection of various medias. The selections which are displayed when programming the button are from the list of Media List File Names established under Media List Files. The medias which will popup are also programmed therein. Generally the medias listed on the popup will be of the same type, but this is not required. Once a button on the Popup window is touched, it is just as if the Button Type Media had been touched. When you select Popup Media List as the Button Type, a list of all programmed Media List File Names will popup. By touching the Media List File Name, the right portion of this popup will show the medias which are programmed to belong to this Media List File. The screenshot which follows illustrates the programming popup window. After selecting the Media List File Name from the left, touch OK to program the button. Note that you can program Auxiliary Text on a Button Type - Media along with programming a Media Finalize button to act as a Next Highest Dollar. The functionality provided through the programming of a Button Type Media is NOT available when selecting a media from a Popup Media List. Button Type Popup Media Type Used to display a popup selection of all medias of a certain type, e.g. all Line Item Discounts or all Media Finalize. Once a button on the Popup window is touched, it is just as if the Button Type Media had been touched. The functionality of the Button Type Popup Media List allows the programmer to pick and choose which media are displayed. Popup Media Type will display ALL of media of the selected media type. In general, it is a better choice to use a Button Type Popup Media List than a Popup Media Type. When you select Popup Media Type as the Button Type, a popup window will display. On the left will be a list of all Media Types. By touching the Media Type Name, the right portion of this popup will show the medias which are active and are of this Media Type. The display presentation is identical to that presented when Button Type Media is selected. The difference is, that with Button Type Media it is a two step process, first select the Media Type, then select the individual Media. With Button Type Popup Media Type, the list Odyssey/BackOffice Suite Programming POS/2100 Application Programming 257

258 of specific Medias are grayed out since there is only a selection of Media Type. After selecting the Media Type from the left, touch OK to program the button. Note that you can program Auxiliary Text on a Button Type - Media along with programming a Media Finalize button to act as a Next Highest Dollar. The functionality provided through the programming of a Button Type Media is NOT available when selecting a media from a Popup Media Type. Button Type Popup Order Video Route This button will display a Popup window presenting two choices for the routing of items to printers and Order Video screen. Refer to the discussion at the bottom of the section under Printer Configuration Terminal Print Options Remote Tab for the programming within Odyssey MWS relating to this functionality. Selecting Standard from the Popup routes only to lines 1 and 2 in each Output Group. Selecting Alternate routes to lines 3 and 4 in each Output Group. Button Type Popup Sale Type This button will display a Popup of Sales Types to allow the POS Operator to change the Sales Type for a particular transaction. The Sales Types will be listed in order, 1 through 3. Depending on the setting for the terminal under POS Terminal Options Transaction Options Start Of Transaction Tab for Active Sales Types, the third Sales Type may not display. The Default Sale Type for a terminal is programmed on the same Tab, as is the flag Compulsory Sales Type Entry which displays this popup for each new transaction. Button Type Pre-Auth Tip Modify This button is used to modify a tip amount which has been added to a credit card after the Pre-Authorization process. Generally, the button will only be used in conjunction with a Modify Payment transaction, since most transactions utilize a single credit card which will pay the transaction in full. However, the POS/2100 supports the use of multiple credit card payments during a single transaction and allows the entry of the tip itself to be postponed when the amount which has been pre-authorized. Programming the button is simply a matter of selecting the Button Type and assigning text to the button. The balance of this section deals with operational issues relating to the use of the Button Type Pre-Auth Tip Modify. This Button Type will not be active unless there is a check next to Credit Card Network Active under POS System Options Credit Card Options. To change the amount of a tip which has been added to a credit card when the transaction has been closed: Access the Closed Check screen. Find the closed check you wish to modify and touch the check in order to highlight it. Touch the Select button. The POS Operator will require the appropriate authority. When the Sales Desktop configured as the Closed Check Desktop is presented, touch the Modify Payment button. The POS Operator will require the appropriate authority. Touch the Charge Tip line on the Guest Check object (illustrated below). Touch the Pre-Auth Tip Modify button. The Tip Entry window will appear, with the previously entered (and already authorized) tip amount entered. The Tip Entry window appears as a screenshot in the following section. Touch the Clear button on the Tip Entry window to clear out the incorrect tip. Enter the correct tip. 258 POS/2100 Application Programming Odyssey/BackOffice Suite Programming

259 Touch the Enter button on the Tip Entry window. An authorization process will occur. Once the authorization process completes, touch Modify Payment again to complete the process. There is a Void button on the Tip Entry window. This button will void the entire credit card transaction, not just the tip. To prevent erroneous entries during a tip modification process, a warning window appears when the Void button is touched on the Tip Entry window. When an amount less than the transaction total is entered through the Pre-Authorization process, the point-ofsale software postpones prompting for the tip amount. Such a pre-authorization will result in a display such as the screenshot which follows. The four leading? characters indicate that no tip has been entered for the Amex credit card. If a tip of any amount, including $0.00, had been entered, these characters would not display. The point-of-sale software will force the entry of a tip amount with every Pre-Authorization process. Of course, $0.00 may be entered but the software will remind the POS Operator that this is inordinately low. For transactions which have not been finalized, to either add a tip to a pre-authorized credit card or change the amount of the tip on a credit card were one has already been applied (and authorized): Touch the Charge Tip line on the Guest Check object. Touch the Pre-Auth Tip Modify button. The Tip Entry window will appear, with the previously entered (and already authorized) tip amount entered, or with a blank entry window if no tip has been entered. The Tip Entry window appears as a screenshot in the following section. Touch the Clear button on the Tip Entry window to clear out the incorrect tip, if necessary. Enter the correct tip. Touch the Enter button on the Tip Entry window. An authorization process will occur. NOTE: If any credit cards have been pre-authorized in an amount less than the transaction total, i.e. the four? characters precede the Charge Tip line on the Guest Check object, no other Media Finalize buttons will be available. The POS Operator MUST follow the process above, even if it is to merely indicate a tip of $0.00. Button Type Pre-Authorization This button is used to initiate a Pre-Authorization process for credit cards. Programming the button is simply a matter of selecting the Button Type and assigning text to the button. The balance of this section deals with operational issues relating to the use of the Button Type Pre-Authorization. This Button Type will not be active unless Credit Card Network Active under POS System Options Credit Card Options is set. When the Pre-Authorization button is touched, the POS Operator will be presented with the Credit Card Number Entry window, a screenshot of which is shown in the Button Type Credit Card Hold section. If a Credit Card Hold button has been previously used to capture the credit card information, this window will already have entries. The POS Operator should either swipe the card or manually enter the card number and expiration date. Odyssey/BackOffice Suite Programming POS/2100 Application Programming 259

260 Immediately following the Credit Card Entry window, the POS Operator will be presented with an Amount Entry window. The exact window will depend on programming, however a typical Amount Entry window for credit cards is shown in a screenshot in the Button Type Credit Card Sale section. The POS Operator should either accept the prompted amount or enter the amount to be pre-authorized on the credit card, then touch the Enter button on the Amount Entry window. The point-of-sale software WILL NOT accept an amount to be pre-authorized which is greater than the transaction total. If an amount greater than the total of the transaction is entered, the following screenshot illustrates the message displayed. If the amount entered to be pre-authorized is exactly the transaction total, the software will automatically Send the transaction and present either the same Desktop as if a Button Type Send was touched. The software will perform the pre-authorization in the background and the voucher will print as soon as the process is complete. While the background process is taking place, the terminal can be used by the same POS Operator, or any other POS Operator, for any point-of-sale function. If the amount entered to be pre-authorized is less than the transaction total, no action will be automatically taken as regards the guest check. The POS Operator may pre-authorize another amount on a different credit card, or even enter more items. The pre-authorization WILL be processed in the background as soon the Enter Button on the Amount Entry window is depressed. As soon as the pre-authorization process is complete, the voucher will print and a line will be added immediately under the payment media on the Guest Check object of????charge Tip.00. This is illustrated in the section Button Type Pre-Auth Tip Modify. As noted in that section, the software REQUIRES that a tip amount, even if it is $0.00, be entered with every pre-authorization process. Refer to that section for instructions on entering the tip on pre-authorized amounts which are less than the transaction total. While it is possible that the same credit card could be used for two separate pre-authorization processes, it is highly unlikely. It is much more likely that the POS Operator, in the confusion of having been given two of the same types of credit cards, has inadvertently swiped the same card twice. To eliminate this kind of error, the software provides a prompt when the same credit card is used for more than one pre-authorization process in the same transaction, as is illustrated in the following screenshot. On the actual point-of-sale screen, the entire swiped number IS displayed. If the same card IS to be preauthorized more than once in a single transaction, the POS Operator should touch Yes. If the swipe was an error, the POS Operator should touch No, then begin the process again by touching the button Pre- Authorization. 260 POS/2100 Application Programming Odyssey/BackOffice Suite Programming

261 If the POS Operator has either entered the exact amount of the transaction on one or more pre-authorization processes, and then the Guest Check has been sent, the next time the guest check is opened after the voucher has been printed, the software will automatically prompt for tip entries. If there is more than one preauthorized amount, the software will lead the POS Operator through the process of entering a tip amount for each and every pre-authorized amount. The following screenshot illustrates the Tip Entry window which will be displayed. The POS Operator can either enter an amount in the window next to Tip or touch the window next to Total and enter the amount the customer has written as the total when the customer manually added the tip to the pre-authorized amount on the presented voucher. After entering either the tip, or the customer s written total, the POS Operator should depress the Enter button. As tip amounts are being entered, the software is checking the settings in POS System Options Credit Options to assist in preventing erroneous entries. If the amount of tip entered is less than the entry Tip Verification Percentage, then the following message will be presented. Card If the amount of tip entered is greater than the entry Pre Authorization Percent, then the following message will be presented. With either of the preceding messages presented, the POS Operator can select either No or Yes. If No is selecte d, the Tip Entry window will be presented again. Odyssey/BackOffice Suite Programming POS/2100 Application Programming 261

262 When all tip entries have been performed, and when the transaction total is $0.00, the software will present one final opportunity for the POS Operator to use the Guest Check object to review all entered tip amounts and totals by displaying the screenshot illustrated below. If any tip amounts require correction, the POS Operator can select No and use Button Type Pre-Auth Tip Modify to change the entered amount. If everything is finally correctly entered, the POS Operator should touch Yes. The entries can still be changed through accessing the Closed Check Desktop. Button Type Preset This button is used to put a POS Item on a button in a button window. When Button Type Preset is selected, the same selection window as is illustrated in the section Button Type Popup Items will appear. Use the two selections on the far right of the screen to pick from main menu items (PLU) or modifiers (DCM). Like placing Medias on a button as opposed to listing them by Media Type, the selection of the Preset is a two step process. First select the List File where the POS Item is located from the left area of the window, then select the POS Item from the list on the right side. Select the OK button to complete the process. NOTE: It is quite possible that a Menu Item will exist in several different List Files, as several different POS Items. Make certain you are selecting the correct List File. The Auxiliary Text field is available for Button Type Preset. An example might be a single button to purchase a dozen donuts, or a single button to purchase a bag of four hamburgers. Like the Auxiliary Text for a Fixed Amount Finalize Media, an entered quantity will be multiplied by the number in the Auxiliary Text field. Button Type Print And Send This button is used to dismiss the current transaction from the Guest Check object, send any new items to the requisition system and print a receipt/guest check. A prompting window including only newly entered items may be programmed to appear by checking Display Current Order With Print under POS Terminal Options Transaction Options on the End Of Transaction Tab. Button Type Print By Category And Send This button is used to dismiss the current transaction from the Guest Check object, send any new items to the requisition system and print a receipt/guest check which will contain a quantity and amount for each category. The categories will print by category number. Button Type Print By Seat And Send This button is used to dismiss the current transaction from the Guest Check object, send any new items to the requisition system and print a receipt/guest check with subtotals, including tax, for all guest check images on the Split Check screen. These images will be listed by Seat Number. The single guest check WILL NOT be separated into multiple checks. The functionality is for presentation purposes only. 262 POS/2100 Application Programming Odyssey/BackOffice Suite Programming

263 Button Type Print Divide Equal And Send This button is used to dismiss the current transaction from the Guest Check object, send any new items to the requisition system and print a receipt/ guest check with subtotals, including tax, based on an entered number of people who will split pay the bill. These images will be listed in a numbered sequence. The single guest check WILL NOT be separated into multiple checks. The functionality is for presentation purposes only. It is mer ely used to assist customers who are trying to equally render payment for the bill. Button Type Priority Order Used in conjunction with an Order Video screen, typically at the drive through window when items are ordered at the p ayment window. Depressing this button will cause the current order to "move to the front" of all other orders on the Order Video screens so that the items may be assembled on a priority basis to "clear the lane". The order will have an extra header line stating "PRIORITY". A priority order will appear in the second order slot, pushing non-priority orders to the right. The second window was chosen over the first to prevent confusion on the part of kitchen staff who might already be working from the order being displayed in the first window. In addition, if staff had just completed the order in the first window, and were about to bump it off, the priority order might be inadvertently bumped off if it were moved to the first window. Button Type Recipe This button may also be placed on the Log In Desktop. The button is used to display an entered text recipe, along with an optional picture of the menu item, if one has been entered for the menu item under Recipe Programming POS Recipe Tab. If an item is highlighted in the Guest Check area, the recipe for that item will be displayed. If no item is highlighted, a list of all menu items with an entered POS Recipe will be displayed for selection by the operator. Button Type Repeat This button is used to enter again any highlighted main menu items and all associated modifiers. The POS Item(s) highlighted must have the Allow Repeat flag set under POS Item Programming on the General Tab. Through the entry in Auxiliary Text, Button Type Repeat can be configured to operate in two different ways. With no entry in Auxiliary Text, highlighting 2 Budweisers will result in 4 Budweisers. The repeated quantity is the quantity of items highlighted. With a 1 in Auxiliary Text, highlighting 2 Budweisers then touching Repeat will result in a total of only 3 Budweisers. The repeated quantity is 1. You can still cause multiple quantities of the highlighted item to be entered with a 1 in Auxiliary Text. Highlighting 2 Budweisers, then touching 5, then touching Repeat will result in a total of 7 Budweisers on guest check, or five more buds. Button Type Room/Acct Print This button functions like Button Type Print and Send, however it inserts four extra lines immediately after the printed total. The lines print TIP: with an area for the patron to enter a tip amount, TOTAL W/TIP: with an area for the patron to add the tip to the printed total, a line with the words Room Number underneath and a line with the words Please Print Name underneath. the Odyssey/BackOffice Suite Programming POS/2100 Application Programming 263

264 Button Type Sale Type This button is used to change the Sale Type of the transaction. The effect is the same as if Button Type Popup Sale Type had been selected, then the appropriate Sale Type selected. When Button Type Sale Type is selected, a Popup window will display the Sale Type Names. Select the appropriate Sale Type and touch the OK button. When the OK button is selected and the Button Properties window is again displayed, the Sale Type Name will appear in the Auxiliary Text field, grayed out. Button Type Scale Used to either interact with an attached scale or manually enter a weight. When Button Type Sale is selected, a list of Scale Buttons will automatically display. Generally there will only be a single Scale button, or perhaps a second for a manual entry backup. Select the Scale Button name. A POS Item with the flag Scale Required set on the Flags Tab under List Files POS Item Programming must be preceded by the use of a Scale Button. Conversely, the Scale Button CAN NOT be used with any POS Item where this flag is NOT set. A POS Item is either weighed, or it is not. Button Type Send Check This button is used to dismiss the current transaction from the Guest Check object and send any new items to the requisition system. A prompting window including only newly entered items may be programmed to appear by checking Display Current Order With Send under POS Terminal Options Transaction Options on the End Of Transaction Tab. If the flag Print Full Detail On Send is set under Terminal Print Options Check 1 Tab, then this Button Type will function identically to Button Type Print and Send. Button Type Split Check This button is used to access the Split Check Desktop. The Split Check Desktop is discussed in the following section. Button Type Tax Shift Used to forgive tax on a particular transaction. If the button is touched a second time, the tax will be restored. This Button Type MUST be used during the same service round or transaction in which payment will be made in full. The status is NOT retained from one service round to the next. Button Type Text This button is used to enter information into the Entry Window. In the demonstration database, there are Fixed Entry buttons of Button Type Text, with Auxiliary Text of 5.00, and This provides a two step Fixed Amount Payment entry. Touch the Text button to get the amount, then touch any Media button. The entire functionality of this Button Type is to enter the Auxiliary Text into the Entry Window as a prelude to touching some other button. Since payment media require either a 5 then either a. or a 00 to enter $5.00, this is often quicker than using the numeric keypad. 264 POS/2100 Application Programming Odyssey/BackOffice Suite Programming

265 Button Type Tip And Total Print This button functions like Button Type Print and Send, however it inserts extra lines immediately after the printed total. The lines printed are TIP: with an area for the patron to enter a tip amount followed by TOTAL W/TIP: with an area for the patron to add the tip to the printed total. A signature line may also print, depending on the setting of the option under Printer Configuration Terminal Print Options, on the Check 2 Tab in the Sign and Tip Lines Section, "Suppress Sign Line". Another related option on the same tab in the same section is "Print Tip Suggestions". Setting this flag will cause a single line to print showing "For Your Convenience" and three calculated tip amounts; 15%, 17.5% and 20%. The percentage is applied to the subtotal, before tax and exclusive of any service charges. Button Type View Prior This button is used to facilitate printing, or reprinting, closed checks from the Sales Desktop, as opposed to accessing the Closed Check Desktop through the Log In Desktop. The button is only available outside of a transaction. It is particularly useful in counter service and quick service applications where checks may not always be printed. When the button is touched, the Closed Check Desktop is displayed. However, there are two differences between this presentation and the actual Closed Check Desktop. The only checks displayed when the POS Operator touched View Prior are ones closed on the terminal on which the View Prior button was touched. After touching the selected guest check, the ONLY option, other than viewing the closed check on the screen, is the Print Button. Button Type View ScoreBoard This button is used to present a full screen image of the Texas Digital customer display. The button may be placed on Sales Desktops for all terminals, but will only present an image on a terminal if the flag ScoreBoard Active is set on Terminal Print Options Remote Tab for the terminal on which the button is touched. The Display Heading, Background Color and Text Color for the image displayed on the point-of-sale terminal when View ScoreBoard is touched are set under Printer Configuration Scoreboard. A screenshot of the image presented follows. The POS Operator is able to use the up arrow and down arrow buttons on the right of the screen to move not only the image on the point-of-sale screen, but the image viewed by the customer on the actual customer display. The Exit button at the bottom returns to the Sales Desktop. Odyssey/BackOffice Suite Programming POS/2100 Application Programming 265

266 Split Check Desktop This Desktop is can be used either to create multiple checks at a single table or to establish seat numbers for various items. During operations, the Split Check Desktop is accessed from any Sales Desktop through Button Type Split Check. When programming, you can not access the Split Check Desktop unless you enter an item. After you have entered an item, then you can select Button Type Split Check to view this Desktop. Items entered will not print or requisition. The easiest way to remove these items and return to the Log In Desktop, when in programming, is to highlight each separately, then touch an Error Correct Media button (Void Item Media, with the flag Current Items Only set.) With all items error corrected, another touch on the Error Correct button will return you to the Log In Desktop. A screenshot of the Split Check Desktop in the default demonstration database follows. There are five objects on the above Desktop. The numeric pad on the left is a button window, with ten Button Type ASCII buttons. The Guest Check display with (orig) at the top, and the object on the right which shows two guest checks, are each separate objects. At the bottom, the white space on the far left is an Entry Window object, and the seven buttons on the bottom right are simply buttons in a button window. You can not delete the two check objects from the Split Check Desktop, you can not size these objects nor can you add these objects. They are fixed as part of the Split Check Desktop. NOTE: Although the Split Check Desktop may be changed, it is highly recommended that you NOT alter the presentation provided in the default POS2100.mdb database, other than perhaps changing the text lines, the icons or the button and text colors. 266 POS/2100 Application Programming Odyssey/BackOffice Suite Programming

267 Split Check Desktop Selection Options The selection options presented when you right click on the Background Color area of the Split Check Desktop are identical to those presented on a Log In Desktop, except there is no Load Template selection. Like the Table List Desktop, there is only one Split Check Desktop. There are only two objects which may be added to the Split Check Desktop, a Button Window and an Entry Window. Split Check Desktop Moving Items This section is entirely operational in nature. To move an item from any check image on the Split Check Desktop to another: Touch the main item. The item will highlight, along with all of its modifiers. Touch as many main items as you wish to move, until all are highlighted. Note that the Combine Mode in the Split Check Desktop is ALWAYS None. This is to facilitate moving individual items. Refer to the section under POS System Options Desktop Options POS Displayed Guest Check Combine Modes for a discussion of Combine Mode. Touch the top of the guest check image to which you wish to move the highlighted item(s). This is the area where the 2 of 3 appears for checks other than the original. When the top area of the guest check image is touched, the items will move, and the top of the check to which the item(s) was moved will turn green. All of the guest check images have a tool to move all items quickly from one check to another. To highlight ALL items on any guest check, touch the white area below the Item Display Area. All items on the selected check image will highlight. Split Check Desktop Button Types The available Button Types on the Split Check Desktop reflect is extremely limited, but powerful, functionality. The following is a complete list of all Button Types available on the Split Check Desktop. Button Type Add Check Used to create another seat, or check view, in the check display object on the right of the screen. The default presentation is the original guest check and two others onto which items may be placed. To create five seats, requiring four checks onto which items may be moved, touch the Add Check button twice. The object which displays guest checks 2 and above is set to only display three checks at a time, for legibility. The scroll bar at the bottom of this object allows the POS Operator to view more than three at a time. The object is shown in the following screenshot after touching the Add Check button two times. Odyssey/BackOffice Suite Programming POS/2100 Application Programming 267

268 Button Type ASCII Used on the numeric keypad. Refer to Login Desktop Button Types ASCII. Button Type Clear Refer to Login Desktop Button Types Clear. Button Type Covers Used to allocate the already entered number of covers between newly created, split checks. After moving items to a new check, touch the banner at the top and then touch the Covers button, generally labeled Change Covers on the Split Check Desktop. The modal window shown below will appear. Touch the + or covers button to add or subtract covers from the selected guest check. Adding to the selected guest check will automatically subtract from the main guest check. This button is intended to allocate already entered covers and will not allow for the addition of any covers from the Split Check Desktop Button Type Create Check Used to create a separate guest check(s), at the same table, using one (or more) of the guest check images on the Split Check Desktop. Move the items as required to one or more of the displayed guest check images. Touch the top of the guest check image you wish to separate into a new check. When you touch the top of the guest check, it will turn green in color. If you are creating more than one additional separate check at the table, touch the top of as many guest check images as desired which have items in the Item Display Area. Touch the Create Check button. Creating separate, new checks at the table may cause guest checks to print, depending on the flag Print On Split Check programmed under Terminal Print Options Check 1 Tab. After the Create Check button is touched, the POS Operator is automatically presented with the End Of Sales Desktop, just as if a Send button had been touched. NOTE: Incorrectly created split checks can be added back together extremely conveniently using the Enable Combine button on the Table List Desktop. Button Type Exit On the Split Check Desktop, this button will return the point-of-sale display to the Sales Desktop on which the Split Check button was touched. 268 POS/2100 Application Programming Odyssey/BackOffice Suite Programming

269 Button Type Print By Seat Check This button will print a single receipt/guest check with subtotals, including tax, for all guest check images on the Split Check screen. These images will be listed by Seat Number. The single guest check WILL NOT be separated into multiple checks. The functionality is for presentation purposes only. NOTE: This button can not be used if there are any new items which have been entered on the guest check during the current service round. Button Type Print Divide Equal This button will present a single guest check, identical to that which is printed when Button Type Print and Send is used from a Sales Desktop, except that separate chits are printed at the bottom of the check. Each chit will contain a separate total, indicating the amount due divided by the entered number of ways to split the amount. If there are items which include a value added tax, the amount of value added tax applicable to each split amount will also print. This button requires that a quantity precede its use, e.g. 3 then Print Divide Equal. If the guest check total was $10.00, then three separate chits will print, with two indicating a total of $2.33 and the third indicating an amount of $3.34. Button Type Print Separate Checks This button will print a separate receipt/ guest check, including tax, for each guest check image on the Split Check screen.. The single guest check WILL NOT be separated into multiple checks. The functionality is for presentation purposes only. NOTE: This button can not be used if there are any new items which have been entered on the guest check during the current service round. Button Type Split Item This button is used to divide a single menu item into fractional parts, each part of which will be automatically moved to a separate guest check image. The guest check images are created automatically, based on the number entered prior to touching Split Item. For example, if two patrons have asked for separate checks, but said Split the bottle of wine between us, all items for the second patron would first be moved to the guest check image indicating 2 of 3. Then the POS Operator would touch the bottle of wine, then touch 2 then touch Split Item. The result of such an operation is illustrated in the screenshot in the first section under Split Check Desktop. You can use Split Item to split ALL items on a single guest check by touching the white area at the bottom of the original image, entering the number of ways to split all items as a quantity, then touching Split Item. Odyssey/BackOffice Suite Programming POS/2100 Application Programming 269