A conference RSVP needs one thing: a headcount. A wedding RSVP needs four. The caterer wants a plate count broken down by meal choice three weeks before the event, not the night before. The couple wants to know how many of the 120 people they invited are actually bringing a plus-one, because that number decides whether the reception hall holds everyone. Somebody has to chase the dozen relatives who never answered, and somebody has to turn all of that into a single list the venue coordinator can read without a login.
Most WordPress RSVP plugins are built for the first case. They collect a yes, a no, and an email address, and they call it done. That works for a webinar. It falls apart the moment “yes” needs to come with a meal choice, a guest count, and a deadline that actually gets enforced. This guide walks through building a wedding RSVP flow on WordPress with Eventonomy, a free self-hosted events and RSVP plugin from Wbcom Designs, and it is honest about where the free plugin’s generic RSVP fields need a small workaround to do wedding-specific work.
Last updated: 6 November 2026
Table of Contents
- By the numbers
- Why a wedding RSVP is not a normal event RSVP
- The numbers behind the chase
- A real scenario: Elena and Marcus build their own wedding page
- Step 1: Set up the wedding event
- Step 2: Configure guest count and meal choice
- Step 3: Set the RSVP deadline and reminders
- Step 4: Publish privately and send the link
- Step 5: Read the guest list and export it for the caterer
- What Eventonomy does not do for a wedding
- What this costs
- FAQ
- Sources
By the numbers
The global event management software market was valued at USD 16.0 billion in 2025 and is projected to reach USD 39.6 billion by 2033, an 11.5% annual growth rate from 2026, according to Grand View Research.
Why a wedding RSVP is not a normal event RSVP
A meetup RSVP answers one question: is this person coming. A wedding RSVP has to answer four, for a guest list the couple only gets to send once.
- Guest count. Invitations go out per household, not per person. “The Alvarez Family” might mean two people or five, and the venue’s capacity and the caterer’s order both depend on getting that number right before the final headcount is due.
- Meal choice. Plated dinners need an answer per guest, not per invitation. Chicken, salmon, or the vegetarian option, collected early enough that the caterer can place the order.
- A deadline that means something. Caterers and venues work off a final-count date, usually two to three weeks out. An RSVP system that does not track or enforce that date leaves the couple manually counting replies against a spreadsheet.
- A personal, branded page. Guests expect a page with the couple’s names, their date, and their story, not a generic ticketing widget that looks like it belongs to a software company.
Generic WordPress RSVP and form plugins can collect a yes or no. Few of them connect that yes to a guest count, a required meal question, and a deadline the site actually enforces, without you bolting together three separate plugins to do it.
The numbers behind the chase: the U.S. wedding industry is valued at more than $100 billion, with roughly 2 million weddings taking place in 2025, according to The Knot Worldwide’s 2026 Real Weddings Study (reported via 5W Public Relations on PR Newswire). The same research found that AI adoption among engaged couples nearly doubled year-over-year to 36% in wedding planning tasks. Couples are already running their weddings through digital tools for budgeting, vendor research, and planning, the RSVP is one of the few steps many of them still manage by hand, in a shared spreadsheet, updated from texts and phone calls.
A real scenario: Elena and Marcus build their own wedding page
Elena and Marcus are getting married in October, 90 guests, plated dinner, two meal choices plus a vegetarian option. They looked at a dedicated wedding-site builder first and backed out when they saw the subscription required to keep the site live past the wedding date, plus a cap on guest list size on the free tier. Marcus already runs a WordPress site for his design business, so they decided to build the wedding page there instead: their own domain, their own photos, no monthly fee, and no company holding their guest list hostage behind a paywall after the wedding is over.
They installed Eventonomy, free, and built the RSVP page in an afternoon. What follows is the exact sequence they used, and the two places where the free plugin’s generic tools needed a small workaround instead of a dedicated wedding field.
Step 1: Set up the wedding event
Install Eventonomy and create a new event the same way you would for any other gathering, with two settings changed immediately because the defaults are built for a public meetup, not a private wedding.
- Turn off account creation for guests. Under Settings → Registration, Eventonomy’s default behavior creates a WordPress account for every new email address that RSVPs. Switch “Do attendees need an account?” to “Guest, no account.” A guest’s great-aunt is not going to register for a website to say yes to a wedding, and any RSVP flow that asks her to will lose her.
- Create the event as a draft. Build the page with the couple’s photo, the date, the venue, and the story while it is still a draft, visible only to people logged into the WordPress admin. Nobody outside the wedding party sees it until it is ready.
- Set the capacity to the guest count. Eventonomy’s RSVP block tracks “spots left” against a capacity number you set on the event. Set it to the venue’s seated capacity, not the invitation count, so the running total guests see matches the room.
Eventonomy’s own RSVP widget, live on its site, shows what guests land on: a three-option RSVP (Going, Maybe, No), a running “spots left” counter, and an “Additional guests” field for the plus-one count.
Step 2: Configure guest count and meal choice
This is where it is worth being precise about what Eventonomy actually does, because “handles plus-ones and meal choices” covers two features that work differently under the hood.
Guest count (the plus-one)
The RSVP form includes an “Additional guests” field by default. It is a number, not a guest list: a guest who RSVPs for themselves plus two others enters “2,” and Eventonomy adds those two to the event’s capacity count automatically. There is a site-wide plus-one cap under Settings → Registration that limits how many extra guests any single RSVP can bring, or switches the feature off entirely if you want every invitation answered as a single headcount.
Where this needs a workaround: that additional-guests number has no field for the extra guest’s name. If “Jordan + guest” RSVPs for two, Eventonomy records the count but not who the second person is. If the couple needs the plus-one’s name, for a place card or a seating chart, the practical fix is to add a short-text custom question, “If you’re bringing a guest, what’s their name?”, rather than expect a dedicated field that does not exist in the free plugin.
Meal choice
Meal selection is not a built-in wedding field either. It runs through Eventonomy’s custom RSVP questions, a general-purpose feature with ten answer types, from short text to a required dropdown or checkboxes. Switch on custom questions under the event’s RSVP settings, then add a question such as “Entrée choice” as a required dropdown with your three options (herb-roasted salmon, braised short rib, garden risotto, for example). Mark it required so the RSVP cannot submit without an answer, and add a second optional short-text question for dietary notes or allergies.
Each guest’s answer rides alongside their RSVP, and when you export the attendee list, every custom question becomes its own column in the CSV, scoped to that event. That is how the caterer gets a clean per-guest meal breakdown: not from a built-in tally inside Eventonomy, but from the export.
Being direct about the gap here: Eventonomy has no running counter that adds up meal choices as RSVPs arrive. You get the count by exporting to CSV and filtering or building a pivot table in a spreadsheet, which takes under a minute once the export is in hand, but it is manual, not automatic. If that single step matters to you, budget for it rather than expecting a live dashboard tally.
Step 3: Set the RSVP deadline and reminders
Caterers and venues work off a final-count date, and Eventonomy enforces one, but the setting lives in an unexpected place and unit. Under Settings → Registration, the RSVP deadline is counted in hours before the event start time, not in a calendar date. Three weeks out is 504 hours. Set that number once and Eventonomy closes new RSVPs automatically when the window passes, so stragglers cannot submit a response the caterer has no way to act on.
Two details worth knowing before you set it:
- The deadline is site-wide, not per-event. If the same WordPress site runs more than one wedding or private event (a wedding planner managing several couples’ sites from one install, for example), the deadline and the plus-one cap apply to every event on that site. There is no per-event override in the free plugin.
- Reminders are included free, with a cadence you set rather than a custom schedule. Eventonomy sends reminder emails at set intervals ahead of the deadline on the free tier. Eventonomy Pro adds configurable reminder scheduling and SMS reminders via Twilio, plus custom email templates, for couples or planners who want to control exactly when and how a nudge goes out. For a single wedding, the free tier’s interval-based reminders are usually enough to catch guests who have not answered before the window closes.
Every RSVP also triggers a confirmation email containing a signed magic link, valid for seven days by default and renewable from the RSVP page, that lets that one guest change or cancel their answer without creating an account or remembering a password.
Step 4: Publish privately and send the link
Eventonomy gives an event three visibility states, and the one built for exactly this situation is the middle one.
| Status | Who sees it | Use it for |
|---|---|---|
| Draft | Only logged-in admins | Building the page before the couple signs off |
| Private | Anyone with the direct link | Sending invitations, never appears in listings, calendars, or feeds |
| Published | Everyone, listed publicly | A public event, not a wedding |
Review the page with the couple while it is a draft, then publish it as Private. A Private event never shows up on the site’s public events page, calendar, or any discovery feed; the only way in is the direct link, which goes out with the invitations, in a text, or on a printed card. Be straightforward with guests about one tradeoff: Private means link-only, not password-protected. Anyone the link gets forwarded to can open the page and RSVP, the same way a Google Doc set to “anyone with the link” works. For a wedding, where the invite list is who you trust with the address, that is usually an acceptable line to draw. If a household shares one email address, have them RSVP once with a guest count rather than trying to submit twice: Eventonomy allows one active RSVP per email address per event, and a second submission from the same address overwrites rather than adds to the first.
Step 5: Read the guest list and export it for the caterer
Attendees land in Eventonomy’s wp-admin screen the same way any other event’s RSVPs do: a filterable list under Eventonomy → Attendees & Orders, showing each guest’s name, email, RSVP status, guest count, and every custom question’s answer next to their name. That screen is the “guest list the couple can see at a glance” the free plugin actually delivers: sortable, filterable by RSVP status, and current the moment a guest submits.
When the caterer’s final-count date arrives, export straight to CSV from that same screen. Names, guest counts, and every custom question’s answer, including the meal choice, come out as one spreadsheet-ready file, one column per question. Pull a fresh export whenever the caterer, the venue, or the day-of coordinator asks for an updated number; there is no limit on how many times you can run it, and each export reflects the current state of RSVPs at the moment you download it.
A privacy note worth passing to whoever manages the site: Tools → Export Personal Data returns one guest’s own RSVP history by their email address, and erasing a guest’s data anonymizes their RSVP while keeping the seat count intact, rather than silently throwing off the headcount. Only give admin access to the event to the couple and the planner, not to every bridesmaid helping with setup, since anyone with access to manage the event can see every guest’s answers.
What Eventonomy does not do for a wedding
A fair how-to guide says what the tool does not cover, not just what it does. Eventonomy is a free RSVP and events plugin, not wedding-planning software, and it is explicit about that scope on its own site. Here is the honest list, and what to pair it with instead.
- No seating chart or table assignment builder. You build those from the CSV export, in a spreadsheet or a dedicated seating-chart tool, not inside Eventonomy.
- No running meal-choice tally. As covered above, the count comes from filtering the CSV export, not a live dashboard number.
- No unique invitation link per guest. Every guest RSVPs through the same shared event link; Eventonomy does not generate a personalized tracking link per invitee the way some dedicated wedding-site tools do. Guests identify themselves by name and email when they RSVP, and get their own private magic link afterward to manage that one response.
- No separate name field for a plus-one. Covered in Step 2: the additional-guests field is a count, so capture a plus-one’s name with a custom text question if you need one.
- No gift registry, cash fund, or honeymoon fund. None of that exists in the plugin; link out to whatever registry service the couple already uses.
- No printed invitations. Eventonomy runs the RSVP page and the digital side; physical invitations and save-the-dates are a separate job.
None of these are hidden costs. They are the difference between an RSVP and ticketing plugin built to run any kind of event, and a single-purpose wedding website service that bundles seating charts and registries into a subscription. For a couple building their own site, free RSVP infrastructure plus a spreadsheet for the seating chart is a reasonable trade for not paying a monthly fee to keep a guest list online.
What this costs
Everything in this guide runs on Eventonomy’s free tier: unlimited events and RSVPs, the going/maybe/no flow with a waitlist, custom RSVP questions, the plus-one count and capacity cap, the deadline and reminder emails, and the CSV export. None of it requires Eventonomy Pro.
Pro becomes relevant only if money changes hands at the wedding itself, for example selling tickets to a separate engagement party or a public reception add-on through Stripe, PayPal, or WooCommerce, or if the couple or their planner wants SMS reminders, a door check-in scanner for a large reception, or analytics across several events. Pro runs $99 a year for one site, $199 a year for five sites, or $249 a year for unlimited sites, with matching lifetime-license options at $249, $499, and $629. For a single wedding with a free RSVP, most couples will never need to open their wallet for this plugin at all.
Build the wedding RSVP page on your own site
If you already have a WordPress site, or are willing to spin one up on hosting you control, download Eventonomy free and build the RSVP flow above in an afternoon, the same way Elena and Marcus did. No subscription to keep the guest list online, no company holding the data after the wedding, and the plugin stays useful for every event that comes after it.
The bottom line
A wedding RSVP is not harder than a meetup RSVP because the technology is more complex. It is harder because a wedding only gets one invitation list, one final count, and one chance to get the meal order right. Eventonomy’s free tier covers the real requirements, guest counts, required meal questions, a deadline that actually closes the form, reminder emails, and a CSV export the caterer can use, without asking the couple to pay a subscription to keep their own wedding website online. It will not build a seating chart or total the meal count on a dashboard for you, and being upfront about that gap is more useful than pretending it is not there. For a couple willing to spend an afternoon setting it up, that is a fair trade for owning the data and the page long after the wedding is over.
FAQ
Does Eventonomy have a dedicated wedding RSVP feature?
No. Eventonomy is a general-purpose events and RSVP plugin with a “For Weddings” landing page that walks through using its general RSVP, custom questions, and capacity features for a wedding specifically. There is no wedding-only mode; everything in this guide uses the same RSVP system Eventonomy ships for any event type.
Can guests select a meal choice when they RSVP?
Yes, through a custom RSVP question set as a required dropdown. It is not a dedicated “meal choice” field, but a general custom-question feature configured to do that job, and it works the same way whether you are asking about an entrée, a shuttle time, or a song request.
Does Eventonomy track how many guests someone is bringing?
Yes, through the “Additional guests” number field on the RSVP form. Each additional guest counts toward the event’s capacity automatically. The field records a count, not a name, so capture a plus-one’s name separately with a custom text question if you need one for place cards or a seating chart.
Can I set a different plus-one limit for each wedding?
Not in the free plugin. The plus-one cap and the RSVP deadline are both site-wide settings under Settings → Registration, so if one WordPress site runs multiple weddings or private events, the same limits apply across all of them.
Is there an RSVP deadline, and can I send reminders before it?
Yes to both. Set the deadline in hours before the event start (three weeks out is 504 hours) under Settings → Registration, and Eventonomy closes new RSVPs automatically once it passes. Reminder emails at set intervals are included free; Pro adds configurable reminder timing and SMS reminders through Twilio.
Can guests change their RSVP after submitting it?
Yes. Every RSVP triggers a confirmation email with a private, signed magic link that lets that guest update or cancel their response without creating an account. The link is valid for seven days by default and a guest can request a fresh one from the RSVP page at any time.
Do guests need to create an account to RSVP?
Only if you leave Eventonomy’s default setting as-is. Switch “Do attendees need an account?” to “Guest, no account” under Settings → Registration before sending invitations, or every new guest email will have a WordPress account created for them, which most wedding guests do not expect and will not want.
Can I see a seating chart or table assignments in Eventonomy?
No. Eventonomy does not build seating charts or assign tables. Export the attendee list to CSV and build the seating chart in a spreadsheet or a dedicated seating-chart tool from there.
How much does Eventonomy cost for a wedding website?
Free, for everything covered in this guide. Pro, starting at $99 a year for one site, is only necessary if you are selling tickets to a related event through Stripe, PayPal, or WooCommerce, or want SMS reminders, door check-in, or analytics.
Can two people share one invitation and RSVP together?
Yes, as a single RSVP with a guest count rather than two separate submissions. Eventonomy allows one active RSVP per email address per event, and a second submission from the same address overwrites the first rather than adding to it, so a couple sharing an email should answer once and set their guest count to match.
Sources
- Grand View Research: Event Management Software Market
- Wbcom Designs: Eventonomy pricing and plans (checked 6 November 2026)