Skip to main content
Mapping modifiers works the same way as regular PMIX mapping. You connect a modifier from your POS to a product or recipe in Garde, then set a scale for how much of that ingredient is used. The difference is that modifiers adjust what’s already on a menu item — they add, remove, or swap ingredients. How modifiers are structured varies between POS systems, so this article covers the general approach.
Why does this matter? If you have an “Add Bacon” modifier on your POS and you don’t map it, Garde won’t know that bacon is being used every time a guest adds it to a burger, salad, or sandwich. That means your theoretical usage of bacon will be too low, and your variance report won’t reflect reality. Map your popular modifiers and you’ll get a much more accurate picture.

​
Where to Map Modifiers

There are two ways to get to your modifiers: Option 1: Click on any menu item to see all its modifier options. Option 2: Scroll down the PMIX mapping menu to find a section listing all your modifiers. Click a modifier to see every parent item it applies to. On either screen, you’ll see the POS button name on the left and the mapped product/recipe on the right.

​
Modifiers That Add Ingredients

To map a modifier that adds a product or recipe, go to the PMIX screen and select the modifier you want to map. In the “mapped to” dropdown, choose the product or recipe that gets added when that modifier is selected. The count by unit will auto-populate. Then set the scale to indicate how much is used. Example: We mapped the recipe “cooked bacon” to the “Add Bacon” modifier. Since the recipe is measured by the piece, we set the scale to 2 — meaning 2 pieces of bacon are used every time someone hits “Add Bacon,” regardless of which menu item they’re customizing.

​
Modifiers That Remove Ingredients

You can also map modifiers that take something away. Select the modifier on the PMIX screen (in this example, “No Bread”). To remove a product from all parent items the modifier affects, enter “removed product” in the product/recipe field and set the scale. In this example, we’re removing a bread bun — and that adjustment applies to any parent item the modifier touches. You can also get more specific. Say you have a “No Cheese” modifier that needs to remove different cheeses from different items. No problem — you can set it to remove cheddar from the cheeseburger, feta from the Greek burger, and mozzarella from the Caprese panini.
When setting the scale for a removed item, don’t use a negative number. Garde handles the subtraction for you.

​
Modifiers with Substitutions

Substitutions are just an add and a remove combined. In the example below, we’re swapping a sesame seed bun for a whole wheat bun across all sandwiches. Since every sandwich uses the same bread, we add “whole wheat bun” and remove “sesame seed bun” in one modifier. What if the substitution removes different items depending on the parent? That works too. Use the bottom view to specify which product gets removed for each specific parent item. If you leave it blank and the “Removed Product” is set in the top view, it’ll assume that product is removed every time the modifier is used. Fill it in for a specific parent item, and it only applies there. Here’s an example of substituting Swiss cheese across three different sandwiches:

​
Scale Override

Sometimes a modifier adds a different quantity depending on which menu item it’s modifying. That’s what Scale Override is for. In this example, a “Rib Combo” can come with 1, 2, or 3 ribs. Scale Override lets you use modifier buttons to reflect the different quantities.
Scale Override only works if the parent button’s scale is set to 1. If you can’t achieve that by mapping a product or recipe directly, you’ll need to create (or modify) a recipe to make it work.