When programming a menu for a full service restaurant. We need Sub Modifiers!!
Lets say the Item is Spaghetti that comes with choice of soup or salad.
Right now the modifier has to read: Every kind of soup and every kind of salad option.
It would be nice if a modifier was able to be programed that said "soup" and then "salad".
Then SUB modifiers would come up. IF Salad was selected all the salad dressings would be listed in the sub modifier. If soup was selected all of the soup options would come up in the sub modifier.
Daryl F commented
@feedback4clover:"currently you can create a modifier group called soup and one called salad and attach that to an item (spaghetti), and place the respective options under those modifier groups. Have you tried doing that?"
Suggestion appreciated but that still ignores the entire point of the request. Clearly, the ones within Clover who are suggesting things like this have NEVER worked in a restaurant with a major POS System. Respectfully, that explains why the concept of multi-layered modifiers, and modifiers that are triggered (popping up only IF...) flies clear over the heads of that type of individual.
Nobody has time to scroll endlessly until finally finding the exact modifier in a sea of them. If you're not ordering a baked potato, for example, WHY WHY WHY does it HAVE to show those modifiers?, If instead you're NOT ordering a Salad as the side option, WHY do you need to display all of those salad adds/minuses? It's insane really to think that one must scroll through every possible combination of options in spite of the fact that - in this example - there are only TWO sides that are included with the "meal" combination.
So, to answer: YES we've tried that. We've frankly gotten pretty good at working around many of Clover POS deficits in comparison to the rest of the POS world.
But there's no hiding this extreme deficit. It must be addressed, and soon, especially when the SaaS costs continue to rise regularly.
Daryl F commented
We have competing POS systems that have as many modifier levels you want, and they prompt, and no, it isn't yet another modifier group you have to scroll through, it walks the server through the natural conversational ordering process. One is on Windows, one is on iOS. At this point as we approach 2023, I have to ask the question: is it Android, or is it that Clover just doesn't want to commit the resources to provide this basic functionality for ALL Table Service Restaurants? If you can't do this, how can we honestly claim to compete with the ones that did commit their resources to get it right?
Please PLEASE get this feature worked out!
Gene Brown commented
I don’t think that anyone from the clover design team has ever worked in a large restaurant
This would be huge. Very difficult, almost impossible for a big menu breakfast restaurant with different breakfast sides like toast types, pancake types and way of preperation such as crispy, not toasted and things of the sort....
very needed functionality to get clover to next level.
I agree we need “SMART MODIFIERS” please!
Any reason you can't make an additional modifier that is 'soup or salad' and only have those as the two options linked to Spaghetti?
Example: If you create a Category; Cocktails, then an Item; Menu Cocktails, then a Modifier; Cosmopolitan, we still need one more layer so we can choose the Vodka used; Toto's. We can then create a modifier in the Stock App that will deduct the portion of the bottle used so we can keep greater controls on the amount of product used.
Elliott Forman commented
Clover absolutely needs "smart" modifiers or the ability to modify a modifier in order to participate in the full service space.
Smart modifiers are a MUST if Clover is going to compete in the dining/bar market. There are plenty of systems that support this and Clover needs to figure it out fast. On top of smart/sub modifiers, they need to add buttons for "toppings" that are smart for "No", "Add", "Extra", etc. Setting up multiple tabs for each topping option is clunky and confusing.
George Fischer commented
Provide Sub-Modifiers in Clover Dining
The majority of our menu items have 3+ modifiers as it is. My goal is to keep it as simple as possible to reduce error and confusion. The less tabs the staff has to sort though to place an order the better.
For example: (item) Spaghetti
(Modifier) Meat Choice
(Modifier) Sauce Choice
(modifier) Soup or Salad
(Modifier) Food Prep (this is loaded with SUB, ADD, NO type functions)
(modifier) Cook Temp
(Modifier) Side Choice
(modifier) Soup or Salad
(modifier) Food Prep
Sub-Modifiers would not only be helping when selecting what kind of soup or salad (our customers choose from 2 different soups and 7 different dressings) but if the side is a Baked Potato to have a modifier of Sour Cream or Butter. or if the Side is Pasta a sub-modifier of types of pasta etc.
currently you can create a modifier group called soup and one called salad and attach that to an item (spaghetti), and place the respective options under those modifier groups. Have you tried doing that?