Mode Settings
General
Description – This is the description for the mode.
Screen Description – This is the description for the mode that will appear on the touchscreen.
Mode Type – This field determines whether a mode is applicable for the touchscreen, online ordering, or self service. Modes may be any of the three, but only one of them.
New Order Settings
New Order Dine-In/Out – This field determines whether the system will prompt the user to select Dine-In or Dine-Out at the start of an order.
New Order Customer Type – This field determines if the system will prompt for customer type at the start of an order. This is only applicable if the mode is being used in store mode or if the mode is being used in restaurant modes where the community is not assigning customers to seats. Most communities assign customers to seats, and therefore this is only applicable in store mode.
Table Layout – This field determines if the system will display tables in table area or floor plan layout. By default, tables will display in table area layout.
New Order Order Notes - This field determines if an order notes prompt should be brought up at the start of an order. This field can be prompted for dine-in, dine-out, both, or none. This is rarely used, but when used, it is typically for dine-outs when the user wants to specify a pick-up or delivery time to be printed on the requisition.
New Order Item Scope – This field determines how new order items are generated. If no items are being generated at the start of the order, leave the field as 1 Per Order. If items are being generated at the start of the order, then choose if the item being generated should be 1 Per Order or 1 Per Seat. New order items are typically used for check-in modes or auto-generated a meal item when creating a new order.
New Order Item Quantity – This field is the quantity on items created via the new order item scope and default item. This is defaulted to 1 and for most situations will stay at this value.
Auto Ok When Seats Are Full – This field will automatically press the OK button when all seats for a table have been assigned. This is used for check-in modes and is only applicable when a community is assigning customers to seats. This should not be used for conventional order taking.
Create Quick Buttons Based On – This field determines what quick buttons are displayed when assigning customers to seats. This is only applicable when a community is assigning customers to seats. Quick buttons generate when a customer is assigned to a seat. These quick buttons can be based on sharing an account (meal plan), sharing an apartment, or either option. If a community does not have its couples share a meal plan, it can make sense to set this setting to sharing an apartment. If couples do share a meal plan, the setting of sharing an account will typically meet the needs of the community, which is the default.
Allow Multiple Orders Per Table – This field determines if the community can assign multiple orders to one table. This is used when a community has a ‘revolving door’ situation where multiple groups of residents sit at one table and it is more convenient to start a new order for each new group of customers than to maintain one order with the changing of customers on it.
New Order Number of Customers – This field determines if the new order number of customers field will appear. This is only applicable for dine-outs or dine-ins that do not have a number of seats assigned to a table. This is also only applicable to restaurant mode. For those communities who are assigning customers to seats, this field is typically set to 1 or 2 to handle dine-out situations.
New Order Table – This field determines if a default table will be assigned to an order. This is only applicable to dine-in orders in restaurant mode. If the table should be selected by the user, set this field to Ask. If the mode will be a check-in mode, a ‘check-in’ table can be selected to mark the order as dine-in and not prompt the user to select a table.
New Order Order Name – This field determines if an order name prompt should be brought up at the start of an order. This is rarely used. This is the equivalent of pressing the Name Order button on the main touchscreen display.
New Order Order Owner – This field determines if a new order owner should be prompted at the start of the order. This is rarely used. This would be used in a circumstance where a hostess starts an order and then assigns it to a server as part of the new order process.
Default Item – This field determines what item to create when starting a new order. This field is used in conjunction with new order item scope and new order item quantity to auto-create an item on a new order. This is typically used in check-in modes or to auto-create a meal item at the start of an order.
Default Menu – This field determines if a new menu will automatically appear when starting a new order. This can be used to help direct servers to the correct starting menu or to open up the only menu applicable to a department in store mode.
Same Customer on Multiple Seats – This field determines if the same customer can be assigned to multiple seats on the same order. This is typically set to the default of Allow With Warning, which warns the user that the same customer is assigned multiple times, but does not stop them from processing the order. This warning is to assist users from accidentally charging a resident multiple times for the same meal.
Default Customer – This field determines if a customer should automatically be assigned to the seats of an order in restaurant mode. This is rarely used. Great caution should be used when deciding to use this setting. It is typically used in circumstances where the community has a check-in process and a food order process. The food ordering process may use the default customer so the server doesn’t have to ask for the customer’s name or go through the process of assigning those customers. The drawback to using this method is there is nothing to prevent the user from assigning charges to this default customer and no recourse to finding out who those charges should have gone to. In self-service mode, the system will use the default customer to display a Continue as Guest button and use the default customer as the 'guest' assigned to the seat.
Dine-Out 1 Settings
Dine Out 1 Screen Desc – This field is the description that will display for the first dine-out button. Typical examples may include dine-out, carry-out, pick-up or delivery.
Dine Out 1 Requisition Desc - This field is the description that will display on the requisition. Typical examples may include dine-out, carry-out, pick-up or delivery.
Dine Out 1 New Item Quantity - This field is the quantity on items created via the dine out 1 new order item scope and dine out 1 item. This is defaulted to 1 and for most situations will stay at this value.
Dine Out 1 Item Scope – This field determines how new order items under dine out 1 are generated. If no items are being generated at the start of the order, leave the field as 1 Per Order. If items are being generated at the start of the order, then choose if the item being generated should be 1 Per Order or 1 Per Seat. New order items are typically used for check-in modes or auto-generated a meal item when creating a new order.
Dine Out 1 Item - This field determines what item to create when starting a new order. This field is used in conjunction with dine out 1 item scope and dine out 1 new order item quantity to auto-create an item on a new order. This is typically used in check-in modes or to auto-create a meal item at the start of an order. This can also be used to charge for delivery fees.
Dine-Out 2 Settings
Dine Out 2 Screen Desc – This field is the description that will display for the second dine-out button. Typical examples may include dine-out, carry-out, pick-up or delivery. If a second dine-out option is not desired, leave blank.
Dine Out 2 Requisition Desc - This field is the description that will display on the requisition. Typical examples may include dine-out, carry-out, pick-up or delivery. If a second dine-out option is not desired, leave blank.
Dine Out 2 New Item Quantity - This field is the quantity on items created via the dine out 2 new order item scope and dine out 2 item. This is defaulted to 1 and for most situations will stay at this value.
Dine Out 2 Item Scope – This field determines how new order items under dine out 2 are generated. If no items are being generated at the start of the order, leave the field as 1 Per Order. If items are being generated at the start of the order, then choose if the item being generated should be 1 Per Order or 1 Per Seat. New order items are typically used for check-in modes or auto-generated a meal item when creating a new order.
Dine Out 2 Item - This field determines what item to create when starting a new order. This field is used in conjunction with dine out 2 item scope and dine out 2 new order item quantity to auto-create an item on a new order. This is typically used in check-in modes or to auto-create a meal item at the start of an order. This can also be used to charge for delivery fees.
Close Order Settings
Close Order Auto Action – This field determines what action the system will take when an order is closed. Options include showing the select/start order screen, creating a new order, or logging the current user out. For a typical table-side service, select/start order is typically chosen. For a check-in mode, create new order is typically chosen. Log out is rarely chosen as an option.
Auto Close Order – This field determines if the system should automatically go into the close order screen when the default item is assigned to the order. This is used for check-in modes with the close order button action.
Close Order Button Action – This field determines if the system will take any automatic action when the Close Order button is pressed. This can be triggered by the user pressing the button or by the auto close order setting. Actions include triggering the residents on order button (rarely used), performing a quick split and close (most typically used), or the performing a quick split (rarely used). If a community does not accept other forms of payment, the close order button action of quick split and close can quickly close an order for the user. If other options are available at the close of an order, then the quick split or residents on order button may be utilized.
Confirm Customer Button Display – This field determines what button options display at the confirm customer screen. This is typically set to Assign and Close Only, since the user typically wants to close the check to the customer after they have been selected. If quick split and close is being utilized or the assign and close field is set to no, this field is not applicable.
Customer Assigned to All Checks – This field determines if a customer must be assigned to all checks, including those closed to other forms of payment (cash, check, and credit). This is rarely changed from its default of Never Required, since most communities do not require a customer to be assigned when a cash order is being closed.
Closed Order Actions Interval (Minutes) – This field determines how many minutes back the system will look for closed orders for closed order receipts, reopen orders, and void orders. The maximum this field should be set to is 240 minutes (4 hours). This allows users to see all order from the current meal period, but does not show too many orders to be able to navigate. There might be circumstances where this will be set longer, but this is typically in a store mode situation where there is a smaller number of total orders for the day.
Assign and Close – This field determines if the assign and close dialog should appear. This dialog has the user confirm if they are choosing the correct customer. This dialog will not appear on quick split and close.
Restaurant Mode Sign In Action – This field determines what happens when a user signs in under restaurant mode. This field is not required and will display the select/start order screen by default. Due to this default behavior, it is rarely set. There are also options to automatically start a new order, which can be used for check-in modes.
Store Mode Sign In Action – This field determines what happens when a user signs in under store mode. This field is not required and will do nothing by default. Due to this default behavior, it is rarely set. There are also options to automatically show the select order screen, which can be used to help avoid open orders.
Allow Splitting Check into Multiple Payments – This field determines if a check can be split into multiple forms of payment. If a community wants to allow their user to split a payment between a customer record and cash, this setting can be set to yes. If a community wants to force a check to only be closed to one form of payment, this setting should be set to no.
Tip - This field determines if tipping is applicable to the mode and if so, what tipping rule to use.
Receipt Settings
Print Receipt Mode – This field determines when a receipt should print. Valid options are never, always, on request, prompt user, and use logic below. Never will never print a receipt and users will not have the option to do so on the touchscreen. Always will always print a receipt when the order is closed or through the receipt/closed order receipt buttons. On request will print through the receipt and closed order receipt buttons, but will not print when an order is closed. Prompt user will print through the receipt and closed order receipt buttons, and will also prompt a user if they want a receipt when an order is closed. Use logic below uses information from the auto print settings to determine if a receipt should print when an order is closed. Receipt will print with this setting automatically through the receipt/closed order receipt buttons.
Totals On Receipts – This field determines if a total line appears on receipts. This is only applicable to receipts being printed where the items being displayed are on a plan that is not declining dollar (meals or points). Declining dollar and charge account items will ignore this field and will always print total lines. By default, this field is set to no and should remain that way.
Usage on Receipts – This field determines if plan usage will print in the plan summary section. This field can be useful when used in combination with show plan allowance and show plan remaining balance. This only prints when items applicable to a plan are on the receipt.
Display Comp Pct Total – This field determines if the system will display a line at the bottom of receipts for total comp pct. This is rarely used and should remain on its default of no.
Show One Check Summary – This field determines if an usage summary for each check should be displayed on a receipt when allow multiple checks per receipt is set to yes. This is typically set to no, the default.
Show Plan(s) Allowance – This field determines if plan allowance will print in the plan summary section. This field can be useful when used in combination with usage on receipts and show plan remaining balance. This only prints when items applicable to a plan are on the receipt.
Tax On Receipt Line Item – This field is used to determine if tax should be included on the line item of the receipt or printed as a total tax line at the end of the receipt. By setting this to yes, the system will print a tax inclusive price on the line item by the receipt. By default, this field is set to no and in most circumstances should stay this way, printing pre-tax amounts on the line items and a line for tax with the totals.
Prices on Receipts - This field determines if prices appear on items on receipts. This is only applicable to receipts being printed where the item being printed is on a plan that is not declining dollar (meals or points). Declining dollar and charge account items will ignore this field and will always print prices. By default, this field is set to no and should remain that way.
Show Plan(s) Remaining Balance – This field determines if plan balance/overage will print in the plan summary section. This field can be useful when used in combination with usage on receipts and show plan allowance. This only prints when items applicable to a plan are on the receipt.
Allow Multiple Checks Per Receipt – This field allows the community to have multiple checks print on the same receipt during a quick split and close. This is typically used by communities who want to print one receipt per couple or one receipt for a resident and their guests. The system uses apartment number to determine when customers should be combined onto the same receipt. As part of the quick split and close, the system will determine which customers should have a shared receipt and print out one receipt with each check printed out with its own heading. This option cannot be used with the print receipt mode of use logic below.
Show Period Charge Account Balance – This field determines if the charge account balance for the period appears on receipts when the receipt contains charge account items. This is used by communities who do not have meal plans for their residents or want to display totals for their employees on payroll deduction.
Show Charge Account Usage – This field determines if the charge account usage for the check appears on receipts when the receipt contains charge account items. This is used by communities who do not have meal plans for their residents or want to display totals for their employees on payroll deduction.
Show Plan Details – This field determines if plan details should be printed on a receipt. Plan details include dates of current period and names of customer(s) on the account. This only prints when items applicable to a plan are on the receipt.
Show Plan Remaining Days – This field determines if the number of days remaining in the plan should appear in the plan summary section. This is used by communities where the residents want to know how many days they have left to use the balance remaining on their receipt. This only prints when items applicable to a plan are on the receipt.
Plans to Print on Receipts - This field determines if all plans or only plans applicable to the check print on receipts. The default is to only print plans on a receipt that are applicable to the plan. Some communities may want to show plan balance on all receipts, including times when the plan is not being utilized on the check.
Print Item Quantity on Receipts - This field determines if item's quantity purchased should show up on the printed receipts when the quantity is not equal to 1, 0, or -1.
Requisition Settings
Print Separate Requisitions for Each Seat – This field determines if separate requisitions should be printed for each seat on an order. By default, requisitions print all seats on the order on one ticket. This field is rarely set to yes.
Show Other Printers For This Order on Requisition – This field determines if a note should be placed on the bottom of the requisition to say any other printers this order was printed on. This can be useful in scenarios where an order prints to a hot and cold printer for the cooks/expeditor to be able to put the order together before it goes out to the table.
Print Jobs from Non-FullCount Machines - This field determines if the mode should put orders in the print queue when printing on the device fails.
Automatic Print From Hold – This field determines if automatic print from hold is applicable. Use Item Time indicates that the Hold Time associated with the item should be used. Use Minimum Order Time will use the minimum hold time associated with items on the order.
Payment Settings
Cash Mode – This field determines if cash is an accepted form of payment.
Credit Mode – This field determines if credit cards processed via Axia are an accepted form of payment.
Gift Card Mode - This field determines if gift cards are an accepted form of payment.
Starting Balance Report – This field determines if a starting balance receipt prints by default when setting up a cash drawer balance. This report can also be printed manually, if not selected to print by default.
Open Cash Drawer – This field determines when the cash drawer opens when closing an order. It is set to Other Forms of Payment Only and will typically stay with this default. There may be times when a customer always wants the cash drawer to open, although this is rare, including sales to named customers and then this field should be set to All Checks.
Check Mode – This field determines if check is an accepted form of payment.
External Credit Mode – This field determines if credit cards processed outside of FullCount are an accepted form of payment.
Loyalty Card Mode – This determines if loyalty cards are accepted in this mode. Loyalty cards are a feature used by only one community, so this field should be set to no. Loyalty cards allow a community to honor a buy 5 meals, get one free or otherwise similar set-up.
Use Existing Cash Drawer Balance – This field determines what happens when a user signs in to start the day and there is already an open cash drawer balance. An open cash drawer balance can occur if the machine was shut off incorrectly or the user chose not the balance the cash drawer the night before when shutting down the terminal. The options for this field include always use existing, ask, and never use existing. Always use existing assumes that the user will want to continue to use the cash drawer balance they had previously set up. This is the most common choice. Ask prompts the user if they want to use the open cash drawer balance that they have. Never use existing closes the previous cash drawer balance and prompts the user to start a new one.
Auto Create Drawer Balance – This field will automatically create a drawer balance with a starting balance of 0, if no open balance exists. This should only be used when the community is only accepting credit cards. This should not be used for cash. This allows users to bypass the cash drawer set-up when there is no physical cash drawer.
Customer Field Alerts
Customer Info Name Seats – This field determines if a customer confirmation dialog should appear when assigning customers to seats. If a community is utilizing pictures, this field is typically set to yes. Otherwise, it is typically set to no because users will be able to see the name on the seat list.
Date Alerts – This field determines if a customer confirmation dialog should appear when there are date alerts associated with the customer when assigning customers to seats. If the community has date alerts (birthday, anniversary), this field is typically set to yes to tell the user about the alert.
Text Alerts – This field determines if a customer confirmation dialog should appear when there are text alerts associated with the customer when assigning customers to seats. If the community has text alerts (dining requests, allergies), this field is typically set to yes to tell the user about the alert.
Balance Alerts – This field determines if a customer confirmation dialog should appear when there are balance alerts associated with the customer when assigning customers to seats. If the community has balance alerts (overage, within X of balance), this field is typically set to yes to tell the user about the alert.
Search Options
Search by Apartment – This setting determines if apartment should be included in the search criteria when a user searches for customer information.
Search by Name – This setting determines if customer name should be included in the search criteria when a user searches for customer information. If this field is set to yes, customer name search options is applicable.
Search by Customer Id – This setting determines if customer id should be included in the search criteria when a user searches for customer information. By default, this is set to no since most users do not know a customer’s customer id.
Customer Name Search Options – This setting determines whether searches on customer name should be based on first and last name or last name only. This is only applicable if search by name is set to yes.
Other
Notes on Items – This field determines if order item notes display in parenthesis next to the item on the order summary. This is helpful for servers to see that the note they typed in is associated with the correct item. This field is typically set to yes for all new installs, although some old installs may have this set to no.
Print Customer Balance – This field determines if a customer balance should automatically print on the receipt printer when looked up on the touchscreen terminal. If this field is set to no, there will be a print button on the screen for users to manually print the balance. Unless a community requests the information to print each time, set this field to no.
Show Own All Orders – This field determines what orders should display on the select/start order screen when the user has the ability to see all orders. When set to show own, users only see their own orders when the screen is brought up and can see all orders via a show all orders button. When set to show all, users see all orders when the screen is brought up and can see their own orders via a show own orders button.
Auto Action From Send Order – This field determines any additional actions that occur when a user sends an order to the kitchen. If no additional options are desired, leave this field blank. This field is typically used for to-go orders where the order can be closed as soon as the items are sent to the kitchen. This should not be used for table-side ordering. Options include split order, close order, quick split and close, and create new order. Split order brings users to the split order screen. Close order brings users to the close order screen. Quick split and close performs a quick split and close. New order leaves the existing order unclosed and creates a new order.
Item Description Automatically Populated on Transaction Description – This field determines if the transaction description should be populated with the item’s description when closing the order. This field is rarely set to yes. This field was created for a community who wanted transaction description included as part of their billing file. In certain departments, they wanted the transaction description to be the item description, but in other departments they only wanted a description if the user typed one in.
TouchScreen (TS) Mode – This setting overrides the department level setting for type of mode. This setting is rarely used and should remain blank in most circumstances. The only situation where this field is currently being used is a health center dining room department that has a traditional table side service and uses the tablets to take orders in a more stream-lined manner. The department is set up in restaurant mode, but several of the modes for the department are set up as process.
Modifiers on Items – This field determines if order item modifiers display in parenthesis next to the item on the order summary. This is helpful for servers to see that the modifiers they selected are associated with the correct item. This field is typically set to yes for all new installs, although some old installs may have this set to no.
Show Hold Warning – This field determines if a warning message should appear if some items on an order are placed on hold and others are not. Hold order is rarely used by communities and a warning about hold state would be used even less than that. This field should be kept at its default of no.
Transfer Enabled – This field determines if orders can be transferred in this mode. Transfer order is rarely used by communities and should stay at the default of no.
User Sign Out Check – Determines if a user should be warned of open orders when they go to sign out. Options include:
Pole Display Enabled – This functionality is not yet available.
Order Name Automatically Populated on Transaction Description – This field determines if the order name should be populated with the item’s description when closing the order. This field is rarely set to yes. This field was created for a community who wanted transaction description included as part of their billing file. In certain departments, they wanted the order name to be the item description.
Notes Delimiter – This field determines what delimiter to use for separating notes when multiple notes buttons are selected on the touchscreen.
Item Notes Allowed in Store Mode - This field determines whether the special notes button should appear in store mode.
Prompt for Reason on Item Comp Percentage - This field determines if the prompt for transaction description dialog should appear after an item comp pct or item comp pct by seat is performed. This should be utilized when communities want to know the reason why an item is being comped.
Display Price on Choice List Items - This field determines if prices are displayed on choice list items when the price of the choice list item is not zero.
Allow Unclosed Orders When Exiting - This field determines if users are allowed to exit and/or close the drawer balance when open orders exist in the department.
Auto Print Settings
These settings are only applicable when use logic below is selected for print receipt mode.
Print When Cash – A receipt will print when cash is a form of payment on the check.
Print When Internal Credit Card – A receipt will print when a credit card processed by Axia is a form of payment on the check.
Print When Gift Card – A receipt will print when gift card is a form of payment on the check.
Print When Daily Overage – A receipt will print when the meal plan on the check is a 24 plan and the user has exceeded their balance for the day.
Print When Charge Account – A receipt will print when any items on the receipt fall under the customer’s charge account.
Print When Check – A receipt will print when check is a form of payment on the check.
Print When External Credit Card – A receipt will print when a credit card processed outside of FullCount is a form of payment on the check.
Print When Period Overage – A receipt will print when the user has exceeded their balance for the period/has an overage.
Print When Allowance – A receipt will print when any items on the check fall under the customer’s plan.
Print When Dine-In – A receipt will print when the order is dine-in.
Print When Dine-Out 1 – A receipt will print when the order is dine-out 1.
Print When Dine-Out 2 – A receipt will print when the order is dine-out 2.
Self Ordering Settings
Requisition Timing – How requisitions should be handled for online ordering. Can be set to one of the following:
Allow Customer Based On – Tells the system which users to create ‘quick’ buttons for
Printed Menu Text – Should the printed menu text from the items page be displayed
Dine In Allowed - This determines whether a dine-in option should be displayed.
Dine In Alias – What dine-in is called, if allowed
Dine In Time Text – What text will appear when the user selects a time for dine-in
Requisition Time of Day - Only appears if "Requisition - Time of Day" is selected for Online Ordering Output. Determines what time of day the requisitions are printed for Dine in.
Requisition Lead Time - Only appears if "Requisition - Lead Time" is selected for Online Ordering Output. Requisitions will be printed this many minutes before the customer's requested time for Dine in.
Carry Out Allowed -This determines whether a carry out option should be displayed.
Carry Out Alias – What carry out is called, if allowed
Carry Out Text – What text will appear when the user selects a time for carry out
Requisition Time of Day - Only appears if "Requisition - Time of Day" is selected for Online Ordering Output. Determines what time of day the requisitions are printed for Carry Out.
Requisition Lead Time - Only appears if "Requisition - Lead Time" is selected for Online Ordering Output. Requisitions will be printed this many minutes before the customer's requested time for Carry Out.
Delivery Allowed - This determines whether a delivery option should be displayed.
Delivery Alias – What delivery is called, if allowed
Delivery Text – What text will appear when the user selects a time for delivery
Requisition Time of Day - Only appears if "Requisition - Time of Day" is selected for Online Ordering Output. Determines what time of day the requisitions are printed for Delivery.
Requisition Lead Time - Only appears if "Requisition - Lead Time" is selected for Online Ordering Output. Requisitions will be printed this many minutes before the customer's requested time for Delivery.
Add Customers Text – What text will appear to the users when they are adding customers to the order. Text should include information on adding customers to the order, as well as a note that clicking on a customer removes them from the order. For example, 'Please add your customers to the order. To remove a customer from the order that was added incorrectly, click on the person's name to remove.'
Minimum Minutes in Future – The minimum number of minutes that users can create orders for. For example users can place orders for 15 minutes or more in the future.
Ask Customer for Special Requests – Prompts the customer with a input field for special requests for Online Ordering and Self-Service mode when adding items to their cart.
Hide Item Prices – Prompts the customer with a input field for special requests for Online Ordering and Self-Service mode when adding items to their cart.
Party Size Limit - Limits the party size of an online order to the specified number.
Low Item Countdown Behavior - Controls if the customer can add a item to their order if the item is configured to use item countdown. This will allow the system to block the user when the current item countdown value is less than the warning amount. This will also allow items with a current countdown amount to be hidden from the menu after the item reaches a lesser amount than the warning amount.
No Item Countdown Behavior - Controls if the customer can add a item to their order if the item is configured to use item countdown. This will allow the system to block the user when the current item countdown value is 0. This will also allow items with a current countdown amount to be hidden from the menu after the item reaches 0.
Mode Gift Card Types
This is only applicable when gift cards are licensed. This table specifies which type of gift cards are accepted for this mode.
Department Modes
This table duplicates what is under the department details page and allows the user to assign departments to a mode from the modes page instead of needing to go to the departments page
Automatic Comp Percent
This table enables percentage discounts for a certain customer type for items. The percent value must be between 0 and 100.