Modifications To Existing Laravel Backend (Front End Script Is Flutter)

We have an existing Multi Restaurant - Food Delivery App with Laravel Admin and Restaurant Panel. Script is in Flutter and Backend is in Laravel. We are developing a new front end in Adobe XD which will be exported into Flutter which must work with these modifications to the backend. Now we want to modify it's structure a bit as per our requirements. This project is Step 1 of many to come. Here's the Admin panel of the purchased script: [login to view URL] Cuisines & Categories The Cuisine & Categories Type would help customers search for their choice of food. They would act as tags so customers can use terms that fit the description of type of cuisine they are looking to order. These can be applied to Food Items individually. Menu Categories -Menu Categories (this would need to be added) organize the food items into categories on the menu set by the restaurant. The Menu Categories should allow users to organize the order they want them displayed. Food Items -Food Items should be organized by the user with drag & drop functions to organize the order they want them displayed. Dietary Groups -Dietary Groups with a pre-populated list we generate in the back end. These can be applied to Food Items, and there is no limit to how many they can add. The Admin should be able to edit this list at any time. (Example: Vegetarian, Vegan, KETO, Halal, etc) These Would Be Represented On The Menu With Images/Symbols That Can Pop-Up. Customers can use filters/search as per their needs. Add Ingredient Modifiers With Auto-Populating Descriptions -Allow "Ingredients" (this feature would need to be added) that would allow the user (the restaurant) to input & list the ingredients to their individual Food items. These ingredients would be used in 2 ways: -Auto populate the Food Items description (Example: The Item Would Be a Cheese Burger, and the Restaurant would input the ingredients. These ingredients would populate in the description of the item as "[ingredient1], [ingredient2] &[ingredient3]" plus option to enter in a generic script and the ability for user to edit.). -Customer would be able to uncheck these ingredients to not include them on their food order. Example, if the customer unchecks "Onions" the ingredient would display "NO Onions". "Attributes" Changed To "Options" -Currently there is "Attributes" which would allow users to input variations to items (Size, exe). This would be changed to "Options". Options Should Be Able To Be Applied To Multiple Menu Items -Options should be able to apply to multiple items. Like Size, instead of just storing the heading "Size" we would want to have the Options be applicable to multiple items (Small +$1, Medium +$2, Large +$3 would apply to a variety of items, so rather than rein-putting them each time it can be set across the board for many items.). Currently, all variations are stored in the individual item, which is what we don't want. Minimum & Maximum Input For Options -These should allow input of minimum and maximum values (Example, some Options would have 1 minimum and 1 maximum -making them mandatory- but an Option for "Choose Up To 3 Types Of Cheese" Would have 0 minimum and 3 maximum). These should also allow to choose multiple options from a group of attributes. Add-On Groups -Currently the Add-Ons just are attributed to items randomly. We would need them to be grouped to organize selections better. Example: Instead of just having the add-on "Cheddar" the add-on would need to be in a group with other cheeses called "Cheese". Food Bundles (Combos, etc) -Finally we would want Food Bundles allowing restaurants to create and add combinations of foods at a discount, for example when ordering a burger you can create a Food Bundle that includes Fries and a Drink at a discount (% or $) We have a presentation outlining the desired workflow made in Adobe XD available upon request to help understand the scope of the project.