Tracking Modifiers in API based POS Systems

Setting up and tracking modifiers from your API POS system can be supported by Decision Logic in one of two ways:

 

Scenario #1
Cheeseburger
1x Mod - Bun
1x Mod - Patty
1x Mod - slice of cheese

When setting this item up in Decision Logic the Cheeseburger recipe would be empty. Setting up the mods as "DL MenuItems", you would include the ingredients in each mod.

When NO slice of cheese is requested, the POS data will look like this.
Cheeseburger
1x Mod - Bun
1x Mod - Patty

This will NOT deplete the "slice of cheese" in DL. But there is no data for "NO Slice of cheese" in Decision Logic.

 

Scenario#2
Cheeseburger
1x Mod - Bun
1x Mod - Patty

When you set this up in Decision Logic cheeseburger recipe will have 1x "slice of cheese" ingredient.

Setting up the mods as "Decision Logic MenuItems", you would include the ingredients in each mode.

When a NO "slice of cheese" is requested, the POS data will look like this.

Cheeseburger
1x Mod - Bun
1x Mod - Patty
1x NO Mod - Slice of Cheeseburger

 

We do get data for the NO mod, and typically we import this as a negative POS ID if “NO” is used as a pre-modifier. Otherwise, this “No” option needs its own PLU assigned in the Point of Sale.

So if regular mod "slice of cheese" is posID=12345 the NO "slice of cheese" is -12345.

For additional questions or assistance, please submit a support ticket by visiting the Decision Logic Service Center.

 



If you'd like to receive news on software releases and product updates, please sign up for our email list.