Condiment Prefixes

Prefixes change the state of a condiment. Many restaurants allow workstation operators to modify menu items, such as adding, removing, increasing and decreasing the number of condiments on the item. Operators can add prefixes (for example, No, Add, Extra) that appear before the condiment on the guest check, order devices, and customer receipts. This provides helpful preparation instructions to the kitchen staff and eliminates order confusion.

Condiment prefixes use the same print class as the condiment they are modifying.

Apply Negative Condiment Price with No and Plain Condiment Prefixes

Some restaurants want to credit a transaction when they remove something that normally comes on an item, like taking tomato off a burger. This feature lets you adjust the transaction total automatically when default condiments are reduced or removed using the No or Plain condiment prefix.

This feature requires the use of Enhanced Condiment Prefixes enabled through menu item class option 65 – Support Enhanced Prefix Mode (Parent Only). It uses the Prefix Level Override setting in the menu item definition and requires a non-zero price for the condiment at the price level specified by the No or Plain prefix. If no price exists on the specified level or the price is zero, the condiment is removed with no price adjustment.

As some or all of a default condiment are removed, the system applies a negative price to update the condiment line total. Depending on how the condiment is priced, the amount shown may be a negative value (a credit) or the net remaining value after the removed quantity is deducted. The price reduction is possible even if the default condiment is initially unpriced. The updated amount appears on the guest check, customer receipt, customer display, and in the journal. It appears in the kitchen only if your configuration is set up to print prices (not typical).

To protect against pricing mistakes, the system includes a guardrail for No and Plain prefix deductions. If removing default condiments would reduce the net value of the menu item (including its condiments) below zero, the system blocks the change and shows an error.

Example: A burger costs 4.00, but removing bacon would deduct 5.00. Because the net value would be negative, the deduction isn’t allowed.

If this happens, review the deduction values tied to the No or Plain prefix (including the price level used by Prefix Level Override) and adjust pricing so the maximum possible deduction can’t exceed the item’s value.

Negative Condiment Pricing Example

The condiment line in the check detail area shows the net change for the adjustment as the quantity of a default condiment is adjusted using the No or Plain prefix.

In the following example, Burger includes 3 Tomato by default. Tomato has a price of 0.05 active on the level specified by the No prefix.


                    Default (no change) 
                    
                    1 Burger       7.00
                    3 Tomato
                    
                    Remove 1 tomato (3 → 2) 
                    
                    1 Burger       7.00 
                    2 Tomato  -0.05
                    
                    Remove 2 tomatoes (3 → 1) 
                    
                    1 Burger       7.00
                    1 Tomato  -0.10
                    
                    Remove all tomatoes (3 → 0) 
                    
                    1 Burger       7.00
                    No Tomato -0.15