Import Menu File Structure that supports modifiers

[PCPowerUser]

I created a proof of concept Menu file format that WoFlo will import and includes modifiers!

Menu Group

Item Name

Variant / Modifier Group Name

Modifier

Default

Price

A couple notes:  

• Leave the menu group, item, and item price on one row
• Use the next row for any Variants / Sizes.  Name the variant Size, and in subsequent rows use the modifier column to list choices.  (Mark them Size - 6 Piece, Size 12 Piece and the variant name will show only 6 piece).
• Use the next row for the modifier group name, optionally followed by (Optional, mix, max)
• Use additional rows to list ingredients and any additional cost.  optionally adding 'Preselect as Default' to have those marked as included.

Feature:

Once a modifier group has been defined, you can use it on other items without listing included ingredients again.

Problem:

It does not like item-specific modifier groups with matching ingredients.  For example, if you wanted to use a common mod group but using different preselect to identify included ingredients, this does not work.  Better is to just clone groups manually by item instead.

Categories must still be assign manually, but you can use the bulk-select / Actions feature to quickly do that (or ask ManagerBot)

Workflow:

Open Menus, Create a new menu, name and mark channels and hours, then choose Other Source (image, PDF, Custom Website), then scroll down to Upload a file or Photo.  Choose the XLS or CSV and give it about 12 hours.

[kacey_k]

Thanks for sharing this proof of concept! It’s great to see members of the community finding creative ways to streamline menu imports, especially for businesses with complex modifier setups.

Supporting modifiers during import would be a significant time saver for restaurants and other sellers managing large menus. Reducing repetitive manual setup and allowing reusable modifier groups would make onboarding and menu maintenance much more efficient.

I also appreciate that you included both the workflow and the current limitations. That kind of detail helps the product team better understand the real-world use case and evaluate what’s needed for a native solution.

Kudos for putting this together and documenting your findings! I hope the team takes a look at what’s possible here. 👍