This is a design mockup for feedback, not the live product - four different approaches shown below for comparison. Quantities and dietary tags are sample data.
At a glance
A - Total + exceptions One quantity per dish, dietary needs entered as deviations from it. Standard count calculated automatically.
B - Order + separate dietary The order stays a plain list of dish and quantity. Dietary is a distinct section that references dishes already ordered.
C - Flat order lines Order-pad style. Every line is independent and equal - no "parent dish, dietary exception" concept at all.
D - Grid The whole menu is always visible as rows. Type numbers directly into dietary columns, no separate "add" step.

Option A - total, with dietary exceptions

Each dish has one total quantity. Dietary needs are entered as exceptions - "3 standard, plus 1 needs Vegan" - with the standard count calculated automatically.

Add a dish

Selected

Option B - order list, dietary kept separate

The order stays a simple list of what was chosen. Dietary requirements live in their own section below, referencing dishes already in the order.

Order

Dietary requirements

Only for guests who need something different from the standard dish.

Option C - flat order lines

Like an order pad: every line is independent and equal - quantity, dish, dietary - with no "parent dish and exceptions" concept. Dishes are grouped visually only for readability, with a computed total shown per dish.

Order lines

Option D - grid

The full menu is always visible as rows. Type a number directly into the column for the dietary type - no separate "add a dish" step at all.

Dish Standard GF Coeliac Veg Vegan Other Total
For feedback
Try each option with a real scenario from a call you've actually taken - a group with a mix of standard orders and a couple of allergies. Which one is closest to how you'd naturally talk through it? Is there anything none of the four get right?