Multi-Unit PMIX Copy Tool

Overview

The Multi-Unit PMIX Copying feature allows users to copy PMIX mappings from one source location to multiple destination locations that use the same POS system within the same company and concept in MarginEdge.

This feature is perfect for multi-unit groups that have the same menu and POS across many locations. It is not designed for groups that have differently named menus/menu items.

There's a video overview, a thorough "Table of Contents" with links directly to what you may need, and FAQs + Troubleshooting at the end! 

"

Table of Contents

• How it works
• How to copy mappings
• Key Features
  • Summary Email
    • Spreadsheets in the Summary Email
    • Error Reasons
  • Copy History/Auditing
  • Revert Feature
• Limitations
  • Exact Matching
  • Unmapping
• FAQs
  • Who can use this feature?
  • Can a copy be reverted/undone?
  • Will this work with my POS?
  • Will the feature automatically sync mappings between my locations?
  • What happens if I have two POS buttons with the exact same name?
  • Will this copy everything over? Or only the most recent changes?
  • Will this copy over mappings from my unsold items? (like an upcoming seasonal menu that hasn't yet been sold)
  • Will this unmap anything in the destination locations?
  • How far back does it copy?
  • How does this feature handle Scale Overrides for modifiers?
• Troubleshooting
  • I don't see my location in the location selection list
  • What does this error mean?
  • Why didn't my mapping copy over?

How it Works

The copy function works by comparing the combination of Major, Minor, and Item Names (ignoring capitalization) between the source and destination locations. If these items match exactly across locations, then the copying process can proceed.

The combination of all three values need to be the same in all locations in order for the copying to succeed

How to Copy Mappings

1. Setup your “Source” Location

   • You start by selecting a source location where you can make changes to the menu item mappings. This location will be the the “source of truth” which will be copied to the other locations.
   • It's important to save any changes you’ve made to mappings before initiating the copy process.
     
      

2. Click “Copy to…” and Select “Destination” Locations

   • The copy process allows you to select multiple locations within the same company and concept.
   • Locations from different concepts won't appear (because menus will not be the same across concepts).
   • Destination locations show which can receive mappings. Some may have warnings indicating that they already have PMIX mappings completed.
     
      

3. Select the Copy Option

   • Copy and overwrite: This option will replace any existing data in the destination locations with the data from the source unit. This is the default option.
   • Only copy where missing: This option only adds mappings to menu items that do not already have mappings, leaving any existing mappings intact.
   • Note that warnings will only appear if “Copy and overwrite” is selected. (Warnings will not be present if “Only copy where missing” is selected.)
     
      

4. Review and Submission

   • Before finalizing, a review screen shows the selected units, with warnings about potential data overwriting (if you’re copying and overwriting).
     
   • Once submitted, the copying process will run in the background, and an email will be sent to the user who initiated the copy when it's complete.
     
      

5. Email Notifications

   • After the process completes, the user who kicked off the copy will receive a detailed summary email, including information about the source location, destination units, and CSVs outlining what was copied over.

While the copy process is running, users will be unable to make changes to the PMIX mappings for all locations involved in the ongoing copy process. The “Save” button and “Copy to…” buttons will be disabled while the copy process is ongoing. 

PMIX Mapping changes will be disabled in the source location while the copy process is underway.
 

PMIX Mapping changes will be disabled in all of the destination locations while the copy process is underway.

Key Features

Summary Email

A summary email will be sent to the user who initiated the copying process. The email includes details about when the copy process started, who initiated it, which source location was used, as well as the destination location(s) that received the mappings.

The email includes CSV attachments that provide detailed reports on which mappings were copied successfully and which ones were skipped, as well as the reasons for why they were skipped (e.g., item name mismatch, conflicting mappings).

Spreadsheets in the Summary Email

There are two CSV files that are attached to the Summary email:

1. Menu Item Mappings Copied
   • This CSV lists all the menu items and modifiers a copy was attempted. It will indicate whether the copy was successful or not for each item (and the reason it errored if it wasn’t successful).
2. Modifier Details Copied
   • This CSV lists all the scale override details for modifiers that have specific scales depending on the item it’s modifying (example: having a larger “Scale” of milk for a cappuccino than a macchiato).

The source location will be included in the name of the CSV file. Each destination location will have its own column in the CSV that indicates whether an item was successfully copied or not. 

If you have questions, or need help with resolving errors from the PMIX copying, then please reach out to help@marginedge.com (and please provide them with the CSVs from the Summary Email!).

Error Reasons

Below is a list of each error message that could appear in the CSV along with what the error means/how to resolve it. After fixing the underlying issue, you will need to use the “Copy to…” action again to copy the mappings to any destination location that previously had the error.

Item not found

This means that the menu item (or modifier) that you are trying to copy from the source location was not found in the destination location. If the name of the menu item/modifier is not an exact match between the source location and the destination location then it’s considered “not found”.

Reasons why an item would be considered not an “exact match”:

• The menu item/modifier has slightly different wording (example: “large latte” vs. “latte large”)
• The menu item/modifier has punctuation in one location but not the other (example: “latte” vs. “latte.”)
• The menu item/modifier has a different Major/Minor (i.e., is under a different menu group) (example: Lunch > Cheeseburger vs. Dinner > Cheeseburger)
• Scenarios where mappings will not be copied due to not having exact match:
  

Resolution

In order to resolve this, we recommend ensuring your POS menu structure/POS buttons are identical across your locations.

Two or more versions of this item have different mappings in source location

If you have two menu items or modifiers with the exact same Major/Minor/Item Name combination then you will encounter this error if the different buttons have different (conflicting) mappings.

This is most common for modifiers since often there are multiple modifier buttons in the POS that have the same name.

Resolution

To resolve this, we recommend assigning the same mapping to all versions of the duplicated item (meaning same Recipe/Product and same Scale). Make sure you filter your results to "All items" on the PMIX Mapping page as there could be some hidden mappings (outside of the date range) that also have the same name that might trigger this error.

You can still click on a modifier and set unique Scale Overrides if you need different scales for specific combinations of modifier/item it’s modifying (example: larger scale of a modifier when it’s modifying a Catering menu item).

If you truly need different mappings for the different versions of the item then we recommend changing the name of one of the buttons in the POS to make them unique.

Recipe is restricted and not available at this location

Permissions/settings currently block this recipe from the destination location. Enable access or sharing for the recipe to this destination location, then try again.

This combination of modifier and the menu item it’s modifying can’t be found in the destination location

This combination of modifier and menu item (the item that it’s modifying) doesn’t exist at the destination - likely because that combination has not yet been sold.

Already has a mapping. Skipping because copy setting is for only copy where missing

There is already a mapping at the destination, and the copy setting was set to “Only where missing” - meaning only copy over the mapping if there’s not already a mapping there.
No action needed, unless you want to overwrite existing mappings.

Recipe not found / Product not found

The mapped recipe or product does not exist at the destination location. 
Verify that the recipe still exists and that the destination location has access, then re-run the mapping copy.

Recipe mapped as the default 'Removed Recipe' on the modifier cannot be found

You’re subtracting a recipe as part of the modifier, but that recipe cannot be found in the destination location. 
Verify that the recipe still exists and that the destination location has access, then re-run the mapping copy.

Recipe/Product mapped as the 'Removed Product' cannot be found in destination location

The recipe or product for a removed/negative/subtract mapping specifically for this combination of modifier and menu item (the item it’s modifying) cannot be found in the destination location. 
Verify that the recipe still exists and that the destination location has access, then re-run the mapping copy.

Copy History/Auditing

At the bottom right of the screen there is a “History” button that maintains a history log of all copy actions, including the source unit, destination units, who initiated the copy action, and when the event occured. 

Hovering over the Destination value will show a list of all destination locations involved in the copy action.

Revert Feature

If you’ve done a copy action and realize that you need to “undo”, then a MarginEdge staff member can revert back to the mappings that were in place right before the last copy action. This is a “point in time” revert, meaning any manual PMIX mapping changes made after the last copy action will also be undone.

We can only revert back the most recent copy action in a destination location.

To request a revert of a copy action, please reach out to help@marginedge.com and inform us of which unit(s) you need reverted.

Limitations

Exact Matching

This feature works by comparing the combination of the Major, Minor, and Item Name from one location to another. This means that your menus and menu items need to have the exact same names across locations in order for this feature to successfully copy mappings. Capitalization doesn’t affect the matching process.

Examples:

Unmapping

This feature does not unmap menu items in the destination locations.

Example: If the source location has “Cheeseburger” unmapped and the destination location has “Cheeseburger” mapped, then this feature will not unmap the Cheeseburger in the destination location to match the source location.

FAQs 

Who can use this feature?

Any user who has access to the PMIX Mapping page will be able to use the “Copy to…” feature.

The list of destination locations that they can copy mappings to will be limited to locations where they have access to the PMIX Mapping page.

Reminder that only locations within the same company and concept will be able to be selected when copying mappings to other locations.

For a list of user roles that have access to the PMIX Mapping page, please refer to our User Permissions help article.

Can a copy be reverted/undone?

Yes! We can undo the most recent copy action in a destination unit.

For more information, please see the Revert Feature section.

To request a revert of a copy action, please reach out to help@marginedge.com and inform us of which unit(s) you need reverted.

Will this work with my POS?

That depends! This feature should work as long as you have the same menu across your locations, regardless of your POS.

This feature is not limited to specific POS systems.

Will the feature automatically sync mappings between my locations?

No, this feature is a one-time copy action. Changes made in the source location will not automatically propagate to the destination locations in the future. However, you can use the copy action each time you make a change in your source location to copy the mappings to the other locations.

What happens if I have two POS buttons with the exact same name?

That depends on how they are mapped!

If items with the same Major/Minor/Item Name have the exact same mapping (Recipe/Product and Scale) then the feature will copy the mapping over! Alternatively, if some of the items with the same name have the same mapping and some are unmapped then the feature will copy the mapping over!

If the items do not have the same mapping then the feature will not copy the mapping over. You will see an error message in the CSV that says “Two or more versions of this this item have different mappings in the source location”. For more information on that error message please see the Error Reasons section.

Will this copy everything over? Or only the most recent changes?

This feature will copy all mappings over, not just the most recent changes.

Will this copy over mappings from my unsold items? (like an upcoming seasonal menu that hasn't yet been sold)

Yes! This feature will copy over all mappings regardless of whether the menu item has been sold in the POS or not. This means even seasonal items that have not yet been sold will be copied over to the other locations as long as the seasonal item exists in the destination location and has a mapping in the source location.

Note: To see your unsold items, change the “View” filter to show “All items”

Will this unmap anything in the destination locations?

No. Currently this feature does not unmap menu items in the destination locations (even if you select “Copy and overwrite”).

The exception is for Scale Overrides on modifiers. For more information on this please see the How does this feature handle Scale Overrides for modifiers? section of the FAQ.

How far back does it copy?

This feature will copy all mappings from your source location, regardless of timeframe. Even items that are under the “All Items” view (not just the “Sold Items”) will have their mappings copied over.

How does this feature handle Scale Overrides for modifiers?

Scale overrides are used when you need to indicate that more of a modifier is needed for certain menu items that it’s modifying (see example below for more almond milk being needed for certain drinks).

When copying mappings over using this feature, the Scale Overrides will also be copied over as long as the combination of modifier + menu item can be found in the destination location.

If that specific combination (example: “latte - large” -> “almond milk”) has not been sold in the destination location then the scale override will not be copied over (error message will say “This combination of modifier and the menu item it’s modifying can’t be found in the destination location”).

Unmapping/removing scale overrides during the copy process

(Only if using “Copy and overwrite” setting) 
If a destination location has a modifier with scale overrides and the “default mapping” of that modifier changes during the copy process, then the old scale overrides will be completely removed/unmapped.

This is because the “old” scale overrides were specific to the “old” default mapping. A new default mapping means that the “old” scale overrides will no longer be applicable.

In the above scenario, all of the “old” scale overrides will be removed (note: the CSV will say “Mapping Reset. If the source location had scale overrides specified then those will be copied over to the destination location.

If the “default mapping” does not change in the destination location, then the scale overrides will not be removed/unmapped. If the source location had scale overrides specified the those will still overwrite the existing scale overrides in the destination location. 

Troubleshooting

If you have questions, or need help with fixing errors from the PMIX copying, then please reach out to help@marginedge.com (and please provide them with the CSVs from the Summary Email!).

I don't see my location in the location selection list

There are a few reasons why you might not see some locations listed in the “Copy to…” feature screen.

Is that location part of the same Concept within MarginEdge?

• Only locations that are part of the same concept within MarginEdge can copy PMIX mappings between them.
• If they’re not part of the same concept then they likely don’t have the same menu (which means this feature would not be able to successfully copy mappings over).

Do you have access to the PMIX Mapping page for that location?

• Only users who have access to the PMIX Mapping page for that location can copy mappings to that location. Just granting access to the location is not sufficient - the user must have access to the PMIX Mapping page as well.
• Please work with your MarginEdge admin to adjust permissions if you don’t have access to the PMIX Mapping page for the missing location.

Is there already an ongoing copy process happening for that location?

• If someone is already copying PMIX data to or from that location then you will be temporarily unable to copy mappings to it. Visit the PMIX Mapping page for that location to see if a copy action is in progress.
• Once the copy process is done then you’ll be able to once again see the location in the list.

Is the location active?

• If the location is marked as “Inactive” in MarginEdge then it will not be available in the location selection list.
• Locations that are “Inactive” will have an “Inactive” icon in the location dropdown list from the top navigation bar.

What does this error mean?

Please see the above section labeled Error Reasons for a list of each of the error messages and what they mean.

If you have questions, or need help with resolving errors from the PMIX copying, then please reach out to help@marginedge.com (and please provide them with the CSVs from the Summary Email!).

Why didn't my mapping copy over?

There could be several reasons why the mapping might not have been successfully copied from the source location to the destination. Attached to the Summary Email (which is sent when the copy action is completed) is a CSV that will list why an item did not have a mapping copied over.

The most common reason is that the item was not found in the destination location. This means an exact match for that item could not be found in the destination location.

For more information on all error messages, please see the Error Reasons section.

If you never received a Summary Email, or you received a Summary Email with a blank/empty CSV, then please reach out to help@marginedge.com and let us know what the source location was and when you initiated the copy action. Reminder that only the user who initiated the copy action will receive the Summary Email.