@senem @LaurenSQ flagging this for the voice ordering team.
We're testing AI voice ordering at our pizza restaurant and hit a wall with nested modifiers. Has anyone else run into this or found a workaround?
Our setup
Our new menu was built around and runs on nested modifiers. So I'm in too deep to turn back ๐
On each pizza, "Remove Toppings" is a parent option, along with Modify Toppings (+ nested) and Remove Toppings (+ nested) and picking it opens the actual choice (No Banana Peppers, No Red Onion, etc.). Add toppings, cheese options, dips and salad dressings work the same way.
None of the child lists are required.
The problem
I called in an order for a pizza with no banana peppers. The AI repeated "no banana peppers" back to me and said it could handle modifiers.
The cart it texted me only showed "Remove Toppings, None." The actual takeoff never made it into the order, so the kitchen ticket just says "Remove Toppings" with nothing to act on.
Steps to reproduce
1. Set up an item with a parent modifier that opens a nested child list
2. Call your Square business number with voice ordering on
3. Order the item with a specific child choice ("no [topping]")
4. Open the texted cart link. Only the parent modifier is there.
It's not just voice. The classic Square Online store does the same thing: it keeps the parent and drops the child.
We moved our ordering link to the new Ordering Profile because of that, but guests with the old link saved still land there.
What works fine
POS, KDS, the new Ordering Profile (web and mobile) and DoorDash all carry the child selection through correctly. So this doesn't look like a catalog setting on our end.
Questions
- Is anyone running voice ordering with nested modifiers successfully?
- Square team: is nested modifier support for voice ordering on the roadmap, and is there a timeline?
- Any workaround that doesn't mean rebuilding everything as flat lists?
We'd love to turn voice ordering on, but we can't trust it with takeoffs until this works.
Thanks!
