What would it take to change the way options are managed in the database?
I have options that have menu item records as well. They are options that can go on a plate of food. The current display of menu items in the cart does not lend itself to a clear understanding of what menu items are supposed to go on one plate. As such, I have worked around this limitation by making a menu item that is essentially one person’s choices of what they want on their plate. That menu item includes options for meat choice, sides choice, bread choice, condiment choices and sauce choice.
This method of presenting to the user the various “optional” items that can be placed on their plate of food makes the display in the cart more clear. TI works as long as I don’t actually run out of something.
The current menu options management system breaks down when I do run out of an item, i.e. I run out of Mac & Cheese. I can make the menu item, Mac & Cheese, not show on the menu page if I change the quantity to -1. However the menu item options where I have added the Side option of Mac & Cheese still shows Mac & Cheese as an option that the user can select. Even if I change the quantity of the option to -1.
Additionally, I would have to change the quantity of the option to -1 on all my menu items where that option is in the list of options. That is too time consuming.
If the options management system used menu items from a category called Options then I could have only one place to add the options and I could manage the availability much easier. I could change the quantity to -1 and thereby make that “option” not available for display to the user.