"What menu would you like for our guests?" is one of the questions venues ask early in the planning, and the answer becomes a logistical headache about three months later when it is time to gather everyone's choices. Most couples handle it badly, not because they are disorganised, but because the tools they use are not built for it.
Here is the realistic way to manage online wedding menu selection in 2026, including the small details that decide whether the catering team thanks you or curses you on the wedding day.
The two ways venues handle menus
Most wedding venues offer one of two menu structures, and your tools should match whichever one yours uses.
Fixed menu, no choices. Everyone gets the same starter, main and dessert. Easy. The only thing you need to track is allergies and intolerances, not preferences.
Multi-choice menu, guests pick. The venue offers two or three options for the main course (meat / fish / vegetarian, sometimes vegan), and you need to give them the count of each one before the wedding.
If you are in the second case — and most couples are — you need a system to collect the choices, summarise them, and hand the venue a clean count. A spreadsheet works for 20 guests. It stops working at 50.
The form fields that matter
The menu section of the RSVP form should have exactly two fields. Anything more and guests start dropping off.
Menu choice (dropdown). A clean dropdown with the categories your venue offers. Three to five options. Each option has a clear name and, ideally, a one-line description: "Beef tenderloin with roasted vegetables", not just "Meat option".
Allergies and intolerances (free text). A single text field where guests type whatever the catering team needs to know. "Lactose intolerant, can have small amounts of butter" is the kind of detail that saves the venue a phone call.
That is it. Do not add "I love spicy food" or "I prefer cooked vegetables". Catering teams cannot personalise individual plates that finely, and the more questions you ask, the more guests skip the menu section entirely.
Kids and special menus
If you are offering a kids menu, treat it as a separate option in the dropdown, not a checkbox somewhere else. Parents need to choose it explicitly: "Kids menu (under 12)". Some venues also offer a "light menu" or a "vegan menu" — same rule, separate option.
The trap to avoid: assuming all kids automatically get the kids menu. Some 11-year-olds want the adult main, some 4-year-olds need to be tracked separately because the kitchen handles them differently. Let the parent choose.
What to show the venue
Two days before the wedding, the venue asks you for the final menu count. They want a number per category, not a list of names. The dashboard should give you that count with one click — group by menu choice, sum, done.
Some venues also want the names per table, with allergies. For that, you generate a per-table sheet showing each guest, their menu choice, and the allergy notes. The catering team uses that sheet on the day to know what plate goes where.
Both views — the count and the per-table sheet — are built into Wedding30s by default. You filter, you export, you send the file to the venue. Five minutes of work the day before the wedding.
The "I will decide on the day" guest
You will have at least one. The guest who fills the RSVP, marks "attending", and leaves the menu choice empty with the implicit assumption that they will decide on the day.
This is a problem because catering teams need the count in advance to order the food. The solution is built into the form: make the menu choice mandatory if "attending = yes". Guests cannot submit the form without picking a menu. They will pick something, even if they end up swapping it on the day.
For the rare case where someone genuinely does not know, add a default option called "I'll go with the recommendation" and pre-assign it to the most popular dish. The venue can plan around that, and the guest gets a plate they did not have to think about.
Common mistakes
Asking for menu choices before the menu is final. If the venue is still tweaking the dishes a month before the wedding, do not push the menu form to guests yet. Wait until the menu is locked, then send it. Guests who already RSVP'd can come back and update their choice.
Mixing the menu choice with other questions. Some couples bundle the menu with "favourite song", "preferred drink", "do you need a chair lift". Each extra question lowers the completion rate. Keep menu and song requests separate, on different sections of the page if you must include both.
Not telling guests when the menu choice closes. Set a clear deadline (typically the same as the RSVP deadline, three weeks before the wedding) and show the countdown on the page. Most guests respond to time pressure better than to friendly reminders.
The 49€ that prevents the headache
You can build all of this in a spreadsheet plus WhatsApp screenshots plus a manual count on the day. You can also use a wedding website builder that handles it by default, for 49€ one time, and spend the saved hours on something that matters more — like writing your vows.
The menu selection is one of the small unglamorous tasks of wedding planning that decides whether the day feels organised or chaotic. The tool you pick to handle it makes more difference than the dish you pick to serve.