April 2027 ☀ Palermo, Italy

Why Attendee Forms Won’t Be on the Checkout Page

In a recent Twitter exchange about where to place conference attendee forms, I asked the WooCommerce community whether they belonged on the single product page, the checkout page, the Thank You page, or somewhere else entirely.

The overwhelming consensus was “checkout page only.”

And yet, for the first time since I started running polls for Checkout Summit decisions, I decided to go against the results. This behind-the-scenes post explains why I’m breaking my own “poll-driven rule,” what influenced my thinking, and how this choice impacts both the attendee experience and the organizational flow.

The Twitter discussion

It all started with a simple question. The replies were quick and clear: if you want attendees to actually complete forms, the checkout page is the “correct answer.” The logic was sound: forms at checkout ensure you capture data upfront, avoid chasing people later, and simplify the admin side.

Why I went against the poll

Despite agreeing with the reasoning, I couldn’t shake two issues. First, checkout should remain as smooth as possible. Adding attendee data forms — sometimes multiple fields per ticket — risks creating friction right before payment. The last thing I want is abandoned carts just because someone didn’t want to type in meal preferences or social links.

Second, forms at checkout would mean repeating the process for each attendee in the same order. That quickly becomes tedious if someone is buying for colleagues. Instead of adding convenience, it might actually slow things down.

My final decision

In the end, I chose to place the forms after the order is completed — on the Thank You page, inside the confirmation email, and within the customer’s My Account section. This way, attendees (or their buyers) have multiple touchpoints to fill in the details at a more relaxed moment, without compromising checkout flow.

The risks

Yes, this means I’ll have to follow up with people who don’t complete the forms right away. There’s a chance some data will never come in. But I’m comfortable making that trade-off. Checkout needs to stay laser-focused on payments, while the rest can happen in the post-purchase journey.

Breaking the “poll-driven rule”

Up until now, every Checkout Summit decision poll I ran on Twitter ended up shaping the actual implementation. This is the first time I’ve gone against a 0% result, and I think that’s a healthy reminder: polls are a great way to get feedback, but they’re not binding. Context, priorities, and personal judgment still matter.

Conclusion

So, while the community voted checkout, the final setup will rely on the Thank You page, confirmation email, and My Account forms.

It may not be the popular choice, but it’s one that to me balances user experience, ticket buyer convenience, and my own peace of mind when it comes to the all-important checkout process.

Sometimes, going against the poll is exactly the right move.

Leave a Reply

Your email address will not be published. Required fields are marked *


Cheers to Our 2026 Partners!

Headline Sponsor

Supporting Sponsors

Side Event Sponsors

{Reloaded} Sponsors

Microsponsors

These attendees went above and beyond!

Media Partners & Press Features

Go With WP Logo
The WP World Logo
PublishPress Logo
WP Builds Logo
WP Minute Logo
The Repository Logo
Webmasters FM Logo
WP-Content.co Logo
Seahawk Logo
WP Pro A to Z Logo
LoopWP Logo
WithinWP Logo
Do The Woo Logo
WP-OK Logo
WP Biz Dev Logo
Seriously Bud Logo
Woo Developer Blog Logo
Tutsflow Logo
Melapress Logo
WP Mayor Logo
StackWC Logo

Founding Contributors

lucia.arsena
Lucia Arsena
#CheckoutSummit