FooEvents Adds Partial Support for the WooCommerce Checkout Block

We’ve just released version 1.20.2 of the FooEvents for WooCommerce plugin, which introduces partial compatibility with the new WooCommerce Checkout and Cart blocks. To take full advantage of this update, please ensure all your installed FooEvents extensions are also updated to their latest versions.

This update makes it possible to use the new WooCommerce Checkout block with FooEvents in cases where event details do not need to be set or modified on the checkout page. It adds compatibility for all event types, and ensures tickets will be generated as expected when the order is completed. Some features that rely on collecting or modifying additional attendee details during checkout—such as seating selection, booking slots, attendee details, or custom attendee details—are only partially supported — see below. 

This release is a stepping stone toward full integration with the WooCommerce block-based checkout experience. Future updates will ensure that all FooEvents features are fully supported in both the Checkout block and classic checkout experiences.

Current Limitations When Using the WooCommerce Checkout Block

Depending on your needs, you can easily switch between the new Checkout block and the classic shortcode-based checkout. The following outlines which FooEvents features are supported by each checkout method and should help you determine which options is best suited for your event.

1. Default Attendee Fields

The Checkout block doesn’t currently support individual attendee details (like first name, last name, email, etc.). These fields are only available through the classic shortcode-based checkout. For now, when using the Checkout block, FooEvents will default to using the billing information for the ticket holder.

2. FooEvents Custom Attendee Fields

If you’re using custom fields to capture additional information (e.g., dietary requirements, t-shirt size), these will not appear on the Checkout block. You’ll need to use the classic checkout for this functionality.

3. FooEvents Bookings

Bookings can’t be selected or changed during checkout when using the Checkout block. Customers will need to choose booking slots directly on the product/event page before adding the event to their cart.

4. FooEvents Seating

Seating selections must also be made on the product/event page. You can’t modify or assign seats at checkout when using the Checkout block.

5. Apple Pay & Google Pay (Stripe Express Checkout)

The WooCommerce Stripe Payment Gateway plugin now uses the WooCommerce Store API. As a result, Apple Pay and Google Pay no longer work with FooEvents when using the classic shortcode-based checkout. If you want to offer Apple Pay or Google Pay, you’ll need to use the new Checkout block.

What’s Next?

We’re currently working on an exciting update that will ensure all FooEvents features—including attendee fields, custom attendee fields, bookings, and seating—are fully compatible with both the Checkout block and classic checkout experience.

This future update will also introduce improvements to the checkout workflow and should help streamline the overall ticket purchase process.

If you’d like to be notified when full support becomes available, sign up here.

Need Help?

If you’re unsure whether to use the Checkout block or classic checkout for your store, or if you have questions about compatibility, feel free to reach out to our support team. We’re happy to assist.