11-17-2024 06:31 PM
I am a Multi-Location Management (MLM) user.
I have successfully created a new version of my Menu for another location.
Now I want to add a new "Menu Group" to both locations.
https://doc.toasttab.com/doc/platformguide/versioningAtTheMenuGroupAndModifierGroupLevel.html
Here's my issue:
1. Create a new "Menu Group" in Location-A's Menu.
2. Create a version of that new "Menu Group" and target Location-B.
3. The new "Menu Group" is created, but does not appear on Location-B's Menu. The menu group is essentially orphaned.
Am I missing something?
Thanks for any advice or suggestions!
Solved! Go to Solution.
11-18-2024 06:32 PM
MLM versioning is tough. When it comes to versioning an entity, keep in mind that EVERY change within a version of a menu entity will only ever be seen by that version's target.
If Location A has a menu, and that menu's target is Location A only, then Location B will never see any groups you add to Location A's version of that menu. Even if you target that newly created group to Location B, it still only exists in Location A's version. Kind of silly, but you get the hang of it. Essentially, once you make a version of an entity, it needs to be modified within that version; not any parent/parallel versions.
Because of this, first make sure your restaurant group structure is set up and nested properly. My general rule of thumb is to always work in the highest level version of a menu entity as much as possible (hence, the "Parent" version for the entire restaurant group), and only ever version something out at the lowest required level. Generally speaking, the fewer versions of anything that you have to deal with, the better. Secondly, when you start to play around with versions, you pretty much always want to be working in the "Advanced Properties" page so you can make sure you're catching all the changes you need to make.
I can help you with your setup, but could you give a little more info about why you're looking to version out your menus for these two locations? The more reasons you can think of, the better! (Just for an example: It could be that you didn't need to version your menu, but rather just your menu groups. Or it could be that you don't need to version anything at all, but rather just create a copy and re-target that copy).
Feel free to shoot me a DM too.
11-18-2024 05:42 PM
Is the "owner" of the Menu Group the MLM? You may have it set to being Location-A which will make it that location specific.
11-18-2024 06:32 PM
MLM versioning is tough. When it comes to versioning an entity, keep in mind that EVERY change within a version of a menu entity will only ever be seen by that version's target.
If Location A has a menu, and that menu's target is Location A only, then Location B will never see any groups you add to Location A's version of that menu. Even if you target that newly created group to Location B, it still only exists in Location A's version. Kind of silly, but you get the hang of it. Essentially, once you make a version of an entity, it needs to be modified within that version; not any parent/parallel versions.
Because of this, first make sure your restaurant group structure is set up and nested properly. My general rule of thumb is to always work in the highest level version of a menu entity as much as possible (hence, the "Parent" version for the entire restaurant group), and only ever version something out at the lowest required level. Generally speaking, the fewer versions of anything that you have to deal with, the better. Secondly, when you start to play around with versions, you pretty much always want to be working in the "Advanced Properties" page so you can make sure you're catching all the changes you need to make.
I can help you with your setup, but could you give a little more info about why you're looking to version out your menus for these two locations? The more reasons you can think of, the better! (Just for an example: It could be that you didn't need to version your menu, but rather just your menu groups. Or it could be that you don't need to version anything at all, but rather just create a copy and re-target that copy).
Feel free to shoot me a DM too.
11-19-2024 04:11 AM
Hi @caffie when I created a new version of the Menu Group, I set the Location as the Owner and unfortunately it did not add itself to the Menu. It just appears orphaned from everything. I appreciate the suggestion.
Hi @nbunda Thanks for the suggestions! We initially setup Versions because different regions would sell slightly different products. We now are looking to reorganize our menu. I noticed that the Menu Groups prior to Versioning are shared, but subsequent ones are not. I just wish there was a way to add a new Menu Group that could still be shared.
We might just look into using different Menu Groups that target specific Location Groups. That method does seem to be more straight forward. Thanks again!
11-20-2024 05:00 PM
Hi @www!
We operate in three different states, each with slightly different menu items. However, the overall menus and menu groups are consistent across all 25 locations. Do you have a location group (restaurant group) that includes all of your locations?
We have a location group called the Egg Harbor Cafe Management Group, which includes all our locations and groups. The target and ownership of our menus and menu groups are set to the Egg Harbor Management group so that all locations have the same menus and groups without having to make copies. We also have location groups created specifically for Illinois and Georgia since we sell slightly different items in those states. For example in Georgia we sell a Chicken & waffle, but we make sure the item itself if targeted to the Georgia group only so that our IL and WI locations do not see this item on their menu.
Below is a preview of our set up:
Menus:
Menu Groups:
Items: