Priced Condiments

Priced condiments are condiments with prices associated with them, and add to the transaction total. For example, adding avocado or bacon to a sandwich might increase the amount due of the order.

Non-Priced Condiments

Non-priced condiments have no prices or a zero price associated with them. There is no charge when these condiments are added to an order. An example of non-priced condiments is the meat temperature instructions rare, medium or well. Condiments such as ketchup, mustard, and mayonnaise are other examples of typical non-priced condiments.

Required Condiments

A selection of a required condiment is mandatory before the menu item is considered complete. Meat temperature in a steak restaurant is often a required condiment because the kitchen must know how the guest wants their steak prepared.

Allowed Condiments

Allowed condiments may be ordered with a menu item, but are not required. Allowed condiments are requests from the guest for a special preparation, addition or removal of an ingredient. A guest may want the sauce for their entrée on the side, may request no tomatoes, or their curry to be mild.

Forced Condiments

Forced condiments are required condiments to which a minimum and maximum number of condiments from the group must be chosen. For example, a banana split requires at least one ice cream flavor, but not more than three.

Default Condiments

Default condiments are condiments which come with a menu item by default. For example, a hamburger might come with lettuce, tomato, and onion. Because the restaurant staff knows what the hamburger comes with, default condiments are usually set to remain hidden when in their default state. Default condiments cannot be voided. Instead, operators interact with default condiments using condiment prefixes such as Add, No, Extra, or Sub (substitute) to indicate the guest’s request (for example, No Onion). Default condiments are typically used in quick service restaurants.

Prefix Condiments

Prefixes change the state of a condiment. Prefix condiments allow operators to interact with both default and non-default condiments. There are seven condiment prefix types:

1. Description: Used to create your own prefixes that describe other condiments. For example, Lite or Extra can be used to describe the amount of sauce or dressing on a menu item.

2. No: Modifies default condiments, overriding a hidden attribute if it exists. For example, all hamburgers come with onions as onions are a default condiment for hamburgers. When the condiment prefix type No is selected followed by onions, onions are no longer hidden and appear as “No onions” on the order.

3. Add: Adds a non-default condiment to the menu item. For example, hamburgers may have default condiments of lettuce, tomato, and onion. Selecting pickles appears as “add pickles” to call attention that it is not normally part of a hamburgers. Using add with a default condiment also increases the quantity of the item. For example, using add with a default condiment of tomato changes the condiment to “2 tomato”.

4. Sub: Substitutes and shows a non-default condiment to indicate it’s replacing a default condiment.

5. Plain: Removes all condiments except default condiments set to persist on plain. For example, applying Plain to a hamburgers removes the lettuce, tomato, and onion, but the hamburgers patty remains if it was set to persist.

6. Reset: Resets a menu item with condiments to its default state with no modifications other than the default condiments.

7. Clear: Removes all quantities of a chosen condiment, and then switches the default condiment to No <condiment>.

Managing Condiment Quantities

The quantity of a condiment added to a menu item can be managed in several ways, depending on business needs. You can set limits on condiment quantities or on the number of condiment group members allowed. See Threshold [1-8] in Configuring Required and Allowed Condiments. The Condiment Order Type also affects how condiment entries are interpreted. See Condiment Order Types in Creating Menu Item Classes for Condiments.

Default Count

Default condiments (configured in Condiment Sets) have a default count of 1. If a quantity greater than one is needed (for example, a hamburger comes with 3 pickle slices), you can change the configured default count. By specifying a default count of 3, 3 pickle slices are added automatically each time a hamburger is added. This quantity can be edited during the ordering process.

Numeric Quantity

A condiment quantity can be entered by using a numeric key and then selecting the condiment from the Condiment Orderer. For example, selecting [5] pickles adds a quantity of 5 pickles to a hamburger.

Update Selected Item Count

If an operator selects a condiment in the check detail area of the workstation, using the Update Selected Item Count function prompts the operator to enter the desired quantity. If an existing quantity is already present (for example, 3 pickles set as a default condiment or previously selected), the pickle quantity changes from 3 to 5. A quantity of zero is not allowed.

Update Selected Item Count, Increment or Decrement

If the Update Selected Item Count function is configured with a “+” or “-” in the button text field in Page Design, the function works as an increment or decrement key. When a condiment is selected in the check detail area, pressing the Update Selected Item Count button increases or decreases the item count by 1. When decrementing the count in this manner, the count can be reduced to zero. The quantity of default condiments can be adjusted using this method only if they are visible in the check detail area (either through a configuration setting or because the default state has been modified).

If you enter a number after the “+” or “-” in the button text field in Page Design, the button increments or decrements the count of the selected item by the specified amount. For example, if text of "+3" is configured, using the Update Selected Item Count button will set the condiment quantity to 3.