topic Re: Menu Build: Build Your Own Menu Items in Restaurant Operations

Menu Build: Build Your Own Menu Items

Sdaniel — Thu, 11 Dec 2025 18:34:46 GMT

Hi everyone!

I’m working on a new Build Your Own Breakfast Wrap, Scrambler, and Skillet setup, and I’m running into a challenge with the meat selection given these limitations:

BYO Structure:

1. Guests may choose up to TWO meats

2. Guests may choose unlimited veggies, cheeses, and sauces

Choose Meat Modifier Group Requirements:

1. Maximum of 2 meats

2. If the guest doesn’t select any meat, the base price should be reduced by $2

Our initial plan was to include a “No Meat” button within the meat selection group that would automatically reduce the price by $2. However, because the group allows up to two selections, guests could select Bacon + No Meat, which creates obvious issues. In store, we can train the staff to avoid this combination, but with online ordering, there’s a much higher risk of guests selecting both.

We're looking for a clean approach for both in store and online ordering.

Suggestions welcomed and appreciated! 🙂

Re: Menu Build: Build Your Own Menu Items

www — Fri, 12 Dec 2025 05:01:24 GMT

The only thing I can think of right now is to set the base price at $2 lower, and then add the meats as a modifier, but then that would require each meat have a certain price.

There is another way that might work (but I haven't tested at all): First create an item called "Meats Selection" and set the base price at $2. Then add to it a modifier group with all your meats (no price for each modifier, 2 selections max).

When you create the Build Your Own Breakfast Wrap, add that item as a modifier (New Modifier from Existing Item).

Of course you still need to set the base price as $2 less, but if they don't select the Meat modifier, then it will be the correct price. And if they do select it, it will just be $2 more, as the meat selections don't have a price.

Re: Menu Build: Build Your Own Menu Items

Sdaniel — Fri, 12 Dec 2025 16:20:05 GMT

Hi!

Thank you for the suggestion! That was actually where my mind was going as well. Unfortunately, I have to stick to the pricing structure that was given to me. The base price is meant to cover the meat plus unlimited veggies, cheeses, and sauces. Lowering the base price by $2 and pricing the meat as an add-on would definitely be ideal, but the menus have already been sent to print, and it might look a bit odd if our online ordering prices don’t match what’s printed.

Re: Menu Build: Build Your Own Menu Items

rcmck — Fri, 12 Dec 2025 16:53:21 GMT

How is the meat selection group setup, can same mod be added twice? If someone wants bacon for both their meats would they select 2x bacon? If it is could you just make no meat subtract $1 and if customer wants no meat at all they would select 2x no meat? As long as that doesn't also violate the pricing structure you need to follow and the kitchen understands a ticket with 1 meat 1 no meat is just half portion.

Re: Menu Build: Build Your Own Menu Items

Sdaniel — Fri, 12 Dec 2025 21:55:02 GMT

Hi! I was able to use the suggestion @www suggested. I had been under the impression that we only listed the price with meat on our printed menu, but the price without meat is also shown. Now I’ll be able to price each meat individually, and adding meat (with a maximum of two) will correctly adjust the total to the “with meat” price. 🙂

Re: Menu Build: Build Your Own Menu Items

Sdaniel — Fri, 12 Dec 2025 21:58:02 GMT

While I have you here… do you know if sequence pricing works with third-party ordering? We have another menu setup where we allow two free ingredients for griddle items, and any additional ingredients after the first two cost $0.50. I can get this working with sequence pricing on the POS/online ordering, but I’m not sure whether there are limitations for third-party platforms.

Re: Menu Build: Build Your Own Menu Items

rcmck — Fri, 12 Dec 2025 22:32:25 GMT

Last I knew it was not supported by anything but toast online ordering and mo&p (documentation still shows that as well). Which is unfortunate because it can make some things a lot easier.